1 Reply Latest reply on Dec 25, 2009 3:21 PM by ron_sigal

how to disable (temporary) rmi interface in jboss 4.2.3 + re

gmainzer Nov 4, 2009 11:23 AM

Hi all,
I have jboss AS 4.2.3GA installed and i upgraded my remoting package (only jboss-remoting.jar) to 2.5.2. we have an RCP client that uses InitialContext to create the RMI proxies.
my problem is that this client queries the jboss all the time and when i want to reset jboss, i calls one of the beans before it is being initiated which causes it to fail.

I thought maybe I can disable the RMI interface untill my management is fully up and only then allow clients to connect.
does anybody knows how can i start my jboss with disabled RMI? if not, how can i know from within jboss which IPs are currently connected to me?

Thanks,
Gal

1. Re: how to disable (temporary) rmi interface in jboss 4.2.3 + re

ron_sigal Dec 25, 2009 3:21 PM (in response to gmainzer)

Hi G,

I can tell you that it's possible to use the "depends" attribute to make MBeans dependent on other MBeans, which can delay their creating and starting, so you may be able to push back the starting of the Remoting connector that supports the EJB3 subsystem. Take a look at the "jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3" MBean in $JBOSS_HOME/server/$CONFIG/deploy/ejb3.deployer/META-INF/jboss-service.xml. Also, look at the AS documentation. Try, for example, "JBoss Application Server 4.2.2" at http://labs.jboss.com/file-access/default/members/jbossas/freezone/docs/Server_Configuration_Guide/4/html/index.html .

However, the details of your question, which concerns services in the Application Server, is outside the scope of Remoting. I'm going to suggest that you post the question to the Application Server forum "Installation, Configuration & Deployment": http://community.jboss.org/en/jbossas/config .

-Ron
Actions