Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-4163

could not get connection using ConnectionFactory which from remote jndi lookup; just using RemoteConnectionFactory

    XMLWordPrintable

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Major
    • 7.1.3.Final (EAP)
    • 7.1.1.Final
    • JMS
    • None
    • Interactive Demo/Tutorial

    Description

      the server side configuration:

      <connectors>
      <netty-connector name="netty" socket-binding="messaging" />
      <netty-connector name="netty-throughput" socket-binding="messaging-throughput">
      <param key="batch-delay" value="50"/>
      </netty-connector>
      <in-vm-connector name="in-vm" server-id="0"/>
      </connectors>
      <acceptors>
      <netty-acceptor name="netty" socket-binding="messaging" />
      <netty-acceptor name="netty-throughput" socket-binding="messaging-throughput">
      <param key="batch-delay" value="50"/>
      <param key="direct-deliver" value="false"/>
      </netty-acceptor>
      <in-vm-acceptor name="in-vm" server-id="0"/>
      </acceptors>
      ....
      <interfaces>
      <interface name="management">
      <inet-address value="${jboss.bind.address.management:10.50.50.13}"/>
      </interface>
      <interface name="public">
      <inet-address value="${jboss.bind.address:10.50.50.13}"/>
      </interface>
      <interface name="unsecure">
      <inet-address value="${jboss.bind.address.unsecure:10.50.50.13}"/>
      </interface>
      </interfaces>
      <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
      <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>
      <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
      <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>
      <socket-binding name="ajp" port="8009"/>
      <socket-binding name="http" port="8080"/>
      <socket-binding name="https" port="8443"/>
      <socket-binding name="jacorb" interface="unsecure" port="3528"/>
      <socket-binding name="jacorb-ssl" interface="unsecure" port="3529"/>
      <socket-binding name="messaging" port="5445"/>
      <socket-binding name="messaging-throughput" port="5455"/>
      <socket-binding name="osgi-http" interface="management" port="8090"/>
      <socket-binding name="remoting" port="4447"/>
      <socket-binding name="txn-recovery-environment" port="4712"/>
      <socket-binding name="txn-status-manager" port="4713"/>
      <outbound-socket-binding name="mail-smtp">
      <remote-destination host="localhost" port="25"/>
      </outbound-socket-binding>
      </socket-binding-group>

      my client side jndi.properties
      java.naming.factory.initial=org.jboss.naming.remote.client.InitialContextFactory
      java.naming.provider.url=remote://222.92.115.15:4447
      java.naming.security.principal=uname
      java.naming.security.credentials=pword

      when i use jndi to lookup an ConnectionFactory,I got the factory like this:
      HornetQConnectionFactory [serverLocator=ServerLocatorImpl [initialConnectors=[org-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=5445&host=10-50-50-13], discoveryGroupConfiguration=null], clientID=null, dupsOKBatchSize=1048576, transactionBatchSize=1048576, readOnly=false]

      but when i use the factory to create an connection,it failed:
      Caused by: HornetQException[errorCode=2 message=Cannot connect to server(s). Tried with all available servers.]

      it used ip 10.50.50.13 to create an connection, but i want to use ip 222.92.115.15 to create an connection.
      I have not found any place to configure this ip for RemoteConnectionFactory

      Attachments

        Activity

          People

            jmesnil1@redhat.com Jeff Mesnil
            129cat gookin wu (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: