Hi Paul,
I think this is due to a fix that was done to support sync scenarios. At
module initiation we add a property to the configContext and this is what
causes this unusual behavior.
There is a TargetResolver object that also get added which should check
weather the message is unreliable and make it work correctly. The problem is
the current check only checks for a boolean property in the message context.
So u hv to add the following property to make the Non-RM case work.
clientOptions.setProperty("Sandesha2UnreliableMessage", Constants.VALUE_TRUE
);
I know it looks bad to ask nonRM clients to add this when the Sandesha2
module is present in the repo. We should think of a better way.
Matt, any ideas on this (this part was added by u, right ? ).
Chamikara
On 4/18/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
I've got a strange problem with the latest builds of Sandesha and Axis2
1.2.
I have a client, and I have Sandesha2 in my modules directory, but not
engaged on the client.
My client is just blocking and completely ignoring the response. If I
delete Sandesha2 MAR from the modules directory, everything works. If
I engage sandesha then it works!
Here is the interaction and the timeout exception.
Response:
HTTP/1.1 200 OK
Content-Length: 728
Content-Type: application/soap+xml; charset=utf-8
Server: Microsoft-HTTPAPI/1.0
Date: Wed, 18 Apr 2007 15:00:04 GMT
Connection: close
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope";
xmlns:a="http://www.w3.org/2005/08/addressing";>
<s:Header>
<a:Action
s:mustUnderstand="1">http://tempuri.org/IProfileServer/getProfileResponse
</a:Action>
<a:RelatesTo>urn:uuid:475EAE3D681354C78C1176908404902</a:RelatesTo>
</s:Header>
<s:Body>
<getProfileResponse xmlns="http://tempuri.org/";>
<getProfileResult
xmlns:b="http://schemas.datacontract.org/2004/07/ProfileServer";
xmlns:i="http://www.w3.org/2001/XMLSchema-instance";>
<b:nickname>paul</b:nickname>
</getProfileResult>
</getProfileResponse>
</s:Body></s:Envelope>
Exception:
18-Apr-2007 16:00:04 org.apache.axis2.deployment.ModuleDeployer deploy
INFO: Deploying module: addressing-1.2
18-Apr-2007 16:00:04 org.apache.axis2.deployment.ModuleDeployer deploy
INFO: Deploying module: sandesha2
18-Apr-2007 16:00:04 org.apache.axis2.deployment.ModuleDeployer deploy
INFO: Deploying module: soapmonitor-1.2
18-Apr-2007 16:00:04 org.apache.sandesha2.SandeshaModule init
SEVERE: Could not load module policies. Using default values.
18-Apr-2007 16:00:04 org.apache.axis2.deployment.ServiceDeployer deploy
INFO: Deploying Web service: version.aar
Exception in thread "main" org.apache.axis2.AxisFault: Time out while
waiting for the server to send the response.
at org.apache.axis2.description.OutInAxisOperationClient.execute(
OutInAxisOperation.java:285)
at org.tempuri.ProfileServerServiceStub.getProfile(
ProfileServerServiceStub.java:149)
at ProfileClient.main(ProfileClient.java:47)
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Chamikara Jayalath
WSO2 Inc.
http://wso2.com/
http://wso2.org/ - For your Oxygen needs
