Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1139601

Summary:

Switchyard remote ( /switchyard-remote ) doesn't work on Fuse + FSW 6.1 DR2

Product:

[JBoss] JBoss Fuse Service Works 6

Reporter:

Martin Swiech <mswiech>

Component:

SwitchYard

Assignee:

tcunning

Status:

CLOSED UPSTREAM

QA Contact:

Matej Melko <mmelko>

Severity:

high

Docs Contact:

Priority:

urgent

Version:

6.1.0

CC:

mvecera, soa-p-jira

Target Milestone:

DR3

Target Release:

6.1.0

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2025-02-10 03:42:58 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:

Attachments:

Description	Flags
catched HTTP communication	none
reproducer test	none

Description Martin Swiech 2014-09-09 10:02:28 UTC

Description of problem:

Version-Release number of selected component (if applicable):
2.0.0.Alpha2-redhat-1

How reproducible:
always

Steps to Reproduce:
1. Install Fuse + FSW 6.1 DR2
2. Run Fuse and install features like switchyard, switchyard-bean, switchyard-sca
3. Deploy switchyard application with some remote SCA service
4. Call that remote SCA service (using HttpInvoker with url http://localhost:8181/switchyard-remote )

Actual results:
Response from /switchyard-remote has status 200 OK, but response length is 0. Service is not executed.

Expected results:
Service is executed and there is correct response from /switchyard-remote

Additional info:
It looks like /switchyard-remote is completly death.

Additional info from Fuse:

JBossFuse:karaf@root> features:list -i | grep switchyard
[installed  ] [2.0.0.Alpha2-redhat-1] switchyard                 switchyard-2.0.0.Alpha2-redhat-1     
[installed  ] [2.0.0.Alpha2-redhat-1] switchyard-internal-core   switchyard-2.0.0.Alpha2-redhat-1     
[installed  ] [5.4.0                ] dozer                      switchyard-2.0.0.Alpha2-redhat-1     
[installed  ] [2.0.0.Alpha2-redhat-1] switchyard-bean            switchyard-2.0.0.Alpha2-redhat-1     
[installed  ] [2.0.0.Alpha2-redhat-1] switchyard-bean-xbean-hack switchyard-2.0.0.Alpha2-redhat-1     
[installed  ] [2.0.0.Alpha2-redhat-1] switchyard-cdi             switchyard-2.0.0.Alpha2-redhat-1     
[installed  ] [2.0.0.Alpha2-redhat-1] switchyard-bpm             switchyard-2.0.0.Alpha2-redhat-1     
[installed  ] [2.0.0.Alpha2-redhat-1] switchyard-camel           switchyard-2.0.0.Alpha2-redhat-1     
[installed  ] [2.0.0.Alpha2-redhat-1] switchyard-http            switchyard-2.0.0.Alpha2-redhat-1     
[installed  ] [2.0.0.Alpha2-redhat-1] switchyard-internal-http   switchyard-2.0.0.Alpha2-redhat-1     
[installed  ] [2.0.0.Alpha2-redhat-1] switchyard-internal-rest   switchyard-2.0.0.Alpha2-redhat-1     
[installed  ] [2.0.0.Alpha2-redhat-1] switchyard-rules           switchyard-2.0.0.Alpha2-redhat-1     
[installed  ] [2.0.0.Alpha2-redhat-1] switchyard-sca             switchyard-2.0.0.Alpha2-redhat-1     
[installed  ] [2.0.0.Alpha2-redhat-1] switchyard-internal-sca    switchyard-2.0.0.Alpha2-redhat-1     
[installed  ] [2.0.0.Alpha2-redhat-1] switchyard-internal-soap   switchyard-2.0.0.Alpha2-redhat-1     



JBossFuse:karaf@root> features:list -i | grep sca
[installed  ] [0.0.1-SNAPSHOT       ] sca3                       repo-0                               
[installed  ] [0.0.1-SNAPSHOT       ] sca2                       repo-0                               
[installed  ] [2.0.0.Alpha2-redhat-1] switchyard-sca             switchyard-2.0.0.Alpha2-redhat-1     
[installed  ] [2.0.0.Alpha2-redhat-1] switchyard-internal-sca    switchyard-2.0.0.Alpha2-redhat-1     



JBossFuse:karaf@root> list
....
[ 364] [Active     ] [Created     ] [       ] [   60] SwitchYard: Karaf Deployer (2.0.0.Alpha2-redhat-1)
.....


JBossFuse:karaf@root> ls 364
......
objectClass = org.switchyard.component.sca.RemoteEndpointPublisher
osgi.service.blueprint.compname = ScaHttpEndpointPublisher
service.id = 487
.......

Comment 1 Martin Swiech 2014-09-09 10:10:03 UTC

Created attachment 935618 [details]
catched HTTP communication

Comment 2 Martin Swiech 2014-09-09 10:24:45 UTC

Created attachment 935624 [details]
reproducer test

Comment 3 Martin Swiech 2014-09-09 10:30:09 UTC

Also I have tried apps.zip ( from here https://issues.jboss.org/browse/SWITCHYARD-2083 ) with changed version of switchyard to "2.0.0.Alpha2-redhat-1" in poms. Didn't work either.

Comment 4 Martin Swiech 2014-09-09 11:32:51 UTC

This bug is blocker for QA.

Comment 5 Martin Swiech 2014-09-18 14:47:13 UTC

This bug is probably caused by synchronization problem.

When I put a breakpoint to the org.switchyard.deploy.osgi.base.AbstractExtender#289 (line extension.start(); in the anonymous Runnable class), something gets more time to initialize. And after resume the OsgiHttpEndpointPublisher is correctly initialized.

Otherwise org.switchyard.component.sca.deploy.SCAComponent#initEndpointPublisher could not find correct RemoteEndpointPublisher and fallback to NOPEndpointPublisher... unfortunately nothing is LOGged.

Comment 6 Rob Cernich 2014-09-19 14:05:57 UTC

SWITCHYARD-2320 adds some logging so you will know if the cause of test failures is because the NOP publisher is being used.  I'm not sure if moving the services into their respective plugins is enough to remove the error, but I also haven't seen it since the changes went in.

Comment 7 JBoss JIRA Server 2014-12-09 01:27:02 UTC

Rob Cernich <rcernich> updated the status of jira SWITCHYARD-2259 to Resolved

Comment 11 Red Hat Bugzilla 2025-02-10 03:42:58 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.