Hi. I found some bugs in stomp transport: CommandParser.java:41 in.readline() can return null -> possible NullPointerException
HeaderParser.java:48 the same - in.readline() can return null -> possible NullPointerException I'm getting these nullpointers when unplugging cable from the client (failover test) - stream returns null when connection is closed (according to DataInput javadoc). After that you have to restart broker to get stomp working - not very nice :-(. Can you please fix that? Generally it would be nice if you test how the Stomp transport behaves in unerliable networks. O maybe I can contribute to the Stomp transport? -- View this message in context: http://www.nabble.com/Bugs-in-Stomp-transport-t1562088.html#a4242326 Sent from the ActiveMQ - User forum at Nabble.com.
