Is there away to not open new TCP connection for each call?

[avihaimar]

Hey,

I have java client that communicate with Ejb3 stateless session bean (deployed on jboss4.2).

The communication is Ejb3 over Https.
I dont have a lot of clients (up to 10 at the same time).
when the client startup it create initial context an lookup for the facade.
all the operation is against this facade.

i noticed that in each call new TCP connection is created, is there a way to avoid it and leave the connection opened all the time?

Thank you

[ron_sigal]

See thread "Socket keep alive with client EJB" http://www.jboss.com/index.html?module=bb&op=viewtopic&t=134089 .

[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

[ron_sigal]

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.