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
Old 04-06-2020
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?
 

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... (6 Replies)
Discussion started by: marty 600
6 Replies

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... (7 Replies)
Discussion started by: andresguillen
7 Replies

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... (1 Reply)
Discussion started by: Balasankar
1 Replies

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... (3 Replies)
Discussion started by: learnix
3 Replies
OCF_HEARTBEAT_TOMCAT(7) 					OCF resource agents					   OCF_HEARTBEAT_TOMCAT(7)

NAME
ocf_heartbeat_tomcat - Manages a Tomcat servlet environment instance SYNOPSIS
tomcat [start | stop | status | monitor | meta-data | validate-all] DESCRIPTION
Resource script for Tomcat. It manages a Tomcat instance as a cluster resource. SUPPORTED PARAMETERS
tomcat_name The name of the resource, added as a Java parameter in JAVA_OPTS: -Dname=<tomcat_name> to Tomcat process on start. Used to ensure process is still running and must be unique. (unique, optional, string, no default) script_log Log file, used during start and stop operations. (unique, optional, string, no default) tomcat_stop_timeout Time-out for stop operation. DEPRECATED (optional, integer, no default) tomcat_suspend_trialcount Maximum number of times to retry stop operation before suspending and killing Tomcat. DEPRECATED. Does not retry. (optional, integer, no default) tomcat_user The user who starts Tomcat. (optional, string, default "root") statusurl URL for state confirmation. (optional, string, no default) max_stop_time Number of seconds to wait during a stop before drastic measures (force kill) are used on the tomcat process. This number MUST be less than your cluster stop timeout for the resource. The default value is five seconds before the timeout value of stop operation. When it is over this value, it stops a process in kill commands. This parameter is only effective on Tomcat 6 or later. (optional, integer, no default) java_home Home directory of Java. (required, string, no default) java_opts Java JVM options used on start and stop. (optional, string, no default) catalina_home Home directory of Tomcat. (required, string, no default) catalina_base Instance directory of Tomcat (unique, optional, string, no default) catalina_out Log file name of Tomcat (unique, optional, string, no default) catalina_pid A PID file name for Tomcat. (unique, optional, string, no default) tomcat_start_script Absolute path to the custom tomcat start script to use. (optional, string, no default) tomcat_start_opts Tomcat start options. (optional, string, no default) catalina_opts Catalina options, for the start operation only. (optional, string, no default) catalina_tmpdir Temporary directory of Tomcat (unique, optional, string, no default) catalina_rotate_log Rotate catalina.out flag. (optional, boolean, default NO) catalina_rotatetime catalina.out rotation interval (seconds). (optional, integer, no default) java_endorsed_dirs Java_endorsed_dirs of tomcat (unique, optional, string, no default) logging_config Logging_config of tomcat (unique, optional, string, no default) logging_manager Logging_manager of tomcat (unique, optional, string, no default) SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 60s. stop Stops the resource. Suggested minimum timeout: 120s. status Performs a status check. Suggested minimum timeout: 60. monitor Performs a detailed status check. Suggested minimum timeout: 30s. Suggested interval: 10s. meta-data Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5s. validate-all Performs a validation of the resource configuration. Suggested minimum timeout: 5. EXAMPLE
The following is an example configuration for a tomcat resource using the crm(8) shell: primitive p_tomcat ocf:heartbeat:tomcat params java_home=string catalina_home=string op monitor depth="0" timeout="30s" interval="10s" SEE ALSO
http://www.linux-ha.org/wiki/tomcat_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents UNKNOWN 06/09/2014 OCF_HEARTBEAT_TOMCAT(7)
All times are GMT -4. The time now is 10:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy