Uploaded image for project: 'Commons SCXML'
  1. Commons SCXML
  2. SCXML-65

NullPointer exceptions during triggerEvent

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.7
    • 0.8
    • None
    • Linux opensuse 10.2 & Sun Solaris 10
      1.5.x java

    Description

      i'm using SCXML state machines in a load generation tool. this tool simulates a client connected to a server.
      the SCXML script used custom actions to send a request using a HTTP based protocol.
      the HTTP response is transformed into a event and inserted into the SCXML script using triggerEvent().
      each SCML executor has 1 dedicated http connection. i'm using around 2 to 10000 clients depending on the
      test scenario's.

      During execution of the scripts a get sporatic nullpointer exceptions. this DOESN'T happen all the time , it is hard to reproduce but when it happens ALL clients have the same problem. resetting the SCXML exector doesn't help

      2008-01-24 14:33:35,593|scxml-1-88|ERROR|SCXMLUser.triggerEvents(181)|9|Current events: events(TriggerEvent

      {name=wv.status,type=3}

      ,TriggerEvent

      {name=wv.ok,type=3}

      )
      2008-01-24 14:33:35,594|scxml-1-88|ERROR|SCXMLUser.triggerEvents(182)|9|error scxml event trigger: null
      java.lang.NullPointerException
      at org.apache.commons.scxml.semantics.SCXMLSemanticsImpl.seedTargetSet(SCXMLSemanticsImpl.java:493)
      at org.apache.commons.scxml.semantics.SCXMLSemanticsImpl.followTransitions(SCXMLSemanticsImpl.java:652)
      at org.apache.commons.scxml.SCXMLExecutor.triggerEvents(SCXMLExecutor.java:127)
      at com.nsn.loadtool.scxml.SCXMLUser.triggerEvents(SCXMLUser.java:164)
      at com.nsn.loadtool.scxml.SCXMLAsyncExecutor$SCXMLWorker.run(SCXMLAsyncExecutor.java:101)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
      at java.lang.Thread.run(Thread.java:595)

      all event triggering is done in a way that only 1 thread can trigger a event.

      Attachments

        Activity

          People

            Unassigned Unassigned
            willems.luc@pandora.be luc willems
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: