Hide Forgot
project_key: SOA When running the "Reset the message counter" operation at the Service level I get this error in the jon server log: 2009-09-16 12:25:56,986 ERROR [OperationManager.invoker-1] (rhq.core.pc.operation.OperationInvocation)- Plugin error: Operation [resetCounter] is defined as returning no results, but it returned non-null results: Configuration[id=0, operationResult=Invoking the resetCounter on the lifecycle.] When running the "Stop listener" operation at the Listener Configuration level I get this error in the jon server log: 2009-09-16 15:55:15,579 ERROR [OperationManager.invoker-1] (rhq.core.pc.operation.OperationInvocation)- Plugin error: Operation [stop] is defined as returning no results, but it returned non-null results: Configuration[id=0, operationResult=Invoking the stop on the lifecycle.] When running the "Start listener" operation at the Listener Configuration level I get this error in the jon server log: 2009-09-16 15:55:29,819 ERROR [OperationManager.invoker-1] (rhq.core.pc.operation.OperationInvocation)- Plugin error: Operation [start] is defined as returning no results, but it returned non-null results: Configuration[id=0, operationResult=Invoking the start on the lifecycle.] Doesn't look like it breaks anything.
Link: Added: This issue Cloned from SOA-1509
This issue is cloned from SOA-1509 - it was considered for SOA-P 4.3.CP05, but since we were not going to ship an update to the JON plugin pack for SOA-P 4.3.CP05, we will not be fixing it there and will fix it in the plugin pack update for SOA-P 5.2.0.GA. Fix this bug against whatever version of JON SOA-P 5.2.0.GA will be qualified for.
Tested against jon 2.4.1, ESB on AS4. Did not see this exception.
Release Notes Docs Status: Added: Not Required Writer: Added: dlesage