Possible race condition related to Object#send
----------------------------------------------

                 Key: JRUBY-941
                 URL: http://jira.codehaus.org/browse/JRUBY-941
             Project: JRuby
          Issue Type: Bug
          Components: Core Classes/Modules
    Affects Versions: JRuby 0.9.9
         Environment: Mac OS X 10.4.9 (Intel)
Java 1.5.0_07
Grinder 3.0 beta33
            Reporter: Paul Carey
         Attachments: jrubygrinder.tar

Firstly, a caveat, this may not be a JRuby issue - it may simply be caused by 
code I've written that's not threadsafe.

When running loadtests concurrently via The Grinder, the following is 
occasionally (but fairly consistently) thrown after invoking Object#send.

Caused by: org.jruby.exceptions.RaiseException: instrument_test_internet is not 
a symbol 
at 
org.jruby.exceptions.JumpException.originalFillInStackTrace(JumpException.java:116)
 
at org.jruby.exceptions.RaiseException.fillInStackTrace(RaiseException.java:134)
 ...
at org.jruby.javasupport.Java$1.invoke(Java.java:595)

I've never seen this error when running tests serially. 

It makes little sense to me that a method is run successfully on most 
invocations, but that some invocations result in the above error.

The source isn't large, but it is spread across a bunch of different files. 
Simply untar the attached jrubygrinder.tar anywhere, modify 
./bin/set_grinder_env.sh as necessary (I believe GRINDERPROPERTIES needs to be 
absolute), run ./bin/compile.sh and ./bin/start_agent.sh. To modify the number 
of threads simply modify grinder.threads in ./etc/grinder.properties. The entry 
point is
loadtestproxy.py. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to