[Jboss-dev-forums] [Design of JBoss Remoting, Unified Invokers] - Re: org.jboss.remoting.CannotConnectException (ejb3)

[mhaerdi <nu...@jb...>]

still the same error... in the tcp/udp traffic on the client side i found at least one udp addressed to the server's internal address (192.168.x.x)

according to http://wiki.jboss.org/wiki/Wiki.jsp?page=Remoting_Transports_Configuration, I changed the file jboss-service.xml in 
\jboss-4.0.2\server\all\deploy\ejb3.deployer\META-INF
to:

<?xml version="1.0" encoding="UTF-8"?>
  | <server>
  |    <mbean code="org.jboss.ejb3.EJB3Deployer" name="jboss.ejb3:service=EJB3Deployer">
  |       <depends>jboss.aop:service=AspectDeployer</depends>
  |    </mbean>
  |    <mbean code="org.jboss.remoting.transport.Connector"
  |       xmbean-dd="org/jboss/remoting/transport/Connector.xml"
  |       name="jboss.remoting:type=Connector,transport=socket3873,handler=ejb3">
  |       <depends>jboss.aop:service=AspectDeployer</depends>
  |       <!--attribute name="InvokerLocator">socket://192.168.123.1:3873</attribute>
  |       <attribute name="Configuration">
  |          <handlers>
  |             <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
  |          </handlers>
  |       </attribute-->
  | 	<attribute name="Configuration">
  | 		<config>
  | 			<invoker transport="socket">
  | 				<attribute name="numAcceptThreads">1</attribute>
  | 				<attribute name="maxPoolSize">303</attribute>
  | 				<attribute name="clientMaxPoolSize">304</attribute>
  | 				<attribute name="socketTimeout">10000</attribute>
  | 				<attribute name="serverBindAddress">192.168.123.1</attribute>
  | 				<attribute name="serverBindPort">3873</attribute>
  | 				<attribute name="clientConnectAddress">212.254.183.234</attribute>
  | 				<attribute name="clientConnectPort">3873</attribute>
  | 				<attribute name="enableTcpNoDelay" isParam="true">false</attribute>
  | 				<attribute name="backlog">200</attribute>
  | 			</invoker>
  | 			<handlers>
  | 				<!--handler subsystem="mock">org.jboss.remoting.transport.mock.MockServerInvocationHandler</handler-->
  | 				<handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
  | 			</handlers>
  | 		</config>
  | 	</attribute>
  |    </mbean>
  | </server>

192.168.123.1 is the internal address of the server in the lan
212.254.183.234 is the external address of the server (firewall wan-ip)

i still start jboss with 
run.bat -c all -Djava.rmi.server.hostname=212.254.183.234 
-Djava.rmi.server.useLocalHostname=false 

The client connects with
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.provider.url=jnp://212.254.183.234:1099

what is wrong/missing?


"tom...@jb..." wrote : Since the ip is 0.0.0.0, the server will just bind to its local host and use that ip as the address it tells clients to connect to.  This is probably something like 192.168.1.1.  The client, which is outside the firewall, probably does not access the server machine via the previous ip, but via some external ip (i.e. 56.23.35.2).  Since the server does not know explicitly what this ip is, it can not tell the client to use this ip.  You can change the address that the client tried to connect to the server on by changing the configuration (see http://wiki.jboss.org/wiki/Wiki.jsp?page=Remoting_Transports_Configuration).
  | 
  | 

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

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