Tech Support Forum banner
Not open for further replies.
1 - 1 of 1 Posts

· Registered
2 Posts
Discussion Starter · #1 ·

Our company runs an application on apache-tomcat-6.0.32, and since January it has been throwing "Connection Time Out" errors very frequently.

There are also other applications in the same server, and they run on apache-tomcat-7.0.12. However these apps do not throw the same error above.

Due to this, we suspect that the apache-tomcat is problematic, and after some research, we found this from an article :

Support for Apache Tomcat 6.0.x ended on 31st December 2016. There have been multiple security vulnerabilities announced since then that are very likely to affect the 6.0.x series (once a Tomcat version reaches EOL, it is not assessed to see if it is affected by new security vulnerability reports).
Thus, we suspect that this could be the cause for the problem.

Is there a temporary workaround for this? Just to stop the timeout errors.

In the mean time we are upgrading the current application to apache-tomcat-8.X.X. And since JOSSO is also used for end-to-end communication, we are also in the midst of upgrading JOSSO from version 1.8 to 2.4. However, this is taking forever, as the platform is new to us, and there are no proper answers/solutions in any of their documentation, official pages nor forums.

If there is a temporary solution to resolve the timeout errors, it would be great. Can timeout variables be added to or any other file in tomcat? Please suggest a proper link/guide for this workaround.
1 - 1 of 1 Posts
Not open for further replies.