Excuting sdkperf in windows

Sbelag
Sbelag Member Posts: 6
Hello,
I'm using sdkperf (sdkperf-jcsmp-8.4.14.10) on a Windows . However, the following command:

sdkperf_java.bat -cip messaging-jms.apps.aro-sndbx.cloud-nuage.com:443 -cu user@vpn -cp pwd

is failing, and I'm encountering the error below.

I want to highlight that I'm utilizing the tcps protocol for both the host address and credentials. ( I've successfully tested the same host address and credentials in Jms Toolbox without encountering any issues).

Any insights or assistance would be appreciated.

======================================================
Getting ready to init clients
E: Initialization error: client creation failed.
com.solacesystems.pubsub.sdkperf.core.PubSubException: Error while connecting.
at com.solacesystems.pubsub.sdkperf.core.AbstractClientCollection.connect(AbstractClientCollection.java:473)
at com.solacesystems.pubsub.sdkperf.SDKPerf_java.run(SDKPerf_java.java:211)
at com.solacesystems.pubsub.sdkperf.SDKPerf_java.main(SDKPerf_java.java:118)
Caused by: com.solacesystems.jcsmp.JCSMPTransportException: (Client name: N35082373/local/pc Local addr: 10.67.114.255 Local port: 58750 Remote addr: messaging-jms.apps.aro-sndbx.cloud-nuage.com Remote port: 443) - Error communicating with the router.
at com.solacesystems.jcsmp.protocol.impl.TcpChannel.executePostOnce(TcpChannel.java:254)
at com.solacesystems.jcsmp.protocol.impl.ChannelOpStrategyClient.performOpen(ChannelOpStrategyClient.java:101)
at com.solacesystems.jcsmp.protocol.impl.TcpClientChannel.performOpenSingle(TcpClientChannel.java:428)
at com.solacesystems.jcsmp.protocol.impl.TcpClientChannel.access$800(TcpClientChannel.java:124)
at com.solacesystems.jcsmp.protocol.impl.TcpClientChannel$ClientChannelConnect.call(TcpClientChannel.java:2661)
at com.solacesystems.jcsmp.protocol.impl.TcpClientChannel.open(TcpClientChannel.java:404)
at com.solacesystems.jcsmp.impl.JCSMPBasicSession.sniffRouter(JCSMPBasicSession.java:423)
at com.solacesystems.jcsmp.impl.JCSMPBasicSession.getMessageProducer(JCSMPBasicSession.java:772)
at com.solacesystems.pubsub.sdkperf.jcsmpcore.JcsmpClient.connect(JcsmpClient.java:1252)
at com.solacesystems.pubsub.sdkperf.core.AbstractClientCollection.connect(AbstractClientCollection.java:471)
... 2 more
Caused by: java.io.IOException: Unable to read enough bytes from stream!
at com.solacesystems.jcsmp.protocol.smf.impl.NetworkIOUtil.readDataSafely(NetworkIOUtil.java:16)
at com.solacesystems.jcsmp.protocol.smf.impl.SMFHeaderDecoder.decodeHeader(SMFHeaderDecoder.java:77)
at com.solacesystems.jcsmp.protocol.smf.SMFWireMessageHandler.readMessage(SMFWireMessageHandler.java:99)
at com.solacesystems.jcsmp.protocol.smf.SimpleSmfClient.readMessage(SimpleSmfClient.java:220)
at com.solacesystems.jcsmp.protocol.smf.SimpleSmfClient.doPost(SimpleSmfClient.java:238)
at com.solacesystems.jcsmp.protocol.impl.TcpChannel.executePostOnce(TcpChannel.java:199)
... 11 more
=======================================================

Best Answers

  • yangsen
    yangsen Member, Employee Posts: 18 Solace Employee
    #2 Answer ✓

    If the port is correct, use this command(note the tcps:// prefix): sdkperf_java.bat -cip tcps://messaging-jms.apps.aro-sndbx.cloud-nuage.com:443 -cu user@vpn -cp pwd

  • Sbelag
    Sbelag Member Posts: 6
    #3 Answer ✓
    thank you so much!! its working after adding the tcps:// , the port was changed by our platform team to 443.

Answers

  • Markus
    Markus Member, Employee Posts: 4 Solace Employee

    If you are using JCSMP , you will typically use port 55443 instead of 443, have you tried that?

  • yangsen
    yangsen Member, Employee Posts: 18 Solace Employee
    #5 Answer ✓

    If the port is correct, use this command(note the tcps:// prefix): sdkperf_java.bat -cip tcps://messaging-jms.apps.aro-sndbx.cloud-nuage.com:443 -cu user@vpn -cp pwd

  • Sbelag
    Sbelag Member Posts: 6
    #6 Answer ✓
    thank you so much!! its working after adding the tcps:// , the port was changed by our platform team to 443.