Classloader conflicts ActiveMQ 5.3.0/Spring 2.5.6 and Spring 3.0.3 in JBoss-EAP

Solution Unverified - Updated -

Issue

We are using JBoss 5.1 and an application that uses Active MQ 5.3.0 adapter (containing Spring 2.5.6, and deployed as separate RAR). The application itself uses Spring 3.0.3.Now we experience that as soon as the application tries to load classes from Spring, JBoss loads classes from the Active MQ adapter, and therefore the wrong classes, leading to (obvious) problems.How can we configure the classloaders that there are no conflicts?

The application should first try to load the classes from the jar libs contained in the application ear. Upgrade Active MQ adapter is no option.

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 5.1
  • ActiveMQ
    • 5.3.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In