Bug 779637 (SOA-2007)

Summary: EsbDeployment stop/start mbean functions do not restart listeners
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Kevin Conner <kevin.conner>
Component: JBossESBAssignee: Kevin Conner <kevin.conner>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 GA   
Target Milestone: ---   
Target Release: 5.0.2   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2007
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-28 13:36:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kevin Conner 2010-03-22 16:13:59 UTC 
Date of First Response: 2010-05-28 09:36:59
Workaround Description: Use the MBeans directly referencing the listeners rather than the deployment.
project_key: SOA

The EsbDeployment registers as an MBean within the jmx-console, with name jboss.esb:deployment=<name>, and exposes a start and stop method.

Stopping the deployment results in the listeners being stopped, however starting the deployment again does nothing.

The simple solution is to null the reference to the controller when stopping, adding a guard for null within that method.

We should also add a state so that this can be queried.
Comment 1 Kevin Conner 2010-04-16 08:11:35 UTC 
Link: Added: This issue depends JBESB-3284
Comment 2 Kevin Conner 2010-04-26 13:40:43 UTC 
Updated in ESB codebase, will be in next merge.
Comment 3 Jiri Pechanec 2010-05-28 13:36:59 UTC 
Verified in CR1
Comment 4 David Le Sage 2010-06-07 04:14:26 UTC 
This is the draft text for the Release Notes:


https://jira.jboss.org/jira/browse/SOA-2007

    The EsbDeployment stop/start MBean functions would not restart the listeners. To fix this problem,
    reference to the controller is nulled upon stopping and a guard for null has been added to the
    method. As a result, the restart function now works as expected. A state for querying this has also
    been added.