Friday, December 17, 2010

ETM Patch for new fusion look and feel

ETM 2.2.0 has released a patch that allows the UI to be presented with a new fuision look and feel. Check on my oracle support patch #10170659.
Posted by at
Labels: ,

2 comments:

mdalton said...

Has anyone found a bug after installing ETM V2.2.0 SP3 and FW SP9 where you begin getting errors when querying data. The errors are all about method handler failure and unable to call java from Cobol.
see below the actual errors (we need to find out the problem asap - any help is great)

ACCTUSR1 - 212846-23-1 2011-01-31 17:02:13,093 [Parent Reader:Thread-15] ERROR (support.cobol.JavaRowProgramHandler) Err
or occurred while calling Java from COBOL program CIPCPERR
ACCTUSR1 - 212846-23-1 2011-01-31 17:02:13,093 [Parent Reader:Thread-15] ERROR (support.cobol.CobolToJavaGateway) Error
invoking method handle
ACCTUSR1 - 212846-23-1 2011-01-31 17:02:13,109 [Parent Reader:Thread-15] ERROR (support.cobol.CobolToJavaGateway) A syst
em error occurred calling method handle on class com.splwg.base.support.cobol.JavaRowProgramHandler
com.splwg.shared.common.LoggedException:
The following stacked messages were reported as the LoggedException was rethrown:
java.lang.reflect.Method.invoke(Unknown Source): Error invoking method handle
com.splwg.base.support.cobol.JavaRowProgramHandler.privateHandle(JavaRowProgramHandler.java:97): Error occurred while ca
lling Java from COBOL program CIPCPERR

The root LoggedException was: Cannot retrieved cobol field instance from dto for field BO_DEFN_AREA
at com.splwg.shared.common.LoggedException.raised(LoggedException.java:65)
at com.splwg.base.support.cobol.entities.TCopybookFactory.newInstance(TCopybookFactory.java:180)
at com.splwg.base.support.cobol.entities.TCopybookFactory.newInstance(TCopybookFactory.java:170)
at com.splwg.base.support.cobol.entities.TCopybookFactory.newInstance(TCopybookFactory.java:165)
at com.splwg.base.support.cobol.JavaRowProgramHandler.privateHandle(JavaRowProgramHandler.java:97)
at com.splwg.base.support.cobol.JavaRowProgramHandler.handle(JavaRowProgramHandler.java:83)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.splwg.base.support.cobol.CobolToJavaGateway$MethodDispatcherCache$MethodDispatcher.dispatchToRequestedMet
hod(CobolToJavaGateway.java:337)
at com.splwg.base.support.cobol.CobolToJavaGateway$MethodDispatcherCache$MethodDispatcher.access$300(CobolToJava
Gateway.java:255)
at com.splwg.base.support.cobol.CobolToJavaGateway$MethodDispatcherCache.dispatchToRequestedMethod(CobolToJavaGa
teway.java:250)
at com.splwg.base.support.cobol.CobolToJavaGateway$MethodDispatcherCache.access$000(CobolToJavaGateway.java:232)

at com.splwg.base.support.cobol.CobolToJavaGateway.callJava(CobolToJavaGateway.java:65)
at com.splwg.base.support.cobol.host.command.CobolToJavaGatewayCommand.invoke(CobolToJavaGatewayCommand.java:33)

at com.splwg.base.support.cobol.host.PerformCommandExecuter.invoke(PerformCommandExecuter.java:68)
at com.splwg.base.support.cobol.host.OptimizedRemoteExecuterSkel$RequestSocketReader.readRequestExecuteAndRespon
d(OptimizedRemoteExecuterSkel.java:157)
at com.splwg.base.support.cobol.host.OptimizedRemoteExecuterSkel$RequestSocketReader.run(OptimizedRemoteExecuter
Skel.java:91)
at com.splwg.base.support.cobol.host.SocketThreadPool$WrappingParentRunnable.run(SocketThreadPool.java:204)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

January 31, 2011 at 5:05 PM
Allan Gaffen said...

recommend you open an SR on this, and provide all the logs. It could be an install issue, memory, cobol not firedup ? could be some settings.

February 1, 2011 at 4:22 AM

Post a Comment

Subscribe to: Post Comments (Atom)