Hi Jens,
Could you please have a look at the sample 54 [1] and 55 [2] about the
session affinity load balancing and fail over endpoints
[1] - http://wso2.org/project/esb/java/1.6/docs/ESB_Samples.html#Sample54
[2] - http://wso2.org/project/esb/java/1.6/docs/ESB_Samples.html#Sample55
Thanks,
Ruwan
(PS: I don't think cross posting between Synapse and ESB is a good
practice, you may send your problem to one list and if unable to get the
answer try the other)
Jens Goldhammer wrote:
Hello,
I have the problem in understanding the session part of web services.
Web services should be stateless. Unfortunately same interactions need
support for sessions to have an idea which service call is in order
and which not according to the state of bpel process for example.
Image that I have competitive consumers which all can fulfill my
service request. Within a bpel process I call an external service
(which is also a bpel process) with synapse as intermediate and get an
answer from the other process back. How can I make sure that the next
call will also reach this bpel process which is already started and
not a bpel process on another server which offers me the same
interface? I have to make synapse clear that it should only send the
message to a certain server, but does not want to loose the
flexibility for failover.
Maybe the first invoke should be send to server 1, all other messages
should be send to server 1 because I have a bpel interaction. If the
first request goes to server 2, all other ongoing requests should be
send to server 2.
Any idea? I hope, it is clear enough...
Thanks,
Jens
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
