11 Replies Latest reply on Sep 22, 2003 12:03 PM by chrise

    Some WARN and a ERROR , when start server, why??

    bluedino Newbie

      Hi,friends.

      When I first start the JBoss, execute the "run.bat", some WARN and a ERROR occured.
      Will somebody tell me what happened and how to get it?

      Thank you!

      17:33:05,359 WARN [MainDeployer] The manifest entry in file:/D:/JBoss 3.2.0/server/all/deploy/jboss-net.sar/commons-logging.jar references URL file:/D:/JBoss 3.2.0/server/all/deploy/jboss-net.sar/log4j.jar which could not be opened, entry ignored
      17:33:05,375 WARN [MainDeployer] The manifest entry in file:/D:/JBoss 3.2.0/server/all/deploy/jboss-net.sar/commons-logging.jar references URL file:/D:/JBoss 3.2.0/server/all/deploy/jboss-net.sar/log4j-core.jar which could not be opened, entry ignored
      17:33:18,062 WARN [MainDeployer] The manifest entry in file:/D:/JBoss 3.2.0/server/all/deploy/jbossweb-tomcat.sar/commons-logging.jar references URL file:/D:/JBoss 3.2.0/server/all/deploy/jbossweb-tomcat.sar/log4j.jar which could not be opened, entry ignored
      17:33:18,062 WARN [MainDeployer] The manifest entry in file:/D:/JBoss 3.2.0/server/all/deploy/jbossweb-tomcat.sar/commons-logging.jar references URL file:/D:/JBoss 3.2.0/server/all/deploy/jbossweb-tomcat.sar/log4j-core.jar which could not be opened, entry ignored
      17:33:18,531 WARN [MainDeployer] The manifest entry in file:/D:/JBoss 3.2.0/server/all/deploy/jbossweb-tomcat.sar/tomcat-jk2.jar references URL file:/D:/JBoss 3.2.0/server/all/deploy/jbossweb-tomcat.sar/workers.jar which could not be opened, entry ignored
      17:33:18,531 WARN [MainDeployer] The manifest entry in file:/D:/JBoss 3.2.0/server/all/deploy/jbossweb-tomcat.sar/tomcat-jk2.jar references URL file:/D:/JBoss 3.2.0/server/all/deploy/classes/ which could not be opened, entry ignored
      17:33:18,546 WARN [MainDeployer] The manifest entry in file:/D:/JBoss 3.2.0/server/all/deploy/jbossweb-tomcat.sar/tomcat-jk2.jar references URL file:/D:/JBoss 3.2.0/server/all/deploy/jbossweb-tomcat.sar/log4j.jar which could not be opened, entry ignored
      17:33:19,500 WARN [MainDeployer] The manifest entry in file:/D:/JBoss 3.2.0/server/all/deploy/jbossweb-tomcat.sar/tomcat-util.jar references URL file:/D:/JBoss 3.2.0/server/all/deploy/jbossweb-tomcat.sar/log4j.jar which could not be opened, entry ignored
      17:33:19,500 WARN [MainDeployer] The manifest entry in file:/D:/JBoss 3.2.0/server/all/deploy/jbossweb-tomcat.sar/tomcat-util.jar references URL file:/D:/JBoss 3.2.0/server/all/deploy/jbossweb-tomcat.sar/log4j-core.jar which could not be opened, entry ignored
      17:33:19,500 WARN [MainDeployer] The manifest entry in file:/D:/JBoss 3.2.0/server/all/deploy/jbossweb-tomcat.sar/tomcat-util.jar references URL file:/D:/JBoss 3.2.0/server/all/deploy/jbossweb-tomcat.sar/mx4j.jar which could not be opened, entry ignored
      17:33:20,265 WARN [MainDeployer] The manifest entry in file:/D:/JBoss 3.2.0/server/all/deploy/jbossweb-tomcat.sar/bootstrap.jar references URL file:/D:/JBoss 3.2.0/server/all/deploy/jbossweb-tomcat.sar/commons-daemon.jar which could not be opened, entry ignored
      17:33:22,265 WARN [JkMain] No properties file found D:\JBoss 3.2.0\server\all\tmp\deploy\server\all\deploy\conf\jk2.properties
      17:33:28,953 WARN [ClassLoadingTask] Duplicate class found: org.jboss.jmx.connector.invoker.InvokerAdaptorService
      Current CS: (file:/D:/JBoss 3.2.0/server/all/deploy/jmx-invoker-adaptor-server.sar/ <no certificates>)
      Duplicate CS: (file:/D:/JBoss 3.2.0/server/all/tmp/deploy/server/all/deploy/jmx-ejb-connector-server.sar/32.jmx-ejb-connector-server.sar <no certificates>)
      17:33:34,625 WARN [ServiceController] Problem creating service jboss:service=HAJNDI
      java.lang.NoClassDefFoundError: gnu/regexp/UncheckedRE
      at javax.management.MatchQueryExp.(MatchQueryExp.java:117)
      at javax.management.Query.match(Query.java:268)
      at org.jboss.ha.jndi.HANamingService.findHAPartitionWithName(HANamingService.java:428)
      at org.jboss.ha.jndi.HANamingService.createService(HANamingService.java:279)
      at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:158)
      at sun.reflect.GeneratedMethodAccessor53.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:966)
      at $Proxy11.create(Unknown Source)
      at org.jboss.system.ServiceController.create(ServiceController.java:310)
      at org.jboss.system.ServiceController.create(ServiceController.java:243)
      at org.jboss.system.ServiceController.create(ServiceController.java:331)
      at org.jboss.system.ServiceController.create(ServiceController.java:243)
      at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy5.create(Unknown Source)
      at org.jboss.deployment.SARDeployer.create(SARDeployer.java:208)
      at org.jboss.deployment.MainDeployer.create(MainDeployer.java:784)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:639)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:613)
      at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy7.deploy(Unknown Source)
      at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:280)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:421)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:200)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:273)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
      at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:966)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:392)
      at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy5.start(Unknown Source)
      at org.jboss.deployment.SARDeployer.start(SARDeployer.java:242)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:613)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:597)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy6.deploy(Unknown Source)
      at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:361)
      at org.jboss.system.server.ServerImpl.start(ServerImpl.java:268)
      at org.jboss.Main.boot(Main.java:156)
      at org.jboss.Main$1.run(Main.java:394)
      at java.lang.Thread.run(Thread.java:536)
      17:33:53,578 WARN [WrappedConnection] Closing a statement you left open, please do your own housekeeping
      17:33:53,578 WARN [WrappedConnection] Closing a statement you left open, please do your own housekeeping

      17:34:00,750 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
      Cause: Incomplete Deployment listing:
      Packages waiting for a deployer:

      Incompletely deployed packages:

      MBeans waiting for classes:

      MBeans waiting for other MBeans:
      [ObjectName: jboss:service=HAJNDI
      state: FAILED
      I Depend On: jboss:service=DefaultPartition

      Depends On Me: java.lang.NoClassDefFoundError: gnu/regexp/UncheckedRE]

        • 1. Re: Some WARN and a ERROR , when start server, why??
          Juha Lindfors Master

          Do you have anything in your jre/lib/ext? (like a regexp lib or sumfin)?

          • 2. Re: Some WARN and a ERROR , when start server, why??
            bluedino Newbie

            I use JDK 1.4.1-rc.

            There are 4 jar files in jre/lib/ext:
            dnsns.jar
            ldapsec.jar
            localedata.jar
            sunjce_provider.jar

            Will you tell me what I should do next??

            • 3. Re: Some WARN and a ERROR , when start server, why??
              bluedino Newbie

              I use JDK 1.4.1-rc.

              There are 4 jar files in jre/lib/ext:
              dnsns.jar
              ldapsec.jar
              localedata.jar
              sunjce_provider.jar

              Will you tell me what I should do next??

              • 4. Re: Some WARN and a ERROR , when start server, why??
                bluedino Newbie

                I use JDK1.4.1-rc.

                There are 4 jar files in jre/lib/ext:
                dnsns.jar
                ldapsec.jar
                localedata.jar
                sunjce_provider.jar

                Would you tell me what I should do next?

                • 5. Re: Some WARN and a ERROR , when start server, why??
                  Jon Barnett Master

                  Try installing JBoss in a directory path that has no spaces in it. Certain Java services (like JNDI and RMI) are sensitive to this. I notice you have "JBoss 3.2.0" as a directory. Try "JBoss-3.2.0" or just "JBoss3.2.0".

                  See if that helps anyway. Don't have your JDK in a directory path that contains spaces either.

                  • 6. Re: Some WARN and a ERROR , when start server, why??
                    arabin Novice

                    I am having the same type of problems.

                    I am using j2sdk1.4.2_01 directory for java installation. My jboss directory name is jboss-3.2.2RC3-install (also no spaces).
                    THe contents of my jre/lib/ext directory is the same. And the messages I am getting are the following:

                    09:21:51,953 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.2.2RC3-
                    install/server/default/deploy/jbossweb-tomcat41.sar/tomcat-jk2.jar references UR
                    L file:/C:/jboss-3.2.2RC3-install/server/default/deploy/jbossweb-tomcat41.sar/wo
                    rkers.jar which could not be opened, entry ignored
                    09:21:51,953 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.2.2RC3-
                    install/server/default/deploy/jbossweb-tomcat41.sar/tomcat-jk2.jar references UR
                    L file:/C:/jboss-3.2.2RC3-install/server/default/deploy/classes/ which could not
                    be opened, entry ignored
                    09:21:51,968 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.2.2RC3-
                    install/server/default/deploy/jbossweb-tomcat41.sar/tomcat-jk2.jar references UR
                    L file:/C:/jboss-3.2.2RC3-install/server/default/deploy/jbossweb-tomcat41.sar/lo
                    g4j.jar which could not be opened, entry ignored
                    09:21:52,015 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.2.2RC3-
                    install/server/default/deploy/jbossweb-tomcat41.sar/bootstrap.jar references URL
                    file:/C:/jboss-3.2.2RC3-install/server/default/deploy/jbossweb-tomcat41.sar/com
                    mons-daemon.jar which could not be opened, entry ignored
                    09:21:52,265 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.2.2RC3-
                    install/server/default/deploy/jbossweb-tomcat41.sar/ant.jar references URL file:
                    /C:/jboss-3.2.2RC3-install/server/default/deploy/jbossweb-tomcat41.sar/xml-apis.
                    jar which could not be opened, entry ignored
                    09:21:52,265 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.2.2RC3-
                    install/server/default/deploy/jbossweb-tomcat41.sar/ant.jar references URL file:
                    /C:/jboss-3.2.2RC3-install/server/default/deploy/jbossweb-tomcat41.sar/xercesImp
                    l.jar which could not be opened, entry ignored
                    09:21:52,265 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.2.2RC3-
                    install/server/default/deploy/jbossweb-tomcat41.sar/ant.jar references URL file:
                    /C:/jboss-3.2.2RC3-install/server/default/deploy/jbossweb-tomcat41.sar/optional.
                    jar which could not be opened, entry ignored
                    09:21:52,265 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.2.2RC3-
                    install/server/default/deploy/jbossweb-tomcat41.sar/ant.jar references URL file:
                    /C:/jboss-3.2.2RC3-install/server/default/deploy/jbossweb-tomcat41.sar/xalan.jar
                    which could not be opened, entry ignored
                    09:21:52,296 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.2.2RC3-
                    install/server/default/deploy/jbossweb-tomcat41.sar/commons-logging.jar referenc
                    es URL file:/C:/jboss-3.2.2RC3-install/server/default/deploy/jbossweb-tomcat41.s
                    ar/log4j.jar which could not be opened, entry ignored
                    09:21:52,296 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.2.2RC3-
                    install/server/default/deploy/jbossweb-tomcat41.sar/commons-logging.jar referenc
                    es URL file:/C:/jboss-3.2.2RC3-install/server/default/deploy/jbossweb-tomcat41.s
                    ar/log4j-core.jar which could not be opened, entry ignored
                    09:21:52,515 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.2.2RC3-
                    install/server/default/deploy/jbossweb-tomcat41.sar/tomcat-util.jar references U
                    RL file:/C:/jboss-3.2.2RC3-install/server/default/deploy/jbossweb-tomcat41.sar/l
                    og4j.jar which could not be opened, entry ignored
                    09:21:52,515 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.2.2RC3-
                    install/server/default/deploy/jbossweb-tomcat41.sar/tomcat-util.jar references U
                    RL file:/C:/jboss-3.2.2RC3-install/server/default/deploy/jbossweb-tomcat41.sar/l
                    og4j-core.jar which could not be opened, entry ignored
                    09:21:52,515 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.2.2RC3-
                    install/server/default/deploy/jbossweb-tomcat41.sar/tomcat-util.jar references U
                    RL file:/C:/jboss-3.2.2RC3-install/server/default/deploy/jbossweb-tomcat41.sar/m
                    x4j.jar which could not be opened, entry ignored

                    I checked the files, and they are not really there (the ones for which the complaints are about).

                    Any ideas?

                    • 7. Re: Some WARN and a ERROR , when start server, why??
                      arabin Novice

                      I just do not have any errors, only warnings. Is that OK?

                      • 9. Re: Some WARN and a ERROR , when start server, why??
                        chrise Newbie

                        It seems that the files for which a warning apears are missing in the directory deploy/jbossweb-tomcat41.sar. I use the 3.2.2RC4 and the missing files (.jar) are: log4j, log4j-core, mx4j, xml-apis, xercesIml, optional, xalan, workers.
                        Does anybody know why this files are missing?

                        • 10. Re: Some WARN and a ERROR , when start server, why??
                          Juha Lindfors Master

                          These libs are already in the JBoss lib.

                          -- Juha

                          • 11. Re: Some WARN and a ERROR , when start server, why??
                            chrise Newbie

                            Ok, thanks.
                            I've found the files. Just wondered about the warning mesage.