[jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1507) Log the JNDI names of beans at INFO level

[Andrew Lee Rubinger (JIRA)]

     [ https://jira.jboss.org/jira/browse/EJBTHREE-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Lee Rubinger updated EJBTHREE-1507:
------------------------------------------

    Attachment: EJBTHREE-1507.patch


Attaching an example of INFO-level consolidated logging

> Log the JNDI names of beans at INFO level
> -----------------------------------------
>
>                 Key: EJBTHREE-1507
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1507
>             Project: EJB 3.0
>          Issue Type: Feature Request
>            Reporter: jaikiran pai
>            Assignee: Andrew Lee Rubinger
>         Attachments: EJBTHREE-1507.patch
>
>
> Currently, when a EJB3 bean is deployed, the Default local/remote business interface JNDI names are logged at DEBUG level and by default don't appear on the CONSOLE.
> This is what i see on the console:
> INFO  [JBossASKernel] Created KernelDeployment for: myapp_ejb3.jar
> INFO  [JBossASKernel] installing bean: jboss.j2ee:ear=ZEJB3Persistence.ear,jar=myapp_ejb3.jar,name=U
> serManagerBean,
> INFO  [JBossASKernel]   with dependencies:
> INFO  [JBossASKernel]   and demands:
> INFO  [JBossASKernel]      persistence.unit:unitName=ZEJB3Persistence.ear/myapp_ejb3.jar#EJB3Persist
> ence
> INFO  [JBossASKernel]      jboss.ejb:service=EJBTimerService
> INFO  [JBossASKernel]   and supplies:
> INFO  [JBossASKernel]      Class:org.myapp.ejb.UserManagerRemote
> INFO  [JBossASKernel]      jndi:ZEJB3Persistence/UserManagerBean/local-org.myapp.ejb.UserManagerLoca
> l
> INFO  [JBossASKernel]      Class:org.myapp.ejb.UserManagerLocal
> INFO  [JBossASKernel]      jndi:ZEJB3Persistence/UserManagerBean/local
> INFO  [JBossASKernel]      jndi:RemoteUserManagerBean
> INFO  [JBossASKernel]      jndi:ZEJB3Persistence/UserManagerBean/remote-org.myapp.ejb.UserManagerRem
> ote
> INFO  [JBossASKernel]      jndi:testMappedNameJai
> INFO  [JBossASKernel] Added bean(jboss.j2ee:ear=ZEJB3Persistence.ear,jar=myapp_ejb3.jar,name=UserMan
> agerBean,service
> .....
> INFO  [EJBContainer] STARTED EJB: org.myapp.ejb.impl.UserManagerBean ejbName: UserManagerBean
> .....
> And in the server.log, we have this useful information at DEBUG level:
> DEBUG [org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase] Default Remote Business View for
>  EJB UserManagerBean to be bound into JNDI at "RemoteUserManagerBean"
> DEBUG [org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase] Default Local Business View for 
> EJB UserManagerBean to be bound into JNDI at "LocalUserManagerBean"
> 	
> I have seen some posts in the User forum where the users found it hard to notice these messages in the server.log because of the other logs contained in that file.
> As a feature enhancement the jndi names could be logged at INFO level.

-- 
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