[jboss-user] [Clustering/JBoss] - Re: JBoss Cluster using Gossip Router

[amardeep21]

Hi,

We are starting jboss using -b option.

./run.sh -c vpn -b vpnip
./run.sh -c static -b staticip

So, bind address should be of VPN node and connection should go to VPN IP :5446
instead if keep trying on STATIC IP:5446

One thing to notice was the jndi lookup goes to VPN IP but why it slips to STATIC IP 
to create ejb connection where it should go to VPN IP.

I have compared the config and can't locate what could be the problem.

Extract from the jboss-service.xml

<mbean code="org.jboss.naming.NamingService"
  | name="jboss:service=Naming"
  | xmbean-dd="resource:xmdesc/NamingService-xmbean.xml">
  | <!-- The call by value mode. true if all lookups are unmarshalled using
  |  the caller's TCL, false if in VM lookups return the value by reference. -->
  |  <attribute name="CallByValue">false</attribute>
  |  <!-- The listening port for the bootstrap JNP service. Set this to -1
  |  to run the NamingService without the JNP invoker listening port. -->
  |  <attribute name="Port">1099</attribute>
  | <attribute name="BindAddress">${jboss.bind.address}</attribute>
  | <!-- The port of the RMI naming service, 0 == anonymous -->
  |  <attribute name="RmiPort">1098</attribute>
  |  <attribute name="RmiBindAddress">${jboss.bind.address}</attribute>
  |  <!-- The thread pool service used to control the bootstrap lookups -->
  |  <depends optional-attribute-name="LookupPool"
  |  proxy-type="attribute">jboss.system:service=ThreadPool</depends>
  |  <!-- An example of using the unifed invoker as the transport.
  | <depends optional-attribute-name="InvokerProxyFactory"
  | proxy-type="attribute">jboss:service=proxyFactory,type=unified,target=Naming
  | </depends>-->
  | <depends optional-attribute-name="Naming"
  |  proxy-type="attribute">jboss:service=NamingBeanImpl</depends>
  | </mbean>


<!-- The Connector is the core component of the remoting server service. -->
  |    <!-- It binds the remoting invoker (transport protocol, callback configuration, -->
  |    <!-- data marshalling, etc.) with the invocation handlers.  -->
  |    <mbean code="org.jboss.remoting.transport.Connector"
  |           name="jboss.remoting:service=Connector,transport=socket"
  |           display-name="Socket transport Connector">
  |      
  |      <attribute name="Configuration">
  |       <config>
  |             <!-- Other than transport type and handler, none of these configurations are required (will just use defaults). -->
  |             <invoker transport="socket">
  |                <attribute name="dataType" isParam="true">invocation</attribute>
  |                <attribute name="marshaller" isParam="true">org.jboss.invocation.unified.marshall.InvocationMarshaller</attribute>
  |                <attribute name="unmarshaller" isParam="true">org.jboss.invocation.unified.marshall.InvocationUnMarshaller</attribute>
  |                <attribute name="clientMaxPoolSize" isParam="true">2000</attribute>
  |                <attribute name="socketTimeout" isParam="true">600000</attribute>
  |                <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
  |                <attribute name="serverBindPort">4446</attribute>
  |                <!-- <attribute name="clientConnectAddress">216.23.33.2</attribute> -->
  |                <!-- <attribute name="clientConnectPort">7777</attribute> -->
  |                <attribute name="enableTcpNoDelay" isParam="true">true</attribute>
  |                <!-- <attribute name="backlog">200</attribute>-->

Thanks,
Amardeep

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

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