Problem with double service in SwitchYard
Issue
- We encountered problems when we deployed a double service with Netty TCP bindings.
- We deployed a service that is listening on port
7777
and another service that is listening on port8585
; all the requests TCP that we sent on the second process (port8585
) are consumed always by first process (port7777
) deployed. switchyard.xml
for the first and second SwitchYard services respectively are as follows:
first service:
<switchyard [...] name="TCP-Adapter" targetNamespace="urn:com.example:tcp-adapter:1.0">
<sca:composite name="TCP-Adapter" targetNamespace="urn:com.example:tcp-adapter:1.0">
<sca:service name="SampleService" promote="SampleServiceBean/SampleService">
<sca:interface.java interface="com.example.tcp.SampleService"/>
<netty:binding.tcp name="tcp1">
[...]
<netty:port>7777</netty:port>
[...]
</netty:binding.tcp>
</sca:service>
[...]
</sca:composite>
</switchyard>
- second service:
<switchyard [...] name="TCP-Adapter" targetNamespace="urn:com.example:tcp-adapter:1.0">
<sca:composite name="TCP-Adapter" targetNamespace="urn:com.example:tcp-adapter:1.0">
<sca:service name="SampleService" promote="SampleServiceBean/SampleService">
<sca:interface.java interface="com.example.tcp.SampleService"/>
<netty:binding.tcp name="tcp1">
[...]
<netty:port>8585</netty:port>
[...]
</netty:binding.tcp>
</sca:service>
[...]
</sca:composite>
</switchyard>
Environment
- Red Hat JBoss Fuse Service Works (FSW)
- 6.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.