[Mulgara-general] RMI port conflict

[Paul Gearon]

Sorry, I was on the road last week and didn't see this.

It looks like it's trying to make a connection and can't.  Without
checking the code, I'm wondering if the RMI port override is telling
the Mulgara server to not start up it's own registry, and instead
connect to one on that port.

Have a go at running rmiregistry on another port, and then start up
Mulgara with the RMI option.  If it's still not working, then let me
know and I'll debug what's going wrong.

Regards,
Paul Gearon

On Jan 25, 2008 7:47 AM, Jain, Kokil <KJain at mcdonaldbradley.com> wrote:
>
>
>
>
> Hi,
>
>
>
> Is there some other way of running mulgara where port 1099 is not free?
>
>
>
> I tried using "java -jar mulgara-1.1.1.jar -r 1299 " with no luck.
>
>
>
> Mulgara Semantic Store Version 1.1.1 (Build 1.1.1.local)
>
>  INFO [main] (EmbeddedMulgaraServer.java:739) - RMI Registry started
> automatical
>
> ly on port 1299
>
> 0 [main] INFO org.mulgara.server.EmbeddedMulgaraServer  - RMI Registry
> started a
>
> utomatically on port 1299
>
>
>
> but then it fails.
>
>
>
> javax.naming.ServiceUnavailableException [Root exception is
> java.rmi.ConnectExce
>
> ption: Connection refused to host: localhost; nested exception is:
>
>         java.net.ConnectException: Connection refused: connect]
>
>         at
> com.sun.jndi.rmi.registry.RegistryContext.rebind(RegistryContext.java
>
> :138)
>
>         at
> com.sun.jndi.rmi.registry.RegistryContext.rebind(RegistryContext.java
>
>
>
> I have been struggling with it for sometime and will appreciate any help.
>
>
>
> Thanks.
> _______________________________________________
> Mulgara-general mailing list
> Mulgara-general at mulgara.org
> http://mulgara.org/mailman/listinfo/mulgara-general
>
>