Re: Sandesha2 question?

David Parsons1 <[email protected]> Tue, 27 Jul 2010 09:44:51 +0100
Newsgroups gmane.comp.apache.webservices.fx.devel
Message-ID <OF4D2466C3.BD90A99E-ON8025776C.005E4905-8025776C.0060D994@uk.ibm.com>
--=_alternative 00609F008025776C_=
Content-Type: text/plain; charset="US-ASCII"

Hi,

In answer to your questions.  UnmanagedNonPersistent is an inmemory 
solution.  The benefits are minimal configuration and reliability during 
service downtime e.g. a service has been taken down for maintenance.

The managed offerings are more than that and are designed for Web Services 
that require reliability but are also highly available and scalable. Hence 
clustered servers are supported and reliability is maintained even if 
servers become unavailable.

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:
Amila Suriarachchi <[email protected]>
To:
David Parsons1/UK/IBM@IBMGB
Cc:
venkov <[email protected]>, [email protected]
Date:
25/07/2010 06:44
Subject:
Re: Sandesha2 question?





On Fri, Jul 23, 2010 at 4:47 PM, David Parsons1 <[email protected]> 
wrote:

Hi, 

The lastMessage property isn't saying to the Sandesha Handler wait for the 
last message before delivering any of the messages on that sequence to the 
client or service.  All it is saying to Sandesha is that there will be no 
more messages sent on this sequence so you can terminate it.  It is just 
there for sequence administration.  One thing you can do is set the 
inorder property.  This tells the Sandesha handler to deliver the messages 
that have arrived in the order they were originally sent by the client. 
 Therefore if message 1 & 3 have arrived but not message 2, Sandesha would 
have the service invoked by message 1 but not message 3.  It would hold 
onto message 3 until msg 2 had arrived and been invoked. 

If you want all or nothing you either need to trust sandesha i.e. that all 
the messages will get sent.  One drawback of this is that your have to 
rely on the server hosting your service to always be available, that way 
the resending of lost messages is handled for you.  Or you switch to 
having some transactional solution. 

I have an article that has some early sections that may be of interest. 
 The sections that may be of interest talk about what WS-RM is and the key 
concepts that it uses, 
http://www.ibm.com/developerworks/websphere/library/techarticles/0912_parsons/0912_parsons.html 


In this article there are three ways of using WS-RM, namely 
UnManagedNonPersistent, ManagedNonPersistent and ManagedPersistent.

What is the real benefit of using UnManagedNonPersistent. In your article 
there are two things. Here first thing does not apply since it can not 
survive on a server restart. Can we achieve the second benefit just 
increasing the tcp time out time? In other words can we use the tcp 
retransmission? I think WS-RM follows the same principles as in tcp 
protocol.

For ManagedNonPersistent and ManagedPersistent what does the clustering 
realy means? I assume underling WS-RM implementation that WAS use is 
Sandesha2. So it is about sharing one storage between different RM Nodes 
so that they can use to receive messages for a same WS-RM sequence? Do you 
refer this common storage as messging engine?

I did my Msc[1] on WS-RM to reasearch on how to achive application to 
application reliability. Is there a similar thing happens in the 
ManagedPersistent using distributed transactions? In my work, it can 
support stanalone clients since I uses the Atomikos library get 
distributed transactions.

thanks,
Amila.

[1] 
http://amilachinthaka.blogspot.com/2010/03/queued-transaction-processing-with-ws.html

 

Regards, 

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: 
23/07/2010 10:20 
Subject: 
Sandesha2 question?






How does Exactly-once option of WSRM works?

I am using the ping sample from sandesha2
where it sends 3 messages and the 3rd is set to be last!
after it gets the 3rd one it terminates the sequence and everything is ok!

But if i remove the last message property or 
before i send the last one i terminate the program!

I have the following situation the server gets first and second message,
execute the action for each one, without waiting for the last message!

I want to execute all or nothing!
-- 
View this message in context: 
http://old.nabble.com/Sandesha2-question--tp29245485p29245485.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 









-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/







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 00609F008025776C_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi,</font>
<br>
<br><font size=2 face="sans-serif">In answer to your questions. &nbsp;UnmanagedNonPersistent
is an inmemory solution. &nbsp;The benefits are minimal configuration and
reliability during service downtime e.g. a service has been taken down
for maintenance.</font>
<br>
<br><font size=2 face="sans-serif">The managed offerings are more than
that and are designed for Web Services that require reliability but are
also highly available and scalable. &nbsp;Hence clustered servers are supported
and reliability is maintained even if servers become unavailable.</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">Amila Suriarachchi &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">David Parsons1/UK/IBM@IBMGB</font>
<tr>
<td valign=top><font size=1 color=#5f5f5f face="sans-serif">Cc:</font>
<td><font size=1 face="sans-serif">venkov &lt;[email protected]&gt;,
[email protected]</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">25/07/2010 06:44</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><font size=3><br>
</font>
<br><font size=3>On Fri, Jul 23, 2010 at 4:47 PM, David Parsons1 &lt;</font><a href=mailto:[email protected]><font size=3 color=blue><u>[email protected]</u></font></a><font size=3>&gt;
wrote:</font>
<br><font size=2 face="sans-serif"><br>
Hi,</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
The lastMessage property isn't saying to the Sandesha Handler wait for
the last message before delivering any of the messages on that sequence
to the client or service. &nbsp;All it is saying to Sandesha is that there
will be no more messages sent on this sequence so you can terminate it.
&nbsp;It is just there for sequence administration. &nbsp;One thing you
can do is set the inorder property. &nbsp;This tells the Sandesha handler
to deliver the messages that have arrived in the order they were originally
sent by the client. &nbsp;Therefore if message 1 &amp; 3 have arrived but
not message 2, Sandesha would have the service invoked by message 1 but
not message 3. &nbsp;It would hold onto message 3 until msg 2 had arrived
and been invoked.</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
If you want all or nothing you either need to trust sandesha i.e. that
all the messages will get sent. &nbsp;One drawback of this is that your
have to rely on the server hosting your service to always be available,
that way the resending of lost messages is handled for you. &nbsp;Or you
switch to having some transactional solution.</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
I have an article that has some early sections that may be of interest.
&nbsp;The sections that may be of interest talk about what WS-RM is and
the key concepts that it uses, </font><a href=http://www.ibm.com/developerworks/websphere/library/techarticles/0912_parsons/0912_parsons.html target=_blank><font size=2 color=blue face="sans-serif"><u>http://www.ibm.com/developerworks/websphere/library/techarticles/0912_parsons/0912_parsons.html</u></font></a><font size=3>
</font>
<br><font size=3><br>
In this article there are three ways of using WS-RM, namely UnManagedNonPersistent,
ManagedNonPersistent and ManagedPersistent.<br>
<br>
What is the real benefit of using UnManagedNonPersistent. In your article
there are two things. Here first thing does not apply since it can not
survive on a server restart. Can we achieve the second benefit just increasing
the tcp time out time? In other words can we use the tcp retransmission?
I think WS-RM follows the same principles as in tcp protocol.<br>
<br>
For ManagedNonPersistent and ManagedPersistent what does the clustering
realy means? I assume underling WS-RM implementation that WAS use is Sandesha2.
So it is about sharing one storage between different RM Nodes so that they
can use to receive messages for a same WS-RM sequence? Do you refer this
common storage as messging engine?<br>
<br>
I did my Msc[1] on WS-RM to reasearch on how to achive application to application
reliability. Is there a similar thing happens in the ManagedPersistent
using distributed transactions? In my work, it can support stanalone clients
since I uses the Atomikos library get distributed transactions.<br>
<br>
thanks,<br>
Amila.<br>
<br>
[1] </font><a href="http://amilachinthaka.blogspot.com/2010/03/queued-transaction-processing-with-ws.html"><font size=3 color=blue><u>http://amilachinthaka.blogspot.com/2010/03/queued-transaction-processing-with-ws.html</u></font></a><font size=3><br>
&nbsp;</font>
<br><font size=2 face="sans-serif"><br>
Regards,</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Dave</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Dave Parsons<br>
Web Services Development<br>
INTERNAL: &nbsp;David Parsons1/UK/IBM@IBMGB :: DE3F20 :: 246930<br>
EXTERNAL: &nbsp;</font><a href=mailto:[email protected] target=_blank><font size=2 color=blue face="sans-serif"><u>[email protected]</u></font></a><font size=2 face="sans-serif">
:: (01962) 816930<br>
Mail Point 211, IBM Hursley Park, Winchester. SO21 2JN</font><font size=3><br>
<br>
<br>
</font>
<table width=100%>
<tr valign=top>
<td width=18%><font size=1 color=#5f5f5f face="sans-serif">From:</font><font size=3>
</font>
<td width=81%><font size=1 face="sans-serif">venkov &lt;</font><a href=mailto:[email protected] target=_blank><font size=1 color=blue face="sans-serif"><u>[email protected]</u></font></a><font size=1 face="sans-serif">&gt;</font><font size=3>
</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font><font size=3>
</font>
<td><a href="mailto:[email protected]" target=_blank><font size=1 color=blue face="sans-serif"><u>[email protected]</u></font></a><font size=3>
</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font><font size=3>
</font>
<td><font size=1 face="sans-serif">23/07/2010 10:20</font><font size=3>
</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font><font size=3>
</font>
<td><font size=1 face="sans-serif">Sandesha2 question?</font></table>
<br><font size=3><br>
</font>
<hr noshade>
<br><font size=3><br>
<br>
</font><tt><font size=2><br>
<br>
How does Exactly-once option of WSRM works?<br>
<br>
I am using the ping sample from sandesha2<br>
where it sends 3 messages and the 3rd is set to be last!<br>
after it gets the 3rd one it terminates the sequence and everything is
ok!<br>
<br>
But if i remove the last message property or <br>
before i send the last one i terminate the program!<br>
<br>
I have the following situation the server gets first and second message,<br>
execute the action for each one, without waiting for the last message!<br>
<br>
I want to execute all or nothing!<br>
-- <br>
View this message in context: </font></tt><a href="http://old.nabble.com/Sandesha2-question--tp29245485p29245485.html" target=_blank><tt><font size=2 color=blue><u>http://old.nabble.com/Sandesha2-question--tp29245485p29245485.html</u></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: </font></tt><a href="mailto:[email protected]" target=_blank><tt><font size=2 color=blue><u>[email protected]</u></font></tt></a><tt><font size=2><br>
For additional commands, e-mail: </font></tt><a href="mailto:[email protected]" target=_blank><tt><font size=2 color=blue><u>[email protected]</u></font></tt></a><tt><font size=2><br>
</font></tt><font size=3><br>
<br>
</font><font size=2 face="sans-serif"><br>
</font><font size=3><br>
</font><font size=2 face="sans-serif"><br>
</font>
<br>
<hr><font size=2 face="sans-serif"><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><font size=3> </font>
<p><font size=2 face="sans-serif"><br>
</font><font size=3><br>
<br>
</font><font size=2 face="sans-serif"><br>
</font>
<p><font size=3><br>
<br>
<br>
-- <br>
Amila Suriarachchi<br>
WSO2 Inc.<br>
blog: </font><a href=http://amilachinthaka.blogspot.com/><font size=3 color=blue><u>http://amilachinthaka.blogspot.com/</u></font></a>
<p>
<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 00609F008025776C_=--