[jboss-jira] [JBoss JIRA] (WFLY-6527) Cannot lookup RemoteConnectionFactory using https-remoting
[
https://issues.jboss.org/browse/WFLY-6527?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on WFLY-6527:
------------------------------------
If possible, please attach a simple application which reproduces this. Or please open a
forum discussion https://developer.jboss.org/en/wildfly/ where this can be looked into in
detail along with code and exception stacktraces.
Cannot lookup RemoteConnectionFactory using https-remoting
----------------------------------------------------------
Key: WFLY-6527
URL: https://issues.jboss.org/browse/WFLY-6527
Project: WildFly
Issue Type: Bug
Components: Remoting
Affects Versions: 10.0.0.Final
Environment: RedHat Linux, Java 1.8
Reporter: George Turner
Assignee: David Lloyd
I have successfully configured the system for two way ssl. I can connect to a topic from
a standalone client, but I cannot connect with the same code from an EJB client using the
following:
Properties props = new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jboss.naming.remote.client.InitialContextFactory");
ctx = new InitialContext(props);
ConnectionFactory cf = (ConnectionFactory)
ctx.lookup("jms/RemoteConnectionFactory");
It seems to "attach" the stateless bean to the first remote instance and then
the second remote instance lookup fails. I have tried using the EJBClientContext
properties (as used for EJB lookups) but no help. There is VERY little documentation
about using https-remoting.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)