This one is a little tougher because it is not based upon protocol. You want
to maintain some kind of internal tracker. Clearly Axis2 does this since it
is able to generate a response to an incoming message. Thus it must have
something that tracks it (which may be based upon protocol). However,
set
[
https://issues.apache.org/jira/browse/AXIS-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728610#comment-13728610
]
Andreas Veithen commented on AXIS-2893:
---
Please note that the Eclipse tooling for Axi
hi brian,
My goal is to achieve fault tolerance using replication in web services,
-->I have a set of web services containers interconnected via a private p2p
network ,which are communicating with a specific protocol(the main
problematic of the project).
-->When a problem occur(one server goes o
It's probably time to reopen the discussion about support for Java 1.5
in Axis2. My POV has always been that we should drop support for Java
1.5 only if there are good reasons to do so. Obviously the fact that
we no longer have a continuous integration system able to support Java
1.5 builds out of
Walid,
Sounds involved. Could the same be accomplished using the WS reliable
messaging protocol (Sandesha project in the Axis2/Apache hierarchy)? Would
be almost no work; just add the module in your Axis2 xml. The main
difference (I think) from your proposal is that this protocol is still point
Yes Brian ,but my first problem is to address problems when a web server
goes down ,and figure a way to not loose requests which are in process,so
the clients can have a response even if it is from another endpoint.
when a web server goes down ,another hosted in another machine,will takes
his place
Walid,
It is my understanding that the ws-reliable transfer does that; if a server
goes down while a request is in progress the request remains on the client
side. The reliable messaging transfer sets up a "shell" around the transfer
of interest and the shell does not terminate until the messag
As i see ws-addressing is very helpful ,but you know my work (final
year engineering project)is an approach based redundancy to achieve fault
tolerance, so processing like that is the only way authorized.thank you
very much Brian for your helpful advises ,I hope that I've not bothered
you too much
Interesting dichotomy as there *seems to be* 2 working solutions for the same
problem
solution1)implement reliable-messaging and block consequent processing until
ALL transmitted messages are acknowledged
PROS: No additional Hardware or servers required ..development effort will
block processin
