]
Kevin Conner reopened JBESB-2034:
---------------------------------
The error messages should be at the correct level, do we know why this is happening?
Seeing ERROR level log mesages for listener state transitions
-------------------------------------------------------------
Key: JBESB-2034
URL:
https://jira.jboss.org/jira/browse/JBESB-2034
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Management
Affects Versions: 4.2.1 CP2
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: 4.4 CP1
From Len, via JBMANCON-411 :
Testing the embedded console with the SPA-P 4.3 IR4 helloworld quickstart - seeing ERROR
level log messages that don't seem to have an operational impact - are these messages
just at the wrong logging level?
Also - all state transitions generate this type of error:
12:17:04,867 ERROR [OperationInvocation] Plugin error: Operation [start] is defined as
returning no results, but it returned non-null results: Configuration[id=0]
------------------------
Test = trying to start a stopped listener.
Steps - deploy the quickstart, navigate to this listener:
Listener used (hirearchy displayed in console):
* : (server name)
* : JBossAS Server
* : (servername) JBossSOA SOA_4.3.0.GA_IR4 default (1099)
* : JBoss ESB Deployment
* : Quickstart_helloworld.esb JBoss ESB statistics
* : JBoss ESB Services
* : SimpleListener JBoss ESB statistics
* : JBoss ESB Listeners
* : FirstServiceESB Listener
Stop the listener, then start it.
12:17:04,264 ERROR [LifecycleController]
org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Tasks remain active in
executor
at
org.jboss.soa.esb.listeners.message.MessageAwareListener.checkExecutorTermination(MessageAwareListener.java:403)
at
org.jboss.soa.esb.listeners.message.MessageAwareListener.doStart(MessageAwareListener.java:225)
at
org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.start(AbstractManagedLifecycle.java:169)
at
org.jboss.soa.esb.listeners.lifecycle.LifecycleController.start(LifecycleController.java:143)
at
org.jboss.soa.esb.listeners.lifecycle.LifecycleController.invoke(LifecycleController.java:319)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at
org.mc4j.ems.impl.jmx.connection.bean.operation.DOperation.invoke(DOperation.java:109)
at
org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:424)
at
org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:399)
at sun.reflect.GeneratedMethodAccessor720.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:446)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
12:17:04,867 ERROR [OperationInvocation] Plugin error: Operation [start] is defined as
returning no results, but it returned non-null results: Configuration[id=0]
Starting a running listener:
12:39:43,386 ERROR [LifecycleController]
org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Invalid state change
from RUNNING to STARTING
at
org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.changeState(AbstractManagedLifecycle.java:306)
at
org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.start(AbstractManagedLifecycle.java:166)
at
org.jboss.soa.esb.listeners.lifecycle.LifecycleController.start(LifecycleController.java:143)
at
org.jboss.soa.esb.listeners.lifecycle.LifecycleController.invoke(LifecycleController.java:319)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at
org.mc4j.ems.impl.jmx.connection.bean.operation.DOperation.invoke(DOperation.java:109)
at
org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:424)
at
org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:399)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:446)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Initializing a running listener:
12:40:03,839 ERROR [LifecycleController]
org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Invalid state change
from RUNNING to INITIALISING
at
org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.changeState(AbstractManagedLifecycle.java:306)
at
org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.initialise(AbstractManagedLifecycle.java:130)
at
org.jboss.soa.esb.listeners.lifecycle.LifecycleController.initialise(LifecycleController.java:136)
at
org.jboss.soa.esb.listeners.lifecycle.LifecycleController.invoke(LifecycleController.java:327)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at
org.mc4j.ems.impl.jmx.connection.bean.operation.DOperation.invoke(DOperation.java:109)
at
org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:424)
at
org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:399)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:446)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
12:40:03,840 ERROR [OperationInvocation] Plugin error: Operation [initialise] is defined
as returning no results, but it returned non-null results: Configuration[id=0]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: