New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

port out of range:-1 #4

Closed
avana9 opened this Issue Feb 23, 2017 · 19 comments

Comments

Projects
None yet
6 participants
@avana9

avana9 commented Feb 23, 2017

i am trying to publish a massage to IOT on port 8883 but detect an exception (in attach the configuration
issue
):

  1. if i use this Server Name: SIT-IOT....... the error is:
    2017/02/23 11:30:11 ERROR - net.xmeter.samplers.PubSampler: Peer disconnected java.io.EOFException: Peer disconnected
    at org.fusesource.hawtdispatch.transport.AbstractProtocolCodec.read(AbstractProtocolCodec.java:331)
    at org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:657)
    at org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:244)
    at org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
    at org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:226)
    at org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:96)
    at org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)

  2. if i use this Server Name: ssl://SIT-IOT....... the error is:
    2017/02/23 11:37:08 ERROR - jmeter.JMeter: Uncaught exception: java.lang.IllegalArgumentException: port out of range:-1
    at java.net.InetSocketAddress.checkPort(Unknown Source)
    at java.net.InetSocketAddress.(Unknown Source)
    at org.fusesource.hawtdispatch.transport.TcpTransport$2.run(TcpTransport.java:416)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

@jinfahua

This comment has been minimized.

Show comment
Hide comment
@jinfahua

jinfahua Mar 7, 2017

Collaborator

Not necessary to add "ssl://" in 'Server name or IP", the protocol is set in the 'Protocols' dropdown box. Please make sure that the user name & password are correct.

Collaborator

jinfahua commented Mar 7, 2017

Not necessary to add "ssl://" in 'Server name or IP", the protocol is set in the 'Protocols' dropdown box. Please make sure that the user name & password are correct.

@avana9

This comment has been minimized.

Show comment
Hide comment
@avana9

avana9 Mar 10, 2017

username and password are correct. I've followed these instructions: https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-mqtt-support (section: Using the MQTT protocol directly) but the error is the same:
ERROR - net.xmeter.samplers.PubSampler: Peer disconnected java.io.EOFException: Peer disconnected

Moreover, where can i set "ClientId"? in MQTT Pub Sampler i see only the tag "ClientId prefix". If i set this filed with my deviceId, i detect another error.

avana9 commented Mar 10, 2017

username and password are correct. I've followed these instructions: https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-mqtt-support (section: Using the MQTT protocol directly) but the error is the same:
ERROR - net.xmeter.samplers.PubSampler: Peer disconnected java.io.EOFException: Peer disconnected

Moreover, where can i set "ClientId"? in MQTT Pub Sampler i see only the tag "ClientId prefix". If i set this filed with my deviceId, i detect another error.

@jinfahua

This comment has been minimized.

Show comment
Hide comment
@jinfahua

jinfahua Mar 13, 2017

Collaborator

Possibly it's caused by not specifying a correct clientID. Currently, only "ClientId prefix" is supported, the fullname of clientID will be generated automatically with "ClientId_prefix" + random string. Please verify if you can use mosquitto client tools pub/sub messages (such as specify a not correct clientId will cause the same problem or not).

Collaborator

jinfahua commented Mar 13, 2017

Possibly it's caused by not specifying a correct clientID. Currently, only "ClientId prefix" is supported, the fullname of clientID will be generated automatically with "ClientId_prefix" + random string. Please verify if you can use mosquitto client tools pub/sub messages (such as specify a not correct clientId will cause the same problem or not).

@god-pane

This comment has been minimized.

Show comment
Hide comment
@god-pane

god-pane Apr 21, 2017

where can i set "ClientId"? in MQTT Pub Sampler i see only the tag "ClientId prefix". If i set this filed with my deviceId, i detect another error.
Do you want to update later? the ClientId

god-pane commented Apr 21, 2017

where can i set "ClientId"? in MQTT Pub Sampler i see only the tag "ClientId prefix". If i set this filed with my deviceId, i detect another error.
Do you want to update later? the ClientId

@rende2005

This comment has been minimized.

Show comment
Hide comment
@rende2005

rende2005 Apr 21, 2017

Contributor

Right now as mentioned in earlier comment, "ClientId" = "ClientId_prefix" + random string.

Maybe I missed something.. are you expecting the exact ClientId field that can be specified on this Pub Sampler UI? If so, can you elaborate how ClientId is being used in your application, should it be the same as your deviceId?

We can consider an option for ClientId without random string any way.

Contributor

rende2005 commented Apr 21, 2017

Right now as mentioned in earlier comment, "ClientId" = "ClientId_prefix" + random string.

Maybe I missed something.. are you expecting the exact ClientId field that can be specified on this Pub Sampler UI? If so, can you elaborate how ClientId is being used in your application, should it be the same as your deviceId?

We can consider an option for ClientId without random string any way.

@god-pane

This comment has been minimized.

Show comment
Hide comment
@god-pane

god-pane Apr 24, 2017

yes, in my application the same as deviceId。
image

god-pane commented Apr 24, 2017

yes, in my application the same as deviceId。
image

@jinfahua

This comment has been minimized.

Show comment
Hide comment
@jinfahua

jinfahua Apr 24, 2017

Collaborator

Please try https://github.com/emqtt/mqtt-jmeter/releases/tag/v0.92_beta.

As in below screen, please uncheck 'add random client id suffix', and then the value of 'ClientId' will be used as client ID.

2017-04-24 11 01 37

Collaborator

jinfahua commented Apr 24, 2017

Please try https://github.com/emqtt/mqtt-jmeter/releases/tag/v0.92_beta.

As in below screen, please uncheck 'add random client id suffix', and then the value of 'ClientId' will be used as client ID.

2017-04-24 11 01 37

@god-pane

This comment has been minimized.

Show comment
Hide comment
@god-pane

god-pane Apr 25, 2017

It's all right now, thank you

god-pane commented Apr 25, 2017

It's all right now, thank you

@jinfahua

This comment has been minimized.

Show comment
Hide comment
@jinfahua

jinfahua Apr 25, 2017

Collaborator

OK, so close the issue and it will be released in 0.92 stable version.

Collaborator

jinfahua commented Apr 25, 2017

OK, so close the issue and it will be released in 0.92 stable version.

@devendrajha

This comment has been minimized.

Show comment
Hide comment
@devendrajha

devendrajha Oct 5, 2017

Hi i have all proper username and password but using tcp i am not able to connect please help me out

devendrajha commented Oct 5, 2017

Hi i have all proper username and password but using tcp i am not able to connect please help me out

@devendrajha

This comment has been minimized.

Show comment
Hide comment
@devendrajha

devendrajha commented Oct 5, 2017

image

@jinfahua

This comment has been minimized.

Show comment
Hide comment
@jinfahua

jinfahua Oct 8, 2017

Collaborator

Maybe it's caused by MQTT version, which was discussed in the thread - #21

Could you have a try for the temp fix attached in the thread?

Collaborator

jinfahua commented Oct 8, 2017

Maybe it's caused by MQTT version, which was discussed in the thread - #21

Could you have a try for the temp fix attached in the thread?

@devendrajha

This comment has been minimized.

Show comment
Hide comment
@devendrajha

devendrajha Oct 9, 2017

In Jmeter testing for IOT-HUB this is TCP protocol or SSL if SSL then how i will manage certificate because i don't have any certificate

devendrajha commented Oct 9, 2017

In Jmeter testing for IOT-HUB this is TCP protocol or SSL if SSL then how i will manage certificate because i don't have any certificate

@jinfahua

This comment has been minimized.

Show comment
Hide comment
@jinfahua

jinfahua Oct 10, 2017

Collaborator

Maybe you should consult Azure.

Collaborator

jinfahua commented Oct 10, 2017

Maybe you should consult Azure.

@devendrajha

This comment has been minimized.

Show comment
Hide comment
@devendrajha

devendrajha Oct 21, 2017

Here i have notice Jmeter doesn't supprot IOT-HUB because while sending multiple message using multiple thread with delay and without delay i am getting connection error as per Azure support they were saying it is try to connect with every thread science using iot hub we can connect once

IoT Hub only supports one active MQTT connection per device. Any new MQTT connection on behalf of the same device ID causes IoT Hub to drop the existing connection.

https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-mqtt-support

@jinfahua please reply with you value-able feedback

devendrajha commented Oct 21, 2017

Here i have notice Jmeter doesn't supprot IOT-HUB because while sending multiple message using multiple thread with delay and without delay i am getting connection error as per Azure support they were saying it is try to connect with every thread science using iot hub we can connect once

IoT Hub only supports one active MQTT connection per device. Any new MQTT connection on behalf of the same device ID causes IoT Hub to drop the existing connection.

https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-mqtt-support

@jinfahua please reply with you value-able feedback

@devendrajha

This comment has been minimized.

Show comment
Hide comment
@devendrajha

devendrajha Oct 21, 2017

@jinfahua Here one thread working properly

devendrajha commented Oct 21, 2017

@jinfahua Here one thread working properly

@jinfahua

This comment has been minimized.

Show comment
Hide comment
@jinfahua

jinfahua Oct 23, 2017

Collaborator

The current design is that all iterations for the same virtual user shares one same connection. But if you have multiple virtual users, then corresponding multiple connections will be created. But different pub & sub samplers in one thread-group DO NOT share the same connections, different samplers in same thread-group will created a separated connection.

Now we have an ongoing release that support share connection for pub/sub samplers in the same thread-group. In real user scenario is that one client can be either pub or sub (with the same connection).

Collaborator

jinfahua commented Oct 23, 2017

The current design is that all iterations for the same virtual user shares one same connection. But if you have multiple virtual users, then corresponding multiple connections will be created. But different pub & sub samplers in one thread-group DO NOT share the same connections, different samplers in same thread-group will created a separated connection.

Now we have an ongoing release that support share connection for pub/sub samplers in the same thread-group. In real user scenario is that one client can be either pub or sub (with the same connection).

@devendrajha

This comment has been minimized.

Show comment
Hide comment
@devendrajha

devendrajha Oct 23, 2017

Thanks jinfahua when can we aspect this new release ??

devendrajha commented Oct 23, 2017

Thanks jinfahua when can we aspect this new release ??

@jinfahua

This comment has been minimized.

Show comment
Hide comment
@jinfahua

jinfahua Oct 24, 2017

Collaborator

The code is already in branch conn_share https://github.com/emqtt/mqtt-jmeter/tree/share_conn , you can check it out and build a binary by yourself. The new release will still take some time.

Collaborator

jinfahua commented Oct 24, 2017

The code is already in branch conn_share https://github.com/emqtt/mqtt-jmeter/tree/share_conn , you can check it out and build a binary by yourself. The new release will still take some time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment