Hello All,

I'm trying to setup the clustering service in such way that all 
"administrative" dialog will use a private network, whild clients will connet 
on another interface.

I use Jboss 3.2.7 on a linux RH AS v3.

I tried several combinations of settings without the expected result:

First combination:
-------------------

Standard startup sequence (/etc/rc.d/init.d/jboss start) and 
cluster-service.xml modified as follows:

    <!-- The address used to determine the node name -->
    legolaslg

             loopback="false" bind_addr="legolaslg" />
 
The logs on two nodes show that a part of dialog is made on the private 
network, but then, farming deployement goes over the public network.
Trying a netstat -a | grep "MyPrivateAddresses" shows also than no connect are 
established over private network.

Clients can connect.

Standard JBoss shutdown command works.


Second combination:
-----------------------

I use the -b switch at JBoss startup to bind all network layers to the 
interface that corresponds to public network.

I use the same settings than above for cluster-service.xml

Result is the same that first combination regarding "administrative dialog"

Client can open a connection.

JBoss shutdown with standard shutdown command also impossible. Only a "kill 
-15" on the java process helps.

When I use the "shutdown.sh -S", I have the following error:

Exception in thread "main" javax.naming.CommunicationException: Could not 
obtain connection to any of these urls: localhost:1099 [Root exception is 
javax.naming.CommunicationException: Failed to connect to server localhost:1099 
[Root exception is javax.naming.ServiceUnavailableException: Failed to connect 
to server localhost:1099 [Root exception is java.net.ConnectException: 
Connection refused]]]
        at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1363)
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:575)
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:568)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at org.jboss.Shutdown.main(Shutdown.java:201)
Caused by: javax.naming.CommunicationException: Failed to connect to server 
localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: 
Failed to connect to server localhost:1099 [Root exception is 
java.net.ConnectException: Connection refused]]
        at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:250)
        at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1348)
        ... 4 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to 
server localhost:1099 [Root exception is java.net.ConnectException: Connection 
refused]
        at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:224)
        ... 5 more
Caused by: java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:364)
        at java.net.Socket.connect(Socket.java:507)
        at java.net.Socket.connect(Socket.java:457)
        at java.net.Socket.(Socket.java:365)
        at java.net.Socket.(Socket.java:265)
        at 
org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:69)
        at 
org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:62)
        at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:220)
        ... 5 more


Third combination:
-----------------------

I use the -b switch at JBoss startup to bind all network layers to the 
interface that corresponds to private network.

I use the same settings than above for cluster-service.xml

This time, client can't open a connection.

JBoss shutdown with standard shutdown command is also impossible. Only a "kill 
-15" on the java process helps.


Doesn't a special directive exist to tell JBoss to use a certain network for 
its administrative dialog, and another to listen to client on another one ?

      Thanks in advande for your help.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866430#3866430

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866430


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to