[jboss-jira] [JBoss JIRA] Commented: (JBAS-7640) Verbose logging when an EJB3 deployment is created
[
https://jira.jboss.org/jira/browse/JBAS-7640?page=com.atlassian.jira.plug...
]
David Lloyd commented on JBAS-7640:
-----------------------------------
No, it's not low-volume. That's like 25 lines for ONE very simple EJB deployment.
If you want to have one single INFO line which summarizes the deployment, like
"Deployed EJB module 'admin-console.war' with 2 EJBs" or something to
that effect, that would be fine, with the rest of that crap at DEBUG. Also, a multi-part
message like this should NOT be split among several log messages because in the presence
of multiple threads, this will be very hard to read.
Verbose logging when an EJB3 deployment is created
--------------------------------------------------
Key: JBAS-7640
URL: https://jira.jboss.org/jira/browse/JBAS-7640
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB3
Affects Versions: JBossAS-6.0.0.M1
Reporter: David Lloyd
Assignee: Carlo de Wolf
Fix For: JBossAS-6.0.0.M3
This output could/should be logged at DEBUG or lower according to
http://community.jboss.org/wiki/UsageOfLoggingLevels
15:52:30,086 INFO [JBossASKernel] Created KernelDeployment for: admin-console.war
15:52:30,090 INFO [JBossASKernel] installing bean:
jboss.j2ee:jar=admin-console.war,name=TimerServiceDispatcher,service=EJB3
15:52:30,090 INFO [JBossASKernel] with dependencies:
15:52:30,090 INFO [JBossASKernel] and demands:
15:52:30,090 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService; Required:
Described
15:52:30,090 INFO [JBossASKernel] and supplies:
15:52:30,090 INFO [JBossASKernel]
Class:org.jboss.seam.async.LocalTimerServiceDispatcher
15:52:30,090 INFO [JBossASKernel] jndi:TimerServiceDispatcher
15:52:30,090 INFO [JBossASKernel]
jndi:TimerServiceDispatcher/local-org.jboss.seam.async.LocalTimerServiceDispatcher
15:52:30,090 INFO [JBossASKernel] jndi:TimerServiceDispatcher/local
15:52:30,090 INFO [JBossASKernel] Added
bean(jboss.j2ee:jar=admin-console.war,name=TimerServiceDispatcher,service=EJB3) to
KernelDeployment of: admin-console.war
15:52:30,092 INFO [JBossASKernel] installing bean:
jboss.j2ee:jar=admin-console.war,name=EjbSynchronizations,service=EJB3
15:52:30,092 INFO [JBossASKernel] with dependencies:
15:52:30,092 INFO [JBossASKernel] and demands:
15:52:30,092 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService; Required:
Described
15:52:30,092 INFO [JBossASKernel] and supplies:
15:52:30,092 INFO [JBossASKernel] jndi:EjbSynchronizations
15:52:30,092 INFO [JBossASKernel] jndi:EjbSynchronizations/local
15:52:30,092 INFO [JBossASKernel]
jndi:EjbSynchronizations/local-org.jboss.seam.transaction.LocalEjbSynchronizations
15:52:30,092 INFO [JBossASKernel]
Class:org.jboss.seam.transaction.LocalEjbSynchronizations
15:52:30,092 INFO [JBossASKernel] Added
bean(jboss.j2ee:jar=admin-console.war,name=EjbSynchronizations,service=EJB3) to
KernelDeployment of: admin-console.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira