null pointer when trying to start after stopped

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. JWebSocketFactory.start()
2. JWebSocketFactory.stop()
3. JWebSocketFactory.start()

What is the expected output? What do you see instead?

Expect factory to start up the same as on the first start.  Instead the 
following exception happens:

java.lang.NullPointerException
        at org.jwebsocket.config.xml.JWebSocketConfigHandler.handleLoggingConfigs(JWebSocketConfigHandler.java:325)
        at org.jwebsocket.config.xml.JWebSocketConfigHandler.processConfig(JWebSocketConfigHandler.java:121)
        at org.jwebsocket.factory.JWebSocketLoader.loadConfiguration(JWebSocketLoader.java:142)
        at org.jwebsocket.factory.JWebSocketLoader.initialize(JWebSocketLoader.java:59)
        at org.jwebsocket.factory.JWebSocketFactory.start(JWebSocketFactory.java:41)

What version of the product are you using? On what operating system?

JWebSocket 0.9.5 on Mac OS X 10.6.4.

Please provide any additional information below.

Looking at the source it appears that the "handlerContext" map is constructed 
via static initializer, then nulled out in "processConfig".  Seems like 
"processConfig" should construct the "handlerContext", since it nulling it out 
when done.

Original issue reported on code.google.com by deniswb...@gmail.com on 2 Jul 2010 at 4:42

GoogleCodeExporter commented 8 years ago

Original comment by mailtopu...@gmail.com on 7 Jul 2010 at 1:14

Changed state: Started

GoogleCodeExporter commented 8 years ago

Original comment by mailtopu...@gmail.com on 7 Jul 2010 at 1:14

GoogleCodeExporter commented 8 years ago

fixed to not null out the handlerContext

Original comment by mailtopu...@gmail.com on 11 Jul 2010 at 5:07

Changed state: Fixed

yrift / jwebsocket

null pointer when trying to start after stopped #23