Hi,
Thanks for your reply. This is the code snippet for my server.
public class TestRMI extends UnicastRemoteObject implements ITestRMI
{
public static void main(String args[])
{
System.setSecurityManager(new RMISecurityManager() );
try
{
TestRMI test = new TestRMI();
Naming.rebind( "TestRMI", test );
System.out.println( "TestRMI object bound to registry" );
}
catch(Exception e)
{
e.printStackTrace();
}
}
}
With that, when I run the server, I get the println() on the screen, and after
that the server exits.
% java -green -Djava.security.policy=./policy TestRMI
TestRMI object bound to registry
%
Pratip
Nick Lawson wrote:
> Hi,
>
> Would it help to add some println()s to your rmi server
> so you could see where it falls out ? Or does the jvm
> exit from within the rebind() call ?
>
> Nick
>
> Pratip Kar wrote:
>
> > Hi,
> >
> > I am running a simple RMI test application. But after doing the
> > "Naming.rebind(....)" the server simply comes out. There is no exception
> > or anything. But instead of waiting for the Client connection, it exits
> > normally after binding to rmiregistry.
> >
> > My system has RH6.0 with glibc2.1. I am not able to run the native
> > thread executables, so I was trying with the green thread ones. Can that
> > be a problem ?
> >
> > Pratip
> >
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
