Re: Problems with tomcat 3.3.2 and IBM JRE 1.3.0
I didn't catch this one early enough :(. JDK 1.3.0 doesn't handle indexes in jar files at all. You need to remove them to run on 1.3.0. Or, better, upgrade to at least 1.3.1. - Original Message - From: "Eduardo Piva" <[EMAIL PROTECTED]> To: Sent: Monday, August 01, 2005 4:36 AM Subject: Problems with tomcat 3.3.2 and IBM JRE 1.3.0 Hello list, I'm trying to use tomcat 3.3.2 with JDK 1.3.0. I'm developing an application in Linux/Windows, using SUN JDK 1.3.0 and tomcat 3.3.2 to test everything locally and everything is going fine. This application will run on an AIX 4, and in this machine the only JRE the sysadmins managed to install was IBM JRE 1.3.0: $ java -version java version "1.3.0" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0) Classic VM (build 1.3.0, J2RE 1.3.0 IBM build ca130-20010330 (JIT enabled: jitc)) I don't know why, but tomcat 3.3.2 doesn't starts in this machine. I need to run the tomcat in this machine, mainly because of internal problems here in the company I'm working to. The sysadmin installed tomcat 3.3.1a in this machine, which start's correctly. With this version, my application refuses to start in the AIX. In Linux with JDK 1.3.0, it start's correctly. I have two questions: 1 - Why jakarta-tomcat 3.3.2 doesn't start's with IBM jdk 1.3.0? Does anyone here managed to do that? 2 - Why my application doesn't start in jakarta-tomcat 3.3.1a in IBM jdk 1.3.0? 3 - Does anyone here uses AIX 4 and knows another VM than the one supplied by IBM for the AIX? AIX 4 is an old version and IBM does not supply JRE 1.4 neither 1.5 for this version. If anyone know how to use a newer version, please help me. :) The logs for both problems 1 and 2 are supplied below: For tomcat 3.3.2, here is the log (after this log, there is the log for my application starting in tomcat 3.3.1a): $ ./startup Using classpath: ./../lib/tomcat.jar:./../lib/common/commons-logging-api.jar Using JAVA_HOME: /usr/java130 Using TOMCAT_HOME: /home/aep022/jakarta-tomcat-3.3.2/ ERROR reading /home/aep022/jakarta-tomcat-3.3.2/conf/server.xml At Line 209 /Server/ContextManager/Http10Connector/ port=8080 secure=false maxThreads=100 maxSpareThreads=50 minSpareThreads=10 java.util.MissingResourceException: Can't find bundle for base name org.apache.tomcat.util.net.res.LocalStrings, locale en_US at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java(Compiled Code)) at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java(Compiled Code)) at java.util.ResourceBundle.getBundle(ResourceBundle.java:547) at org.apache.tomcat.util.res.StringManager.(StringManager.java:78) at org.apache.tomcat.util.res.StringManager.(StringManager.java:70) at org.apache.tomcat.util.res.StringManager.getManager(StringManager.java:249) at org.apache.tomcat.util.net.PoolTcpEndpoint.(PoolTcpEndpoint.java:58) at org.apache.tomcat.modules.server.PoolTcpConnector.(PoolTcpConnector.java:60) at org.apache.tomcat.modules.server.Http10Interceptor.(Http10Interceptor.java:68) at java.lang.Class.newInstance0(Native Method) at java.lang.Class.newInstance(Class.java:254) at org.apache.tomcat.util.xml.ObjectCreate.start(XmlMapper.java:797) at org.apache.tomcat.util.xml.XmlMapper.matchStart(XmlMapper.java:516) at org.apache.tomcat.util.xml.XmlMapper.startElement(XmlMapper.java:114) at org.apache.xerces.parsers.SAXParser.startElement(SAXParser.java(Compiled Code)) at org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValidator.java(Compiled Code)) at org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanner.java(Compiled Code)) at org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java(Compiled Code)) at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:380) at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:908) at org.apache.tomcat.util.xml.XmlMapper.readXml(XmlMapper.java:334) at org.apache.tomcat.modules.config.ServerXmlReader.loadConfigFile(ServerXmlReader.java:137) at org.apache.tomcat.modules.config.ServerXmlReader.addInterceptor(ServerXmlReader.java:113) at org.apache.tomcat.core.ContextManager.addInterceptor(ContextManager.java:393) at org.apache.tomcat.startup.EmbededTomcat.initContextManager(EmbededTomcat.java:613) at org.apache.tomcat.startup.EmbededTomcat.execute1(EmbededTomcat.java:791) at org.apache.tomcat.startup.EmbededTomcat$1.run(EmbededTomcat.java:775) at org.apache.tomcat.util.compat.Jdk12Support$PrivilegedProxy.run(Jdk12Support.java:166) at java.security.AccessController.doPrivileged(Native Method)
Re: Problems with tomcat 3.3.2 and IBM JRE 1.3.0
Thanks Larry.
The jaxp implementation tomcat was using is located in jre/lib/ext,
under IBM JRE 1.3. I don't know if this jar is from IBM or if the
sysadm of this machine installed it. I made a new install of JRE 1.3
without this jar and putted the new version of AJAX in lib/common and
the springframework worked fine.
If I have problems with tomcat 3.3.1a I'll try to upgrade to 3.3.2 and
use your tips. I won't upgrade if I don't have problems because this
would require a new installation of tomcat, and since I'm not the
sysadm of the machine, this requires authorization and stuffs like
that here in the company.
Does anyone here knows of some serious issue in tomcat 3.3.1a?
Thanks for the help!
On 8/1/05, Larry Isaacs <[EMAIL PROTECTED]> wrote:
> Eduardo,
>
> The first problem looks like the bug in JDK 1.3.x ResourceBundle
> handling (I can't recall the bug number). I believe to work
> around this you should create "classes" directory under your
> installation's "lib/common" directory. Then extract the
> "org/apache/tomcat/util/net/res/LocalStrings.properties" file from
> "lib/common/tomcat-util.jar" into the "classes" directory,
> preserving the path. Finally rename the "LocalStrings.properties"
> file to "LocalStrings_en_US.properties" ("LocalStrings_en.properties"
> might also work). ResourceBundle should keep searching all the way
> back to just "LocalStrings.properties" in this situation, but doesn't.
>
> Your second problem seems to be that the spring framework is expecting
> a newer JAXP parser than what is provided by "lib/container/crimson.jar".
> You can try a newer parser, but I can't say which versions still run
> under JDK 1.3.x. For info about controlling the parser seen
> automatically by contexts, see:
>
> http://jakarta.apache.org/tomcat/tomcat-3.3-doc/serverxml.html#LoaderInterceptor11
>
> HTH
>
> Cheers,
> Larry
>
> > -Original Message-
> > From: Eduardo Piva [mailto:[EMAIL PROTECTED]
> > Sent: Monday, August 01, 2005 7:37 AM
> > To: tomcat-dev@jakarta.apache.org
> > Subject: Problems with tomcat 3.3.2 and IBM JRE 1.3.0
> >
> > Hello list,
> >
> > I'm trying to use tomcat 3.3.2 with JDK 1.3.0. I'm developing
> > an application in Linux/Windows, using SUN JDK 1.3.0 and
> > tomcat 3.3.2 to test everything locally and everything is
> > going fine. This application will run on an AIX 4, and in
> > this machine the only JRE the sysadmins managed to install
> > was IBM JRE 1.3.0:
> >
> >
> > $ java -version
> > java version "1.3.0"
> > Java(TM) 2 Runtime Environment, Standard Edition (build
> > 1.3.0) Classic VM (build 1.3.0, J2RE 1.3.0 IBM build
> > ca130-20010330 (JIT
> > enabled: jitc))
> >
> >
> > I don't know why, but tomcat 3.3.2 doesn't starts in this
> > machine. I need to run the tomcat in this machine, mainly
> > because of internal problems here in the company I'm working to.
> >
> > The sysadmin installed tomcat 3.3.1a in this machine, which
> > start's correctly. With this version, my application refuses
> > to start in the AIX. In Linux with JDK 1.3.0, it start's correctly.
> >
> > I have two questions:
> >
> > 1 - Why jakarta-tomcat 3.3.2 doesn't start's with IBM jdk
> > 1.3.0? Does anyone here managed to do that?
> > 2 - Why my application doesn't start in jakarta-tomcat 3.3.1a
> > in IBM jdk 1.3.0?
> > 3 - Does anyone here uses AIX 4 and knows another VM than the
> > one supplied by IBM for the AIX? AIX 4 is an old version and
> > IBM does not supply JRE 1.4 neither 1.5 for this version. If
> > anyone know how to use a newer version, please help me. :)
> >
> > The logs for both problems 1 and 2 are supplied below:
> >
> > For tomcat 3.3.2, here is the log (after this log, there is
> > the log for my application starting in tomcat 3.3.1a):
> > $ ./startup
> > Using classpath:
> > ./../lib/tomcat.jar:./../lib/common/commons-logging-api.jar
> > Using JAVA_HOME: /usr/java130
> > Using TOMCAT_HOME: /home/aep022/jakarta-tomcat-3.3.2/
> > ERROR reading /home/aep022/jakarta-tomcat-3.3.2/conf/server.xml
> > At Line 209 /Server/ContextManager/Http10Connector/ port=8080
> > secure=false maxThreads=100 maxSpareThreads=50 minSpareThreads=10
> > java.util.MissingResourceException: Can't find bundle for
> > base name org.apache.tomcat.util.net.res.LocalStrings, locale en_US
> > at
> >
RE: Problems with tomcat 3.3.2 and IBM JRE 1.3.0
Eduardo,
The first problem looks like the bug in JDK 1.3.x ResourceBundle
handling (I can't recall the bug number). I believe to work
around this you should create "classes" directory under your
installation's "lib/common" directory. Then extract the
"org/apache/tomcat/util/net/res/LocalStrings.properties" file from
"lib/common/tomcat-util.jar" into the "classes" directory,
preserving the path. Finally rename the "LocalStrings.properties"
file to "LocalStrings_en_US.properties" ("LocalStrings_en.properties"
might also work). ResourceBundle should keep searching all the way
back to just "LocalStrings.properties" in this situation, but doesn't.
Your second problem seems to be that the spring framework is expecting
a newer JAXP parser than what is provided by "lib/container/crimson.jar".
You can try a newer parser, but I can't say which versions still run
under JDK 1.3.x. For info about controlling the parser seen
automatically by contexts, see:
http://jakarta.apache.org/tomcat/tomcat-3.3-doc/serverxml.html#LoaderInterceptor11
HTH
Cheers,
Larry
> -Original Message-
> From: Eduardo Piva [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 01, 2005 7:37 AM
> To: tomcat-dev@jakarta.apache.org
> Subject: Problems with tomcat 3.3.2 and IBM JRE 1.3.0
>
> Hello list,
>
> I'm trying to use tomcat 3.3.2 with JDK 1.3.0. I'm developing
> an application in Linux/Windows, using SUN JDK 1.3.0 and
> tomcat 3.3.2 to test everything locally and everything is
> going fine. This application will run on an AIX 4, and in
> this machine the only JRE the sysadmins managed to install
> was IBM JRE 1.3.0:
>
>
> $ java -version
> java version "1.3.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build
> 1.3.0) Classic VM (build 1.3.0, J2RE 1.3.0 IBM build
> ca130-20010330 (JIT
> enabled: jitc))
>
>
> I don't know why, but tomcat 3.3.2 doesn't starts in this
> machine. I need to run the tomcat in this machine, mainly
> because of internal problems here in the company I'm working to.
>
> The sysadmin installed tomcat 3.3.1a in this machine, which
> start's correctly. With this version, my application refuses
> to start in the AIX. In Linux with JDK 1.3.0, it start's correctly.
>
> I have two questions:
>
> 1 - Why jakarta-tomcat 3.3.2 doesn't start's with IBM jdk
> 1.3.0? Does anyone here managed to do that?
> 2 - Why my application doesn't start in jakarta-tomcat 3.3.1a
> in IBM jdk 1.3.0?
> 3 - Does anyone here uses AIX 4 and knows another VM than the
> one supplied by IBM for the AIX? AIX 4 is an old version and
> IBM does not supply JRE 1.4 neither 1.5 for this version. If
> anyone know how to use a newer version, please help me. :)
>
> The logs for both problems 1 and 2 are supplied below:
>
> For tomcat 3.3.2, here is the log (after this log, there is
> the log for my application starting in tomcat 3.3.1a):
> $ ./startup
> Using classpath:
> ./../lib/tomcat.jar:./../lib/common/commons-logging-api.jar
> Using JAVA_HOME: /usr/java130
> Using TOMCAT_HOME: /home/aep022/jakarta-tomcat-3.3.2/
> ERROR reading /home/aep022/jakarta-tomcat-3.3.2/conf/server.xml
> At Line 209 /Server/ContextManager/Http10Connector/ port=8080
> secure=false maxThreads=100 maxSpareThreads=50 minSpareThreads=10
> java.util.MissingResourceException: Can't find bundle for
> base name org.apache.tomcat.util.net.res.LocalStrings, locale en_US
> at
> java.util.ResourceBundle.throwMissingResourceException(Resourc
> eBundle.java(Compiled
> Code))
> at
> java.util.ResourceBundle.getBundleImpl(ResourceBundle.java(Compiled
> Code))
> at java.util.ResourceBundle.getBundle(ResourceBundle.java:547)
> at
> org.apache.tomcat.util.res.StringManager.(StringManager.java:78)
> at
> org.apache.tomcat.util.res.StringManager.(StringManager.java:70)
> at
> org.apache.tomcat.util.res.StringManager.getManager(StringMana
> ger.java:249)
> at
> org.apache.tomcat.util.net.PoolTcpEndpoint.(PoolTcpEndpo
> int.java:58)
> at
> org.apache.tomcat.modules.server.PoolTcpConnector.(PoolT
> cpConnector.java:60)
> at
> org.apache.tomcat.modules.server.Http10Interceptor.(Http
> 10Interceptor.java:68)
> at java.lang.Class.newInstance0(Native Method)
> at java.lang.Class.newInstance(Class.java:254)
> at
> org.apache.tomcat.util.xml.ObjectCreate.start(XmlMapper.java:797)
> at
> org.apache.tomcat.util.xml.XmlMapper.matchStart(XmlMapper.java:516)
> at
> org.apache.tomcat.util
RE: Problems with tomcat 3.3.2 and IBM JRE 1.3.0
Hi, Oh, that is unfortunate. 1.3.0 is the single buggiest release in Sun's history, if I recall correctly a report I read a couple of years ago. Both 1.2.7 and 1.3.1 are significantly better ;( I'm sorry I can't help more, as I'm neither a Tomcat 3.x nor an AIX expert. My only suggestion would be: can you run the thing on Linux? That'll enable you to use a more updated OS, JDK, Tomcat... But I'm guessing if you could do that, you already would have ;( Yoav Shapira System Design and Management Fellow MIT Sloan School of Management Cambridge, MA [EMAIL PROTECTED] / [EMAIL PROTECTED] > -Original Message- > From: Eduardo Piva [mailto:[EMAIL PROTECTED] > Sent: Monday, August 01, 2005 7:37 AM > To: tomcat-dev@jakarta.apache.org > Subject: Problems with tomcat 3.3.2 and IBM JRE 1.3.0 > > Hello list, > > I'm trying to use tomcat 3.3.2 with JDK 1.3.0. I'm developing an > application in Linux/Windows, using SUN JDK 1.3.0 and tomcat 3.3.2 to > test everything locally and everything is going fine. This application > will run on an AIX 4, and in this machine the only JRE the sysadmins > managed to install was IBM JRE 1.3.0: > > > $ java -version > java version "1.3.0" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0) > Classic VM (build 1.3.0, J2RE 1.3.0 IBM build ca130-20010330 (JIT > enabled: jitc)) > > > I don't know why, but tomcat 3.3.2 doesn't starts in this machine. I > need to run the tomcat in this machine, mainly because of internal > problems here in the company I'm working to. > > The sysadmin installed tomcat 3.3.1a in this machine, which start's > correctly. With this version, my application refuses to start in the > AIX. In Linux with JDK 1.3.0, it start's correctly. > > I have two questions: > > 1 - Why jakarta-tomcat 3.3.2 doesn't start's with IBM jdk 1.3.0? Does > anyone here managed to do that? > 2 - Why my application doesn't start in jakarta-tomcat 3.3.1a in IBM jdk > 1.3.0? > 3 - Does anyone here uses AIX 4 and knows another VM than the one > supplied by IBM for the AIX? AIX 4 is an old version and IBM does not > supply JRE 1.4 neither 1.5 for this version. If anyone know how to use > a newer version, please help me. :) > > The logs for both problems 1 and 2 are supplied below: > > For tomcat 3.3.2, here is the log (after this log, there is the log > for my application starting in tomcat 3.3.1a): > $ ./startup > Using classpath: ./../lib/tomcat.jar:./../lib/common/commons-logging- > api.jar > Using JAVA_HOME: /usr/java130 > Using TOMCAT_HOME: /home/aep022/jakarta-tomcat-3.3.2/ > ERROR reading /home/aep022/jakarta-tomcat-3.3.2/conf/server.xml > At Line 209 /Server/ContextManager/Http10Connector/ port=8080 > secure=false maxThreads=100 maxSpareThreads=50 minSpareThreads=10 > java.util.MissingResourceException: Can't find bundle for base name > org.apache.tomcat.util.net.res.LocalStrings, locale en_US > at > java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java > (Compiled > Code)) > at > java.util.ResourceBundle.getBundleImpl(ResourceBundle.java(Compiled > Code)) > at java.util.ResourceBundle.getBundle(ResourceBundle.java:547) > at > org.apache.tomcat.util.res.StringManager.(StringManager.java:78) > at > org.apache.tomcat.util.res.StringManager.(StringManager.java:70) > at > org.apache.tomcat.util.res.StringManager.getManager(StringManager.java:249 > ) > at > org.apache.tomcat.util.net.PoolTcpEndpoint.(PoolTcpEndpoint.java:58) > at > org.apache.tomcat.modules.server.PoolTcpConnector.(PoolTcpConnector. > java:60) > at > org.apache.tomcat.modules.server.Http10Interceptor.(Http10Intercepto > r.java:68) > at java.lang.Class.newInstance0(Native Method) > at java.lang.Class.newInstance(Class.java:254) > at > org.apache.tomcat.util.xml.ObjectCreate.start(XmlMapper.java:797) > at > org.apache.tomcat.util.xml.XmlMapper.matchStart(XmlMapper.java:516) > at > org.apache.tomcat.util.xml.XmlMapper.startElement(XmlMapper.java:114) > at > org.apache.xerces.parsers.SAXParser.startElement(SAXParser.java(Compiled > Code)) > at > org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValid > ator.java(Compiled > Code)) > at > org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScan > ner.java(Compiled > Code)) > at > org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch( > XMLDocumentScanner.java(Compiled > Code)) > at > org.apache.xerces.framework.
Problems with tomcat 3.3.2 and IBM JRE 1.3.0
Hello list, I'm trying to use tomcat 3.3.2 with JDK 1.3.0. I'm developing an application in Linux/Windows, using SUN JDK 1.3.0 and tomcat 3.3.2 to test everything locally and everything is going fine. This application will run on an AIX 4, and in this machine the only JRE the sysadmins managed to install was IBM JRE 1.3.0: $ java -version java version "1.3.0" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0) Classic VM (build 1.3.0, J2RE 1.3.0 IBM build ca130-20010330 (JIT enabled: jitc)) I don't know why, but tomcat 3.3.2 doesn't starts in this machine. I need to run the tomcat in this machine, mainly because of internal problems here in the company I'm working to. The sysadmin installed tomcat 3.3.1a in this machine, which start's correctly. With this version, my application refuses to start in the AIX. In Linux with JDK 1.3.0, it start's correctly. I have two questions: 1 - Why jakarta-tomcat 3.3.2 doesn't start's with IBM jdk 1.3.0? Does anyone here managed to do that? 2 - Why my application doesn't start in jakarta-tomcat 3.3.1a in IBM jdk 1.3.0? 3 - Does anyone here uses AIX 4 and knows another VM than the one supplied by IBM for the AIX? AIX 4 is an old version and IBM does not supply JRE 1.4 neither 1.5 for this version. If anyone know how to use a newer version, please help me. :) The logs for both problems 1 and 2 are supplied below: For tomcat 3.3.2, here is the log (after this log, there is the log for my application starting in tomcat 3.3.1a): $ ./startup Using classpath: ./../lib/tomcat.jar:./../lib/common/commons-logging-api.jar Using JAVA_HOME: /usr/java130 Using TOMCAT_HOME: /home/aep022/jakarta-tomcat-3.3.2/ ERROR reading /home/aep022/jakarta-tomcat-3.3.2/conf/server.xml At Line 209 /Server/ContextManager/Http10Connector/ port=8080 secure=false maxThreads=100 maxSpareThreads=50 minSpareThreads=10 java.util.MissingResourceException: Can't find bundle for base name org.apache.tomcat.util.net.res.LocalStrings, locale en_US at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java(Compiled Code)) at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java(Compiled Code)) at java.util.ResourceBundle.getBundle(ResourceBundle.java:547) at org.apache.tomcat.util.res.StringManager.(StringManager.java:78) at org.apache.tomcat.util.res.StringManager.(StringManager.java:70) at org.apache.tomcat.util.res.StringManager.getManager(StringManager.java:249) at org.apache.tomcat.util.net.PoolTcpEndpoint.(PoolTcpEndpoint.java:58) at org.apache.tomcat.modules.server.PoolTcpConnector.(PoolTcpConnector.java:60) at org.apache.tomcat.modules.server.Http10Interceptor.(Http10Interceptor.java:68) at java.lang.Class.newInstance0(Native Method) at java.lang.Class.newInstance(Class.java:254) at org.apache.tomcat.util.xml.ObjectCreate.start(XmlMapper.java:797) at org.apache.tomcat.util.xml.XmlMapper.matchStart(XmlMapper.java:516) at org.apache.tomcat.util.xml.XmlMapper.startElement(XmlMapper.java:114) at org.apache.xerces.parsers.SAXParser.startElement(SAXParser.java(Compiled Code)) at org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValidator.java(Compiled Code)) at org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanner.java(Compiled Code)) at org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java(Compiled Code)) at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:380) at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:908) at org.apache.tomcat.util.xml.XmlMapper.readXml(XmlMapper.java:334) at org.apache.tomcat.modules.config.ServerXmlReader.loadConfigFile(ServerXmlReader.java:137) at org.apache.tomcat.modules.config.ServerXmlReader.addInterceptor(ServerXmlReader.java:113) at org.apache.tomcat.core.ContextManager.addInterceptor(ContextManager.java:393) at org.apache.tomcat.startup.EmbededTomcat.initContextManager(EmbededTomcat.java:613) at org.apache.tomcat.startup.EmbededTomcat.execute1(EmbededTomcat.java:791) at org.apache.tomcat.startup.EmbededTomcat$1.run(EmbededTomcat.java:775) at org.apache.tomcat.util.compat.Jdk12Support$PrivilegedProxy.run(Jdk12Support.java:166) at java.security.AccessController.doPrivileged(Native Method) at org.apache.tomcat.util.compat.Jdk12Support.doPrivileged(Jdk12Support.java:76) at org.apache.tomcat.startup.EmbededTomcat.execute(EmbededTomcat.java:773) at java.lang.reflect.Method.invoke(Native Method) at org.apache.tomcat.util.IntrospectionUtils.execute(IntrospectionUtils.java:52) at org.apache.tomcat.startup.Main.execute(Main.java:272) at org.apache.tomcat.startup.Main.main(Main.java:98) EmbededTomcat: exception initial
