problem starting multiple JBossAS instances at boottime

[lafr]

I have a mysterious problem with JBoss AS 7.20 at a customer.

There we have 6 instances on Solaris SPARC 10 server. All in the same file system, but distinct JBOSS_HOMEs, port-offset's, ...

On reboot some of this 6 do not start successfully, sometimes 2, sometimes 1. Also different instances that fail, not always th first or the last ones.

The failure occurs in an very early while reading the standalone-...xml config file and loading the modules.

I attached a server.log starting with the failure yesterday, the successful manual start yesterday and the failure this morning.

I have no clue what's going on and what might be causing this problem. Any hint?

[ctomc]

What looks fishy is this part of stacktrace:

Caused by: java.lang.ArrayIndexOutOfBoundsException

    at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.scanData(XMLEntityScanner.java:1250) [rt.jar:1.6.0_07]

    at com.sun.org.apache.xerces.internal.impl.XMLScanner.scanComment(XMLScanner.java:756) [rt.jar:1.6.0_07]

    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanComment(XMLDocumentFragmentScannerImpl.java:1036) [rt.jar:1.6.0_07]

    at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:945) [rt.jar:1.6.0_07]

    at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) [rt.jar:1.6.0_07]

    at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) [rt.jar:1.6.0_07]

    at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:548) [rt.jar:1.6.0_07]

    at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.nextTag(XMLStreamReaderImpl.java:1219) [rt.jar:1.6.0_07]

    at org.jboss.modules.ModuleXmlParser.parseDocument(ModuleXmlParser.java:540) [jboss-modules.jar:1.1.3.GA]

    at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:288) [jboss-modules.jar:1.1.3.GA]

    at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:243) [jboss-modules.jar:1.1.3.GA]

    at org.jboss.modules.LocalModuleLoader.parseModuleInfoFile(LocalModuleLoader.java:138) [jboss-modules.jar:1.1.3.GA]

    at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:122) [jboss-modules.jar:1.1.3.GA]

    at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275) [jboss-modules.jar:1.1.3.GA]

    at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222) [jboss-modules.jar:1.1.3.GA]

    at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94) [jboss-modules.jar:1.1.3.GA]

    at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:204) [jboss-modules.jar:1.1.3.GA]

    at org.jboss.as.controller.parsing.ExtensionXml.loadModule(ExtensionXml.java:177) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]

    at org.jboss.as.controller.parsing.ExtensionXml.access$000(ExtensionXml.java:68) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]

    at org.jboss.as.controller.parsing.ExtensionXml$1.call(ExtensionXml.java:126) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]

    at org.jboss.as.controller.parsing.ExtensionXml$1.call(ExtensionXml.java:123) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]

which would point that is is using wrong parser.

Can you try with newer version of jdk, as 1.6 update 7 is extra extra old

there ware also some changes around xml parsers around update 15 if i recall correctly.

--

tomaz

[lafr]

Oh yes, there should be a newer version. I thought we already do so.

I replaced 1.6.0_07 with 1.6.0_45.

After reboot of server all 6 instances are alive.