On 11/21/2013 03:17 PM, Mark Thomas wrote:
You appear to be complaining about specification mandated behaviour. The
scan is required as soon as there is an SCI that declares an interest in
a class.
As far as I know we do not use any such thing.
We do use two ServletContextListener and from the
Hi!
I have tried to upgrade our system to more modern tomcat (from 7.0.28) to
7.0.47 and we also get the slow startup due to annotations processing.
In my case it makes tomcat startup go from 1 second to ~8 seconds and
for development that is annoying, even if it is not critical for
production
Hi!
I just started an upgrade of our tomcat, 7.0.47, to 7.0.52 and got into a
problem. Tomcat did not want to start our webapp. Looking in the log
I see:
Mar 26, 2014 2:10:42 PM org.apache.catalina.startup.ContextConfig
parseWebXml
SEVERE: Parse error in application web.xml file at
Hi!
On Tue, 2019-10-15 at 14:37 +0100, Mark Thomas wrote:
> Generally, no. You've done it in what I'd consider to be the "safer" way
> by exposing all the JARs visible to the client to the application's
> class loader rather than the other way around.
Ok, good to hear, we will try this and
Hi!
Some background:
We are currently running tomcat (9.0.26) and we serve data to
both html/webapp and to our java application. The java application
uses a lot of the same jar files that our servlets use.
We have had tomcat setup with two directories:
1) webapps//WEB-INF/lib (as usual for
On Wed, 2022-05-18 at 17:36 -0400, Christopher Schultz wrote:
> > > > > Is it possible to find out the per deployed context heap usage in
> > > > > tomcat?
> > > >
> > > > With a profiler you can look at the retained size of the web
> > > > application class loader instance associated with a
