tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <rmannibu...@gmail.com>
Subject Re: RemoteClient blocked
Date Thu, 21 Feb 2013 09:04:35 GMT
Hi,

can you try last release (4.5.1)?

*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*



2013/2/21 Etienne Vincelette <etienne.vincelette@pco-innovation.com>

> Hi, I use stand alone openEJB 4.0 application. I have only one stateless
> bean
> implementing a remote interface. The client application run five thread
> that
> access this bean remotely. The client is on the same computer that the
> server. When the server sent few requests to the server, everything is
> working correctly. When the client send a lot of request on heavy load
> tests, everything go well for fifteen minutes then client cannot connect to
> server anymore.
>
> I'have checked the number of tcp connection, there is 5 established connect
> at all time. Before each use of my bean, I try to access the ping method
> implemented on the bean. If it doesn't response, I try to get my bean with
> context.lookup(). It is where I got
> ConnectionFailed{uri=ejbd://localhost:14201} message on my log. The only
> way
> to reestablish connection is to restart the client.
>
> Is there a way to force a connection, or all connection, to be released
> before next lookup?
>
> Regards,
>
> Etienne
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/RemoteClient-blocked-tp4660922.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message