3 Replies Latest reply on Dec 19, 2014 8:30 AM by peter craddock

    Wildfly 8.2 JMS Topic connection over https

    peter craddock Novice

      I have raised this before against version 8 and 8.1 and the following jira has been raised and closed [HORNETQ-1317] Error connecting with http-upgrade mechanism against https port on WildFly - JBoss Issue Tracker

       

      I may have got the configuration wrong but from what I can tell it still does not work.

       

      Here is my JMS Config

              <connectors>
                 <http-connector name="http-connector" socket-binding="https">
                    <param key="http-upgrade-endpoint" value="http-acceptor"/>
                 </http-connector>
                 <http-connector name="http-connector-throughput" socket-binding="https">
                    <param key="http-upgrade-endpoint" value="http-acceptor-throughput"/>
                    <param key="batch-delay" value="50"/>
                 </http-connector>
                 <in-vm-connector name="in-vm" server-id="0"/>
              </connectors>
              <acceptors>
                 <http-acceptor http-listener="default" name="http-acceptor"/>
                 <http-acceptor http-listener="default" name="http-acceptor-throughput">
                    <param key="batch-delay" value="50"/>
                    <param key="direct-deliver" value="false"/>
                 </http-acceptor>
                 <in-vm-acceptor name="in-vm" server-id="0"/>
              </acceptors>

       

       

      Here is the undertow config

              <http-listener max-parameters="10000" name="local" socket-binding="http"/>
              <host alias="localhost" name="default-host">
                 <location handler="welcome-content" name="/wildfly"/>
                 <filter-ref name="server-header"/>
                 <filter-ref name="x-powered-by-header"/>
              </host>
              <https-listener max-parameters="10000" name="default" security-realm="ssl-realm" socket-binding="https"/>       

       

      The Client is connecting to the rmi using http-upgrade. I had to pass the following because I was using a self signed cert

           -Djavax.net.ssl.trustStore=${client.keystore} -Djavax.net.ssl.trustStorePassword=password

       

      My remote client connect using the following context properties.

       

      java.naming.provider.url=http-remoting://x2100a.coa.local:11171,https-remoting://x2100a.coa.local:11171

      java.naming.factory.initial=org.jboss.naming.remote.client.InitialContextFactory

      java.naming.security.authentication=simple

      java.naming.security.principal=admin

      jboss.naming.client.ejb.context=true

      java.naming.security.credentials=password

       

      Here is the client stack trace

      [java] at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:673)
      [java] at org.hornetq.jms.client.HornetQConnectionFactory.createTopicConnection(HornetQConnectionFactory.java:193)
      [java] at org.hornetq.jms.client.HornetQConnectionFactory.createTopicConnection(HornetQConnectionFactory.java:188)
      [java]

      at com.cedar.cp.util.common.JmsConnectionImpl$AbstractJmsTopic.<init>(JmsConnectionImpl.java:289)