NullPionterException in 7.4.1

[Yu L]

Hi,

I upgraded swiftmq from 7.4.0 to 7.4.1 on solaris. I didn't make any change to routerconfig.xml or "store" directory. When started swiftmq, got this exception:

bash-2.05$ Booting SwiftMQ 7.4.1 Production ...
... startup: Trace Swiftlet
... startup: Log Swiftlet
... startup: Threadpool Swiftlet
... startup: Timer Swiftlet
... startup: Network Swiftlet
... startup: High Availability Controller Swiftlet
SwiftMQ 7.4.1 Production is ready.
... startup: Authentication Swiftlet
... startup: Store Swiftlet (HA)
... startup: Queue Manager Swiftlet (HA)
... startup: Topic Manager Swiftlet
... startup: Management Swiftlet
... startup: XA Resource Manager Swiftlet
... startup: Routing Swiftlet (Unlimited Connections)
... startup: JNDI Swiftlet
... startup: JMS Swiftlet (XAASF)
... startup: Deploy Swiftlet
... startup: JMS Application Container Swiftlet
java.lang.Exception
        at com.swiftmq.impl.jac.standard.HotDeployContainer.a(Unknown Source)
        at com.swiftmq.impl.jac.standard.HotDeployContainer.a(Unknown Source)
        at com.swiftmq.impl.jac.standard.HotDeployContainer.<init>(Unknown Source)
        at com.swiftmq.impl.jac.standard.JACSwiftlet.bundleAdded(Unknown Source)
        at com.swiftmq.impl.jac.standard.JACSwiftlet.startup(Unknown Source)
        at com.swiftmq.swiftlet.SwiftletManager.startUpSwiftlet(Unknown Source)
        at com.swiftmq.swiftlet.SwiftletManager.startKernelSwiftlet(Unknown Source)
        at com.swiftmq.swiftlet.HASwiftletManager.stateChangedAction(Unknown Source)
        at com.swiftmq.swiftlet.HASwiftletManager.access$800(Unknown Source)
        at com.swiftmq.swiftlet.HASwiftletManager$HAAdapter.stateStandalone(Unknown So                                              urce)
        at com.swiftmq.impl.hacontroller.standard.state.StateRegistry.a(Unknown Source                                              )
        at com.swiftmq.impl.hacontroller.standard.state.StateRegistry.setCurrentState(                                              Unknown Source)
        at com.swiftmq.impl.hacontroller.standard.state.StateRegistry.activate(Unknown                                               Source)
        at com.swiftmq.impl.hacontroller.standard.HAControllerSwiftletImpl.activate(Un                                              known Source)
        at com.swiftmq.swiftlet.HASwiftletManager$8.run(Unknown Source)
com.swiftmq.swiftlet.SwiftletException
        at com.swiftmq.impl.jac.standard.JACSwiftlet.startup(Unknown Source)
        at com.swiftmq.swiftlet.SwiftletManager.startUpSwiftlet(Unknown Source)
        at com.swiftmq.swiftlet.SwiftletManager.startKernelSwiftlet(Unknown Source)
        at com.swiftmq.swiftlet.HASwiftletManager.stateChangedAction(Unknown Source)
        at com.swiftmq.swiftlet.HASwiftletManager.access$800(Unknown Source)
        at com.swiftmq.swiftlet.HASwiftletManager$HAAdapter.stateStandalone(Unknown So                                              urce)
        at com.swiftmq.impl.hacontroller.standard.state.StateRegistry.a(Unknown Source                                              )
        at com.swiftmq.impl.hacontroller.standard.state.StateRegistry.setCurrentState(                                              Unknown Source)
        at com.swiftmq.impl.hacontroller.standard.state.StateRegistry.activate(Unknown                                               Source)
        at com.swiftmq.impl.hacontroller.standard.HAControllerSwiftletImpl.activate(Un                                              known Source)
        at com.swiftmq.swiftlet.HASwiftletManager$8.run(Unknown Source)
... startup: Scheduler Swiftlet
java.lang.NullPointerException
        at java.io.StringReader.<init>(Unknown Source)
        at com.swiftmq.mgmt.XMLUtilities.createDocument(Unknown Source)
        at com.swiftmq.swiftlet.SwiftletManager.loadSwiftlet(Unknown Source)
        at com.swiftmq.swiftlet.SwiftletManager.loadExtensionSwiftlet(Unknown Source)
        at com.swiftmq.swiftlet.SwiftletDeployer.start(Unknown Source)
        at com.swiftmq.swiftlet.SwiftletDeployer$4.swiftletStarted(Unknown Source)
        at com.swiftmq.swiftlet.SwiftletManager.fireSwiftletManagerEvent(Unknown Sourc                                              e)
        at com.swiftmq.swiftlet.SwiftletManager.startUpSwiftlet(Unknown Source)
        at com.swiftmq.swiftlet.SwiftletManager.startKernelSwiftlet(Unknown Source)
        at com.swiftmq.swiftlet.HASwiftletManager.stateChangedAction(Unknown Source)
        at com.swiftmq.swiftlet.HASwiftletManager.access$800(Unknown Source)
        at com.swiftmq.swiftlet.HASwiftletManager$HAAdapter.stateStandalone(Unknown So                                              urce)
        at com.swiftmq.impl.hacontroller.standard.state.StateRegistry.a(Unknown Source                                              )
        at com.swiftmq.impl.hacontroller.standard.state.StateRegistry.setCurrentState(                                              Unknown Source)
        at com.swiftmq.impl.hacontroller.standard.state.StateRegistry.activate(Unknown                                               Source)
        at com.swiftmq.impl.hacontroller.standard.HAControllerSwiftletImpl.activate(Un                                              known Source)
        at com.swiftmq.swiftlet.HASwiftletManager$8.run(Unknown Source)
... startup: Monitor Swiftlet (HA)
+++ High Availability State: STANDALONE/STANDALONE
bash-2.05$

 
If I copied over our 7.4.0's routerconfig.xml and "store" direcotory to 7.4.1's install, I got the same exception. They all worked fine with our 7.4.0 install.

Did anybody see the similar problem? How to fix it? Thanks.

Yu

[IIT Software]

Yu L wrote:

java.lang.NullPointerException
        at java.io.StringReader.<init>(Unknown Source)
        at com.swiftmq.mgmt.XMLUtilities.createDocument(Unknown Source)

Hmm. Seems your routerconfig.xml is corrupt in some way or there is a classpath problem or both.

Did you follow the upgrade instructions? You should.

[Yu L]

Thanks for looking this. I did followed the exact upgrade instructions, so routerconfig.xml should be fine. It might be a classpath problem. Is there any new jar added or renamed in 7.4.1 from 7.4.0? Thanks.

Yu

[IIT Software]

No. Just follow the upgrade instructions. I've never seens this kind of exceptions as a result of an upgrade.