1 2 Previous Next 18 Replies Latest reply on Nov 27, 2009 11:13 AM by André Dantas Rocha

    Struggling with jboss-classloading.xml

    André Dantas Rocha Newbie

      Hi all,

      I've be struggling with jboss-classloading.xml for about one week and really don't know even if it is possible. There is my problem (JBoss 5.1):

      1) I have a RAR that contains a lot of jars that must be exposed to other applications. Everything is working fine and after deploy I can access the classes, but my log configuration is not working (SLF4J)

      2) To sove the problem, I need to invert RAR classloader, in order to use a specific SLF4J configurarion (because JBoss has its particular one that is loaded from lib/common). My jboss-classloading.xml is:

      <classloading xmlns="urn:jboss:classloading:1.0"
       domain="IsolatedWithParentDomain"
       parent-domain="DefaultDomain"
       parent-first="false">
      </classloading>
      


      Now I can't see that classes inside RAR anymore.

      My question is: is there a way to invert classloader in RAR and continue seeing the classes?

      I've tried a lot of jboss-classloading attributes combinations, but none seams to work (ParentDomain, DefaultDomain, etc).

      Any ideas?

      Thanks,

      Andre


        • 1. Re: Struggling with jboss-classloading.xml
          Ales Justin Master

           

          "ad-rocha" wrote:

          My question is: is there a way to invert classloader in RAR and continue seeing the classes?

          Hmmm, you could try "osgi" rules.

          Import more specific version of slf4j via rar's cl requirements.
          But then you also need to properly "osgi"-ize your slf4j jar.

          You can either
          * re-package that slf4j jar to include proper jboss-classloading.xml
          * wrap slf4j jar with another jar which has proper jboss-classloading.xml

          But the problem might be that slf4j in common/lib is not exposed via "osgi" rules,
          so you would still pick up that one - you can just try or I have to properly check that.

          If it's just logging config, you can probably add some TCL filtering:
          * https://jira.jboss.org/jira/browse/JBLOGGING-30
          which could do the trick w/o any "real" cl tricks :-)

          • 2. Re: Struggling with jboss-classloading.xml
            André Dantas Rocha Newbie

            Hi Ales,

            First of all, thank you for your reply.

            Well, putting jboss-classloading.xml inside my slf4j didn´t work (I laso removed jboss-classloading.xml from RAR because of classes visibility).

            Anyway, I don't believe it is a ellegant approach and now I suppose I'm tied to JBoss SLF4J implementation :-(

            Now, I'll try TCL filter.

            Please let me know if there is another approach that I can try, because I really prefer do not changing server files...

            Thanks again,

            Andre

            • 3. Re: Struggling with jboss-classloading.xml
              Ales Justin Master

               

              "ad-rocha" wrote:

              Anyway, I don't believe it is a ellegant approach and now I suppose I'm tied to JBoss SLF4J implementation :-(

              That's as elegant as it gets. :-)
              But I think you're not doing it right.

              Try doing this.
              Create new jar, which includes this contents

              wrapper.jar
              * lib
              ** slf4j.jar
              * META-INF
              ** jboss-structure.xml
              ** jboss-classloading.xml

              where jboss-structure.xml looks like
              <structure>
               <context>
               <path name=""/>
               <metaDataPath>
               <path name="META-INF"/>
               </metaDataPath>
               <classpath>
               <path name="lib" suffixes=".jar"/>
               </classpath>
               </context>
              </structure>
              


              and jboss-classloading.xml like
              <classloading xmlns="urn:jboss:classloading:1.0">
               <capabilities>
               <module name="slf4.jar" version="2.0"/>
               </capabilities>
              </classloading>
              


              then simply have this jboss-classloading.xml in your rar
              <classloading xmlns="urn:jboss:classloading:1.0" export-all="NON_EMPTY">
               <requirements>
               <module name="slf4j.jar" from-inclusive="2.0"/>
               </requirements>
              </classloading>
              


              I might be missing some details, but let's see how far we get.


              • 4. Re: Struggling with jboss-classloading.xml
                André Dantas Rocha Newbie

                Hi Ales,

                Thanks for your help, I just sow your answer. I followEd your instructions, but I could not deploy my RAR (all jars of my RAR reside in root dir).

                Stack trace is shown below.

                Andre

                2009-11-23 09:49:23,660 WARN [org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder] (main) Error populating deployment vfszip:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/
                org.jboss.deployers.spi.DeploymentException: Unable to find class path entry ClassPathEntryImpl{path=lib suffixes=.jar} from rysys-cobol-connector-1.1.5.rar
                 at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
                 at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:188)
                 at org.jboss.deployers.structure.spi.helpers.AbstractStructureBuilder.populateContext(AbstractStructureBuilder.java:141)
                 at org.jboss.deployers.structure.spi.helpers.AbstractStructureBuilder.populateContext(AbstractStructureBuilder.java:92)
                 at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:89)
                 at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:1004)
                 at org.jboss.deployers.plugins.main.MainDeployerImpl.determineDeploymentContext(MainDeployerImpl.java:440)
                 at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:390)
                 at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:300)
                 at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.addDeployment(MainDeployerAdapter.java:86)
                 at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:61)
                 at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
                 at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
                 at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
                 at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
                 at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
                 at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
                 at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
                 at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
                 at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
                 at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
                 at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
                 at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
                 at org.jboss.Main.boot(Main.java:221)
                 at org.jboss.Main$1.run(Main.java:556)
                 at java.lang.Thread.run(Thread.java:619)
                Caused by: java.io.IOException: Child not found lib for DelegatingHandler@16662014[path=rysys-cobol-connector-1.1.5.rar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar], available children:
                
                ---- TEXT REMOVED DUE TO THE SIZE ---
                
                 at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:461)
                 at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:184)
                 ... 24 more
                


                • 5. Re: Struggling with jboss-classloading.xml
                  Ales Justin Master

                   

                  "ad-rocha" wrote:

                  [org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder] (main) Error populating deployment vfszip:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/
                  org.jboss.deployers.spi.DeploymentException: Unable to find class path entry ClassPathEntryImpl{path=lib suffixes=.jar} from rysys-cobol-connector-1.1.5.rar
                  


                  You put the jboss-structure.xml into the wrong jar.

                  • 6. Re: Struggling with jboss-classloading.xml
                    André Dantas Rocha Newbie

                    My structure is:

                    rysys-cobol-connector-1.1.5.rar
                    * META-INF
                    ** jboss-classloading.xml (references slf4j-1.5.6-wrapper.jar)
                    * slf4j-1.5.6-wrapper.jar
                    ** lib
                    *** slf4j-api-1.5.6.jar
                    ** META-INF
                    *** jboss-structure.xml
                    *** jboss-classloading.xml (references slf4j-api-1.5.6.jar)

                    Thanks,

                    Andre

                    • 7. Re: Struggling with jboss-classloading.xml
                      Ales Justin Master

                      Ah, you shouldn't deploy it all in a single rar.
                      Split it in two - rar and wrapper.jar.

                      • 8. Re: Struggling with jboss-classloading.xml
                        André Dantas Rocha Newbie

                        Hi Ales,

                        I splited the files and put both in deplor dir. Now I got this error:

                        DEPLOYMENTS MISSING DEPENDENCIES:
                         Deployment "jboss.jca:name=ra/rysys-connector,service=ConnectionFactoryBinding" is missing the following dependencies:
                         Dependency "jboss.jca:name=ra/rysys-connector,service=TxCM" (should be in state "Create", but is actually in state "Configured")
                         Deployment "jboss.jca:name=ra/rysys-connector,service=ManagedConnectionFactory" is missing the following dependencies:
                         Dependency "jboss.jca:name='rysys-cobol-connector-1.1.5.rar',service=RARDeployment" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name='rysys-cobol-connector-1.1.5.rar',service=RARDeployment' **")
                         Deployment "jboss.jca:name=ra/rysys-connector,service=ManagedConnectionPool" is missing the following dependencies:
                         Dependency "jboss.jca:name=ra/rysys-connector,service=ManagedConnectionFactory" (should be in state "Create", but is actually in state "Configured")
                         Deployment "jboss.jca:name=ra/rysys-connector,service=TxCM" is missing the following dependencies:
                         Dependency "jboss.jca:name=ra/rysys-connector,service=ManagedConnectionPool" (should be in state "Create", but is actually in state "Configured")
                         Deployment "vfszip:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/" is missing the following dependencies:
                         Dependency "<UNKNOWN vfszip:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/>" (should be in state "ClassLoader", but is actually in state "** UNRESOLVED ModuleRequirement{slf4j-1.5.6-wrapper.jar (0.0.0,?)} **")
                        
                        DEPLOYMENTS IN ERROR:
                         Deployment "<UNKNOWN vfszip:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/>" is in error due to the following reason(s): ** UNRESOLVED ModuleRequirement{slf4j-1.5.6-wrapper.jar (0.0.0,?)} **
                         Deployment "jboss.jca:name='rysys-cobol-connector-1.1.5.rar',service=RARDeployment" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name='rysys-cobol-connector-1.1.5.rar',service=RARDeployment' **
                        


                        Any idea?

                        Tnaks,

                        Andre

                        • 9. Re: Struggling with jboss-classloading.xml
                          Ales Justin Master

                          What are the contents of your jboss-classloading files?

                          • 10. Re: Struggling with jboss-classloading.xml
                            André Dantas Rocha Newbie

                            slf4j-1.5.6-wrapper.jar

                            <classloading xmlns="urn:jboss:classloading:1.0">
                             <capabilities>
                             <module name="slf4j-api-1.5.6.jar" version="2.0"/>
                             </capabilities>
                            </classloading>
                            


                            rysys-cobol-connector-1.1.5.rar
                            <classloading xmlns="urn:jboss:classloading:1.0" export-all="NON_EMPTY">
                             <requirements>
                             <module name="slf4j-1.5.6-wrapper.jar" from-inclusive="2.0"/>
                             </requirements>
                            </classloading>
                            


                            Andre

                            • 11. Re: Struggling with jboss-classloading.xml
                              Ales Justin Master

                              slf4j-api-1.5.6.jar != slf4j-1.5.6-wrapper.jar ;-)

                              • 12. Re: Struggling with jboss-classloading.xml
                                André Dantas Rocha Newbie

                                Hi Ales,

                                It did not work either. Now, the problem is because of jboss-classloading.xml inside RAR (error below).

                                Anyway, I don't think it will work, because JBoss already has a slf4j implementation in commons lib (slf4j-jboss-logging.jar), so it will never choose my log implementation (logback)...

                                I think the simpler and easy way is to configure jboss-log4j.xml according to my system :-)

                                Thanks for all your help!

                                Andre

                                2009-11-25 09:34:27,415 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Instantiated: name=jboss.jca:name='rysys-cobol-connector-1.1.5.rar',service=RARDeployment state=Described mode=Manual requiredState=Configured
                                java.lang.ClassNotFoundException: org.jboss.resource.deployers.RARDeployment from BaseClassLoader@219f32{VFSClassLoaderPolicy@15aa868{name=vfszip:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/ domain=ClassLoaderDomain@1f1cbf6{name=DefaultDomain parentPolicy=BEFORE parent=org.jboss.bootstrap.NoAnnotationURLClassLoader@7a84e4} roots=[MemoryContextHandler@15095815[path= context=vfsmemory://67113k-c08jdd-g2g0otth-1-g2g0p9b8-23 real=vfsmemory://67113k-c08jdd-g2g0otth-1-g2g0p9b8-23], DelegatingHandler@23938122[path=rysys-cobol-connector-1.1.5.rar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar], DelegatingHandler@10308773[path=rysys-cobol-connector-1.1.5.rar/aspectjrt-1.6.5.jar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/aspectjrt-1.6.5.jar], DelegatingHandler@18028343[path=rysys-cobol-connector-1.1.5.rar/avalon-framework-4.1.3.jar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/avalon-framework-4.1.3.jar], DelegatingHandler@5848910[path=rysys-cobol-connector-1.1.5.rar/commons-beanutils-1.8.0.jar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/commons-beanutils-1.8.0.jar], DelegatingHandler@21712743[path=rysys-cobol-connector-1.1.5.rar/commons-lang-2.4.jar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/commons-lang-2.4.jar], DelegatingHandler@21631386[path=rysys-cobol-connector-1.1.5.rar/commons-logging-1.1.jar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/commons-logging-1.1.jar], DelegatingHandler@29998362[path=rysys-cobol-connector-1.1.5.rar/easymbean-alpha-2.jar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/easymbean-alpha-2.jar], DelegatingHandler@27136921[path=rysys-cobol-connector-1.1.5.rar/log4j-1.2.12.jar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/log4j-1.2.12.jar], DelegatingHandler@18405633[path=rysys-cobol-connector-1.1.5.rar/logback-classic-0.9.15.jar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/logback-classic-0.9.15.jar], DelegatingHandler@5176659[path=rysys-cobol-connector-1.1.5.rar/logback-core-0.9.15.jar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/logback-core-0.9.15.jar], DelegatingHandler@31024311[path=rysys-cobol-connector-1.1.5.rar/logkit-1.0.1.jar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/logkit-1.0.1.jar], DelegatingHandler@23280573[path=rysys-cobol-connector-1.1.5.rar/oro-2.0.8.jar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/oro-2.0.8.jar], DelegatingHandler@31922664[path=rysys-cobol-connector-1.1.5.rar/rysys-cobol-1.1.5.jar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/rysys-cobol-1.1.5.jar], DelegatingHandler@22409515[path=rysys-cobol-connector-1.1.5.rar/rysys-core-1.1.5.jar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/rysys-core-1.1.5.jar], DelegatingHandler@21789768[path=rysys-cobol-connector-1.1.5.rar/rysys-utils-1.1.5.jar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/rysys-utils-1.1.5.jar], DelegatingHandler@7575855[path=rysys-cobol-connector-1.1.5.rar/slf4j-api-1.5.6.jar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/slf4j-api-1.5.6.jar], DelegatingHandler@21881611[path=rysys-cobol-connector-1.1.5.rar/ssh2-213.jar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/ssh2-213.jar], DelegatingHandler@7677284[path=rysys-cobol-connector-1.1.5.rar/xpp3_min-1.1.4c.jar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/xpp3_min-1.1.4c.jar], DelegatingHandler@15334863[path=rysys-cobol-connector-1.1.5.rar/xstream-1.3.jar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/xstream-1.3.jar]] delegates=[FilteredDelegateLoader@1653c4{delegate=VFSClassLoaderPolicy@1fcb1a{vfszip:/C:/Java/jboss-5.1.0.GA/server/default/deploy/slf4j-1.5.6-wrapper.jar/}}] exported=[ch.qos.logback.core.spi, , com.trilead.ssh2.crypto.digest, org.apache.log4j, com.thoughtworks.xstream.io.path, org.apache.log4j.lf5.config, org.apache.log4j.spi, ch.qos.logback.core, ch.qos.logback.core.joran.action, org.apache.commons.beanutils.locale.converters, org.apache.commons.beanutils.converters, br.com.codecompany.rysys.cobol.jmx, com.thoughtworks.xstream.converters.reflection, br.com.codecompany.rysys.cobol.driver, org.apache.log4j.chainsaw, META-INF.maven.br.com.codecompany.rysys-core, ch.qos.logback.core.net, com.thoughtworks.xstream.converters.collections, br.com.codecompany.rysys.cobol.function, com.thoughtworks.xstream.core, ch.qos.logback.core.rolling, com.trilead.ssh2, org.apache.avalon.framework.parameters, org.xmlpull.v1, org.apache.avalon.framework.context, br.com.codecompany.rysys.core.driver, ch.qos.logback.classic, org.aspectj.internal.lang.reflect, com.thoughtworks.xstream.io.json, ch.qos.logback.core.pattern.parser, ch.qos.logback.classic.boolex, com.trilead.ssh2.log, ch.qos.logback.classic.filter, ch.qos.logback.classic.joran, ch.qos.logback.core.helpers, com.thoughtworks.xstream.io, org.apache.commons.lang.builder, com.trilead.ssh2.transport, org.apache.commons.beanutils.locale, org.aspectj.runtime.internal.cflowstack, org.apache.commons.logging.impl, org.apache.log4j.lf5.util, org.apache.log4j.jdbc, org.apache.commons.logging, org.apache.commons.lang.enum, com.thoughtworks.xstream.io.copy, org.apache.avalon.framework.configuration, org.apache.commons.collections, com.thoughtworks.xstream.io.xml.xppdom, org.apache.avalon.framework.component, ch.qos.logback.classic.html, com.trilead.ssh2.channel, org.apache.oro.util, ch.qos.logback.classic.pattern, ch.qos.logback.core.joran.spi, org.apache.log.output.net, org.apache.commons.lang, org.slf4j.spi, ch.qos.logback.classic.net, br.com.codecompany.rysys.cobol.executor, org.apache.log4j.lf5, ch.qos.logback.classic.log4j, com.trilead.ssh2.util, org.apache.log.output.jms, org.apache.commons.lang.exception, br.com.codecompany.rysys.core.balancing, org.apache.avalon.framework.service, com.thoughtworks.xstream.alias, org.apache.commons.lang.text, META-INF.maven.ch.qos.logback.logback-classic, org.aspectj.runtime.internal, org.apache.log4j.lf5.viewer.images, ch.qos.logback.classic.turbo, com.trilead.ssh2.crypto.dh, ch.qos.logback.core.sift, org.apache.log.output.db, org.apache.log.util, ch.qos.logback.core.pattern, com.thoughtworks.xstream.core.util, org.slf4j, com.trilead.ssh2.packets, org.apache.avalon.framework, org.aspectj.internal.lang.annotation, com.thoughtworks.xstream.converters, META-INF.services, META-INF.maven.commons-beanutils.commons-beanutils, org.apache.log4j.varia, org.aspectj.runtime, org.jmanage.easymbean.impl, ch.qos.logback.core.util, org.apache.log4j.lf5.viewer.configure, ch.qos.logback.core.rolling.helper, br.com.codecompany.rysys.core.jmx.database, org.apache.oro.text, ch.qos.logback.classic.util, org.apache.avalon.framework.thread, org.apache.avalon.framework.container, ch.qos.logback.core.db.dialect, org.xmlpull.mxp1, org.apache.log.format, org.apache.commons.beanutils.expression, com.trilead.ssh2.auth, org.apache.commons.lang.mutable, org.apache.log4j.nt, br.com.codecompany.rysys.util, br.com.codecompany.rysys.core.jce, br.com.codecompany.rysys.core.cache, com.thoughtworks.xstream.io.binary, com.thoughtworks.xstream.io.xml, org.apache.log4j.xml, ch.qos.logback.core.joran.event, com.thoughtworks.xstream.mapper, br.com.codecompany.rysys.core.jmx, ch.qos.logback.core.joran, ch.qos.logback.core.boolex, META-INF.maven.com.thoughtworks.xstream.xstream, com.trilead.ssh2.sftp, org.apache.oro.io, ch.qos.logback.classic.jmx, ch.qos.logback.core.read, com.thoughtworks.xstream, org.jmanage.easymbean.annotations, br.com.codecompany.rysys.cobol.cache, org.apache.oro.text.perl, org.apache.log4j.lf5.viewer.categoryexplorer, com.thoughtworks.xstream.converters.javabean, com.trilead.ssh2.crypto, META-INF.maven.br.com.codecompany.rysys-utils, org.aspectj.lang.annotation, org.aspectj.lang.internal.lang, ch.qos.logback.classic.db, ch.qos.logback.core.filter, com.thoughtworks.xstream.converters.extended, org.apache.log.output.io.rotate, org.aspectj.lang.reflect, ch.qos.logback.classic.sift, com.trilead.ssh2.signature, org.apache.log4j.or, org.apache.commons.lang.time, org.apache.commons.lang.math, ch.qos.logback.core.status, org.apache.commons.beanutils, org.apache.log4j.net, META-INF.maven.commons-lang.commons-lang, org.apache.log4j.lf5.viewer, br.com.codecompany.rysys.core.jca.eis, org.apache.log4j.jmx, org.apache.log4j.config, org.apache.log4j.helpers, org.apache.commons.lang.enums, org.apache.oro.text.awk, com.thoughtworks.xstream.converters.basic, org.apache.log.output.io, ch.qos.logback.classic.joran.action, org.apache.log4j.or.jms, org.apache.log.filter, org.aspectj.lang, META-INF.maven.ch.qos.logback.logback-core, org.apache.avalon.framework.activity, org.slf4j.impl, org.apache.log.output, com.thoughtworks.xstream.annotations, org.slf4j.helpers, org.aspectj.runtime.reflect, com.trilead.ssh2.crypto.cipher, META-INF.maven.br.com.codecompany.rysys-cobol, br.com.codecompany.rysys.core.jca.eis.transaction, ch.qos.logback.core.db, org.apache.avalon.framework.logger, org.apache.log4j.or.sax, ch.qos.logback.classic.selector, META-INF, ch.qos.logback.core.html, org.apache.log, ch.qos.logback.core.layout, ch.qos.logback.classic.selector.servlet, org.jmanage.easymbean, META-INF.maven.org.slf4j.slf4j-api, ch.qos.logback.core.pattern.util, META-INF.maven.br.com.codecompany.rysys-cobol-connector, com.thoughtworks.xstream.persistence, org.apache.oro.text.regex, com.thoughtworks.xstream.converters.enums, ch.qos.logback.classic.spi]NON_EMPTY}}
                                 at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:448)
                                 at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
                                 at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:1213)
                                 at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:286)
                                 at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:344)
                                 at org.jboss.system.ServiceCreator.installPlainMBean(ServiceCreator.java:211)
                                 at org.jboss.system.ServiceCreator.install(ServiceCreator.java:130)
                                 at org.jboss.system.microcontainer.InstantiateAction.installAction(InstantiateAction.java:45)
                                 at org.jboss.system.microcontainer.InstantiateAction.installAction(InstantiateAction.java:37)
                                


                                • 13. Re: Struggling with jboss-classloading.xml
                                  Ales Justin Master

                                  Weird, I would expect this class to be present in DefaultDomain,
                                  which is also your domain:

                                  java.lang.ClassNotFoundException: org.jboss.resource.deployers.RARDeployment from BaseClassLoader@21
                                  9f32{VFSClassLoaderPolicy@15aa868{name=vfszip:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-co
                                  bol-connector-1.1.5.rar/ domain=ClassLoaderDomain@1f1cbf6{name=DefaultDomain parentPolicy=BEFORE par
                                  ent=org.jboss.bootstrap.NoAnnotationURLClassLoader@7a84e4}
                                  

                                  Can you go over JMX console and check in which domain this class actually lives?

                                  I'll try to mock your example ... once I find the time ...


                                  • 14. Re: Struggling with jboss-classloading.xml
                                    André Dantas Rocha Newbie

                                    Hi ales,

                                    From JMX I could see this:

                                    Regarding to RARDeployer service:
                                    Domain jboss.deployment
                                    type Component
                                    id "RARDeployer"
                                    Java Class org.jboss.deployers.structure.spi.helpers.ComponentDeploymentContext
                                    Description Management Bean.

                                    Regarding to connector:
                                    Domain jboss.deployment
                                    type Deployment
                                    id "vfszip:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/"
                                    Java Class org.jboss.deployers.vfs.plugins.structure.AbstractVFSDeploymentContext
                                    Description Management Bean.

                                    If you need more information, please let me know where (in jmx console) I can find it.

                                    Andre


                                    1 2 Previous Next