- Hot deployments are not working on the JBoss EAP instances. How can I establish the likely root cause of the problem?
- Sometimes when we deploy a new application (e.g. an EAR including JSP), the JSPs are not made available and old ones, from the previous version of the EAR, are kept.
For example : we have a servlet S, deployed in JBoss, using field F in a class C, all included in an EAR v1. We do upgrade the EAR with v2 where field F does not exist anymore and servlet S is of course not using it anymore. When we are accessing the servlet it still tries to access field F which is no longer available. Thus, the class C has been updated but not the servlet S... while they both are in the same EAR. Stopping and restarting the server has no effect.
- To deploy new version of application, we copy new WAR into deploy folder of the JBoss server and restart the server. This works most of time, but once we found that after restart, the new WAR does not get loaded or worse, the classloader loads some classes from old WAR and other from new WAR. We suspect that it is due to JBOSS not being not shutdown correctly as a result the $SERVER_CONF/tmp/deploy/ directory (where JBOSS normally uncompress WAR/EAR files when deploying) is not cleaned.
- JBoss Enterprise Application Platform (EAP)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.