[esb-java-dev] tomcat/war support

[Asankha C. Perera]

Sanjiva
> Axis2 most certainly does not open up new ports .. which is a lot more 
> significant than starting a thread.
Sorry.. I made a mistake here. You are correct, not if one uses the TCP 
transport.. etc but that would not be a common case anyway

The difference between Axis2 and Synapse is that with a blocking servlet 
model, an ESB can easily exhaust all threads. This can be even shown for 
a Tomcat server with a concurrent user counter over its configured 
thread count - if the requests are made to take a bit of time. I 
remember I did this with around 100 users for a plain tomcat servlet.. 
where as the NIO transport has allowed us to go even more than 2560 
concurrent users. After all we dont want someone to report something 
like this against us http://issues.apache.org/activemq/browse/SM-1002 
(Note this was reported by Ruwan against SM)
> I agree we need to keep the NIO model in its native form, of course. 
> However, I'm not convinced that people won't be really surprised that 
> they deploy as a war but need to go to a port different from the 
> servlet container's port to access the features!
No.. the luckily ESB console runs off the default port of the container :-)
> Can you guys ask the user who asked for this and get his/her opinion?
http://mail-archives.apache.org/mod_mbox/ws-synapse-user/200707.mbox/%3cB319B58E71D8C6469773C11686024E69F7841B@exbah01.e-Space.local%3e

That's the response from the actual user..

thanks
asnakha