Bug 44753 - RMI Exceptions from JMeter Servers
Summary: RMI Exceptions from JMeter Servers
Status: RESOLVED WONTFIX
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 2.3.1
Hardware: PC Windows XP
: P2 critical (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-03 17:00 UTC by BK
Modified: 2008-05-13 14:53 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description BK 2008-04-03 17:00:00 UTC 
I'm running 20 threads each on my two remote JMeter Server instances from the JMeter GUI.  I get the following exception on the JMeter Server instances after about 2-3 minutes.  Is this normal?



2008/04/03 16:59:04 ERROR - jmeter.samplers.BatchSampleSender: sampleOccurred java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is: 
	java.io.EOFException
	at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
	at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
	at sun.rmi.server.UnicastRef.invoke(Unknown Source)
	at org.apache.jmeter.samplers.RemoteSampleListenerImpl_Stub.processBatch(Unknown Source)
	at org.apache.jmeter.samplers.BatchSampleSender.SampleOccurred(BatchSampleSender.java:131)
	at org.apache.jmeter.samplers.RemoteListenerWrapper.sampleOccurred(RemoteListenerWrapper.java:86)
	at org.apache.jmeter.threads.ListenerNotifier.notifyListeners(ListenerNotifier.java:240)
	at org.apache.jmeter.threads.JMeterThread.notifyListeners(JMeterThread.java:576)
	at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:313)
	at java.lang.Thread.run(Unknown Source)
Comment 1 Sebb 2008-05-09 02:03:32 UTC 
Not seen the problem, but it looks like the Java library (rather than JMeter) has detected a problem, possibly network-related.

Have you got a simple test case that can be used to reliably demonstrate the problem?
Comment 2 BK 2008-05-09 11:48:53 UTC 
(In reply to comment #1)
> Not seen the problem, but it looks like the Java library (rather than JMeter)
> has detected a problem, possibly network-related.
> 
> Have you got a simple test case that can be used to reliably demonstrate the
> problem?
> 

I don't really have a test case. I was actually just testing against a MediaWiki link (just one URL, not a scenario) and had it loaded up to about 200 concurrent connections over two machines (100 connections each).

It seems that when JMeter is under great load link this that it's fairly reproducable.  Maybe a limitation of the rmiregistry process under load?
Comment 3 Sebb 2008-05-13 14:53:09 UTC 
It does not look like there is anything that JMeter can do to prevent this occurring.
Comment 4 The ASF infrastructure team 2022-09-24 20:37:41 UTC 
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2092