RTE Protocol Plugin - Unknown telnet command type: FD 27

104 views
Skip to first unread message

christopher...@gmail.com

unread,
Feb 21, 2019, 11:53:37 AM2/21/19
to jmeter-plugins
I can connect to our Mainframe and run tests perfectly fine with JMeter/RTE Protocol Plugin.

I can connect to our Micro Focus TN3270 Environment (Simulated Mainframe) via Reflections 3270 Emulation Software perfectly fine.

When I try to connect to the Micro Focus TN3270 Environment using JMeter/RTE Protocol Plugin I get the following error:

2019-02-21 11:05:30,750 INFO o.a.j.e.StandardJMeterEngine: Starting ThreadGroup: 1 : Thread Group - Micro Focus LOGIN
2019-02-21 11:05:30,750 INFO o.a.j.e.StandardJMeterEngine: Starting 1 threads for group Thread Group - Micro Focus LOGIN.
2019-02-21 11:05:30,750 INFO o.a.j.e.StandardJMeterEngine: Thread will continue on error
2019-02-21 11:05:30,750 INFO o.a.j.t.ThreadGroup: Starting thread group... number=1 threads=1 ramp-up=5 perThread=5000.0 delayedStart=false
2019-02-21 11:05:30,750 INFO o.a.j.t.ThreadGroup: Started thread group number 1
2019-02-21 11:05:30,750 INFO o.a.j.e.StandardJMeterEngine: All thread groups have been started
2019-02-21 11:05:30,766 INFO o.a.j.t.JMeterThread: Thread started: Thread Group - Micro Focus LOGIN 1-1
2019-02-21 11:05:30,797 ERROR o.a.j.JMeter: Uncaught exception: 
java.security.InvalidParameterException: Unknown telnet command type: FD 27

java.net.SocketException: Connection reset
	at java.net.SocketInputStream.read(Unknown Source) ~[?:1.8.0_162]
	at java.net.SocketInputStream.read(Unknown Source) ~[?:1.8.0_162]
	at sun.security.ssl.InputRecord.readFully(Unknown Source) ~[?:1.8.0_162]
	at sun.security.ssl.InputRecord.read(Unknown Source) ~[?:1.8.0_162]
	at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source) ~[?:1.8.0_162]
	at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source) ~[?:1.8.0_162]
	at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) ~[?:1.8.0_162]
	at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) ~[?:1.8.0_162]
	at org.apache.http.conn.ssl.SSLSocketFactory.createLayeredSocket(SSLSocketFactory.java:570) ~[httpclient-4.5.7.jar:4.5.7]
	at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:554) ~[httpclient-4.5.7.jar:4.5.7]
	at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:415) ~[httpclient-4.5.7.jar:4.5.7]
	at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180) ~[httpclient-4.5.7.jar:4.5.7]
	at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:326) ~[httpclient-4.5.7.jar:4.5.7]
	at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:605) ~[httpclient-4.5.7.jar:4.5.7]
	at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:440) ~[httpclient-4.5.7.jar:4.5.7]
	at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:835) ~[httpclient-4.5.7.jar:4.5.7]
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) ~[httpclient-4.5.7.jar:4.5.7]
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56) ~[httpclient-4.5.7.jar:4.5.7]
	at org.jmeterplugins.repository.JARSourceHTTP.execute(JARSourceHTTP.java:499) ~[jmeter-plugins-manager-1.3.jar:?]
	at org.jmeterplugins.repository.JARSourceHTTP.execute(JARSourceHTTP.java:494) ~[jmeter-plugins-manager-1.3.jar:?]
	at org.jmeterplugins.repository.JARSourceHTTP.getJSON(JARSourceHTTP.java:152) ~[jmeter-plugins-manager-1.3.jar:?]
	at org.jmeterplugins.repository.JARSourceHTTP.getRepositories(JARSourceHTTP.java:276) ~[jmeter-plugins-manager-1.3.jar:?]
	at org.jmeterplugins.repository.JARSourceHTTP.getRepo(JARSourceHTTP.java:304) ~[jmeter-plugins-manager-1.3.jar:?]
	at org.jmeterplugins.repository.PluginManager.load(PluginManager.java:71) ~[jmeter-plugins-manager-1.3.jar:?]
	at org.jmeterplugins.repository.PluginManagerMenuItem$1.run(PluginManagerMenuItem.java:41) [jmeter-plugins-manager-1.3.jar:?]
2019-02-21 11:06:30,805 WARN c.b.j.r.s.RTESampler: Timeout error
java.util.concurrent.TimeoutException: Timeout waiting for emulator to be unlocked after 60000 millis. Check if Timeout values of the 'Wait for' components are greater than Stable time or Silent interval.

roger.a...@abstracta.com.uy

unread,
Feb 22, 2019, 3:13:57 PM2/22/19
to jmeter-plugins
Hello

FD 27 looks like a TN5250 protocol message, are you sure that the environment is 3270 instead of 5250? Can you try using Wireshark to capture the traffic and see what telnet sub command is identified by Wireshark for that FD 27 packet?

Regards 

Chris Bradshaw

unread,
Feb 25, 2019, 9:58:07 AM2/25/19
to jmeter-...@googlegroups.com
Hello Roger,

It's 3270, I can use Reflections to connect without any issues.  I'll try to capture more telnet info for you, but as my environment is locked down very tight, may have trouble...

Thanks,
Chris

--
You received this message because you are subscribed to a topic in the Google Groups "jmeter-plugins" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jmeter-plugins/ruNNHRWiw4I/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jmeter-plugin...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Janani n

unread,
Apr 20, 2022, 7:46:05 AM4/20/22
to jmeter-plugins

Hi,

Even I found the same kind of error.  

2022-04-20 11:29:01,400 INFO o.j.r.PluginManager: Plugins Status: [jpgc-graphs-additional=2.0, bzm-rte=3.2, jpgc-plugins-manager=1.7, jmeter-core=5.4.3, jmeter-ftp=5.4.3, jmeter-http=5.4.3, jmeter-jdbc=5.4.3, jmeter-jms=5.4.3, jmeter-junit=5.4.3, jmeter-java=5.4.3, jmeter-ldap=5.4.3, jmeter-mail=5.4.3, jmeter-mongodb=5.4.3, jmeter-native=5.4.3, jmeter-tcp=5.4.3, jmeter-components=5.4.3]
2022-04-20 11:29:01,401 INFO o.j.r.PluginManagerMenuItem: Plugins Manager has upgrades: [bzm-rte]
2022-04-20 11:30:06,905 ERROR o.a.j.JMeter: Uncaught exception in thread Thread[AWT-EventQueue-0,6,main]
java.lang.IllegalStateException: No ThreadGroup or RecordingController was found where to add recorded samplers
    at com.blazemeter.jmeter.rte.recorder.RecordingTargetFinder.findTargetControllerNode(RecordingTargetFinder.java:20) ~[jmeter-bzm-rte-3.2.jar:?]
    at com.blazemeter.jmeter.rte.recorder.RTERecorder.onRecordingStart(RTERecorder.java:214) ~[jmeter-bzm-rte-3.2.jar:?]
    at com.blazemeter.jmeter.rte.recorder.RTERecorderGui.onRecordingStart(RTERecorderGui.java:124) ~[jmeter-bzm-rte-3.2.jar:?]
    at com.blazemeter.jmeter.rte.recorder.RTERecorderPanel.actionPerformed(RTERecorderPanel.java:188) ~[jmeter-bzm-rte-3.2.jar:?]
    at javax.swing.AbstractButton.fireActionPerformed(Unknown Source) ~[?:1.8.0_321]
    at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) ~[?:1.8.0_321]
    at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) ~[?:1.8.0_321]
    at javax.swing.DefaultButtonModel.setPressed(Unknown Source) ~[?:1.8.0_321]
    at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source) ~[?:1.8.0_321]
    at java.awt.Component.processMouseEvent(Unknown Source) ~[?:1.8.0_321]
    at javax.swing.JComponent.processMouseEvent(Unknown Source) ~[?:1.8.0_321]
    at java.awt.Component.processEvent(Unknown Source) ~[?:1.8.0_321]
    at java.awt.Container.processEvent(Unknown Source) ~[?:1.8.0_321]
    at java.awt.Component.dispatchEventImpl(Unknown Source) ~[?:1.8.0_321]
    at java.awt.Container.dispatchEventImpl(Unknown Source) ~[?:1.8.0_321]
    at java.awt.Component.dispatchEvent(Unknown Source) ~[?:1.8.0_321]
    at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) ~[?:1.8.0_321]
    at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) ~[?:1.8.0_321]
    at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) ~[?:1.8.0_321]
    at java.awt.Container.dispatchEventImpl(Unknown Source) ~[?:1.8.0_321]
    at java.awt.Window.dispatchEventImpl(Unknown Source) ~[?:1.8.0_321]
    at java.awt.Component.dispatchEvent(Unknown Source) ~[?:1.8.0_321]
    at java.awt.EventQueue.dispatchEventImpl(Unknown Source) ~[?:1.8.0_321]
    at java.awt.EventQueue.access$500(Unknown Source) ~[?:1.8.0_321]
    at java.awt.EventQueue$3.run(Unknown Source) ~[?:1.8.0_321]
    at java.awt.EventQueue$3.run(Unknown Source) ~[?:1.8.0_321]
    at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_321]
    at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) ~[?:1.8.0_321]
    at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) ~[?:1.8.0_321]
    at java.awt.EventQueue$4.run(Unknown Source) ~[?:1.8.0_321]
    at java.awt.EventQueue$4.run(Unknown Source) ~[?:1.8.0_321]
    at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_321]
    at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) ~[?:1.8.0_321]
    at java.awt.EventQueue.dispatchEvent(Unknown Source) ~[?:1.8.0_321]
    at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) [?:1.8.0_321]
    at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) [?:1.8.0_321]
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) [?:1.8.0_321]
    at java.awt.EventDispatchThread.pumpEvents(Unknown Source) [?:1.8.0_321]
    at java.awt.EventDispatchThread.pumpEvents(Unknown Source) [?:1.8.0_321]
    at java.awt.EventDispatchThread.run(Unknown Source) [?:1.8.0_321]
2022-04-20 11:30:45,238 INFO o.a.j.e.StandardJMeterEngine: Running the test!
2022-04-20 11:30:45,239 INFO o.a.j.s.SampleEvent: List of sample_variables: []
2022-04-20 11:30:45,239 INFO o.a.j.s.SampleEvent: List of sample_variables: []
2022-04-20 11:30:45,240 INFO o.a.j.e.u.CompoundVariable: Note: Function class names must contain the string: '.functions.'
2022-04-20 11:30:45,240 INFO o.a.j.e.u.CompoundVariable: Note: Function class names must not contain the string: '.gui.'
2022-04-20 11:30:45,519 INFO o.a.j.g.u.JMeterMenuBar: setRunning(true, *local*)
2022-04-20 11:30:45,581 INFO o.a.j.e.StandardJMeterEngine: Starting ThreadGroup: 1 : Thread Group
2022-04-20 11:30:45,581 INFO o.a.j.e.StandardJMeterEngine: Starting 1 threads for group Thread Group.
2022-04-20 11:30:45,581 INFO o.a.j.e.StandardJMeterEngine: Thread will continue on error
2022-04-20 11:30:45,582 INFO o.a.j.t.ThreadGroup: Starting thread group... number=1 threads=1 ramp-up=1 delayedStart=false
2022-04-20 11:30:45,585 INFO o.a.j.t.ThreadGroup: Started thread group number 1
2022-04-20 11:30:45,585 INFO o.a.j.e.StandardJMeterEngine: All thread groups have been started
2022-04-20 11:30:45,585 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-1
2022-04-20 11:30:45,588 INFO o.a.j.t.JMeterThread: Thread is done: Thread Group 1-1
2022-04-20 11:30:45,588 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-1
2022-04-20 11:30:45,588 INFO o.a.j.e.StandardJMeterEngine: Notifying test listeners of end of test
2022-04-20 11:30:45,589 INFO o.a.j.s.FileServer: Default base='D:\Ally\Rajasri\apache-jmeter-5.4.3\apache-jmeter-5.4.3\bin'
2022-04-20 11:30:45,590 INFO o.a.j.g.u.JMeterMenuBar: setRunning(false, *local*)
2022-04-20 11:31:21,974 INFO o.a.j.s.FileServer: Set new base='D:\Ally\Rajasri\apache-jmeter-5.4.3\apache-jmeter-5.4.3\bin'
2022-04-20 11:31:22,129 INFO o.a.j.s.SaveService: Testplan (JMX) version: 2.2. Testlog (JTL) version: 2.2
2022-04-20 11:31:22,144 INFO o.a.j.s.SaveService: Using SaveService properties file encoding UTF-8
2022-04-20 11:31:22,145 INFO o.a.j.s.SaveService: Using SaveService properties version 5.0
2022-04-20 11:31:22,167 INFO o.a.j.e.StandardJMeterEngine: Running the test!
2022-04-20 11:31:22,167 INFO o.a.j.s.SampleEvent: List of sample_variables: []
2022-04-20 11:31:22,168 INFO o.a.j.g.u.JMeterMenuBar: setRunning(true, *local*)
2022-04-20 11:31:22,222 INFO o.a.j.e.StandardJMeterEngine: Starting ThreadGroup: 1 : Thread Group
2022-04-20 11:31:22,222 INFO o.a.j.e.StandardJMeterEngine: Starting 1 threads for group Thread Group.
2022-04-20 11:31:22,222 INFO o.a.j.e.StandardJMeterEngine: Thread will continue on error
2022-04-20 11:31:22,222 INFO o.a.j.t.ThreadGroup: Starting thread group... number=1 threads=1 ramp-up=1 delayedStart=false
2022-04-20 11:31:22,223 INFO o.a.j.t.ThreadGroup: Started thread group number 1
2022-04-20 11:31:22,223 INFO o.a.j.e.StandardJMeterEngine: All thread groups have been started
2022-04-20 11:31:22,223 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-1
2022-04-20 11:31:22,224 INFO o.a.j.t.JMeterThread: Thread is done: Thread Group 1-1
2022-04-20 11:31:22,224 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-1
2022-04-20 11:31:22,224 INFO o.a.j.e.StandardJMeterEngine: Notifying test listeners of end of test
2022-04-20 11:31:22,224 INFO o.a.j.g.u.JMeterMenuBar: setRunning(false, *local*)
2022-04-20 11:31:26,351 INFO o.a.j.s.SampleResult: Note: Sample TimeStamps are START times
2022-04-20 11:31:26,351 INFO o.a.j.s.SampleResult: sampleresult.default.encoding is set to ISO-8859-1
2022-04-20 11:31:26,351 INFO o.a.j.s.SampleResult: sampleresult.useNanoTime=true
2022-04-20 11:31:26,351 INFO o.a.j.s.SampleResult: sampleresult.nanoThreadSleep=5000
2022-04-20 11:31:26,386 ERROR o.a.j.JMeter: Uncaught exception in thread Thread[Thread-7,5,main]

java.security.InvalidParameterException: Unknown telnet command type: FD 27

    at com.bytezone.dm3270.telnet.TelnetCommand.<init>(TelnetCommand.java:82) ~[dm3270-lib-0.13.jar:?]
    at com.bytezone.dm3270.streams.TelnetListener.processTelnetCommand(TelnetListener.java:146) ~[dm3270-lib-0.13.jar:?]
    at com.bytezone.dm3270.telnet.TelnetProcessor.listen(TelnetProcessor.java:105) ~[dm3270-lib-0.13.jar:?]
    at com.bytezone.dm3270.streams.TelnetListener.listen(TelnetListener.java:58) ~[dm3270-lib-0.13.jar:?]
    at com.bytezone.dm3270.streams.TerminalServer.run(TerminalServer.java:71) ~[dm3270-lib-0.13.jar:?]
    at java.lang.Thread.run(Unknown Source) [?:1.8.0_321]

I can connect to our Micro Focus TN3270 Environment (Simulated Mainframe) via Reflections 3270 Emulation Software perfectly fine.


DT

unread,
Apr 20, 2022, 10:57:54 AM4/20/22
to jmeter-plugins
Try increasing JMeter logging verbosity for the RTE plugin by adding the next line to log4j2.xml file:

<Logger name=" com.blazemeter.jmeter.rte" level="debug" />

and check jmeter.log file for any suspicious entries.

Looking here the issue might be cause by protocols mismatch, i.e, you're using 5250 instead of 3270 or something like this.

If you're absolutely sure that your setup is correct you canraise an issue at the RTE Plugin Github page or open a BlazeMeter Support Ticket
Reply all
Reply to author
Forward
0 new messages