4 Replies Latest reply on May 27, 2010 9:24 AM by jaikiran

    Warnings when undeploying EJB 3.

    gcollin

      Hi,

       

      We have an Enterprise Application (.ear) with Seam-enabled EJB3 beans in JBoss 4.2.3

       

      When I exit JBoss or undeploy the application, I see warnings:

       

      2010-05-27 12:09:13,674 WARN  [org.jboss.ejb3.JmxKernelAbstraction] jboss.j2ee:ear=amanda2.ear,jar=business-1.9.1.jar,name=CoverageReferenceDao,service=EJB3 is not registered
      2010-05-27 12:09:13,674 WARN  [org.jboss.ejb3.JmxKernelAbstraction] jboss.j2ee:ear=amanda2.ear,jar=business-1.9.1.jar,name=CoverageReferenceTypeDao,service=EJB3 is not registered

      ....

       

      This goes one for all beans.

       

      Does someone please know what this means ?

      The logs would be cleaner without these messages, how can I get rid of them (without removing all the potential warnings from JmxKernelAbstraction) ?

       

      Thanks,

       

      GC.

        • 1. Re: Warnings when undeploying EJB 3.
          jaikiran

          Looking at the nature of those logs, I guess you can ignore those. By the way, I would recommend you upgrade to 5.1.0 of AS, since 4.2.3 doesn't have a EJB3 compliant implementation.

          • 2. Re: Warnings when undeploying EJB 3.
            gcollin

            Thanks for the answer.

             

            I knew I can ignore these messages, at least because I'm exiting JBoss.

            I've seen that lots of other people are quietly ignoring these messages too.

             

            I just wanted to know if we can get rid of them, since they seem to be useless. Don't they ?

             

            Regards,

             

            GC.

            • 3. Re: Warnings when undeploying EJB 3.
              gcollin

              As for the JBoss 5.1 suggestions, sadly I'm not the one who decides this....

              Otherwise we'll use 6.0rc !

               

              GC.

              • 4. Re: Warnings when undeploying EJB 3.
                jaikiran

                Gerard COLLIN wrote:

                 


                I just wanted to know if we can get rid of them, since they seem to be useless. Don't they ?

                 


                You could set the log level of org.jboss.ejb3.JmxKernelAbstraction to ERROR in the jboss-log4j.xml file. But that would also mean that you would lose any other lesser level log statements from that class.