top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Tomcat: Strange behaviour when redeploying

+4 votes
263 views

Ive come into a strange problem using tomcat with one of our WAR file.The application works as a charm, but when using the manager to redeploy it, roughly one time out of two, the heap size explodes:

Please note that the _used_ heap does not - according to JVisualVM anyway. After that, everything hangs, and the tomcat stops responding, with CPU usage ranging from 60 to 100%. Also, this issue has been reproduced on several Tomcat version ranging from 7.0.32 to 8.0-RC5, and on several machines (all Windows though).

Could anyone direct me to the clues to look for?

posted Oct 25, 2013 by Amit Parthsarthi

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
0 votes
Tomcat: Different behaviour when start inside Eclipse

When I start the Tomcat 7 by invoking startup.sh via gnome-terminal I can reach the administration console while browsing localhost:8080. But when I start the same Tomcat inside the Eclipse although my web application is working properly when I browse localhost:8080/my_application/index.html, I get error 404 when I try browse localhost:8080. What is the difference about start process between Eclipse and startup.sh?

+2 votes
java.net.SocketException: "Permission denied": connect, when running Tomcat 7 as a windows service

I'm receiving the following exception:

java.net.SocketException: "Permission denied": connect

when instantiating a Socket from a servlet:

final Socket smtpSocket = new Socket(mailTransportHost, mailTransportPort);

This application was running as a service under Windows Server 3003 R2 32-bits. After migrating it to Windows Server 2008 R2 64-bit, I cannot longer establish connection with the smtp server.

This only happen when running Tomcat as a service. Running as a standalone (starting it up using startup.bat) works fine. No exception instantiating Socket, emails are sent.

Environment:

 - Windows Server 2008 R2 64-bit
 - Tomcat 7.0.39
 - jdk1.6.0_33-x64
0 votes
Why do sticky sessions matter when session replication turned on in Tomcat

Setup:
- Two physical servers each running Tomcat 7.0.42
- Brocade load balancer in front

The load balancer is set to source IP persistence for 5 minutes. This time can be changed of course.

The thing I don't understand is 5 minutes or 5 hours - at then end that time limit the user can be sent to the other server and lose data stored in the session.

So why do sticky sessions matter when session replication turned on in Tomcat? Is a performance issue?

+1 vote
Expected Delay when Switching to New Version of Application Using Parallel Deployment (Tomcat 7.0.27)

For a simple web application, what is the expected delay when switching to new version of an application when using the parallel deployment process? I'm trying to do timings right now with a single Hello World JSP and sometimes there is a delay of up to 4 seconds when the new version of the application is deployed (running 5 users simultaneously using Jmeter with cookies turned off), but other times I don't see this behavior. Does anyone know if it is expected for there to be a slight hiccup in response times when the applications are deployed via parallel deployment? I understand that many applications will have initialization logic and that may cause a delay, but I'm wondering if I should expect tomcat to introduce a very small delay when switching from the old version to the new version and if so, how long should I expect that process to take.

0 votes
Memory limits for children processes when running Tomcat as service?

I have a JSF2.0 app that executes (via ProcessBuilder) an external script. This script opens PPTX via PowerPoint ActiveX object, manipulate it and save. It runs on Windows Server 2008 R2 64-bit, 4GB RAM, JDK 7.

When tomcat 7 is launched using startup.bat (with original settings), it works fine.

When tomcat runs as a service, opening the PPTX in the PowerPoint fails because of Out Of Memory error regardless Xmx settings (tomcat7w.exe).

I originally asked PowerPoint forum, but haven't get any explanation yet:
http://answers.microsoft.com/thread/37cbebf6-4003-4ab0-9295-92413aaecc2e

But as the entry point is Tomcat and the only difference between problematic and non problematic behavior is the 'service' mode, maybe there is something related in the tomcat7.exe code base. Just guessing.

Has anybody an idea why both modes behave differently?

...