It's all about the answers!

Ask a question

RTC Friend Applications not communicating


Glenn Watkins (8836) | asked Nov 27 '15, 8:57 a.m.
 Good Afternoon

We are using RTC v 5.0

This afternoon we are having an issue where the various applications are not communicating giving the below error. 
 Application: the root services resource at https://innovate.wesbank.co.za/vvc/rootservices for "/vvc" cannot be accessed:

java.net.SocketTimeoutException: Read timed out
Application: the service contribution resource at https://innovate.wesbank.co.za/vvc/scr for "/vvc" cannot be accessed:
java.net.SocketTimeoutException: Read timed out
Application: the root services resource at https://innovate.wesbank.co.za/dm/rootservices for "/dm" cannot be accessed:
java.net.SocketTimeoutException: Read timed out
Application: the service contribution resource at https://innovate.wesbank.co.za/dm/scr for "/dm" cannot be accessed:
java.net.SocketTimeoutException: Read timed out
Application: the root services resource at https://innovate.wesbank.co.za/rm/rootservices for "/rm" cannot be accessed:
java.net.SocketTimeoutException: Read timed out
Application: the service contribution resource at https://innovate.wesbank.co.za/rm/scr for "/rm" cannot be accessed:
java.net.SocketTimeoutException: Read timed out

Could anyone suggest a possible cause and solution.


Kind Regards

Glenn


Comments
Chao Wang commented Nov 27 '15, 11:20 a.m.

Hi Glenn,

Can you try hitting each of the scr URL from your browser? Are they accessible? Since the URL you have there doesn't have a port number, are you using a proxy server or are you just using 443 as the application server's listening port? If you are using proxy server can you try to use the Application server URL to access these scr links directly?
Are you using tomcat or Websphere for application server?
You can also take a look at the application logs and see if you see any errors in there.
Is your deployment standalone or distributed?


Glenn Watkins commented Dec 01 '15, 3:48 a.m.

 Hi Chao


Thank you for taking the time to answer, please see my answer below to Srinivas.

Best Regards
Glenn

Accepted answer


permanent link
Srinivas Mandava (15815) | answered Dec 01 '15, 12:21 a.m.
JAZZ DEVELOPER
 From the error it appears either the application servers or the proxy server is down.You might want to check if the application server or the proxy server is running first.
Glenn Watkins selected this answer as the correct answer

Comments
Glenn Watkins commented Dec 01 '15, 3:46 a.m.

 Hi Srinivas
Thanks for taking the time to answer.


What we found out was that the min and max heap allocations that was initially set on the W.A.S, was set to 6GB, this impacted the applications as they were running out of memory. We have subsequently increased the min and max allocation to 10GB and all is running smoothly again.

Best Regards
Glenn 

Your answer


Register or to post your answer.