You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by scabbage <gu...@gmail.com> on 2010/08/12 02:07:05 UTC
Tomcat 6 thread limit problem on Mac OS X Server 10.5.5
I did not configure the native webserver/tomcat server come with the Mac OS X
Server. I downloaded a Tomcat 6.0.29 and tried to run it on port 80 (using
sudo). I have been able to have the service up for no problem until
yesterday. Now I when I launch Tomcat, I got the following:
Aug 11, 2010 5:01:57 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path:
.:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
Aug 11, 2010 5:01:57 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-80
Aug 11, 2010 5:01:57 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 425 ms
Aug 11, 2010 5:01:57 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Aug 11, 2010 5:01:57 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.29
Aug 11, 2010 5:01:57 PM org.apache.catalina.startup.HostConfig
deployDescriptor
INFO: Deploying configuration descriptor host-manager.xml
Aug 11, 2010 5:01:57 PM org.apache.catalina.startup.HostConfig
deployDescriptor
INFO: Deploying configuration descriptor manager.xml
Aug 11, 2010 5:01:57 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory docs
Aug 11, 2010 5:01:57 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory examples
Aug 11, 2010 5:01:58 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory ROOT
Aug 11, 2010 5:01:58 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-80
Aug 11, 2010 5:01:58 PM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Aug 11, 2010 5:01:58 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/24 config=null
Aug 11, 2010 5:01:58 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 700 ms
Aug 11, 2010 5:02:10 PM org.apache.tomcat.util.net.JIoEndpoint
createWorkerThread
INFO: Maximum number of threads (200) created for connector with address
null and port 80
If I go the http://localhost/manager/status, I saw a whole bunch of threads
with:
P ? ? ? ? ? ?
Now I'm completely lost as to how these threads get spawned.
Can anyone give me some ideas?
Thanks.
--
View this message in context: http://old.nabble.com/Tomcat-6-thread-limit-problem-on-Mac-OS-X-Server-10.5.5-tp29414129p29414129.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat 6 thread limit problem on Mac OS X Server 10.5.5
Posted by scabbage <gu...@gmail.com>.
This just started to happened yesterday. Users of my website started to
experience a long delay when opening pages. I guess a DoS attack is
possible. Maybe I need to report it.
my server.xml is the default setting except for changing from port 8080 to
80.
n828cl wrote:
>
>> From: scabbage [mailto:guanshan@gmail.com]
>> Subject: Tomcat 6 thread limit problem on Mac OS X Server 10.5.5
>>
>> If I go the http://localhost/manager/status, I saw a whole
>> bunch of threads with:
>>
>> P ? ? ? ? ? ?
>
> I'm guessing that someone is probing your system. Seen any DoS attacks
> lately?
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you
> received this in error, please contact the sender and delete the e-mail
> and its attachments from all computers.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
--
View this message in context: http://old.nabble.com/Tomcat-6-thread-limit-problem-on-Mac-OS-X-Server-10.5.5-tp29414129p29420620.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat 6 thread limit problem on Mac OS X Server 10.5.5
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: scabbage [mailto:guanshan@gmail.com]
> Subject: Tomcat 6 thread limit problem on Mac OS X Server 10.5.5
>
> If I go the http://localhost/manager/status, I saw a whole
> bunch of threads with:
>
> P ? ? ? ? ? ?
I'm guessing that someone is probing your system. Seen any DoS attacks lately?
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 6 thread limit problem on Mac OS X Server 10.5.5
Posted by Pid <pi...@pidster.com>.
On 12/08/2010 01:07, scabbage wrote:
>
> I did not configure the native webserver/tomcat server come with the Mac OS X
> Server. I downloaded a Tomcat 6.0.29 and tried to run it on port 80 (using
> sudo). I have been able to have the service up for no problem until
> yesterday. Now I when I launch Tomcat, I got the following:
>
>
> Aug 11, 2010 5:01:57 PM org.apache.catalina.core.AprLifecycleListener init
> INFO: The APR based Apache Tomcat Native library which allows optimal
> performance in production environments was not found on the
> java.library.path:
> .:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
> Aug 11, 2010 5:01:57 PM org.apache.coyote.http11.Http11Protocol init
> INFO: Initializing Coyote HTTP/1.1 on http-80
> Aug 11, 2010 5:01:57 PM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 425 ms
> Aug 11, 2010 5:01:57 PM org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina
> Aug 11, 2010 5:01:57 PM org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/6.0.29
> Aug 11, 2010 5:01:57 PM org.apache.catalina.startup.HostConfig
> deployDescriptor
> INFO: Deploying configuration descriptor host-manager.xml
> Aug 11, 2010 5:01:57 PM org.apache.catalina.startup.HostConfig
> deployDescriptor
> INFO: Deploying configuration descriptor manager.xml
> Aug 11, 2010 5:01:57 PM org.apache.catalina.startup.HostConfig
> deployDirectory
> INFO: Deploying web application directory docs
> Aug 11, 2010 5:01:57 PM org.apache.catalina.startup.HostConfig
> deployDirectory
> INFO: Deploying web application directory examples
> Aug 11, 2010 5:01:58 PM org.apache.catalina.startup.HostConfig
> deployDirectory
> INFO: Deploying web application directory ROOT
> Aug 11, 2010 5:01:58 PM org.apache.coyote.http11.Http11Protocol start
> INFO: Starting Coyote HTTP/1.1 on http-80
> Aug 11, 2010 5:01:58 PM org.apache.jk.common.ChannelSocket init
> INFO: JK: ajp13 listening on /0.0.0.0:8009
> Aug 11, 2010 5:01:58 PM org.apache.jk.server.JkMain start
> INFO: Jk running ID=0 time=0/24 config=null
> Aug 11, 2010 5:01:58 PM org.apache.catalina.startup.Catalina start
> INFO: Server startup in 700 ms
> Aug 11, 2010 5:02:10 PM org.apache.tomcat.util.net.JIoEndpoint
> createWorkerThread
> INFO: Maximum number of threads (200) created for connector with address
> null and port 80
>
> If I go the http://localhost/manager/status, I saw a whole bunch of threads
> with:
>
> P ? ? ? ? ? ?
>
>
> Now I'm completely lost as to how these threads get spawned.
Please edit your server.xml to remove all comments and any sensitive
information, such as passwords - then post it, inline, here.
p