Hello Chris, Thank you for your quick response.
When connecting from Tomcat to third party, we are going through a servlet code which is customized by us. We package the code into a jar file which sits on the \WEB-INF\lib folder. When connection, we create a session and connect through the application server IP address, jolt port, username and password. The third party system we connect to is a PeopleSoft ERP system. When the problem occurs, I would estimate it to be about 200 or so active sessions through just that one folder. Now, another thing I forgot to mention is, we have multiple web application folders with the same files but just different PeopleTools version to support for different clients. These are not slowing up and they have about maybe 10 - 20 sessions. Just throwing this information out there in case. Also to note again, I do not think it is the connection to the third party. While reviewing the logs, I notice when connecting to third party, it takes about 10 seconds round-trip. We write logs when it begin connection to end connection. Something is bottlenecking in the tomcat server before trying to connect. Hope this helps. Thanks, Thone -----Original Message----- From: cjder...@gmail.com [mailto:cjder...@gmail.com] On Behalf Of chris derham Sent: Monday, January 12, 2015 2:43 PM To: Tomcat Users List Subject: Re: Slow HTTP Rquest via Tomcat On 13 January 2015 at 11:38, Thone Soungpanya <thone.soungpa...@higherone.com> wrote: > Hello, > > Can anyone give some advice on what the issue may be? We have a web > application folder in Tomcat that have been slowing the http request's > connection to another third party system when there are high traffic. It > seems to be halting in the Tomcat server for about 20 - 50 seconds before > attempting to connect to the third party system. Once it tries to connect to > the third party system, the response time is only about 6 - 10 seconds which > is normal. It does not seem to be an issue at the third party's end as the > response time is quick once we get connected. > > Here are the specs that we have and additional information... > > 1) Apache Tomcat 7.0.56 > 2) JVM version 1.7 > 3) Running on Linux OS Version 2.6.32 > > Connection Flow: > 1) User submits a HTTP request from web application to Tomcat > 2) Tomcat calls Java's servlet code along with HTTP request parameters > 3) Java servlet code connects to third party system via application > server and jolt port > 4) Third party system returns requested information > > We thought it would be a session issue which we lowered the session timeout > (just for that folder) in WEB-INF folder to 5 minutes from defaulted 30 > minutes but it is still doing the same thing. > > Any advice on what it may be? Let me know if you need additional information. How does your code connect to the 3rd party? There are libraries that do this, please elaborate which you use. I recall using one, and it had a limit on the number of concurrent connections to a 3rd party. Perhaps you hit this limit? How many connections are you talking about when the problem occurs - 10s, 100s, 1000s or more? Chris > Thank you in advance! > > Thone --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
