Based on your stack trace and the fact that Bamboo had the problem, I'd say its not specifically related to Inspektr. At the moment, I don't know the exact cause though :-) Looks like a classpath issue with logging or something though.
On Tue, Apr 6, 2010 at 4:21 PM, Patrick Berry <[email protected]> wrote: > > > On Tue, Apr 6, 2010 at 12:59 PM, Patrick Berry <[email protected]> wrote: > >> >> >> On Tue, Apr 6, 2010 at 11:43 AM, Scott Battaglia < >> [email protected]> wrote: >> >>> Are you putting your pooling jar in Tomcat's common, or with the >>> application? >>> >>> >> With the application via a maven dependency, in both the dbcp and c3p0 >> cases. I'll try breaking them out and running through it again. >> >> >> > Afraid that didn't do anything. Do you think this might be an Inspecktr > bug? It seems to pop-up regardless of pooling or databases. > > Pat > > -- > You are currently subscribed to [email protected] as: > [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
