On 29 Nov 2011, at 01:05, Mike Wertheim m...@hyperreal.org wrote:
I have a web app that has been running on Tomcat 7.0.21 with APR 1.4.2
and Tomcat Native 1.1.20 on 64-bit Java 1.6.0.23 on CentOS Linux.
I upgraded half of my servers to Tomcat 7.0.23 and left the other half
at 7.0.21. I
Am 29.11.2011 01:28, schrieb Zampani, Michael:
-Original Message-
From: ma...@apache.org [mailto:ma...@apache.org]
Sent: Monday, November 28, 2011 4:02 PM
To: Tomcat Users List
Subject: Re: Tomcat-7.0.23 startup deadlocks
Zampani, Michael zamp...@amazon.com wrote:
Hi,
I'm trying to
Nuances:
- no errors are displayed in logs
- tomcat process can't be shutted down with shutdown.sh script
- http request on 80 port wait forever
- it's a multi host configuration
- the same setup works well on all previous build, including 7.0.22
- when lib/*.jar files of tomcat-7.0.23 are
Issue is Non Paged pool of tomcat increases until the OS crashes
On Tue, Nov 29, 2011 at 9:52 AM, Pid * p...@pidster.com wrote:
On 28 Nov 2011, at 18:09, Doron Tsur qbal...@gmail.com wrote:
Hi All
I've been having an issue in one of our production servers. The Non Paged
Pool creeps up
Am 29.11.2011 10:19, schrieb ~ ~:
Nuances:
- no errors are displayed in logs
- tomcat process can't be shutted down with shutdown.sh script
- http request on 80 port wait forever
- it's a multi host configuration
- the same setup works well on all previous build, including 7.0.22
- when
On 29/11/2011 09:32, Doron Tsur wrote:
Issue is Non Paged pool of tomcat increases until the OS crashes
Please post replies below the question so people can follow the
conversation.
p
--
[key:62590808]
signature.asc
Description: OpenPGP digital signature
On 29/11/2011 09:32, Doron Tsur wrote:
On Tue, Nov 29, 2011 at 9:52 AM, Pid * p...@pidster.com wrote:
On 28 Nov 2011, at 18:09, Doron Tsur qbal...@gmail.com wrote:
Hi All
I've been having an issue in one of our production servers. The Non Paged
Pool creeps up slowly until the system hangs
~ ~ a19...@mail.ru wrote:
Nuances:
- no errors are displayed in logs
- tomcat process can't be shutted down with shutdown.sh script
- http request on 80 port wait forever
- it's a mu
ti host configuration
- the same setup works well on all previous build, including 7.0.22
- when lib/*.jar files
2. where do i find Michael Zampani's report?
29 ноября 2011, 14:47 от ma...@apache.org:
~ ~ a19...@mail.ru wrote:
Nuances:
- no errors are displayed in logs
- tomcat process can't be shutted down with shutdown.sh script
- http request on 80 port wait forever
- it's a mu
ti host
Hi All,
I am using apache-tomcat-6.0.26.
My question is Tomcat Closed TIMEOUT or CLOSE_WAIT socket or is there any
mechanism to do the same.
My client is mobile based application.
Here is server.xml's connector.
Connector port=8080 protocol=org.apache.coyote.http11.Http11NioProtocol
Am 29.11.2011 12:34, schrieb ~ ~:
2. where do i find Michael Zampani's report?
http://www.mail-archive.com/users@tomcat.apache.org/msg94574.html
29 ноября 2011, 14:47 от ma...@apache.org:
~ ~ a19...@mail.ru wrote:
Nuances:
- no errors are displayed in logs
- tomcat process can't be
i''ve added inside Engine tag:
Realm className=org.apache.catalina.realm.LockOutRealm /
and now it works, but it worked without this tag prior to 7.0.23. what has
changed?
29 ноября 2011, 13:38 от Felix Schumacher felix.schumac...@internetallee.de:
Am 29.11.2011 10:19, schrieb ~ ~:
i''ve added inside Engine tag:
Realm className=org.apache.catalina.realm.LockOutRealm /
and now it works, but it worked without this tag prior to 7.0.23. what has
changed?
29 ноября 2011, 15:42 от Felix Schumacher felix.schumac...@internetallee.de:
Am 29.11.2011 12:34, schrieb ~ ~:
2.
so, regarding this:
http://www.mail-archive.com/users@tomcat.apache.org/msg94585.html
i think it's obvious it's a bug. so i was right ;)
synchonization bug in 7.0.23 release.
29 ноября 2011, 14:47 от ma...@apache.org:
~ ~ a19...@mail.ru wrote:
Nuances:
- no errors are displayed in logs
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gábor,
On 11/29/11 6:34 AM, Gábor Györkei wrote:
Thank you for your answer, I debugged into tomcat, and than I
found the bug in our code...
Glad you found the problem. What did it turn out to be? If you ask a
question on the list, it's always nice
Hi,
I am using Tomcat 5.0.27. I cannot use more then 2GB for Tomcat 5.0.27. Our OS
is 32-bit Linux. Can ane one tell me why this happening? And is there any way
to get rid of this problem and use lot of memory?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doron,
On 11/29/11 4:32 AM, Doron Tsur wrote:
Issue is Non Paged pool of tomcat increases until the OS crashes
Wow, the OS crashes? That really sounds like an OS bug to me.
Why do you suspect afd.dll is the cause (or symptom) of this problem?
Do
On Tue, Nov 29, 2011 at 16:05, hi tanin hi_ta...@yahoo.com wrote:
Hi,
I am using Tomcat 5.0.27. I cannot use more then 2GB for Tomcat 5.0.27. Our
OS is 32-bit Linux. Can ane one tell me why this happening? And is there any
way to get rid of this problem and use lot of memory?
Normally, the
that's a restriction of 32 bit systems. upgrade to 64 bit for more memory
requirements
depending on the kernel, you can go to 3.7gb for a 32 bit system
- Original Message -
From: hi tanin hi_ta...@yahoo.com
To: users@tomcat.apache.org
Sent: Tuesday, November 29, 2011 8:05:51 AM
Subject:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chandrakant,
On 11/29/11 6:37 AM, Chandrakant Solanki wrote:
I am using apache-tomcat-6.0.26.
Can you upgrade? That version is about 18 months old and some
important updates have been included in later releases.
My question is Tomcat Closed
Thanks for your reply. If i upgrated into 64-bit system then what will be the
memory limit for Tomcat 5.0.27? Is there any way to find out the mamimum
memoery limit ?
From: Francis GALIEGUE f...@one2team.com
To: Tomcat Users List users@tomcat.apache.org; hi
On Tue, Nov 29, 2011 at 16:26, hi tanin hi_ta...@yahoo.com wrote:
Thanks for your reply. If i upgrated into 64-bit system
__AND__ 64bit JDK...
then what will be the memory limit for Tomcat 5.0.27? Is there any way to
find out the mamimum memoery limit ?
More than you will be able to buy!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill,
On 11/28/11 7:08 PM, Bill Wang wrote:
Here I have the last question, what's the reload option, is it same
as stop/start?
According to markt (who is known to be occasionally trustworthy):
reload = stop + start
If it is, maybe I just need
Thank you very much for your nice reply
From: Francis GALIEGUE f...@one2team.com
To: Tomcat Users List users@tomcat.apache.org; hi tanin hi_ta...@yahoo.com
Sent: Tuesday, November 29, 2011 7:28 AM
Subject: Re: Server crash for memory limit
On Tue, Nov 29,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Francis,
On 11/29/11 10:28 AM, Francis GALIEGUE wrote:
On Tue, Nov 29, 2011 at 16:26, hi tanin hi_ta...@yahoo.com
wrote:
Thanks for your reply. If i upgrated into 64-bit system
__AND__ 64bit JDK...
Yes, this is the important part. You can
Christopher Schultz ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill,
On 11/28/11 7:08 PM, Bill Wang wrote:
Here I have the last question, what's the reload option, is it same
as stop/start?
According to markt (who is known to be occasionally
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject: Re: Server crash for memory limit
Yup. 2^64 is a *lot* of memory.
It's really just 2^48 on current x86-64 chips, but that's still more than you
can use.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR
I can run tomcat with examples scripts (i just install t 7.0.23) and i
have this error:
2011-11-29 17:38:43 org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [http-bio-8080]
2011-11-29 17:38:43 org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
On 11/29/11 11:31 AM, Caldarale, Charles R wrote:
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject: Re: Server crash for memory limit
Yup. 2^64 is a *lot* of memory.
It's really just 2^48 on current x86-64
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 11/29/11 11:15 AM, ma...@apache.org wrote:
Christopher Schultz ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
Bill,
On 11/28/11 7:08 PM, Bill Wang wrote:
Here I have the last question, what's the
Which two threads are waiting on the same lock? I don't see that in your
thread dump.
It's not obvious from the thread dump, but if I attach with jconsole, I see:
Name: main
State: WAITING on java.util.concurrent.FutureTask$Sync@6cc2a4
Name: pool-2-thread-1
State: BLOCKED on
Hi all,
I'd like to know it is possible to have equivalent functionality to the
extended document root provided by the WebSphere product. This feature
allows you to define a location outside the webapp to make contribution
without having to redeploy the application. This mechanism first checks if
On 29/11/2011 17:05, Christopher Schultz wrote:
Mark,
On 11/29/11 11:15 AM, ma...@apache.org wrote:
Christopher Schultz ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
Bill,
On 11/28/11 7:08 PM, Bill Wang wrote:
Here I have the last question, what's
Hello everyone,
Has anyone yet figured out how to cast the PoolableConnection that Tomcat 7 now
returns when you get a Connection from a DataSource as an OracleConnection? In
Tomcat 6 the connection was returned as T4CConnection and had no problem being
cast as an OracleConnection. Now, I
I think you are right. When no realm is configured in server.xml and in the
context of a webapp, StandardEngine tries to set a default realm.
That is guarded by a lock, which is held by the main thread.
To work around this problem, you can define a simple realm inside the
context of your
On 29/11/2011 19:27, Zampani, Michael wrote:
I think you are right. When no realm is configured in server.xml and in the
context of a webapp, StandardEngine tries to set a default realm.
That is guarded by a lock, which is held by the main thread.
To work around this problem, you can define a
An update on the situation... The Tomcat 7.0.23 servers tend to blow
up (refusing to accept connections), which the Tomcat 7.0.21 servers
didn't do. So I've downgraded all of the servers except one to
7.0.21. I'm keeping one of them at 7.0.23 in order to try to
troubleshoot this problem.
I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sirwiz,
On 11/29/11 11:51 AM, sir...@8host.pl wrote:
I can run tomcat with examples scripts (i just install t 7.0.23)
and i have this error:
2011-11-29 17:38:43 org.apache.coyote.AbstractProtocol start INFO:
Starting ProtocolHandler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason,
On 11/29/11 2:34 PM, Jason Perrone wrote:
Has anyone yet figured out how to cast the PoolableConnection that
Tomcat 7 now returns when you get a Connection from a DataSource
as an OracleConnection?
If you are using the standard pool
I did try getInnermostDelegate after casting to DelegatingConnection, but I did
not set accessToUnderlyingConnectionAllowed. I will try that tomorrow. Thanks.
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Tuesday, November 29, 2011 5:08 PM
To:
From: mike.werth...@gmail.com [mailto:mike.werth...@gmail.com] On Behalf Of
Mike Wertheim
Subject: Re: increase in file descriptor use from Tomcat 7.0.21 to 7.0.23
Number of those file descriptors that have filename with socket: 13783 (40%)
Number of those file descriptors that have
That was a typo. The 40% (next to socket) should have been 70%.
So it should say:
Number of open file descriptors according to ls -l /proc/1648/fd | wc
-l: 19478
Number of those file descriptors that have filename with socket: 13783 (70%)
Number of those file descriptors that have filename with
Hi,
I am trying to find best way to handle tomcat bounce in production
environments with out effecting connected users
please give me some suggestions, Is there a way to bounce tomcat with out
effecting connected users?
--
Thanks,
Srinivas.
Is there a way to change session timeouts in tomcat via JMX? I've only
seen the operation called expireSession, but not one that can change
the session timeout period.
The only way I've found so far to modify session timeouts is by
modifying web.xml and restarting Tomcat.
However, in our
Sure, using tomcat cluster and session replication.
On Wed, Nov 30, 2011 at 2:37 PM, Srinivas Chejerla
srinivascheje...@gmail.com wrote:
Hi,
I am trying to find best way to handle tomcat bounce in production
environments with out effecting connected users
please give me some suggestions,
On Wed, Nov 30, 2011 at 4:11 PM, Ellecer Valencia elle...@gmail.com wrote:
Is there a way to change session timeouts in tomcat via JMX? I've only
seen the operation called expireSession, but not one that can change
the session timeout period.
The only way I've found so far to modify
By the way, as I remember from the time I worked with Weblogic, which is up
to version 10, you need to restart the application, I say the application
not the server, when ever you change the timeout in the web.xml for that
app.
In Weblogic there is another file weblogic.xml where you can set the
Hi ,
Is there any cap on maximum memory that can be assigned to tomcat
on 32 bit Windows machines ? I have found out that even if we have 8GB
memory in the server , can not assign more 1.4/1.5 GB to Tomcat . I also
found this thread which reinforces what I have been seeing ? We are
On 14/10/11 04:04, Brian Burch wrote:
I will go quiet for a few days while I checkout 6.0.28 and get it to
build.
Phew! That took me longer than I expected I got 6.0.28 to build,
then ran all the unit tests, then debugged the SSO logic and started to
understand it.
Then I
49 matches
Mail list logo
