Bug 1175442
| Summary: | [GSS](6.4.z) Client Mapping expressions are allowed but are not resolved if used | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | wfink |
| Component: | Clustering | Assignee: | Chao Wang <chaowan> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jitka Kozana <jkudrnac> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.3.2 | CC: | bmaxwell, cdewolf, chaowan, heiner.tittelbach, istudens, lthon |
| Target Milestone: | CR1 | ||
| Target Release: | EAP 6.4.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-17 10:35:11 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1231259 | ||
Chao Wang <chaowan> updated the status of jira WFLY-4188 to Resolved Verified with EAP 6.4.3.CP.CR1. Retroactively bulk-closing issues from released EAP 6.4 cummulative patches. |
Description of problem: If socket binding with client-mapping is used to provide a valid client address for EJB invocation to the client the expressions are not resolved. Depend on the attribute the parsing failed direct during startup (port# is not numeric) or the expression is send to the client where the Exception is thrown at runtime. Notice for EJB invocation the problem is only visible if the application is clustered, otherwise the cluster view (where the client-mapping take effect) is not send to the client. How reproducible: ejb-remote quickstart can be used (SLSB need to be @Clustered) Steps to Reproduce: 1. use a EAP6.3 server and change the standalone-ha.xml <socket-binding name="remoting" port="${my.remoting.port}"> <client-mapping destination-address="${jboss.node.name}" destination-port="4447"/> </socket-binding> 2. start the server and deploy the ejb-remote app the ${my.remoting.port} is correct resolved 3. Start the client this will fail as the client receive the ${jboss.node.name} as IP address Actual results: Depend on the attribute the server start fail or the client fail at runtime - if client-mapping port use expr the parser fail during startup Expected results: To have a configuration which can use expressions (expr is allowed if I check CLI) it need to be resolved