-
Bug
-
Resolution: Done
-
Major
-
None
-
False
-
False
-
-
-
-
-
-
+
-
Undefined
-
When an EJB client 4 application interacts with an EAP 7.0 server (using version 2 of the EJB client wire protocol), service URLs for deployments are not constructed correctly.
For example, for a client and server application using the same deployment, if we execute the application using a version 3 client and a version 2 server, we get service URLs:
NodeInformation: node node-1 has serviceURLs = [ service:ejb.jboss:remote+http://127.0.0.1:9080;node=node-1, service:ejb.jboss:remote+http://127.0.0.1:9080;cluster=ejb;node=node-1, service:ejb.jboss:remote+http://localhost:9080;node=node-1;ejb-module=ear/ear,ear/test,ear/ejb // error! ******************************* ] NodeInformation: node node-2 has serviceURLs = [ service:ejb.jboss:remote+http://localhost:10080;node=node-2;ejb-module=ear/ear,ear/test,ear/ejb, service:ejb.jboss:remote+http://127.0.0.1:10080;node=node-2, service:ejb.jboss:remote+http://127.0.0.1:10080;cluster=ejb;node=node-2 // error! ********************************** ]
and if we run the same application but using a version 3 server, we see service URLs:
NodeInformation: node node-1 has serviceURLs = [ service:ejb.jboss:remote+http://127.0.0.1:9080;node=node-1;ejb-module=ear/test,ear/ejb, service:ejb.jboss:remote+http://127.0.0.1:9080;cluster=ejb;node=node-1;ejb-module=ear/test,ear/ejb, service:ejb.jboss:remote+http://localhost:9080;node=node-1;ejb-module=ear/test,ear/ejb ] NodeInformation: node node-2 has serviceURLs = [ service:ejb.jboss:remote+http://localhost:10080;node=node-2;ejb-module=ear/test,ear/ejb, service:ejb.jboss:remote+http://127.0.0.1:10080;node=node-2;ejb-module=ear/test,ear/ejb, service:ejb.jboss:remote+http://127.0.0.1:10080;cluster=ejb;node=node-2;ejb-module=ear/test,ear/ejb ]
- incorporates
-
-
- Resolved
-
- is incorporated by
-
JBEAP-19790 [GSS](7.3.z) Upgrade jboss-ejb-client from 4.0.33.SP1-redhat-00001 to 4.0.37.Final-redhat-00001
-
- Closed
-
- relates to
-
-
- Closed
-
- links to
