3

I have a problem concerning JBoss and class loading.

Here is the configuration I am working with. I have two instances of JBoss 4.2.3.GA on the same server. On each instance an application is running, and these applications are communicating with each other. There is an utility class, packed in both applications archives. This utility class is strictly the same in both applications.

This usually works fine, but in particular situations, I get ClassCastException. The case is the following:

A user is using a web application, which calls the application on the first JBoss instance (let's call it the application A). And application A calls the application B (on the second instance). This particular call takes several seconds to succeed.

If another user is trying to use the web application in a similar context (call to application A, which calls application B), and if this call happens during the first user call, I get systematically a ClassCastException : X cannot be cast to X (where X is my utility class, shared by both applications).

I found some information, and I deduced it was a class loading problem. Indeed, in this particular context of concurrent calls, my utility class is not loaded by the same class loader. I put a print command to see which class loader is used. In usual behavior, org.jboss.mx.loading.UnifiedClassLoader3 is used to load classes. In the particular described above, the application B seems to used a different class loader for the second user. My print command gave me the following:

WebappClassLoader
  delegate: false
  repositories:
    /WEB-INF/classes/----------> Parent Classloader:java.net.FactoryURLClassLoader@de8209

My guess is that application B return an instance of my utility class loaded by this WebappClassLoader, and application A (which is using UnifiedClassLoader3) cannot cast it.

But i don't get why the UnifiedClassLoader3 cannot be used in this case, on application B. And why is this WebappClassLoader used ?

All I know about the class loading configuration in my JBoss instances is that class loading isolation is used, the following configuration is used for both applications :

<jboss-app>
  <module-order>strict</module-order>  
  <loader-repository>applicationAorApplicationB.ear</loader-repository>
</jboss-app>

Do you have any advice to resolve this problem? How can I configure jboss class loader to avoid these class cast exception?

I precise that there is no hot deployment: I clean the server each time I deploy the applications.

halfer
  • 19,824
  • 17
  • 99
  • 186
OutOfBound
  • 1,120
  • 3
  • 19
  • 25
  • This is similar to http://stackoverflow.com/questions/14057932/javax-xml-bind-jaxbexception-class-nor-any-of-its-super-class-is-known-to-t/41526616#41526616 – John Jan 07 '17 at 21:26

1 Answers1

0

If JBoss is using different classloaders for different packages, it is actually following the behavior according to the spec. For many releases it did not do this. You can disable WAR classloader isolation. See the JBoss documentation for more information.

You can also use a variety of different methods that do not require the applications to be in the same classloader for communication, and this would make your applications more specification compliant. See this stackoverflow question for more details.

Community
  • 1
  • 1
justkt
  • 14,610
  • 8
  • 42
  • 62