Bug 1009589 - [rhq-plugin] service state is NONE
Summary: [rhq-plugin] service state is NONE
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: JON
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 6.1.0
Assignee: tcunning
QA Contact: Jiri Sedlacek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-18 16:26 UTC by Viet Nguyen
Modified: 2016-01-28 11:53 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
If you stop a service from either the JON UI or the Admin console and then check the service state, you will see that it is reported as being NONE. This is due to SwitchYard reporting back the incorrect value.
Clone Of:
Environment:
Last Closed: 2015-07-14 17:54:52 UTC
Type: Bug

Attachments (Terms of Use)
screenshot (305.03 KB, image/png)
2013-09-18 16:27 UTC, Viet Nguyen 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ENTESB-3631 0 Major Closed [rhq-plugin] service state is NONE 2016-01-28 11:53:43 UTC
Red Hat Issue Tracker SWITCHYARD-1828 0 Major Resolved Distinguish between binding lifecycle not present and stopped 2016-01-28 10:22:10 UTC

Description Viet Nguyen 2013-09-18 16:26:52 UTC 
Description of problem:

"NONE" is used when service is in Stopped state. See attachment.

Version-Release number of selected component (if applicable):
master

How reproducible:
Stop a service either from JON UI or SOA Admin console.  Check trait value.
Comment 1 Viet Nguyen 2013-09-18 16:27:32 UTC 
Created attachment 799480 [details]
screenshot
Comment 3 Mike Foley 2013-11-09 00:06:47 UTC 
retested by varun 11/9.  valid BZ,
Comment 4 kconner 2013-11-09 15:29:56 UTC 
The value is being returned from SwitchYard, will investigate

            "name" => "{urn:switchyard-quickstart:bean-service:0.1.0}OrderService",
            "application" => "{urn:switchyard-quickstart:bean-service:0.1.0}orders",
            "interface" => "wsdl/OrderService.wsdl#wsdl.porttype(OrderService)",
            "promotedService" => "{urn:switchyard-quickstart:bean-service:0.1.0}OrderService",
            "gateways" => [{
                "name" => "_OrderService_soap_1",
                "type" => "soap",
                "configuration" => "<binding.soap xmlns=\"urn:switchyard-component-soap:config:1.0\">
    <wsdl>wsdl/OrderService.wsdl</wsdl>
    <socketAddr>:18001</socketAddr>
    <contextPath>quickstart-bean</contextPath>
</binding.soap>",
                "state" => "NONE"
            }],
            "throttling" => {
                "enabled" => false,
                "maxRequests" => 0,
                "timePeriod" => 1000L
            }
Comment 6 tcunning 2015-07-14 17:54:52 UTC 
We're moving to JIRA for tracking issues for Fuse 6.2.1.   Logged https://issues.jboss.org/browse/ENTESB-3631.    Closing this issue, work will continue at related JIRA.
Comment 7 JBoss JIRA Server 2015-07-15 21:24:18 UTC 
Tom Cunningham <tcunning> updated the status of jira ENTESB-3631 to Resolved
Comment 8 JBoss JIRA Server 2016-01-28 11:53:43 UTC 
Tomas Plevko <tplevko> updated the status of jira ENTESB-3631 to Closed
Note You need to log in before you can comment on or make changes to this bug.