At 11:16 AM 07/14/2000 -0700, you wrote:
>Hi,
>
>I am having problem of deploy the sample app interest that part of jboss
>documentation. It works fine when both the client and jboss in the same
>machine. When they are apart, following the instruction I change the
>client's provider url to wherever jboss server is, the error gets
>generated from this line:
>
>Object ref = jndiContext.lookup("interest/Interest");
>
>The error is:
>javax.naming.CommunicationException. Root exception is
>java.rmi.ConnectException: Connection refused to host: localhost; nested
>exception is:
>System Error: java.net.ConnectException: Connection refused: no
>further information
>System Error: java.net.ConnectException: Connection refused: no further
>information
>
>Has anyone successfully deployed any beans that can be access
>remotely? Can you tell me is there any other additional configuration I
>must set to have this works correctly.
I've seen this kind of problem when trying to use RMI on JDK 1.3, which has
a new requirement for an RMI security policy. What worked for me there was
using -D to add a security policy file for launching rmid. I don't know how
this translates to jBoss, though.
-- Ken Jenks, http://abiblion.com/
Tools for reading.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
