Hi, I have a Service that is deployed, following the instructions in the Sandesha2 user guide.
* The Service.xml for this service engages Sandesha2 by including: <module ref="sandesha2" /> * The axis2.xml file in the Axis web app. has been updated to include the <phase name="RMPhase"/> (in four places) * The service AAR deploys fine and I can see the service operations (including the Sandesha2 operations) when I access the URL: http://localhost:9081/axis2 and click on Services and then my service So everything appears OK on the service deployment, as far as I can tell. The client engages sandesha2: client.engageModule("sandesha2"); and the axis2.xml file used by the client also includes the <phase name="RMPhase"/> entries. When I run the client and watch via tcpmon, I see the CreateSequence and the corresponding CreateSequenceResponse. But I don't see the follow-up call to the actual service operation. The client blocks indefinitely (eventually times out) and the service is not invoked on the server side. The line of code that is blocked is response = client.sendReceive(...); If I disengage Sandesha2, everything works fine. When I engage it, the above code blocks until it times out. Any thoughts on what might be wrong or what typically causes such a behavior in Sandesha2? I am using Axis2 1.2 on WebSphere 6. - Nagi --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
