Skip to main content
R
RaajeevHDave1-Visitor
1-Visitor
August 3, 2018
Question

How Thingworx Connection Sever connect with Platform on Web Socket

  • August 3, 2018
  • 9 replies
  • 3324 views
 

We have connected around 20000 device with connection server we can see number of connections on connection server ( using netstat) but we cannot see same amount of connection on Platform.

 

How we can check this same on platform specially on WSS ( Web Socket) 

 

Look like we can see multiple thread on connection server (Based on connected agents) but this is transferring data on platform in single thread?

 

Please suggest

9 replies

R
Rick-Stanley5-Regular Member
5-Regular Member
August 3, 2018

That sounds like everything is working as designed, what problems are you seeing?

 

The Connection Server offloads work from the platform server by acting as a multiplexer for edge devices. It handles many connections to edge devices then sends and receives the messages for the edge devices with one connection to the platform.

    R
    RaajeevHDave1-VisitorAuthor
    1-Visitor
    August 3, 2018
    Thanks. Appreciate your quick response.
    I have couple of more questions.

    1. Does this connection goes through tomcat on platform or directly to postgres database. Because I cannot see any connection on tomcat console.

    2. Can we detect this connection on platform server?

    3. If this queue to platform then this will certainly decrease speed of overall server.

    Thanks in advance.

    M
    mmartin15-Regular Member
    5-Regular Member
    August 3, 2018
    1. The connections are through tomcat, not directly to the storage layer.
    2. Yes, you should see the connections via netstat, same as on the connection-server.
      Local address will by tomcat port (8080 in my case):
      tcp        0      0 172.72.0.2:8080         172.72.0.3:33180        ESTABLISHED
      tcp        0      0 172.72.0.2:8080         172.72.0.3:33182        ESTABLISHED
      tcp        0      0 172.72.0.2:8080         172.72.0.3:33176        ESTABLISHED
      tcp        0      0 172.72.0.2:8080         172.72.0.3:33174        ESTABLISHED
      tcp        0      0 172.72.0.2:8080         172.72.0.3:33184        ESTABLISHED
    3. The messages arriving from the 20K devices are not queued.  The protocol can handle multiple concurrent requests without any head-of-line blocking issues, as would be the case with HTTP.
    Terms & ConditionsAccessibility statement