Hide Forgot
Date of First Response: 2010-01-13 10:07:25 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 is a dependency of SOA-1628
Link: Added: This issue is a dependency of JBESB-2991
Link: Removed: This issue is a dependency of SOA-1628
Link: Removed: This issue is a dependency of JBESB-2991
Link: Added: This issue is related to SOA-1628
Checked with Tom and he reckons porting over the fix from soa-1628 would not be much work, as long as Len and QA are going to do a requalification of the JON plugin. Len says that seems ok.
This issue is not approved for SOA 4.3 CP03. If this needs to be reconsidered, please raise the issue with the SOA PM team.
Link: Added: This issue Cloned to SOA-2971
This bug was considered for SOA-P 4.3.0.CP5. Since it needs a new JON plugin pack and no JON plugin pack will be shipped for SOA-P 4.3.0.CP5, it was cloned for 5.2 (SOA-2971) and this issue will be closed as Won't Fix.