-
1. Re: Is there away to not open new TCP connection for each ca
ron_sigal May 2, 2008 2:16 AM (in response to avihaimar)See thread "Socket keep alive with client EJB" http://www.jboss.com/index.html?module=bb&op=viewtopic&t=134089 .
-
2. Re: Is there away to not open new TCP connection for each ca
avihaimar May 2, 2008 2:50 AM (in response to avihaimar)Thank you,
i saw this, but i am using jboss4.2.
so for remoting i am using -JBossRemoting Version 2.2.0 SP4 (Bluto)
can i upgrade only this (or group of jars)?
Do i have any other alternative?
Thank you -
3. Re: Is there away to not open new TCP connection for each ca
ron_sigal May 10, 2008 5:19 AM (in response to avihaimar)1. You could try running AS 4.2 with Remoting 2.4. It hasn't been tested, but I believe it should work. No promises, though.
2. You could apply the change from JBREM-877 "New Socket Connection is being Created for Every Client Request to the Server" and roll your own jboss-remoting.jar.
3. As I mentioned in the other thread, multiple copies of org.jboss.remoting.Client (which is used by EJB3 clients) connected to the same server share the same underlying invoker and connection pool. If you keep one EJB3 alive, that should be enough to keep a shared connection pool in existence.