Wildfly extremely slow with Console logging

[isa154]

Hi All

We have been migrating our JBoss4.2.3 environment to Wildfly and found wildfly to be much slower. This slowness did not improve as we upgraded from WF Alpha/Beta/CR and Final. After a lot of troubleshooting we have found that console logging as causing the issue. If I remove the <handler name="CONSOLE"/> we saw immediate improvements and our response was faster that jboss.4.2.3 in most cases.

Any idea why this is happening ? I would really like to have console logging since it is easy to check for errors on start up.

[spolti]

wich is the java version?

How is defined your log level?

You can see any error in the log?

[wdfink]

Console logging might be slow.

Did you change the logging and see more with AS7 then with AS4?

I recommend to use the console logging only for development and remove it complete in production.

[jamezp]

Are you logging a lot of messages? If you're strict on using loggers/categories in your application you could always set your base category to use-parent-handlers=false and add the FILE handler to the logger. This would stop log messages from your application being logged to the console.

--

James R. Perkins

[isa154]

java version "1.7.0_25"

Log Level: Info

No errors

Also one strange thing is if console logging is on is and I exit the terminal session. Than WF gets even slower a web services call  that will take 2sec will now take 20sec.

[jamezp]

If you're doing something like $JBOSS_HOME/bin/standalone.sh then exit the terminal WildFly should terminate. The only way console logging is going to slow things down is if your application is logging a lot of messages.

--

James R. Perkins