Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-3293

Excessive ERROR logging on JBAS014559: Invocation cannot proceed as component is shutting dow

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Minor
    • 9.0.0.Final
    • 8.0.0.Final
    • EJB
    • None

    Description

      on server shutdown excessive ERROR logs are produced related to EJB invocations on beans in state shutdown.

      2014-04-26 09:38:43,059 ERROR [org.jboss.as.ejb3.invocation] (ServerService Thread Pool – 377) JBAS014134: EJB Invocation failed on component SMSQueueConsumer for method public void at.telekom.sms.esms.service.
      common.queue.SMSQueueConsumer.stopping(): org.jboss.as.ejb3.component.EJBComponentUnavailableException: JBAS014559: Invocation cannot proceed as component is shutting down
      at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:59) [wildfly-ejb3-8.0.0.Final.jar:8.0.0.Final]
      at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)

      IMHO this is definitely no error and is very alarming for production environments, INFO w/o stacktrace, in level DEBUG full stacktrace would suffice.

      Attachments

        Activity

          People

            dlloyd@redhat.com David Lloyd
            fruehbeck@aon.at Thomas Fr├╝hbeck (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: