5 Replies Latest reply on Jun 7, 2010 2:04 PM by peterj

    In windows 7, JBoss 4.2.0 startup failed

      I am getting error:

      12:19:15,649 WARN  [Catalina] Catalina.start using C:\jboss-4.2.0.GA\server\abc\tmp\server5422489394033096524.xml:
      java.lang.NullPointerException
      at org.apache.tomcat.util.digester.Digester.fatalError(Digester.java:1473)
          at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
          at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
          at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
          at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
          at org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(Unknown Source)
          at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
          at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
          at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
          at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
          at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
          at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
          at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1562)
          at org.apache.catalina.startup.Catalina.load(Catalina.java:504)
          at org.apache.catalina.startup.Catalina.start(Catalina.java:558)
          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:592)

       

       

       

      The C:\jboss-4.2.0.GA\server\abc\tmp\server5422489394033096524.xml file only contains xml header

      <?xml version="1.0" encoding="UTF-8"?>

       

      It used to be working in XP, after I copied everything to Windows7 and switch to 64 bit it failed to start.

       

      Any suggestion?

       

      Thanks.

        • 1. Re: In windows 7, JBoss 4.2.0 startup failed
          saltnlight5

          Files under tmp are auto generated by the server at runtime, and they shouldn't needed to restart the previous working jboss server. So would I would try removing tmp directory and have a clean restart of the jboss to see.

          • 2. Re: In windows 7, JBoss 4.2.0 startup failed

            Rolling to 64bit OS's can have adverse effects on some programs, and not only did you roll to a 64bit but a new OS base (XP to Win7).  If doing the fresh restart of the server, I would recommend doing a reinstall of JBoss, some things might not have been properly updated when you made the big switch.

             

            Also, follow the stack trace, it's there for a reason, and your help.  Apache seems to be kicking an XML error, so it might not even be a problem with JBoss itself.  The error doesn't even touch any of the JBoss methods/instances/packages so you might be having a problem with tomcat/apache and not JBoss at all.  Further into that, it looks like tomcat isn't getting a correct XML file, either there's a processing error in tomcat itself or it is receiving a bad file from JBoss, I would also look into that.

             

            Just some suggestions to look into.

            • 3. Re: In windows 7, JBoss 4.2.0 startup failed

              Yes, I have removed tmp directory and restart. The behavior is the same.

              • 4. Re: In windows 7, JBoss 4.2.0 startup failed

                Seems I need to do a fresh installation of JBoss on 64 bit machine.

                 

                The xml file appears working in XP environment.

                 

                Thanks.

                • 5. Re: In windows 7, JBoss 4.2.0 startup failed
                  peterj
                  Seems I need to do a fresh installation of JBoss on 64 bit machine.

                  Does this mean that your reinstalled JBoss AS and that it is now working?