Susan Javurek added a comment - 28/Oct/11 04:42 PM

<transportConnector name="ws" uri="ws://localhost:61618/stomp"/>

<!-- check connection/disconnection -->
  <!-- FAILS -->
  <script src="unit/connection.js"></script>

  <!-- check send/receive messages -->
  <!-- FAILS -->
  <!--script src="unit/message.js"></script-->
  <script src="unit/message.js"></script>

Susan Javurek added a comment - 28/Oct/11 04:42 PM To reproduce this error, please complete the following steps: 1. Download the attached unix tarball (downloaded from: https://github.com/jmesnil/stomp-websocket) 2. Add a web socket transport to your broker: 3. If you changed the IP in step 2, update config file: jmesnil-stomp-websocket-ace6be7/test/unit/config.js Accordingly. I used default username and password as well. 4. This test runs loads of tests but alls you really need to see is the simple connection to cause the error. As such, I commented most of them out in the attached tar file: jmesnil-stomp-websocket-ace6be7/test/index.html Rest of tests are commented out. 5. Using FireFox 7.0.1 or Google Chrome 15.0.874.106, open the file: file:///Users/sjavurek/Fuse/SRs/cern/dev-3520/jmesnil-stomp-websocket-ace6be7/test/index.html In the broker log, you will see the Null Pointer error. 6. Open the same file in Safari (Version 5.1 (6534.50)), no Null pointer. I also spotted this stomple client https://github.com/krukow/stomple which uses hornetq. It has the same problems in these browsers. Hope that helps. Please let me know if you need anything else. Kindest regards, Susan

Dave Stanley added a comment - 25/Nov/11 04:03 PM

Dave Stanley added a comment - 25/Nov/11 04:03 PM Fixed in 5.6, we cannot backport as change is too disruptive to codebase.