Bug 779667 (SOA-2033)

Summary:	Deployment State in SOA-P 5
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	david.boeren <david.boeren>
Component:	JBossESB	Assignee:	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.1.0 GA
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-2033
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-02-11 06:00:03 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description david.boeren 2010-04-08 17:14:28 UTC

Date of First Response: 2010-04-08 14:00:43
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&tid=581783&gid=1354
project_key: SOA

in ESB 4.6 there was a MBean attribute "StateString" available via the JMX console telling about the deployment state of an ESB package like "Started" or "Stopped".

We're searching for a solution on SOA-P 5 where this attribute doesn't seem to exist anymore.

Can this attribute or something similar be re-added for SOA-P 5.0?

Comment 2 Anne-Louise Tangring 2010-09-21 20:39:12 UTC

Candidate (optional) for SOA 5.1.0.

Comment 3 Kevin Conner 2010-09-27 15:38:39 UTC

Link: Added: This issue depends JBESB-3491

Comment 4 Kevin Conner 2010-10-11 09:03:52 UTC

Updated in ESB codebase, will need an updated plugin.

Comment 6 Dana Mison 2011-01-05 00:14:32 UTC

Writer: Added: dlesage

Comment 7 David Le Sage 2011-02-11 05:54:15 UTC

Temporarily reopening to update release note info.

Comment 8 David Le Sage 2011-02-11 05:58:35 UTC

Release Notes Docs Status: Added: Documented as Resolved Issue
Release Notes Text: Added: https://issues.jboss.org/browse/JBESB-3491

The MBean attribute "StateString" that was previously available via the JMX console was no long present. This was because the SOA Platform is running on Application Server 5.  As a result, users could not find out the ESB package's deployment state (such as "Started" or "Stopped") via the JMX Console.  This feature has now been  ported to Application Server 5 so it can be utilised again.