[jboss-jira] [JBoss JIRA] (WFLY-3293) Excessive ERROR logging on JBAS014559: Invocation cannot proceed as component is shutting dow

[Thomas Frühbeck (JIRA)]

Thomas Frühbeck created WFLY-3293:
-------------------------------------

             Summary: Excessive ERROR logging on JBAS014559: Invocation cannot proceed as component is shutting dow
                 Key: WFLY-3293
                 URL: https://issues.jboss.org/browse/WFLY-3293
             Project: WildFly
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: EJB
    Affects Versions: 8.0.0.Final
            Reporter: Thomas Frühbeck
            Assignee: David Lloyd
            Priority: Minor


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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira