This content has been marked as final.
Show 1 reply
-
1. Re: refused connection
vashistvishal Apr 4, 2005 1:44 AM (in response to bungrudi)First check yr security settings in policy file for the standalone client.
Secodly binding address for the naming service
under server/{default/all/minimal}/conf/jboss-service.xml can be chnged here as shon below.<mbean code="org.jboss.naming.NamingService" name="jboss:service=Naming"> <!-- 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">true</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> <!-- The bootstrap JNP server bind address. This also sets the default RMI service bind address. Empty == all addresses --> <attribute name="BindAddress">${jboss.bind.address}</attribute> <!-- The port of the RMI naming service, 0 == anonymous --> <attribute name="RmiPort">1098</attribute> <!-- The RMI service bind address. Empty == all addresses --> <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> </mbean>
Vishal.
http://vashistvishal.blogspot.com