[jboss-user] [JBoss Messaging] - ConnectionFactory returns invalid URL which causes MessagingNetworkFailureException

[Duane Zamrok]

Duane Zamrok [https://community.jboss.org/people/dewthefifth] created the discussion

"ConnectionFactory returns invalid URL which causes MessagingNetworkFailureException"

To view the discussion, visit: https://community.jboss.org/message/714389#714389

--------------------------------------------------------------
Hello, and thank you in advance for any assistence you might offer.

I am trying to connect two JBoss servers, executing on separate machines, to one another using JMS through JBoss Messaging. Due to network topography and proxying requirements, the each machine is referenced differently than the machine's hostname. I'll elaborate. 

Network one contains a machine which we will call Jboss01.
Network two contains two machines, Jboss02 and Jboss03. 
Network one and Network two communicate through a shared domain controller which we'll call DC01.
When Jboss01 attempts to access Jboss02 then DC01 directs Jboss01 to JbossProxy which will proxy traffic on port 443 to port 8443.
Jboss01 is incapable of reaching Jboss02 directly
When Jboss02 attempts to access Jboss03 then DC01 directs Jboss02 to JbossProxy which will proxy traffic on port 443 to port 8443.
Jboss02 is capable of reaching Jboss03 directly by asking specifically for Jboss03-vm which DC01 understands to be a direct link

Jboss01>hostname will return Jboss01
Jboss02>hostname will return Jboss02
Jboss03>hostname will return Jboss03

I am trying to send JMS messages from Jboss02 to Jboss03, but the org.jboss.jms.server.connectionfactory.ConnectionFactory returned from JNDI attempts to connect to Jboss03 instead of Jboss03-vm. This causes the connection to be routed through the proxy, which does not service the JMS port, and results in the MessageNetworkingFailureException mentioned in the topic. My JNDI connection is through Jboss03-vm, and I have set several properties (bind.addres, java.rmi.server.hostname) to Jboss03-vm to facilitate the direct connection that I require, but I cannot figure out how to configure the org.jboss.remoting.transport.Connector to use Jboss03-vm instead of Jboss03.

Thanks again for any help you might offer.

*Environment*
I am currently working within a customer controlled environment, which limits some of my options for upgrades and solutions.

*JbossAS*
jboss-eap-4.3

*JbossMessaging*
jboss.messaging.jmsVersion=1.1
jboss.messaging.jmsMajorVersion=1
jboss.messaging.jmsMinorVersion=1
jboss.messaging.jmsProviderName=JBoss Messaging
jboss.messaging.providerVersion=1.4.0.SP3-CP08.patch01
jboss.messaging.providerMajorVersion=1
jboss.messaging.providerMinorVersion=4
jboss.messaging.providerIncrementingVersion=32

*JbossRemoting*
Name: JBossRemoting
Specification-Title: JBossRemoting
Implementation-Title: JBossRemoting
Specification-Vendor: JBoss Inc.
Specification-Version: 2.2.3
Implementation-Vendor-Id:  http://www.jboss.org http://www.jboss.org
Implementation-Version: 2.2.3
Implementation-Vendor: JBoss Inc.

*Properties*
bind.address=intellex-vm
jboss.bind.address=0.0.0.0
java.rmi.server.hostname=intellex-vm
--------------------------------------------------------------

Reply to this message by going to Community
[https://community.jboss.org/message/714389#714389]

Start a new discussion in JBoss Messaging at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2042]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20120203/83a3b93e/attachment.html