Resolving problems with web application Post: 303045649

Sponsored Content

Top Forums Web Development Resolving problems with web application Post 303045649 by anaigini45 on Monday 6th of April 2020 08:47:22 AM

04-06-2020

Registered User

Resolving problems with web application

Hi,

There is an application that our team uses that has been throwing "Connection Time Out" errors very often.
We want to resolve this problem ASAP, but we are at a dead end of how to go about resolving this problem.

The application that we use is apache-tomcat-6.0.32. In the same server that this version of tomcat runs, we also have applications running on apache-tomcat-7.0.12.
For the latter, there is no connection time out problems. After further investigation, I found an article that says :

Quote:

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).

So I believe that this is the cause for the problem ?

To resolve this our team has discussed, and the plan is to upgrade the tomcat to tomcat 8, and josso from 1.8 to josso 2. I have started the setup and config of josso2, however now I am stuck at getting the user credentials from our database.
I am sure this will take some time to resolve, although I cannot estimate how long.

Is there a way to temporarily stop the "Connection Time Out" problem? Is it possible to add some values/variables in workers.properties or any other config file in tomcat to resolve this problem temporarily?

anaigini45

View Public Profile for anaigini45

Find all posts by anaigini45

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Web Server - uploading Frontpage web - will there be problems??

hiya All, New to this Web site stuff. Will be installing Fedora's latest O/S (including Apache) - onto a spare PC Then... Gulp... setting up a Web server. Designing a Web site using WINDOWS FRONT PAGE 2002: * Simply easiest/quickiest way to knock up a basic site. * There won't be...

2. Web Development

Problems with an application

I gurus Can any guru of networking or applications can help me with this problem please. I Attached a document where I try to explain in detail the problem. So I attached a wireshark capture too. I attached a file where I can explain in detail the problem and a pcap file where you can observe...

3. Web Development

Web Application creation on UNIX

Hi, I would like to create an application with HTML front end in Unix. I am working on enterprise Unix server, so I could not install any add ons or software in my machine. but still i have super user permissions. I can change the permissions as i wish. I have built a small application with...

4. Web Development

Starting Web Application on Jboss

Hello, I installed Jboss EAP 6 on a remote Linux server in standalone mode, and deployed a HelloWorld war file successfully. Opened a browser on my PC and pointed to http://127.0.0.1:8080/filename. I can see “Hello World!” on my browser. However, if the browser points to http://server's...

LEARN ABOUT PHP

mongoconnectionexception

MONGOCONNECTIONEXCEPTION(3)						 1					       MONGOCONNECTIONEXCEPTION(3)

The MongoConnectionException class

INTRODUCTION

	Thrown when the driver fails to connect to the database.

	There are a number of possible error messages to help you diagnose the connection problem. These are:

	      o No  candidate  servers	found  Thrown when the driver cannot establish a connection to MongoDB (fulfilling the ReadPreferences, if
		specified).

	      o No server name given. This error occurs if you pass in "" as the server name, probably because of an typo with	string	interpola-
		tion, e.g., "$servr" instead of "$server".

	      o
		 failed to get host [hostname] or port [portnum] from [server].  This indicated that the server string was malformed. "[hostname]"
		and "[portnum]" will be as much as the driver could dicipher of it.

	      o Operation in progress Connecting to the database timed out.

	      o Transport endpoint is not connected Generally means that the connection string isn't correct, the driver couldn't  even  find  the
		database server.

	      o couldn't determine master No server in a replica set connection was identified as the primary.

	      o couldn't  get  host  info for [server] This indicated that DNS could not resolve the server address you gave. This could easily be
		caused by a typo, for example, "server" instead of "$server".

	      o Invalid Argument This can be caused by attempting to connect to a machine that is up but that the database isn't actually  running
		on. Make sure that you've started the database server before connecting.

	      o Permission  denied  This  means  that  the  socket could not be opened due to permissions issues. On Red Hat variants, this can be
		caused by a default setting that does not allow Apache to create network connections. You can override this setting by running:

	      $ /usr/sbin/setsebool -P httpd_can_network_connect 1

	If the error message is not listed above, it is probably an error from the C socket, and you can search the web for its usual cause.

CLASS SYNOPSIS

       MongoConnectionException

       MongoConnectionExceptionextends
       MongoException

PHP Documentation Group 											       MONGOCONNECTIONEXCEPTION(3)