0 Replies Latest reply on May 2, 2003 7:58 AM by sys user

    Order matters when deploying sars?

    sys user Master

      When starting up my JBoss 3.0.7 instance, I get the following error:

      2003-05-02 15:51:13,783 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/D:/jboss/jboss-3.0.7/server/default/deploy/dl-services.sar
      2003-05-02 15:51:14,393 WARN [org.jboss.system.ServiceConfigurator] Failed to complete install
      java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.resource.connectionmanager.LocalTxConnectionManager
      at org.jboss.mx.loading.LoadMgr.beginLoadTask(LoadMgr.java:156)

      However, if I remove my dl-services.sar and restart, everything deploys correctly. I can then deploy my dl-services.sar and get my data source up and running.

      A workaround is to create a directory "dl" in my deploy dir and put the sar in there, or to rename my sar to zdl.sar. This seems to imply that the alphabetical ordering is important, which I guess is caused by a dependency problem. However, my jboss-service.xml file is copied straight from the examples in the docs folder.

      The workaround works for me, but I would like to know if this a bug, a feature, an out-dated sample, or what. Anybody have a clue?

      (Btw, I didn't get my *-ds file to work in JBoss3.2 either, probably for different reasons, thats why I'm still using 3.0.7).