You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by pedroaraujo <ze...@gmail.com> on 2009/07/23 12:43:21 UTC
ServiceMix + ODE problems
Hi all!
I'm new to ServiceMix and ODE. I got a little problem... i will try to
explain. (I know this isn't Apache ODE forum but i think the problem is
somewhere between these two)
My scenario is something like this:
Client <-> CXF-BC <-> Apache ODE <-> CXF-SE
I've got a BPEL process exposed with CXF-BC that just invokes an external
webservice exposed inside servicemix with CXF-SE. All works perfectly until
when Apache ODE needs to reply the output to the client... it fails and
gives some strange errors...
what i'm doing wrong? can you guys help me?
Thanks!
My environment:
Servicemix: 3.3.1
Apache ODE: 2.0 (tried with 1.2 and 1.3.2 too)
I'm using JbiWsdl11WrapperMapper.
All messages:
DEBUG - CxfBcComponent - Created correlation id:
ID:127.0.0.1-122a6adaf30-10:0
DEBUG - DeliveryChannelImpl - SendSync
ID:127.0.0.1-122a6adaf30-10:0 in DeliveryChannel{servicemix-cxf-bc}
DEBUG - SecuredBroker - send exchange with secure broker
DEBUG - SecuredBroker - service name
:{http://teste/CP/}mainService
DEBUG - SecuredBroker - operation name
:{http://teste/CP/}process
DEBUG - SedaFlow - Called Flow send
DEBUG - DeliveryChannelImpl - Waiting for exchange
ID:127.0.0.1-122a6adaf30-10:0 (9e31f0) to be answered in
DeliveryChannel{servicemix-cxf-bc} from sendSync
DEBUG - SedaQueue -
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@95306c dequeued
exchange: InOut[
id: ID:127.0.0.1-122a6adaf30-10:0
status: Active
role: provider
interface: {http://teste/CP/}mainService
service: {http://teste/CP/}mainService
endpoint: mainPort
operation: {http://teste/CP/}process
in: <?xml version="1.0" encoding="UTF-8"?>1000
]
DEBUG - DeliveryChannelImpl - Accepting
ID:127.0.0.1-122a6adaf30-10:0 in DeliveryChannel{OdeBpelEngine}
INFO - Query - This query on type "class
org.apache.ode.dao.jpa.MessageExchangeDAOImpl" must load the entire
candidate class extent and evaluate the query in-memory. This may be very
slow. The query must be executed in memory because OpenJPA is configured
with IgnoreCache=false and FlushBeforeQueries=false and there are dirty
instances that may affect the query's outcome in the cache.
DEBUG - DeliveryChannelImpl - Send ID:127.0.0.1-122a6adaf30-20:0
in DeliveryChannel{OdeBpelEngine}
DEBUG - SecuredBroker - send exchange with secure broker
DEBUG - SecuredBroker - service name
:{http://teste/CP/}TesteServiceImplService
DEBUG - SecuredBroker - operation name
:{http://teste/CP/}number
DEBUG - SedaFlow - Called Flow send
DEBUG - SedaQueue -
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@1ee3a29 dequeued
exchange: InOut[
id: ID:127.0.0.1-122a6adaf30-20:0
status: Active
role: provider
service: {http://teste/CP/}TesteServiceImplService
endpoint: TesteServiceImplPort
operation: {http://teste/CP/}number
in: <?xml version="1.0" encoding="UTF-8" standalone="no"?>
1000
]
DEBUG - CxfSeComponent - Received exchange: status: Active,
role: provider
DEBUG - CxfSeComponent - Retrieved correlation id: null
Jul 23, 2009 10:46:28 AM org.apache.cxf.transport.jbi.JBITransportFactory
setDeliveryChannel
INFO: configuring DeliveryChannel:
org.apache.servicemix.common.EndpointDeliveryChannel@188fa1d
********* TesteServiceImpl: number(): 1000 ******************* CXF-SE
INVOKED
DEBUG - DeliveryChannelImpl - Send ID:127.0.0.1-122a6adaf30-20:0
in DeliveryChannel{servicemix-cxf-se}
DEBUG - SecuredBroker - send exchange with secure broker
DEBUG - SedaFlow - Called Flow send
DEBUG - SedaQueue -
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@15476cc dequeued
exchange: InOut[
id: ID:127.0.0.1-122a6adaf30-20:0
status: Active
role: consumer
interface: {http://teste/CP/}TesteServiceImpl
service: {http://teste/CP/}TesteServiceImplService
endpoint: TesteServiceImplPort
operation: {http://teste/CP/}number
in: <?xml version="1.0" encoding="UTF-8"?>
1000
out: <?xml version="1.0" encoding="UTF-8"?>1000
]
DEBUG - DeliveryChannelImpl - Accepting
ID:127.0.0.1-122a6adaf30-20:0 in DeliveryChannel{OdeBpelEngine}
WARN - OdeConsumer - Received a response for unknown
partner role message exchange ID:127.0.0.1-122a6adaf30-20:0
DEBUG - DeliveryChannelImpl - Send ID:127.0.0.1-122a6adaf30-20:0
in DeliveryChannel{OdeBpelEngine}
DEBUG - SecuredBroker - send exchange with secure broker
DEBUG - SedaFlow - Called Flow send
DEBUG - SedaQueue -
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@1fd9d8e dequeued
exchange: InOut[
id: ID:127.0.0.1-122a6adaf30-20:0
status: Done
role: provider
interface: {http://teste/CP/}TesteServiceImpl
service: {http://teste/CP/}TesteServiceImplService
endpoint: TesteServiceImplPort
operation: {http://teste/CP/}number
in: <?xml version="1.0" encoding="UTF-8" standalone="no"?>
1000
out: <?xml version="1.0" encoding="UTF-8" standalone="no"?>1000
]
DEBUG - CxfSeComponent - Received exchange: status: Done,
role: provider
DEBUG - CxfSeComponent - Retrieved correlation id: null
Jul 23, 2009 10:46:28 AM org.apache.cxf.transport.jbi.JBITransportFactory
setDeliveryChannel
INFO: configuring DeliveryChannel:
org.apache.servicemix.common.EndpointDeliveryChannel@188fa1d
WARN - DiscoveryNetworkConnector - Could not start network bridge
between: vm://localhost and: tcp://brgx0001:61616 due to:
java.net.NoRouteToHostException: No route to host
WARN - DiscoveryNetworkConnector - Could not start network bridge
between: vm://localhost and: tcp://brgx0001:61616 due to:
java.net.NoRouteToHostException: No route to host
WARN - DiscoveryNetworkConnector - Could not start network bridge
between: vm://localhost and: tcp://brgx0001:61616 due to:
java.net.NoRouteToHostException: No route to host
WARN - DiscoveryNetworkConnector - Could not start network bridge
between: vm://localhost and: tcp://brgx0001:61616 due to:
java.net.NoRouteToHostException: No route to host
ERROR - OdeService - ODE MEX
{MyRoleMex#hqejbhcnphr4ge5foktvuu [Client null] calling
{http://teste/CP/}mainService.process(...)} resulted in an error.
DEBUG - DeliveryChannelImpl - Send ID:127.0.0.1-122a6adaf30-10:0
in DeliveryChannel{OdeBpelEngine}
DEBUG - SecuredBroker - send exchange with secure broker
DEBUG - SedaFlow - Called Flow send
DEBUG - SedaQueue -
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@a0f9cb dequeued
exchange: InOut[
id: ID:127.0.0.1-122a6adaf30-10:0
status: Error
role: consumer
interface: {http://teste/CP/}mainService
service: {http://teste/CP/}mainService
endpoint: mainPort
operation: {http://teste/CP/}process
in: <?xml version="1.0" encoding="UTF-8" standalone="no"?>1000
error: java.util.concurrent.TimeoutException
]
DEBUG - DeliveryChannelImpl - Notifying exchange
ID:127.0.0.1-122a6adaf30-10:0(9e31f0) in DeliveryChannel{servicemix-cxf-bc}
from processInboundSynchronousExchange
DEBUG - DeliveryChannelImpl - Notified:
ID:127.0.0.1-122a6adaf30-10:0(9e31f0) in DeliveryChannel{servicemix-cxf-bc}
from sendSync
Jul 23, 2009 10:46:57 AM org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
INFO: Interceptor has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault
at
org.apache.servicemix.cxfbc.CxfBcConsumer$JbiPostInvokerInterceptor.handleMessage(CxfBcConsumer.java:647)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:78)
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:278)
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:252)
at
org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:70)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:722)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206)
at org.mortbay.jetty.handler.HandlerList.handle(HandlerList.java:49)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:324)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
at
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:842)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:648)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)
Caused by: java.util.concurrent.TimeoutException
at
org.apache.ode.bpel.engine.UnreliableMyRoleMessageExchangeImpl$ResponseFuture.get(UnreliableMyRoleMessageExchangeImpl.java:99)
at
org.apache.ode.bpel.engine.UnreliableMyRoleMessageExchangeImpl$ResponseFuture.get(UnreliableMyRoleMessageExchangeImpl.java:76)
at
org.apache.ode.bpel.engine.UnreliableMyRoleMessageExchangeImpl.invokeBlocking(UnreliableMyRoleMessageExchangeImpl.java:66)
at org.apache.ode.jbi.OdeService.invokeOde(OdeService.java:205)
at
org.apache.ode.jbi.OdeService.onJbiMessageExchange(OdeService.java:142)
at
org.apache.ode.jbi.JbiMessageExchangeEventRouter.onJbiMessageExchange(JbiMessageExchangeEventRouter.java:67)
at org.apache.ode.jbi.Receiver$1.run(Receiver.java:179)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
--
View this message in context: http://www.nabble.com/ServiceMix-%2B-ODE-problems-tp24623303p24623303.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: ServiceMix + ODE problems
Posted by Pedro Araújo <ze...@gmail.com>.
Hi,
i think my problem is related with this warning:
WARN - OdeConsumer - Received a response for unknown
partner role message exchange ID:127.0.0.1-122a6adaf30-20:0
i've found this issue recently... it's almost the same problem i have.
#ODE-579
https://issues.apache.org/jira/browse/ODE-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
In Apache ODE 1.2 i got this message in my xfire client:
Jul 27, 2009 12:14:17 PM org.codehaus.xfire.jaxb2.JaxbType readObject
SEVERE: javax.xml.bind.UnmarshalException: unexpected element (uri:"",
local:"mainResponse"). Expected elements are
<{http://teste/CP/}mainRequest>,<{http://teste/CP/}mainResponse>,<{http://teste/CP/}number>,<{http://teste/CP/}numberResponse>,<{http://teste/CP/}printGreaterThan>,<{http://teste/CP/}printGreaterThanResponse>,<{http://teste/CP/}printLessThan>,<{http://teste/CP/}printLessThanResponse>
Exception in thread "main" org.codehaus.xfire.XFireRuntimeException: Could
not invoke service.. Nested exception is
org.codehaus.xfire.fault.XFireFault: Could not unmarshall type : unexpected
element (uri:"", local:"mainResponse"). Expected elements are
<{http://teste/CP/}mainRequest>,<{http://teste/CP/}mainResponse>,<{http://teste/CP/}number>,<{http://teste/CP/}numberResponse>,<{http://teste/CP/}printGreaterThan>,<{http://teste/CP/}printGreaterThanResponse>,<{http://teste/CP/}printLessThan>,<{http://teste/CP/}printLessThanResponse>
org.codehaus.xfire.fault.XFireFault: Could not unmarshall type : unexpected
element (uri:"", local:"mainResponse"). Expected elements are
<{http://teste/CP/}mainRequest>,<{http://teste/CP/}mainResponse>,<{http://teste/CP/}number>,<{http://teste/CP/}numberResponse>,<{http://teste/CP/}printGreaterThan>,<{http://teste/CP/}printGreaterThanResponse>,<{http://teste/CP/}printLessThan>,<{http://teste/CP/}printLessThanResponse>
at org.codehaus.xfire.jaxb2.JaxbType.readObject(JaxbType.java:216)
at
org.codehaus.xfire.aegis.AegisBindingProvider.readParameter(AegisBindingProvider.java:162)
at
org.codehaus.xfire.service.binding.AbstractBinding.read(AbstractBinding.java:206)
at
org.codehaus.xfire.service.binding.DocumentBinding.readMessage(DocumentBinding.java:32)
at
org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42)
at
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at org.codehaus.xfire.client.Client.onReceive(Client.java:387)
at
org.codehaus.xfire.transport.http.HttpChannel.sendViaClient(HttpChannel.java:139)
at
org.codehaus.xfire.transport.http.HttpChannel.send(HttpChannel.java:48)
at
org.codehaus.xfire.handler.OutMessageSender.invoke(OutMessageSender.java:26)
at
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:75)
at org.codehaus.xfire.client.Client.invoke(Client.java:335)
at
org.codehaus.xfire.client.XFireProxy.handleRequest(XFireProxy.java:77)
at org.codehaus.xfire.client.XFireProxy.invoke(XFireProxy.java:57)
at $Proxy13.process(Unknown Source)
at Main.main(Main.java:22)
Caused by: javax.xml.bind.UnmarshalException: unexpected element (uri:"",
local:"mainResponse"). Expected elements are
<{http://teste/CP/}mainRequest>,<{http://teste/CP/}mainResponse>,<{http://teste/CP/}number>,<{http://teste/CP/}numberResponse>,<{http://teste/CP/}printGreaterThan>,<{http://teste/CP/}printGreaterThanResponse>,<{http://teste/CP/}printLessThan>,<{http://teste/CP/}printLessThanResponse>
at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.handleEvent(UnmarshallingContext.java:525)
at
com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:199)
at
com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:194)
at
com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportUnexpectedChildElement(Loader.java:71)
at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext$DefaultRootLoader.childElement(UnmarshallingContext.java:922)
at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext._startElement(UnmarshallingContext.java:366)
at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.startElement(UnmarshallingContext.java:347)
at
com.sun.xml.bind.v2.runtime.unmarshaller.InterningXmlVisitor.startElement(InterningXmlVisitor.java:35)
at
com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.handleStartElement(StAXStreamConnector.java:201)
at
com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(StAXStreamConnector.java:135)
at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:337)
at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:309)
at org.codehaus.xfire.jaxb2.JaxbType.readObject(JaxbType.java:200)
... 16 more
Caused by: javax.xml.bind.UnmarshalException: unexpected element (uri:"",
local:"mainResponse"). Expected elements are
<{http://teste/CP/}mainRequest>,<{http://teste/CP/}mainResponse>,<{http://teste/CP/}number>,<{http://teste/CP/}numberResponse>,<{http://teste/CP/}printGreaterThan>,<{http://teste/CP/}printGreaterThanResponse>,<{http://teste/CP/}printLessThan>,<{http://teste/CP/}printLessThanResponse>
... 29 more
Pedro Araújo wrote:
>
> Hi Vincent,
>
> another servicemix was running in another pc on my network... the problem
> is not from that warning because i've tested with only my pc running and i
> get the same error...
>
> Could someone try to reproduce the error or look at the source and see if
> it is something missing? In the attachment i have the two SAs (zips)
> already.
>
> Regards,
> Pedro
>
> http://www.nabble.com/file/p24642990/project.zip project.zip
>
> TheWinch wrote:
>>
>> Hi Pedro,
>>
>> Have you an idea of the cause of these errors:
>>
>> WARN - DiscoveryNetworkConnector - Could not start network bridge
>> between: vm://localhost and: tcp://brgx0001:61616 due to:
>> java.net.NoRouteToHostException: No route to host
>>
>> Try resolving this error first (check your routing tables and your
>> /etc/hosts or C:\Windows\system32\driverse\etc\hosts) and tell us if you
>> see an improvement. My feeling is that your host does not know brgx0001.
>>
>> Vincent
>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/ServiceMix-%2B-ODE-problems-tp24623307p24679194.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: ServiceMix + ODE problems
Posted by Pedro Araújo <ze...@gmail.com>.
Hi Vincent,
another servicemix was running in another pc on my network... the problem is
not from that warning because i've tested with only my pc running and i get
the same error...
Could someone try to reproduce the error or look at the source and see if it
is something missing? In the attachment i have the two SAs (zips) already.
Regards,
Pedro
http://www.nabble.com/file/p24642990/project.zip project.zip
TheWinch wrote:
>
> Hi Pedro,
>
> Have you an idea of the cause of these errors:
>
> WARN - DiscoveryNetworkConnector - Could not start network bridge
> between: vm://localhost and: tcp://brgx0001:61616 due to:
> java.net.NoRouteToHostException: No route to host
>
> Try resolving this error first (check your routing tables and your
> /etc/hosts or C:\Windows\system32\driverse\etc\hosts) and tell us if you
> see an improvement. My feeling is that your host does not know brgx0001.
>
> Vincent
>
>
>
--
View this message in context: http://www.nabble.com/ServiceMix-%2B-ODE-problems-tp24623307p24642990.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: ServiceMix + ODE problems
Posted by Vincent GIRARDREYDET <vi...@thalesgroup.com>.
Hi Pedro,
Have you an idea of the cause of these errors:
WARN - DiscoveryNetworkConnector - Could not start network bridge
between: vm://localhost and: tcp://brgx0001:61616 due to:
java.net.NoRouteToHostException: No route to host
Try resolving this error first (check your routing tables and your /etc/hosts or C:\Windows\system32\driverse\etc\hosts) and tell us if you see an improvement. My feeling is that your host does not know brgx0001.
Vincent
Re: ServiceMix + ODE problems
Posted by pedroaraujo <ze...@gmail.com>.
Hi Jean,
Thank you for trying to help me!
I've done what you said, but i only see lots of SQL statements, i don't see
any kind of error... :\
Any clue?
Regards,
Pedro Araújo
Jean-Baptiste Onofré wrote:
>
> Hi Pedrp,
>
> could you try the ODE log level to DEBUG and check if there is any error ?
> I think that the incoming message is not the expected one.
>
> If you use SMX3, it's in the conf/log4j.xml file. Add a
> category/appender for org.apache.ode package.
>
> Regards
> JB
>
> pedroaraujo wrote:
>> Hi all!
>>
>> I'm new to ServiceMix and ODE. I got a little problem... i will try to
>> explain. (I know this isn't Apache ODE forum but i think the problem is
>> somewhere between these two)
>>
>> My scenario is something like this:
>> Client <-> CXF-BC <-> Apache ODE <-> CXF-SE
>>
>> I've got a BPEL process exposed with CXF-BC that just invokes an external
>> webservice exposed inside servicemix with CXF-SE. All works perfectly
>> until
>> when Apache ODE needs to reply the output to the client... it fails and
>> gives some strange errors...
>>
>> what i'm doing wrong? can you guys help me?
>> Thanks!
>>
>> My environment:
>> Servicemix: 3.3.1
>> Apache ODE: 2.0 (tried with 1.2 and 1.3.2 too)
>> I'm using JbiWsdl11WrapperMapper.
>>
>> All messages:
>>
>> DEBUG - CxfBcComponent - Created correlation id:
>> ID:127.0.0.1-122a6adaf30-10:0
>> DEBUG - DeliveryChannelImpl - SendSync
>> ID:127.0.0.1-122a6adaf30-10:0 in DeliveryChannel{servicemix-cxf-bc}
>> DEBUG - SecuredBroker - send exchange with secure broker
>> DEBUG - SecuredBroker - service name
>> :{http://teste/CP/}mainService
>> DEBUG - SecuredBroker - operation name
>> :{http://teste/CP/}process
>> DEBUG - SedaFlow - Called Flow send
>> DEBUG - DeliveryChannelImpl - Waiting for exchange
>> ID:127.0.0.1-122a6adaf30-10:0 (9e31f0) to be answered in
>> DeliveryChannel{servicemix-cxf-bc} from sendSync
>> DEBUG - SedaQueue -
>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@95306c dequeued
>> exchange: InOut[
>> id: ID:127.0.0.1-122a6adaf30-10:0
>> status: Active
>> role: provider
>> interface: {http://teste/CP/}mainService
>> service: {http://teste/CP/}mainService
>> endpoint: mainPort
>> operation: {http://teste/CP/}process
>> in: <?xml version="1.0" encoding="UTF-8"?>1000
>> ]
>> DEBUG - DeliveryChannelImpl - Accepting
>> ID:127.0.0.1-122a6adaf30-10:0 in DeliveryChannel{OdeBpelEngine}
>> INFO - Query - This query on type "class
>> org.apache.ode.dao.jpa.MessageExchangeDAOImpl" must load the entire
>> candidate class extent and evaluate the query in-memory. This may be
>> very
>> slow. The query must be executed in memory because OpenJPA is configured
>> with IgnoreCache=false and FlushBeforeQueries=false and there are dirty
>> instances that may affect the query's outcome in the cache.
>> DEBUG - DeliveryChannelImpl - Send
>> ID:127.0.0.1-122a6adaf30-20:0
>> in DeliveryChannel{OdeBpelEngine}
>> DEBUG - SecuredBroker - send exchange with secure broker
>> DEBUG - SecuredBroker - service name
>> :{http://teste/CP/}TesteServiceImplService
>> DEBUG - SecuredBroker - operation name
>> :{http://teste/CP/}number
>> DEBUG - SedaFlow - Called Flow send
>> DEBUG - SedaQueue -
>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@1ee3a29 dequeued
>> exchange: InOut[
>> id: ID:127.0.0.1-122a6adaf30-20:0
>> status: Active
>> role: provider
>> service: {http://teste/CP/}TesteServiceImplService
>> endpoint: TesteServiceImplPort
>> operation: {http://teste/CP/}number
>> in: <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>> 1000
>>
>> ]
>> DEBUG - CxfSeComponent - Received exchange: status:
>> Active,
>> role: provider
>> DEBUG - CxfSeComponent - Retrieved correlation id: null
>> Jul 23, 2009 10:46:28 AM org.apache.cxf.transport.jbi.JBITransportFactory
>> setDeliveryChannel
>> INFO: configuring DeliveryChannel:
>> org.apache.servicemix.common.EndpointDeliveryChannel@188fa1d
>> ********* TesteServiceImpl: number(): 1000 ******************* CXF-SE
>> INVOKED
>> DEBUG - DeliveryChannelImpl - Send
>> ID:127.0.0.1-122a6adaf30-20:0
>> in DeliveryChannel{servicemix-cxf-se}
>> DEBUG - SecuredBroker - send exchange with secure broker
>> DEBUG - SedaFlow - Called Flow send
>> DEBUG - SedaQueue -
>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@15476cc dequeued
>> exchange: InOut[
>> id: ID:127.0.0.1-122a6adaf30-20:0
>> status: Active
>> role: consumer
>> interface: {http://teste/CP/}TesteServiceImpl
>> service: {http://teste/CP/}TesteServiceImplService
>> endpoint: TesteServiceImplPort
>> operation: {http://teste/CP/}number
>> in: <?xml version="1.0" encoding="UTF-8"?>
>> 1000
>>
>> out: <?xml version="1.0" encoding="UTF-8"?>1000
>> ]
>> DEBUG - DeliveryChannelImpl - Accepting
>> ID:127.0.0.1-122a6adaf30-20:0 in DeliveryChannel{OdeBpelEngine}
>> WARN - OdeConsumer - Received a response for unknown
>> partner role message exchange ID:127.0.0.1-122a6adaf30-20:0
>> DEBUG - DeliveryChannelImpl - Send
>> ID:127.0.0.1-122a6adaf30-20:0
>> in DeliveryChannel{OdeBpelEngine}
>> DEBUG - SecuredBroker - send exchange with secure broker
>> DEBUG - SedaFlow - Called Flow send
>> DEBUG - SedaQueue -
>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@1fd9d8e dequeued
>> exchange: InOut[
>> id: ID:127.0.0.1-122a6adaf30-20:0
>> status: Done
>> role: provider
>> interface: {http://teste/CP/}TesteServiceImpl
>> service: {http://teste/CP/}TesteServiceImplService
>> endpoint: TesteServiceImplPort
>> operation: {http://teste/CP/}number
>> in: <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>> 1000
>>
>> out: <?xml version="1.0" encoding="UTF-8" standalone="no"?>1000
>> ]
>> DEBUG - CxfSeComponent - Received exchange: status: Done,
>> role: provider
>> DEBUG - CxfSeComponent - Retrieved correlation id: null
>> Jul 23, 2009 10:46:28 AM org.apache.cxf.transport.jbi.JBITransportFactory
>> setDeliveryChannel
>> INFO: configuring DeliveryChannel:
>> org.apache.servicemix.common.EndpointDeliveryChannel@188fa1d
>> WARN - DiscoveryNetworkConnector - Could not start network bridge
>> between: vm://localhost and: tcp://brgx0001:61616 due to:
>> java.net.NoRouteToHostException: No route to host
>> WARN - DiscoveryNetworkConnector - Could not start network bridge
>> between: vm://localhost and: tcp://brgx0001:61616 due to:
>> java.net.NoRouteToHostException: No route to host
>> WARN - DiscoveryNetworkConnector - Could not start network bridge
>> between: vm://localhost and: tcp://brgx0001:61616 due to:
>> java.net.NoRouteToHostException: No route to host
>> WARN - DiscoveryNetworkConnector - Could not start network bridge
>> between: vm://localhost and: tcp://brgx0001:61616 due to:
>> java.net.NoRouteToHostException: No route to host
>> ERROR - OdeService - ODE MEX
>> {MyRoleMex#hqejbhcnphr4ge5foktvuu [Client null] calling
>> {http://teste/CP/}mainService.process(...)} resulted in an error.
>> DEBUG - DeliveryChannelImpl - Send
>> ID:127.0.0.1-122a6adaf30-10:0
>> in DeliveryChannel{OdeBpelEngine}
>> DEBUG - SecuredBroker - send exchange with secure broker
>> DEBUG - SedaFlow - Called Flow send
>> DEBUG - SedaQueue -
>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@a0f9cb dequeued
>> exchange: InOut[
>> id: ID:127.0.0.1-122a6adaf30-10:0
>> status: Error
>> role: consumer
>> interface: {http://teste/CP/}mainService
>> service: {http://teste/CP/}mainService
>> endpoint: mainPort
>> operation: {http://teste/CP/}process
>> in: <?xml version="1.0" encoding="UTF-8" standalone="no"?>1000
>> error: java.util.concurrent.TimeoutException
>> ]
>> DEBUG - DeliveryChannelImpl - Notifying exchange
>> ID:127.0.0.1-122a6adaf30-10:0(9e31f0) in
>> DeliveryChannel{servicemix-cxf-bc}
>> from processInboundSynchronousExchange
>> DEBUG - DeliveryChannelImpl - Notified:
>> ID:127.0.0.1-122a6adaf30-10:0(9e31f0) in
>> DeliveryChannel{servicemix-cxf-bc}
>> from sendSync
>> Jul 23, 2009 10:46:57 AM org.apache.cxf.phase.PhaseInterceptorChain
>> doIntercept
>> INFO: Interceptor has thrown exception, unwinding now
>> org.apache.cxf.interceptor.Fault
>> at
>> org.apache.servicemix.cxfbc.CxfBcConsumer$JbiPostInvokerInterceptor.handleMessage(CxfBcConsumer.java:647)
>> at
>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220)
>> at
>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:78)
>> at
>> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:278)
>> at
>> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:252)
>> at
>> org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:70)
>> at
>> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:722)
>> at
>> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206)
>> at
>> org.mortbay.jetty.handler.HandlerList.handle(HandlerList.java:49)
>> at
>> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
>> at org.mortbay.jetty.Server.handle(Server.java:324)
>> at
>> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
>> at
>> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:842)
>> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:648)
>> at
>> org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205)
>> at
>> org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
>> at
>> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
>> at
>> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)
>> Caused by: java.util.concurrent.TimeoutException
>> at
>> org.apache.ode.bpel.engine.UnreliableMyRoleMessageExchangeImpl$ResponseFuture.get(UnreliableMyRoleMessageExchangeImpl.java:99)
>> at
>> org.apache.ode.bpel.engine.UnreliableMyRoleMessageExchangeImpl$ResponseFuture.get(UnreliableMyRoleMessageExchangeImpl.java:76)
>> at
>> org.apache.ode.bpel.engine.UnreliableMyRoleMessageExchangeImpl.invokeBlocking(UnreliableMyRoleMessageExchangeImpl.java:66)
>> at org.apache.ode.jbi.OdeService.invokeOde(OdeService.java:205)
>> at
>> org.apache.ode.jbi.OdeService.onJbiMessageExchange(OdeService.java:142)
>> at
>> org.apache.ode.jbi.JbiMessageExchangeEventRouter.onJbiMessageExchange(JbiMessageExchangeEventRouter.java:67)
>> at org.apache.ode.jbi.Receiver$1.run(Receiver.java:179)
>> at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>> at
>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.java:619)
>
>
--
View this message in context: http://www.nabble.com/ServiceMix-%2B-ODE-problems-tp24623307p24626273.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: ServiceMix + ODE problems
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Pedrp,
could you try the ODE log level to DEBUG and check if there is any error ?
I think that the incoming message is not the expected one.
If you use SMX3, it's in the conf/log4j.xml file. Add a
category/appender for org.apache.ode package.
Regards
JB
pedroaraujo wrote:
> Hi all!
>
> I'm new to ServiceMix and ODE. I got a little problem... i will try to
> explain. (I know this isn't Apache ODE forum but i think the problem is
> somewhere between these two)
>
> My scenario is something like this:
> Client <-> CXF-BC <-> Apache ODE <-> CXF-SE
>
> I've got a BPEL process exposed with CXF-BC that just invokes an external
> webservice exposed inside servicemix with CXF-SE. All works perfectly until
> when Apache ODE needs to reply the output to the client... it fails and
> gives some strange errors...
>
> what i'm doing wrong? can you guys help me?
> Thanks!
>
> My environment:
> Servicemix: 3.3.1
> Apache ODE: 2.0 (tried with 1.2 and 1.3.2 too)
> I'm using JbiWsdl11WrapperMapper.
>
> All messages:
>
> DEBUG - CxfBcComponent - Created correlation id:
> ID:127.0.0.1-122a6adaf30-10:0
> DEBUG - DeliveryChannelImpl - SendSync
> ID:127.0.0.1-122a6adaf30-10:0 in DeliveryChannel{servicemix-cxf-bc}
> DEBUG - SecuredBroker - send exchange with secure broker
> DEBUG - SecuredBroker - service name
> :{http://teste/CP/}mainService
> DEBUG - SecuredBroker - operation name
> :{http://teste/CP/}process
> DEBUG - SedaFlow - Called Flow send
> DEBUG - DeliveryChannelImpl - Waiting for exchange
> ID:127.0.0.1-122a6adaf30-10:0 (9e31f0) to be answered in
> DeliveryChannel{servicemix-cxf-bc} from sendSync
> DEBUG - SedaQueue -
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@95306c dequeued
> exchange: InOut[
> id: ID:127.0.0.1-122a6adaf30-10:0
> status: Active
> role: provider
> interface: {http://teste/CP/}mainService
> service: {http://teste/CP/}mainService
> endpoint: mainPort
> operation: {http://teste/CP/}process
> in: <?xml version="1.0" encoding="UTF-8"?>1000
> ]
> DEBUG - DeliveryChannelImpl - Accepting
> ID:127.0.0.1-122a6adaf30-10:0 in DeliveryChannel{OdeBpelEngine}
> INFO - Query - This query on type "class
> org.apache.ode.dao.jpa.MessageExchangeDAOImpl" must load the entire
> candidate class extent and evaluate the query in-memory. This may be very
> slow. The query must be executed in memory because OpenJPA is configured
> with IgnoreCache=false and FlushBeforeQueries=false and there are dirty
> instances that may affect the query's outcome in the cache.
> DEBUG - DeliveryChannelImpl - Send ID:127.0.0.1-122a6adaf30-20:0
> in DeliveryChannel{OdeBpelEngine}
> DEBUG - SecuredBroker - send exchange with secure broker
> DEBUG - SecuredBroker - service name
> :{http://teste/CP/}TesteServiceImplService
> DEBUG - SecuredBroker - operation name
> :{http://teste/CP/}number
> DEBUG - SedaFlow - Called Flow send
> DEBUG - SedaQueue -
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@1ee3a29 dequeued
> exchange: InOut[
> id: ID:127.0.0.1-122a6adaf30-20:0
> status: Active
> role: provider
> service: {http://teste/CP/}TesteServiceImplService
> endpoint: TesteServiceImplPort
> operation: {http://teste/CP/}number
> in: <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> 1000
>
> ]
> DEBUG - CxfSeComponent - Received exchange: status: Active,
> role: provider
> DEBUG - CxfSeComponent - Retrieved correlation id: null
> Jul 23, 2009 10:46:28 AM org.apache.cxf.transport.jbi.JBITransportFactory
> setDeliveryChannel
> INFO: configuring DeliveryChannel:
> org.apache.servicemix.common.EndpointDeliveryChannel@188fa1d
> ********* TesteServiceImpl: number(): 1000 ******************* CXF-SE
> INVOKED
> DEBUG - DeliveryChannelImpl - Send ID:127.0.0.1-122a6adaf30-20:0
> in DeliveryChannel{servicemix-cxf-se}
> DEBUG - SecuredBroker - send exchange with secure broker
> DEBUG - SedaFlow - Called Flow send
> DEBUG - SedaQueue -
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@15476cc dequeued
> exchange: InOut[
> id: ID:127.0.0.1-122a6adaf30-20:0
> status: Active
> role: consumer
> interface: {http://teste/CP/}TesteServiceImpl
> service: {http://teste/CP/}TesteServiceImplService
> endpoint: TesteServiceImplPort
> operation: {http://teste/CP/}number
> in: <?xml version="1.0" encoding="UTF-8"?>
> 1000
>
> out: <?xml version="1.0" encoding="UTF-8"?>1000
> ]
> DEBUG - DeliveryChannelImpl - Accepting
> ID:127.0.0.1-122a6adaf30-20:0 in DeliveryChannel{OdeBpelEngine}
> WARN - OdeConsumer - Received a response for unknown
> partner role message exchange ID:127.0.0.1-122a6adaf30-20:0
> DEBUG - DeliveryChannelImpl - Send ID:127.0.0.1-122a6adaf30-20:0
> in DeliveryChannel{OdeBpelEngine}
> DEBUG - SecuredBroker - send exchange with secure broker
> DEBUG - SedaFlow - Called Flow send
> DEBUG - SedaQueue -
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@1fd9d8e dequeued
> exchange: InOut[
> id: ID:127.0.0.1-122a6adaf30-20:0
> status: Done
> role: provider
> interface: {http://teste/CP/}TesteServiceImpl
> service: {http://teste/CP/}TesteServiceImplService
> endpoint: TesteServiceImplPort
> operation: {http://teste/CP/}number
> in: <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> 1000
>
> out: <?xml version="1.0" encoding="UTF-8" standalone="no"?>1000
> ]
> DEBUG - CxfSeComponent - Received exchange: status: Done,
> role: provider
> DEBUG - CxfSeComponent - Retrieved correlation id: null
> Jul 23, 2009 10:46:28 AM org.apache.cxf.transport.jbi.JBITransportFactory
> setDeliveryChannel
> INFO: configuring DeliveryChannel:
> org.apache.servicemix.common.EndpointDeliveryChannel@188fa1d
> WARN - DiscoveryNetworkConnector - Could not start network bridge
> between: vm://localhost and: tcp://brgx0001:61616 due to:
> java.net.NoRouteToHostException: No route to host
> WARN - DiscoveryNetworkConnector - Could not start network bridge
> between: vm://localhost and: tcp://brgx0001:61616 due to:
> java.net.NoRouteToHostException: No route to host
> WARN - DiscoveryNetworkConnector - Could not start network bridge
> between: vm://localhost and: tcp://brgx0001:61616 due to:
> java.net.NoRouteToHostException: No route to host
> WARN - DiscoveryNetworkConnector - Could not start network bridge
> between: vm://localhost and: tcp://brgx0001:61616 due to:
> java.net.NoRouteToHostException: No route to host
> ERROR - OdeService - ODE MEX
> {MyRoleMex#hqejbhcnphr4ge5foktvuu [Client null] calling
> {http://teste/CP/}mainService.process(...)} resulted in an error.
> DEBUG - DeliveryChannelImpl - Send ID:127.0.0.1-122a6adaf30-10:0
> in DeliveryChannel{OdeBpelEngine}
> DEBUG - SecuredBroker - send exchange with secure broker
> DEBUG - SedaFlow - Called Flow send
> DEBUG - SedaQueue -
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@a0f9cb dequeued
> exchange: InOut[
> id: ID:127.0.0.1-122a6adaf30-10:0
> status: Error
> role: consumer
> interface: {http://teste/CP/}mainService
> service: {http://teste/CP/}mainService
> endpoint: mainPort
> operation: {http://teste/CP/}process
> in: <?xml version="1.0" encoding="UTF-8" standalone="no"?>1000
> error: java.util.concurrent.TimeoutException
> ]
> DEBUG - DeliveryChannelImpl - Notifying exchange
> ID:127.0.0.1-122a6adaf30-10:0(9e31f0) in DeliveryChannel{servicemix-cxf-bc}
> from processInboundSynchronousExchange
> DEBUG - DeliveryChannelImpl - Notified:
> ID:127.0.0.1-122a6adaf30-10:0(9e31f0) in DeliveryChannel{servicemix-cxf-bc}
> from sendSync
> Jul 23, 2009 10:46:57 AM org.apache.cxf.phase.PhaseInterceptorChain
> doIntercept
> INFO: Interceptor has thrown exception, unwinding now
> org.apache.cxf.interceptor.Fault
> at
> org.apache.servicemix.cxfbc.CxfBcConsumer$JbiPostInvokerInterceptor.handleMessage(CxfBcConsumer.java:647)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220)
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:78)
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:278)
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:252)
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:70)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:722)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206)
> at org.mortbay.jetty.handler.HandlerList.handle(HandlerList.java:49)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
> at org.mortbay.jetty.Server.handle(Server.java:324)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:842)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:648)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
> at
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)
> Caused by: java.util.concurrent.TimeoutException
> at
> org.apache.ode.bpel.engine.UnreliableMyRoleMessageExchangeImpl$ResponseFuture.get(UnreliableMyRoleMessageExchangeImpl.java:99)
> at
> org.apache.ode.bpel.engine.UnreliableMyRoleMessageExchangeImpl$ResponseFuture.get(UnreliableMyRoleMessageExchangeImpl.java:76)
> at
> org.apache.ode.bpel.engine.UnreliableMyRoleMessageExchangeImpl.invokeBlocking(UnreliableMyRoleMessageExchangeImpl.java:66)
> at org.apache.ode.jbi.OdeService.invokeOde(OdeService.java:205)
> at
> org.apache.ode.jbi.OdeService.onJbiMessageExchange(OdeService.java:142)
> at
> org.apache.ode.jbi.JbiMessageExchangeEventRouter.onJbiMessageExchange(JbiMessageExchangeEventRouter.java:67)
> at org.apache.ode.jbi.Receiver$1.run(Receiver.java:179)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)