This week's book giveaway is in the Servlets forum.
We're giving away four copies of Murach's Java Servlets and JSP and have Joel Murach on-line!
See this thread for details.
The moose likes Tomcat and the fly likes fuego.papi.impl.EngineExecutionException: Process execution engine execution error.Oracle BPM-Tomcat Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Products » Tomcat
Bookmark "fuego.papi.impl.EngineExecutionException: Process execution engine execution error.Oracle BPM-Tomcat" Watch "fuego.papi.impl.EngineExecutionException: Process execution engine execution error.Oracle BPM-Tomcat" New topic
Author

fuego.papi.impl.EngineExecutionException: Process execution engine execution error.Oracle BPM-Tomcat

Vinod Vijay
Ranch Hand

Joined: Sep 13, 2011
Posts: 137

Hi I'm getting below issue. I'm using Tomcat 7 and Oracle BPM. While trying to call the Approval service, Im getting below error. When I checked the at BPM side, actually code is working, Approval is happening but still somehow I'm getting this issue on my server console. Any Idea? I heard abouty WebLogic with Oracle BPM works fine. Is there any specific configuration I need to do at Tomcat side to resolve this issue?

Kindly suggest

fuego.papi.impl.EngineExecutionException: Process execution engine execution error.
Operation exception.

Caused by: invalid type code: AC; nested exception is:

java.io.StreamCorruptedException: invalid type code: AC

Caused by: invalid type code: AC

fuego.papi.OperationException: Operation exception.

at fuego.papi.OperationException.wrap(OperationException.java:65)

at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.disconnectProcessControl(J2EEEngineAccessImpl.java:207)

at fuego.papi.impl.ProcessServiceSessionImpl.disconnectProcessControls(ProcessServiceSessionImpl.java:4129)

at fuego.papi.impl.ProcessServiceSessionImpl.disconnectFromEngines(ProcessServiceSessionImpl.java:3855)

at fuego.papi.impl.ProcessServiceSessionImpl.close(ProcessServiceSessionImpl.java:3832)

at com.erms.ermsinterface.process.service.BaseProcessService.closeProcessServiceSession(BaseProcessService.java:87)

at com.erms.ermsinterface.process.ERMSProcess.closeUserSession(ERMSProcess.java:119)

at com.erms.ermsinterface.process.ERMSProcess.sendToMO(ERMSProcess.java:2616)

at com.erms.ermsinterface.workflow.ProcessInterface.sendForApproval(ProcessInterface.java:8050)

at com.erms.manager.WorkPermitManager.updateKPEAccessRequestJobWorkFlow(WorkPermitManager.java:799)

at com.erms.manager.WorkPermitManager.processKPEAccessJob(WorkPermitManager.java:703)

at com.erms.action.KPEAuthorizationAccessApprovalAction.executeSubmit(KPEAuthorizationAccessApprovalAction.java:297)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:280)

at org.apache.struts.actions.DispatchAction.execute(DispatchAction.java:216)

at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)

at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)

at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)

at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)

at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)

at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)

at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)

at java.lang.Thread.run(Thread.java:619)

Caused by: java.rmi.UnmarshalException: invalid type code: AC; nested exception is:

java.io.StreamCorruptedException: invalid type code: AC

at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:350)

at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)

at fuego.ejbengine.EJBProcessControl_1zamnl_EOImpl_1030_WLStub.remove(Unknown Source)

at fuego.papi.impl.j2ee.EJBProcessControlInterfaceWrapper.remove(EJBProcessControlInterfaceWrapper.java:2321)

at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.disconnectProcessControl(J2EEEngineAccessImpl.java:204)

... 34 more

Caused by: java.io.StreamCorruptedException: invalid type code: AC

at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1356)

at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)

at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)

at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)

at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)

at weblogic.rjvm.ResponseImpl.getReplicaInfo(ResponseImpl.java:211)

at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:339)


Vinod Vijay Nair
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 15952
    
  19

Hmmm. I think that "quote" doesn't make stack traces easier to read. Oh well.

There are things in your stack trace that would make me wonder if you are actually running under Tomcat or if you are running under WebLogic.

You cannot include WebLogic classes in a Tomcat webapp, however, if that's what you're doing.


Customer surveys are for companies who didn't pay proper attention to begin with.
Vinod Vijay
Ranch Hand

Joined: Sep 13, 2011
Posts: 137

Tim Holloway wrote:Hmmm. I think that "quote" doesn't make stack traces easier to read. Oh well.

There are things in your stack trace that would make me wonder if you are actually running under Tomcat or if you are running under WebLogic.

You cannot include WebLogic classes in a Tomcat webapp, however, if that's what you're doing.


I myself have figured out the root cause of issue. It was pointing to wrong JRE. I have pointed to JRE1.5 and it started working fine.
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: fuego.papi.impl.EngineExecutionException: Process execution engine execution error.Oracle BPM-Tomcat
 
Similar Threads
StreamCorruptedException error
Problem while using JXLS API
Problem in struts DispatchAction
Access datasource from standalone application using weblogic 9.0 getting exception
java.rmi.UnmarshalException: failed to unmarshal interface java.util.Set; nested exce