Jboss 5.1 hot deploy failed

[retep1025]

I have multiple EJB 3.x application that we used to work correctly when we are using Jboss 4.x and we recently upgraded jboss 5.1. All the application work corretly when we start the server. But when trying to hot deploy ear, it hangs jboss 5.1 and nothing work afterward. If we shutdown the server and restarted it work perfectly. Any body have any idea what the problem is. But war are hot deploying correctly just not the ear

I see the ear file being undeploy but it just won't redeploy

Note: When we only deploy any single one ears the hot deploy works fine, but when all of the ear are deployed it fail to hot deploy and crash jboss and some time run out of heap space. It seems that it goes into infinate loop on class loading

windows xp

jboss 5.1

ear

EJB 3.X

[retep1025]

solved the problem by changing the EarClassLoaderDeployer from false to true

/jboss-5.1.0.GA/server/default/deployers/ear-deployer-jboss-beans.xml

   <bean name="EARClassLoaderDeployer" class="org.jboss.deployment.EarClassLoaderDeployer">
      <!-- A flag indicating if ear deployments should have their own scoped
         class loader to isolate their classes from other deployments.
      -->     
      <property name="isolated">true</property>
   </bean>

[vickyk]

retep1025 wrote:

solved the problem by changing the EarClassLoaderDeployer from false to true

I don't understand how setting the isolation to true would help here.

Would it be possible for you to invetigate it more and explain why such settings sorted the issue?

[retep1025]

We have about 10 ears deploy in jboss 5.1, and some of the ear shares common libs like: apache-commons etc... I think there is a bug in the hot deploy... it goes into infinate loop trying to load classes and match the already existing class already loaded in other ears.... so by setting isolation to true, we get around the bug

[vickyk]

retep1025 wrote:

We have about 10 ears deploy in jboss 5.1, and some of the ear shares common libs like: apache-commons etc... I think there is a bug in the hot deploy... it goes into infinate loop trying to load classes and match the already existing class already loaded in other ears.... so by setting isolation to true, we get around the bug

Can you please enable the logs on CL and HDScanner and paste the details here? This might help us to identify the bug if it exists as I think if this is an issue then it needs to be sorted out as it could be critical.