This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
Hi all, We have an application deployed on JBoss 4.0.4. Some parts of the application depend on accessing some web services. We are using Apache Axis 1.4 for that. We had a need to deploy another version of a running application on the same server. After doing so, I noticed that the EJB classes are loaded in a shared class loader, which caused the web application to call the wrong EJBs. Consequently, we�ve changed the JBoss configuration to isolate EAR deployments as follows:
Then the two applications were successfully deployed on the same server. However, since then we�ve started receiving some unexpected exceptions from the server, when the application is trying to access any of the web services using the Axis client. The problem is that the exception message is not descriptive at all, and there�s no specific scenario to trigger them. When we first start up the JBoss, everything works fine. After a certain period of time, this exception happens and we have to restart the JBoss again to resolve it. The exception stack trace is as follows:
Any help about this urgent issue will be highly appreciated
Share Knowledge to gain it.<br /> <br />SCJP 1.2, SCDJWS 1.4, SCWCD 1.4, SCBCD 1.3, ICAD