Deploying to linked deploy directory causes other applications to become unresponsive.
Issue
Created an e:\data\JBApps directory to keep our application war files separate from the standard JBoss deploy folder – this is not linked in windows, we have updated the JBoss configuration file (jboss-service.xml) to include the directory as part of the attribute below so any wars get picked up by JBoss
<attribute name="URLs">
deploy/,file:/E:/data/JBApps
</attribute>
As per your advice when deploying a new version we delete the WAR file from the above folder.
We then copy the new version of the WAR file into the folder.
What we have noticed is:
1. By just deploying one application all other applications become unavailable for a period and seem to restart.
2. The new version does not always start up and so we have to stop/start JBOSS.
3. Sometimes JBOSS does not stop and we have to kill process JAVA.EXE
4. Sometimes the new changes are not picked and we have to go into E:\APPS\Jboss-Inst\jboss-as\server\production\tmp\deploy and
E:\APPS\Jboss-Inst\jboss-as\server\production\work\jboss.web\localhost to delete any files relating to the application and then restart.
Environment
JBoss Enterprise Application Platform 4.3.0.GA_CP02
Java version: 1.6.0_07,Sun Microsystems Inc.
Windows 2003 5.2,x86
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
