Apologies, I should have explained.
This issue was caused by as pair of rogue System.out.println statements
which had been used for debugging. They were erroneously retained when the
code went live.
-----Original Message-----
From: cjderham@gmail.com [mailto:cjderham@gmail.com] On Behalf Of chris
derham
Sent: 06 Aug 2013 12 20
To: Tomcat Users List
Subject: Re: Why does JDBC application logging SQL instructions in Apache
Tomcat lists 545 repeatedly
On Tue, Aug 6, 2013 at 7:52 AM, Martin O'Shea <appy74@dsl.pipex.com> wrote:
> This is now resolved. Thanks anyway.
For the benefit of anybody else that hits this issue, care to explain how it
was resolved?
Thanks
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
|