tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff <mojo...@gmail.com>
Subject Re: Unable to start tomcat with Security Manager
Date Thu, 27 Jun 2019 14:17:04 GMT
Thanks Chris.  How can I determine what is causing it to stop?  Within
seconds of starting it fails "due to previous errors" but the only thing
mentioned before is regarding  "Deploying configuration descriptor" which I
didn't think it would cause tomcat not to start.  Both manager.xml and
host-manager.xml exist but only contain the following:

<Context antiResourceLocking="false" privileged="true" >
  <!--
    Remove the comment markers from around the Valve below to limit access
to
    the manager application to clients connecting from localhost
  -->
  <!--
  <Valve className="org.apache.catalina.valves.RemoteAddrValve"
         allow="127\.\d+\.\d+\.\d+|::1|0:0:0:0:0:0:0:1" />
  -->
</Context>



On Thu, Jun 27, 2019 at 9:55 AM Christopher Schultz <
chris@christopherschultz.net> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Jeff,
>
> On 6/27/19 09:24, Jeff wrote:
> > Hello all,
> >
> > Hit a roadblock trying to start tomcat with Security Manager and
> > don't even know where to start looking.  Any help would be
> > appreciated.
> >
> > catalina.out: 27-Jun-2019 06:01:57.627 INFO [main]
> > org.apache.catalina.core.StandardEngine.startInternal Starting
> > Servlet Engine: Apache Tomcat/8.0.17 27-Jun-2019 06:01:57.646 INFO
> > [localhost-startStop-1]
> > org.apache.catalina.startup.HostConfig.deployDescriptor Deploying
> > configuration descriptor /apps/supp/server/tomcat/apache-tomca
> > t-8.0.17-SupportCentral/conf/Catalina/localhost/host-manager.xml
> > 27-Jun-2019 06:01:58.060 INFO [localhost-startStop-1]
> > org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was
> > scanned for TLDs yet contained no TLDs. Enable debug logging for
> > this logger for a complete list of JARs that were scanned but no
> > TLDs were found in them. Skipping unneeded JARs during scanning can
> > improve startup time and JSP compilation time. 27-Jun-2019
> > 06:01:58.167 INFO [localhost-startStop-1]
> > org.apache.catalina.startup.HostConfig.deployDescriptor Deployment
> > of configuration descriptor /apps/supp/server/tomcat/apache-t
> > omcat-8.0.17-SupportCentral/conf/Catalina/localhost/host-manager.xml
> > has finished in 521 ms 27-Jun-2019 06:01:58.167 INFO
> > [localhost-startStop-1]
> > org.apache.catalina.startup.HostConfig.deployDescriptor Deploying
> > configuration descriptor /apps/supp/server/tomcat/apache-tomca
> > t-8.0.17-SupportCentral/conf/Catalina/localhost/manager.xml
> > 27-Jun-2019 06:01:58.233 INFO [localhost-startStop-1]
> > org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was
> > scanned for TLDs yet contained no TLDs. Enable debug logging for
> > this logger for a complete list of JARs that were scanned but no
> > TLDs were found in them. Skipping unneeded JARs during scanning can
> > improve startup time and JSP compilation time. 27-Jun-2019
> > 06:01:58.238 INFO [localhost-startStop-1]
> > org.apache.catalina.startup.HostConfig.deployDescriptor Deployment
> > of configuration descriptor /apps/supp/server/tomcat/apache-t
> > omcat-8.0.17-SupportCentral/conf/Catalina/localhost/manager.xml
> > has finished in 71 ms 27-Jun-2019 06:01:58.243 INFO
> > [localhost-startStop-1]
> > org.apache.catalina.startup.HostConfig.deployWAR Deploying web
> > application archive /apps/supp/server/tomcat/apache-tomcat-8.0.17
> > -SupportCentral/webapps/supportcentral.war 27-Jun-2019 06:02:07.797
> > SEVERE [localhost-startStop-1]
> > org.apache.catalina.core.StandardContext.startInternal Error
> > listenerStart 27-Jun-2019 06:02:07.833 SEVERE
> > [localhost-startStop-1]
> > org.apache.catalina.core.StandardContext.startInternal Context
> > [/supportcentral] startup failed due to previous errors 27-Jun-2019
> > 06:02:07.854 INFO [localhost-startStop-1]
> > org.apache.catalina.startup.HostConfig.deployWAR Deployment of web
> > application archive /apps/supp/server/tomcat/apache-tomcat-8.
> > 0.17-SupportCentral/webapps/supportcentral.war has finished in
> > 9,611 ms
> >
> >
> > Further down in the logs I see:
> >
> > 27-Jun-2019 06:07:00.125 INFO [AD Thread Pool-Global0]
> > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResource
> Loading
> >
> >
> Illegal access: this web application instance has be
> > en stopped already. Could not load [org.slf4j.Marker]. The
> > following stack trace is thrown for debugging purposes as well as
> > to attempt to terminate the thread which caused the illegal
> > access. java.lang.IllegalStateException: Illegal access: this web
> > application instance has been stopped already. Could not load
> > [org.slf4j.Marker]. The following stack trace is thrown for debu
> > gging purposes as well as to attempt to terminate the thread which
> > caused the illegal access. at
> > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResource
> Loading(WebappClassLoaderBase.java:1327)
> >
> >
> at
> > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoa
> ding(WebappClassLoaderBase.java:1313)
> >
> >
> at
> > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClass
> LoaderBase.java:1196)
> >
> >
> at
> > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClass
> LoaderBase.java:1157)
> >
> >
> at java.lang.Class.getDeclaredMethods0(Native Method)
> > at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) at
> > java.lang.Class.getDeclaredMethods(Class.java:1975) at
> > com.singularity.ee.agent.appagent.services.o.a(o.java:445) at
> > com.singularity.ee.agent.appagent.services.o.a(o.java:94) at
> > com.singularity.ee.agent.appagent.services.F.a(F.java:847) at
> > com.singularity.ee.agent.appagent.services.F.run(F.java:736) at
> > com.singularity.ee.util.javaspecific.scheduler.n.run(n.java:122)
> > at
> > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511
> )
> >
> >
> at com.singularity.ee.util.javaspecific.scheduler.z.e(z.java:335)
> > at com.singularity.ee.util.javaspecific.scheduler.a.b(a.java:152)
> > at com.singularity.ee.util.javaspecific.scheduler.b.a(b.java:119)
> > at com.singularity.ee.util.javaspecific.scheduler.b.b(b.java:206)
> > at
> > com.singularity.ee.util.javaspecific.scheduler.b.run(b.java:236) at
> > com.singularity.ee.util.javaspecific.scheduler.i.a(i.java:694) at
> > com.singularity.ee.util.javaspecific.scheduler.i.run(i.java:726) at
> > java.lang.Thread.run(Thread.java:745)
> >
> > catalina.policy grant codeBase
> > "file:${catalina.base}/webapps/supportcentral.war*/-" { //
> > permission java.io.FilePermission
> > "file:${catalina.base}/webapps/supportcentral/-", "read, write";
> > permission java.security.AllPermission; permission
> > java.io.FilePermission "*","read,write,execute"; permission
> > java.lang.RuntimePermission "setContextClassLoader"; }; grant
> > codeBase "file:/apps/appdynamics/-" { permission
> > java.security.AllPermission; permission java.io.FilePermission
> > "*","read,write,execute"; permission java.lang.RuntimePermission
> > "setContextClassLoader"; };
> >
> > TIA
>
> This is actually a problem stopping the web application, not starting
> it, and it doesn't look to be Security-Manager-related to me.
>
> After the web application has been stopped, the ClassLoader which
> handles all of the class loading for that instance/deployment of the
> webapp is marked as "stopped", and will refuse to load any more classes.
>
> The error you are seeing above is mostly likely caused by something
> the application is trying to do *after* it has shut down, most likely
> by a thread started by the application and not stopped.
>
> It's clear that it's some kind of scheduled job, which fits that
> analysis. Perhaps you are not properly shutting-down your in-memory
> scheduler as the application is being taken down?
>
> Check to make sure that you have a ServletContextListener for things
> like this, so you can stop any "services" like a task-scheduler that
> your application starts as it is coming-down.
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
>
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl0UytIACgkQHPApP6U8
> pFjIzg/9EviJZrkj/mb5M8/aHtewYKdqrsBWqYpkdemnNQwK9SvACM8ajLmgBtVu
> VR16SOHSF9zeAkEMlaZef603p/Ustdp9nfk2aYzRT+wd9n64gD/BLnAsoMlRULOj
> gtz5R4b6Fs+TyRt3v2XpGmYRRH+AM1qLGoY2VXOwjMxYtaHx8YPywXej/2p5rFQy
> SFlmfsVYmWYB++OWbEoIICjv4uZLDomp32kcrLf3aNdGYjWQbm66kDBA4kUCJdjA
> 1N/Uf+chD23f2J7jhiRyoi3/qTiBJDFtqL6eg+XOlkCGnUwsDtojH5NqcioqsugS
> 1C+Btqq6KOD4JSSdqiZPahazE2oZY6ZuEdunVSFgd02mf6Mtuzds9O6zYfJ5nhaP
> i/SBZK74kvG+NodxitXgiw3fgjL2uWb4Z/sMLCglDbYZ5wLzBYOnWYF+Txjr5PRK
> 3BoawPJloJTcmwune8vmlhq2xMAxhOLP91n/W3GnCX89wUCr3dPvPcMM8EZx4mqM
> bkj07ssQgt2XRgzOaBI87AuQMph/eqESNmH8c1+uIZEmIM9WY6wIdZY0tY4+duCI
> skOSOurQ4d1pXT4QUkMwL/FOx6V1ZQte6Ay2XOi24ECJedbWF+24wtEPW7fMTiyq
> JUbTogLnsiMchdfbLgWPkvlluSYwFPnc9M/fCXcb9goBVjLSrlg=
> =Q59G
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message