Re: Sandesha2 question?

--=_alternative 0045FEA38025776D_=
Content-Type: text/plain; charset="US-ASCII"

Hi,

If the JVM your client is running in also has Sandesha2 and you are using 
the Sandesha2 inmemory storage manager and your client crashing means the 
JVM is lost, all WS-RM sequence state will be lost as well.  When your 
client then restarts and resends the messages, Sandesha will see them as 
new messages and will send them on new sequences.  Your provider will then 
see the messages coming in on new sequences and have them invoked as if 
they had never arrived before.

You may want to consider the persistent storage manager implementation 
that is available as part of Sandesha2.  I'm not  too familiar with this. 
I don;t think this will work for request/response clients (i.e. 2 way) as 
your client would have to know a response was due after it recovered. That 
is for Sync and Async.  You may also want to consider having a 
transactional solution whereby you write the reliability into the apps 
yourself and not use Sandesha2.  This could work better for recoverable 
clients that are doing two way request/response message exchange 
protocols.

As for your issue with the createSequenceResponse I think this could be 
related to this JIRA, https://issues.apache.org/jira/browse/SANDESHA2-197
Are you using an Axis2 release of 1.4 or higher and is your failing 
scenario a sync request using WS-RM 1.1?  If  so it is likely to be the 
same issue.  A later matching 1.5 release of Sandesha2 has been on the 
cards for a while.

Dave

Dave Parsons
Web Services Development
INTERNAL:  David Parsons1/UK/IBM@IBMGB :: DE3F20 :: 246930
EXTERNAL:  [email protected] :: (01962) 816930
Mail Point 211, IBM Hursley Park, Winchester. SO21 2JN




From:
venkov <[email protected]>
To:
[email protected]
Date:
26/07/2010 14:48
Subject:
Re: Sandesha2 question?




Hi, there!
Thanks for the response!
I think i understood that!

I am trying to create the following situation:
Make a connection between the server and client,
and crash the client after he sends some messages, but not all.
After that i restart it, so it sends all again.

The server receive them and makes the first ones like duplicates and 
delete
them!
I tried every option and forums, but i could not do it!
the servers executes everything from the beginning!

I am using this client:
http://old.nabble.com/file/p29266722/SyncPingClient.java 
SyncPingClient.java 

Another problem i got is when i uncomment the spec option,
to use spec.v1_1, the client send CreateSequance, The Server creates
CreateSequanceResponse but does not send it or I don`t know where it sends
it!
Any idea what should i do!
-- 
View this message in context: 
http://old.nabble.com/Sandesha2-question--tp29245485p29266722.html
Sent from the Apache Sandesha mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]









Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU






--=_alternative 0045FEA38025776D_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi,</font>
<br>
<br><font size=2 face="sans-serif">If the JVM your client is running in
also has Sandesha2 and you are using the Sandesha2 inmemory storage manager
and your client crashing means the JVM is lost, all WS-RM sequence state
will be lost as well. &nbsp;When your client then restarts and resends
the messages, Sandesha will see them as new messages and will send them
on new sequences. &nbsp;Your provider will then see the messages coming
in on new sequences and have them invoked as if they had never arrived
before.</font>
<br>
<br><font size=2 face="sans-serif">You may want to consider the persistent
storage manager implementation that is available as part of Sandesha2.
&nbsp;I'm not &nbsp;too familiar with this. &nbsp;I don;t think this will
work for request/response clients (i.e. 2 way) as your client would have
to know a response was due after it recovered. &nbsp;That is for Sync and
Async. &nbsp;You may also want to consider having a transactional solution
whereby you write the reliability into the apps yourself and not use Sandesha2.
&nbsp;This could work better for recoverable clients that are doing two
way request/response message exchange protocols.</font>
<br>
<br><font size=2 face="sans-serif">As for your issue with the createSequenceResponse
I think this could be related to this JIRA, </font><a href="https://issues.apache.org/jira/browse/SANDESHA2-197"><font size=2 face="sans-serif">https://issues.apache.org/jira/browse/SANDESHA2-197</font></a>
<br><font size=2 face="sans-serif">Are you using an Axis2 release of 1.4
or higher and is your failing scenario a sync request using WS-RM 1.1?
&nbsp;If &nbsp;so it is likely to be the same issue. &nbsp;A later matching
1.5 release of Sandesha2 has been on the cards for a while.</font>
<br>
<br><font size=2 face="sans-serif">Dave</font>
<br>
<br><font size=2 face="sans-serif">Dave Parsons<br>
Web Services Development<br>
INTERNAL: &nbsp;David Parsons1/UK/IBM@IBMGB :: DE3F20 :: 246930<br>
EXTERNAL: &nbsp;[email protected] :: (01962) 816930<br>
Mail Point 211, IBM Hursley Park, Winchester. SO21 2JN<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">venkov &lt;[email protected]&gt;</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">[email protected]</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">26/07/2010 14:48</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">Re: Sandesha2 question?</font></table>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2><br>
Hi, there!<br>
Thanks for the response!<br>
I think i understood that!<br>
<br>
I am trying to create the following situation:<br>
Make a connection between the server and client,<br>
and crash the client after he sends some messages, but not all.<br>
After that i restart it, so it sends all again.<br>
<br>
The server receive them and makes the first ones like duplicates and delete<br>
them!<br>
I tried every option and forums, but i could not do it!<br>
the servers executes everything from the beginning!<br>
<br>
I am using this client:<br>
</font></tt><a href=http://old.nabble.com/file/p29266722/SyncPingClient.java><tt><font size=2>http://old.nabble.com/file/p29266722/SyncPingClient.java</font></tt></a><tt><font size=2>
SyncPingClient.java <br>
<br>
Another problem i got is when i uncomment the spec option,<br>
to use spec.v1_1, the client send CreateSequance, The Server creates<br>
CreateSequanceResponse but does not send it or I don`t know where it sends<br>
it!<br>
Any idea what should i do!<br>
-- <br>
View this message in context: </font></tt><a href="http://old.nabble.com/Sandesha2-question--tp29245485p29266722.html"><tt><font size=2>http://old.nabble.com/Sandesha2-question--tp29245485p29266722.html</font></tt></a><tt><font size=2><br>
Sent from the Apache Sandesha mailing list archive at Nabble.com.<br>
<br>
<br>
---------------------------------------------------------------------<br>
To unsubscribe, e-mail: [email protected]<br>
For additional commands, e-mail: [email protected]<br>
<br>
</font></tt>
<br>
<br><font size=2 face="sans-serif"><br>
</font>
<br><font size=2 face="sans-serif"><br>
</font>
<hr><font size=2 face="sans-serif"><br>
<i><br>
</i></font>
<p><font size=2 face="sans-serif"><i>Unless stated otherwise above:<br>
IBM United Kingdom Limited - Registered in England and Wales with number
741598. <br>
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU</i></font>
<p><font size=2 face="sans-serif"><br>
<br>
</font>
<br>
<br><font size=2 face="sans-serif"><br>
</font>
--=_alternative 0045FEA38025776D_=--