> This means that either there is no Registry running at port 1900 of the
> host 192.168.1.101, or there is a firewall in the way.
Well I found out that something else was using port 1900, so I started
it on a different port. my next question is how can I bundle my app
as a jar such that is starts up rmiregistry for me instead of having
to have someone open up a command prompt, run rmiregistry, then open
another prompt and run the app. this is on windows by the way.
thanks
Arne Vajhøj - 27 Mar 2007 03:59 GMT
>> This means that either there is no Registry running at port 1900 of the
>> host 192.168.1.101, or there is a firewall in the way.
>
> Well I found out that something else was using port 1900, so I started
> it on a different port.
:-)
> my next question is how can I bundle my app
> as a jar such that is starts up rmiregistry for me instead of having
> to have someone open up a command prompt, run rmiregistry, then open
> another prompt and run the app.
Run the rmiregistry within your server app.
Arne
Esmond Pitt - 27 Mar 2007 05:52 GMT
> Well I found out that something else was using port 1900, so I started
> it on a different port.
Something wrong with 1099? the default RMI Registry port? which has been
reserved for RMI by IANA for ten years?
> my next question is how can I bundle my app
> as a jar such that is starts up rmiregistry for me instead of having
> to have someone open up a command prompt, run rmiregistry, then open
> another prompt and run the app. this is on windows by the way.
java.rmi.registry.LocateRegistry.createRegistry()