BPEL Errors

Question

I've successfully deployed the sun bpel engine on servicemix. I get the following error when processing the response message from a another bpel (or service) on the bus invoked by original called bpel. It seems as though the bpel engine might not setting/processing all required atrributes for message exchange to correctly identify the original endpoint. Any solution for this?
java.lang.NullPointerException at com.sun.jbi.engine.bpel.impl.EndpointStatisticsHelper.getOutboundEndpointStatus(EndpointStatisticsHelper.java:91)
INFO: BPEL service engine started with following configurations
        Persistence Enabled : false
        Monitor Enabled : false
        Persistence Database NonXA JNDI Resource Name : jdbc/bpelseNonXA
        Persistence Database XA JNDI Resource Name : jdbc/bpelseXA
        Engine Expiry Interval (failover setting) : 60 seconds
        Debug Enabled : false
        Debug Port : 3,343
        Thread Count 10
        Engine Installed on Application Server Cluster : false
Dec 5, 2007 1:09:05 PM com.sun.jbi.engine.bpel.BPELSEInOutThread run
INFO: Started BPEL service engine in-out thread
Dec 5, 2007 1:09:05 PM com.sun.jbi.engine.bpel.BPELSEInOutThread run
INFO: Started BPEL service engine in-out thread
Dec 5, 2007 1:09:05 PM com.sun.jbi.engine.bpel.BPELSEDeployer init
INFO: Starting BPELSE deploy process
Dec 5, 2007 1:09:05 PM com.sun.bpel.model.impl.DefaultWSDLResolverImpl parseWSDL
INFO: Using DefaultParseContext for wsdl
Retrieving document at 'EchoService2.wsdl', relative to 'file:/C:/apache-service
mix-3.2.1/data/smx/service-assemblies/ServiceMix%20Sun%20BPEL%20Example/version_
1/sus/sun-bpel-engine/EchoService2/EchoService2Wrapper.wsdl'.
Dec 5, 2007 1:09:06 PM com.sun.bpel.model.impl.DefaultWSDLResolverImpl parseWSDL
INFO: Using DefaultParseContext for wsdl
Dec 5, 2007 1:09:06 PM com.sun.jbi.engine.bpel.EngineHelper deploy
INFO: Loaded bpel processes to engine
Dec 5, 2007 1:09:06 PM com.sun.jbi.engine.bpel.BPELSEDeployer init
INFO: Activated an endpoint. Service name {http://j2ee.netbeans.org/bpel/EchoSer
vice2}EchoService2Link, endpoint name EchoService2Role_myRole
Dec 5, 2007 1:09:06 PM com.sun.jbi.engine.bpel.BPELSEDeployer init
INFO: BPELSE deploy process finished
Dec 5, 2007 1:09:06 PM com.sun.jbi.engine.bpel.BPELSEDeployer init
INFO: Starting BPELSE deploy process
Dec 5, 2007 1:09:06 PM com.sun.bpel.model.impl.DefaultWSDLResolverImpl parseWSDL
INFO: Using DefaultParseContext for wsdl
Retrieving document at 'EchoService2.wsdl', relative to 'file:/C:/apache-service
mix-3.2.1/data/smx/service-assemblies/ServiceMix%20Sun%20BPEL%20Example/version_
1/sus/sun-bpel-engine/CallEchoService2/EchoService2Wrapper.wsdl'.
Dec 5, 2007 1:09:06 PM com.sun.bpel.model.impl.DefaultWSDLResolverImpl parseWSDL
INFO: Using DefaultParseContext for wsdl
Dec 5, 2007 1:09:06 PM com.sun.bpel.model.impl.DefaultWSDLResolverImpl parseWSDL
INFO: Using DefaultParseContext for wsdl
Retrieving document at 'CallEchoService2.wsdl', relative to 'file:/C:/apache-ser
vicemix-3.2.1/data/smx/service-assemblies/ServiceMix%20Sun%20BPEL%20Example/vers
ion_1/sus/sun-bpel-engine/CallEchoService2/CallEchoService2Wrapper.wsdl'.
Dec 5, 2007 1:09:06 PM com.sun.bpel.model.impl.DefaultWSDLResolverImpl parseWSDL
INFO: Using DefaultParseContext for wsdl
Dec 5, 2007 1:09:06 PM com.sun.jbi.engine.bpel.EngineHelper deploy
INFO: Loaded bpel processes to engine
Dec 5, 2007 1:09:06 PM com.sun.jbi.engine.bpel.EngineHelper deploy
INFO: Consumes Endpoint, service name {http://j2ee.netbeans.org/bpel/CallProxySe
rvice2}EchoService2Link, endpoint name EchoService2Role_partnerRole
Dec 5, 2007 1:09:06 PM com.sun.jbi.engine.bpel.BPELSEDeployer init
INFO: Activated an endpoint. Service name {http://j2ee.netbeans.org/bpel/CallPro
xyService2}CallEchoService2Link, endpoint name CallEchoService2Role_myRole
Dec 5, 2007 1:09:06 PM com.sun.jbi.engine.bpel.BPELSEDeployer init
INFO: BPELSE deploy process finished
INFO  - DefaultListableBeanFactory     - Pre-instantiating singletons in org.spr
[email protected]52e: defining b
eans [org.apache.servicemix.http.endpoints.HttpSoapConsumerEndpoint,org.apache.s
ervicemix.http.endpoints.HttpSoapConsumerEndpoint#1]; root of factory hierarchy
INFO  - jetty                          - jetty-6.1.5
INFO  - jetty                          - Started SelectChannelConnector@localhos
t:28181
Dec 5, 2007 1:09:33 PM com.sun.jbi.engine.bpel.BPELSEInOutThread processMsgEx
INFO: Pattern for exchange Id ID:129.2.134.164-116ab7f0043-10:0 is http://www.w3
.org/2004/08/wsdl/in-out
Dec 5, 2007 1:09:33 PM com.sun.jbi.engine.bpel.EngineChannel twoWayInvoke
INFO: Sending a two  way outbound message to the NMR. MessageExchangeId is ID:12
9.2.134.164-116ab7f0043-20:0, service name is {http://j2ee.netbeans.org/bpel/Cal
lProxyService2}EchoService2Link, endpoint name is EchoService2Role_partnerRole.
Dec 5, 2007 1:09:33 PM com.sun.jbi.engine.bpel.BPELSEInOutThread processMsgEx
INFO: Pattern for exchange Id ID:129.2.134.164-116ab7f0043-20:0 is http://www.w3
.org/2004/08/wsdl/in-out
Dec 5, 2007 1:09:33 PM com.sun.jbi.engine.bpel.EngineChannel reply
INFO: Sending Reply for MessageEx id ID:129.2.134.164-116ab7f0043-20:0
Dec 5, 2007 1:09:33 PM com.sun.jbi.engine.bpel.BPELSEInOutThread processMsgEx
INFO: Pattern for exchange Id ID:129.2.134.164-116ab7f0043-20:0 is http://www.w3
.org/2004/08/wsdl/in-out
Dec 5, 2007 1:09:33 PM com.sun.jbi.engine.bpel.BPELSEInOutThread processMsgEx
WARNING: Failed to process response for InOut Message M Ex ID:129.2.134.164-116a
b7f0043-20:0
java.lang.NullPointerException
        at com.sun.jbi.engine.bpel.impl.EndpointStatisticsHelper.getOutboundEndp
ointStatus(EndpointStatisticsHelper.java:91)
        at com.sun.jbi.engine.bpel.BPELSEInOutThread.processResponse(BPELSEInOut
Thread.java:431)
        at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThr
ead.java:257)
        at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:
161)
Dec 5, 2007 1:09:33 PM com.sun.jbi.engine.bpel.BPELSEHelper sendError
WARNING: Setting MessageEx id ID:129.2.134.164-116ab7f0043-20:0 with error: null
Dec 5, 2007 1:09:33 PM com.sun.jbi.engine.bpel.BPELSEInOutThread processMsgEx
INFO: Pattern for exchange Id ID:129.2.134.164-116ab7f0043-20:0 is http://www.w3
.org/2004/08/wsdl/in-out

Answer 1

That definitely sounds incorrect. But I have few questions,
The code just makes use of the service and endpoint and nothing else. It is using the same service and endpoint that the bpel-se set on the message exchange. So it is odd that it should fail!! unless somewhere in the round trip of the invoke these value got changed. While I am sure that no one should be changing these values on ME, maybe someone does. Could you please verify that didn't happen? Is it possible for you to verify?
Did you try the same BPEL-SE outside of service mix and does it happen?
thanks,
Kiran Bhumana.