File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes JBoss/WildFly and the fly likes jboss-eap-6.1 - unable to see the System.out.println in console Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "jboss-eap-6.1 - unable to see the System.out.println in console" Watch "jboss-eap-6.1 - unable to see the System.out.println in console" New topic
Author

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

aman hindustani
Ranch Hand

Joined: Jun 15, 2006
Posts: 57
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.
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 9327
    
110

Are you packaging any logging libraries or logging configuration files in that application?

[My Blog] [JavaRanch Journal]
aman hindustani
Ranch Hand

Joined: Jun 15, 2006
Posts: 57
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
Marshal

Joined: Jul 20, 2005
Posts: 9327
    
110

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
Marshal

Joined: Jul 20, 2005
Posts: 9327
    
110

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

Joined: Jun 15, 2006
Posts: 57
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.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: jboss-eap-6.1 - unable to see the System.out.println in console
 
Similar Threads
404 error for a deployed EAR.
Monitoring Jboss
messages are not consuming in jboss 5.1.1 EAP
jmx remote
after migrate from 4.0.1 to 4.2.0, cannot load web.xml in .war/WEB-INF