Problem with Tomcat 4.1.27, Xerces 2.5 and IBM JVM 1.4.0
We have just upgraded to the Xerces 2.5. We use Tomcat 4.1.27 as our servlet engine. The Xerces code is working in our Microsoft and Linux environment using the Sun 1.4.2 JDK however when we try to use this version of Xerces in our AIX environment using JDK 1.4.0 we receive the following root cause exception below in the local host log and Tomcat never loads our application. Any help in diagnosing this problem will be greatly appreciated. Tim - Root Cause - java.lang.VerifyError: (class: org/apache/xerces/parsers/IntegratedParserConfiguration, method: configurePipeline signature: ()V) Incompatible type for getting or setting field at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:1641) at java.lang.Class.getConstructor0(Class.java:1813) at java.lang.Class.newInstance0(Class.java:304) at java.lang.Class.newInstance(Class.java:283) at org.apache.xerces.util.ObjectFactory.newInstance(ObjectFactory.java:292) at org.apache.xerces.util.ObjectFactory.createObject(ObjectFactory.java:224) at org.apache.xerces.util.ObjectFactory.createObject(ObjectFactory.java:119) at org.apache.xerces.parsers.DOMParser.(DOMParser.java:109) at org.apache.xerces.jaxp.DocumentBuilderImpl.(DocumentBuilderImpl.java:106) at org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(DocumentBuilderFactoryImpl.java:88) at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:656) at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:616) at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:584) at org.apache.log4j.xml.XMLWatchdog.doOnChange(DOMConfigurator.java:815) at org.apache.log4j.helpers.FileWatchdog.checkAndConfigure(FileWatchdog.java:80) at org.apache.log4j.helpers.FileWatchdog.(FileWatchdog.java:49) at org.apache.log4j.xml.XMLWatchdog.(DOMConfigurator.java:807) at org.apache.log4j.xml.DOMConfigurator.configureAndWatch(DOMConfigurator.java:574) at net.casi.platform.core.LoggerFactory.startLoggerFactory(Unknown Source) at net.casi.platform.core.LoggerFactory.configureLoggerFactory(Unknown Source) at net.casi.platform.core.LoggerFactory.getLogger(Unknown Source) at at net.casi.app.Main.(Main.java:44).null(Unknown Source) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:61) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:42) at java.lang.reflect.Constructor.newInstance(Constructor.java(Compiled Code)) at java.lang.Class.newInstance0(Class.java:340) at java.lang.Class.newInstance(Class.java:283) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:903) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:823) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3421) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3609) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:821) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:579) at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:307) at org.apache.catalina.core.StandardHost.install(StandardHost.java:772) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:559) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:401) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:718) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:358) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:166) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1196) at org.apache.catalina.core.StandardHost.start(StandardHost.java:738) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347) at org.apache.catalina.core.StandardService.start(StandardService.java:497) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2190) at org.apache.catalina.startup.Catalina.start(Catalina.java:512) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.ref
RE: ssl problem with Tomcat 4.1.27
Hi I'm using the following connector definition in 4.1.27. Same works well in 4.1.24. port="8443" minProcessors="5" maxProcessors="75" enableLookups="true" acceptCount="100" debug="0" scheme="https" secure="true" useURIValidationHack="false" disableUploadTimeout="true"> keystoreFile="keystore_location_which_is_generated_from_keytool" keystorePass="changeit" clientAuth="false" protocol="TLS" /> Could you provide some leads? thanks, Naresh -Original Message-----From: Yuriy Stul [mailto:[EMAIL PROTECTED]Sent: Wednesday, October 29, 2003 6:28 PMTo: Agarwal, NareshCc: [EMAIL PROTECTED]Subject: RE: ssl problem with Tomcat 4.1.27 No problem with SLL in 4.1.27 version, we use 4.1.27 version and SSL. -Original Message-----From: Agarwal, Naresh [mailto:[EMAIL PROTECTED]Sent: Tuesday, October 28, 2003 5:11 PMTo: [EMAIL PROTECTED]Subject: ssl problem with Tomcat 4.1.27 Hi I successfully configured Tomcat 4.1.24 (using JDK 1.3) for SSL using keystore generated by keytool and used my webapp over HTTPS. However, when I did the same for Tomcat 4.1.27, I could access my webapp over HTTPS only twice, but after this, I'm getting the following error: [ERROR] Http11Protocol - -Error reading request, ignored ging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.SimpleLog does not implement Log>org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.SimpleLog does not implement Log at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:532) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:246) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395) at org.apache.tomcat.util.net.jsse.JSSESupport.(JSSESupport.java:87) at org.apache.tomcat.util.net.jsse.JSSE13Factory.getSSLSupport(JSSE13Factory.java:84) at org.apache.tomcat.util.net.jsse.JSSEImplementation.getSSLSupport(JSSEImplementation.java:118) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:385) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Thread.run(Thread.java:479) Is there any problem with 4.1.27 version? thanks, Naresh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: ssl problem with Tomcat 4.1.27
No problem with SLL in 4.1.27 version, we use 4.1.27 version and SSL. -Original Message- From: Agarwal, Naresh [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 28, 2003 5:11 PM To: [EMAIL PROTECTED] Subject: ssl problem with Tomcat 4.1.27 Hi I successfully configured Tomcat 4.1.24 (using JDK 1.3) for SSL using keystore generated by keytool and used my webapp over HTTPS. However, when I did the same for Tomcat 4.1.27, I could access my webapp over HTTPS only twice, but after this, I'm getting the following error: [ERROR] Http11Protocol - -Error reading request, ignored org.apache.commons.logging.Lo gConfigurationException: org.apache.commons.logging.LogConfigurationException: o rg.apache.commons.logging.LogConfigurationException: Class org.apache.commons.lo gging.impl.SimpleLog does not implement Log at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactory Impl.java:532) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactory Impl.java:272) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactory Impl.java:246) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395) at org.apache.tomcat.util.net.jsse.JSSESupport.(JSSESupport.java:8 7) at org.apache.tomcat.util.net.jsse.JSSE13Factory.getSSLSupport(JSSE13Fac tory.java:84) at org.apache.tomcat.util.net.jsse.JSSEImplementation.getSSLSupport(JSSE Implementation.java:118) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce ssConnection(Http11Protocol.java:385) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java :565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP ool.java:619) at java.lang.Thread.run(Thread.java:479) Is there any problem with 4.1.27 version? thanks, Naresh
reposting : ssl problem with Tomcat 4.1.27
Hi I posted this message yesterday. But it didn't appear in the list, so I'm reposting it. I successfully configured Tomcat 4.1.24 (using JDK 1.3) for SSL using keystore generated by keytool and used my webapp over HTTPS. However, when I did the same for Tomcat 4.1.27, I could access my webapp over HTTPS only twice, but after this, I'm getting the following error: [ERROR] Http11Protocol - -Error reading request, ignored ging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.SimpleLog does not implement Log>org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.SimpleLog does not implement Log at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:532) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:246) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395) at org.apache.tomcat.util.net.jsse.JSSESupport.(JSSESupport.java:87) at org.apache.tomcat.util.net.jsse.JSSE13Factory.getSSLSupport(JSSE13Factory.java:84) at org.apache.tomcat.util.net.jsse.JSSEImplementation.getSSLSupport(JSSEImplementation.java:118) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:385) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Thread.run(Thread.java:479) Is there any problem with 4.1.27 version? thanks, Naresh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ssl problem with Tomcat 4.1.27
Hi I successfully configured Tomcat 4.1.24 (using JDK 1.3) for SSL using keystore generated by keytool and used my webapp over HTTPS. However, when I did the same for Tomcat 4.1.27, I could access my webapp over HTTPS only twice, but after this, I'm getting the following error: [ERROR] Http11Protocol - -Error reading request, ignored ging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.SimpleLog does not implement Log>org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.SimpleLog does not implement Log at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:532) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:246) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395) at org.apache.tomcat.util.net.jsse.JSSESupport.(JSSESupport.java:87) at org.apache.tomcat.util.net.jsse.JSSE13Factory.getSSLSupport(JSSE13Factory.java:84) at org.apache.tomcat.util.net.jsse.JSSEImplementation.getSSLSupport(JSSEImplementation.java:118) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:385) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Thread.run(Thread.java:479) Is there any problem with 4.1.27 version? thanks, Naresh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
problem with tomcat 4.1.27
Hi all, i just downloaded tomcat 4.1.27 for windows and installed it on a windows 2000 professional machine. During the setup everything was just fine but when i try to start tomcat i get the following errors: Using CATALINA_BASE: C:\tomcat 4.1 Using CATALINA_HOME: C:\tomcat 4.1 Using CATALINA_TMPDIR: C:\tomcat 4.1\temp Using JAVA_HOME: C:\j2sdk1.4.1_02 Catalina.start: java.lang.ClassNotFoundException: org.apache.catalina.core.StandardServer java.lang.ClassNotFoundException: org.apache.catalina.core.StandardServer at org.apache.commons.digester.Digester.createSAXException(Digester.java:2540) at org.apache.commons.digester.Digester.createSAXException(Digester.java:2566) at org.apache.commons.digester.Digester.startElement(Digester.java:1276) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unkno wn Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElem entHook(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc her.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1548) at org.apache.catalina.startup.Catalina.start(Catalina.java:449) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) I´ve already set up the catalina variable to c:\tomcat 4.1 which is the installation directory i choose. The JAVA_HOME variable is already set to. Thanks for your help. Kelly. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.516 / Virus Database: 313 - Release Date: 1/9/2003 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with Tomcat 4.1.27 version?
You answer is in the release notes. The invoker servlet has been disabled by default for quite a few versions of Tomcat now because it is a security risk. You can turn it on by uncommenting the appropriate servlet mapping in conf/web.xml Jake At 10:59 PM 8/10/2003 -0700, you wrote: Hello, I shifted from Tomcat 4.0.4 and JDK 1.4 to Tomcat 4.1.27 and JDK 1.4.2 on my Windows 2000 Professional. My application works fine on the older Tomcat but when I run the application on Tomcat 4.1.27 I get an error - HTTP Status 404 - /netapsv1/servlet/EntryServlet type Status report message /netapsv1/servlet/EntryServlet description The requested resource (/netapsv1/servlet/EntryServlet) is not available. The index.jsp runs but can't get my servlet running. The same works fine with Tomcat 4.0.4 and JDK 1.4.2 What could be the problem? All help appreciated. Regards, Satish - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with Tomcat 4.1.27 version?
Thanks. It worked. Satish - Original Message - From: "Jacob Kjome" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Sunday, August 10, 2003 11:32 PM Subject: Re: Problem with Tomcat 4.1.27 version? > > You answer is in the release notes. The invoker servlet has been disabled > by default for quite a few versions of Tomcat now because it is a security > risk. You can turn it on by uncommenting the appropriate servlet mapping > in conf/web.xml > > Jake > > At 10:59 PM 8/10/2003 -0700, you wrote: > >Hello, > > > >I shifted from Tomcat 4.0.4 and JDK 1.4 to Tomcat 4.1.27 and JDK 1.4.2 on > >my Windows 2000 Professional. > > > >My application works fine on the older Tomcat but when I run the > >application on Tomcat 4.1.27 I get an error - > >HTTP Status 404 - /netapsv1/servlet/EntryServlet > > > >--- - > > > >type Status report > > > >message /netapsv1/servlet/EntryServlet > > > >description The requested resource (/netapsv1/servlet/EntryServlet) is not > >available. > > > > > >The index.jsp runs but can't get my servlet running. > > > >The same works fine with Tomcat 4.0.4 and JDK 1.4.2 What could be the problem? > > > >All help appreciated. > > > >Regards, > > > >Satish > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with Tomcat 4.1.27 using Arabic
Hi,
I am running a web application using Jsp/Servlet With Tomcat 4.1.18 as the
Servlet Container.
I have a Jsp Page where in I am displaying a Link for Editing a Particular
Record like as shown below:-
Page1.jsp:-
<%@ page language="java" contentType="text/html; charset=windows-1256"%>
..
where ad object is stored in Session.
ad.getAccountName() stores a Arabic String in Unicode and because of the
meta-tag at top it is rendered in Arabic on JSP page.
Now on Edit.jsp Page When I try to convert that Arabic String back to
Unicode using the code as shown below it gets
converted to Unicode and hence my search inside session variable for that
record succeeds.
Then I display all the details for that Record.
Edit.jsp page:-
<%@ page language="java" contentType="text/html; charset=windows-1256" %>
..
<%
String accName = new String(
request.getParameter("accountName").getBytes("ISO8859_1") , "Cp1256");
.
%>
Now here after this conversion I am getting the Arabic String back in
Unicode.
This sequence of Code works fine with Tomcat 4.0.1,Tomcat 4.1.18 But it does
not work with Tomcat 4.1.24 and Tomcat 4.1.27.
Can Anyone tell me why is this happening and whats the remedy.
I have confirmed the same after printing the binary sequences with my
utility.
Also I noted that on Jsp Page or inside Servlets When I try to get the
Request Encoding using request.getCharacterEncoding(),
it always returns NULL . Why is this happening?
Waiting for Early Reply.
Thanks
Mumtaz
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Problem with Tomcat 4.1.27 version?
Hello, I shifted from Tomcat 4.0.4 and JDK 1.4 to Tomcat 4.1.27 and JDK 1.4.2 on my Windows 2000 Professional. My application works fine on the older Tomcat but when I run the application on Tomcat 4.1.27 I get an error - HTTP Status 404 - /netapsv1/servlet/EntryServlet type Status report message /netapsv1/servlet/EntryServlet description The requested resource (/netapsv1/servlet/EntryServlet) is not available. The index.jsp runs but can't get my servlet running. The same works fine with Tomcat 4.0.4 and JDK 1.4.2 What could be the problem? All help appreciated. Regards, Satish
