Caldarale, Charles R wrote:
From: Prakash P [mailto:prakash@gmail.com]
Subject: Tomcat 7.0.27 graceful shutdown fails
Ooops.
When I stop the tomcat by calling the shutdown.sh script or sending SIGTERM
signal to the java process it's throwing the following exception and the
shutdown get
Prakash P wrote:
W
hen I stop the tomcat by calling the shutdown.sh script or sending SIGTERM
signal to the java process it's throwing the following exception and the
shutdown get hung.
INFO: Destroying ProtocolHandler ["http-bio-80"]
Jul 11, 2013 10:01:58 AM org.apache.catalina.util.LifecycleMB
> From: Prakash P [mailto:prakash@gmail.com]
> Subject: Tomcat 7.0.27 graceful shutdown fails
> When I stop the tomcat by calling the shutdown.sh script or sending SIGTERM
> signal to the java process it's throwing the following exception and the
> shutdown get hung.
And a thread dump shows?
Konstantin Kolinko wrote:
2013/7/13 Jerry Lampi :
On Fri, Jul 12, 2013 at 4:21 PM, André Warnier wrote:
Jerry Lampi wrote:
On Fri, Jul 12, 2013 at 2:27 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jerry,
On 7/12/13 2:16
W
hen I stop the tomcat by calling the shutdown.sh script or sending SIGTERM
signal to the java process it's throwing the following exception and the
shutdown get hung.
INFO: Destroying ProtocolHandler ["http-bio-80"]
Jul 11, 2013 10:01:58 AM org.apache.catalina.util.LifecycleMBeanBase
unregister
2013/7/13 Jerry Lampi :
> On Fri, Jul 12, 2013 at 4:21 PM, André Warnier wrote:
>
>> Jerry Lampi wrote:
>>
>>> On Fri, Jul 12, 2013 at 2:27 PM, Christopher Schultz <
>>> ch...@christopherschultz.net> wrote:
>>>
>>> -BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jerry,
On
On Fri, Jul 12, 2013 at 4:21 PM, André Warnier wrote:
> Jerry Lampi wrote:
>
>> On Fri, Jul 12, 2013 at 2:27 PM, Christopher Schultz <
>> ch...@christopherschultz.net> wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA256
>>>
>>> Jerry,
>>>
>>> On 7/12/13 2:16 PM, Jerry Lampi wrote:
>
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 7/12/13 4:16 AM, André Warnier wrote:
Harsimranjit singh Kler wrote:
Using tomcat 6.I Always confused with
connectionTimeout
The number of milliseconds this *Connector* will wait, after
accepting a connecti
Jerry Lampi wrote:
On Fri, Jul 12, 2013 at 2:27 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jerry,
On 7/12/13 2:16 PM, Jerry Lampi wrote:
When we switched from tomcat 6.0.35 to 6.0.36, the initial load of
our sign on page bec
On Fri, Jul 12, 2013 at 2:27 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Jerry,
>
> On 7/12/13 2:16 PM, Jerry Lampi wrote:
> > When we switched from tomcat 6.0.35 to 6.0.36, the initial load of
> > our sign on page became e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 7/11/13 11:20 AM, chris derham wrote:
> On Thu, Jul 11, 2013 at 11:35 AM, Stefan Magnus Landrø
> wrote:
>>
>>
>> Den 11. juli 2013 kl. 15:44 skrev chris derham
>> :
>>
>>> Stefan,
>>>
but I'm not sure which values to tune. Proba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 7/12/13 4:16 AM, André Warnier wrote:
> Harsimranjit singh Kler wrote:
>> Using tomcat 6.I Always confused with
>>
>> connectionTimeout
>>
>> The number of milliseconds this *Connector* will wait, after
>> accepting a connection, for the
Jerry Lampi wrote:
When we switched from tomcat 6.0.35 to 6.0.36, the initial load of our sign
on page became extremely slow. In 6.0.35, it would load in about 2
seconds; in 6.0.36, it loads in about 60 seconds.
Our environment is an IBM mainframe running z/OS. Tomcat runs under USS
(Unix Syst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jerry,
On 7/12/13 2:16 PM, Jerry Lampi wrote:
> When we switched from tomcat 6.0.35 to 6.0.36, the initial load of
> our sign on page became extremely slow. In 6.0.35, it would load
> in about 2 seconds; in 6.0.36, it loads in about 60 seconds.
Ca
When we switched from tomcat 6.0.35 to 6.0.36, the initial load of our sign
on page became extremely slow. In 6.0.35, it would load in about 2
seconds; in 6.0.36, it loads in about 60 seconds.
Our environment is an IBM mainframe running z/OS. Tomcat runs under USS
(Unix System Services). The JV
On Fri, Jul 12, 2013 at 11:52 AM, Terence M. Bandoian wrote:
> Really generous responses.
That's very normal on this list. I have found Apache user lists to be very
(user) friendly. :)
On 7/11/2013 6:46 PM, Mark Eggers wrote:
> Comments mostly inline.
>
> Lots at the end - channeling James Fenimore Cooper.
>
> On 7/11/2013 3:26 PM, Mark Eggers wrote:
>> On 7/11/2013 3:06 PM, Caldarale, Charles R wrote:
From: john Matlock [mailto:johndmatl...@gmail.com] Subject: Re:
Movi
Thanks Chris for the suggestions. At this point I think it will be good
enough for our needs. Your comments have helped me understand the
process/inner-workings better.
Jeremy
On 7/11/13 10:39 AM, "Christopher Schultz"
wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA256
>
>Jeremy,
>
>On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Frank,
On 7/12/13 5:52 AM, Frank Sommer wrote:
> Hello,
>
> I'm using URL rewriting and recently upgraded my tomcat version
> from 6.0.32 to 6.0.33. I figured out that since 6.0.33 the
> jsessionid attribute is omitted in the Location header when T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 7/11/13 2:51 PM, Chris Cheshire wrote:
> I am working on migrating from TC6 to 7, and noticed in the log
> file the info messages about jars being needlessly scanned. Did all
> my googling and stuff and added all the jars mentioned to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 7/11/13 11:36 AM, André Warnier wrote:
> Leo Donahue - RDSA IT wrote:
>>> -Original Message- From: Tim Funk
>>> [mailto:funk...@apache.org] Subject: Re: [OT] WEB-INF
>>>
>>> Its a best practice to keep your jsp's inside of WEB-INF
> The Connector's are "shared" by all Hosts and all applications.
> So the connectionTimeout is already global for all requests that come in
> on the corresponding Connector port.
>
> This parameter is there specifically to fight one type of
> Denial-Of-Service attack, whereby some malicious client
Hello,
I'm using URL rewriting and recently upgraded my tomcat version from 6.0.32 to
6.0.33. I figured out that since 6.0.33 the jsessionid attribute is omitted in
the Location header when Tomcat forces a trailing slash redirect e.g. from
/mypath to /mypath/.
The effect is that the session inf
I would second reading the Tomcat security how-to. The OWASP guide to securing
tomcat : https://www.owasp.org/index.php/Securing_tomcat is also worth a look.
You could also consider starting tomcat with the security manager enabled...
although intially finding and configuring all the permissions
Hi Ognjen,
On 12.7.2013 6:51, Chanaka Dharmarathna wrote:
>
>> I'm using Tomcat 7.0.40 for hosted application. I have not configured any
>> user accounts for tomcat (admin, manager, user etc.). Recently my deployed
>> web application was damaged. Restarting tomcat recovered it back.
>>
>> But it s
Harsimranjit singh Kler wrote:
Using tomcat 6.I Always confused with
connectionTimeout
The number of milliseconds this *Connector* will wait, after accepting a
connection, for the request URI line to be presented. The default value is
6 (i.e. 60 seconds).
Helpful if anyone can explain.?
I
Chanaka,
On 12.7.2013 6:51, Chanaka Dharmarathna wrote:
I'm using Tomcat 7.0.40 for hosted application. I have not configured any
user accounts for tomcat (admin, manager, user etc.). Recently my deployed
web application was damaged. Restarting tomcat recovered it back.
But it seems someone tri
Using tomcat 6.I Always confused with
connectionTimeout
The number of milliseconds this *Connector* will wait, after accepting a
connection, for the request URI line to be presented. The default value is
6 (i.e. 60 seconds).
Helpful if anyone can explain.?
Is there any connector parameter w
28 matches
Mail list logo
