Don't forget to also activate the server side SSL session cache (Apache HTTPD, NGinx, etc).
-- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Fri, Oct 17, 2014 at 10:23 AM, Romain Manni-Bucau < rmannibu...@tomitribe.com> wrote: > Hi > > pooling has to be done in your ConnectionFactory (cause the factory > knows about the "key" to use for the connection). You can have a look > to org.apache.openejb.client.SocketConnectionFactory which uses a map > of pool for this purpose. > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > > 2014-10-17 10:05 GMT+02:00 renz <renald.hene...@areasante.com>: > > Hello, > > > > I'm using remote EJB over HTTPS in a JSE app. > > I've set up mutual authentification to use a smart card on the client > side. > > I've developped my own ConnectionFactory and register it like explained > in a > > former post : > > > http://tomee-openejb.979440.n4.nabble.com/Remote-EJB-Client-With-Multiple-Certificates-td4665780.html#a4667061 > > > > Everything works fine except performance. It takes about 15 sec for each > > request. > > I can accept it for the first one because of the SSL Handshake. > > But it seems like a new connection with a new handshake is done for every > > request even 2 : > > - 1 for the bean lookup > > - 1 for the remote call > > > > Is there a way to use connection pooling or something else to try to > reuse > > connection when it is possible and avoid new SSL Handshake? > > > > I've logged one the server side and the header keep-alive is activate for > > each request. > > > > Any idea? > > > > Thank you very much. > > > > > > > > > > -- > > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/Remote-EJB-Client-Poor-Performance-tp4672371.html > > Sent from the TomEE Users mailing list archive at Nabble.com. >
