RE: IIS-Tomcat 4.1 integration
Tomcat is running on 8080 and IIS on the default 80 port. -Original Message- From: Propes, Barry L [mailto:[EMAIL PROTECTED] Sent: Friday, February 01, 2008 4:11 PM To: Tomcat Users List Subject: RE: IIS-Tomcat 4.1 integration sounds like Tomcat might be using port 80 (default) instead of IIS now. I think, short of some plug-in, you'll have to specify another port for one of the two...I keep TC on 8080, and IIS on 80 on mine. -Original Message- From: Chacko Kuruvilla [mailto:[EMAIL PROTECTED] Sent: Friday, February 01, 2008 1:00 PM To: users@tomcat.apache.org Subject: IIS-Tomcat 4.1 integration Hello, I am in the process of trying to integrate IIS 6.0 and Tomcat 4.1. I get a page not found error when I try to access my web site using IIS. It works just fine using Tomcat though. The error I see in httperr1.log is, #Software: Microsoft HTTP API 1.0 #Version: 1.0 #Date: 2008-02-01 18:47:40 #Fields: date time c-ip c-port s-ip s-port cs-version cs-method cs-uri sc-status s-siteid s-reason s-queuename 2008-02-01 18:47:40 127.0.0.1 1115 127.0.0.1 80 HTTP/1.1 GET /dchqweb/partners.htm - 1 Connection_Dropped DefaultAppPool Any help is appreciated. Thanks, Chacko. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
IIS-Tomcat 4.1 integration
Hello, I am in the process of trying to integrate IIS 6.0 and Tomcat 4.1. I get a page not found error when I try to access my web site using IIS. It works just fine using Tomcat though. The error I see in httperr1.log is, #Software: Microsoft HTTP API 1.0 #Version: 1.0 #Date: 2008-02-01 18:47:40 #Fields: date time c-ip c-port s-ip s-port cs-version cs-method cs-uri sc-status s-siteid s-reason s-queuename 2008-02-01 18:47:40 127.0.0.1 1115 127.0.0.1 80 HTTP/1.1 GET /dchqweb/partners.htm - 1 Connection_Dropped DefaultAppPool Any help is appreciated. Thanks, Chacko.
RE: ISAPI redirector error in Tomcat 4.1
Thanks for your response. I removed the older version of isapi redirector and started from scratch using isapi_redirect-1.2.26.dll. When I try now, I get an "Incorrect function" message on the browser. Any ideas? Thanks. -Original Message- From: Rainer Jung [mailto:[EMAIL PROTECTED] Sent: Thursday, December 27, 2007 1:43 PM To: Tomcat Users List Subject: Re: ISAPI redirector error in Tomcat 4.1 Hi Chacko, if you can reproduce the problem easily, please do the following: - make sure you are using the latest version of the isapi redirector (at the moment 1.2.26) - Make sure your redirector is correctly configured, especially, that it writes a log file - increase isapi redirector log level to debug - do a fresh start of iis (clean log file before) and reproduce the problem - Give us a way to look at the file - let us know, how the http request that produces the problem exactly looks like Regards, Rainer Chacko Kuruvilla schrieb: > Can somebody help me with this error? > > Thanks a lot. > > -Original Message- > From: Chacko Kuruvilla [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 26, 2007 1:23 PM > To: 'Tomcat Users List' > Subject: RE: ISAPI redirector error in Tomcat 4.1 > > Here it is... > > Created MBeanServer with ID: c4fe76:11716dc479f:-8000:DCHS-HIPAA-VM:1 > Dec 26, 2007 8:30:11 AM org.apache.coyote.http11.Http11BaseProtocol init > INFO: Initializing Coyote HTTP/1.1 on http-8080 > Starting service Tomcat-Standalone > Apache Tomcat/4.1.36 > Dec 26, 2007 8:30:21 AM org.apache.coyote.http11.Http11BaseProtocol start > INFO: Starting Coyote HTTP/1.1 on http-8080 > Dec 26, 2007 8:30:22 AM org.apache.jk.common.ChannelSocket init > INFO: JK: ajp13 listening on /0.0.0.0:8009 > Dec 26, 2007 8:30:22 AM org.apache.jk.server.JkMain start > INFO: Jk running ID=0 time=0/47 config=null > Stopping service Tomcat-Standalone > Dec 26, 2007 8:33:23 AM org.apache.coyote.http11.Http11BaseProtocol destroy > INFO: Stopping Coyote HTTP/1.1 on http-8080 > Created MBeanServer with ID: c4fe76:11716e053b4:-8000:DCHS-HIPAA-VM:1 > Dec 26, 2007 8:34:36 AM org.apache.coyote.http11.Http11BaseProtocol init > INFO: Initializing Coyote HTTP/1.1 on http-8080 > Starting service Tomcat-Standalone > Apache Tomcat/4.1.36 > Dec 26, 2007 8:34:44 AM org.apache.coyote.http11.Http11BaseProtocol start > INFO: Starting Coyote HTTP/1.1 on http-8080 > Dec 26, 2007 8:34:44 AM org.apache.jk.common.ChannelSocket init > INFO: JK: ajp13 listening on /0.0.0.0:8009 > Dec 26, 2007 8:34:44 AM org.apache.jk.server.JkMain start > INFO: Jk running ID=0 time=0/62 config=null > Dec 26, 2007 8:37:31 AM org.apache.jk.core.MsgContext action > WARNING: Error sending end packet > java.net.SocketException: Software caused connection abort: socket write > error > at java.net.SocketOutputStream.socketWrite0(Native Method) > at > java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) > at java.net.SocketOutputStream.write(SocketOutputStream.java:136) > at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:537) > at > org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:127) > at org.apache.jk.core.MsgContext.action(MsgContext.java:302) > at org.apache.coyote.Response.action(Response.java:183) > at org.apache.coyote.Response.finish(Response.java:305) > at > org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:285) > at > org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.java: > 438) > at > org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:158) > at > org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200) > at > org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283) > at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:773) > at > org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:703) > at > org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java > :895) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav > a:685) > at java.lang.Thread.run(Thread.java:536) > Dec 26, 2007 8:37:31 AM org.apache.jk.common.ChannelSocket processConnection > WARNING: processCallbacks status 2 > Dec 26, 2007 8:37:31 AM org.apache.jk.core.MsgContext action > WARNING: Error sending end packet > java.net.SocketException: Software caused connection abort: socket write > error > at java.net.SocketOutputStream.socketWrite0(Native Method) > at > java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) > at java.net.SocketOutputStream.write(SocketOutputStream.java:136) >
RE: ISAPI redirector error in Tomcat 4.1
Can somebody help me with this error? Thanks a lot. -Original Message- From: Chacko Kuruvilla [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 26, 2007 1:23 PM To: 'Tomcat Users List' Subject: RE: ISAPI redirector error in Tomcat 4.1 Here it is... Created MBeanServer with ID: c4fe76:11716dc479f:-8000:DCHS-HIPAA-VM:1 Dec 26, 2007 8:30:11 AM org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.36 Dec 26, 2007 8:30:21 AM org.apache.coyote.http11.Http11BaseProtocol start INFO: Starting Coyote HTTP/1.1 on http-8080 Dec 26, 2007 8:30:22 AM org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:8009 Dec 26, 2007 8:30:22 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=0/47 config=null Stopping service Tomcat-Standalone Dec 26, 2007 8:33:23 AM org.apache.coyote.http11.Http11BaseProtocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8080 Created MBeanServer with ID: c4fe76:11716e053b4:-8000:DCHS-HIPAA-VM:1 Dec 26, 2007 8:34:36 AM org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.36 Dec 26, 2007 8:34:44 AM org.apache.coyote.http11.Http11BaseProtocol start INFO: Starting Coyote HTTP/1.1 on http-8080 Dec 26, 2007 8:34:44 AM org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:8009 Dec 26, 2007 8:34:44 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=0/62 config=null Dec 26, 2007 8:37:31 AM org.apache.jk.core.MsgContext action WARNING: Error sending end packet java.net.SocketException: Software caused connection abort: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:537) at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:127) at org.apache.jk.core.MsgContext.action(MsgContext.java:302) at org.apache.coyote.Response.action(Response.java:183) at org.apache.coyote.Response.finish(Response.java:305) at org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:285) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.java: 438) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:158) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:773) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:703) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java :895) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:685) at java.lang.Thread.run(Thread.java:536) Dec 26, 2007 8:37:31 AM org.apache.jk.common.ChannelSocket processConnection WARNING: processCallbacks status 2 Dec 26, 2007 8:37:31 AM org.apache.jk.core.MsgContext action WARNING: Error sending end packet java.net.SocketException: Software caused connection abort: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:537) at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:127) at org.apache.jk.core.MsgContext.action(MsgContext.java:302) at org.apache.coyote.Response.action(Response.java:183) at org.apache.coyote.Response.finish(Response.java:305) at org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:285) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.java: 438) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:158) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:773) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:703) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java :895) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:685) at java.lang.Thread.run(Thread.java:536) Dec 26, 2007 8:37:31 AM org.apache.jk.common.ChannelSocket processConnection WARNING: processCallbacks status 2 Dec 26, 2007 8:39:49 AM org.apache.jk.core.MsgContext acti
RE: ISAPI redirector error in Tomcat 4.1
Here it is... Created MBeanServer with ID: c4fe76:11716dc479f:-8000:DCHS-HIPAA-VM:1 Dec 26, 2007 8:30:11 AM org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.36 Dec 26, 2007 8:30:21 AM org.apache.coyote.http11.Http11BaseProtocol start INFO: Starting Coyote HTTP/1.1 on http-8080 Dec 26, 2007 8:30:22 AM org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:8009 Dec 26, 2007 8:30:22 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=0/47 config=null Stopping service Tomcat-Standalone Dec 26, 2007 8:33:23 AM org.apache.coyote.http11.Http11BaseProtocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8080 Created MBeanServer with ID: c4fe76:11716e053b4:-8000:DCHS-HIPAA-VM:1 Dec 26, 2007 8:34:36 AM org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.36 Dec 26, 2007 8:34:44 AM org.apache.coyote.http11.Http11BaseProtocol start INFO: Starting Coyote HTTP/1.1 on http-8080 Dec 26, 2007 8:34:44 AM org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:8009 Dec 26, 2007 8:34:44 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=0/62 config=null Dec 26, 2007 8:37:31 AM org.apache.jk.core.MsgContext action WARNING: Error sending end packet java.net.SocketException: Software caused connection abort: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:537) at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:127) at org.apache.jk.core.MsgContext.action(MsgContext.java:302) at org.apache.coyote.Response.action(Response.java:183) at org.apache.coyote.Response.finish(Response.java:305) at org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:285) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.java: 438) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:158) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:773) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:703) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java :895) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:685) at java.lang.Thread.run(Thread.java:536) Dec 26, 2007 8:37:31 AM org.apache.jk.common.ChannelSocket processConnection WARNING: processCallbacks status 2 Dec 26, 2007 8:37:31 AM org.apache.jk.core.MsgContext action WARNING: Error sending end packet java.net.SocketException: Software caused connection abort: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:537) at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:127) at org.apache.jk.core.MsgContext.action(MsgContext.java:302) at org.apache.coyote.Response.action(Response.java:183) at org.apache.coyote.Response.finish(Response.java:305) at org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:285) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.java: 438) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:158) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:773) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:703) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java :895) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:685) at java.lang.Thread.run(Thread.java:536) Dec 26, 2007 8:37:31 AM org.apache.jk.common.ChannelSocket processConnection WARNING: processCallbacks status 2 Dec 26, 2007 8:39:49 AM org.apache.jk.core.MsgContext action WARNING: Error sending end packet java.net.SocketException: Software caused connection abort: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
RE: ISAPI redirector error in Tomcat 4.1
Thank you Martin for your response. I quickly reviewed the web site you recommended. I did not see any troubleshooting section. Attached is the entire log file as requested. Chacko. -Original Message- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 26, 2007 9:15 AM To: [EMAIL PROTECTED] Subject: Re: ISAPI redirector error in Tomcat 4.1 Error 2 is 'directory program or file not found' the best tutorial on fronting Tomcat with IIS is to follow Mladen Turk's advice at http://people.apache.org/~mturk/docs/article/ftwai.html In the meanwhile Send us the whole stack dump so we can see the specific message on what is missing HTH/ M-- - Original Message - From: "Chacko Kuruvilla" <[EMAIL PROTECTED]> To: Sent: Wednesday, December 26, 2007 10:05 AM Subject: ISAPI redirector error in Tomcat 4.1 > Hello, > > > > I am in the process of setting up Tomcat 4.1 and IIS on a Windows 2003 > server. Our web application is in JSP and Java servlets. The application > works just fine off Tomcat 4.1 which is setup to run as a service. However, > I am having trouble getting it to integrate with IIS 6.0. Initially, after > setting up the ISAPI redirector in IIS, I received a 404 error. However, I > was told that I need to add the ISAPI redirector in IIS as a web service > extension. However, after I do that, I just get a "Page cannot be displayed" > error. > > > > I also see the following in the stdout_20071226 log file in > %TOMCATE_HOME%\logs folder. > > > > Dec 26, 2007 8:52:38 AM org.apache.jk.core.MsgContext action > > WARNING: Error sending end packet > > java.net.SocketException: Software caused connection abort: socket write > error > > at java.net.SocketOutputStream.socketWrite0(Native Method) > > at > java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) > > at > java.net.SocketOutputStream.write(SocketOutputStream.java:136) > > at > org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:537) > > at > org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:127) > > at org.apache.jk.core.MsgContext.action(MsgContext.java:302) > > at org.apache.coyote.Response.action(Response.java:183) > > at org.apache.coyote.Response.finish(Response.java:305) > > at > org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:285) > > at > org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.java: > 438) > > at > org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:158) > > at > org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200) > > at > org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283) > > at > org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:773) > > at > org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:703) > > at > org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java > :895) > > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav > a:685) > > at java.lang.Thread.run(Thread.java:536) > > Dec 26, 2007 8:52:38 AM org.apache.jk.common.ChannelSocket processConnection > > WARNING: processCallbacks status 2 > > > > Any help is greatly appreciated. > > > > Thanks, > > Chacko. > > - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ISAPI redirector error in Tomcat 4.1
Hello, I am in the process of setting up Tomcat 4.1 and IIS on a Windows 2003 server. Our web application is in JSP and Java servlets. The application works just fine off Tomcat 4.1 which is setup to run as a service. However, I am having trouble getting it to integrate with IIS 6.0. Initially, after setting up the ISAPI redirector in IIS, I received a 404 error. However, I was told that I need to add the ISAPI redirector in IIS as a web service extension. However, after I do that, I just get a "Page cannot be displayed" error. I also see the following in the stdout_20071226 log file in %TOMCATE_HOME%\logs folder. Dec 26, 2007 8:52:38 AM org.apache.jk.core.MsgContext action WARNING: Error sending end packet java.net.SocketException: Software caused connection abort: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:537) at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:127) at org.apache.jk.core.MsgContext.action(MsgContext.java:302) at org.apache.coyote.Response.action(Response.java:183) at org.apache.coyote.Response.finish(Response.java:305) at org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:285) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.java: 438) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:158) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:773) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:703) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java :895) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:685) at java.lang.Thread.run(Thread.java:536) Dec 26, 2007 8:52:38 AM org.apache.jk.common.ChannelSocket processConnection WARNING: processCallbacks status 2 Any help is greatly appreciated. Thanks, Chacko.
RE: Tomcat 4.1 and JDK 1.4 error
I have uninstalled all Java versions using Add/Remove programs before I freshly installed JDK 1.4. This comes up as my current version when I do java -version command. Is there a way to find out if I have other JVM's installed along with 1.4? Thanks, Chacko. -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 12, 2007 10:32 AM To: Tomcat Users List Subject: RE: Tomcat 4.1 and JDK 1.4 error > From: Chacko Kuruvilla [mailto:[EMAIL PROTECTED] > Subject: Tomcat 4.1 and JDK 1.4 error > > bad class file: > c:\j2sdk1.4.1_05\jre\lib\rt.jar(java/lang/Object.class) > > class file has wrong version 48.0, should be 47.0 Your JVM installation continues to be hosed. Version 47 classes are the highest supported by 1.3, 48 is supported by 1.4. You still have an old JVM installed - get rid of it. I'd strongly suggest you remove _all_ JVMss that are anywhere on your system, and install at least 1.5, and preferably 6. Why do you insist on using such old software? If you're going to upgrade, get serious about it. - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 4.1 and JDK 1.4 error
Hello, I currently have a web application running on Tomcat 4.0.6 and JDK 1.3. I am in the process of trying to upgrade to Tomcat 4.1 on JDK 1.4 mainly to run Tomcat as a service since I am not sure if I can run Tomcat 4.0.6 as a windows service. I was able to successfully install and setup the web application on Tomcat 4.1 and JDK 1.4 and also run it as a service. However, while trying to log into my web application, I receive the following error. C:\Program Files\Apache Software Foundation\Tomcat 4.1\work\Standalone\localhost \_\dchqweb\AdminMessages_jsp.java:10: cannot access java.lang.Object bad class file: c:\j2sdk1.4.1_05\jre\lib\rt.jar(java/lang/Object.class) class file has wrong version 48.0, should be 47.0 Please remove or make sure it appears in the correct subdirectory of the classpa th. String gsUserId = ""; ^ 1 error Any ideas? Thanks, Chacko.
RE: Tomcat 4.1 error
Everything works just fine if I start Tomcat using startup.bat. Look like the issue is with running Tomcat 4.1 as a service on JDK 1.3. Not sure what the problem is though. -Original Message- From: Christopher Schultz [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 11, 2007 4:21 PM To: Tomcat Users List Subject: Re: Tomcat 4.1 error -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chacko, Chacko Kuruvilla wrote: > Yep, I uninstalled both JDK 1.4 and Tomcat completely, then re-installed JDK > 1.3 followed by Tomcat 4.1. Something is obviously still wrong. Does that path exist that the service was trying to access? Maybe before you get the service working, you should try starting using bin\startup.bat. It's (somewhat) less complicated than using the service, and you get all error messages on the console, which is nice. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG5wag9CaO5/Lv0PARAslCAJ4muuLjtl8u/Bq5VykDP5BZCplX1gCfSy6Z yHkA8R7bQMPofENyIZIidUU= =GgqS -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 4.1 error
Can somebody help me with this issue? I am trying to setup Tomcat 4.1 on JDK 1.3.1. Installation was successful. However, got the following error in the log file when trying to start the Tomcat service. [2007-09-11 13:11:00] [394 javajni.c] [error] CreateJavaVM Failed [2007-09-11 13:11:00] [992 prunsrv.c] [error] Failed initializing java C:\Program Files\Apache Software Foundation\Tomcat 4.1\bin\bootstrap.jar [2007-09-11 13:11:00] [1260 prunsrv.c] [error] ServiceStart returned 2 Thanks, Chacko.
RE: Tomcat 4.1 error
Yep, I uninstalled both JDK 1.4 and Tomcat completely, then re-installed JDK 1.3 followed by Tomcat 4.1. -Original Message- From: Christopher Schultz [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 11, 2007 2:59 PM To: Tomcat Users List Subject: Re: Tomcat 4.1 error -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chacko, Chacko Kuruvilla wrote: > It sounds like Tomcat is having issues starting JVM to run Tomcat as > a Windows service. I did see similar issue reported by other users, > but could not get a specific one to resolve my issue. I re-installed > with default setup as before. Did you uninstall the old service before you re-installed Tomcat? You might want to do it again. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG5vN09CaO5/Lv0PARAtD9AJ0fYoEsJTlvP6pcHLbaBZxBW35gIACgtckg BJTzKgj9Xg/S5e7sMjFu/mY= =/6DV -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 4.1 error
It sounds like Tomcat is having issues starting JVM to run Tomcat as a Windows service. I did see similar issue reported by other users, but could not get a specific one to resolve my issue. I re-installed with default setup as before. -Original Message- From: Christopher Schultz [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 11, 2007 2:53 PM To: Tomcat Users List Subject: Re: Tomcat 4.1 error -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chacko, Chacko Kuruvilla wrote: > Thanks Chris, that took care of the login page issue. However, since > I ran into database connection problems, I decided to go back to > jdk1.3.1_09 which is what I am currently using with Tomcat 4.0.6. I > reinstalled jdk1.3.1_09 and Tomcat 4.1 on my test machine and tried to > start Tomcat 4.1. But, now I am unable to start Tomcat 4.1 and see the > following error in the log. > > [2007-09-11 13:11:00] [394 javajni.c] [error] CreateJavaVM Failed > [2007-09-11 13:11:00] [992 prunsrv.c] [error] Failed initializing java > C:\Program Files\Apache Software Foundation\Tomcat 4.1\bin\bootstrap.jar > [2007-09-11 13:11:00] [1260 prunsrv.c] [error] ServiceStart returned 2 Looks like you boned your reinstall. Re-read that error message: it says it can't find something in Tomcat 4.1 directory. Did you reinstall to a different location or something? The version of Java, by the way, shouldn't matter too much. The version of Tomcat is way more important. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG5vIS9CaO5/Lv0PARAuIgAKCsJPcsvaiN1N/mLQHAsVpKeCEHwwCeMa1m kDU/BgvvQaqNL3zq1IgQAlM= =Rhb4 -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 4.1 error
Thanks Chris, that took care of the login page issue. However, since I ran into database connection problems, I decided to go back to jdk1.3.1_09 which is what I am currently using with Tomcat 4.0.6. I reinstalled jdk1.3.1_09 and Tomcat 4.1 on my test machine and tried to start Tomcat 4.1. But, now I am unable to start Tomcat 4.1 and see the following error in the log. [2007-09-11 13:11:00] [394 javajni.c] [error] CreateJavaVM Failed [2007-09-11 13:11:00] [992 prunsrv.c] [error] Failed initializing java C:\Program Files\Apache Software Foundation\Tomcat 4.1\bin\bootstrap.jar [2007-09-11 13:11:00] [1260 prunsrv.c] [error] ServiceStart returned 2 Any help is appreciated. Thanks, Chacko. -Original Message- From: Christopher Schultz [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 11, 2007 10:49 AM To: Tomcat Users List Subject: Re: Tomcat 4.1 error -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chacko, Chacko Kuruvilla wrote: > Thank you Chris, an empty import was the issue. I was able to get to > the login page. Now, when I try to login, I get the following error > even though I do find the login page JSP and class file in the > appropriate places. > > The requested resource (/servlet/dchqweb.Userlogin) is not available Tomcat 4.1 might have the "invoker" servlet (the one that actually runs servlets invoked using the /servlet/... URL space) disabled by default. Check the global web.xml file (in TOMCAT_HOME/conf/web.xml) and search for 'invoker' to see if it is enabled or disabled. I thought that the /servlet syntax would have been /servlet/dchqweb/Userlogin - using a '/' instead of using the "." character. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG5rjk9CaO5/Lv0PARAqQcAKCXyjl61wzTVBQU1SpE0GxOU0LY8ACggRDQ M/cJ3I/2pwDTgfDdaiZpdrE= =EX4I -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 4.1 error
Thank you Chris, an empty import was the issue. I was able to get to the login page. Now, when I try to login, I get the following error even though I do find the login page JSP and class file in the appropriate places. The requested resource (/servlet/dchqweb.Userlogin) is not available Any idea why? Thanks, Chacko. -Original Message- From: Christopher Schultz [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 11, 2007 10:18 AM To: Tomcat Users List Subject: Re: Tomcat 4.1 error -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chacko, Chacko Kuruvilla wrote: > I am in the process of trying to upgrade from Tomcat 4.0.6 to 4.1. If you're going to spend time upgrading and testing, why not jump to Tomcat 5.5 or even 6.0? Tomcat 4 is /super/ old. I recently went from 4.1 to 5.5 and it wasn't bad at all. > C:\Program Files\Apache Software Foundation\Tomcat > 4.1\work\Standalone\localhost\_\dchqweb\UserLogin_jsp.java:7: > expected > > import ; > >^ > > 1 error You wrote a JSP that the compiler can't compile. The new compiler is probably more strict than the old one. Check your <@page directive in UserLogin.jsp... perhaps there are empty lines in your "import" directives? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG5rG99CaO5/Lv0PARAu+gAJ9EYvVx5sM55Np6QFw0nUa9Lx5OqwCfRk97 pmgZfzLxKbc/9aeuVkY82Mw= =0Uqc -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 4.1 error
Hello, I am in the process of trying to upgrade from Tomcat 4.0.6 to 4.1. I installed JDK 1.4 and then installed Tomcat 4.1 using the Windows installer package. I am able to successfully get to the Tomcat administration page. However, I get the following error when I try to navigate to the home page of my web application that works just fine on Tomcat 4.0.6. Please help! org.apache.jasper.JasperException: Unable to compile class for JSP An error occurred at line: -1 in the jsp file: null Generated servlet error: [javac] Warning: dchqweb\UserLogin_jsp.java modified in the future. [javac] Compiling 1 source file C:\Program Files\Apache Software Foundation\Tomcat 4.1\work\Standalone\localhost\_\dchqweb\UserLogin_jsp.java:7: expected import ; ^ 1 error Thanks, Chacko.
