[ grinder-Bugs-3525733 ] No clear errors logged with Grinder

Bugs item #3525733, was opened at 2012-05-10 22:29
Message generated for change (Tracker Item Submitted) made by oviney
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=118598&aid=3525733&group_id=18598

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core engine
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Ouray Viney (oviney)
Assigned to: Nobody/Anonymous (nobody)
Summary: No clear errors logged with Grinder

Initial Comment:
Hi All:

I ran into an odd issue today when testing a Grinder upgrade from version 3.4 to 3.8.  I performed the upgrade, tested out a script.  During this process I noticed that the agent worker processor started up and then died (CPU spiked and then dropped back to zero).  There were no results in the console and no trace of any errors/exceptions in the logs.  So decided a good testing strategy was to roll back the Grinder version until I got some logging about what was wrong.

Here is what was showing up in the logs with Grinder version 3.8:

2012-05-09 10:23:14,465 INFO  lingrndctl-0 : The Grinder version 3.8
2012-05-09 10:23:14,470 INFO  lingrndctl-0 : Java(TM) SE Runtime Environment 1.6.0_13-b03: Java HotSpot(TM) Client VM (11.3-b02, mixed mode) on Linux i386 2.6.18-194.32.1.el5xen
2012-05-09 10:23:14,474 INFO  lingrndctl-0 : time zone is EDT (-0400)
2012-05-09 10:23:14,563 INFO  lingrndctl-0 : worker process 0 of agent number 0
2012-05-09 10:23:14,766 INFO  lingrndctl-0 : instrumentation agents: byte code transforming instrumenter for Jython 2.5; byte code transforming instrumenter for Java
2012-05-09 10:23:18,439 INFO  lingrndctl-0 : registered plug-in net.grinder.plugin.http.HTTPPlugin

I had to "roll back" all the way to Grinder 3.4 before I actually got to the root of the issue.  From the error log provided in Grinder 3.4, it was caused by a missing jar that was being referenced in my script.

I will post my script and Grinder environment details later today, don't have access to the stuff at the moment.

** Note:  **  In order to reproduce this, you should be able to take any script that uses a third party library.  In my example, I was using Jsoup (http://jsoup.org/).  Since I had recently done an upgrade, I had forgotten to add the jar to the path.  IIRC, you have two options here, 1) place a reference to the jar in the setGrinderEnv script (bat or shell) 2) add the appropriate path to the said grinder.properties to have the jars added to the class path of the worker processor.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=118598&aid=3525733&group_id=18598

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/