D
Dshebeko
Guest
Thanks for quick answer
Setting up RunTimeProperties.setInitialConnections(10) results in establishing 10 connections between Java client and OpenEdge AppServer after instantiating AppObject (in my case OpenEdgeProxy) class. So conn.getSessionPool().size() returns 10; Obviously, both sides (java client and appserver) are implied cause every connection implies at least two sides. 1. Actually Tomcat is running threads according to Java Servlet API specification, I can't manage this, think it's is running at most 20 threads concurrently. Each such a thread calls sendMessage(). 2. I set up initialSrvrInstance to 2, maxSrvrInstance to 35 Although I didn't change default maxClientInstance value, max number of client connections is 25. I see it in AppServer status after testing. Number of my client connections is limited when I run both java client and app server in State-free mode. It exactly equals to sessionPoolSize (25) Dmitry Shebeko, Banking Information Systems (http://www.bis.ru/eng/)
Continue reading...
Setting up RunTimeProperties.setInitialConnections(10) results in establishing 10 connections between Java client and OpenEdge AppServer after instantiating AppObject (in my case OpenEdgeProxy) class. So conn.getSessionPool().size() returns 10; Obviously, both sides (java client and appserver) are implied cause every connection implies at least two sides. 1. Actually Tomcat is running threads according to Java Servlet API specification, I can't manage this, think it's is running at most 20 threads concurrently. Each such a thread calls sendMessage(). 2. I set up initialSrvrInstance to 2, maxSrvrInstance to 35 Although I didn't change default maxClientInstance value, max number of client connections is 25. I see it in AppServer status after testing. Number of my client connections is limited when I run both java client and app server in State-free mode. It exactly equals to sessionPoolSize (25) Dmitry Shebeko, Banking Information Systems (http://www.bis.ru/eng/)Continue reading...