7 Replies Latest reply on Oct 30, 2008 11:46 AM by Kamil Demecki

    Logging JNDI names of beans at INFO level

    jaikiran pai Master

      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=UserManagerBean,
      INFO [JBossASKernel] with dependencies:
      INFO [JBossASKernel] and demands:
      INFO [JBossASKernel] persistence.unit:unitName=ZEJB3Persistence.ear/myapp_ejb3.jar#EJB3Persistence
      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.UserManagerLocal
      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.UserManagerRemote
      INFO [JBossASKernel] jndi:testMappedNameJai
      INFO [JBossASKernel] Added bean(jboss.j2ee:ear=ZEJB3Persistence.ear,jar=myapp_ejb3.jar,name=UserManagerBean,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.

      Is it OK to change the logging level of these JNDI binding message for the default business interfaces to INFO level?