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 HPUX

userdbck

userdbck(1M)															      userdbck(1M)

NAME

       userdbck - verify or fix information in the user database, /var/adm/userdb

SYNOPSIS

       [file]

DESCRIPTION

       verifies the information in the user database reports inconsistencies, and fixes problems.

       If no options and no arguments are specified, reports all data corruption problems in all files in

       If the option is also specified, each reported problem is repaired.

       If a file argument (hex 00-ff) is specified, only that file in the directory is verified.

   Options
       The following options are recognized:

	      Verify attributes.  Information in
		   is  used  to report any attribute that is not valid, not allowed in the user database, has an invalid value, or is allowed only
		   for a local user and the user is not in

	      Normally when the user database is disabled (see
		   userdb(4)), immediately exits without verifying or repairing the database.  The option overrides this and forces to	verify	or
		   repair the database.

	      Verify user names.
		   User names found in the database are reported if they do not exist in any of the repositories defined in This option could take
		   a long time on a system with many users.

	      Repair all data corruption problems that are found.
		   If this option is not specified, problems are reported but not repaired.

   Notes
       Only users who have read and write access to can run

RETURN VALUE

       exits with one of the following values:

       success: no inconsistencies were found
       inconsistencies were found and fixed
       invalid usage
       database is disabled; see
	  userdb(4)
       inconsistencies were found but not fixed,
	  because the option was not specified
       a problem was found that could not be fixed

EXAMPLES

       In the following example, all problems in the user database are reported but not repaired.

       In the following example, all problems in file are reported and repaired.

FILES

       user database
       security defaults configuration file
       security attributes description file

SEE ALSO

       userdbget(1M), userdbset(1M), userdb_read(3), security(4), userdb(4).

																      userdbck(1M)