EARGENT!
Hi, I am running Tomcat/JServ on Linux with Inprise ejb container. When I access one of my jsp pages, I got error message from Apache's error log (see bellow). I checked mod_jserv.log also. There some info in the mod_jserv.log such as: ...(EMERGENCY) ajp12: can not connect to host 127.0.0.1 ...(EMERGENCY) ajp12: function connection fail. ... ...(ERROR) wrapper: argument[..] /usr/local/jdk1.3/bin/java ... I have no idea what's causing this. And, not all jsp access fails. Most of the jsps functioning correctly. Bellow is the error I found from apache's error_log. I need to fix this now and get the app running right away! So please help me! Many thanks. Lifeng java.rmi.MarshalException: CORBA MARSHAL 0[] at java.lang.Throwable.init(Throwable.java:96) at java.lang.Exception.init(Exception.java:44) at java.io.IOException.init(IOException.java:49) at java.rmi.RemoteException.init(RemoteException.java:58) at java.rmi.MarshalException.init(MarshalException.java:49) at java.lang.reflect.Constructor.newInstance(Native Method) at com.inprise.vbroker.rmi.CORBA.UtilImpl.newInstance(UtilImpl.java:82) at com.inprise.vbroker.rmi.CORBA.UtilImpl._mapSystemException(UtilImpl.java:326 ) at com.inprise.vbroker.rmi.CORBA.UtilImpl.mapSystemException(UtilImpl.java:451) at javax.rmi.CORBA.Util.mapSystemException(Util.java:51) at com.rims.memberlink.ejb._NewEnrollee_Stub.validateNewDemo(_NewEnrollee_Stub. java:208) at com.rims.memberlink.toolkit.NewEnrollmentToolkit.ValidateCurrentPage(NewEnro llmentToolkit.java:1318) at com.rims.memberlink.toolkit.NewEnrollmentToolkit.processPage(NewEnrollmentTo olkit.java:995) at _0002fValidate_0002ejspValidate_jsp_0._jspService(_0002fValidate_0002ejspVal idate_jsp_0.java:373) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:126) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.ja va:174) at org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:261) at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:369) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:503) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:559) 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:498) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: EARGENT!
Do you have Apache running? Or you run in standalone mode? (Only Tomcat) Original Message On 2/13/01, 9:45:08 AM, "Lifeng Xu" [EMAIL PROTECTED] wrote regarding EARGENT!: Hi, I am running Tomcat/JServ on Linux with Inprise ejb container. When I access one of my jsp pages, I got error message from Apache's error log (see bellow). I checked mod_jserv.log also. There some info in the mod_jserv.log such as: ...(EMERGENCY) ajp12: can not connect to host 127.0.0.1 ...(EMERGENCY) ajp12: function connection fail. ... ...(ERROR) wrapper: argument[..] /usr/local/jdk1.3/bin/java ... I have no idea what's causing this. And, not all jsp access fails. Most of the jsps functioning correctly. Bellow is the error I found from apache's error_log. I need to fix this now and get the app running right away! So please help me! Many thanks. Lifeng java.rmi.MarshalException: CORBA MARSHAL 0[] at java.lang.Throwable.init(Throwable.java:96) at java.lang.Exception.init(Exception.java:44) at java.io.IOException.init(IOException.java:49) at java.rmi.RemoteException.init(RemoteException.java:58) at java.rmi.MarshalException.init(MarshalException.java:49) at java.lang.reflect.Constructor.newInstance(Native Method) at com.inprise.vbroker.rmi.CORBA.UtilImpl.newInstance(UtilImpl.java:82) at com.inprise.vbroker.rmi.CORBA.UtilImpl._mapSystemException(UtilImpl.java:3 26 ) at com.inprise.vbroker.rmi.CORBA.UtilImpl.mapSystemException(UtilImpl.java:45 1) at javax.rmi.CORBA.Util.mapSystemException(Util.java:51) at com.rims.memberlink.ejb._NewEnrollee_Stub.validateNewDemo(_NewEnrollee_Stu b. java:208) at com.rims.memberlink.toolkit.NewEnrollmentToolkit.ValidateCurrentPage(NewEn ro llmentToolkit.java:1318) at com.rims.memberlink.toolkit.NewEnrollmentToolkit.processPage(NewEnrollment To olkit.java:995) at _0002fValidate_0002ejspValidate_jsp_0._jspService(_0002fValidate_0002ejspV al idate_jsp_0.java:373) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:126) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet. ja va:174) at org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:261) at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:369) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:50 3) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:559) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnecti on (Ajp12ConnectionHandler.java:156) at org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java:3 38 ) at java.lang.Thread.run(Thread.java:498) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] NOTICE: This communication may contain confidential or other privileged information. If you are not the intended recipient, or believe that you have received this communication in error, please do not print, copy, retransmit, disseminate, or otherwise use the information. Also, please indicate to the sender that you have received this email in error, and delete the copy you received. Any communication that does not relate to official Columbia business is that of the sender and is neither given nor endorsed by Columbia. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: EARGENT!
Thanks for your response! I configured to start Tomcat when apache starts. Seems to me that they starts ok... Lifeng -Original Message- From: John Golubenko [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 13, 2001 11:51 AM To: [EMAIL PROTECTED] Subject: Re: EARGENT! Do you have Apache running? Or you run in standalone mode? (Only Tomcat) Original Message On 2/13/01, 9:45:08 AM, "Lifeng Xu" [EMAIL PROTECTED] wrote regarding EARGENT!: Hi, I am running Tomcat/JServ on Linux with Inprise ejb container. When I access one of my jsp pages, I got error message from Apache's error log (see bellow). I checked mod_jserv.log also. There some info in the mod_jserv.log such as: ...(EMERGENCY) ajp12: can not connect to host 127.0.0.1 ...(EMERGENCY) ajp12: function connection fail. ... ...(ERROR) wrapper: argument[..] /usr/local/jdk1.3/bin/java ... I have no idea what's causing this. And, not all jsp access fails. Most of the jsps functioning correctly. Bellow is the error I found from apache's error_log. I need to fix this now and get the app running right away! So please help me! Many thanks. Lifeng java.rmi.MarshalException: CORBA MARSHAL 0[] at java.lang.Throwable.init(Throwable.java:96) at java.lang.Exception.init(Exception.java:44) at java.io.IOException.init(IOException.java:49) at java.rmi.RemoteException.init(RemoteException.java:58) at java.rmi.MarshalException.init(MarshalException.java:49) at java.lang.reflect.Constructor.newInstance(Native Method) at com.inprise.vbroker.rmi.CORBA.UtilImpl.newInstance(UtilImpl.java:82) at com.inprise.vbroker.rmi.CORBA.UtilImpl._mapSystemException(UtilImpl.java:3 26 ) at com.inprise.vbroker.rmi.CORBA.UtilImpl.mapSystemException(UtilImpl.java:45 1) at javax.rmi.CORBA.Util.mapSystemException(Util.java:51) at com.rims.memberlink.ejb._NewEnrollee_Stub.validateNewDemo(_NewEnrollee_Stu b. java:208) at com.rims.memberlink.toolkit.NewEnrollmentToolkit.ValidateCurrentPage(NewEn ro llmentToolkit.java:1318) at com.rims.memberlink.toolkit.NewEnrollmentToolkit.processPage(NewEnrollment To olkit.java:995) at _0002fValidate_0002ejspValidate_jsp_0._jspService(_0002fValidate_0002ejspV al idate_jsp_0.java:373) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:126) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet. ja va:174) at org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:261) at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:369) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:50 3) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:559) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnecti on (Ajp12ConnectionHandler.java:156) at org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java:3 38 ) at java.lang.Thread.run(Thread.java:498) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] NOTICE: This communication may contain confidential or other privileged information. If you are not the intended recipient, or believe that you have received this communication in error, please do not print, copy, retransmit, disseminate, or otherwise use the information. Also, please indicate to the sender that you have received this email in error, and delete the copy you received. Any communication that does not relate to official Columbia business is that of the sender and is neither given nor endorsed by Columbia. Thank you. - 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: EARGENT!
Probably not. It's clear that you got problems between two of those. The AJP12 protocol tomcat uses to communicate with Apache (that's why you load mod_jser.o in Apache), First thing to do, is try to load the pages using the Tomcat's default port 8080, like localhost:8080/path/to/jsp , /examples, /path/to/servlet/ServletName, etc. If 8080 port isn't working, check the $TOMCAT_HOME/conf/server.xml file. (or check by running: cat $TOMCAT_HOME/conf/server.xml | grep 80, this will show the 80* ports you have, if any at all.). If you got your pages loaded under 8080, then it's a Apaches-Tomcat problem. The configuration file maybe not valid. You may send the apache's httpd.conf and tomcats server.xml file here, so we can take a look at it. Because I personally have no idea what's going on there. - John. P.S. This is why I think it is: ...(EMERGENCY) ajp12: can not connect to host 127.0.0.1 ...(EMERGENCY) ajp12: function connection fail. And: org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnecti on (Ajp12ConnectionHandler.java:156) Original Message On 2/13/01, 9:58:29 AM, "Lifeng Xu" [EMAIL PROTECTED] wrote regarding RE: EARGENT!: Thanks for your response! I configured to start Tomcat when apache starts. Seems to me that they starts ok... Lifeng -Original Message- From: John Golubenko [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 13, 2001 11:51 AM To: [EMAIL PROTECTED] Subject: Re: EARGENT! Do you have Apache running? Or you run in standalone mode? (Only Tomcat) Original Message On 2/13/01, 9:45:08 AM, "Lifeng Xu" [EMAIL PROTECTED] wrote regarding EARGENT!: Hi, I am running Tomcat/JServ on Linux with Inprise ejb container. When I access one of my jsp pages, I got error message from Apache's error log (see bellow). I checked mod_jserv.log also. There some info in the mod_jserv.log such as: ...(EMERGENCY) ajp12: can not connect to host 127.0.0.1 ...(EMERGENCY) ajp12: function connection fail. ... ...(ERROR) wrapper: argument[..] /usr/local/jdk1.3/bin/java ... I have no idea what's causing this. And, not all jsp access fails. Most of the jsps functioning correctly. Bellow is the error I found from apache's error_log. I need to fix this now and get the app running right away! So please help me! Many thanks. Lifeng java.rmi.MarshalException: CORBA MARSHAL 0[] at java.lang.Throwable.init(Throwable.java:96) at java.lang.Exception.init(Exception.java:44) at java.io.IOException.init(IOException.java:49) at java.rmi.RemoteException.init(RemoteException.java:58) at java.rmi.MarshalException.init(MarshalException.java:49) at java.lang.reflect.Constructor.newInstance(Native Method) at com.inprise.vbroker.rmi.CORBA.UtilImpl.newInstance(UtilImpl.java:82) at com.inprise.vbroker.rmi.CORBA.UtilImpl._mapSystemException(UtilImpl.java:3 26 ) at com.inprise.vbroker.rmi.CORBA.UtilImpl.mapSystemException(UtilImpl.java:45 1) at javax.rmi.CORBA.Util.mapSystemException(Util.java:51) at com.rims.memberlink.ejb._NewEnrollee_Stub.validateNewDemo(_NewEnrollee_Stu b. java:208) at com.rims.memberlink.toolkit.NewEnrollmentToolkit.ValidateCurrentPage(NewEn ro llmentToolkit.java:1318) at com.rims.memberlink.toolkit.NewEnrollmentToolkit.processPage(NewEnrollment To olkit.java:995) at _0002fValidate_0002ejspValidate_jsp_0._jspService(_0002fValidate_0002ejspV al idate_jsp_0.java:373) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:126) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet. ja va:174) at org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:261) at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:369) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:50 3) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:559) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnecti on (Ajp12ConnectionHandler.java:156) at org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java:3 38 ) at java.lang.Thread.run(Thread.java:498) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] NOTICE: This communication may contain confidential or other privileged information. If you are not the intended recipient, or believe that you have received this communication in error, please do not print, copy, retransmit, disseminate, or otherwise use the information. Also, please indicate to the sender that you have received this email in error, and delete the cop
RE: EARGENT!
John, Thank you again for your help! My Tomcat can start. I can run some of my jsps through Tomcat, but not all of them. Attached is all of my configuration files. The httpd.com is located in /usr/local/apache/conf directory, the mod_jserv.log is in .../apache/logs, and the rest of them are located in /opt/MemberLink_IAS/com/rims/memberlink/conf directory. Thank you very much Lifeng -Original Message- From: John Golubenko [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 13, 2001 12:23 PM To: [EMAIL PROTECTED] Subject: RE: EARGENT! Probably not. It's clear that you got problems between two of those. The AJP12 protocol tomcat uses to communicate with Apache (that's why you load mod_jser.o in Apache), First thing to do, is try to load the pages using the Tomcat's default port 8080, like localhost:8080/path/to/jsp , /examples, /path/to/servlet/ServletName, etc. If 8080 port isn't working, check the $TOMCAT_HOME/conf/server.xml file. (or check by running: cat $TOMCAT_HOME/conf/server.xml | grep 80, this will show the 80* ports you have, if any at all.). If you got your pages loaded under 8080, then it's a Apaches-Tomcat problem. The configuration file maybe not valid. You may send the apache's httpd.conf and tomcats server.xml file here, so we can take a look at it. Because I personally have no idea what's going on there. - John. P.S. This is why I think it is: ...(EMERGENCY) ajp12: can not connect to host 127.0.0.1 ...(EMERGENCY) ajp12: function connection fail. And: org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnecti on (Ajp12ConnectionHandler.java:156) Original Message On 2/13/01, 9:58:29 AM, "Lifeng Xu" [EMAIL PROTECTED] wrote regarding RE: EARGENT!: Thanks for your response! I configured to start Tomcat when apache starts. Seems to me that they starts ok... Lifeng -Original Message- From: John Golubenko [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 13, 2001 11:51 AM To: [EMAIL PROTECTED] Subject: Re: EARGENT! Do you have Apache running? Or you run in standalone mode? (Only Tomcat) Original Message On 2/13/01, 9:45:08 AM, "Lifeng Xu" [EMAIL PROTECTED] wrote regarding EARGENT!: Hi, I am running Tomcat/JServ on Linux with Inprise ejb container. When I access one of my jsp pages, I got error message from Apache's error log (see bellow). I checked mod_jserv.log also. There some info in the mod_jserv.log such as: ...(EMERGENCY) ajp12: can not connect to host 127.0.0.1 ...(EMERGENCY) ajp12: function connection fail. ... ...(ERROR) wrapper: argument[..] /usr/local/jdk1.3/bin/java ... I have no idea what's causing this. And, not all jsp access fails. Most of the jsps functioning correctly. Bellow is the error I found from apache's error_log. I need to fix this now and get the app running right away! So please help me! Many thanks. Lifeng java.rmi.MarshalException: CORBA MARSHAL 0[] at java.lang.Throwable.init(Throwable.java:96) at java.lang.Exception.init(Exception.java:44) at java.io.IOException.init(IOException.java:49) at java.rmi.RemoteException.init(RemoteException.java:58) at java.rmi.MarshalException.init(MarshalException.java:49) at java.lang.reflect.Constructor.newInstance(Native Method) at com.inprise.vbroker.rmi.CORBA.UtilImpl.newInstance(UtilImpl.java:82) at com.inprise.vbroker.rmi.CORBA.UtilImpl._mapSystemException(UtilImpl.java:3 26 ) at com.inprise.vbroker.rmi.CORBA.UtilImpl.mapSystemException(UtilImpl.java:45 1) at javax.rmi.CORBA.Util.mapSystemException(Util.java:51) at com.rims.memberlink.ejb._NewEnrollee_Stub.validateNewDemo(_NewEnrollee_Stu b. java:208) at com.rims.memberlink.toolkit.NewEnrollmentToolkit.ValidateCurrentPage(NewEn ro llmentToolkit.java:1318) at com.rims.memberlink.toolkit.NewEnrollmentToolkit.processPage(NewEnrollment To olkit.java:995) at _0002fValidate_0002ejspValidate_jsp_0._jspService(_0002fValidate_0002ejspV al idate_jsp_0.java:373) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:126) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet. ja va:174) at org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:261) at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:369) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:50 3) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:559) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnecti on (Ajp12ConnectionHandler.java:156) at org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java:3 38 ) at java.lang.Thread
RE: EARGENT!
Ok, I've looked at configs (a bit), first question comes in mind: Why do you run Jserv and Tomcat? The Tomcat is the one you should run, and disable Jserv. Jserv is only needed (if you need Tomcat+Apache as all have) to get mod_jserv.o library, to use ajp12 protocol. If you look at server.xml, and jserv.conf, both servers are using same 8007 port to connect. You should shutdown the Jserv, uncomment this in server.xml of Tomcat: !-- Connector className="org.apache.tomcat.service.SimpleTcpConnector" Parameter name="handler" value="org.apache.tomcat.service.http.HttpConnectionHandler"/ Parameter name="port" value="8080"/ /Connector -- Then load the pages like: localhost:8080/path/to/pages Where 8080 is the port it uses to serve the pages. The stuff you got in jserv.properties all goes into /path/to/web_root/WEB-INF/web.xml file. I'm going for lunch now, I'll be back, and may help (if I do so) more. While im out, please check the FAQ on tomcat's web-site, about web.xml file, and how to move configuration from jserv.properties to it. Till then, John. P.S. People, help him out! Original Message On 2/13/01, 11:11:46 AM, "Lifeng Xu" [EMAIL PROTECTED] wrote regarding RE: EARGENT!: John, Thank you again for your help! My Tomcat can start. I can run some of my jsps through Tomcat, but not all of them. Attached is all of my configuration files. The httpd.com is located in /usr/local/apache/conf directory, the mod_jserv.log is in .../apache/logs, and the rest of them are located in /opt/MemberLink_IAS/com/rims/memberlink/conf directory. Thank you very much Lifeng -Original Message- From: John Golubenko [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 13, 2001 12:23 PM To: [EMAIL PROTECTED] Subject: RE: EARGENT! Probably not. It's clear that you got problems between two of those. The AJP12 protocol tomcat uses to communicate with Apache (that's why you load mod_jser.o in Apache), First thing to do, is try to load the pages using the Tomcat's default port 8080, like localhost:8080/path/to/jsp , /examples, /path/to/servlet/ServletName, etc. If 8080 port isn't working, check the $TOMCAT_HOME/conf/server.xml file. (or check by running: cat $TOMCAT_HOME/conf/server.xml | grep 80, this will show the 80* ports you have, if any at all.). If you got your pages loaded under 8080, then it's a Apaches-Tomcat problem. The configuration file maybe not valid. You may send the apache's httpd.conf and tomcats server.xml file here, so we can take a look at it. Because I personally have no idea what's going on there. - John. P.S. This is why I think it is: ...(EMERGENCY) ajp12: can not connect to host 127.0.0.1 ...(EMERGENCY) ajp12: function connection fail. And: org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnecti on (Ajp12ConnectionHandler.java:156) Original Message On 2/13/01, 9:58:29 AM, "Lifeng Xu" [EMAIL PROTECTED] wrote regarding RE: EARGENT!: Thanks for your response! I configured to start Tomcat when apache starts. Seems to me that they starts ok... Lifeng -Original Message- From: John Golubenko [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 13, 2001 11:51 AM To: [EMAIL PROTECTED] Subject: Re: EARGENT! Do you have Apache running? Or you run in standalone mode? (Only Tomcat) Original Message On 2/13/01, 9:45:08 AM, "Lifeng Xu" [EMAIL PROTECTED] wrote regarding EARGENT!: Hi, I am running Tomcat/JServ on Linux with Inprise ejb container. When I access one of my jsp pages, I got error message from Apache's error log (see bellow). I checked mod_jserv.log also. There some info in the mod_jserv.log such as: ...(EMERGENCY) ajp12: can not connect to host 127.0.0.1 ...(EMERGENCY) ajp12: function connection fail. ... ...(ERROR) wrapper: argument[..] /usr/local/jdk1.3/bin/java ... I have no idea what's causing this. And, not all jsp access fails. Most of the jsps functioning correctly. Bellow is the error I found from apache's error_log. I need to fix this now and get the app running right away! So please help me! Many thanks. Lifeng java.rmi.MarshalException: CORBA MARSHAL 0[] at java.lang.Throwable.init(Throwable.java:96) at java.lang.Exception.init(Exception.java:44) at java.io.IOException.init(IOException.java:49) at java.rmi.RemoteException.init(RemoteException.java:58) at java.rmi.MarshalException.init(MarshalException.java:49) at java.lang.reflect.Constructor.newInstance(Native Method) at com.inprise.vbroker.rmi.CORBA.UtilImpl.newInstance(UtilImpl.java:82) at com.inprise.vbroker.rmi.CORBA.UtilImpl._mapSystemException(UtilImpl.java:3 26 ) at com.inprise.vbroker.rmi.CORBA.UtilImpl.mapSystemException(Ut
RE: EARGENT!
Can I have apache starts Tomcat while not having JServ running? How do I turn JServ off then? You are right, the only thing I care about is Tomcat, but I also need it be started automaticly by Apache. I thought what I do was the only way to get that happen. Thanks. Lifeng -Original Message- From: John Golubenko [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 13, 2001 1:31 PM To: [EMAIL PROTECTED] Subject: RE: EARGENT! Ok, I've looked at configs (a bit), first question comes in mind: Why do you run Jserv and Tomcat? The Tomcat is the one you should run, and disable Jserv. Jserv is only needed (if you need Tomcat+Apache as all have) to get mod_jserv.o library, to use ajp12 protocol. If you look at server.xml, and jserv.conf, both servers are using same 8007 port to connect. You should shutdown the Jserv, uncomment this in server.xml of Tomcat: !-- Connector className="org.apache.tomcat.service.SimpleTcpConnector" Parameter name="handler" value="org.apache.tomcat.service.http.HttpConnectionHandler"/ Parameter name="port" value="8080"/ /Connector -- Then load the pages like: localhost:8080/path/to/pages Where 8080 is the port it uses to serve the pages. The stuff you got in jserv.properties all goes into /path/to/web_root/WEB-INF/web.xml file. I'm going for lunch now, I'll be back, and may help (if I do so) more. While im out, please check the FAQ on tomcat's web-site, about web.xml file, and how to move configuration from jserv.properties to it. Till then, John. P.S. People, help him out! Original Message On 2/13/01, 11:11:46 AM, "Lifeng Xu" [EMAIL PROTECTED] wrote regarding RE: EARGENT!: John, Thank you again for your help! My Tomcat can start. I can run some of my jsps through Tomcat, but not all of them. Attached is all of my configuration files. The httpd.com is located in /usr/local/apache/conf directory, the mod_jserv.log is in .../apache/logs, and the rest of them are located in /opt/MemberLink_IAS/com/rims/memberlink/conf directory. Thank you very much Lifeng -Original Message- From: John Golubenko [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 13, 2001 12:23 PM To: [EMAIL PROTECTED] Subject: RE: EARGENT! Probably not. It's clear that you got problems between two of those. The AJP12 protocol tomcat uses to communicate with Apache (that's why you load mod_jser.o in Apache), First thing to do, is try to load the pages using the Tomcat's default port 8080, like localhost:8080/path/to/jsp , /examples, /path/to/servlet/ServletName, etc. If 8080 port isn't working, check the $TOMCAT_HOME/conf/server.xml file. (or check by running: cat $TOMCAT_HOME/conf/server.xml | grep 80, this will show the 80* ports you have, if any at all.). If you got your pages loaded under 8080, then it's a Apaches-Tomcat problem. The configuration file maybe not valid. You may send the apache's httpd.conf and tomcats server.xml file here, so we can take a look at it. Because I personally have no idea what's going on there. - John. P.S. This is why I think it is: ...(EMERGENCY) ajp12: can not connect to host 127.0.0.1 ...(EMERGENCY) ajp12: function connection fail. And: org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnecti on (Ajp12ConnectionHandler.java:156) Original Message On 2/13/01, 9:58:29 AM, "Lifeng Xu" [EMAIL PROTECTED] wrote regarding RE: EARGENT!: Thanks for your response! I configured to start Tomcat when apache starts. Seems to me that they starts ok... Lifeng -Original Message- From: John Golubenko [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 13, 2001 11:51 AM To: [EMAIL PROTECTED] Subject: Re: EARGENT! Do you have Apache running? Or you run in standalone mode? (Only Tomcat) Original Message On 2/13/01, 9:45:08 AM, "Lifeng Xu" [EMAIL PROTECTED] wrote regarding EARGENT!: Hi, I am running Tomcat/JServ on Linux with Inprise ejb container. When I access one of my jsp pages, I got error message from Apache's error log (see bellow). I checked mod_jserv.log also. There some info in the mod_jserv.log such as: ...(EMERGENCY) ajp12: can not connect to host 127.0.0.1 ...(EMERGENCY) ajp12: function connection fail. ... ...(ERROR) wrapper: argument[..] /usr/local/jdk1.3/bin/java ... I have no idea what's causing this. And, not all jsp access fails. Most of the jsps functioning correctly. Bellow is the error I found from apache's error_log. I need to fix this now and get the app running right away! So please help me! Many thanks. Lifeng java.rmi.MarshalException: CORBA MARSHAL 0[] at java.lang.Throwable.init(Throwable.java:96) at java.lang.Exception.init(Exception.java:44) at java.io.IOException.init(I
RE: EARGENT!
Thanks John, for your help. Yes, the configuration I have was working before -- actually, it's still working, for most of our jsp ejbs, except the bean that causing the problem. It's just recently we changed our ejb container, so we need to modified the configuration to work with the new pieces. The guy who origionally developed this has gone, but we know it worked. Thanks again. Lifeng -Original Message- From: John Golubenko [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 13, 2001 3:41 PM To: [EMAIL PROTECTED] Subject: RE: EARGENT! Well, the Jserv and Tomcat and Apache is all different things. The Jserv was the first project (I believe) of Apache Group to handle the Servlets. While Tomcat is completely different project, which handles Servlets, and JSP's. You probably can't start the tomcat by apache, since the tomcat has to be started first. But you do can start the apache from tomcat, by modifying the tomcat.sh, and adding the apaches startup script at the end, or better modifying the /etc/rc.d/rc.httpd (booting script) and add tomcat and then apache startup scripts. What you need to do, is, fallow the Jserv installation process (I think you've done it already), make sure that mod_jser.o is loaded into apache at startup. Then, include the $TOMCAT_HOME/conf/apache-tomcat.conf into the bottom of Apache's $APACHE/conf/httpd.conf file. (Include /path/to/apache-tomcat.conf) Modify the $TOMCAT_HOME/conf/server.xml file, to fit your need. Move all properties from jserv.properties into $WWW_ROOT/WEB-INF/web.xml file. (read http://jakarta.apache.org/jyve-faq/Turbine/screen/MainMenu/action/SetAll /screen/DisplayTopics/faq_id/12/project_id/2;jsessionid=7yjh5swq41 ). After setting things up, run both or 1 (tomcat) servers. You should be able to do everything in Tomcat, w/o even using apache. Probably starting from scratch is best | fastest way to go. Also, this stuff you have, where did you got it? Was it working before? You may want to back-up, and see when things went wrong. Good Luck. - John. Original Message On 2/13/01, 11:49:44 AM, "Lifeng Xu" [EMAIL PROTECTED] wrote regarding RE: EARGENT!: Can I have apache starts Tomcat while not having JServ running? How do I turn JServ off then? You are right, the only thing I care about is Tomcat, but I also need it be started automaticly by Apache. I thought what I do was the only way to get that happen. Thanks. Lifeng -Original Message- From: John Golubenko [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 13, 2001 1:31 PM To: [EMAIL PROTECTED] Subject: RE: EARGENT! Ok, I've looked at configs (a bit), first question comes in mind: Why do you run Jserv and Tomcat? The Tomcat is the one you should run, and disable Jserv. Jserv is only needed (if you need Tomcat+Apache as all have) to get mod_jserv.o library, to use ajp12 protocol. If you look at server.xml, and jserv.conf, both servers are using same 8007 port to connect. You should shutdown the Jserv, uncomment this in server.xml of Tomcat: !-- Connector className="org.apache.tomcat.service.SimpleTcpConnector" Parameter name="handler" value="org.apache.tomcat.service.http.HttpConnectionHandler"/ Parameter name="port" value="8080"/ /Connector -- Then load the pages like: localhost:8080/path/to/pages Where 8080 is the port it uses to serve the pages. The stuff you got in jserv.properties all goes into /path/to/web_root/WEB-INF/web.xml file. I'm going for lunch now, I'll be back, and may help (if I do so) more. While im out, please check the FAQ on tomcat's web-site, about web.xml file, and how to move configuration from jserv.properties to it. Till then, John. P.S. People, help him out! Original Message On 2/13/01, 11:11:46 AM, "Lifeng Xu" [EMAIL PROTECTED] wrote regarding RE: EARGENT!: John, Thank you again for your help! My Tomcat can start. I can run some of my jsps through Tomcat, but not all of them. Attached is all of my configuration files. The httpd.com is located in /usr/local/apache/conf directory, the mod_jserv.log is in .../apache/logs, and the rest of them are located in /opt/MemberLink_IAS/com/rims/memberlink/conf directory. Thank you very much Lifeng -Original Message- From: John Golubenko [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 13, 2001 12:23 PM To: [EMAIL PROTECTED] Subject: RE: EARGENT! Probably not. It's clear that you got problems between two of those. The AJP12 protocol tomcat uses to communicate with Apache (that's why you load mod_jser.o in Apache), First thing to do, is try to load the pages using the Tomcat's default port 8080, like localhost:8080/path/to/jsp , /examples, /path/to/servlet/ServletName, etc. If 8080 port isn't working, check the $TOMCAT_HOME/conf/server.xml file. (or check by runnin
RE: EARGENT!
Well, the Jserv and Tomcat and Apache is all different things. The Jserv was the first project (I believe) of Apache Group to handle the Servlets. While Tomcat is completely different project, which handles Servlets, and JSP's. You probably can't start the tomcat by apache, since the tomcat has to be started first. But you do can start the apache from tomcat, by modifying the tomcat.sh, and adding the apaches startup script at the end, or better modifying the /etc/rc.d/rc.httpd (booting script) and add tomcat and then apache startup scripts. What you need to do, is, fallow the Jserv installation process (I think you've done it already), make sure that mod_jser.o is loaded into apache at startup. Then, include the $TOMCAT_HOME/conf/apache-tomcat.conf into the bottom of Apache's $APACHE/conf/httpd.conf file. (Include /path/to/apache-tomcat.conf) Modify the $TOMCAT_HOME/conf/server.xml file, to fit your need. Move all properties from jserv.properties into $WWW_ROOT/WEB-INF/web.xml file. (read http://jakarta.apache.org/jyve-faq/Turbine/screen/MainMenu/action/SetAll /screen/DisplayTopics/faq_id/12/project_id/2;jsessionid=7yjh5swq41 ). After setting things up, run both or 1 (tomcat) servers. You should be able to do everything in Tomcat, w/o even using apache. Probably starting from scratch is best | fastest way to go. Also, this stuff you have, where did you got it? Was it working before? You may want to back-up, and see when things went wrong. Good Luck. - John. Original Message On 2/13/01, 11:49:44 AM, "Lifeng Xu" [EMAIL PROTECTED] wrote regarding RE: EARGENT!: Can I have apache starts Tomcat while not having JServ running? How do I turn JServ off then? You are right, the only thing I care about is Tomcat, but I also need it be started automaticly by Apache. I thought what I do was the only way to get that happen. Thanks. Lifeng -Original Message- From: John Golubenko [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 13, 2001 1:31 PM To: [EMAIL PROTECTED] Subject: RE: EARGENT! Ok, I've looked at configs (a bit), first question comes in mind: Why do you run Jserv and Tomcat? The Tomcat is the one you should run, and disable Jserv. Jserv is only needed (if you need Tomcat+Apache as all have) to get mod_jserv.o library, to use ajp12 protocol. If you look at server.xml, and jserv.conf, both servers are using same 8007 port to connect. You should shutdown the Jserv, uncomment this in server.xml of Tomcat: !-- Connector className="org.apache.tomcat.service.SimpleTcpConnector" Parameter name="handler" value="org.apache.tomcat.service.http.HttpConnectionHandler"/ Parameter name="port" value="8080"/ /Connector -- Then load the pages like: localhost:8080/path/to/pages Where 8080 is the port it uses to serve the pages. The stuff you got in jserv.properties all goes into /path/to/web_root/WEB-INF/web.xml file. I'm going for lunch now, I'll be back, and may help (if I do so) more. While im out, please check the FAQ on tomcat's web-site, about web.xml file, and how to move configuration from jserv.properties to it. Till then, John. P.S. People, help him out! Original Message On 2/13/01, 11:11:46 AM, "Lifeng Xu" [EMAIL PROTECTED] wrote regarding RE: EARGENT!: John, Thank you again for your help! My Tomcat can start. I can run some of my jsps through Tomcat, but not all of them. Attached is all of my configuration files. The httpd.com is located in /usr/local/apache/conf directory, the mod_jserv.log is in .../apache/logs, and the rest of them are located in /opt/MemberLink_IAS/com/rims/memberlink/conf directory. Thank you very much Lifeng -Original Message- From: John Golubenko [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 13, 2001 12:23 PM To: [EMAIL PROTECTED] Subject: RE: EARGENT! Probably not. It's clear that you got problems between two of those. The AJP12 protocol tomcat uses to communicate with Apache (that's why you load mod_jser.o in Apache), First thing to do, is try to load the pages using the Tomcat's default port 8080, like localhost:8080/path/to/jsp , /examples, /path/to/servlet/ServletName, etc. If 8080 port isn't working, check the $TOMCAT_HOME/conf/server.xml file. (or check by running: cat $TOMCAT_HOME/conf/server.xml | grep 80, this will show the 80* ports you have, if any at all.). If you got your pages loaded under 8080, then it's a Apaches-Tomcat problem. The configuration file maybe not valid. You may send the apache's httpd.conf and tomcats server.xml file here, so we can take a look at it. Because I personally have no idea what's going on there. - John. P.S. This is why I think it is: ...(EMERGENCY) ajp12: can not connec
