Skip to main content
1-Visitor
August 20, 2019
Solved

Socket error when trying to import entities

  • August 20, 2019
  • 1 reply
  • 1785 views

I am getting a socket error when I try to import entities from file, which is strange as I am importing from a local file. Binary and xml return the same error. The app log only returns the 5 lines below. Any help is appreciated.

 

2019-08-20 17:42:16.193-0400 [L: WARN] [O: c.t.s.s.p.PlatformSubsystem] [I: ] [U: ] [S: ] [T: pool-13-thread-1] Thingworx System Metrics_-----------------------------------------------------------------$
2019-08-20 17:42:26.271-0400 [L: ERROR] [O: E.c.t.w.Importer] [I: ] [U: Administrator] [S: ] [T: https-jsse-nio-443-exec-6] [message: java.net.SocketTimeoutException]
2019-08-20 17:42:26.274-0400 [L: ERROR] [O: c.t.w.Importer] [I: ] [U: Administrator] [S: ] [T: https-jsse-nio-443-exec-6] Invalid request: org.apache.catalina.connector.ClientAbortException: java.net.Soc$
2019-08-20 17:42:26.274-0400 [L: INFO] [O: c.t.migration] [I: ] [U: ] [S: ] [T: https-jsse-nio-443-exec-6] Start post migrating from version [8.3.0] to version [8.3.0] ...
2019-08-20 17:42:26.274-0400 [L: INFO] [O: c.t.migration] [I: ] [U: ] [S: ] [T: https-jsse-nio-443-exec-6] Finished post migrating from version [8.3.0] to version [8.3.0].

Best answer by clansdale

Turns out it was an error from WSEMS on the client side that occurred after I upgraded from TW 7.4 to 8.1.

1 reply

16-Pearl
August 22, 2019

@clansdale 

Maybe the firewall is blocking Binary/XML imports.

1. Can you check the value of the parameter connectionTimeout in server.xml of Tomcat?

2. Please send the Tomcat logs, we might find more relevant information there as well

For more info, you can refer to this article and this

 

 

16-Pearl
August 28, 2019

@clansdale I just wanted to follow up with you to see if previous response was helpful for your question?

If so, please indicate the appropriate response as the Accepted Solution for the benefit of other Community members who have the same question.

 

Thanks,

Vibhuti

 

clansdale1-VisitorAuthorAnswer
1-Visitor
August 29, 2019

Turns out it was an error from WSEMS on the client side that occurred after I upgraded from TW 7.4 to 8.1.