Skip to main content

Analysis fails to open in TIBCO Spotfire Web Player with error: "Software caused connection abort: recv failed" seen in the logs

Rich Talbot
  • Created
Date Posted:
Product: TIBCO Spotfire®

Problem:

Analysis fails to open in TIBCO Spotfire Web Player with error: "Software caused connection abort: recv failed" seen in the logs


Solution:

Accessing a report through the TIBCO Spotfire Web Player might fail and show "Internal Server Error" message in the web page. In the server.log on the TIBCO Spotfire Server, an error trace similar to the one below may be seen: 

???????ERROR 2019-12-06T14:39:30,952-0500 [test@domain.com, #28, #887] wp.controller.WebPlayerExceptionController: Internal Server Error e783361a-2156-4ef9-b6e7-315b954c5cc7: I/O error on POST request for "https://testNodeManager.domain.com:9501/5b6418bb-b36b-57d0-9d6d-f6b757085798/SessionService/createSession": Software caused connection abort: recv failed; nested exception is java.net.SocketException: Software caused connection abort: recv failed org.springframework.web.client.ResourceAccessException: I/O error on POST request for "https://testNodeManager.domain.com:9501/5b6418bb-b36b-57d0-9d6d-f6b757085798/SessionService/createSession": Software caused connection abort: recv failed; nested exception is java.net.SocketException: Software caused connection abort: recv failed     at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:696) ~[spring-web.jar:5.0.10.RELEASE]     at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:662) ~[spring-web.jar:5.0.10.RELEASE]      Caused by: java.net.SocketException: Software caused connection abort: recv failed     at java.net.SocketInputStream.socketRead0(Native Method) ~[?:1.8.0_191]     at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) ~[?:1.8.0_191]     at java.net.SocketInputStream.read(SocketInputStream.java:171) ~[?:1.8.0_191]     at java.net.SocketInputStream.read(SocketInputStream.java:141) ~[?:1.8.0_191]     at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) ~[?:1.8.0_191]     at sun.security.ssl.InputRecord.read(InputRecord.java:503) ~[?:1.8.0_191]     at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:975) ~[?:1.8.0_191]     at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367) ~[?:1.8.0_191]     at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395) ~[?:1.8.0_191]     at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379) ~[?:1.8.0_191]     at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.jav
The above error can be seen if the TIBCO Web Player communication port on the Node Manager machine, which is set to 9501 by default, is blocked or unavailable. In that case, the server will fail to communicate with the Web Player. To resolve the issue, make sure this port is open and is not used by any other application.

Note: A temporary network glitch might also result in the same error trace. The reason again, would be connectivity issue on port 9501 on the Node Manager machine as a result of the network glitch. Doc: Ports

Related articles

Comments

0 comments

Article is closed for comments.