Skip to main content
G
gherr-21-Visitor
1-Visitor
August 18, 2016
Solved

Connection Error using Basic Thing with Property

  • August 18, 2016
  • 1 reply
  • 4662 views

Hi all,

I am running ThingWorx on localhost using Apache Tomcat 8.0. I have modified the config.json file with IP Address  as 'localhost'. This is how the link to my ThingWorx webpage looks like : http://localhost/Thingworx/Composer/index.html. When I am trying to run the example # 3, I am unable to create the connection. Following are the logs:

SELECTED: Basic Thing with Property

Running Example #3: minimal agent w/ property

[Error] Error intializing socket connection.  Err = 111

[Error] twWs_Connect: Error restarting socket.  Error 111

[Error] twMessage_Send: Error sending Message with RequestId 1

[Error] [HomeLight0]: Error calling twApi_WriteProperty() for LightLocation - 1107

[Error] Error intializing socket connection.  Err = 111

[Error] twWs_Connect: Error restarting socket.  Error 111

[Error] twMessage_Send: Error sending Message with RequestId 2

[Error] [HomeLight0]: Error calling twApi_PushProperties() - 1107

[Error] Error connecting - 1001

Could you please help? TIA!

Best answer by ttielebein

Well, if you are connecting to ThingWorx with the provided URL above (http://localhost/Thingworx/Composer/index.html​), then you know that ThingWorx is running on port 80 (as none is specified and port 80 is the default for HTTP). So I don't think the comment about port 22 is entirely relevant. Might be worth a try just to swap those guys out since it is easy to check.

I don't think that "tls" is a valid parameter. If you are trying to set the encryption to false, I'd use:

"ws_connection": {

       "encryption": "none"

}

If swapping that syntax out doesn't help, try adding:

"certificates": {

     "validate": false,

     "allow_self_signed": true

}

Let me know how this goes. For a full list of valid parameters for this file, see the config.json.complete file, which should have been included in your EMS download.

1 reply

T
ttielebein5-Regular Member
5-Regular Member
August 18, 2016

Can you please post the rest of your config.json file contents here so I can look at it?

Thanks!

Tori

G
gherr-21-VisitorAuthor
1-Visitor
August 18, 2016

Thank you Tori for your reply. CJ.PNG

Also, I have checked the ports opened on my Rpi using netstat -tln: It is listening only on port 22 and not 80. I am not sure if this makes a difference  or not.

T
ttielebein5-Regular MemberAnswer
5-Regular Member
August 18, 2016

Well, if you are connecting to ThingWorx with the provided URL above (http://localhost/Thingworx/Composer/index.html​), then you know that ThingWorx is running on port 80 (as none is specified and port 80 is the default for HTTP). So I don't think the comment about port 22 is entirely relevant. Might be worth a try just to swap those guys out since it is easy to check.

I don't think that "tls" is a valid parameter. If you are trying to set the encryption to false, I'd use:

"ws_connection": {

       "encryption": "none"

}

If swapping that syntax out doesn't help, try adding:

"certificates": {

     "validate": false,

     "allow_self_signed": true

}

Let me know how this goes. For a full list of valid parameters for this file, see the config.json.complete file, which should have been included in your EMS download.

    Terms & ConditionsAccessibility statement