ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan <leutnant....@gmail.com>
Subject Re: a tale of two receives
Date Fri, 03 Aug 2007 00:40:54 GMT
The behavior sounds very similar.  I don't get that particular exception,

Usually all I get is 'exchange not found' when servicemix or jetty gives up:
DEBUG - DeliveryChannelImpl            - Accepting ID:
localhost.localdomain-56122-1186064097134-3:44 in
<< Aprox 1min timeout here >>
DEBUG - JettyContextManager            - Dispatching job: HEP@3150098
DEBUG - jetty                          - resume continuation
java.lang.IllegalStateException: Exchange not found
        at org.apache.servicemix.http.processors.ConsumerProcessor.process(

If I try to use joins in a flow I get a nullpointer when the correlation key
is initialized in the opposite branch.

ERROR - BpelEngineImpl                 - Scheduled job failed;
jobDetail={type=MATCHER, inmem=true, ckey=null, correlatorId=30.operationB,
        at org.apache.ode.bpel.common.CorrelationKey.<init>(
        at org.apache.ode.bpel.engine.WorkEvent.getCorrelationKey(


On 8/2/07, Paul Brown <paulrbrown@gmail.com> wrote:
> On 8/2/07, Dan <leutnant.dan@gmail.com> wrote:
> > I'm having difficulty orchestrating a sequence of receives with ode-jbi.
> > While the first message is always received correctly, the second message
> > gets delivered by jetty to ode, but ode never seems to act on it.
> > Eventually jetty reports exchange not found.
> I had a similar issue with the AXIS integration layer and a sequence
> of receives; I think that I narrowed it down to an issue with
> correlations.  Have a look at ODE-137 and see if that looks similar to
> your situation:
> https://issues.apache.org/jira/browse/ODE-137
> -- Paul

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message