3 Replies Latest reply on Oct 27, 2004 10:37 AM by Kalyan

    JBOSS start-up problem

    Tripp Bishop Newbie

      Howdy all. We recently moved our JBOSS application server onto a new box. We literally copied the jboss directory and all of its contents. We noticed the following stack trace when starting up JBOSS:

      2004-10-21 13:21:11,782 WARN [org.jboss.ejb.EjbModule] Could not load the org.j
      boss.resource.connectionmanager.CachedConnectionInterceptor interceptor for this
      container
      java.lang.ClassNotFoundException: org.jboss.resource.connectionmanager.CachedCon
      nectionInterceptor
      at java.net.URLClassLoader.findClass(URLClassLoader.java(Compiled Code))
      at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code))
      at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code))
      at org.jboss.ejb.EjbModule.addInterceptors(EjbModule.java:803)
      at org.jboss.ejb.EjbModule.initializeContainer(EjbModule.java:690)
      at org.jboss.ejb.EjbModule.createStatelessSessionContainer(EjbModule.jav
      a:494)
      at org.jboss.ejb.EjbModule.createContain ...


      And so forth. We finally tracked the class
      org.jboss.resource.connectionmanager.CachedConnectionInterceptor down in the jboss-jca.sar. We also noticed that in the server.log it appears that this sar is loaded AFTER our code. Later, JBOSS reloads this SAR file but throws errors complaining about things that are already loaded.

      One difference we noticed is that on our development server the jboss-jca.sar is one of the first things to be loaded. Is there a way to specify the order of things during the loading process?

      Cheers,

      Tripp

        • 1. Re: JBOSS start-up problem
          Kalyan Newbie

          You could probably use URLDeploymentSorter in your conf/jboss-service.xml file and make your jboss-jca.sar file get deployed before anyother services are deployed.

          For example:

          <attribute name="URLComparator">org.jboss.deployment.scanner.PrefixDeploymentSorter</attribute>
          
          <attribute name="URLs">
          1.deploy/jboss-jca.sar
          </attribute>
          


          HTH,
          Kalyan.


          • 2. Re: JBOSS start-up problem
            Thomas Krug Newbie

            Hi,

            I don't think using the PrefixDeploymentSorter would be the best way since SAR's are the first to be deployed when using the default DeploymentSorter.

            What kind of application (SAR, EAR, JAR....) are you using. Does it work if you move your package from the /deploy folder and back after JBoss started up?

            Thomas

            • 3. Re: JBOSS start-up problem
              Kalyan Newbie

              Why can't a SAR be deployed with PrefixDeploymentSorter? I don't see any reason for not employing this technique.

              From what you say (or from the comments in jboss-service.xml), it appears that, SARs should get deployed first. But from the exception that's mentioned, it shows that the SARs are not getting deployed. So, that would mean that DeploymentSorter isn't functioning properly.

              Kalyan