0

[7/11/19 10:34:41:786 EDT] 0000010b SystemOut O [2019-07-11 10:34:41,785] [WebContainer : 2] DEBUG loader.Loader (getRow:1533)- Result row:

This effectively slows down the deployment to > 30 minutes.

The application I am working in does not have a logging config and relies on WebSphere's Logs and Trace to control logging. I checked the log level at Troubleshooting > Logs and trace > server_name > Change log detail levels and it is set to *=info. No matter what log level is set here, SystemOut is going to print, as i believe it is not controlled by this configuration. New 20MB logs is created every 4 seconds or so.

There are no genericJvmArguments set. verboseModeClass is false. I compared server.xml of this server with another which doesn't output such SystemOut and the files look similar.

How do I troubleshoot this? What configuration could be causing this?

  • 1
    That looks to me like it's coming from custom/application code rather than WebSphere. – dbreaux Jul 11 at 16:21
  • The application I am working in does not have a logging config and relies on WebSphere's Logs and Trace to control logging. And there is the fact that the second server does not have this problem. – user2891264 Jul 11 at 20:00
  • I am just looking for the things I can try in the server that might help me understand or give a clue. – user2891264 Jul 11 at 20:03
  • "DEBUG" isn't a string that WebSphere writes. Nor that "loader.Loader..." details. I think some component in the application itself or deployed to the same WebSphere server is writing those entries. A quick search suggests maybe Hibernate? – dbreaux Jul 11 at 20:53
  • You are correct. Hibernate maven dependency tree adds jboss-logging:jar:3.3.1.Final as its dependency. The first log having this issue is also related to jboss [7/12/19 2:26:07:299 EDT] 00000095 SystemOut O [2019-07-12 02:26:07,289] [Default : 7] DEBUG jboss.logging (<clinit>:38)- Logging Provider: org.jboss.logging.Log4jLoggerProvider I expected that if my project does not have a logging configuration, WebSphere Admin logging config will take over. Has the JBoss logging taken over control of logging? – user2891264 Jul 12 at 14:07

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.