[ grinder-Bugs-2988256 ] NoClassDefFoundError when starting worker thread
"SourceForge.net" <[email protected]>
| Newsgroups | gmane.comp.java.grinder.devel |
|---|---|
| Message-ID | <[email protected]> |
Bugs item #2988256, was opened at 2010-04-16 16:00 Message generated for change (Comment added) made by zverik You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=118598&aid=2988256&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: Ilya Zverev (zverik) Assigned to: Philip Aston (philipa) Summary: NoClassDefFoundError when starting worker thread Initial Comment: Windows XP, start console and agent from command prompt. Then click 'distribute and run' in console, see agent throwing exception and stopping. 16.04.10 15:39:32 (agent): received a start message 16.04.10 15:39:32 (agent): Worker process command line: java '-javaagent:D:\Progr\grinder-3.4\lib\grinder-agent.jar' -classpath 'grinder.jar' net.grinder.engine.process.WorkerProcessEntryPoint java.lang.NoClassDefFoundError: net/grinder/engine/process/WorkerProcessEntryPoint Exception in thread "main" net.grinder.engine.common.EngineException: Failed to send initialisation message at net.grinder.engine.agent.AbstractWorkerFactory.create(AbstractWorkerFactory.java:95) at net.grinder.engine.agent.WorkerLauncher.startSomeWorkers(WorkerLauncher.java:99) at net.grinder.engine.agent.WorkerLauncher.startAllWorkers(WorkerLauncher.java:87) at net.grinder.engine.agent.AgentImplementation.run(AgentImplementation.java:322) at net.grinder.Grinder.run(Grinder.java:134) at net.grinder.Grinder.main(Grinder.java:75) Caused by: net.grinder.communication.CommunicationException: Exception whilst sending message at net.grinder.communication.AbstractSender.send(AbstractSender.java:58) at net.grinder.engine.agent.AbstractWorkerFactory.create(AbstractWorkerFactory.java:91) ... 5 more Caused by: java.io.IOException: The pipe has been ended at java.io.FileOutputStream.writeBytes(Native Method) at java.io.FileOutputStream.write(Unknown Source) at java.io.BufferedOutputStream.flushBuffer(Unknown Source) at java.io.BufferedOutputStream.flush(Unknown Source) at java.io.BufferedOutputStream.flush(Unknown Source) at java.io.ObjectOutputStream$BlockDataOutputStream.flush(Unknown Source) at java.io.ObjectOutputStream.flush(Unknown Source) at net.grinder.communication.AbstractSender.writeMessageToStream(AbstractSender.java:91) The reason: incorrect quotation marks in the command line. It should look like this: java "-javaagent:D:\Progr\grinder-3.4\lib\grinder-agent.jar" -classpath "grinder.jar" net.grinder.engine.process.WorkerProcessEntryPoint ---------------------------------------------------------------------- >Comment By: Ilya Zverev (zverik) Date: 2010-04-16 16:29 Message: You're right, absoulte path did work. Thanks! Please add this to FAQ or somewhere accessible by google. I didn't find a soultion when I was searching for it. ---------------------------------------------------------------------- Comment By: Philip Aston (philipa) Date: 2010-04-16 16:18 Message: I don't believe the reason you give is correct. The Grinder only adds the single quotes to the string it displays in the terminal output. The actual process arguments are passed unquoted, as an array of strings to the Java ProcessBuilder API. There's some sort of bug here, no doubt. Can you retry with your CLASSPATH set to an absolute path (i.e. D:\Progr\grinder-3.4\lib\grinder.jar). Thanks, - Phil ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=118598&aid=2988256&group_id=18598 ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev