Running JBoss 4.0.5 takes 15 minutes, deploying one war file

Question

This JBoss instance deploys several military files. The rest of the JBoss launch takes about 5 minutes or less. But when it falls into one specific war file, the launch simply freezes without further output to the jboss log. He waits there for about 15 minutes, and then the war suddenly begins. The rest of the JBoss launch is then perfect.

What do I want to know, what steps do you recommend me to take to diagnose the cause of this condition?

It is not possible to upgrade this site to a newer version of JBoss or java (currently 1.5.0.7). It runs on 32-bit CentOS 5.3 Linux on three xen virtual servers in a load-balanced configuration. This code is common to all three servers through the nfs share. The same problem was noticed, however, when 3 servers were physical and the code was local to each server. The servers have 2 processors, 4 GB of operational servers.

Like FYI, the wars that are deployed in this instance of JBoss are actually blown up wars contained in the directories in the deployment directory.

Answer 1

Most likely, jBoss unpacks the war file into the tmp directory. It will take some time by car with a slow drive or a big war. Try deploying it to the deployment directory. Here's a wiki on the topic , but in the short version, a directory is created with the name of the war, including .war at the end, and unzip the contents into it. It will be something like %JBOSS_HOME%\server\<instance>\deploy\<war_file>.war .

Answer 2

What I want to know, what steps do you recommend that I diagnose the cause of this condition?

First of all, 15 minutes is a typical latency, perhaps an attempt to access a network resource.

• 1st strace -p pid to find out what the server is doing (system calls)

• 2nd create some dumps of a stream during idle time to find out where it stuck.

• 3rd check $ JBOSS_HOME/bin/run.conf for JAVA_OPTS for weird changes.