Avoiding tomcat crashes or do auto restarts?
Platform: Intel PIII, RedHat 8, IBMJava2-SDK-1.3.1-3.0, tomcat4-4.1.18-full.1jpp We have found that if we push the server too hard, the Java VM running tomcat crashes. I'm assuming it's running out of memory, or file descriptors, or somesuch. Does anyone have a solution to this type of problem? Config parameters that can be tuned? A watchdog process that will restart the Java VM if it crashes (ie. something like the apache httpd does)? A temporary problem caused by a restart is acceptable. Flatlining due to a VM crash isn't. - Steinar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
tomcat 4.1.18 won't work with IBM Java SDK 1.1.8
Platform: dual Intel PIII, RedHat 8.0, IBM Java SDK 1.1.8 (from RPM), tomcat 4.1.18 (from Henri Gomez' 4.1.18-1jpp RPM) Tomcat 4.1.18 won't work with IBM Java 1.1.8 on this platform. I get tomcat working with both Blackdown Sun JDK 1.3.1 and 1.4.1 on the same platform. Is tomcat 4.1.18 supposed to work with IBM Java 1.1.8? Should I expect the linux port of IBM Java 1.1.8 to work on RedHat 8? (glibc incompatibilities? gcc incompatibilities?) Here are some facts: When I let JAVA_HOME in /etc/tomcat4/conf/tomcat.conf point to Blackdown Sun JDK 1.3.1 and 1.4.1, tomcat 4.1.18 starts and runs normally: - I can access demo applications on http://127.0.0.1:8080/ - /etc/init.d/tomcat4 stop and restart works - netstat -a shows a listener on port 8005 (it's also possible to telnet to that port) - stuff is written to files in /var/log/tomcat4/ Ie. from a brief test, tomcat seems to be working. When I edit JAVA_HOME to point to /usr/jdk118, I see the following - Nothing responds on http://127.0.0.1:8080/ - /etc/init.d/tomcat4 stop and restart hangs forever when attempting to stop tomcat - netstat -a doesn't show anything listening to port 8005, and it's not possible to telnet into that port - nothing is written to files in /var/log/tomcat4/, but the /var/log/tomcat4/catalina.out file is touched (timestamp is updated) - ps axu | grep tomcat lists a process /usr/jdk118/bin/linux/native_threads/java -Djava.endorsed.dirs= -classpath /usr/jdk118/lib/tools.jar:/var/tomcat4/bin/bootstrap.jar -Dcatalina.base=/var/tomcat4 -Dcatalina.home=/var/tomcat4 -Djava.io.tmpdir=/var/tomcat4/temp org/apache/catalina/startup/Bootstrap start Thanx! - Steinar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat 4.1.18 won't work with IBM Java SDK 1.1.8
Larry Meadors [EMAIL PROTECTED]: [EMAIL PROTECTED] 03/07/03 05:45 AM Is tomcat 4.1.18 supposed to work with IBM Java 1.1.8? No. It requires 1.2 or later. http://jakarta.apache.org/tomcat/tomcat-4.1-doc/RUNNING.txt An excerpt: [snip!] * Download a Java Development Kit (JDK) release (version 1.2 or later) from: http://java.sun.com/j2se/ Ie. it requires Java2? I thought that IBM version numbers didn't neccessarily follow Sun's version numbers, and that 1.1.8 was Java2. Looks like I was wrong: http://www-106.ibm.com/developerworks/java/jdk/118/linux/ I guess I will see what I can find from this website: http://www-106.ibm.com/developerworks/java/jdk/linux140/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat 4.1.18 won't work with IBM Java SDK 1.1.8
Jon Roberts [EMAIL PROTECTED]: Shapira, Yoav wrote: As an aside, don't pigeon-hole yourself into the IBM JDK. Try Sun's and others as well (JRockit etc.) I'm not sure how active development is on the IBM JDK. I know it used to be more active in the past than it is now, that's for sure. If you're talking Linux, don't forget Blackdown ( www.blackdown.org ). Their JDK 1.4.1 works fine with Tomcat 4.1.18, and their releases have been top notch IMHO. I have been using Blackdown JDK 1.3.1, and we've had problems with the tomcat performance. We have a problem handling peak loads. I've heard that switching to the IBM VM could improve tomcat performance, so I wanted to try that out. Thanx! - Steinar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat 4.1.18 won't work with IBM Java SDK 1.1.8
Chong Yu Meng [EMAIL PROTECTED]: I'm using IBM's Java2 SDK 1.3.1 with Tomcat 4.1.18, not JDK 1.1.8. You can download version 1.3.1 from IBM's Developerworks website. If you need help installing the IBM Java2 SDK, I've done a write-up on it. See http://linux-sxs.org/programming/java131.html Interesting reading. Thanx for writing this up. Incidentially, RedHat 8 is a gcc 3.2-based distro. So far I seem to be able to run Blackdown Sun JDK 1.3.1 and 1.4.1, and IBM 1.1.8 and 1.4.0 on it. The Blackdown Sun JDK 1.3.1 is the exact same package as I've been running on RedHat 7.2 for quite a while now. There are 2 Java2 versions. Use 1.3.1. You *can* use 1.4, but there are a few issues specific to that version of Java -- configuration related. I haven't finished my write-up on that one yet. Ah, OK. I downloaded 1.4 today, because that was the only one I found on the download page. I'll look for 1.3.1 on monday. Thanx! - Steinar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: automatically redirect http to https in tomcat
[EMAIL PROTECTED]: Yes, I use struts. It used to automatically redirect http request to https with https setup in ssl.conf. After I upgraded to b3, 4.1.18, 2.0.44, http is http and https is https. What I've done in Struts, is to subclass ActionServlet, replace the doGet() and doPost() methods, and in the replaced methods test if HttpServletRequest.isSecure() is true or false, and if false, redirect to an HTTPS URL. This worked with Tomcat 3.2 and the Jk connector to apache, but didn't work with Tomcat 4.1.12 and the Coyote connector (I had to use the Jk connector), but it now works with tomcat 4.1.18 and the Coyote connector (which seems to be able to handle a lot more traffic than the okd Jk connector). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Simultanous access to Ajp13 connector by more than one apache?
Platform: Intel PIII, debian testing/unstable (sarge) Blackdown JDK 1.3.1 (j2sdk 1.3.1.0b-2), tomcat4 4.1.16-1, apache 1.3.26-1.1, apache-ssl 1.3.26+1.48-2 Is it possible to access an Ajp13 connector in tomcat 4.1.x at the same time, by more than one apache web server? The reason I'm asking is that debian package apache without SSL and apache with SSL as separate daemon processes. I'm seeing some strange behaviour right now (sometimes it's possible to connect to the Ajp13 connector on port 8009, sometimes it's not. Sometimes it works, sometimes it doesn't), and I was wondering if this was caused by two separate clients attempting to access the Ajp13 connector simultanously? All info appreciated! Thanx! - Steinar -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
tomcat version numbering (Was: HttpServletRequest.isSecure()fails...)
Steinar Bang [EMAIL PROTECTED]: Steinar Bang [EMAIL PROTECTED]: Do the 4.1.13 and 4.1.14 versions you refer to, exist as separate branches in the CVS? Or is 4.1.13 a branch, and 4.1.14-to-be HEAD? Not sure if they are branch tags, but there are tags named TOMCAT_4_1_13 and TOMCAT_4_1_14. If one looks at the distribution directory of tomcat, it is easy to get confused. It contains the directories: v4.0.5/ 09-Oct-2002 07:28- v4.0.6/ 08-Oct-2002 08:27- v4.1.12/02-Oct-2002 03:01- v4.1.15-alpha/ 14-Nov-2002 00:48- Ie. there's a 4.1.12, no 4.1.13, or 4.1.14, but instead a 4.1.15 that is marked alpha. The immediate question is: is this an alpha of a final 4.1.15 release? Or is 4.1.15 an alpha release of the final version of 4.1.x? A bit of googling found me URL:http://www.faqchest.com/prgm/tomcat-l/tmct-02/tmct-0208/tmct-020879/tmct02082620_30399.html And I guess the answer is sort of the first one, and sort of the last one. Ie. if 4.1.15-alpha turns out to be a stable release, the -alpha will be yanked from the version number, and 4.1.15 will become a production release. However, if 4.1.15 isn't found good enough, it will be completely yanked from the distribution directory, and consigned to the scrapheap of history. And then a new version 4.1.16-alpha will be announced. I'm still a little confused, but I guess that whatever 4.1.x with x=14 is finally released, will have a working HttpServletRequest.isSecure() when using the Coyote Ajp1.3 connector. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Is there a tomcat manager API? (tomcat 4.1.12)
I would like to reload our user webapp from our own manager webapp, when properties have been changed in the manager webapp. Is there a .jar file I could include into our own manager webapp, and an API I can access? Or is the proper way to use the HTTP interface, described here? URL:http://jakarta.apache.org/tomcat/tomcat-4.1-doc/manager-howto.html#Supported%20Manager%20Commands I tried looking at the Catalina Javadocs, linked to from the Manager howto page, but that link gave me a 404 not found. Thanx! - Steinar -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Current performance comparisons of PHP vs. JSP anywhere?
I typed the three words php jsp performace to www.google.com, and I got the following relevant matches: URL:http://www.linuxdocs.org/HOWTOs/PHP-HOWTO-13.html URL:http://www.zend.com/zend/art/php-over-java.php Both articles are referring to an eWeek test that showed JSP to be 3,5 times slower than PHP when serving pages from the same hardware. The article containing the test was published in October 2000, which is quite a while ago in JSP terms. Has there been any newer tests that google doesn't know about? The second article has a link to the original article, but it doesn't work. I was hoping I could go there and perhaps find links to related articles. Thanx! - Steinar -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Re: HttpServletRequest.isSecure() fails with Coyote AJP 1.3Connector
Bill Barker [EMAIL PROTECTED]: On Fri, 1 Nov 2002, Steinar Bang wrote: If I use the old AJP 1.3 connector, I can use the HttpServletRequest.isSecure() function to determine if the client used an HTTPS connection to the apache server. With the Coyote AJP 1.3 connector this information is lost. Ie. HttpServletRequest.isSecure() always returns false, and HttpServletRequest.getScheme() always returns http. I believe that this is a bug, and has been fixed in 4.1.14 (and, even, 4.1.13 if you can run Tomcat without a sandbox). Thanx for the info! As far as I can tell, 4.1.12 is the latest available version of tomcat, even counting nightly builds? Do the 4.1.13 and 4.1.14 versions you refer to, exist as separate branches in the CVS? Or is 4.1.13 a branch, and 4.1.14-to-be HEAD? Thanx! - Steinar -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Avoiding YYYY-MM-DD in log file names (tomcat 4.1.12)
Is it possible to avoid the -MM-DD in the log file names of tomcat 4.1.12? I would prefer to just let linux logrotate handle the rotation of log files. According to URL:http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/logger.html there is no possibility to configure it away, but perhaps someone knows of a simple workaround? Thanx! - Steinar -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Re: HttpServletRequest.isSecure() fails with Coyote AJP 1.3Connector
Steinar Bang [EMAIL PROTECTED]: Do the 4.1.13 and 4.1.14 versions you refer to, exist as separate branches in the CVS? Or is 4.1.13 a branch, and 4.1.14-to-be HEAD? Not sure if they are branch tags, but there are tags named TOMCAT_4_1_13 and TOMCAT_4_1_14. -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
HttpServletRequest.isSecure() fails with Coyote AJP 1.3 Connector
Platform: Intel PIII, RedHat 7.2, apache 1.3.20, ajp1.3 tomcat 4.1.12, BlackDown Java SDK 1.3.1, Struts 1.1-b2 Is there a way to pass the scheme used by the client when talking to the apache server (ie. http or https) through the Coyote AJP 1.3 connector? If I use the old AJP 1.3 connector, I can use the HttpServletRequest.isSecure() function to determine if the client used an HTTPS connection to the apache server. With the Coyote AJP 1.3 connector this information is lost. Ie. HttpServletRequest.isSecure() always returns false, and HttpServletRequest.getScheme() always returns http. The Connector elelement for Coyote have the attributes secure, and scheme, which affects the above values of HttpServletRequest. But these settings are constants. Do I need to set up a separate AJP 1.3 connection on a different port to handle HTTPS requests to apache? If so, how's that done? Thanx! - Steinar -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Re: Profiling with tomcat
Graham King [EMAIL PROTECTED]: I found a combination of -Xrunhprof (see 'java -Xrunhprof:help') and HPjmeter (free tool from HP for visualising the output of hprof. See http://www.hp.com/products1/unix/java/hpjmeter/index.html) Is this program available for free download? I was unable to determine from the web pages whether it was a freely downloadable program, or whether it was a commercial product. -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Re: Profiling with tomcat
Ralph Einfeldt [EMAIL PROTECTED]: From: Steinar Bang [mailto:sb;dod.no] Is this program available for free download? I was unable to determine from the web pages whether it was a freely downloadable program, or whether it was a commercial product. Have a look at http://www.hp.com/products1/unix/java/hpjmeter/downloads/license_hpjmeter_1-5.html I've seen it. But it contradicts with the information that's displayed during download, ie. the 90 day's warranty statement, that looks like it's meant for a commercial product. I kept looking for where they would be asking me for my credit card number. -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Coyote AJP 1.3 connector: apache HTTPS info blocked
Platform: Intel PIII, RedHat 7.2, apache 1.3.20, ajp1.3 tomcat 4.1.12, BlackDown Java SDK 1.3.1, Struts 1.1-b2 Is there a way to pass the scheme used by the client when talking to the apache server (ie. http or https) through the Coyote AJP 1.3 connector? If I use the old AJP 1.3 connector, I can use the HttpServletRequest.isSecure() function to determine if the client used an HTTPS connection to the apache server. With the Coyote AJP 1.3 connector this information is lost. Ie. HttpServletRequest.isSecure() always returns false, and HttpServletRequest.getScheme() always returns http. The Connector elelement for Coyote have the attributes secure, and scheme, which affects the above values of HttpServletRequest. But these settings are constants. Do I need to set up a separate AJP 1.3 connection on a different port to handle HTTPS requests to apache? If so, how's that done? Thanx! - Steinar -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Re: VerifyError when creating Struts action bean
Steinar Bang [EMAIL PROTECTED]:
Platform: Intel PIII, RedHat 7.2, apache 1.3.20, ajp1.3
tomcat 4.1.12, BlackDown Java SDK 1.3.1,
Struts 1.1-b2, xerces-j 1.4.4
When I run with tomcat 3.3 my webapp run as expected, but when I try
it with tomcat 4.1.12, I get a VerifyError when creating one of the
webapp's Action beans. The error output is attached to the end of
this message.
[snip!]
The action definition from struts-config.xml, is:
actionpath=/main
type=no.dod.TPS.corba.stb.WelcomeAction
scope=request
forward name=success path=/stb/main.jsp/
/action
[snip!]
[ERROR] RequestProcessor - -No action instance for path /main could be created
java.lang.VerifyError: (class: no/dod/TPS/corba/stb/WelcomeAction, method: doPerform
signature:
(Lorg/apache/struts/action/ActionMapping;Lorg/apache/struts/action/ActionForm;Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;Lno/dod/T
The problem is releated to the use of org.apache.xerces.parsers.SAXParser
in the Action bean it can't create.
A call to SAXParser.setContentHandler(), can be left in place, but
when I remove the calls to SAXParser.reset() and SAXParser.parse(), (I
have to remove both) the VerifyError problem goes away.
But of course the Action bean isn't very functional.
I thought this might have something to do with colliding versions of
xerces.jar, so I've replaced
pathelement location=${deploy.home}/WEB-INF/lib/xerces.jar/
with
pathelement location=/usr/share/java/xerces.jar/
,removed xerces.jar from the WEB-INF/lib directory of the compiled
webapp, and done a complete rebuild of the webapp, but I still get the
VerifyError.
I belive /usr/share/java/xerces.jar, which is the the version
installed by the xerces-j 1.4.4 RPM, is the version used by tomcat
4.1.12 (is there a way to find out what xerces.jar file it loads?).
Any hints and guesses that might shed some light on this problem, are
appreciated!
Thanx!
- Steinar
--
To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Re: VerifyError when creating Struts action bean
Steinar Bang [EMAIL PROTECTED]:
Platform: Intel PIII, RedHat 7.2, apache 1.3.20, ajp1.3
tomcat 4.1.12, BlackDown Java SDK 1.3.1,
Struts 1.1-b2, xerces-j 1.4.4
When I run with tomcat 3.3 my webapp run as expected, but when I try
it with tomcat 4.1.12, I get a VerifyError when creating one of the
webapp's Action beans.
[snip!]
[ERROR] RequestProcessor - -No action instance for path /main could be created
java.lang.VerifyError: (class: no/dod/TPS/corba/stb/WelcomeAction, method: doPerform
signature:
(Lorg/apache/struts/action/ActionMapping;Lorg/apache/struts/action/ActionForm;Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;Lno/dod/T
When I replaced
pathelement location=${deploy.home}/WEB-INF/lib/xerces.jar/
with
pathelement location=/var/tomcat4/common/endorsed/jaxp_parser_impl.jar/
in the classpath element in the javac task of the ant build file,
the problem went away.
This is replacing (an unknown version of) xerces.jar in our CVS, with
the version 2-something of xerces distributed with tomcat 4.1.12.
--
To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
VerifyError when creating Struts action bean
Platform: Intel PIII, RedHat 7.2, apache 1.3.20, ajp1.3 tomcat 4.1.12, BlackDown Java SDK 1.3.1, Struts 1.1b2 When I run with tomcat 3.3 my webapp run as expected, but when I try it with tomcat 4.1.12, I get a VerifyError when creating one of the webapp's Action beans. The error output is attached to the end of this message. I've searched www.google.com for this problem, and I've found that some people have had problems with custom tags when changing to tomcat4, but I haven't found anyone having problems with actions. I have cleaned away the webapp, rebuilt it, and stopped and started tomcat, to make sure it hadn't cached a broken .class file. The action definition from struts-config.xml, is: actionpath=/main type=no.dod.TPS.corba.stb.WelcomeAction scope=request forward name=success path=/stb/main.jsp/ /action Has anyone seen a similar problem? Does anyone know what to do to fix it? Thanx! - Steinar [INFO] RequestProcessor - -Processing a 'GET' for path '/main' java.lang.VerifyError: (class: no/dod/TPS/corba/stb/WelcomeAction, method: doPerform signature: (Lorg/apache/struts/action/ActionMapping;Lorg/apache/struts/action/ActionForm;Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;Lno/dod/T at java.lang.Class.newInstance0(Native Method) at java.lang.Class.newInstance(Class.java:237) at org.apache.struts.util.RequestUtils.applicationInstance(RequestUtils.java:219) at org.apache.struts.action.RequestProcessor.processActionCreate(RequestProcessor.java:314) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:258) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1292) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at org.apache.catalina.core.ApplicationDispatcher.invoke(Unknown Source) at org.apache.catalina.core.ApplicationDispatcher.doForward(Unknown Source) at org.apache.catalina.core.ApplicationDispatcher.forward(Unknown Source) at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1019) at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:422) at org.apache.struts.action.RequestProcessor.processActionForward(RequestProcessor.java:389) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:269) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1292) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Unknown Source) at org.apache.catalina.core.ApplicationFilterChain.doFilter(Unknown Source) at org.apache.catalina.core.StandardWrapperValve.invoke(Unknown Source) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Unknown Source) at org.apache.catalina.core.StandardPipeline.invoke(Unknown Source) at org.apache.catalina.core.ContainerBase.invoke(Unknown Source) at org.apache.catalina.core.StandardContextValve.invoke(Unknown Source) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Unknown Source) at org.apache.catalina.core.StandardPipeline.invoke(Unknown Source) at org.apache.catalina.core.ContainerBase.invoke(Unknown Source) at org.apache.catalina.core.StandardContext.invoke(Unknown Source) at org.apache.catalina.core.StandardHostValve.invoke(Unknown Source) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Unknown Source) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(Unknown Source) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Unknown Source) at org.apache.catalina.valves.ErrorReportValve.invoke(Unknown Source) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Unknown Source) at org.apache.catalina.core.StandardPipeline.invoke(Unknown Source) at org.apache.catalina.core.ContainerBase.invoke(Unknown Source) at org.apache.catalina.core.StandardEngineValve.invoke(Unknown Source) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Unknown Source) at org.apache.catalina.core.StandardPipeline.invoke(Unknown Source) at org.apache.catalina.core.ContainerBase.invoke(Unknown Source) at
VerifyError when creating action
Platform: Intel PIII, RedHat 7.2, apache 1.3.20, ajp1.3 tomcat 4.1.12, BlackDown Java SDK 1.3.1 When I run with tomcat 3.3 my webapp run as expected, but when I try it with tomcat 4.1.12, I get a VerifyError when creating one of the webapp's Action beans. The error output is attached to the end of this message. I've searched www.google.com for this problem, and I've found that some people have had problems with custom tags when changing to tomcat4, but I haven't found anyone having problems with actions. I have cleaned away the webapp, rebuilt it, and stopped and started tomcat, to make sure it hadn't cached a broken .class file. The action definition from struts-config.xml, is: actionpath=/main type=no.dod.TPS.corba.stb.WelcomeAction scope=request forward name=success path=/stb/main.jsp/ /action Has anyone seen a similar problem? Does anyone know what to do to fix it? Thanx! - Steinar [INFO] RequestProcessor - -Processing a 'GET' for path '/main' java.lang.VerifyError: (class: no/dod/TPS/corba/stb/WelcomeAction, method: doPerform signature: (Lorg/apache/struts/action/ActionMapping;Lorg/apache/struts/action/ActionForm;Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;Lno/dod/T at java.lang.Class.newInstance0(Native Method) at java.lang.Class.newInstance(Class.java:237) at org.apache.struts.util.RequestUtils.applicationInstance(RequestUtils.java:219) at org.apache.struts.action.RequestProcessor.processActionCreate(RequestProcessor.java:314) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:258) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1292) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at org.apache.catalina.core.ApplicationDispatcher.invoke(Unknown Source) at org.apache.catalina.core.ApplicationDispatcher.doForward(Unknown Source) at org.apache.catalina.core.ApplicationDispatcher.forward(Unknown Source) at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1019) at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:422) at org.apache.struts.action.RequestProcessor.processActionForward(RequestProcessor.java:389) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:269) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1292) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Unknown Source) at org.apache.catalina.core.ApplicationFilterChain.doFilter(Unknown Source) at org.apache.catalina.core.StandardWrapperValve.invoke(Unknown Source) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Unknown Source) at org.apache.catalina.core.StandardPipeline.invoke(Unknown Source) at org.apache.catalina.core.ContainerBase.invoke(Unknown Source) at org.apache.catalina.core.StandardContextValve.invoke(Unknown Source) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Unknown Source) at org.apache.catalina.core.StandardPipeline.invoke(Unknown Source) at org.apache.catalina.core.ContainerBase.invoke(Unknown Source) at org.apache.catalina.core.StandardContext.invoke(Unknown Source) at org.apache.catalina.core.StandardHostValve.invoke(Unknown Source) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Unknown Source) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(Unknown Source) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Unknown Source) at org.apache.catalina.valves.ErrorReportValve.invoke(Unknown Source) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Unknown Source) at org.apache.catalina.core.StandardPipeline.invoke(Unknown Source) at org.apache.catalina.core.ContainerBase.invoke(Unknown Source) at org.apache.catalina.core.StandardEngineValve.invoke(Unknown Source) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Unknown Source) at org.apache.catalina.core.StandardPipeline.invoke(Unknown Source) at org.apache.catalina.core.ContainerBase.invoke(Unknown Source) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:458)
tomcat4, which ajp1.3 connector to use? (Coyote? plain?)
Platform: Intel PIII, RedHat 7.2, apache 1.3.20, ajp1.3 tomcat 4.1.12, BlackDown Java SDK 1.3.1 The tomcat4 server.xml file came with the Coyote/JK2 Ajp 1.3 Connector enabled and the normal(?) Ajp 1.3 connector disabled (the class is org.apache.ajp.tomcat4.Ajp13Connector). I had to disable the Coyote connector and enable the normal connector to be able to make things work. Is this to be expected? Or would it be preferrable if I would be able to make tomcat/apache use the Coyote connector? Thanx! - Steinar -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Re: Connect Java Profiler to Tomcat
Zhenxin wang [EMAIL PROTECTED]:
I used OptimizeIt, which has special script for Tomcat 4. Follow the
instructions from OptimizeIt to modify the script to suit your
environment, it should be easy to gt it working.
I've aquired a test license from Borland, but haven't been able to get
it working yet.
Platform: Intel PIII, RedHat 7.2, Blackdown JDK 1.3.1_01-fcs, tomcat 3.3
Both the JDK and tomcat were installed from RPMs.
What I've done is to:
cd /var/tomcat/
mkdir bin
cd bin
ln -s /usr/bin/tomcat tomcat.sh
and then run the wizard in Tools/Application server integration.
The wizard created the files
/var/tomcat/bin/oi_filter.oif
/var/tomcat/bin/tomcat3_OI.sh
I've then stopped the running daemon with
/etc/init.d/tomcat
and started the script /var/tomcat/bin/tomcat3_OI.sh.
The script outputs some text and then terminates. After the
script has terminated no tomcat process is running. The
output by the script, is:
# /var/tomcat/bin/tomcat3_OI.sh
/usr/java/jdk1.3.1_01/bin/java
-Xbootclasspath/a:/usr/local/OptimizeitSuiteDemo/lib/oibcp.jar -classpath
/var/tomcat/lib/tomcat.jar:/usr/local/OptimizeitSuiteDemo/lib/optit.jar:/usr/java/jdk1.3.1_01/lib/tools.jar:
-Dtomcat.home=/var/tomcat -DGCOPSIZE=5 intuitive.audit.GenericAudit
org.apache.tomcat.startup.Main start
OptimizeIt Profiler 4.11 build 449 Audit System.
(c) 1997, 1998, 1999, 2000, 2001 Borland.
Port is 1470
Using 5MB for GC operation pool
OptimizeIt generic Audit System. [Hotspot runtime detected]
EmbededTomcat: Init time 1066
EmbededTomcat: Startup time 0
#
The generated tomcat3_OI.sh script is appended to the end of this message.
All hints, tips, and guesses appreciated!
Thanx
- Steinar
-wizard generated tomcat start script tomcat3_OI.sh--
#!/bin/sh
# This script allows to start Jakarta Tomcat 3.1, 3.2 and 3.3 with Optimizeit #
# tools. It should be completed before use.#
# Use this script to start Tomcat with the Optimizeit Audit System selected#
# with the Audit System Selector (OptIt_Dir/oiselector program). #
# Refer to the tutorial for Tomcat 3 for more information. #
# (tutorials are located under OptIt_Dir/tutorials) #
# This entry contains the directory where you installed Tomcat
# (Ex: /home/jay/jakarta-tomcat-3.3)
TOMCAT_HOME=/var/tomcat
#This entry contains the path to the OptimizeIt directory
# (Ex: /home/ted/OptimizeitSuite4.1)
OPTIT_HOME=/usr/local/OptimizeitSuiteDemo
# This entry contains the path to the directory of the vm that you want to use
# (Ex: /home/ted/jdk1.3.1)
JAVA_HOME=/usr/java/jdk1.3.1_01
# Enter any required extra java classpath at this entry
JAVA_CLASSPATH=
# Add any extra java arguments at this entry
# (such as -D java properties used by 3rd party products)
JAVA_ARGS=
# Increase the GCOP value if you get some GCOP buffer too small errors
# with the Profiler (size is in Mb)
GCOPSIZE=5
# ** You should not have to modify anything below this line **
# -
if [ ! -d $JAVA_HOME ] ; then
echo The JAVA_HOME specified $JAVA_HOME does not exists.
echo Make sure to specify a correct JAVA_HOME in the tomcat3_OI.sh script.
exit
fi
if [ -f $JAVA_HOME/bin/java ]
then
JAVA=$JAVA_HOME/bin/java
elif [ -f $JAVA_HOME/bin/jre ]
then
JAVA=$JAVA_HOME/bin/jre
else
echo No java or jre found under the directory $JAVA_HOME
echo Make sure to specify a correct JAVA_HOME in the tomcat3_OI.sh script.
exit
fi
if [ ! -f $OPTIT_HOME/lib/optit.jar ] ; then
echo Cannot find the OptimizeIt library optit.jar under the directory $OPTIT_HOME
echo Make sure to specify a correct OPTIT_HOME in the tomcat3_OI.sh script.
exit
fi
LD_LIBRARY_PATH=${LD_LIBRARY_PATH:-.}:${OPTIT_HOME}/lib
export LD_LIBRARY_PATH
OI_PATH=$PATH
export OI_PATH
if [ -z $AUDIT ] ; then
AUDIT=`$OPTIT_HOME/runtime/bin/jre -classpath
$OPTIT_HOME/runtime/lib/rt.jar:$OPTIT_HOME/lib/optit.jar
intuitive.optit.fileop.JavaTester $JAVA 2 /dev/null`
fi
# Always use native threads
JAVATHREADS=-native -DOPTITTHR=native
case $AUDIT in
11) COMMAND=$JAVA $JAVATHREADS -noclassgc -Djava.compiler=NONE -DAUDIT=11
JAVACP=$JAVA_HOME/lib/classes.zip:$OPTIT_HOME/lib/optit.jar;;
118pr) COMMAND=$JAVA $JAVATHREADS -noclassgc -Djava.compiler=NONE -DAUDIT=118pr
JAVACP=$JAVA_HOME/lib/classes.zip:$OPTIT_HOME/lib/optit.jar;;
12) COMMAND=$JAVA $JAVATHREADS -Xrunoii -Xnoclassgc -Djava.compiler=NONE -DAUDIT=12
JAVACP=$OPTIT_HOME/lib/optit.jar:$JAVA_HOME/lib/tools.jar ;;
JNI) COMMAND=$JAVA -Xrunoii -DAUDIT=jni
JAVACP=$OPTIT_HOME/lib/optit.jar:$JAVA_HOME/lib/tools.jar ;;
*) echo Virtual machine not recognized, using default settings...
COMMAND=$JAVA -Xrunoii -DAUDIT=jni
Re: Connect Java Profiler to Tomcat
Zhenxin Wang [EMAIL PROTECTED]: I wonder anyone has done hooking up a Java Profiler such as OptimizeIt or JProbe. I've asked the same question on different newsgroups, but got no responses. The Tomcat startup script is a bit hard to digest. How to start Tomcat (4.0.4) by running java . from cmd line? If you get it working, could you perhaps post your experiences here? :-) Thanx! - Steinar -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: ajp14.service() error sending, retry on a new endpoint ajp13
Adrian [EMAIL PROTECTED]: What does your httpd.conf look like ? Attached. Modified by me, based on my apache 1.3/tomcat 3.x config. Actually it's called httpd2.conf. What about your server.xml? Attached. As installed by the tomcat 4.0.3 RPM, ie. unchanged by me. Did you do any configuration, or just startup both Tomcat and Apache? I have done some configuration to get in all the things done in the httpd.conf we use with apache 1.3/tomcat 3.x, and make tomcat run with Blackdown Java SDK 1.3.1. I always test on the examples first then remove the 8080 to confirm connection. Connection to port 8180 works. Make sure to start Tomcat first, check server.xml to make sure you have a ajp14 connector running. This may be it. There is no ajp14 connector defined in server.xml. I wondered about those ajp14 error messages in the error_log. I have been trying to use ajp13 in the config files. Show me what you added to httpd.conf , or if you used an include file what does it look like. mod_jk2.conf which is included into httpd2.conf is attached. This one has also been modified by me, from the one distributed on the RPM. Both for bugfixes (path name corrections), and for adding my own stuff. Thanx! - Steinar (sorry about the way the attachments look. I tried making them text/plain parts in a multipart/mixed message, which the way Gnus make them, are both human readable and machine readable, but ezlm bounced that message) -httpd2.conf---Apache 2.x config file for use with tomcat4-- # # Based upon the NCSA server configuration files originally by Rob McCool. # # This is the main Apache server configuration file. It contains the # configuration directives that give the server its instructions. # See URL:http://httpd.apache.org/docs-2.0/ for detailed information about # the directives. # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # The configuration directives are grouped into three basic sections: # 1. Directives that control the operation of the Apache server process as a # whole (the 'global environment'). # 2. Directives that define the parameters of the 'main' or 'default' server, # which responds to requests that aren't handled by a virtual host. # These directives also provide default values for the settings # of all virtual hosts. # 3. Settings for virtual hosts, which allow Web requests to be sent to # different IP addresses or hostnames and have them handled by the # same Apache server process. # # Configuration and logfile names: If the filenames you specify for many # of the server's control files begin with / (or drive:/ for Win32), the # server will use that explicit path. If the filenames do *not* begin # with /, the value of ServerRoot is prepended -- so /var/log/httpd2/foo.log # with ServerRoot set to /etc/httpd2 will be interpreted by the # server as /etc/httpd2//var/log/httpd2/foo.log. # ### Section 1: Global Environment # # The directives in this section affect the overall operation of Apache, # such as the number of concurrent requests it can handle or where it # can find its configuration files. # # # ServerRoot: The top of the directory tree under which the server's # configuration, error, and log files are kept. # # NOTE! If you intend to place this on an NFS (or otherwise network) # mounted filesystem then please read the LockFile documentation # (available at URL:http://httpd.apache.org/docs-2.0/mod/core.html#lockfile); # you will save yourself a lot of trouble. # # Do NOT add a slash at the end of the directory path. # ServerRoot /etc/httpd2 # # The accept serialization lock file MUST BE STORED ON A LOCAL DISK. # IfModule !mpm_winnt.c IfModule !mpm_netware.c #LockFile /var/log/httpd2/accept.lock /IfModule /IfModule # # ScoreBoardFile: File used to store internal server process information. # If unspecified (the default), the scoreboard will be stored in an # anonymous shared memory segment, and will be unavailable to third-party # applications. # If specified, ensure that no two invocations of Apache share the same # scoreboard file. The scoreboard file MUST BE STORED ON A LOCAL DISK. # IfModule !mpm_netware.c IfModule !perchild.c #ScoreBoardFile /var/log/httpd2/apache_runtime_status /IfModule /IfModule # # PidFile: The file in which the server should record its process # identification number when it starts. # IfModule !mpm_netware.c PidFile /var/run/httpd2.pid /IfModule # # Timeout: The number of seconds before receives and sends time out. # Timeout 300 # # KeepAlive: Whether or not to allow persistent connections (more than # one request per connection). Set to Off to deactivate. # KeepAlive On # # MaxKeepAliveRequests: The maximum number of requests to allow # during a persistent connection. Set to 0 to allow an unlimited amount. # We recommend you leave this
Re: Problems using a tomcat 3.3 .war file with tomcat 4.0.3
Steinar Bang [EMAIL PROTECTED]: Steinar Bang [EMAIL PROTECTED]: Perhaps my JkMount statements aren't included into httpd2.conf. Hmm... I don't think that's it, either... I get the following message, when I'm starting apache: # /etc/init.d/httpd2 start Starting httpd2: XXX Create dir config (null) 0x80da5d0 set2.mount /*.jsp ajp13 [snip!] set2.mount /tps ajp13 set2.mount /tps/* ajp13 The two latest lines seems to come from JkMount calls to the part of URL space under /tps/, which is where I get 404 responses. I tried accessing the URL http://myhost/tps/ directly from tomcat, instead of via apache. So I opened http://myhost:8180/tps/ which opens the file http://myhost:8180/tps/index.html which redirects to the Struts URL http://myhost:8180/tps/TPSHome.do which results in the following response (no classes of mine in there, as far as I can see): message Internal Server Error description The server encountered an internal error (Internal Server Error) that prevented it from fulfilling this request. exception javax.servlet.ServletException: Servlet.init() for servlet action threw exception at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:935) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:653) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1012) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1107) at java.lang.Thread.run(Thread.java:484) root cause java.lang.NoClassDefFoundError: org/w3c/dom/range/Range at org.apache.xerces.validators.dtd.DTDGrammar.callStartDTD(DTDGrammar.java:190) at org.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner.java:1073) at org.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDecl(XMLDocumentScanner.java:2177) at org.apache.xerces.framework.XMLDocumentScanner.access$0(XMLDocumentScanner.java:2133) at org.apache.xerces.framework.XMLDocumentScanner$PrologDispatcher.dispatch(XMLDocumentScanner.java:882) at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:380) at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:861) at javax.xml.parsers.SAXParser.parse(SAXParser.java) at javax.xml.parsers.SAXParser.parse(SAXParser.java) at org.apache.struts.digester.Digester.parse(Digester.java:755) at org.apache.struts.action.ActionServlet.initMapping(ActionServlet.java:1331) at org.apache.struts.action.ActionServlet.init(ActionServlet.java:465) at javax.servlet.GenericServlet.init(GenericServlet.java) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:916) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:653) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke
Re: Problems using a tomcat 3.3 .war file with tomcat 4.0.3
Platform: Intel PIII, RedHat 7.2, apache 2.0.35 from the RPM in URL http://ftp.falsehope.com/home/gomez/apache2/, tomcat 4.0.3, and mod_jk2 from RPMs in http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.3/rpms/ [trying to use a .war created for tomcat 3.3, with tomcat 4.0.3] Steinar Bang [EMAIL PROTECTED]: [snip!] root cause java.lang.NoClassDefFoundError: org/w3c/dom/range/Range at org.apache.xerces.validators.dtd.DTDGrammar.callStartDTD(DTDGrammar.java:190) [snip!] It looks like Xerces is missing some stuff when creating a DOM tree from SAX calls. As far as I can see, the class is available in the .jar file installed from the xerces RPM: # unzip -l /usr/share/java/xerces.jar | grep Range 7120 02-13-02 00:32 org/apache/xerces/utils/regex/RangeToken.class 514 02-13-02 00:32 org/apache/xerces/utils/regex/Op$RangeOp.class 499 02-13-02 00:32 org/apache/xerces/utils/StringPool$CharArrayRange.class 11745 02-13-02 00:33 org/apache/xerces/dom/RangeImpl.class 258 02-13-02 00:33 org/apache/xerces/dom/RangeExceptionImpl.class 404 02-13-02 00:32 org/w3c/dom/ranges/RangeException.class 179 02-13-02 00:32 org/w3c/dom/ranges/DocumentRange.class 1408 02-13-02 00:32 org/w3c/dom/ranges/Range.class Is tomcat4 running a different Xerces from a different .jar perhaps? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: undefined symbol apt_pool_create when loading mod_jk2.so
Steinar Bang [EMAIL PROTECTED]: Platform: Intel PIII, RedHat 7.2, apache 2.0.35 from the RPM in URL http://ftp.falsehope.com/home/gomez/apache2/, mod_jk2 from the RPM in http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.3/rpms/ When I try starting apache, I get the following error message: # /etc/init.d/httpd2 start Starting httpd2: Syntax error on line 256 of /etc/httpd2/conf/httpd2.conf: Cannot load /etc/httpd2/modules/mod_jk2.so into server: /etc/httpd2/modules/mod_jk2.so: undefined symbol: apr_pool_create [FAILED] I haven't found a source RPM for mod_jk2, so I can't rebuild with a link to the appropriate .so defining this symbol. The source RPM for mod_jk2 as well as the other connectors, is http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.3/rpms/tomcat-connectors-1.0-1.4.0.2.src.rpm I installed it with rpm -i, opened the SPEC file in emacs, and changed the release number, and tried rpm -ba on the SPEC file. Then I installed all the RPMs the build complained was missing, and did rpm -ba once more. When I upgraded with rpm -U there was problems with the %preun section of the original mod_jk2 rpm. But the result seems to work anyway. I do get some strange output when starting apache, though: # /etc/init.d/httpd2 start Starting httpd2: XXX Create dir config (null) 0x80da5d0 set2.mount /*.jsp ajp13 set2.mount /servlet/* ajp13 set2.mount /examples/servlet/* ajp13 set2.mount /examples/*.jsp ajp13 set2.mount /admin/servlet/* ajp13 set2.mount /admin/*.jsp ajp13 set2.mount /test/servlet/* ajp13 set2.mount /test/*.jsp ajp13 set2.mount /tps ajp13 set2.mount /tps/* ajp13 [ OK ] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Problems using a tomcat 3.3 .war file with tomcat 4.0.3
Platform: Intel PIII, RedHat 7.2, apache 2.0.35 from the RPM in URL http://ftp.falsehope.com/home/gomez/apache2/, tomcat 4.0.3, and mod_jk2 from RPMs in http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.3/rpms/ I am trying to use a .war created for use with tomcat 3.3, with tomcat 4.0.3. Is this supposed to work? Searches on the web hasn't found me any place that talks about this. What I have done, is to drop the .war file in /var/tomcat4/webapps/. When starting, tomcat4 writes the following to the /var/tomcat4/logs/catalina.log file: Starting service Tomcat-Standalone Apache Tomcat/4.0.3 PARSE error at line 138 column 12 org.xml.sax.SAXParseException: The content of element type web-app must match (icon?,display-name?,description?,distributable?,context-param*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*). line 138 of the web.xml file of the .war file I'm using contains the /web-app end tag, with the as the final character on the line, in column 10 (ie. there is no column 12 on that line). All ideas, hints, etc. appreciated! Thanx! - Steinar -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Problems using a tomcat 3.3 .war file with tomcat 4.0.3
Steinar Bang [EMAIL PROTECTED]: Platform: Intel PIII, RedHat 7.2, apache 2.0.35 from the RPM in URL http://ftp.falsehope.com/home/gomez/apache2/, tomcat 4.0.3, and mod_jk2 from RPMs in http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.3/rpms/ I am trying to use a .war created for use with tomcat 3.3, with tomcat 4.0.3. Is this supposed to work? Searches on the web hasn't found me any place that talks about this. What I get, when I try to access URLs inside the webapp, is 404 not found. As far as I can tell, I have the appropriate JkMount statements in a file included into httpd2.conf. What I have done, is to drop the .war file in /var/tomcat4/webapps/. When starting, tomcat4 writes the following to the /var/tomcat4/logs/catalina.log file: Starting service Tomcat-Standalone Apache Tomcat/4.0.3 PARSE error at line 138 column 12 org.xml.sax.SAXParseException: The content of element type web-app must match (icon?,display-name?,description?,distributable?,context-param*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*). This was caused by a session-config in the wrong place according to the 2.2 DTD. I moved it so that the web.xml file validated, and the above message went away. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Problems using a tomcat 3.3 .war file with tomcat 4.0.3
Peter Davison [EMAIL PROTECTED]: Sounds like your web.xml file has a problem in it somewhere. Yep, it did. Sometimes the messages you get from the parser don't necessarily point you to the actual problem (much like compilers I guess). Can you post the contents of your web.xml so that we can have a look? I found the problem with the web.xml file. A session-config was in the wrong place according to the DTD. But this was masking the real problem, which is that I get 404 not found on the webapp URLs. Perhaps my JkMount statements aren't included into httpd2.conf. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Problems using a tomcat 3.3 .war file with tomcat 4.0.3
Steinar Bang [EMAIL PROTECTED]: But this was masking the real problem, which is that I get 404 not found on the webapp URLs. Perhaps my JkMount statements aren't included into httpd2.conf. Hmm... I don't think that's it, either... I get the following message, when I'm starting apache: # /etc/init.d/httpd2 start Starting httpd2: XXX Create dir config (null) 0x80da5d0 set2.mount /*.jsp ajp13 set2.mount /servlet/* ajp13 set2.mount /examples/servlet/* ajp13 set2.mount /examples/*.jsp ajp13 set2.mount /admin/servlet/* ajp13 set2.mount /admin/*.jsp ajp13 set2.mount /test/servlet/* ajp13 set2.mount /test/*.jsp ajp13 set2.mount /tps ajp13 set2.mount /tps/* ajp13 [ OK ] The two latest lines seems to come from JkMount calls to the part of URL space under /tps/, which is where I get 404 responses. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
undefined symbol apt_pool_create when loading mod_jk2.so
Platform: Intel PIII, RedHat 7.2, apache 2.0.35 from the RPM in URL http://ftp.falsehope.com/home/gomez/apache2/, mod_jk2 from the RPM in http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.3/rpms/ When I try starting apache, I get the following error message: # /etc/init.d/httpd2 start Starting httpd2: Syntax error on line 256 of /etc/httpd2/conf/httpd2.conf: Cannot load /etc/httpd2/modules/mod_jk2.so into server: /etc/httpd2/modules/mod_jk2.so: undefined symbol: apr_pool_create [FAILED] I haven't found a source RPM for mod_jk2, so I can't rebuild with a link to the appropriate .so defining this symbol. Does anyone know of a quick workaround? Thanx! - Steinar -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
