top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

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

+1 vote
267 views

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.

posted Jul 5, 2013 by anonymous

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

Similar Questions
0 votes
Application Deployment in Tomcat 7.X

We are using tomcat 7.X for our project. So far we deploy only one application in tomcat.

Now we are planning to deploy one more application with existing one.

There is requirement that failure of deployment of new application should not affect existing application deployment and tomcat startup. As per my understanding, If any application deployment fails, Tomcat startup will fail.

Please let us know if there is any way to start the tomcat in case of failure of one application deployment also.

+2 votes
Issue related to Deployment (Specifically Auto Deployment) in Tomcat 7

Here is the scenario

We have a build process setup from Jenkins tool to build and auto ftp the war file to the Webapps € folder of Tomcat.

In Tomcat we have deployed the SailPoint IdentityIQ toll which is a 300mbwar file.

Often the IdentityIQ application will be running few Tasks which take longer duration (5-6 hours)

When the application is executing the long running taks, though the war file is placed/updated in web apps, tomcat is unable to stop the application due to task execution and we are unable to stop Tomcat as well

We are forced to kill Tomcat and re trigger the Jenkins build.

I am looking on few options to configure on the Tomcat server side to check for any Active sessions OR threads running related to the application and abort the Redeployment/Auto Deployment

Will it be possible?

0 votes
Multiple instances of Tomcat 7.0 on one server

We currently are setting a site that receives fairly heavy traffic (5000 simultaneous users). We have two physical servers.

As a general idea, is there performance to be gained by running multiple instances of Tomcat 7.0? For example, two instances on one physical server and two instances on the other physical server? Assume all are running the same webapp.

...