-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Jeff,
Aha. There is a "SEVERE .. [/supportcentral] startup failed due to
previous errors". If no errors are showing in catalina.out, check the
other log files like perhaps locahost-*.log in your logs directory.
At some point, the web application is failing to start (probably
because of a SecurityManager thing!) and this ungraceful shutdown is
just a symptom. You should definitely fix the symptom, too, but the
real cause of the failed startup should be in one of those log files.
- -chris
> 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.xm
l
>>>>
>>>>
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.checkStateForResou
rce
>
>>>>
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.checkStateForResou
rce
>
>>>>
Loading(WebappClassLoaderBase.java:1327)
>>>>
>>>>
> at
>>>> org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClass
Loa
>
>>>>
ding(WebappClassLoaderBase.java:1313)
>>>>
>>>>
> at
>>>> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappCl
ass
>
>>>>
LoaderBase.java:1196)
>>>>
>>>>
> at
>>>> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappCl
ass
>
>>>>
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
>>
>> ---------------------------------------------------------------------
>>
>>
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
>
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl0Vd5EACgkQHPApP6U8
pFisuw/+OK7EX9uniJSGwF96lbWES0RIDB9x+UBbXl/UwvxkYPUwooR7YqXmbp2E
ohdjaC0oYV79/ZwgwsbaSMdHs99XxxEOWmD0RcFaggzQNGXCKqV1ZSUluGL++Bsa
XFiCR4rFJYh0geimd/PG4MUE9mDYcfLmAN/0jpmMEK+itVIeDOWgB7mglMRX2Ix3
o17Sefy1Wtjd8JxzCi3L+vXgQgY5TM1kV8xMdctUzncR9JFN4QEH+geiBz6utMdz
oO3dx27FC7L57uCe289hJKlXeNa7vNksFzFsrg8eXDIj9uXNEROvB2qP0/SzLZVl
LUufBLlIM/8/yKVcSLBdAS+ZxT17gP5EYIzCZh/KlRu3QPPO0hj4r6g92FIUQMOs
W2HilTpqbGAnitTwI/FCqdYCVgWP473Yi7UgWg0FIyMp2mMtJxzwAGCwkbIKi+Cn
QFWI6naAHr2i6rGedJezrZFOwfcrrdbFPc0y1MZMpfSnse2nhE+0I4dfO0HGJwPT
aR88mOvpNW6vL+g1B5ipyAmyUh3UWFhUnP0wHoEq1ngvbt/mBHay1h8CWwzev4eT
pV6ZObgh/mvbf+Ov+Y4PL1cXzNRZZkThBQBLv1SYKs2s7C+ktN9di+xqxksJ+VKU
QfcqWoerrt2CVvfSjKs38V8F/yNiIioyoybZkp5wEP8idFe7bcA=
=cwon
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
