Return-Path: Delivered-To: apmail-commons-issues-archive@locus.apache.org Received: (qmail 14118 invoked from network); 26 Apr 2008 17:34:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Apr 2008 17:34:32 -0000 Received: (qmail 63840 invoked by uid 500); 26 Apr 2008 17:34:32 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 63761 invoked by uid 500); 26 Apr 2008 17:34:32 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 63750 invoked by uid 99); 26 Apr 2008 17:34:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Apr 2008 10:34:32 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Apr 2008 17:33:47 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id B7A65234C113 for ; Sat, 26 Apr 2008 10:30:55 -0700 (PDT) Message-ID: <1791099377.1209231055750.JavaMail.jira@brutus> Date: Sat, 26 Apr 2008 10:30:55 -0700 (PDT) From: "luc willems (JIRA)" To: issues@commons.apache.org Subject: [jira] Closed: (SCXML-65) NullPointer exceptions during triggerEvent In-Reply-To: <2853700.1201380274745.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/SCXML-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luc willems closed SCXML-65. ---------------------------- Resolution: Fixed tested with my linux (opensuse 10.3) and Solaris 10. fixed in upcoming 0.8 release thanks > NullPointer exceptions during triggerEvent > ------------------------------------------ > > Key: SCXML-65 > URL: https://issues.apache.org/jira/browse/SCXML-65 > 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 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. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.