Ajp12Interceptor: HANDLER THREAD PROBLEM
Hi All, I have set up a website on my test machines using Apache1.3 Tomcat3.3.2 and mod_jk. While connecting to http://localhost/ I get the following error shown for Tomcat. Also attaching the error.log of httpd.conf. 2004-12-02 14:11:51 - Ctx() : Class not found: TOMCAT/JSP/index.jsp 2004-12-02 14:11:51 - Ctx() : Status code:404 request:R( + /index.jsp + null) m sg:null 2004-12-02 14:11:53 - Ctx() : Status code:404 request:R( + /index.jsp + null) m sg:null 2004-12-02 14:17:48 - Ctx() : Status code:404 request:R( + /index.jsp + null) m sg:null 2004-12-02 14:26:24 - Ajp12Interceptor: HANDLER THREAD PROBLEM - java.io.IOExcep tion: Stream broken at org.apache.tomcat.modules.server.Ajp12.readNextRequest(Ajp12.java:277 ) at org.apache.tomcat.modules.server.AJP12Request.readNextRequest(Ajp12In terceptor.java:215) at org.apache.tomcat.modules.server.Ajp12Interceptor.processConnection(A jp12Interceptor.java:178) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java :571) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP ool.java:644) at java.lang.Thread.run(Thread.java:534) error.log- [Thu Dec 02 14:17:36 2004] [warn] module mod_jk.c is already added, skipping program files/apache group/apache/htdocs/manual/urlmapping.html [Wed Dec 01 16:16:58 2004] [error] [client 127.0.0.1] File does not exist: d:/program files/apache group/apache/htdocs/manual/urlmapping.html [Wed Dec 01 16:17:34 2004] [error] [client 127.0.0.1] File does not exist: d:/program files/apache group/apache/htdocs/manual/urlmapping.html [Wed Dec 01 16:54:14 2004] [error] [client 127.0.0.1] File does not exist: d:/program files/apache group/apache/htdocs/manual/urlmapping.html Apache server shutdown initiated... Apache server shutdown initiated... [Wed Dec 01 19:13:38 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-on.gif [Wed Dec 01 19:13:38 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-off.gif [Wed Dec 01 19:14:25 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-on.gif [Wed Dec 01 19:14:25 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-off.gif [Wed Dec 01 19:15:24 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-on.gif [Wed Dec 01 19:15:24 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-off.gif [Wed Dec 01 21:52:25 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-on.gif [Wed Dec 01 21:52:25 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-off.gif [Thu Dec 02 12:08:50 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-on.gif [Thu Dec 02 12:08:50 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-off.gif [Thu Dec 02 13:49:40 2004] [warn] module mod_jk.c is already added, skipping [Thu Dec 02 14:10:57 2004] [warn] module mod_jk.c is already added, skipping [Thu Dec 02 14:12:32 2004] [warn] module mod_jk.c is already added, skipping [Thu Dec 02 14:17:35 2004] [warn] module mod_jk.c is already added, skipping Could you please show me a way ? Thanks. Mayuresh.
Re: Ajp12Interceptor: HANDLER THREAD PROBLEM
It looks like you DocumentRoot in Apache isn't matching up with the ROOT context in Tomcat. As a start, you could find the ApacheConfig element in server.xml, and add the attribute 'noRoot=false'. Then run $TOMCAT_HOME/bin/tomcat run -jkconf You should then compare $TOMCAT_HOME/conf/auto/mod_jk.conf with your Apache configuration as a hint for what isn't matching up. Mayuresh Kshirsagar [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hi All, I have set up a website on my test machines using Apache1.3 Tomcat3.3.2 and mod_jk. While connecting to http://localhost/ I get the following error shown for Tomcat. Also attaching the error.log of httpd.conf. 2004-12-02 14:11:51 - Ctx() : Class not found: TOMCAT/JSP/index.jsp 2004-12-02 14:11:51 - Ctx() : Status code:404 request:R( + /index.jsp + null) m sg:null 2004-12-02 14:11:53 - Ctx() : Status code:404 request:R( + /index.jsp + null) m sg:null 2004-12-02 14:17:48 - Ctx() : Status code:404 request:R( + /index.jsp + null) m sg:null 2004-12-02 14:26:24 - Ajp12Interceptor: HANDLER THREAD PROBLEM - java.io.IOExcep tion: Stream broken at org.apache.tomcat.modules.server.Ajp12.readNextRequest(Ajp12.java:277 ) at org.apache.tomcat.modules.server.AJP12Request.readNextRequest(Ajp12In terceptor.java:215) at org.apache.tomcat.modules.server.Ajp12Interceptor.processConnection(A jp12Interceptor.java:178) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java :571) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP ool.java:644) at java.lang.Thread.run(Thread.java:534) error.log- [Thu Dec 02 14:17:36 2004] [warn] module mod_jk.c is already added, skipping program files/apache group/apache/htdocs/manual/urlmapping.html [Wed Dec 01 16:16:58 2004] [error] [client 127.0.0.1] File does not exist: d:/program files/apache group/apache/htdocs/manual/urlmapping.html [Wed Dec 01 16:17:34 2004] [error] [client 127.0.0.1] File does not exist: d:/program files/apache group/apache/htdocs/manual/urlmapping.html [Wed Dec 01 16:54:14 2004] [error] [client 127.0.0.1] File does not exist: d:/program files/apache group/apache/htdocs/manual/urlmapping.html Apache server shutdown initiated... Apache server shutdown initiated... [Wed Dec 01 19:13:38 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-on.gif [Wed Dec 01 19:13:38 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-off.gif [Wed Dec 01 19:14:25 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-on.gif [Wed Dec 01 19:14:25 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-off.gif [Wed Dec 01 19:15:24 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-on.gif [Wed Dec 01 19:15:24 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-off.gif [Wed Dec 01 21:52:25 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-on.gif [Wed Dec 01 21:52:25 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-off.gif [Thu Dec 02 12:08:50 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-on.gif [Thu Dec 02 12:08:50 2004] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/support.cp.net/images/myprofile-off.gif [Thu Dec 02 13:49:40 2004] [warn] module mod_jk.c is already added, skipping [Thu Dec 02 14:10:57 2004] [warn] module mod_jk.c is already added, skipping [Thu Dec 02 14:12:32 2004] [warn] module mod_jk.c is already added, skipping [Thu Dec 02 14:17:35 2004] [warn] module mod_jk.c is already added, skipping Could you please show me a way ? Thanks. Mayuresh. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
HANDLER THREAD PROBLEM
Hi all: I'm using Tomcat 3.2.3 with Apache. A few days ago often an error apperar when tomcat is running. The Exception is: HANDLER THREAD PROBLEM: java.io.IOException: Stream closed prematurely java.io.IOException: Stream closed prematurely at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Ajp1 2ConnectionHandler.java:422) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection (Ajp12ConnectionHandler.java:147) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501) at java.lang.Thread.run(Thread.java:536) The tomcat continue running. I have read that there is more people with the same problem but I haven´t found a solution. Any suggestion. Thank you. - Miguel Ángel Medina López Logic Factory: www.logic-factory.com Granada - España -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
HANDLER THREAD PROBLEM: java.io.IOException: Stream broken
Hi Everyone, While testing Tomcat Tomcat 3.2.4 with ./startup.sh it works perfectly with :8080 But it gets stucked after the line PoolTcpConnector: Starting Ajp12ConnectionHandler on 8007 and when it is stucked it does work with the IP:8080 but when I try to access with IP:8007 the server receives the following error HANDLER THREAD PROBLEM: java.io.IOException: Stream broken java.io.IOException: Stream broken at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Ajp12ConnectionHandler.java:426) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection(Ajp12ConnectionHandler.java:147) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501) at java.lang.Thread.run(Thread.java:484) Can Anyone help Me?? Thanks in advance Vikas -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
HANDLER THREAD PROBLEM
Hi. I startup tomcat and every thing es ok. but when I try to access http://host:8007 in the host console view the follow IOException: HANDLER THREAD PROBLEM: java.io.IOException: Stream broken java.io.IOException: Stream broken at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Ajp12ConnectionHandler.java:426) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection(Ajp12ConnectionHandler.java:147) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501) at java.lang.Thread.run(Thread.java:484) what happen? thanks! Juan
RE: HANDLER THREAD PROBLEM
Your are doing a request to the port that talks to apache and tomcat talk to.. That is not a protocol like http, it is the ajp protocol.. You have to do a request to http://host or http://host:8080. Mvgr, Martin -Original Message- From: Juan Andres Sanin Pineda [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 06, 2001 5:03 AM To: [EMAIL PROTECTED] Subject: HANDLER THREAD PROBLEM Hi. I startup tomcat and every thing es ok. but when I try to access http://host:8007 in the host console view the follow IOException: HANDLER THREAD PROBLEM: java.io.IOException: Stream broken java.io.IOException: Stream broken at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRe quest(Ajp12ConnectionHandler.java:426) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.process Connection(Ajp12ConnectionHandler.java:147) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501) at java.lang.Thread.run(Thread.java:484) what happen? thanks! Juan
HANDLER THREAD PROBLEM
I was getting this error, I rebuilt and it went away but my buddy is getting it on his development box. It happens when you make an http request to tomcat , I believe its an error in .conf or .xml and I wonder if anyone is familiar with it. thanksTIA(); rick HANDLER THREAD PROBLEM: java.lang.NullPointerException java.lang.NullPointerException at org.apache.tomcat.core.ContextManager.handleError(ContextManager.java:644) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:566) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection (Ajp12ConnectionHandler.java:156) at org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java:338 ) at java.lang.Thread.run(Thread.java:479)
HANDLER THREAD PROBLEM when accessing servlet
is it really necessary to recompile the mod_jk.so just so that Tomcat will run fine with Apache? I have Apache web server and jakarta-tomcat-3.2.1 running on red hat linux 6. I am running tomcat using the startup.sh script (I guess this means it's stand-alone). I get an error while accessing a servlet in my defined context path but the example was working well. Error is: HANDLER THREAD PROBLEM: java.io.IOException: Stream broken java.io.IOException: Stream broken at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Ajp1 2ConnectionHandler.java:386) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection (Ajp12ConnectionHandler.java:134) at org.apache.tomcat.service.TcpWorkerThread.run(PoolTcpEndpoint.java:366) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:411) at java.lang.Thread.run(Thread.java:484) Any ideas? TIA. :^) A chain is only as strong as its weakest link. Ricky Y. Artigas Analyst/Programmer Information Technology Division Easycall Communications Phils., Inc. - Easycall Internet - 418 Arayat St., Mandaluyong City 1550, Philippines Personal WAP Site: http://www.buzzed.co.uk/mobile/?rya Company Website: http://www.easycall.com.ph Tel.no: (+632) 5338001 ext.6574 Mobile:(+63) 0917-8951783 Pager: 141-002955 Email: [EMAIL PROTECTED] --- IMPORTANT NOTICE: This message (and any attachment hereto) may contain privileged and/or confidential information specific to EasyCall. If you are not the intended addressee indicated in this message, you may not copy or disseminate this message (or any attachment hereto) to anyone. Instead, please destroy this message (and any attachment hereto), and kindly notify the sender by reply email. Any information in this message (and any attachment thereto) that do not relate to the official business of EasyCall shall be understood as neither given nor endorsed by the company. -Original Message- From: Noel E. Lecaros [SMTP:[EMAIL PROTECTED]] Sent: Monday, May 07, 2001 6:02 PM To: [EMAIL PROTECTED] Subject: Re: wired CLASSPATH behaviour Hi, Roman Just a thought, but have you tried RENAMING the file db2java.zip to db2java.jar? Regards, Noel Lecaros Gerteis, Roman wrote: Hay there, when I was deploying a application on Tomcat 3.2.1 we had some really wired Problems with CLASSPATH issues. First of all this is the environment: * apache 1.3.14 * mod_jk.so * tomcat 3.2.1 on Redhat 6.2 JVM 1.3 (Sun distribution) ok. So we were putting JDBC Drivers of IBM (db2java.zip) on various places where we should be able to put them. 1. we put it into the $TOMCAT_HOME/lib/ to be include for whole tomcat. (did not work) 2. we put it into the CLASSPATH environment inside the $TOMCAT_HOME/tomcat.sh script (did not work) 3. we put it into $TOMCAT_HOME/webapps/our_app/WEB-INF/lib/ (did not work) 4. we unpacked the zip file and put the package tree under $TOMCAT_HOME/webapps/our_app/WEB-INF/classes/ -- YUHEE, it worked. the depressing part of it was, that db2java.zip and the _right_ Path to it was shown in the CLASSPATH variable on every of the setups (System.out.println, or shellscript ECHO). But the JDBC Driver Manager dumped no suitable driver found. It took me quite a lot of time to make the application run, cause there was no reason for the failure (If you have a package in your classpath, then you would suggest that it is loaded, right?). Anyways. The whole adventure brings me to the conclusion that either the CLASSPATH environment of Sun JDK 1.3 for Linux is not working properly or .. the dynamic loading of packages of TomCat is not fully reliable (which I honestly do not believe). Does anyone had similar Problems, and can someone give me a tip for where to put JDBC Driver packages inside a Webapp? (WEB-INF/lib/ I thought, but) thx. and regards roman
AW: HANDLER THREAD PROBLEM when accessing servlet
Hay, yes it's necessary to compile mod_jk.so, but it's really easy. get the Tomcat ressources and do exactly what is said in: http://jakarta.apache.org/tomcat/jakarta-tomcat/src/doc/mod_jk-howto.html#s6 2 The build depends on OS and Apache Version so normally the distributed binary is matching exactly one environment exapmle. (Probably not yours ;) If you start the startup.sh (default configuration) TomCat runs standalone and with the interface for Apache connections. (Port 8080 is standalone Version, Port 8007 is for mod_jk connections) Therefore you can try both. If Apache works well with your Tomcat you can remove the: Connector className=org.apache.tomcat.service.PoolTcpConnector Parameter name=handler value=org.apache.tomcat.service.http.HttpConnectionHandler/ Parameter name=port value=8080/ /Connector Entry form $TOMCATHOME/conf/server.xml to run Tomcat not standalone anymore. Regards. roman -Ursprüngliche Nachricht- Von: Artigas, Ricardo Y. [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 7. Mai 2001 12:27 An: [EMAIL PROTECTED] Betreff: HANDLER THREAD PROBLEM when accessing servlet is it really necessary to recompile the mod_jk.so just so that Tomcat will run fine with Apache? I have Apache web server and jakarta-tomcat-3.2.1 running on red hat linux 6. I am running tomcat using the startup.sh script (I guess this means it's stand-alone). I get an error while accessing a servlet in my defined context path but the example was working well. Error is: HANDLER THREAD PROBLEM: java.io.IOException: Stream broken java.io.IOException: Stream broken at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Ajp1 2ConnectionHandler.java:386) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection (Ajp12ConnectionHandler.java:134) at org.apache.tomcat.service.TcpWorkerThread.run(PoolTcpEndpoint.java:366) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:411) at java.lang.Thread.run(Thread.java:484) Any ideas? TIA. :^) A chain is only as strong as its weakest link. Ricky Y. Artigas Analyst/Programmer Information Technology Division Easycall Communications Phils., Inc. - Easycall Internet - 418 Arayat St., Mandaluyong City 1550, Philippines Personal WAP Site: http://www.buzzed.co.uk/mobile/?rya Company Website: http://www.easycall.com.ph Tel.no: (+632) 5338001 ext.6574 Mobile:(+63) 0917-8951783 Pager: 141-002955 Email: [EMAIL PROTECTED] --- IMPORTANT NOTICE: This message (and any attachment hereto) may contain privileged and/or confidential information specific to EasyCall. If you are not the intended addressee indicated in this message, you may not copy or disseminate this message (or any attachment hereto) to anyone. Instead, please destroy this message (and any attachment hereto), and kindly notify the sender by reply email. Any information in this message (and any attachment thereto) that do not relate to the official business of EasyCall shall be understood as neither given nor endorsed by the company. -Original Message- From: Noel E. Lecaros [SMTP:[EMAIL PROTECTED]] Sent: Monday, May 07, 2001 6:02 PM To: [EMAIL PROTECTED] Subject: Re: wired CLASSPATH behaviour Hi, Roman Just a thought, but have you tried RENAMING the file db2java.zip to db2java.jar? Regards, Noel Lecaros Gerteis, Roman wrote: Hay there, when I was deploying a application on Tomcat 3.2.1 we had some really wired Problems with CLASSPATH issues. First of all this is the environment: * apache 1.3.14 * mod_jk.so * tomcat 3.2.1 on Redhat 6.2 JVM 1.3 (Sun distribution) ok. So we were putting JDBC Drivers of IBM (db2java.zip) on various places where we should be able to put them. 1. we put it into the $TOMCAT_HOME/lib/ to be include for whole tomcat. (did not work) 2. we put it into the CLASSPATH environment inside the $TOMCAT_HOME/tomcat.sh script (did not work) 3. we put it into $TOMCAT_HOME/webapps/our_app/WEB-INF/lib/ (did not work) 4. we unpacked the zip file and put the package tree under $TOMCAT_HOME/webapps/our_app/WEB-INF/classes/ -- YUHEE, it worked. the depressing part of it was, that db2java.zip and the _right_ Path to it was shown in the CLASSPATH variable on every of the setups (System.out.println, or shellscript ECHO). But the JDBC Driver Manager dumped no suitable driver found. It took me quite a lot of time to make the application run, cause there was no reason for the failure (If you have a package in your classpath, then you would suggest that it is loaded, right?). Anyways. The whole adventure brings me to the conclusion that either the CLASSPATH environment of Sun JDK 1.3 for Linux is not working properly or .. the dynamic loading of packages of TomCat is not fully reliable (which I honestly do not believe
tomcat HANDLER THREAD PROBLEM
hi, i'm using tomcat with apache on RedHat 7.0 i'm using a WebPerformance software to test my webpage with multiple users (100 users) in the beginning it all works good but after about 15 minutes of stress test i start getting this error with tomcat . *** HANDLER THREAD PROBLEM: java.lang.NullPointerException java.lang.NullPointerException at org.apache.tomcat.service.connector.AJP12ResponseAdapter.sendStatus(Ajp12Con nectionHandler.java:439) at org.apache.tomcat.service.http.HttpResponseAdapter.endHeaders(HttpResponseAd apter.java(Compiled Code)) at org.apache.tomcat.core.BufferedServletOutputStream.sendHeaders(BufferedServl etOutputStream.java:127) at org.apache.tomcat.core.BufferedServletOutputStream.reallyFlush(BufferedServl etOutputStream.java(Compiled Code)) at org.apache.tomcat.core.ResponseImpl.finish(ResponseImpl.java(Compiled Code)) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection (Ajp12ConnectionHandler.java:158) at org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java(Com piled Code)) *** Does anyone know what may have caused this error and is there anyway to fix it ? thanks Georges
Handler Thread Problem
Anybody know why I'm getting this? The access thru Apache works fine. but, when trying to access directly thru Tomcat I get th following exception on the server side: Redirecting to /recruiting/jsp/Login.jsp... Redirecting to /recruiting/jsp/Login.jsp?showLoginError=true... HANDLER THREAD PROBLEM: java.io.IOException: Stream broken java.io.IOException: Stream broken at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Ajp1 2ConnectionHandler.java:386) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection (Ajp12ConnectionHandler.java:134) at org.apache.tomcat.service.TcpWorkerThread.run(PoolTcpEndpoint.java:366) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:411) at java.lang.Thread.run(Thread.java:484) From what I understand about Tomcat I shouldn't have to have Apache up and running to access the application directly with Tomcat. Thanks, -Ben
HANDLER THREAD PROBLEM: java.net.SocketException Invalid argument
I am using Linux RedHat 7.0, Tomcat 3.2.1, Apache 1.3.14-3and Iget anexception when I try to route the requestto tomcat through Apache. The error is as following # HANDLER THREAD PROBLEM: java.net.SocketException: Invalid argumentjava.net.SocketException: Invalid argument at java.net.PlainSocketImpl.socketSetOption(PlainSocketImpl.java:native) at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:158) at java.net.Socket.setSoLinger(Socket.java:106) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection(Ajp12ConnectionHandler.java:122) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498) at java.lang.Thread.run(Thread.java:325) Thank you for your help. Mike Mikolajczyk
Re: HANDLER THREAD PROBLEM: java.net.SocketException Invalid argument
I finally figured it out. The problem is with
the version of java I was using:
(Kaffe Virtual MachineCopyright (c) 1996-2000Transvirtual
Technologies, Inc. All rights reservedEngine: Just-in-time
v3 Version: 1.0.6 Java Version: 1.1)
After pointing Tomcat to:
{java version "1.3.0"Java(TM) 2 Runtime Environment, Standard
Edition (build 1.3.0)Java HotSpot(TM) Client VM (build 1.3.0, mixed
mode)}
everything worked fine. Easy fix, sometimes you forget to look at
thosesimple things first.
Michael Mikolajczyk
- Original Message -
From:
Michael
Mikolajczyk
To: [EMAIL PROTECTED]
Sent: Thursday, February 15, 2001 12:30
PM
Subject: HANDLER THREAD PROBLEM:
java.net.SocketException Invalid argument
I am using Linux RedHat 7.0, Tomcat 3.2.1, Apache 1.3.14-3and
Iget anexception when I try to route the requestto tomcat
through Apache.
The error is as following
# HANDLER THREAD PROBLEM: java.net.SocketException: Invalid
argumentjava.net.SocketException: Invalid
argument at
java.net.PlainSocketImpl.socketSetOption(PlainSocketImpl.java:native)
at
java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:158)
at
java.net.Socket.setSoLinger(Socket.java:106)
at
org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection(Ajp12ConnectionHandler.java:122)
at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
at java.lang.Thread.run(Thread.java:325)
Thank you for your help.
Mike Mikolajczyk
Handler thread problem - How to overcome?
Hello All, I am getting the following exception when I use Tomcat Apache combination. HANDLER THREAD PROBLEM: java.Lang.NullPointerException. at org.apache.tomcat.service.http.HttpResponseAdapter.endHeaders (HttpResponseAdapter.java:111). Has any one got such exception before. If so please indicate how to overcome such problem. I am using Tomcat(3.1) apache( 3.1.12) Thanking you Sriranga. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Handler Thread Problem
Community, I'm getting the following error message when a request comes in for port 8007? I know I have to include some sort of threading instructions for tomcat to handle the request. The only problem I have is how do I know what is the proper thread handling scheme? Any thoughts, idea's or tip's is greatly appreciated. 2001-02-03 14:52:02 - Ajp12Interceptor: HANDLER THREAD PROBLEM - java.io.IOException: Stream broken at org.apache.tomcat.modules.server.Ajp12.readNextRequest(Ajp12.java:300) at org.apache.tomcat.modules.server.AJP12Request.readNextRequest(Ajp12Interceptor.java:223) at org.apache.tomcat.modules.server.Ajp12Interceptor.processConnection(Ajp12Interceptor.java:186) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:426) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:497) at java.lang.Thread.run(Thread.java:484) Regards, Nael Neomar, Inc Product Support [EMAIL PROTECTED]
Re: Handler Thread Problem
I think port 8007 is used for connection to Apache. Are you trying to use it as a regular web service port? Original Message dated 2/3/01, 6:58:01 PM Author: Nael Mohammad [EMAIL PROTECTED] Re: Handler Thread Problem: Community, I'm getting the following error message when a request comes in for port 8007? I know I have to include some sort of threading instructions for tomcat to handle the request. The only problem I have is how do I know what is the proper thread handling scheme? Any thoughts, idea's or tip's is greatly appreciated. 2001-02-03 14:52:02 - Ajp12Interceptor: HANDLER THREAD PROBLE M - java.io.IOException: Stream broken at org.apache.tomcat.modules.server.Ajp12.readNextRequest(Ajp12.java:300 ) at org.apache.tomcat.modules.server.AJP12Request.readNextRequest(Ajp12In terceptor.java:223) at org.apache.tomcat.modules.server.Ajp12Interceptor.processConnection(A jp12Interceptor.java:186) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java :426) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP ool.java:497) at java.lang.Thread.run(Thread.java:484) Regards, Nael Neomar, Inc Product Support [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Handler Thread Problem
You're right, I figured that out, that Apache makes the request for 8007 to tomcat. So tomcat is listening to 8007 from apache. Thanks, Now time to conquer cocoon.!!! -Original Message- From: Chris Janicki [mailto:[EMAIL PROTECTED]] Sent: Saturday, February 03, 2001 6:41 PM To: [EMAIL PROTECTED] Subject: Re: Handler Thread Problem I think port 8007 is used for connection to Apache. Are you trying to use it as a regular web service port? Original Message dated 2/3/01, 6:58:01 PM Author: Nael Mohammad [EMAIL PROTECTED] Re: Handler Thread Problem: Community, I'm getting the following error message when a request comes in for port 8007? I know I have to include some sort of threading instructions for tomcat to handle the request. The only problem I have is how do I know what is the proper thread handling scheme? Any thoughts, idea's or tip's is greatly appreciated. 2001-02-03 14:52:02 - Ajp12Interceptor: HANDLER THREAD PROBLE M - java.io.IOException: Stream broken at org.apache.tomcat.modules.server.Ajp12.readNextRequest(Ajp12.java:300 ) at org.apache.tomcat.modules.server.AJP12Request.readNextRequest(Ajp12In terceptor.java:223) at org.apache.tomcat.modules.server.Ajp12Interceptor.processConnection(A jp12Interceptor.java:186) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java :426) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP ool.java:497) at java.lang.Thread.run(Thread.java:484) Regards, Nael Neomar, Inc Product Support [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Handler Thread Problem
Yes, it has nothing to do with HTTP requests. (8080 default.) Original Message On 2/3/01, 6:42:47 PM, Nael Mohammad [EMAIL PROTECTED] wrote regarding RE: Handler Thread Problem: You're right, I figured that out, that Apache makes the request for 8007 to tomcat. So tomcat is listening to 8007 from apache. Thanks, Now time to conquer cocoon.!!! -Original Message- From: Chris Janicki [mailto:[EMAIL PROTECTED]] Sent: Saturday, February 03, 2001 6:41 PM To: [EMAIL PROTECTED] Subject: Re: Handler Thread Problem I think port 8007 is used for connection to Apache. Are you trying to use it as a regular web service port? Original Message dated 2/3/01, 6:58:01 PM Author: Nael Mohammad [EMAIL PROTECTED] Re: Handler Thread Problem: Community, I'm getting the following error message when a request comes in for port 8007? I know I have to include some sort of threading instructions for tomcat to handle the request. The only problem I have is how do I know what is the proper thread handling scheme? Any thoughts, idea's or tip's is greatly appreciated. 2001-02-03 14:52:02 - Ajp12Interceptor: HANDLER THREAD PROBLE M - java.io.IOException: Stream broken at org.apache.tomcat.modules.server.Ajp12.readNextRequest(Ajp12.java:300 ) at org.apache.tomcat.modules.server.AJP12Request.readNextRequest(Ajp12In terceptor.java:223) at org.apache.tomcat.modules.server.Ajp12Interceptor.processConnection(A jp12Interceptor.java:186) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java :426) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP ool.java:497) at java.lang.Thread.run(Thread.java:484) Regards, Nael Neomar, Inc Product Support [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Handler Thread Problem
Hey thanks, that fixed most of my problems. Thanks. Nael :) Now I have this thread problem: I suspect I have to limit the number of threads running Any ideas, here is the error: nix 2 [ ] DGRAM620270 -More--2001-02-02 12:36:09 - Ajp12Interceptor: HANDLER THREAD PROBLEM - java.io IOException: Stream broken at org.apache.tomcat.modules.server.Ajp12.readNextRequest(Ajp12.java:287 at org.apache.tomcat.modules.server.AJP12Request.readNextRequest(Ajp12In erceptor.java:223) at org.apache.tomcat.modules.server.Ajp12Interceptor.processConnection(A p12Interceptor.java:186) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java 426) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP ol.java:497) at java.lang.Thread.run(Thread.java:484) -Original Message- From: Geoff Lane [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 01, 2001 9:43 PM To: [EMAIL PROTECTED] Subject: Re: starting Tomcat at boot time on Linux Here's one I wrote - works on Solaris and Linux . . . Nael Mohammad wrote: Do you want to contribute your script to the community? I for one would like to see it as a learning tool that I can use. Thanks, Nael Nael Mohammad Customer Support Analyst Neomar, Inc. 180 Montgomery Street Suite 2000 San Francisco, CA 94104 Tel: 415-403-7300 ext. 274 Fax: 415-403-7373 " Wireless Means Business" -- Sent from my BlackBerry Wireless Handheld (www.BlackBerry.net) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] -- --- Geoff Lane [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RedHat 7 :HANDLER THREAD PROBLEM: java.io.IOException:
Hi, I'm installing "Tomcat 3.2.1" on a Linux RedHat 7 system running a 2.2.16 kernel and the "jdk1.3" Java version. Tomcat in stand-alone mode produces the following error: (I try to connect to "http://localhost:8007", the default settings) HANDLER THREAD PROBLEM: java.io.IOException: Stream brokenjava.io.IOException: Stream broken at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Ajp12ConnectionHandler.java:486) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection(Ajp12ConnectionHandler.java:147) ... Please, Is there anybody that solved this problem??? Any idea?? Thanks, Joel ___ Do You Yahoo!? -- Pour dialoguer en direct avec vos amis, Yahoo! Messenger : http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Handler Thread Problem : java.lang.NullPointerException
Hi, I upgraded to Tomcat 3.2 because I'm getting Handler Thread Problem : java.lang.NullPointerException I thought it was caused by the virtual hosts, so I tried using the new HOST directive for server.XML You can see my config files below. When I surf to: http://www.garages.be this redirects to http://212.100.172.240/park/index.jsp and gives the error Handler Thread Problem : java.lang.NullPointerException When I simply type http://212.100.172.240/park/index.jspeverything works fine. The index.jsp is completely stripped to %@ page language="java" import="com.kmoware.register.servlets.*" errorPage="error.jsp" %htmlheadbodyURLFORWARDING TEST/body/html Getting desperate !!! Thx, Koen * HTTPD.CONF [] VirtualHost 10.0.1.201 ServerAdmin [EMAIL PROTECTED] ServerAlias be-day.com ServerAlias 192.168.1.254 # reached via internal IP ServerAlias www.be-day.com DocumentRoot /var/tomcat/webapps/register ServerName be-day.com ErrorLog logs/www.be-day.com-error_log CustomLog logs/www.be-day.com-access_log combined ApJServMount /register/servlet /register Alias /register /var/tomcat/webapps/register Directory "/var/tomcat/webapps/register" Options FollowSymLinks /Directory Location /register/WEB-INF/ AllowOverride None deny from all /Location/VirtualHost VirtualHost 10.0.1.201 ServerAlias * DocumentRoot /var/tomcat/webapps/park ServerName park.be-day.com ErrorLog logs/park.be-day.com-error_log CustomLog logs/park.be-day.com-access_log combined ApJServMount /park/servlet /park Alias /park /var/tomcat/webapps/park Directory "/var/tomcat/webapps/park" Options FollowSymLinks /Directory Location /park/WEB-INF/ AllowOverride None deny from all /Location/VirtualHost[] SERVER.XML [] Host name="be-day.com" Context path="/register" docBase="webapps/register" debug="0" reloadable="true" /Host Host name="park.be-day.com" Context path="/park" docBase="webapps/park" debug="0" reloadable="true" /Host[] smime.p7s
Handler Thread Problem : java.lang.NullPointerException ?HELP?
Hi, I upgraded to Tomcat 3.2 because I'm getting Handler Thread Problem : java.lang.NullPointerException I thought it was caused by the virtual hosts, so I tried using the new HOST directive for server.XML You can see my config files below. When I surf to: http://www.garages.be this redirects to http://212.100.172.240/park/index.jsp and gives the error Handler Thread Problem : java.lang.NullPointerException When I simply type http://212.100.172.240/park/index.jspeverything works fine. The index.jsp is completely stripped to %@ page language="java" import="com.kmoware.register.servlets.*" errorPage="error.jsp" %htmlheadbodyURLFORWARDING TEST/body/html Getting desperate !!! Thx, Koen * HTTPD.CONF [] VirtualHost 10.0.1.201 ServerAdmin [EMAIL PROTECTED] ServerAlias be-day.com ServerAlias 192.168.1.254 # reached via internal IP ServerAlias www.be-day.com DocumentRoot /var/tomcat/webapps/register ServerName be-day.com ErrorLog logs/www.be-day.com-error_log CustomLog logs/www.be-day.com-access_log combined ApJServMount /register/servlet /register Alias /register /var/tomcat/webapps/register Directory "/var/tomcat/webapps/register" Options FollowSymLinks /Directory Location /register/WEB-INF/ AllowOverride None deny from all /Location/VirtualHost VirtualHost 10.0.1.201 ServerAlias * DocumentRoot /var/tomcat/webapps/park ServerName park.be-day.com ErrorLog logs/park.be-day.com-error_log CustomLog logs/park.be-day.com-access_log combined ApJServMount /park/servlet /park Alias /park /var/tomcat/webapps/park Directory "/var/tomcat/webapps/park" Options FollowSymLinks /Directory Location /park/WEB-INF/ AllowOverride None deny from all /Location/VirtualHost[] SERVER.XML [] Host name="be-day.com" Context path="/register" docBase="webapps/register" debug="0" reloadable="true" /Host Host name="park.be-day.com" Context path="/park" docBase="webapps/park" debug="0" reloadable="true" /Host[]
RE: Handler Thread Problem : java.lang.NullPointerException
How
about trying this for your index.jsp:
--- Begin Code --
!-- Put your imports here
--
%@ page import="java.io.*,java.util.*
%
html
body
% response.sendRedirect
("http://212.100.172.240/park/index.jsp");
%
/body
/html
!-- End Code --
Just a
thought
Adam
-Original Message-From: Koen Maes (BE-day.com)
[mailto:[EMAIL PROTECTED]]Sent: Wednesday, December 27, 2000 11:02
AMTo: [EMAIL PROTECTED]Subject: Handler
Thread Problem : java.lang.NullPointerException
Hi,
I upgraded to Tomcat 3.2 because I'm getting
Handler Thread Problem : java.lang.NullPointerException
I thought it was caused by the virtual hosts, so
I tried using the new HOST directive for server.XML
You can see my config files below.
When I surf to: http://www.garages.be this redirects to http://212.100.172.240/park/index.jsp
and gives the error Handler Thread Problem :
java.lang.NullPointerException
When I simply type http://212.100.172.240/park/index.jspeverything
works fine.
The index.jsp is completely stripped
to
%@ page language="java"
import="com.kmoware.register.servlets.*" errorPage="error.jsp"
%htmlheadbodyURLFORWARDING
TEST/body/html
Getting desperate !!!
Thx,
Koen
* HTTPD.CONF
[]
VirtualHost
10.0.1.201 ServerAdmin [EMAIL PROTECTED]
ServerAlias be-day.com ServerAlias 192.168.1.254 #
reached via internal IP ServerAlias www.be-day.com
DocumentRoot /var/tomcat/webapps/register ServerName
be-day.com ErrorLog
logs/www.be-day.com-error_log CustomLog
logs/www.be-day.com-access_log combined ApJServMount
/register/servlet /register Alias /register
/var/tomcat/webapps/register Directory
"/var/tomcat/webapps/register" Options
FollowSymLinks /Directory
Location /register/WEB-INF/ AllowOverride
None deny from all
/Location/VirtualHost
VirtualHost
10.0.1.201 ServerAlias *
DocumentRoot /var/tomcat/webapps/park ServerName
park.be-day.com ErrorLog
logs/park.be-day.com-error_log CustomLog
logs/park.be-day.com-access_log combined ApJServMount
/park/servlet /park Alias /park
/var/tomcat/webapps/park Directory
"/var/tomcat/webapps/park" Options
FollowSymLinks /Directory
Location /park/WEB-INF/ AllowOverride
None deny from all
/Location/VirtualHost[]
SERVER.XML
[]
Host name="be-day.com"
Context path="/register" docBase="webapps/register" debug="0"
reloadable="true"
/Host
Host
name="park.be-day.com"
Context path="/park" docBase="webapps/park" debug="0"
reloadable="true"
/Host[]
HANDLER THREAD PROBLEM : java.lang.NullPointerException
Hi I've got my website uprunning http://www.be-day.com and it is completely running using Tomcat. We are selling domainnames for .BE (Belgium) Everything works fine but our latest feature : URL Forwarding. Tomcat always reports : HANDLER THREAD PROBLEM : java.lang.NullPointerException We configured apache to take any unknown URL entering to one specific virtual host which has an index.jsp file ready. In case the customer configured URL Forwarding, I query the database and turn the index.jsp page into a forwarding page to forward to the configured URL. If no URL Forwarding is configured by the customer in the database, I just turn the index.jsp page into a "parked domain" page. If I access the index.jsp page directly I get no problems. I just type : www.myserver.be/park/index.jsp and Tomcat responds properly. But if I enter with www.mycustomerdomain.be, then apache takes this URL to www.myserver.be/park/index.jsp but Tomcat responds with HANDLER THREAD PROBLEM : java.lang.NullPointerException The parked pages and the rest of the website run in the same Tomcat context. I already tried to fix this by separating the contexts. No luck. Thx for your time patience, Pls CC: [EMAIL PROTECTED] Koen
HANDLER THREAD PROBLEM: java.lang.NullPointerException
I get these errors sometimes, can cant figure out what the problem is. Can someone tell me where should I start looking ? Thanks Shahed HANDLER THREAD PROBLEM: java.lang.NullPointerExceptionERROR: can't find default error handler or error in default error page
RE: Help : HANDLER THREAD PROBLEM (Tomcat3.2b6, NT4.0, JDK1.2)
Philip, I had this problem with Tomcat 3.1 with Apache on AIX (there's a previous post by me with title 'Handler thread problem) I Isolated the problem to mod_jserv. Recompiling solved it. It should be the same with mod_jk. Rit -Original Message-From: Philip Chan [mailto:[EMAIL PROTECTED]]Sent: Wednesday, November 29, 2000 12:47 AMTo: [EMAIL PROTECTED]Subject: Help : HANDLER THREAD PROBLEM (Tomcat3.2b6, NT4.0, JDK1.2) I got this error when I try this URL http://localhost:8007 Is this a known bug ?(I seem to recall seeing posting with title like HANDLER ...). Thx I download Tomcat3.2, install it and start it as "standalone"without changing the configs. All the servlet/jsp works. So I think everything is working but this. Here is the actual output in the log 2000-11-29 12:50:44 - ContextManager: Adding context Ctx( /examples )2000-11-29 12:50:44 - ContextManager: Adding context Ctx( /admin )Starting tomcat. Check logs/tomcat.log for error messages2000-11-29 12:50:44 - ContextManager: Adding context Ctx( )2000-11-29 12:50:44 - ContextManager: Adding context Ctx( /test )2000-11-29 12:50:46 - PoolTcpConnector: Starting HttpConnectionHandler on 80802000-11-29 12:50:46 - PoolTcpConnector: Starting Ajp12ConnectionHandler on 8007 HANDLER THREAD PROBLEM: java.io.IOException: Stream brokenjava.io.IOException: Stream broken at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Compiled Code) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection(Ajp12ConnectionHandler.java:147) at org.apache.tomcat.service.TcpWorkerThread.runIt(Compiled Code) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(Compiled Code) at java.lang.Thread.run(Compiled Code)2000-11-29 01:03:43 - Ctx( /examples ): IOException in: R( /examples + /jsp/index.html + null) socket write error (code=10053)
RE: HANDLER THREAD PROBLEM: Stream closed prematurely
I got mod_jserv to compile and link on AIX. The linker was trying to use an exports file that was missing. I did the following: 1. Hacked the apxs file and added -qcpluscmt to make the compiler ignore the // comments 2. Took a look at .exp files for the .so modules. Each had one line: modulename_module. I created a file in the current directory called mod_jerv.exp with one line: jserv_module. 3. invoked ld with -bE:mod_jserv.exp This resulted in a successful compile. However, I'm now getting a core dump :-/ from httpd. Am I doing things the right way? Rit -Original Message- From: Ranko Bijelonic [mailto:[EMAIL PROTECTED]] Sent: Monday, November 27, 2000 10:08 AM To: [EMAIL PROTECTED] Subject: RE: HANDLER THREAD PROBLEM: Stream closed prematurely i still think its not the platform. My stuff worked fine until I used a version of Apache with ssl, then I got the same problem as you. And building mod_jserv from scratch did not help me either. I had to 'apxs it in'. I don't know why it worked, or what it really did, but just rebuilding mod_jserv.so and sticking it into libexec directory it did not work. it had to be apxs-ed for some reason :). what do you mean apxs does not work though? what kind of errors do you get? I think among other options you have to say with EAPI also. -Original Message- From: Ritwick Dhar [mailto:[EMAIL PROTECTED]] Sent: Monday, November 27, 2000 10:42 AM To: '[EMAIL PROTECTED]' Subject: RE: HANDLER THREAD PROBLEM: Stream closed prematurely Unfortunately, in my case, it doesn't work. The problem is compounded in my case because my platform is AIX4.3.3 + IBM Apache 1.3.6.2 + Tomcat 3.1. Something is seriously screwed up in this level of AIX. apxs does not work. Period. No matter what I do. I built IBM's version of apache from scratch with DSO support. Then I downloaded Apache jServ and built that from scratch. This resulted in a new mod_jserv.so. However, this one makes Apache core dump. So I'm back to square one. Can't believe its *this* difficult getting tomcat to run/build on AIX!!! -Original Message- From: Ranko Bijelonic [mailto:[EMAIL PROTECTED]] Sent: Monday, November 27, 2000 9:47 AM To: [EMAIL PROTECTED] Subject: RE: HANDLER THREAD PROBLEM: Stream closed prematurely I had the exact same problem. Nothing helped until I recompiled mod_jserv using the apache apxs utility. So recompile, and everything should be fine. -Original Message- From: Ritwick Dhar [mailto:[EMAIL PROTECTED]] Sent: Friday, November 24, 2000 4:04 PM To: '[EMAIL PROTECTED]' Subject: RE: HANDLER THREAD PROBLEM: Stream closed prematurely Update on this problem: I simplified the client to simply POST a line of text and the server to simply echo it back. The results seem to be: The client can open an outputstream to a servlet and write to it, but a close() or even a flush() causes the stream to be shut down and the server prints the stacktrace for an IOException. If the stream is not flushed, however, the server proceeds without any input whatsoever (contentlength = 0). I tried this servlet on Jrun and WebSphere. Both work without a hitch. I think this is starting to smell like a bug. Thanks Ritwick -Original Message- From: William Brogden [mailto:[EMAIL PROTECTED]] Sent: Friday, November 24, 2000 11:27 AM To: [EMAIL PROTECTED] Subject: Re: HANDLER THREAD PROBLEM: Stream closed prematurely Does your client close the stream that writes the request or just flush it? I seem to recall having a problem similar to this where the solution was to not close the client's output stream until after the complete transaction. Ritwick Dhar wrote: Hi, This problem is driving me nuts. I've tried debugging this, but nothing yet. I was hoping someone on this list will have come accross this before. Case: I have a servlet (server) that accepts POST requests (content-type= application/x-ofx), and sends back a OFX response. I have another servlet (client), that opens a URL to the server, writes the request, and reads the reponse. Simple. The problem is, the moment the client tries to call 'urlConn.getInputStream()' to get an inputstream from the server, I get this (on the server console): HANDLER THREAD PROBLEM: java.io.IOException: Stream closed prematurely java.io.IOException: Stream closed prematurely at java.lang.Throwable.init(Compiled Code) at java.lang.Exception.init(Compiled Code) at java.io.IOException.init(Compiled Code) at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Comp iled Code) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection (Compiled Code) at org.apache.tomcat.service.TcpConnectionThread.run(Compiled Code) at java.lang.Thread.run(Compiled Code) What's really driving me up the wall is that this works perfectly fine with Both WebSphere and JRun. Is this something particular to Tomcat?? Thanks
Help : HANDLER THREAD PROBLEM (Tomcat3.2b6, NT4.0, JDK1.2)
I got this error when I try this URL http://localhost:8007 Is this a known bug ?(I seem to recall seeing posting with title like HANDLER ...). Thx I download Tomcat3.2, install it and start it as "standalone"without changing the configs. All the servlet/jsp works. So I think everything is working but this. Here is the actual output in the log 2000-11-29 12:50:44 - ContextManager: Adding context Ctx( /examples )2000-11-29 12:50:44 - ContextManager: Adding context Ctx( /admin )Starting tomcat. Check logs/tomcat.log for error messages2000-11-29 12:50:44 - ContextManager: Adding context Ctx( )2000-11-29 12:50:44 - ContextManager: Adding context Ctx( /test )2000-11-29 12:50:46 - PoolTcpConnector: Starting HttpConnectionHandler on 80802000-11-29 12:50:46 - PoolTcpConnector: Starting Ajp12ConnectionHandler on 8007 HANDLER THREAD PROBLEM: java.io.IOException: Stream brokenjava.io.IOException: Stream broken at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Compiled Code) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection(Ajp12ConnectionHandler.java:147) at org.apache.tomcat.service.TcpWorkerThread.runIt(Compiled Code) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(Compiled Code) at java.lang.Thread.run(Compiled Code)2000-11-29 01:03:43 - Ctx( /examples ): IOException in: R( /examples + /jsp/index.html + null) socket write error (code=10053)
RE: HANDLER THREAD PROBLEM: Stream closed prematurely
i still think its not the platform. My stuff worked fine until I used a version of Apache with ssl, then I got the same problem as you. And building mod_jserv from scratch did not help me either. I had to 'apxs it in'. I don't know why it worked, or what it really did, but just rebuilding mod_jserv.so and sticking it into libexec directory it did not work. it had to be apxs-ed for some reason :). what do you mean apxs does not work though? what kind of errors do you get? I think among other options you have to say with EAPI also. -Original Message- From: Ritwick Dhar [mailto:[EMAIL PROTECTED]] Sent: Monday, November 27, 2000 10:42 AM To: '[EMAIL PROTECTED]' Subject: RE: HANDLER THREAD PROBLEM: Stream closed prematurely Unfortunately, in my case, it doesn't work. The problem is compounded in my case because my platform is AIX4.3.3 + IBM Apache 1.3.6.2 + Tomcat 3.1. Something is seriously screwed up in this level of AIX. apxs does not work. Period. No matter what I do. I built IBM's version of apache from scratch with DSO support. Then I downloaded Apache jServ and built that from scratch. This resulted in a new mod_jserv.so. However, this one makes Apache core dump. So I'm back to square one. Can't believe its *this* difficult getting tomcat to run/build on AIX!!! -Original Message- From: Ranko Bijelonic [mailto:[EMAIL PROTECTED]] Sent: Monday, November 27, 2000 9:47 AM To: [EMAIL PROTECTED] Subject: RE: HANDLER THREAD PROBLEM: Stream closed prematurely I had the exact same problem. Nothing helped until I recompiled mod_jserv using the apache apxs utility. So recompile, and everything should be fine. -Original Message- From: Ritwick Dhar [mailto:[EMAIL PROTECTED]] Sent: Friday, November 24, 2000 4:04 PM To: '[EMAIL PROTECTED]' Subject: RE: HANDLER THREAD PROBLEM: Stream closed prematurely Update on this problem: I simplified the client to simply POST a line of text and the server to simply echo it back. The results seem to be: The client can open an outputstream to a servlet and write to it, but a close() or even a flush() causes the stream to be shut down and the server prints the stacktrace for an IOException. If the stream is not flushed, however, the server proceeds without any input whatsoever (contentlength = 0). I tried this servlet on Jrun and WebSphere. Both work without a hitch. I think this is starting to smell like a bug. Thanks Ritwick -Original Message- From: William Brogden [mailto:[EMAIL PROTECTED]] Sent: Friday, November 24, 2000 11:27 AM To: [EMAIL PROTECTED] Subject: Re: HANDLER THREAD PROBLEM: Stream closed prematurely Does your client close the stream that writes the request or just flush it? I seem to recall having a problem similar to this where the solution was to not close the client's output stream until after the complete transaction. Ritwick Dhar wrote: Hi, This problem is driving me nuts. I've tried debugging this, but nothing yet. I was hoping someone on this list will have come accross this before. Case: I have a servlet (server) that accepts POST requests (content-type= application/x-ofx), and sends back a OFX response. I have another servlet (client), that opens a URL to the server, writes the request, and reads the reponse. Simple. The problem is, the moment the client tries to call 'urlConn.getInputStream()' to get an inputstream from the server, I get this (on the server console): HANDLER THREAD PROBLEM: java.io.IOException: Stream closed prematurely java.io.IOException: Stream closed prematurely at java.lang.Throwable.init(Compiled Code) at java.lang.Exception.init(Compiled Code) at java.io.IOException.init(Compiled Code) at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Comp iled Code) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection (Compiled Code) at org.apache.tomcat.service.TcpConnectionThread.run(Compiled Code) at java.lang.Thread.run(Compiled Code) What's really driving me up the wall is that this works perfectly fine with Both WebSphere and JRun. Is this something particular to Tomcat?? Thanks for all help Rit -- WBB - [EMAIL PROTECTED] Author of Java Developer's Guide to Servlets and JSP ISBN 0-7821-2809-2
HANDLER THREAD PROBLEM: Stream closed prematurely
Hi, This problem is driving me nuts. I've tried debugging this, but nothing yet. I was hoping someone on this list will have come accross this before. Case: I have a servlet (server) that accepts POST requests (content-type= application/x-ofx), and sends back a OFX response. I have another servlet (client), that opens a URL to the server, writes the request, and reads the reponse. Simple. The problem is, the moment the client tries to call 'urlConn.getInputStream()' to get an inputstream from the server, I get this (on the server console): HANDLER THREAD PROBLEM: java.io.IOException: Stream closed prematurely java.io.IOException: Stream closed prematurely at java.lang.Throwable.init(Compiled Code) at java.lang.Exception.init(Compiled Code) at java.io.IOException.init(Compiled Code) at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Comp iled Code) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection (Compiled Code) at org.apache.tomcat.service.TcpConnectionThread.run(Compiled Code) at java.lang.Thread.run(Compiled Code) What's really driving me up the wall is that this works perfectly fine with Both WebSphere and JRun. Is this something particular to Tomcat?? Thanks for all help Rit
RE: HANDLER THREAD PROBLEM: Stream closed prematurely
If you are running Tomcat standalone I would suggest to try it with Apache web server. We had some problems with tomcat built in web server - POST input stream would only give you first 1300 bytes of POST data and some other problems I do not remember. I believe apache inherited it from Sun Web server which had these problems. However all these problems were not present when we access tomcat via Apache web server Alex -Original Message- From: Ritwick Dhar [mailto:[EMAIL PROTECTED]] Sent: Friday, November 24, 2000 11:35 AM To: '[EMAIL PROTECTED]' Subject: HANDLER THREAD PROBLEM: Stream closed prematurely Hi, This problem is driving me nuts. I've tried debugging this, but nothing yet. I was hoping someone on this list will have come accross this before. Case: I have a servlet (server) that accepts POST requests (content-type= application/x-ofx), and sends back a OFX response. I have another servlet (client), that opens a URL to the server, writes the request, and reads the reponse. Simple. The problem is, the moment the client tries to call 'urlConn.getInputStream()' to get an inputstream from the server, I get this (on the server console): HANDLER THREAD PROBLEM: java.io.IOException: Stream closed prematurely java.io.IOException: Stream closed prematurely at java.lang.Throwable.init(Compiled Code) at java.lang.Exception.init(Compiled Code) at java.io.IOException.init(Compiled Code) at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Comp iled Code) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection (Compiled Code) at org.apache.tomcat.service.TcpConnectionThread.run(Compiled Code) at java.lang.Thread.run(Compiled Code) What's really driving me up the wall is that this works perfectly fine with Both WebSphere and JRun. Is this something particular to Tomcat?? Thanks for all help Rit
RE: HANDLER THREAD PROBLEM: Stream closed prematurely
Alex, Unfortunately, I'm already running it with Apache. (IBM HTTP Server based on Apache with SSL). Thanks for the reply. Rit -Original Message- From: Roytman, Alex [mailto:[EMAIL PROTECTED]] Sent: Friday, November 24, 2000 10:53 AM To: '[EMAIL PROTECTED]' Subject: RE: HANDLER THREAD PROBLEM: Stream closed prematurely If you are running Tomcat standalone I would suggest to try it with Apache web server. We had some problems with tomcat built in web server - POST input stream would only give you first 1300 bytes of POST data and some other problems I do not remember. I believe apache inherited it from Sun Web server which had these problems. However all these problems were not present when we access tomcat via Apache web server Alex -Original Message- From: Ritwick Dhar [mailto:[EMAIL PROTECTED]] Sent: Friday, November 24, 2000 11:35 AM To: '[EMAIL PROTECTED]' Subject: HANDLER THREAD PROBLEM: Stream closed prematurely Hi, This problem is driving me nuts. I've tried debugging this, but nothing yet. I was hoping someone on this list will have come accross this before. Case: I have a servlet (server) that accepts POST requests (content-type= application/x-ofx), and sends back a OFX response. I have another servlet (client), that opens a URL to the server, writes the request, and reads the reponse. Simple. The problem is, the moment the client tries to call 'urlConn.getInputStream()' to get an inputstream from the server, I get this (on the server console): HANDLER THREAD PROBLEM: java.io.IOException: Stream closed prematurely java.io.IOException: Stream closed prematurely at java.lang.Throwable.init(Compiled Code) at java.lang.Exception.init(Compiled Code) at java.io.IOException.init(Compiled Code) at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Comp iled Code) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection (Compiled Code) at org.apache.tomcat.service.TcpConnectionThread.run(Compiled Code) at java.lang.Thread.run(Compiled Code) What's really driving me up the wall is that this works perfectly fine with Both WebSphere and JRun. Is this something particular to Tomcat?? Thanks for all help Rit
Re: HANDLER THREAD PROBLEM: Stream closed prematurely
Ritwick Dhar wrote: HANDLER THREAD PROBLEM: java.io.IOException: Stream closed prematurely java.io.IOException: Stream closed prematurely at java.lang.Throwable.init(Compiled Code) at java.lang.Exception.init(Compiled Code) at java.io.IOException.init(Compiled Code) at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Comp iled Code) Could it be that you want to connect via port 8007 (which is for connections using the AJP12 protocol) when you really want to be using port 8080 (which is the port to use for normal HTTP requests)? -- Kurt Bernhard Pruenner --- Haendelstrasse 17 --- 4020 Linz --- Austria Music: http://www.mp3.com/Leak --- Work: http://www.ssw.uni-linz.ac.at ...It might be written "Mindfuck", but it's spelt "L-A-I-N"... np: Senor Coconut - Showroom Dummies (El Baile Aleman)
RE: HANDLER THREAD PROBLEM: Stream closed prematurely
Kurt, No. Post 8008 is for the stand-alone server - I'm using apache. 8007 is the internal port which Tomcat uses to talk to Apache (I think). I'm simply sending my requests to 80. William, You may be on to something. I've tried not closing the output stream from the client at all, but that didn't do much good. Maybe I'll try some other things on those lines now. Thanks Rit -Original Message- From: William Brogden [mailto:[EMAIL PROTECTED]] Sent: Friday, November 24, 2000 11:27 AM To: [EMAIL PROTECTED] Subject: Re: HANDLER THREAD PROBLEM: Stream closed prematurely Does your client close the stream that writes the request or just flush it? I seem to recall having a problem similar to this where the solution was to not close the client's output stream until after the complete transaction. Ritwick Dhar wrote: Hi, This problem is driving me nuts. I've tried debugging this, but nothing yet. I was hoping someone on this list will have come accross this before. Case: I have a servlet (server) that accepts POST requests (content-type= application/x-ofx), and sends back a OFX response. I have another servlet (client), that opens a URL to the server, writes the request, and reads the reponse. Simple. The problem is, the moment the client tries to call 'urlConn.getInputStream()' to get an inputstream from the server, I get this (on the server console): HANDLER THREAD PROBLEM: java.io.IOException: Stream closed prematurely java.io.IOException: Stream closed prematurely at java.lang.Throwable.init(Compiled Code) at java.lang.Exception.init(Compiled Code) at java.io.IOException.init(Compiled Code) at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Comp iled Code) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection (Compiled Code) at org.apache.tomcat.service.TcpConnectionThread.run(Compiled Code) at java.lang.Thread.run(Compiled Code) What's really driving me up the wall is that this works perfectly fine with Both WebSphere and JRun. Is this something particular to Tomcat?? Thanks for all help Rit -- WBB - [EMAIL PROTECTED] Author of Java Developer's Guide to Servlets and JSP ISBN 0-7821-2809-2
RE: HANDLER THREAD PROBLEM: Stream closed prematurely
Update on this problem: I simplified the client to simply POST a line of text and the server to simply echo it back. The results seem to be: The client can open an outputstream to a servlet and write to it, but a close() or even a flush() causes the stream to be shut down and the server prints the stacktrace for an IOException. If the stream is not flushed, however, the server proceeds without any input whatsoever (contentlength = 0). I tried this servlet on Jrun and WebSphere. Both work without a hitch. I think this is starting to smell like a bug. Thanks Ritwick -Original Message- From: William Brogden [mailto:[EMAIL PROTECTED]] Sent: Friday, November 24, 2000 11:27 AM To: [EMAIL PROTECTED] Subject: Re: HANDLER THREAD PROBLEM: Stream closed prematurely Does your client close the stream that writes the request or just flush it? I seem to recall having a problem similar to this where the solution was to not close the client's output stream until after the complete transaction. Ritwick Dhar wrote: Hi, This problem is driving me nuts. I've tried debugging this, but nothing yet. I was hoping someone on this list will have come accross this before. Case: I have a servlet (server) that accepts POST requests (content-type= application/x-ofx), and sends back a OFX response. I have another servlet (client), that opens a URL to the server, writes the request, and reads the reponse. Simple. The problem is, the moment the client tries to call 'urlConn.getInputStream()' to get an inputstream from the server, I get this (on the server console): HANDLER THREAD PROBLEM: java.io.IOException: Stream closed prematurely java.io.IOException: Stream closed prematurely at java.lang.Throwable.init(Compiled Code) at java.lang.Exception.init(Compiled Code) at java.io.IOException.init(Compiled Code) at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Comp iled Code) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection (Compiled Code) at org.apache.tomcat.service.TcpConnectionThread.run(Compiled Code) at java.lang.Thread.run(Compiled Code) What's really driving me up the wall is that this works perfectly fine with Both WebSphere and JRun. Is this something particular to Tomcat?? Thanks for all help Rit -- WBB - [EMAIL PROTECTED] Author of Java Developer's Guide to Servlets and JSP ISBN 0-7821-2809-2
Help :HANDLER THREAD PROBLEM?
I get the following exception: HANDLER THREAD PROBLEM: java.io.IOException: Stream closed prematurely java.io.IOException: Stream closed prematurely at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextReque st(Ajp12ConnectionHandler.java, Compiled Code) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processCon nection(Ajp12ConnectionHandler.java, Compiled Code) at org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.j ava, Compiled Code) at java.lang.Thread.run(Thread.java, Compiled Code) What is his meaning? Att. Mauricio
RE: Help :HANDLER THREAD PROBLEM?
Are you using a secure Apache server like the one with mod_ssl or Raven or anything like that? Also did you just dowload mod_jserv binary? What you need to do is compile the mod_jserv binary using the Apache apxs script and make it a part of EAPI (note that I'm not sure exactely what I'm talking about, but that this is what you have to do). This problem has been driving me crazy for the past couple days, but recompiling solved it. Let me know if you have any questions. -Original Message- From: Mauricio Nuñez [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 31, 2000 12:54 PM To: [EMAIL PROTECTED] Subject: Help :HANDLER THREAD PROBLEM? I get the following exception: HANDLER THREAD PROBLEM: java.io.IOException: Stream closed prematurely java.io.IOException: Stream closed prematurely at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextReque st(Ajp12ConnectionHandler.java, Compiled Code) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processCon nection(Ajp12ConnectionHandler.java, Compiled Code) at org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.j ava, Compiled Code) at java.lang.Thread.run(Thread.java, Compiled Code) What is his meaning? Att. Mauricio
