[jboss-user] [Remoting] - unrecognized invoker locator

2008-08-07 Thread ecatum
Hi, I'm making an update of jboss remoting from 1.4.2 to 2.4.0. I find this link https://jira.jboss.org/jira/browse/JBWS-1134 which describe how to do it. I ve made the update and connection between server and client using invoke() works fine. But I have a warning message each time I made

[jboss-user] [Remoting] - Re: unrecognized invoker locator

2008-08-07 Thread ecatum
l'InvokerLocator doesn't support loopback address. API InvokerLocator : anonymous wrote : | NOTE: the hostname will automatically be resolved to the outside IP address of the local machine if localhost or 127.0.0.1 is used as the hostname in the URI. If it cannot be determined or resolved,

[jboss-user] [Remoting] - Connect or not CannotConnectException that is the question ?

2008-05-16 Thread ecatum
Hi, I m develloped an application which use jboss remoting and rmi. For the server, I implement ServerInvocationHandler. For the client, I use org.jboss.remoting.Client to communicate with the server. I periodically make invocation from clients to the server and release the connection using

[jboss-user] [Remoting] - Connection refused

2008-02-13 Thread ecatum
Hello, I m actually coding a server/client application using rmi and ServerInvocationHandler for the server. When I use the client on the same system as the server, there is no problem. But when I use the client on a different system, the client catch the exception : |

[jboss-user] [Remoting] - Re: Connection refused

2008-02-13 Thread ecatum
Solution : if the parameter jboss.bind.address is not defined with the -b [ip] or -Djboss.bind.address=[ip] option, some services bind the loopback adress whereas other one bind all network interfaces To solve my problem I remove the parameter jboss.bind.address. It allows me to bind the

[jboss-user] [Remoting] - RMI : Boss Remoting heavy load

2007-06-18 Thread ecatum
Hi, here the situation : - A client make remoting call on a object using rmi via org.jboss.remoting.Client and org.jboss.remoting.InvokerLocator. - On the server side, we use ServerInvocationHandler and implement the method invoke(...). Using jetty, we add on jboss-service.xml this

[jboss-user] [Management, JMX/JBoss] - Changing from remoting.transport.Connector to invocation.poo

2007-06-15 Thread ecatum
Hi, We've developped an application where a webapp agent communicates using Invoke/rmi with a server servlet serviced by our handler (MySubSys.class): | --- - | | webapp agent .invoke | ---RMI--- | servlet - handler