-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
7.4.0.Beta
-
None
-
3
-
False
-
False
-
-
-
-
-
-
Undefined
-
By default there is 1 remoting connector http-remoting-connector.
If you add another connector such as the legacy-remoting-connector , those connectors should be listed in the 'remote' 'connectors' element of the ejb3 subsystem. By default it only had a connector-ref and did not allow specifying multiple connectors.
<subsystem xmlns="urn:jboss:domain:ejb3:8.0"> ... <remote cluster="ejb" connectors="http-remoting-connector" thread-pool-name="default"> <channel-creation-options> <option name="MAX_OUTBOUND_MESSAGES" value="1234" type="remoting"/> </channel-creation-options> </remote> ... <subsystem xmlns="urn:jboss:domain:remoting:4.0"> <connector name="legacy-remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/> <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/> </subsystem> </subsystem> ....
Setting the connectors to http-remoting-connector , legacy-remoting-connector :
/subsystem=ejb3/service=remote:write-attribute(name=connectors, value=[http-remoting-connector, legacy-remoting-connector])
- is related to
-
JBEAP-21074 Model change in EJB remote service causes regression against 7.3
- Closed
- relates to
-
WINDUPRULE-735 ejb3 subsystem connector-ref attribute deprecated
- In Progress