Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via ode-dev by Rafal Rusin (JIRA), 1 year ago
via ode-dev by Rafal Rusin (JIRA), 1 year ago
java.lang.IllegalArgumentException: INTERNAL ERROR: No ENTRY for RESPONSE CHANNEL 123 at org.apache.ode.bpel.engine.OutstandingRequestManager.associate(OutstandingRequestManager.java:145) at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.inputMsgMatch(BpelRuntimeContextImpl.java:872) at org.apache.ode.bpel.engine.PartnerLinkMyRoleImpl.invokeInstance(PartnerLinkMyRoleImpl.java:211) at org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:198) at org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(BpelProcess.java:362) at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:328) at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:373) at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:341) at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:340) at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:179) at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:339) at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:336) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595)