-
1. Remote JMS client hanging on createConnection
clebert.suconic Apr 25, 2011 8:59 PM (in response to andrew.s)take a look at your hornetq-configuration.xml acceptors.. I don't think the jboss-bind-address is being used by default. Maybe you have to add the IP manually or change the properties.
That's something we changed on the EAP integration, and AS6 integration.. but I'm not sure about the integration with AS 5.
-
2. Remote JMS client hanging on createConnection
andrew.s Apr 25, 2011 9:57 PM (in response to clebert.suconic)I'm basing my connectors and acceptors off of the 2.2.2 ssl-servlet example. I've pasted them below.
<connectors>
<connector name="netty-servlet">
<factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class>
<param key="host" value="localhost"/>
<param key="port" value="8443"/>
<param key="use-servlet" value="true"/>
<param key="servlet-path" value="/SSD-web/HornetQServlet"/>
<param key="ssl-enabled" value="true"/>
<param key="key-store-path" value="/SSD/keystore/ssd.keystore"/>
<param key="key-store-password" value="ssdkeystore"/>
</connector>
</connectors>
<acceptors>
<acceptor name="netty-servlet">
<factory-class>org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory</factory-class>
<param key="use-invm" value="true"/>
<param key="host" value="org.hornetq"/>
</acceptor>
<acceptor name="netty-invm">
<factory-class>org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory</factory-class>
<param key="use-invm" value="true"/>
<param key="host" value="org.hornetq"/>
</acceptor>
</acceptors>
Should I change the host value? If I should change it, I'm figuring I should put 0.0.0.0 in there, correct? Why would this have worked with everything located on the same server (still remote JMS) versus with the AS remotely located?
Thanks again for your help,
Andrew
-
3. Remote JMS client hanging on createConnection
clebert.suconic Apr 25, 2011 10:35 PM (in response to andrew.s)You need to define both these properties on both acceptors and connectors:
<param key="host" value="${jboss.bind.address:localhost}"/>
<param key="port" value="${hornetq.remoting.netty.port:5445}"/>
or maybe
<param key="host" value="${jboss.bind.address:localhost}"/>
<param key="port" value="${hornetq.remoting.netty.ssl.port:5446}"/>
you currently have the connector trying localhost and the acceptor is not listening to any other port.
I also suggest you looking at chapter 16: http://docs.jboss.org/hornetq/2.2.2.Final/user-manual/en/html/configuring-transports.html#configuring-transports.acceptors
-
4. Remote JMS client hanging on createConnection
andrew.s Apr 25, 2011 10:52 PM (in response to clebert.suconic)Thanks for the info....I'll give it a try. I've actually looked at that chapter, but I'll give it another read through, since obviously I don't have everything down.
On a side note, will the standard netty TCP work over SSL for a remote client into the app server? I'd prefer to use this over the ssl servlet, but since I didn't see an example for this, was thinking it might not work. I looked for it in the documentation, but I wasn't sure if all the different types of connectors/acceptors worked while running in the app server.
Thanks for the help,
Andrew
-
5. Remote JMS client hanging on createConnection
clebert.suconic Apr 26, 2011 12:33 AM (in response to andrew.s)1 of 1 people found this helpfulIt should all work the same being standalone or inside the App server.
-
6. Remote JMS client hanging on createConnection
andrew.s Apr 26, 2011 12:38 AM (in response to clebert.suconic)Yes, thanks, I tried it locally just to see after I replied. It definitely worked. I will try on my remote setup tomorrow when I'm in the office for the binding solution.
Thanks for all of you help/info,
Andrew