[wsas-java-dev] [Fwd: Fwd: Wierd problem with Sandesha]
Chamikara Jayalath
chamikara at wso2.com
Thu Apr 19 00:07:31 PDT 2007
Solved. Will commit the correction.
Chamikara
Paul Fremantle wrote:
> Folks
>
> This model means that (since Sandesha is deployed by default) *every*
> WSAS client is going to have to be updated with this hack. I don't
> think thats acceptable.
>
> Paul
>
> ---------- Forwarded message ----------
> From: Chamikara Jayalath <chamikaramj at gmail.com>
> Date: Apr 19, 2007 5:47 AM
> Subject: Re: Wierd problem with Sandesha
> To: Paul Fremantle <pzfreo at gmail.com>
> Cc: sandesha-dev at ws.apache.org, Matthew Lovett <MLOVETT at uk.ibm.com>
>
>
> 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 < pzfreo at gmail.com> 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
>> paul at wso2.com
>>
>> "Oxygenating the Web Service Platform", www.wso2.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: sandesha-dev-unsubscribe at ws.apache.org
>> For additional commands, e-mail: sandesha-dev-help at ws.apache.org
>>
>>
>
>
>
--
Chamikara Jayalath
WSO2 Inc.
http://wso2.com/
http://wso2.org/ - For your Oxygen needs
More information about the Wsas-java-dev
mailing list