On 15/08/2012 22:48, llow...@oreillyauto.com wrote:
> Mark Thomas wrote on 08/15/2012 03:48:04 PM:
>
On 15/08/2012 21:13, llow...@oreillyauto.com wrote:
> The understanding of the actual developer was that the jars would
>>> already
> be loaded by the JVM and shouldn't need to be re-
Mark Thomas wrote on 08/15/2012 03:48:04 PM:
> >> On 15/08/2012 21:13, llow...@oreillyauto.com wrote:
> >>> The understanding of the actual developer was that the jars would
> > already
> >>> be loaded by the JVM and shouldn't need to be re-opened.
> >>
> >> That understanding is no longer correc
On 15/08/2012 21:44, llow...@oreillyauto.com wrote:
> Mark Thomas wrote on 08/15/2012 03:22:07 PM:
>
>> From: Mark Thomas
>> To: Tomcat Users List
>> Date: 08/15/2012 03:29 PM
>> Subject: Re: Questions about walking the class path
>>
>> On 15/08
Mark Thomas wrote on 08/15/2012 03:22:07 PM:
> From: Mark Thomas
> To: Tomcat Users List
> Date: 08/15/2012 03:29 PM
> Subject: Re: Questions about walking the class path
>
> On 15/08/2012 21:13, llow...@oreillyauto.com wrote:
> > The understanding of the actual dev
On 15/08/2012 21:13, llow...@oreillyauto.com wrote:
> The understanding of the actual developer was that the jars would already
> be loaded by the JVM and shouldn't need to be re-opened.
That understanding is no longer correct. See:
http://svn.apache.org/viewvc?view=revision&revision=1343708
I a
All,
I've ran into a bug with a 3rd party app I use to monitor my tomcat server.
What is happening is that when I go to the log tab to view a list of
available logs the open file handlers spike, hitting ulimit on my
production and test servers, which causes breakage.
The app in question uses th
