Bug 1025319 - Trouble with EJB invocation from a server with/without SSL
Summary: Trouble with EJB invocation from a server with/without SSL
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Remoting
Version: 6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: CR1
: ---
Assignee: Brian Stansberry
QA Contact: Jitka Kozana
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-31 13:29 UTC by wfink
Modified: 2018-12-03 20:31 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When creating an outbound remote connection, the service that creates the connection would apply the default settings after applying user-defined configuration settings. This resulted in the default settings incorrectly overriding any user-defined settings that had the same key. As a result of this situation, SSL could not be disabled on remote EJB connections which originated from the server. This issue has been fixed in this release of JBoss EAP 6. User-defined settings are now applied after the default settings, which ensures that user-defined settings take precedence. As a result, SSL can now be disabled on outbound remote connections.
Clone Of:
Environment:
Last Closed: 2013-12-15 16:23:42 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-1924 0 Major Resolved An EJB on a WildFly server can't call another bean on a second server with remoting and SSL 2014-07-22 04:57:25 UTC

Description wfink 2013-10-31 13:29:29 UTC 
If the remote-outbound-connection disable SSL or add SSL properties that might fail if there are different SSL related properties are overridden by default ones where it should be vice versa.

The analysis will be difficult as in EAP6 the failure messages are swallowed. They are only visible in org.jboss.as.ejb3 DEBUG mode.
Comment 5 Ladislav Thon 2013-11-12 11:24:26 UTC 
This issue was verified using the 6.2.0.CR1 preview bits.
Note You need to log in before you can comment on or make changes to this bug.