commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar (JIRA)" <>
Subject [jira] Commented: (SCXML-65) NullPointer exceptions during triggerEvent
Date Fri, 07 Mar 2008 23:35:46 GMT


Rahul Akolkar commented on SCXML-65:

Thanks for digging into this, no worries about the delay :-)

I agree with most of your analysis. In the meantime, I had made one change that should eliminate
any issue here (the paths are now calculated at document parsing time, before any executor
instances are created). That simple change is here (though its impact is perhaps subtle):

Could you please try out the latest build from trunk (without your change, ofcourse) and see
if that fixes the problem as well? Thanks in advance.

> NullPointer exceptions during triggerEvent
> ------------------------------------------
>                 Key: SCXML-65
>                 URL:
>             Project: Commons SCXML
>          Issue Type: Bug
>    Affects Versions: 0.7
>         Environment: Linux opensuse 10.2 & Sun Solaris 10 
> 1.5.x java
>            Reporter: luc willems
>             Fix For: 0.8
> 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
> 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:
> 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(
>         at org.apache.commons.scxml.semantics.SCXMLSemanticsImpl.followTransitions(
>         at org.apache.commons.scxml.SCXMLExecutor.triggerEvents(
>         at com.nsn.loadtool.scxml.SCXMLUser.triggerEvents(
>         at com.nsn.loadtool.scxml.SCXMLAsyncExecutor$
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at
> all event triggering is done in a way that only 1 thread can trigger a event.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message