Ok, sorry Paul :). I simply meant if there's anything special I should know in order to use pure JMS inside my web service running on top of axis2/synapse, i.e. I guess I should use a TextMessage if I want to forward a message somewhere. What shall the it include?, just the SOAP body or the full envelope? Does it make sense to mix pure JMS and SOAP or it's better to split these tasks? If I split them, what about inter-leavings and other time related problems?
Thanks, Michele On Thu, 2007-08-09 at 14:55 +0100, Paul Fremantle wrote: > I didn't understand part two of question #1!!!! > > Synapse can also do load-balancing based on Axis2 sessions with > affinity, so each request goes to the server that initiated the > session. > > Paul > > On 8/9/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > > Paul, > > > > thanks very much for the quick answer. However my idea about the proxy > > was a bit different, that is the proxy is used to address fault > > tolerance issues (at least at this stage), not for performance reasons. > > The rationale is that my web service is statefull and it looks to me > > that keeping the replica in sync would be very messy as the load > > increases (and beyond a certain point it would be infeasible). > > I've notice you didn't reply to the second part of question #1, so I > > guess I can do it the usual way (i.e. via MessageListener on the > > receiver side for async processing). > > > > Thanks, > > Michele > > > > > > On Thu, 2007-08-09 at 13:47 +0100, Paul Fremantle wrote: > > > Michele > > > > > > You could use Apache Synapse (ws.apache.org/synapse). It can take > > > XML/SOAP over HTTP requests and forward them to JMS. No coding > > > required. It can also perform load-balancing. You could do round-robin > > > DNS to Synapse to spread the load to a pair of Synapse servers or just > > > have one. It can handle fairly high loads on its own. > > > > > > Paul > > > > > > On 8/9/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > > > > Hi all, > > > > > > > > I want use both SOAP over HTTP and SOAP over JMS (topic with multiple > > > > subscribers) but it's not very clear how to achieve my goal. > > > > I want to put a sort of proxy/load balancer in front of my distributed > > > > app to receive HTTP requests and forward them via JMS to a replicated > > > > web service. > > > > Here are my questions: > > > > 1 - How do I configure axis2 assuming it runs inside tomcat? I guess the > > > > transport is completely transparent to my app, but what about if I want > > > > to use JMS to accomplish other tasks? > > > > 2 - What do you suggest to use as proxy (I'll eventually need to modify > > > > it in order to detect and react to node crashes). > > > > > > > > > > > > Thanks, > > > > Michele > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
