You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "James H. H. Lampert" <ja...@touchtonecorp.com.INVALID> on 2021/08/02 23:31:13 UTC
Tomcat 8.5.68 failing on takeoff!
This is beyond my pay grade, I'm afraid. Hopefully somebody here has a
clue what went wrong.
I installed Tomcat 8.5.68 on an AS/400 with Java 8, that had been
running Tomcat 7 for years with no problems.
On launching Tomcat 8, if I try to connect to "manager" (the only
context currently in Webapps), right after:
02-Aug-2021 18:15:11.655 INFO [main]
org.apache.catalina.startup.Catalina.load Initialization processed in
3271 ms
I'm getting
02-Aug-2021 18:15:11.707 WARNING [main]
org.apache.catalina.users.MemoryUserDatabase.open Exception configuring
digester to permit java encoding names in XML files. Only IANA encoding
names will be supported.
org.xml.sax.SAXNotRecognizedException: Feature:
http://apache.org/xml/features/allow-java-encodings
at
org.apache.crimson.parser.XMLReaderImpl.setFeature(XMLReaderImpl.java:213)
at
org.apache.crimson.jaxp.SAXParserImpl.setFeatures(SAXParserImpl.java:143)
at org.apache.crimson.jaxp.SAXParserImpl.<init>(SAXParserImpl.java:126)
at
org.apache.crimson.jaxp.SAXParserFactoryImpl.newSAXParserImpl(SAXParserFactoryImpl.java:113)
at
org.apache.crimson.jaxp.SAXParserFactoryImpl.setFeature(SAXParserFactoryImpl.java:141)
at org.apache.tomcat.util.digester.Digester.setFeature(Digester.java:526)
at
org.apache.catalina.users.MemoryUserDatabase.open(MemoryUserDatabase.java:440)
at
org.apache.catalina.users.MemoryUserDatabaseFactory.getObjectInstance(MemoryUserDatabaseFactory.java:105)
at
org.apache.naming.factory.FactoryBase.getObjectInstance(FactoryBase.java:96)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:332)
at org.apache.naming.NamingContext.lookup(NamingContext.java:847)
at org.apache.naming.NamingContext.lookup(NamingContext.java:157)
at
org.apache.naming.NamingContextBindingsEnumeration.nextElementInternal(NamingContextBindingsEnumeration.java:115)
at
org.apache.naming.NamingContextBindingsEnumeration.next(NamingContextBindingsEnumeration.java:69)
at
org.apache.naming.NamingContextBindingsEnumeration.next(NamingContextBindingsEnumeration.java:32)
at
org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.createMBeans(GlobalResourcesLifecycleListener.java:131)
at
org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.createMBeans(GlobalResourcesLifecycleListener.java:105)
at
org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.lifecycleEvent(GlobalResourcesLifecycleListener.java:80)
at
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
at
org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423)
at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366)
at
org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:763)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.startup.Catalina.start(Catalina.java:688)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:345)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:476)
I can't recall ever seeing anything like this.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: More information, Re: Tomcat 8.5.68 failing on takeoff!
Posted by "James H. H. Lampert" <ja...@touchtonecorp.com.INVALID>.
On 8/6/21 1:40 AM, Mark Thomas wrote:
> Tomcat 7 doesn't have JASPIC support so you'll never see this issue in
> Tomcat 7.
What's a JASPIC?
And as to configuration, Mr. Schultz, my usual procedure is to (after
commenting out the default 8080 unsecured connector) copy and paste the
active secured port 443 connector *directly* from the Tomcat 7
conf/server.xml to the Tomcat 8 conf/server.xml. Ditto for the one user
definition in tomcat-users.xml.
That particular installation has a note to add this clause
<context-param>
<param-name>birtUseSvg</param-name>
<param-value>false</param-value>
</context-param>
to the web.xml of *our webapp,* but nothing server-wide.
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: More information, Re: Tomcat 8.5.68 failing on takeoff!
Posted by Mark Thomas <ma...@apache.org>.
On 06/08/2021 06:15, Christopher Schultz wrote:
> On 8/5/21 18:33, James H. H. Lampert wrote:
<snip/>
>> java.lang.SecurityException: org.xml.sax.SAXNotRecognizedException:
>> Feature: http://apache.org/xml/features/allow-java-encodings
>> org.apache.catalina.authenticator.jaspic.PersistentProviderRegistrations.loadProviders(PersistentProviderRegistrations.java:65)
>>
>> org.apache.catalina.authenticator.jaspic.AuthConfigFactoryImpl.loadPersistentRegistrations(AuthConfigFactoryImpl.java:345)
>>
>> org.apache.catalina.authenticator.jaspic.AuthConfigFactoryImpl.<init>(AuthConfigFactoryImpl.java:68)
>>
>> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>> Method)
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:83)
>>
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57)
>>
>> java.lang.reflect.Constructor.newInstance(Constructor.java:437)
>> javax.security.auth.message.config.AuthConfigFactory$1.run(AuthConfigFactory.java:76)
>>
>> javax.security.auth.message.config.AuthConfigFactory$1.run(AuthConfigFactory.java:67)
>>
>> java.security.AccessController.doPrivileged(AccessController.java:696)
>>
>> javax.security.auth.message.config.AuthConfigFactory.getFactory(AuthConfigFactory.java:66)
>>
<snip/>
> Now THAT looks like a bug. Here is the code around that setFeature() call:
>
> Digester digester = new Digester();
>
> try {
>
> digester.setFeature("http://apache.org/xml/features/allow-java-encodings",
> true);
> digester.setValidating(true);
> digester.setNamespaceAware(true);
> } catch (Exception e) {
> throw new SecurityException(e);
> }
>
> That digester.setFeature() call should be in its own try/catch block
> which issues a warning if a SAXException is thrown.
+1
>> And to reiterate, the very same JVM has no difficulty at all running
>> Tomcat 7.0.93.
>
> Something seems odd about that. There must be soe configuration
> difference between your 7.0.x environment and the 8.5.x environment you
> are testing.
Tomcat 7 doesn't have JASPIC support so you'll never see this issue in
Tomcat 7.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: More information, Re: Tomcat 8.5.68 failing on takeoff!
Posted by Christopher Schultz <ch...@christopherschultz.net>.
James,
On 8/5/21 18:33, James H. H. Lampert wrote:
> I finally had a chance to switch the customer back to the failing Tomcat
> 8.5.68, and this is what the browser error page shows (with a 500 error):
>
>
> Type Exception Report
>
> Message AuthConfigFactory error:
> java.lang.reflect.InvocationTargetException
>
> Description The server encountered an unexpected condition that
> prevented it from fulfilling the request.
>
> Exception
>
> java.lang.SecurityException: AuthConfigFactory error:
> java.lang.reflect.InvocationTargetException
> javax.security.auth.message.config.AuthConfigFactory.getFactory(AuthConfigFactory.java:85)
> org.apache.catalina.authenticator.AuthenticatorBase.findJaspicProvider(AuthenticatorBase.java:1421)
> org.apache.catalina.authenticator.AuthenticatorBase.getJaspicProvider(AuthenticatorBase.java:1411)
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:535)
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)
> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:698)
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:364)
> org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:624)
> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:831)
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1651)
> org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> java.lang.Thread.run(Thread.java:811)
> Root Cause
>
> java.lang.reflect.InvocationTargetException
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:83)
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57)
> java.lang.reflect.Constructor.newInstance(Constructor.java:437)
> javax.security.auth.message.config.AuthConfigFactory$1.run(AuthConfigFactory.java:76)
> javax.security.auth.message.config.AuthConfigFactory$1.run(AuthConfigFactory.java:67)
> java.security.AccessController.doPrivileged(AccessController.java:696)
> javax.security.auth.message.config.AuthConfigFactory.getFactory(AuthConfigFactory.java:66)
> org.apache.catalina.authenticator.AuthenticatorBase.findJaspicProvider(AuthenticatorBase.java:1421)
> org.apache.catalina.authenticator.AuthenticatorBase.getJaspicProvider(AuthenticatorBase.java:1411)
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:535)
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)
> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:698)
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:364)
> org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:624)
> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:831)
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1651)
> org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> java.lang.Thread.run(Thread.java:811)
> Root Cause
>
> java.lang.SecurityException: org.xml.sax.SAXNotRecognizedException:
> Feature: http://apache.org/xml/features/allow-java-encodings
> org.apache.catalina.authenticator.jaspic.PersistentProviderRegistrations.loadProviders(PersistentProviderRegistrations.java:65)
> org.apache.catalina.authenticator.jaspic.AuthConfigFactoryImpl.loadPersistentRegistrations(AuthConfigFactoryImpl.java:345)
> org.apache.catalina.authenticator.jaspic.AuthConfigFactoryImpl.<init>(AuthConfigFactoryImpl.java:68)
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:83)
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57)
> java.lang.reflect.Constructor.newInstance(Constructor.java:437)
> javax.security.auth.message.config.AuthConfigFactory$1.run(AuthConfigFactory.java:76)
> javax.security.auth.message.config.AuthConfigFactory$1.run(AuthConfigFactory.java:67)
> java.security.AccessController.doPrivileged(AccessController.java:696)
> javax.security.auth.message.config.AuthConfigFactory.getFactory(AuthConfigFactory.java:66)
> org.apache.catalina.authenticator.AuthenticatorBase.findJaspicProvider(AuthenticatorBase.java:1421)
> org.apache.catalina.authenticator.AuthenticatorBase.getJaspicProvider(AuthenticatorBase.java:1411)
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:535)
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)
> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:698)
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:364)
> org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:624)
> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:831)
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1651)
> org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> java.lang.Thread.run(Thread.java:811)
> Root Cause
>
> org.xml.sax.SAXNotRecognizedException: Feature:
> http://apache.org/xml/features/allow-java-encodings
> org.apache.crimson.parser.XMLReaderImpl.setFeature(XMLReaderImpl.java:213)
> org.apache.crimson.jaxp.SAXParserImpl.setFeatures(SAXParserImpl.java:143)
> org.apache.crimson.jaxp.SAXParserImpl.<init>(SAXParserImpl.java:126)
> org.apache.crimson.jaxp.SAXParserFactoryImpl.newSAXParserImpl(SAXParserFactoryImpl.java:113)
> org.apache.crimson.jaxp.SAXParserFactoryImpl.setFeature(SAXParserFactoryImpl.java:141)
> org.apache.tomcat.util.digester.Digester.setFeature(Digester.java:526)
> org.apache.catalina.authenticator.jaspic.PersistentProviderRegistrations.loadProviders(PersistentProviderRegistrations.java:61)
> org.apache.catalina.authenticator.jaspic.AuthConfigFactoryImpl.loadPersistentRegistrations(AuthConfigFactoryImpl.java:345)
> org.apache.catalina.authenticator.jaspic.AuthConfigFactoryImpl.<init>(AuthConfigFactoryImpl.java:68)
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:83)
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57)
> java.lang.reflect.Constructor.newInstance(Constructor.java:437)
> javax.security.auth.message.config.AuthConfigFactory$1.run(AuthConfigFactory.java:76)
> javax.security.auth.message.config.AuthConfigFactory$1.run(AuthConfigFactory.java:67)
> java.security.AccessController.doPrivileged(AccessController.java:696)
> javax.security.auth.message.config.AuthConfigFactory.getFactory(AuthConfigFactory.java:66)
> org.apache.catalina.authenticator.AuthenticatorBase.findJaspicProvider(AuthenticatorBase.java:1421)
> org.apache.catalina.authenticator.AuthenticatorBase.getJaspicProvider(AuthenticatorBase.java:1411)
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:535)
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)
> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:698)
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:364)
> org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:624)
> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:831)
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1651)
> org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> java.lang.Thread.run(Thread.java:811)
> Note The full stack trace of the root cause is available in the server
> logs.
Now THAT looks like a bug. Here is the code around that setFeature() call:
Digester digester = new Digester();
try {
digester.setFeature("http://apache.org/xml/features/allow-java-encodings",
true);
digester.setValidating(true);
digester.setNamespaceAware(true);
} catch (Exception e) {
throw new SecurityException(e);
}
That digester.setFeature() call should be in its own try/catch block
which issues a warning if a SAXException is thrown.
> I will note that the *second* SAXNotRecognizedException stack trace
> starts out exactly like the one in catalina.out, but diverges after
> Digester.java:526. The first three stacktraces on the error page look
> completely different.
Yep: the other one you showed was caught and logged, but otherwise ignored.
> The first stacktrace on the error page looks similar to one in
> localhost.2021-08-05.log, timestamped when I attempted to access manager:
>
> 05-Aug-2021 17:05:52.697 SEVERE [https-jsse-nio-443-exec-10]
> org.apache.catalina.core.StandardHostValve.invoke Exception Processing
> /manager/
> java.lang.SecurityException: AuthConfigFactory error:
> java.lang.reflect.InvocationTargetException
> at
> javax.security.auth.message.config.AuthConfigFactory.getFactory(AuthConfigFactory.java:85)
>
> . . .
>
> localhost_access_log.2021-08-05.txt shows (IP address redacted):
> [05/Aug/2021:17:05:52 -0500] "GET /manager HTTP/1.1" 302 -
> [05/Aug/2021:17:05:52 -0500] "GET /manager/ HTTP/1.1" 500 9663
>
> and the manager log shows nothing at all.
>
> And to reiterate, the very same JVM has no difficulty at all running
> Tomcat 7.0.93.
Something seems odd about that. There must be soe configuration
difference between your 7.0.x environment and the 8.5.x environment you
are testing. Somehow, the Crimson XML library is not being used by
Tomcat in your 7.0.x environment. Do you know if you have customized
your conf/catalina.properties or have some non-mundane CATALINA_OPTS
being set in your 7.0.x and.or 8.5.x environments?
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: More information, Re: Tomcat 8.5.68 failing on takeoff!
Posted by Pete Helgren <pe...@valadd.com>.
I don't have an AS/400 any longer but I do I have a 9009 running IBM i.
If you use iACS and go to the IFS menu option, you can filter by a file
name. Are you looking for a class file within a jar or just the jar itself?
Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
AWS Certified Cloud Practitioner
Microsoft Certified: Azure Fundamentals
Twitter - Sys_i_Geek IBM_i_Geek
On 8/6/2021 11:49 AM, James H. H. Lampert wrote:
> Searching JAR files for "crimson" would likely be an exercise in
> futility on an AS/400.
>
> --
> JHHL
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: More information, Re: Tomcat 8.5.68 failing on takeoff!
Posted by Jo...@wellsfargo.com.INVALID.
> -----Original Message-----
> From: James H. H. Lampert <ja...@touchtonecorp.com.INVALID>
> Sent: Friday, August 06, 2021 11:49 AM
> To: Tomcat Users List <us...@tomcat.apache.org>
> Subject: Re: More information, Re: Tomcat 8.5.68 failing on takeoff!
>
> Searching JAR files for "crimson" would likely be an exercise in futility on an
> AS/400.
>
> --
> JHHL
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
I think it's likely to have "crimson" in the file name.
https://search.maven.org/artifact/crimson/crimson/1.1.3/jar
It's ancient, BTW.
Re: More information, Re: Tomcat 8.5.68 failing on takeoff!
Posted by "James H. H. Lampert" <ja...@touchtonecorp.com.INVALID>.
Searching JAR files for "crimson" would likely be an exercise in
futility on an AS/400.
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: More information, Re: Tomcat 8.5.68 failing on takeoff!
Posted by Rob Sargent <rs...@xmission.com>.
> On Aug 6, 2021, at 10:17 AM, Konstantin Kolinko <kn...@gmail.com> wrote:
>
> пт, 6 авг. 2021 г. в 01:33, James H. H. Lampert
> <ja...@touchtonecorp.com.invalid>:
>> org.xml.sax.SAXNotRecognizedException: Feature:
>> http://apache.org/xml/features/allow-java-encodings
>> org.apache.crimson.parser.XMLReaderImpl.setFeature(XMLReaderImpl.java:213)
>> org.apache.crimson.jaxp.SAXParserImpl.setFeatures(SAXParserImpl.java:143)
>> org.apache.crimson.jaxp.SAXParserImpl.<init>(SAXParserImpl.java:126)
>> org.apache.crimson.jaxp.SAXParserFactoryImpl.newSAXParserImpl(SAXParserFactoryImpl.java:113)
>> org.apache.crimson.jaxp.SAXParserFactoryImpl.setFeature(SAXParserFactoryImpl.java:141)
>
> Try to find what *.jar file in your system contains the above classes.
>
> E.g. searching for string "crimson" in *.jar files.
> That string will be visible in the archive file as it is a name of a directory.
>
> HTH.
>
I have a bash function which does this moderately well. Happy to share it, if needed.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: More information, Re: Tomcat 8.5.68 failing on takeoff!
Posted by Jo...@wellsfargo.com.INVALID.
> -----Original Message-----
> From: James H. H. Lampert <ja...@touchtonecorp.com.INVALID>
> Sent: Monday, August 09, 2021 12:21 PM
> To: users@tomcat.apache.org
> Subject: Re: More information, Re: Tomcat 8.5.68 failing on takeoff!
>
> On 8/6/21 9:17 AM, Konstantin Kolinko wrote:
>
> > Try to find what *.jar file in your system contains the above classes.
> >
> > E.g. searching for string "crimson" in *.jar files.
> > That string will be visible in the archive file as it is a name of a directory.
>
> I've learned that QShell (a *nix-like shell that was added with Java
> support) on an AS/400 does have both "find" and "grep," so it wasn't quite so
> futile as I thought.
>
> If I go into QShell, navigate to the JVM home directory, and do a "find . -
> name '*.jar'"
> I get
>
> ./jre/lib/ppc64/compressedrefs/jclSC180/vm.jar
> ./jre/lib/ppc64/default/jclSC180/vm.jar
> ./jre/lib/ext/db2_classes18.jar
> ./jre/lib/ext/CmpCrmf.jar
> ./jre/lib/ext/IBMSecureRandom.jar
> ./jre/lib/ext/cldrdata.jar
> ./jre/lib/ext/dnsns.jar
> ./jre/lib/ext/dtfj.jar
> ./jre/lib/ext/dtfjview.jar
> ./jre/lib/ext/gskikm.jar
> ./jre/lib/ext/healthcenter.jar
> ./jre/lib/ext/ibmcmsprovider.jar
> ./jre/lib/ext/ibmjcefips.jar
> ./jre/lib/ext/ibmjceplus.jar
> ./jre/lib/ext/ibmjceprovider.jar
> ./jre/lib/ext/ibmkeycert.jar
> ./jre/lib/ext/ibmpkcs11impl.jar
> ./jre/lib/ext/ibmsaslprovider.jar
> ./jre/lib/ext/ibmxmlcrypto.jar
> ./jre/lib/ext/ibmxmldsigprovider.jar
> ./jre/lib/ext/ibmxmlencprovider.jar
> ./jre/lib/ext/jaccess.jar
> ./jre/lib/ext/localedata.jar
> ./jre/lib/ext/nashorn.jar
> ./jre/lib/ext/traceformat.jar
> ./jre/lib/ext/xmlencfw.jar
> ./jre/lib/ext/zipfs.jar
> ./jre/lib/aggressive.jar
> ./jre/lib/charsets.jar
> ./jre/lib/dataaccess.jar
> ./jre/lib/ddr/j9ddr.jar
> ./jre/lib/deploy.jar
> ./jre/lib/ibmcertpathfw.jar
> ./jre/lib/ibmcertpathprovider.jar
> ./jre/lib/ibmcfw.jar
> ./jre/lib/ibmjcefw.jar
> ./jre/lib/ibmjgssfw.jar
> ./jre/lib/ibmjgssprovider.jar
> ./jre/lib/ibmjssefw.jar
> ./jre/lib/ibmjsseprovider2.jar
> ./jre/lib/ibmorb.jar
> ./jre/lib/ibmorbapi.jar
> ./jre/lib/ibmpkcs.jar
> ./jre/lib/ibmsaslfw.jar
> ./jre/lib/javaws.jar
> ./jre/lib/management-agent.jar
> ./jre/lib/math.jar
> ./jre/lib/plugin.jar
> ./jre/lib/resources.jar
> ./jre/lib/rt.jar
> ./jre/lib/se-service.jar
> ./jre/lib/security/US_export_policy_56bit.jar
> ./jre/lib/security/local_policy_56bit.jar
> ./jre/lib/security/policy/limited/US_export_policy.jar
> ./jre/lib/security/policy/limited/local_policy.jar
> ./jre/lib/security/policy/unlimited/US_export_policy.jar
> ./jre/lib/security/policy/unlimited/local_policy.jar
> ./jre/lib/tools/monitoring-api.jar
> ./jre/lib/xml.jar
> ./jre/lib/xmldsigfw.jar
> ./IBMmisc.jar
> ./lib/dt.jar
> ./lib/ibmorbtools.jar
> ./lib/jconsole.jar
> ./lib/tools.jar
> ./lib/IBMi5OSJSSE.jar
>
> If I do a "find . -name '*crimson*'", I get nothing.
>
> If I do a "find . -name '*.jar' -exec grep -l 'crimson' {} \;", I also get nothing.
>
> So unless anybody else has any ideas, I'm once again stuck, at least on this
> angle.
>
> Mark Thomas wrote:
> > Tomcat 7 doesn't have JASPIC support so you'll never see this issue in
> Tomcat 7.
>
> . . . to which I replied (seriously, rather than flippantly) "What's a JASPIC?"
>
> I've finally taken a look at what JASPIC is. Interesting. If it's JASPIC support in
> Tomcat 8 that is throwing exceptions and killing manager under this particular
> Java 8 JVM, is there a way to disable it, at least until the customer has their
> PTFs up to date?
>
> --
> JHHL
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
Check under the Tomcat webapps and lib directories.
Re: More information, Re: Tomcat 8.5.68 failing on takeoff!
Posted by "James H. H. Lampert" <ja...@touchtonecorp.com.INVALID>.
On 8/9/21 11:33 AM, Mark Thomas wrote:
> The fix will be in the September releases.
Thanks.
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: More information, Re: Tomcat 8.5.68 failing on takeoff!
Posted by Mark Thomas <ma...@apache.org>.
On August 9, 2021 5:31:41 PM UTC, "James H. H. Lampert" <ja...@touchtonecorp.com.INVALID> wrote:
>On 8/9/21 10:24 AM, Mark Thomas wrote:
>> Future versions of Tomcat won't see this issue but if the customer is
>
>> prepared to update Tomcat to fix this issue then they might as well
>just
>> update Java (assuming that is indeed sufficient to fix this).
>
>Given that they currently seem to be happy as clams on their currently
>installed Tomcat 7, and that we've only been updating customers to
>Tomcat 8 in order to proactively deal with any security complaints that
>
>might come up, they can presumably wait for a Tomcat 8 that has the
>relevant fix.
>
>And this customer is not in any particular hurry for updating
>*anything*
>(a trait I share).
>
>Any idea when a Tomcat 8 with the relevant fix might come out?
The fix will be in the September releases.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: More information, Re: Tomcat 8.5.68 failing on takeoff!
Posted by "James H. H. Lampert" <ja...@touchtonecorp.com.INVALID>.
On 8/9/21 10:24 AM, Mark Thomas wrote:
> Future versions of Tomcat won't see this issue but if the customer is
> prepared to update Tomcat to fix this issue then they might as well just
> update Java (assuming that is indeed sufficient to fix this).
Given that they currently seem to be happy as clams on their currently
installed Tomcat 7, and that we've only been updating customers to
Tomcat 8 in order to proactively deal with any security complaints that
might come up, they can presumably wait for a Tomcat 8 that has the
relevant fix.
And this customer is not in any particular hurry for updating *anything*
(a trait I share).
Any idea when a Tomcat 8 with the relevant fix might come out?
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: More information, Re: Tomcat 8.5.68 failing on takeoff!
Posted by Mark Thomas <ma...@apache.org>.
On 09/08/2021 19:21, James H. H. Lampert wrote:
> On 8/6/21 9:17 AM, Konstantin Kolinko wrote:
>
>> Try to find what *.jar file in your system contains the above classes.
>>
>> E.g. searching for string "crimson" in *.jar files.
>> That string will be visible in the archive file as it is a name of a
>> directory.
>
> I've learned that QShell (a *nix-like shell that was added with Java
> support) on an AS/400 does have both "find" and "grep," so it wasn't
> quite so futile as I thought.
>
> If I go into QShell, navigate to the JVM home directory, and do a
> "find . -name '*.jar'"
> I get
>
> ./jre/lib/ppc64/compressedrefs/jclSC180/vm.jar
> ./jre/lib/ppc64/default/jclSC180/vm.jar
> ./jre/lib/ext/db2_classes18.jar
> ./jre/lib/ext/CmpCrmf.jar
> ./jre/lib/ext/IBMSecureRandom.jar
> ./jre/lib/ext/cldrdata.jar
> ./jre/lib/ext/dnsns.jar
> ./jre/lib/ext/dtfj.jar
> ./jre/lib/ext/dtfjview.jar
> ./jre/lib/ext/gskikm.jar
> ./jre/lib/ext/healthcenter.jar
> ./jre/lib/ext/ibmcmsprovider.jar
> ./jre/lib/ext/ibmjcefips.jar
> ./jre/lib/ext/ibmjceplus.jar
> ./jre/lib/ext/ibmjceprovider.jar
> ./jre/lib/ext/ibmkeycert.jar
> ./jre/lib/ext/ibmpkcs11impl.jar
> ./jre/lib/ext/ibmsaslprovider.jar
> ./jre/lib/ext/ibmxmlcrypto.jar
> ./jre/lib/ext/ibmxmldsigprovider.jar
> ./jre/lib/ext/ibmxmlencprovider.jar
> ./jre/lib/ext/jaccess.jar
> ./jre/lib/ext/localedata.jar
> ./jre/lib/ext/nashorn.jar
> ./jre/lib/ext/traceformat.jar
> ./jre/lib/ext/xmlencfw.jar
> ./jre/lib/ext/zipfs.jar
> ./jre/lib/aggressive.jar
> ./jre/lib/charsets.jar
> ./jre/lib/dataaccess.jar
> ./jre/lib/ddr/j9ddr.jar
> ./jre/lib/deploy.jar
> ./jre/lib/ibmcertpathfw.jar
> ./jre/lib/ibmcertpathprovider.jar
> ./jre/lib/ibmcfw.jar
> ./jre/lib/ibmjcefw.jar
> ./jre/lib/ibmjgssfw.jar
> ./jre/lib/ibmjgssprovider.jar
> ./jre/lib/ibmjssefw.jar
> ./jre/lib/ibmjsseprovider2.jar
> ./jre/lib/ibmorb.jar
> ./jre/lib/ibmorbapi.jar
> ./jre/lib/ibmpkcs.jar
> ./jre/lib/ibmsaslfw.jar
> ./jre/lib/javaws.jar
> ./jre/lib/management-agent.jar
> ./jre/lib/math.jar
> ./jre/lib/plugin.jar
> ./jre/lib/resources.jar
> ./jre/lib/rt.jar
> ./jre/lib/se-service.jar
> ./jre/lib/security/US_export_policy_56bit.jar
> ./jre/lib/security/local_policy_56bit.jar
> ./jre/lib/security/policy/limited/US_export_policy.jar
> ./jre/lib/security/policy/limited/local_policy.jar
> ./jre/lib/security/policy/unlimited/US_export_policy.jar
> ./jre/lib/security/policy/unlimited/local_policy.jar
> ./jre/lib/tools/monitoring-api.jar
> ./jre/lib/xml.jar
> ./jre/lib/xmldsigfw.jar
> ./IBMmisc.jar
> ./lib/dt.jar
> ./lib/ibmorbtools.jar
> ./lib/jconsole.jar
> ./lib/tools.jar
> ./lib/IBMi5OSJSSE.jar
>
> If I do a "find . -name '*crimson*'", I get nothing.
>
> If I do a "find . -name '*.jar' -exec grep -l 'crimson' {} \;", I also
> get nothing.
>
> So unless anybody else has any ideas, I'm once again stuck, at least on
> this angle.
>
> Mark Thomas wrote:
>> Tomcat 7 doesn't have JASPIC support so you'll never see this issue in
>> Tomcat 7.
>
> . . . to which I replied (seriously, rather than flippantly) "What's a
> JASPIC?"
>
> I've finally taken a look at what JASPIC is. Interesting. If it's JASPIC
> support in Tomcat 8 that is throwing exceptions and killing manager
> under this particular Java 8 JVM, is there a way to disable it, at least
> until the customer has their PTFs up to date?
Sorry, no. The code in question is always going to get executed.
Future versions of Tomcat won't see this issue but if the customer is
prepared to update Tomcat to fix this issue then they might as well just
update Java (assuming that is indeed sufficient to fix this).
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: More information, Re: Tomcat 8.5.68 failing on takeoff!
Posted by "James H. H. Lampert" <ja...@touchtonecorp.com.INVALID>.
On 8/6/21 9:17 AM, Konstantin Kolinko wrote:
> Try to find what *.jar file in your system contains the above classes.
>
> E.g. searching for string "crimson" in *.jar files.
> That string will be visible in the archive file as it is a name of a directory.
I've learned that QShell (a *nix-like shell that was added with Java
support) on an AS/400 does have both "find" and "grep," so it wasn't
quite so futile as I thought.
If I go into QShell, navigate to the JVM home directory, and do a
"find . -name '*.jar'"
I get
./jre/lib/ppc64/compressedrefs/jclSC180/vm.jar
./jre/lib/ppc64/default/jclSC180/vm.jar
./jre/lib/ext/db2_classes18.jar
./jre/lib/ext/CmpCrmf.jar
./jre/lib/ext/IBMSecureRandom.jar
./jre/lib/ext/cldrdata.jar
./jre/lib/ext/dnsns.jar
./jre/lib/ext/dtfj.jar
./jre/lib/ext/dtfjview.jar
./jre/lib/ext/gskikm.jar
./jre/lib/ext/healthcenter.jar
./jre/lib/ext/ibmcmsprovider.jar
./jre/lib/ext/ibmjcefips.jar
./jre/lib/ext/ibmjceplus.jar
./jre/lib/ext/ibmjceprovider.jar
./jre/lib/ext/ibmkeycert.jar
./jre/lib/ext/ibmpkcs11impl.jar
./jre/lib/ext/ibmsaslprovider.jar
./jre/lib/ext/ibmxmlcrypto.jar
./jre/lib/ext/ibmxmldsigprovider.jar
./jre/lib/ext/ibmxmlencprovider.jar
./jre/lib/ext/jaccess.jar
./jre/lib/ext/localedata.jar
./jre/lib/ext/nashorn.jar
./jre/lib/ext/traceformat.jar
./jre/lib/ext/xmlencfw.jar
./jre/lib/ext/zipfs.jar
./jre/lib/aggressive.jar
./jre/lib/charsets.jar
./jre/lib/dataaccess.jar
./jre/lib/ddr/j9ddr.jar
./jre/lib/deploy.jar
./jre/lib/ibmcertpathfw.jar
./jre/lib/ibmcertpathprovider.jar
./jre/lib/ibmcfw.jar
./jre/lib/ibmjcefw.jar
./jre/lib/ibmjgssfw.jar
./jre/lib/ibmjgssprovider.jar
./jre/lib/ibmjssefw.jar
./jre/lib/ibmjsseprovider2.jar
./jre/lib/ibmorb.jar
./jre/lib/ibmorbapi.jar
./jre/lib/ibmpkcs.jar
./jre/lib/ibmsaslfw.jar
./jre/lib/javaws.jar
./jre/lib/management-agent.jar
./jre/lib/math.jar
./jre/lib/plugin.jar
./jre/lib/resources.jar
./jre/lib/rt.jar
./jre/lib/se-service.jar
./jre/lib/security/US_export_policy_56bit.jar
./jre/lib/security/local_policy_56bit.jar
./jre/lib/security/policy/limited/US_export_policy.jar
./jre/lib/security/policy/limited/local_policy.jar
./jre/lib/security/policy/unlimited/US_export_policy.jar
./jre/lib/security/policy/unlimited/local_policy.jar
./jre/lib/tools/monitoring-api.jar
./jre/lib/xml.jar
./jre/lib/xmldsigfw.jar
./IBMmisc.jar
./lib/dt.jar
./lib/ibmorbtools.jar
./lib/jconsole.jar
./lib/tools.jar
./lib/IBMi5OSJSSE.jar
If I do a "find . -name '*crimson*'", I get nothing.
If I do a "find . -name '*.jar' -exec grep -l 'crimson' {} \;", I also
get nothing.
So unless anybody else has any ideas, I'm once again stuck, at least on
this angle.
Mark Thomas wrote:
> Tomcat 7 doesn't have JASPIC support so you'll never see this issue in Tomcat 7.
. . . to which I replied (seriously, rather than flippantly) "What's a
JASPIC?"
I've finally taken a look at what JASPIC is. Interesting. If it's JASPIC
support in Tomcat 8 that is throwing exceptions and killing manager
under this particular Java 8 JVM, is there a way to disable it, at least
until the customer has their PTFs up to date?
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: More information, Re: Tomcat 8.5.68 failing on takeoff!
Posted by Konstantin Kolinko <kn...@gmail.com>.
пт, 6 авг. 2021 г. в 01:33, James H. H. Lampert
<ja...@touchtonecorp.com.invalid>:
> org.xml.sax.SAXNotRecognizedException: Feature:
> http://apache.org/xml/features/allow-java-encodings
> org.apache.crimson.parser.XMLReaderImpl.setFeature(XMLReaderImpl.java:213)
> org.apache.crimson.jaxp.SAXParserImpl.setFeatures(SAXParserImpl.java:143)
> org.apache.crimson.jaxp.SAXParserImpl.<init>(SAXParserImpl.java:126)
> org.apache.crimson.jaxp.SAXParserFactoryImpl.newSAXParserImpl(SAXParserFactoryImpl.java:113)
> org.apache.crimson.jaxp.SAXParserFactoryImpl.setFeature(SAXParserFactoryImpl.java:141)
Try to find what *.jar file in your system contains the above classes.
E.g. searching for string "crimson" in *.jar files.
That string will be visible in the archive file as it is a name of a directory.
HTH.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
More information, Re: Tomcat 8.5.68 failing on takeoff!
Posted by "James H. H. Lampert" <ja...@touchtonecorp.com.INVALID>.
I finally had a chance to switch the customer back to the failing Tomcat
8.5.68, and this is what the browser error page shows (with a 500 error):
Type Exception Report
Message AuthConfigFactory error: java.lang.reflect.InvocationTargetException
Description The server encountered an unexpected condition that
prevented it from fulfilling the request.
Exception
java.lang.SecurityException: AuthConfigFactory error:
java.lang.reflect.InvocationTargetException
javax.security.auth.message.config.AuthConfigFactory.getFactory(AuthConfigFactory.java:85)
org.apache.catalina.authenticator.AuthenticatorBase.findJaspicProvider(AuthenticatorBase.java:1421)
org.apache.catalina.authenticator.AuthenticatorBase.getJaspicProvider(AuthenticatorBase.java:1411)
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:535)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:698)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:364)
org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:624)
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:831)
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1651)
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
java.lang.Thread.run(Thread.java:811)
Root Cause
java.lang.reflect.InvocationTargetException
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:83)
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57)
java.lang.reflect.Constructor.newInstance(Constructor.java:437)
javax.security.auth.message.config.AuthConfigFactory$1.run(AuthConfigFactory.java:76)
javax.security.auth.message.config.AuthConfigFactory$1.run(AuthConfigFactory.java:67)
java.security.AccessController.doPrivileged(AccessController.java:696)
javax.security.auth.message.config.AuthConfigFactory.getFactory(AuthConfigFactory.java:66)
org.apache.catalina.authenticator.AuthenticatorBase.findJaspicProvider(AuthenticatorBase.java:1421)
org.apache.catalina.authenticator.AuthenticatorBase.getJaspicProvider(AuthenticatorBase.java:1411)
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:535)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:698)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:364)
org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:624)
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:831)
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1651)
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
java.lang.Thread.run(Thread.java:811)
Root Cause
java.lang.SecurityException: org.xml.sax.SAXNotRecognizedException:
Feature: http://apache.org/xml/features/allow-java-encodings
org.apache.catalina.authenticator.jaspic.PersistentProviderRegistrations.loadProviders(PersistentProviderRegistrations.java:65)
org.apache.catalina.authenticator.jaspic.AuthConfigFactoryImpl.loadPersistentRegistrations(AuthConfigFactoryImpl.java:345)
org.apache.catalina.authenticator.jaspic.AuthConfigFactoryImpl.<init>(AuthConfigFactoryImpl.java:68)
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:83)
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57)
java.lang.reflect.Constructor.newInstance(Constructor.java:437)
javax.security.auth.message.config.AuthConfigFactory$1.run(AuthConfigFactory.java:76)
javax.security.auth.message.config.AuthConfigFactory$1.run(AuthConfigFactory.java:67)
java.security.AccessController.doPrivileged(AccessController.java:696)
javax.security.auth.message.config.AuthConfigFactory.getFactory(AuthConfigFactory.java:66)
org.apache.catalina.authenticator.AuthenticatorBase.findJaspicProvider(AuthenticatorBase.java:1421)
org.apache.catalina.authenticator.AuthenticatorBase.getJaspicProvider(AuthenticatorBase.java:1411)
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:535)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:698)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:364)
org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:624)
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:831)
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1651)
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
java.lang.Thread.run(Thread.java:811)
Root Cause
org.xml.sax.SAXNotRecognizedException: Feature:
http://apache.org/xml/features/allow-java-encodings
org.apache.crimson.parser.XMLReaderImpl.setFeature(XMLReaderImpl.java:213)
org.apache.crimson.jaxp.SAXParserImpl.setFeatures(SAXParserImpl.java:143)
org.apache.crimson.jaxp.SAXParserImpl.<init>(SAXParserImpl.java:126)
org.apache.crimson.jaxp.SAXParserFactoryImpl.newSAXParserImpl(SAXParserFactoryImpl.java:113)
org.apache.crimson.jaxp.SAXParserFactoryImpl.setFeature(SAXParserFactoryImpl.java:141)
org.apache.tomcat.util.digester.Digester.setFeature(Digester.java:526)
org.apache.catalina.authenticator.jaspic.PersistentProviderRegistrations.loadProviders(PersistentProviderRegistrations.java:61)
org.apache.catalina.authenticator.jaspic.AuthConfigFactoryImpl.loadPersistentRegistrations(AuthConfigFactoryImpl.java:345)
org.apache.catalina.authenticator.jaspic.AuthConfigFactoryImpl.<init>(AuthConfigFactoryImpl.java:68)
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:83)
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57)
java.lang.reflect.Constructor.newInstance(Constructor.java:437)
javax.security.auth.message.config.AuthConfigFactory$1.run(AuthConfigFactory.java:76)
javax.security.auth.message.config.AuthConfigFactory$1.run(AuthConfigFactory.java:67)
java.security.AccessController.doPrivileged(AccessController.java:696)
javax.security.auth.message.config.AuthConfigFactory.getFactory(AuthConfigFactory.java:66)
org.apache.catalina.authenticator.AuthenticatorBase.findJaspicProvider(AuthenticatorBase.java:1421)
org.apache.catalina.authenticator.AuthenticatorBase.getJaspicProvider(AuthenticatorBase.java:1411)
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:535)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:698)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:364)
org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:624)
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:831)
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1651)
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
java.lang.Thread.run(Thread.java:811)
Note The full stack trace of the root cause is available in the server logs.
I will note that the *second* SAXNotRecognizedException stack trace
starts out exactly like the one in catalina.out, but diverges after
Digester.java:526. The first three stacktraces on the error page look
completely different.
The first stacktrace on the error page looks similar to one in
localhost.2021-08-05.log, timestamped when I attempted to access manager:
05-Aug-2021 17:05:52.697 SEVERE [https-jsse-nio-443-exec-10]
org.apache.catalina.core.StandardHostValve.invoke Exception Processing
/manager/
java.lang.SecurityException: AuthConfigFactory error:
java.lang.reflect.InvocationTargetException
at
javax.security.auth.message.config.AuthConfigFactory.getFactory(AuthConfigFactory.java:85)
. . .
localhost_access_log.2021-08-05.txt shows (IP address redacted):
[05/Aug/2021:17:05:52 -0500] "GET /manager HTTP/1.1" 302 -
[05/Aug/2021:17:05:52 -0500] "GET /manager/ HTTP/1.1" 500 9663
and the manager log shows nothing at all.
And to reiterate, the very same JVM has no difficulty at all running
Tomcat 7.0.93.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 8.5.68 failing on takeoff!
Posted by Christopher Schultz <ch...@christopherschultz.net>.
James,
On 8/3/21 08:42, Christopher Schultz wrote:
> James,
>
> On 8/2/21 19:31, James H. H. Lampert wrote:
>> This is beyond my pay grade, I'm afraid. Hopefully somebody here has a
>> clue what went wrong.
>>
>> I installed Tomcat 8.5.68 on an AS/400 with Java 8, that had been
>> running Tomcat 7 for years with no problems.
>>
>> On launching Tomcat 8, if I try to connect to "manager" (the only
>> context currently in Webapps), right after:
>>
>> 02-Aug-2021 18:15:11.655 INFO [main]
>> org.apache.catalina.startup.Catalina.load Initialization processed in
>> 3271 ms
>>
>> I'm getting
>>
>> 02-Aug-2021 18:15:11.707 WARNING [main]
>> org.apache.catalina.users.MemoryUserDatabase.open Exception
>> configuring digester to permit java encoding names in XML files. Only
>> IANA encoding names will be supported.
>> org.xml.sax.SAXNotRecognizedException: Feature:
>> http://apache.org/xml/features/allow-java-encodings
>> at
>> org.apache.crimson.parser.XMLReaderImpl.setFeature(XMLReaderImpl.java:213)
>>
>> at
>> org.apache.crimson.jaxp.SAXParserImpl.setFeatures(SAXParserImpl.java:143)
>> at
>> org.apache.crimson.jaxp.SAXParserImpl.<init>(SAXParserImpl.java:126)
>> at
>> org.apache.crimson.jaxp.SAXParserFactoryImpl.newSAXParserImpl(SAXParserFactoryImpl.java:113)
>>
>> at
>> org.apache.crimson.jaxp.SAXParserFactoryImpl.setFeature(SAXParserFactoryImpl.java:141)
>>
>> at
>> org.apache.tomcat.util.digester.Digester.setFeature(Digester.java:526)
>> at
>> org.apache.catalina.users.MemoryUserDatabase.open(MemoryUserDatabase.java:440)
>>
>> at
>> org.apache.catalina.users.MemoryUserDatabaseFactory.getObjectInstance(MemoryUserDatabaseFactory.java:105)
>>
>> at
>> org.apache.naming.factory.FactoryBase.getObjectInstance(FactoryBase.java:96)
>>
>> at
>> javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:332)
>> at org.apache.naming.NamingContext.lookup(NamingContext.java:847)
>> at org.apache.naming.NamingContext.lookup(NamingContext.java:157)
>> at
>> org.apache.naming.NamingContextBindingsEnumeration.nextElementInternal(NamingContextBindingsEnumeration.java:115)
>>
>> at
>> org.apache.naming.NamingContextBindingsEnumeration.next(NamingContextBindingsEnumeration.java:69)
>>
>> at
>> org.apache.naming.NamingContextBindingsEnumeration.next(NamingContextBindingsEnumeration.java:32)
>>
>> at
>> org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.createMBeans(GlobalResourcesLifecycleListener.java:131)
>>
>> at
>> org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.createMBeans(GlobalResourcesLifecycleListener.java:105)
>>
>> at
>> org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.lifecycleEvent(GlobalResourcesLifecycleListener.java:80)
>>
>> at
>> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
>>
>> at
>> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423)
>>
>> at
>> org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366)
>> at
>> org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:763)
>>
>> at
>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
>> at org.apache.catalina.startup.Catalina.start(Catalina.java:688)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
>>
>> at java.lang.reflect.Method.invoke(Method.java:508)
>> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:345)
>> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:476)
>>
>>
>> I can't recall ever seeing anything like this.
>
> I checked the code and this is a non-fatal warning. I can find no
> information about the
> http://apache.org/xml/features/allow-java-encodings SAX parser feature
> and Google seems to be no help, here.
For completeness, here is the refefence that explains this feature:
https://xerces.apache.org/xerces2-j/features.html
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 8.5.68 failing on takeoff!
Posted by Christopher Schultz <ch...@christopherschultz.net>.
James,
On 8/2/21 19:31, James H. H. Lampert wrote:
> This is beyond my pay grade, I'm afraid. Hopefully somebody here has a
> clue what went wrong.
>
> I installed Tomcat 8.5.68 on an AS/400 with Java 8, that had been
> running Tomcat 7 for years with no problems.
>
> On launching Tomcat 8, if I try to connect to "manager" (the only
> context currently in Webapps), right after:
>
> 02-Aug-2021 18:15:11.655 INFO [main]
> org.apache.catalina.startup.Catalina.load Initialization processed in
> 3271 ms
>
> I'm getting
>
> 02-Aug-2021 18:15:11.707 WARNING [main]
> org.apache.catalina.users.MemoryUserDatabase.open Exception configuring
> digester to permit java encoding names in XML files. Only IANA encoding
> names will be supported.
> org.xml.sax.SAXNotRecognizedException: Feature:
> http://apache.org/xml/features/allow-java-encodings
> at
> org.apache.crimson.parser.XMLReaderImpl.setFeature(XMLReaderImpl.java:213)
> at
> org.apache.crimson.jaxp.SAXParserImpl.setFeatures(SAXParserImpl.java:143)
> at
> org.apache.crimson.jaxp.SAXParserImpl.<init>(SAXParserImpl.java:126)
> at
> org.apache.crimson.jaxp.SAXParserFactoryImpl.newSAXParserImpl(SAXParserFactoryImpl.java:113)
>
> at
> org.apache.crimson.jaxp.SAXParserFactoryImpl.setFeature(SAXParserFactoryImpl.java:141)
>
> at
> org.apache.tomcat.util.digester.Digester.setFeature(Digester.java:526)
> at
> org.apache.catalina.users.MemoryUserDatabase.open(MemoryUserDatabase.java:440)
>
> at
> org.apache.catalina.users.MemoryUserDatabaseFactory.getObjectInstance(MemoryUserDatabaseFactory.java:105)
>
> at
> org.apache.naming.factory.FactoryBase.getObjectInstance(FactoryBase.java:96)
>
> at
> javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:332)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:847)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:157)
> at
> org.apache.naming.NamingContextBindingsEnumeration.nextElementInternal(NamingContextBindingsEnumeration.java:115)
>
> at
> org.apache.naming.NamingContextBindingsEnumeration.next(NamingContextBindingsEnumeration.java:69)
>
> at
> org.apache.naming.NamingContextBindingsEnumeration.next(NamingContextBindingsEnumeration.java:32)
>
> at
> org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.createMBeans(GlobalResourcesLifecycleListener.java:131)
>
> at
> org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.createMBeans(GlobalResourcesLifecycleListener.java:105)
>
> at
> org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.lifecycleEvent(GlobalResourcesLifecycleListener.java:80)
>
> at
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
>
> at
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423)
>
> at
> org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366)
> at
> org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:763)
>
> at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:688)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
>
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:345)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:476)
>
>
> I can't recall ever seeing anything like this.
I checked the code and this is a non-fatal warning. I can find no
information about the
http://apache.org/xml/features/allow-java-encodings SAX parser feature
and Google seems to be no help, here.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat 8.5.68 failing on takeoff!
Posted by jo...@wellsfargo.com.INVALID.
I'm no expert, especially on AS400's, but make sure that your Java 8 is good. Saw someone on CentOS having a similar issue and it was a bad Java.
Dream * Excel * Explore * Inspire
Jon McAlexander
Infrastructure Engineer
Asst Vice President
Middleware Product Engineering
Enterprise CIO | Platform Services | Middleware | Infrastructure Solutions
8080 Cobblestone Rd | Urbandale, IA 50322
MAC: F4469-010
Tel 515-988-2508 | Cell 515-988-2508
jonmcalexander@wellsfargo.com
Upcoming PTO: 10/30/2020, 11/6/2020, 11/13/2020, 11/20/2020, 11/27/2020, 12/2/2020, 12/4/2020, 12/11/2020, 12/18/2020, 12/28/2020, 12/29/2020, 12/30/2020, 12/31/2020
This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.
> -----Original Message-----
> From: James H. H. Lampert <ja...@touchtonecorp.com.INVALID>
> Sent: Monday, August 2, 2021 6:31 PM
> To: Tomcat Users List <us...@tomcat.apache.org>
> Subject: Tomcat 8.5.68 failing on takeoff!
>
> This is beyond my pay grade, I'm afraid. Hopefully somebody here has a clue
> what went wrong.
>
> I installed Tomcat 8.5.68 on an AS/400 with Java 8, that had been running
> Tomcat 7 for years with no problems.
>
> On launching Tomcat 8, if I try to connect to "manager" (the only context
> currently in Webapps), right after:
>
> 02-Aug-2021 18:15:11.655 INFO [main]
> org.apache.catalina.startup.Catalina.load Initialization processed in
> 3271 ms
>
> I'm getting
>
> 02-Aug-2021 18:15:11.707 WARNING [main]
> org.apache.catalina.users.MemoryUserDatabase.open Exception configuring
> digester to permit java encoding names in XML files. Only IANA encoding
> names will be supported.
> org.xml.sax.SAXNotRecognizedException: Feature:
> https://urldefense.com/v3/__http://apache.org/xml/features/allow-java-
> encodings__;!!F9svGWnIaVPGSwU!9FyRcl2TpIK2uUGhl8znN39ty5Z8hd7W3z
> MEHabLBNJauJFSdGQX9Qyj1azOxNKQgopT690$
> at
> org.apache.crimson.parser.XMLReaderImpl.setFeature(XMLReaderImpl.java
> :213)
> at
> org.apache.crimson.jaxp.SAXParserImpl.setFeatures(SAXParserImpl.java:143
> )
> at
> org.apache.crimson.jaxp.SAXParserImpl.<init>(SAXParserImpl.java:126)
> at
> org.apache.crimson.jaxp.SAXParserFactoryImpl.newSAXParserImpl(SAXPars
> erFactoryImpl.java:113)
> at
> org.apache.crimson.jaxp.SAXParserFactoryImpl.setFeature(SAXParserFactor
> yImpl.java:141)
> at
> org.apache.tomcat.util.digester.Digester.setFeature(Digester.java:526)
> at
> org.apache.catalina.users.MemoryUserDatabase.open(MemoryUserDatabas
> e.java:440)
> at
> org.apache.catalina.users.MemoryUserDatabaseFactory.getObjectInstance(
> MemoryUserDatabaseFactory.java:105)
> at
> org.apache.naming.factory.FactoryBase.getObjectInstance(FactoryBase.java
> :96)
> at
> javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:
> 332)
> at
> org.apache.naming.NamingContext.lookup(NamingContext.java:847)
> at
> org.apache.naming.NamingContext.lookup(NamingContext.java:157)
> at
> org.apache.naming.NamingContextBindingsEnumeration.nextElementIntern
> al(NamingContextBindingsEnumeration.java:115)
> at
> org.apache.naming.NamingContextBindingsEnumeration.next(NamingConte
> xtBindingsEnumeration.java:69)
> at
> org.apache.naming.NamingContextBindingsEnumeration.next(NamingConte
> xtBindingsEnumeration.java:32)
> at
> org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.createMBean
> s(GlobalResourcesLifecycleListener.java:131)
> at
> org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.createMBean
> s(GlobalResourcesLifecycleListener.java:105)
> at
> org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.lifecycleEvent
> (GlobalResourcesLifecycleListener.java:80)
> at
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:1
> 23)
> at
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423
> )
> at
> org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366)
> at
> org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:7
> 63)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:688)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
> ava:90)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:345)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:476)
>
>
> I can't recall ever seeing anything like this.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 8.5.68 failing on takeoff!
Posted by "James H. H. Lampert" <ja...@touchtonecorp.com.INVALID>.
Mssrs. Kolinko and Schultz said:
>> 2. The stack trace starts with "Bootstrap.main". I.e. it is the thread
>> that starts Tomcat.
>>
>> I.e. this occurs when Tomcat starts up and has nothing to do with your
>> attempt to access the Manager web application.
>>
>>
>> 3. The stack trace contains "org.apache.crimson".
>>
>> Apache Crimson project was retired 11 years ago and should not be used
>> nowadays.
>> https://xml.apache.org/crimson/
>> https://attic.apache.org/projects/crimson.html
>>
>> You have that library in Tomcat classpath? Where? Why?
>
> Good catch.
>
> The JVM has been bundled with a SAX parser for ages, now. You might ask
> your application/engineering team if it's okay to try your application
> without a bundled XML library.
>
> You might also ask why it's being put into CATALINA_BASE/lib (or
> endorsed-libs?) instead of in the application's WEB-INF/lib where it
> belongs.
A bit more information:
Our application isn't even *installed* in the new Tomcat yet. As I said,
the *only* context currently in Webapps is manager; everything else was
stripped out, including the default ROOT, shortly after I unpacked the
Tomcat 8.5.68 ZIP file on the box.
Tomcat 7.0.93 continues to run just fine, under the same Java 8, after I
swapped it back in (and I'm definitely glad I do updates in a way that
makes that easy).
Last night, I was a bit lax in proofreading my initial post, and somehow
some critical information got left out.
The stacktrace included in the post was, of course, from the launch
process.
When I attempt to connect to manager, I get a "500-Internal Server
Error" page, that has a few stacktraces of its own (but adds nothing to
Catalina.out). Alas, I didn't save a copy of the error page, and it
could be several hours before I can swap the 8.5.68 back in and take
down the details.
Jon McAlexander suggested a possible bad JVM; while I wonder how that
could be, given that Tomcat 7.0.98 runs just fine, I will note that this
particular box is on a slightly different Java 8 JVM from what we see on
other customer boxes where we already have 8.5.6x running, and I think
we've already asked them to check on whether their Java PTFs (analogous
to what M$ calls "service packs") are current. The Tomcat 7 manager
reports their JVM version as "8.0.5.20 - pap6480sr5fp20-20180802_01(SR5
FP20)"
I just checked the Catalina.out of another customer we have on 8.5.68.
Nothing at all between
06-Jul-2021 19:11:49.841 INFO [main]
org.apache.catalina.startup.Catalina.load Initialization processed in
3303 ms
and
06-Jul-2021 19:11:49.905 INFO [main]
org.apache.catalina.core.StandardService.startInternal Starting service
[Catalina]
Is there any other information I could gather, without having to switch
the customer's Tomcat 8 live?
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 8.5.68 failing on takeoff!
Posted by Christopher Schultz <ch...@christopherschultz.net>.
Konstantin,
On 8/3/21 04:07, Konstantin Kolinko wrote:
> вт, 3 авг. 2021 г. в 02:31, James H. H. Lampert
> <ja...@touchtonecorp.com.invalid>:
>>
>> This is beyond my pay grade, I'm afraid. Hopefully somebody here has a
>> clue what went wrong.
>>
>> I installed Tomcat 8.5.68 on an AS/400 with Java 8, that had been
>> running Tomcat 7 for years with no problems.
>>
>> On launching Tomcat 8, if I try to connect to "manager" (the only
>> context currently in Webapps), right after:
>>
>> 02-Aug-2021 18:15:11.655 INFO [main]
>> org.apache.catalina.startup.Catalina.load Initialization processed in
>> 3271 ms
>>
>> I'm getting
>>
>> 02-Aug-2021 18:15:11.707 WARNING [main]
>> org.apache.catalina.users.MemoryUserDatabase.open Exception configuring
>> digester to permit java encoding names in XML files. Only IANA encoding
>> names will be supported.
>> org.xml.sax.SAXNotRecognizedException: Feature:
>> http://apache.org/xml/features/allow-java-encodings
>> at
>> org.apache.crimson.parser.XMLReaderImpl.setFeature(XMLReaderImpl.java:213)
>> at
>> org.apache.crimson.jaxp.SAXParserImpl.setFeatures(SAXParserImpl.java:143)
>> at org.apache.crimson.jaxp.SAXParserImpl.<init>(SAXParserImpl.java:126)
>> at
>> org.apache.crimson.jaxp.SAXParserFactoryImpl.newSAXParserImpl(SAXParserFactoryImpl.java:113)
>> at
>> org.apache.crimson.jaxp.SAXParserFactoryImpl.setFeature(SAXParserFactoryImpl.java:141)
>> at org.apache.tomcat.util.digester.Digester.setFeature(Digester.java:526)
>> at
>> org.apache.catalina.users.MemoryUserDatabase.open(MemoryUserDatabase.java:440)
>
> [...]
>
>> at org.apache.catalina.startup.Catalina.start(Catalina.java:688)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
>> at java.lang.reflect.Method.invoke(Method.java:508)
>> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:345)
>> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:476)
>
> 1. It is a warning, not an error. If you look at
> MemoryUserDatabase.java:440 you will see that it is caught and
> ignored.
>
> It means that the XML parser does not recognize the
> "http://apache.org/xml/features/allow-java-encodings" feature name.
>
>
> 2. The stack trace starts with "Bootstrap.main". I.e. it is the thread
> that starts Tomcat.
>
> I.e. this occurs when Tomcat starts up and has nothing to do with your
> attempt to access the Manager web application.
>
>
> 3. The stack trace contains "org.apache.crimson".
>
> Apache Crimson project was retired 11 years ago and should not be used nowadays.
> https://xml.apache.org/crimson/
> https://attic.apache.org/projects/crimson.html
>
> You have that library in Tomcat classpath? Where? Why?
Good catch.
The JVM has been bundled with a SAX parser for ages, now. You might ask
your application/engineering team if it's okay to try your application
without a bundled XML library.
You might also ask why it's being put into CATALINA_BASE/lib (or
endorsed-libs?) instead of in the application's WEB-INF/lib where it
belongs.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 8.5.68 failing on takeoff!
Posted by Konstantin Kolinko <kn...@gmail.com>.
вт, 3 авг. 2021 г. в 02:31, James H. H. Lampert
<ja...@touchtonecorp.com.invalid>:
>
> This is beyond my pay grade, I'm afraid. Hopefully somebody here has a
> clue what went wrong.
>
> I installed Tomcat 8.5.68 on an AS/400 with Java 8, that had been
> running Tomcat 7 for years with no problems.
>
> On launching Tomcat 8, if I try to connect to "manager" (the only
> context currently in Webapps), right after:
>
> 02-Aug-2021 18:15:11.655 INFO [main]
> org.apache.catalina.startup.Catalina.load Initialization processed in
> 3271 ms
>
> I'm getting
>
> 02-Aug-2021 18:15:11.707 WARNING [main]
> org.apache.catalina.users.MemoryUserDatabase.open Exception configuring
> digester to permit java encoding names in XML files. Only IANA encoding
> names will be supported.
> org.xml.sax.SAXNotRecognizedException: Feature:
> http://apache.org/xml/features/allow-java-encodings
> at
> org.apache.crimson.parser.XMLReaderImpl.setFeature(XMLReaderImpl.java:213)
> at
> org.apache.crimson.jaxp.SAXParserImpl.setFeatures(SAXParserImpl.java:143)
> at org.apache.crimson.jaxp.SAXParserImpl.<init>(SAXParserImpl.java:126)
> at
> org.apache.crimson.jaxp.SAXParserFactoryImpl.newSAXParserImpl(SAXParserFactoryImpl.java:113)
> at
> org.apache.crimson.jaxp.SAXParserFactoryImpl.setFeature(SAXParserFactoryImpl.java:141)
> at org.apache.tomcat.util.digester.Digester.setFeature(Digester.java:526)
> at
> org.apache.catalina.users.MemoryUserDatabase.open(MemoryUserDatabase.java:440)
[...]
> at org.apache.catalina.startup.Catalina.start(Catalina.java:688)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:345)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:476)
1. It is a warning, not an error. If you look at
MemoryUserDatabase.java:440 you will see that it is caught and
ignored.
It means that the XML parser does not recognize the
"http://apache.org/xml/features/allow-java-encodings" feature name.
2. The stack trace starts with "Bootstrap.main". I.e. it is the thread
that starts Tomcat.
I.e. this occurs when Tomcat starts up and has nothing to do with your
attempt to access the Manager web application.
3. The stack trace contains "org.apache.crimson".
Apache Crimson project was retired 11 years ago and should not be used nowadays.
https://xml.apache.org/crimson/
https://attic.apache.org/projects/crimson.html
You have that library in Tomcat classpath? Where? Why?
HTH
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org