• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Why does JDBC application logging SQL instructions in Apache Tomcat list 545 repeatedly

 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm currently running a number of programs in batch which dynamically create and populate a number of tables in MySQL Server Version 5.5.

When I do this, I am logging the SQL to an Apache Tomcat log file. Sometimes the SQL listings
will list a particular series of queries reading the <title> elements of RSS feeds one by one such as:



Then the name of the system will be printed as follows in the log file:



And then there will be a series of lines reading:



Before the next series of queries run. And when the next series of queries does run, the text of each query is listed, and then another line lists the system name.



MyApp is written in Java and running under Tomcat 6.0.26. I should add that sometimes the number of queries producing the data for one table, which may number in the hundreds, appear to be fine. Other times the 545 message is listed: this appears to be sporadic with no apparent pattern.

Though the queries appear to be running, can anyone tell me what 545 might mean? It seems to happen on two separate servers running the same programs but over different data.

Thanks.
 
Sheriff
Posts: 10445
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Are you sure it's not something that the application code itself is printing out (perhaps hardcoded or some such thing)? What exactly do those entire lines of logs look like?
 
Martin Oshea
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The problem has been traced to a pair of 'rogue' System.out.println(...) statements, which had been used for debugging, and which were erroneously retained when the relevant classes were deployed live.

Thanks to Jaikiran Pai .
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic