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
Plack::Middleware::Auth::Basic(3pm)			User Contributed Perl Documentation		       Plack::Middleware::Auth::Basic(3pm)

NAME
Plack::Middleware::Auth::Basic - Simple basic authentication middleware SYNOPSIS
use Plack::Builder; my $app = sub { ... }; builder { enable "Auth::Basic", authenticator => &authen_cb; $app; }; sub authen_cb { my($username, $password) = @_; return $username eq 'admin' && $password eq 's3cr3t'; } DESCRIPTION
Plack::Middleware::Auth::Basic is a basic authentication handler for Plack. CONFIGURATION
authenticator A callback function that takes username and password supplied and returns whether the authentication succeeds. Required. Authenticator can also be an object that responds to "authenticate" method that takes username and password and returns boolean, so backends for Authen::Simple is perfect to use: use Authen::Simple::LDAP; enable "Auth::Basic", authenticator => Authen::Simple::LDAP->new(...); realm Realm name to display in the basic authentication dialog. Defaults to restricted area. LIMITATIONS
This middleware expects that the application has a full access to the headers sent by clients in PSGI environment. That is normally the case with standalone Perl PSGI web servers such as Starman or HTTP::Server::Simple::PSGI. However, in a web server configuration where you can't achieve this (i.e. using your application via Apache's mod_cgi), this middleware does not work since your application can't know the value of "Authorization:" header. If you use Apache as a web server and CGI to run your PSGI application, you can either a) compile Apache with "-DSECURITY_HOLE_PASS_AUTHORIZATION" option, or b) use mod_rewrite to pass the Authorization header to the application with the rewrite rule like following. RewriteEngine on RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L] AUTHOR
Tatsuhiko Miyagawa SEE ALSO
Plack perl v5.14.2 2012-06-21 Plack::Middleware::Auth::Basic(3pm)
All times are GMT -4. The time now is 10:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy