Re: Tomcat locking up, not responding to requests

2004-11-21 Thread Stefan
Hi,

Using Tomcat 5.0.28 standalone on windows XP with JVM 1.4, I get this error
even though I have mapped my servlet in the web.xml file of the web app:


HTTP Status 404 - /loginResponse.do




type Status report

message /loginResponse.do

description The requested resource (/loginResponse.do) is not available.





Apache Tomcat/5.0.28


I've placed my webapp folder in Tomcats' webapps directory and all the jsp
pages run fine as do my POJO's for business logic, any ideas why the servlet
code could be causing problems?

The servlet mappings:


  code:

--

   loginResponse
com._ABC.authenticateAdmin   

adminPassword  
xxx
 
loginResponse
/loginResponse.do

--



It's my first time using Tomcat, been a Resin user for years ...

Thanks,

Stef



www.killersites.com


- Original Message - 
From: "Ben Simon" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Sunday, November 21, 2004 6:36 AM
Subject: Re: Tomcat locking up, not responding to requests


> >>>>> "ZK" == Zsolt Koppany <[EMAIL PROTECTED]> writes:
>
>  ZK> Check release notes!
>
> Naturally, after spending days on the issue - I posted to this list. And
> within minutes, discovered the information you mention below.
>
>  ZK> export LD_ASSUME_KERNEL=2.2.5
>  ZK> ...
>  ZK> Start tomcat
>
> Duh -- seems so obvious now.
>
> Thanks,
> Ben
>
> -- 
> Ben Simon Amazing Media, Inc.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Tomcat locking up, not responding to requests

2004-11-21 Thread Ben Simon
> "ZK" == Zsolt Koppany <[EMAIL PROTECTED]> writes:

 ZK> Check release notes!

Naturally, after spending days on the issue - I posted to this list. And
within minutes, discovered the information you mention below.

 ZK> export LD_ASSUME_KERNEL=2.2.5
 ZK> ...
 ZK> Start tomcat

Duh -- seems so obvious now.

Thanks,
Ben

-- 
Ben Simon Amazing Media, Inc.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Tomcat locking up, not responding to requests

2004-11-21 Thread Zsolt Koppany
Check release notes!

export LD_ASSUME_KERNEL=2.2.5
...
Start tomcat

Zsolt

> -Original Message-
> From: Ben Simon [mailto:[EMAIL PROTECTED]
> Sent: Sunday, November 21, 2004 3:48 AM
> To: [EMAIL PROTECTED]
> Subject: Tomcat locking up, not responding to requests
> 
> Howdy All,
> 
> I'm running Tomcat 5.0.28, on Linux (RedHat 9, kernel: 2.4.20-8smp) with
> java 1.4.2_06-b03 (from SUN) on a dual processor Intel box and seeing
> very odd behavior.  I'll start up tomcat, and use it to test/author a
> web application (struts based). At the end of the day, I'll leave the
> server running and go home. The next morning, I'll come in and try to
> hit the server, only to have any HTTP requests I make to it simply hang.
> They aren't rejected, timed out, or cause an exception. The requests
> just hang.
> 
> The load on the server is low and there appears to be plenty of memory
> available (-Xms100M, -Xmx256M).  There aren't any messages in the
> logs. When I do a `kill -3' on the process I get a stack trace (included
> below) and all the threads seem to be waiting for a connection.  Yet, the
> server simply hangs.  The only way I have found to proceed is to kill -9
> the process and to start it up again.
> 
> This is so odd. It appears as though simply leaving the machine alone
> (without any load or activity) eventually causes the server to lock up.
> 
> It's also worth mentioning I've seen this behavior on at least two
> different machines, so I'm confident that the issue isn't just bad
> hardware.
> 
> Anyone ever seen anything like this before?
> 
> Thanks in advance,
> Ben Simon
> 
> [Stack trace from a hung server]
> Full thread dump Java HotSpot(TM) Client VM (1.4.2_06-b03 mixed mode):
> 
> "NonBlockingPmapSerializer Worker: CampaignDaoFactory" daemon prio=1
> tid=0x5b510d40 nid=0x7b3 in Object.wait() [5b9ff000..5b9ff198]
>   at java.lang.Object.wait(Native Method)
>   at com.amazingmedia.sync.Daemon.daemonSleep(Daemon.java:331)
>   - locked <0x4651ba48> (a com.amazingmedia.sync.Daemon)
>   at com.amazingmedia.sync.Daemon.access$6(Daemon.java)
>   at com.amazingmedia.sync.Daemon$DaemonThread.run(Daemon.java:365)
> 
> "NonBlockingPmapSerializer Worker: DirectoryDaoFactory" daemon prio=1
> tid=0x5b513cc0 nid=0x7b3 in Object.wait() [5b97f000..5b97f218]
>   at java.lang.Object.wait(Native Method)
>   at com.amazingmedia.sync.Daemon.daemonSleep(Daemon.java:331)
>   - locked <0x4651bab8> (a com.amazingmedia.sync.Daemon)
>   at com.amazingmedia.sync.Daemon.access$6(Daemon.java)
>   at com.amazingmedia.sync.Daemon$DaemonThread.run(Daemon.java:365)
> 
> "NonBlockingPmapSerializer Worker: SimpleStorageService" daemon prio=1
> tid=0x5b506ba8 nid=0x7b3 in Object.wait() [5b8ff000..5b8ff298]
>   at java.lang.Object.wait(Native Method)
>   at com.amazingmedia.sync.Daemon.daemonSleep(Daemon.java:331)
>   - locked <0x464863e8> (a com.amazingmedia.sync.Daemon)
>   at com.amazingmedia.sync.Daemon.access$6(Daemon.java)
>   at com.amazingmedia.sync.Daemon$DaemonThread.run(Daemon.java:365)
> 
> "http-8453-Monitor" prio=1 tid=0x0851ed88 nid=0x7b3 in Object.wait()
> [5b87f000..5b87f318]
>   at java.lang.Object.wait(Native Method)
>   - waiting on <0x463fc900> (a
> org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable)
>   at
> org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable.run(ThreadPool.j
> ava:559)
>   - locked <0x463fc900> (a
> org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable)
>   at java.lang.Thread.run(Thread.java:534)
> 
> "http-8453-Processor4" daemon prio=1 tid=0x086d01b0 nid=0x7b3 runnable
> [5b7ff000..5b7ff398]
>   at java.net.PlainSocketImpl.socketAccept(Native Method)
>   at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353)
>   - locked <0x45d2f2d0> (a java.net.PlainSocketImpl)
>   at java.net.ServerSocket.implAccept(ServerSocket.java:448)
>   at
> com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(DashoA12275)
>   at
> org.apache.tomcat.util.net.jsse.JSSESocketFactory.acceptSocket(JSSESocketF
> actory.java:110)
>   at
> org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.ja
> va:368)
>   at
> org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:549)
>   at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.j
> ava:683)
>   at java.lang.Thread.run(Thread.java:534)
> 
> "http-8453-Processor3" daemon prio=1 tid=0x08523d28 nid=0x7b3 in
> Object.wait() [5b77f000..5b77f418]
>   at java.lang.Object.wait(Native Method)
>   - waiting on <0x463fcaf0> (a
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
>   at java.lang.Object.wait(Object.java:429)
>   at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.j
> ava:655)
>   - locked <0x463fcaf0> (a
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
>   at java.lang.Thread.run(Thread.java:534