You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by Eduardo Burgos <eb...@gmail.com> on 2007/07/28 00:36:25 UTC

about ode-jbi and flows

Hi,

I just got this error right when my process finishes the execution, when its
trying to return the result to another endpoint.



18:18:55,472 | ERROR | pool-11-thread-1 | OdeService               |
org.apache.ode.jbi.OdeService   312 | Error bridging ODE out response:
javax.jbi.messaging.MessagingException: Flow 'Seda' was specified but not
able to handle exchange
    at org.apache.servicemix.jbi.nmr.flow.DefaultFlowChooser.chooseFlow(
DefaultFlowChooser.java:46)
    at org.apache.servicemix.jbi.nmr.DefaultBroker.sendExchangePacket(
DefaultBroker.java:277)
    at org.apache.servicemix.jbi.security.SecuredBroker.sendExchangePacket(
SecuredBroker.java:81)
    at org.apache.servicemix.jbi.container.JBIContainer.sendExchange(
JBIContainer.java:793)
    at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(
DeliveryChannelImpl.java:381)
    at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(
DeliveryChannelImpl.java:417)
    at org.apache.ode.jbi.OdeService.outResponse(OdeService.java:309)
    at org.apache.ode.jbi.OdeService.onResponse(OdeService.java:195)
    at org.apache.ode.jbi.MessageExchangeContextImpl.onAsyncReply(
MessageExchangeContextImpl.java:53)
    at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.reply(
BpelRuntimeContextImpl.java:582)
    at org.apache.ode.bpel.runtime.REPLY.run(REPLY.java:64)
    at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.apache.ode.jacob.vpu.JacobVPU$JacobThreadImpl.run(JacobVPU.java
:451)
    at org.apache.ode.jacob.vpu.JacobVPU.execute(JacobVPU.java:139)
    at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.execute(
BpelRuntimeContextImpl.java:834)
    at org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(
BpelProcess.java:336)
    at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(
BpelEngineImpl.java:318)
    at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(
BpelServerImpl.java:364)
    at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(
SimpleScheduler.java:316)
    at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(
SimpleScheduler.java:315)
    at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(
SimpleScheduler.java:154)
    at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(
SimpleScheduler.java:314)
    at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(
SimpleScheduler.java:311)
    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)




Is there a problem with Seda flows and ode? What could be happening there?
Please help me.

Re: about ode-jbi and flows

Posted by Alex Boisvert <bo...@intalio.com>.
Oooops.  Yes, it's -Dorg.apache.ode.jbi.sendSynch=true.   Apparently I've
been misguiding a lot of people recently.  :-|

alex


On 7/31/07, Eduardo Burgos <eb...@gmail.com> wrote:
>
> yep, I found it, thanks, I also found in the code that its "sendSynch"
> instead of "sendSync", is that correct?
>
> On 7/30/07, Alex Boisvert <bo...@intalio.com> wrote:
> >
> > You add it to your JAVA_OPTS environment variable, or directly in
> > servicemix.sh / servicemix.bat (see DEFAULT_JAVA_OPTS).   It is a
> > command-line parameter for the "java" executable, e.g.,
> >
> > java -Dorg.apache.ode.jbi.sendSync=true [other arguments]
> >
> > alex
> >
> >
> > On 7/30/07, Eduardo Burgos <eb...@gmail.com> wrote:
> > >
> > > where can I put this -Dorg.apache.ode.jbi.sendSync
> > > >
> > > > =true option?
> > >
> > >
> > > On 7/29/07, Alex Boisvert <bo...@intalio.com> wrote:
> > > >
> > > > Hi Eduardo,
> > > >
> > > > I'm not sure what's happening so I'll need more information to help
> > you.
> > > > This error can happen if the flow is marked as persistent, clustered
> > or
> > > > transacted.  SedaFlow doesn't support these "qualities of service"
> > > (QoS).
> > > > You can check the code where the exchange is created, and perhaps
> try
> > > with
> > > > "-Dorg.apache.ode.jbi.sendSync=true" to see if you get better result
> > (or
> > > > better error reporting) that way.
> > > >
> > > > alex
> > > >
> > > > On 7/27/07, Eduardo Burgos <eb...@gmail.com> wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I just got this error right when my process finishes the
> execution,
> > > when
> > > > > its
> > > > > trying to return the result to another endpoint.
> > > > >
> > > > >
> > > > >
> > > > > 18:18:55,472 | ERROR | pool-11-thread-1 | OdeService
> |
> > > > > org.apache.ode.jbi.OdeService   312 | Error bridging ODE out
> > response:
> > > > > javax.jbi.messaging.MessagingException: Flow 'Seda' was specified
> > but
> > > > not
> > > > > able to handle exchange
> > > > >     at
> > > org.apache.servicemix.jbi.nmr.flow.DefaultFlowChooser.chooseFlow(
> > > > > DefaultFlowChooser.java:46)
> > > > >     at
> > org.apache.servicemix.jbi.nmr.DefaultBroker.sendExchangePacket(
> > > > > DefaultBroker.java:277)
> > > > >     at
> > > > org.apache.servicemix.jbi.security.SecuredBroker.sendExchangePacket
> > > > > (
> > > > > SecuredBroker.java:81)
> > > > >     at
> org.apache.servicemix.jbi.container.JBIContainer.sendExchange
> > (
> > > > > JBIContainer.java:793)
> > > > >     at
> > org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(
> > > > > DeliveryChannelImpl.java:381)
> > > > >     at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(
> > > > > DeliveryChannelImpl.java:417)
> > > > >     at org.apache.ode.jbi.OdeService.outResponse(OdeService.java
> > :309)
> > > > >     at org.apache.ode.jbi.OdeService.onResponse(OdeService.java
> :195)
> > > > >     at org.apache.ode.jbi.MessageExchangeContextImpl.onAsyncReply(
> > > > > MessageExchangeContextImpl.java:53)
> > > > >     at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.reply(
> > > > > BpelRuntimeContextImpl.java:582)
> > > > >     at org.apache.ode.bpel.runtime.REPLY.run(REPLY.java:64)
> > > > >     at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown
> Source)
> > > > >     at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > > > > DelegatingMethodAccessorImpl.java:25)
> > > > >     at java.lang.reflect.Method.invoke(Method.java:585)
> > > > >     at org.apache.ode.jacob.vpu.JacobVPU$JacobThreadImpl.run(
> > > > JacobVPU.java
> > > > > :451)
> > > > >     at org.apache.ode.jacob.vpu.JacobVPU.execute(JacobVPU.java
> :139)
> > > > >     at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.execute(
> > > > > BpelRuntimeContextImpl.java:834)
> > > > >     at org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(
> > > > > BpelProcess.java:336)
> > > > >     at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(
> > > > > BpelEngineImpl.java:318)
> > > > >     at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(
> > > > > BpelServerImpl.java:364)
> > > > >     at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(
> > > > > SimpleScheduler.java:316)
> > > > >     at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(
> > > > > SimpleScheduler.java:315)
> > > > >     at
> > org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction
> > > (
> > > > > SimpleScheduler.java:154)
> > > > >     at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(
> > > > > SimpleScheduler.java:314)
> > > > >     at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(
> > > > > SimpleScheduler.java:311)
> > > > >     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)
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Is there a problem with Seda flows and ode? What could be
> happening
> > > > there?
> > > > > Please help me.
> > > > >
> > > >
> > >
> >
>

Re: about ode-jbi and flows

Posted by Eduardo Burgos <eb...@gmail.com>.
yep, I found it, thanks, I also found in the code that its "sendSynch"
instead of "sendSync", is that correct?

On 7/30/07, Alex Boisvert <bo...@intalio.com> wrote:
>
> You add it to your JAVA_OPTS environment variable, or directly in
> servicemix.sh / servicemix.bat (see DEFAULT_JAVA_OPTS).   It is a
> command-line parameter for the "java" executable, e.g.,
>
> java -Dorg.apache.ode.jbi.sendSync=true [other arguments]
>
> alex
>
>
> On 7/30/07, Eduardo Burgos <eb...@gmail.com> wrote:
> >
> > where can I put this -Dorg.apache.ode.jbi.sendSync
> > >
> > > =true option?
> >
> >
> > On 7/29/07, Alex Boisvert <bo...@intalio.com> wrote:
> > >
> > > Hi Eduardo,
> > >
> > > I'm not sure what's happening so I'll need more information to help
> you.
> > > This error can happen if the flow is marked as persistent, clustered
> or
> > > transacted.  SedaFlow doesn't support these "qualities of service"
> > (QoS).
> > > You can check the code where the exchange is created, and perhaps try
> > with
> > > "-Dorg.apache.ode.jbi.sendSync=true" to see if you get better result
> (or
> > > better error reporting) that way.
> > >
> > > alex
> > >
> > > On 7/27/07, Eduardo Burgos <eb...@gmail.com> wrote:
> > > >
> > > > Hi,
> > > >
> > > > I just got this error right when my process finishes the execution,
> > when
> > > > its
> > > > trying to return the result to another endpoint.
> > > >
> > > >
> > > >
> > > > 18:18:55,472 | ERROR | pool-11-thread-1 | OdeService               |
> > > > org.apache.ode.jbi.OdeService   312 | Error bridging ODE out
> response:
> > > > javax.jbi.messaging.MessagingException: Flow 'Seda' was specified
> but
> > > not
> > > > able to handle exchange
> > > >     at
> > org.apache.servicemix.jbi.nmr.flow.DefaultFlowChooser.chooseFlow(
> > > > DefaultFlowChooser.java:46)
> > > >     at
> org.apache.servicemix.jbi.nmr.DefaultBroker.sendExchangePacket(
> > > > DefaultBroker.java:277)
> > > >     at
> > > org.apache.servicemix.jbi.security.SecuredBroker.sendExchangePacket
> > > > (
> > > > SecuredBroker.java:81)
> > > >     at org.apache.servicemix.jbi.container.JBIContainer.sendExchange
> (
> > > > JBIContainer.java:793)
> > > >     at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(
> > > > DeliveryChannelImpl.java:381)
> > > >     at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(
> > > > DeliveryChannelImpl.java:417)
> > > >     at org.apache.ode.jbi.OdeService.outResponse(OdeService.java
> :309)
> > > >     at org.apache.ode.jbi.OdeService.onResponse(OdeService.java:195)
> > > >     at org.apache.ode.jbi.MessageExchangeContextImpl.onAsyncReply(
> > > > MessageExchangeContextImpl.java:53)
> > > >     at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.reply(
> > > > BpelRuntimeContextImpl.java:582)
> > > >     at org.apache.ode.bpel.runtime.REPLY.run(REPLY.java:64)
> > > >     at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
> > > >     at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > > > DelegatingMethodAccessorImpl.java:25)
> > > >     at java.lang.reflect.Method.invoke(Method.java:585)
> > > >     at org.apache.ode.jacob.vpu.JacobVPU$JacobThreadImpl.run(
> > > JacobVPU.java
> > > > :451)
> > > >     at org.apache.ode.jacob.vpu.JacobVPU.execute(JacobVPU.java:139)
> > > >     at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.execute(
> > > > BpelRuntimeContextImpl.java:834)
> > > >     at org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(
> > > > BpelProcess.java:336)
> > > >     at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(
> > > > BpelEngineImpl.java:318)
> > > >     at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(
> > > > BpelServerImpl.java:364)
> > > >     at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(
> > > > SimpleScheduler.java:316)
> > > >     at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(
> > > > SimpleScheduler.java:315)
> > > >     at
> org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction
> > (
> > > > SimpleScheduler.java:154)
> > > >     at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(
> > > > SimpleScheduler.java:314)
> > > >     at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(
> > > > SimpleScheduler.java:311)
> > > >     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)
> > > >
> > > >
> > > >
> > > >
> > > > Is there a problem with Seda flows and ode? What could be happening
> > > there?
> > > > Please help me.
> > > >
> > >
> >
>

Re: about ode-jbi and flows

Posted by Alex Boisvert <bo...@intalio.com>.
You add it to your JAVA_OPTS environment variable, or directly in
servicemix.sh / servicemix.bat (see DEFAULT_JAVA_OPTS).   It is a
command-line parameter for the "java" executable, e.g.,

java -Dorg.apache.ode.jbi.sendSync=true [other arguments]

alex


On 7/30/07, Eduardo Burgos <eb...@gmail.com> wrote:
>
> where can I put this -Dorg.apache.ode.jbi.sendSync
> >
> > =true option?
>
>
> On 7/29/07, Alex Boisvert <bo...@intalio.com> wrote:
> >
> > Hi Eduardo,
> >
> > I'm not sure what's happening so I'll need more information to help you.
> > This error can happen if the flow is marked as persistent, clustered or
> > transacted.  SedaFlow doesn't support these "qualities of service"
> (QoS).
> > You can check the code where the exchange is created, and perhaps try
> with
> > "-Dorg.apache.ode.jbi.sendSync=true" to see if you get better result (or
> > better error reporting) that way.
> >
> > alex
> >
> > On 7/27/07, Eduardo Burgos <eb...@gmail.com> wrote:
> > >
> > > Hi,
> > >
> > > I just got this error right when my process finishes the execution,
> when
> > > its
> > > trying to return the result to another endpoint.
> > >
> > >
> > >
> > > 18:18:55,472 | ERROR | pool-11-thread-1 | OdeService               |
> > > org.apache.ode.jbi.OdeService   312 | Error bridging ODE out response:
> > > javax.jbi.messaging.MessagingException: Flow 'Seda' was specified but
> > not
> > > able to handle exchange
> > >     at
> org.apache.servicemix.jbi.nmr.flow.DefaultFlowChooser.chooseFlow(
> > > DefaultFlowChooser.java:46)
> > >     at org.apache.servicemix.jbi.nmr.DefaultBroker.sendExchangePacket(
> > > DefaultBroker.java:277)
> > >     at
> > org.apache.servicemix.jbi.security.SecuredBroker.sendExchangePacket
> > > (
> > > SecuredBroker.java:81)
> > >     at org.apache.servicemix.jbi.container.JBIContainer.sendExchange(
> > > JBIContainer.java:793)
> > >     at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(
> > > DeliveryChannelImpl.java:381)
> > >     at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(
> > > DeliveryChannelImpl.java:417)
> > >     at org.apache.ode.jbi.OdeService.outResponse(OdeService.java:309)
> > >     at org.apache.ode.jbi.OdeService.onResponse(OdeService.java:195)
> > >     at org.apache.ode.jbi.MessageExchangeContextImpl.onAsyncReply(
> > > MessageExchangeContextImpl.java:53)
> > >     at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.reply(
> > > BpelRuntimeContextImpl.java:582)
> > >     at org.apache.ode.bpel.runtime.REPLY.run(REPLY.java:64)
> > >     at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
> > >     at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > > DelegatingMethodAccessorImpl.java:25)
> > >     at java.lang.reflect.Method.invoke(Method.java:585)
> > >     at org.apache.ode.jacob.vpu.JacobVPU$JacobThreadImpl.run(
> > JacobVPU.java
> > > :451)
> > >     at org.apache.ode.jacob.vpu.JacobVPU.execute(JacobVPU.java:139)
> > >     at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.execute(
> > > BpelRuntimeContextImpl.java:834)
> > >     at org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(
> > > BpelProcess.java:336)
> > >     at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(
> > > BpelEngineImpl.java:318)
> > >     at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(
> > > BpelServerImpl.java:364)
> > >     at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(
> > > SimpleScheduler.java:316)
> > >     at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(
> > > SimpleScheduler.java:315)
> > >     at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction
> (
> > > SimpleScheduler.java:154)
> > >     at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(
> > > SimpleScheduler.java:314)
> > >     at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(
> > > SimpleScheduler.java:311)
> > >     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)
> > >
> > >
> > >
> > >
> > > Is there a problem with Seda flows and ode? What could be happening
> > there?
> > > Please help me.
> > >
> >
>

Re: about ode-jbi and flows

Posted by Eduardo Burgos <eb...@gmail.com>.
where can I put this -Dorg.apache.ode.jbi.sendSync
>
> =true option?







On 7/29/07, Alex Boisvert <bo...@intalio.com> wrote:
>
> Hi Eduardo,
>
> I'm not sure what's happening so I'll need more information to help you.
> This error can happen if the flow is marked as persistent, clustered or
> transacted.  SedaFlow doesn't support these "qualities of service" (QoS).
> You can check the code where the exchange is created, and perhaps try with
> "-Dorg.apache.ode.jbi.sendSync=true" to see if you get better result (or
> better error reporting) that way.
>
> alex
>
> On 7/27/07, Eduardo Burgos <eb...@gmail.com> wrote:
> >
> > Hi,
> >
> > I just got this error right when my process finishes the execution, when
> > its
> > trying to return the result to another endpoint.
> >
> >
> >
> > 18:18:55,472 | ERROR | pool-11-thread-1 | OdeService               |
> > org.apache.ode.jbi.OdeService   312 | Error bridging ODE out response:
> > javax.jbi.messaging.MessagingException: Flow 'Seda' was specified but
> not
> > able to handle exchange
> >     at org.apache.servicemix.jbi.nmr.flow.DefaultFlowChooser.chooseFlow(
> > DefaultFlowChooser.java:46)
> >     at org.apache.servicemix.jbi.nmr.DefaultBroker.sendExchangePacket(
> > DefaultBroker.java:277)
> >     at
> org.apache.servicemix.jbi.security.SecuredBroker.sendExchangePacket
> > (
> > SecuredBroker.java:81)
> >     at org.apache.servicemix.jbi.container.JBIContainer.sendExchange(
> > JBIContainer.java:793)
> >     at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(
> > DeliveryChannelImpl.java:381)
> >     at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(
> > DeliveryChannelImpl.java:417)
> >     at org.apache.ode.jbi.OdeService.outResponse(OdeService.java:309)
> >     at org.apache.ode.jbi.OdeService.onResponse(OdeService.java:195)
> >     at org.apache.ode.jbi.MessageExchangeContextImpl.onAsyncReply(
> > MessageExchangeContextImpl.java:53)
> >     at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.reply(
> > BpelRuntimeContextImpl.java:582)
> >     at org.apache.ode.bpel.runtime.REPLY.run(REPLY.java:64)
> >     at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
> >     at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > DelegatingMethodAccessorImpl.java:25)
> >     at java.lang.reflect.Method.invoke(Method.java:585)
> >     at org.apache.ode.jacob.vpu.JacobVPU$JacobThreadImpl.run(
> JacobVPU.java
> > :451)
> >     at org.apache.ode.jacob.vpu.JacobVPU.execute(JacobVPU.java:139)
> >     at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.execute(
> > BpelRuntimeContextImpl.java:834)
> >     at org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(
> > BpelProcess.java:336)
> >     at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(
> > BpelEngineImpl.java:318)
> >     at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(
> > BpelServerImpl.java:364)
> >     at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(
> > SimpleScheduler.java:316)
> >     at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(
> > SimpleScheduler.java:315)
> >     at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(
> > SimpleScheduler.java:154)
> >     at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(
> > SimpleScheduler.java:314)
> >     at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(
> > SimpleScheduler.java:311)
> >     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)
> >
> >
> >
> >
> > Is there a problem with Seda flows and ode? What could be happening
> there?
> > Please help me.
> >
>

Re: about ode-jbi and flows

Posted by Alex Boisvert <bo...@intalio.com>.
Hi Eduardo,

I'm not sure what's happening so I'll need more information to help you.
This error can happen if the flow is marked as persistent, clustered or
transacted.  SedaFlow doesn't support these "qualities of service" (QoS).
You can check the code where the exchange is created, and perhaps try with
"-Dorg.apache.ode.jbi.sendSync=true" to see if you get better result (or
better error reporting) that way.

alex

On 7/27/07, Eduardo Burgos <eb...@gmail.com> wrote:
>
> Hi,
>
> I just got this error right when my process finishes the execution, when
> its
> trying to return the result to another endpoint.
>
>
>
> 18:18:55,472 | ERROR | pool-11-thread-1 | OdeService               |
> org.apache.ode.jbi.OdeService   312 | Error bridging ODE out response:
> javax.jbi.messaging.MessagingException: Flow 'Seda' was specified but not
> able to handle exchange
>     at org.apache.servicemix.jbi.nmr.flow.DefaultFlowChooser.chooseFlow(
> DefaultFlowChooser.java:46)
>     at org.apache.servicemix.jbi.nmr.DefaultBroker.sendExchangePacket(
> DefaultBroker.java:277)
>     at org.apache.servicemix.jbi.security.SecuredBroker.sendExchangePacket
> (
> SecuredBroker.java:81)
>     at org.apache.servicemix.jbi.container.JBIContainer.sendExchange(
> JBIContainer.java:793)
>     at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(
> DeliveryChannelImpl.java:381)
>     at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(
> DeliveryChannelImpl.java:417)
>     at org.apache.ode.jbi.OdeService.outResponse(OdeService.java:309)
>     at org.apache.ode.jbi.OdeService.onResponse(OdeService.java:195)
>     at org.apache.ode.jbi.MessageExchangeContextImpl.onAsyncReply(
> MessageExchangeContextImpl.java:53)
>     at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.reply(
> BpelRuntimeContextImpl.java:582)
>     at org.apache.ode.bpel.runtime.REPLY.run(REPLY.java:64)
>     at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
>     at java.lang.reflect.Method.invoke(Method.java:585)
>     at org.apache.ode.jacob.vpu.JacobVPU$JacobThreadImpl.run(JacobVPU.java
> :451)
>     at org.apache.ode.jacob.vpu.JacobVPU.execute(JacobVPU.java:139)
>     at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.execute(
> BpelRuntimeContextImpl.java:834)
>     at org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(
> BpelProcess.java:336)
>     at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(
> BpelEngineImpl.java:318)
>     at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(
> BpelServerImpl.java:364)
>     at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(
> SimpleScheduler.java:316)
>     at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(
> SimpleScheduler.java:315)
>     at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(
> SimpleScheduler.java:154)
>     at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(
> SimpleScheduler.java:314)
>     at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(
> SimpleScheduler.java:311)
>     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)
>
>
>
>
> Is there a problem with Seda flows and ode? What could be happening there?
> Please help me.
>