On Fri, Sep 5, 2014 at 12:57 AM, Konstantin Kolinko
wrote:
> 2014-09-04 19:55 GMT+04:00 Martin Knoblauch :
> >
> > It seems it happens between 7.0.42 and 7.0.47. I would "bisect", but
> cannot
> > find any tarballs between those two releases.
> >
>
> Those versions have been votes as broken and n
2014-09-04 19:55 GMT+04:00 Martin Knoblauch :
>
> It seems it happens between 7.0.42 and 7.0.47. I would "bisect", but cannot
> find any tarballs between those two releases.
>
Those versions have been votes as broken and not released.
>> > 2) How can one find out which jars are "problematic"
>>
>
On Thu, Sep 4, 2014 at 4:58 PM, Mark Thomas wrote:
> On 04/09/2014 15:38, Martin Knoblauch wrote:
> > Hi,
> >
> > I am using JDK 1.7.0_67 and Tomcat 7.0.55. At application startup I am
> > seeing a bunch of below messages flying by. The messages have not been
> > observed with Tomcat 7.042. The
On 04/09/2014 15:38, Martin Knoblauch wrote:
> Hi,
>
> I am using JDK 1.7.0_67 and Tomcat 7.0.55. At application startup I am
> seeing a bunch of below messages flying by. The messages have not been
> observed with Tomcat 7.042. There are exactly 135 of them, which is the sum
> of the jars in $C
Hi,
I am using JDK 1.7.0_67 and Tomcat 7.0.55. At application startup I am
seeing a bunch of below messages flying by. The messages have not been
observed with Tomcat 7.042. There are exactly 135 of them, which is the sum
of the jars in $CATALINA_HOME/lib and my applications WEB-INF/lib.
Two qu
