2018-03-06 18:43 GMT+03:00 Christopher Schultz :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> All,
>
> I think I already know the answer to this question, but I'm going to
> ask anyway in case it helps others understand what's going on.
>
> I have a custom MBean for a loadable-object in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Akhilesh,
On 3/6/18 7:31 AM, Akhilesh ET wrote:
> We are facing a situation wherein one of our production servers
> running tomcat 6.0.18 is unable to generate logs after service
> startup. Logging just stops after service start up.
Maybe it's dyi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ken,
On 3/6/18 9:09 AM, Kenneth Taylor wrote:
> More troubleshooting revealed that our root context xml had been
> copied from another installation and had a wrong path in it.
Do I smell another Darwin Award nomination?
> However, I don’t think th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I think I already know the answer to this question, but I'm going to
ask anyway in case it helps others understand what's going on.
I have a custom MBean for a loadable-object in my web application.
This is an object that lives in the applicat
Kenneth,
On 06.03.2018 15:09, Kenneth Taylor wrote:
More troubleshooting revealed that our root context xml had been
copied from another installation and had a wrong path in it. However,
I don’t think this was the problem since it was only a path to a Log4J
config. We re-installed Tomcat
Kenneth,
As MarkT suggested earlier, there is no such "Cache". If you are using
Tag/Cotext Pooling - it's a separate issue and you need to check tomcat's
documentation to check what options you need/don't need.
"The “-XX:+DisableAttachMechanism” JVM option does not work with Tomcat" -
what do you
More troubleshooting revealed that our root context xml had been copied from
another installation and had a wrong path in it. However, I don't think this
was the problem since it was only a path to a Log4J config. We re-installed
Tomcat from scratch and it seems to have resolved it, but this
Hi Thomas,
Thanks for the reply.
Yes we have checked that it is fine. Also the same server with the same
configuration and permissions is working fine if we change the IP address.
Thanks & Regards
Akhilesh.E.T
ITC Infotech India Ltd.,
ITC Infotech Park, #18 Banaswadi Main Road, Bangalore - 560
Hi Akhilesh,
have you checked your file system permissions? Has the Tomcat runtime user the
permissions to write into the log directory?
Regards,
Thomas
BTW: Tomcat 6 ist end of life since 31 December 2016
(https://tomcat.apache.org/tomcat-60-eol.html). Please consider upgrading to
Tom
Hi All,
We are facing a situation wherein one of our production servers running tomcat
6.0.18 is unable to generate logs after service startup. Logging just stops
after service start up.
[cid:image001.png@01D3B575.098BBBF0]
The setup is such a way that the control flows from a Apache Webserver
On 06/03/18 09:19, Clemens Wyss DEV wrote:
>> you;d expect such threads to be started and stopped by a
>> ServletContextListener
> I guess the ServletContextListener is being called/executed from/by another
> thread than the startStop-thread (and hence has another classloader)?
It will be loaded
We are migrating from 6.0.48 to 7.0.82 , after updating the libraries we
are hitting the below issue
java.lang.NullPointerException
at
org.apache.catalina.core.ApplicationContext.populateSessionTrackingModes(ApplicationContext.java:1263)
at
org.apache.catalina.core.ApplicationCont
>you;d expect such threads to be started and stopped by a ServletContextListener
I guess the ServletContextListener is being called/executed from/by another
thread than the startStop-thread (and hence has another classloader)?
-Ursprüngliche Nachricht-
Von: Clemens Wyss DEV
Gesendet: Di
13 matches
Mail list logo
