• 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

jboss-eap-6.1 - unable to see the System.out.println in console

 
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi ,

we had deployed one of the working war file from tomcat 6.x to jboss-eap-6.1 . The whole application is working fine.
but we are unable to see the System.out.println statements on the console.

we have deployed another simple war file with single servlet with system.out.println statement. this application is showing the system.out.println on console.

please help us how to handle this.

regards,
Aman.
 
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 packaging any logging libraries or logging configuration files in that application?
 
aman hindustani
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
yes, we are using logging in the application.
commons-logging-1.0.4.jar
log4j-1.2.14.jar
and other supporting jar files.

 
Jaikiran Pai
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
Is it just the jars or do you even have a logging configuration file (like log4j.xml or log4j.properties or logging.properties) within that application? It does look like the presence of these logging libraries might be causing this (sigh!).
 
Jaikiran Pai
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
By the way, just a note - in production logging to console isn't really a good idea. So even if you end up fixing the issue, you might still want to just keep logging to log files instead of the console.
 
aman hindustani
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
we are using log4j.properties to store error logs into the file. A part from that System.out.println are also used for initial level of debugging.
 
reply
    Bookmark Topic Watch Topic
  • New Topic