[Mulgara-general] RMI port conflict

[Paul Gearon]

This process is wrong, since you only told Mulgara not to start an RMI  
server.  You also needed to tell Mulgara which port it should find the  
new server.

Unfortunately, even if you do it right, it looks like the server still  
won't work.  I just tried it now, and it complains that it can't find  
a _Stub class for the session factory.  This has come about because  
RMI no longer generates _Skel and _Stub classes by default in Java 5.   
Anyway, it looks broken for the moment.  I'm looking into it now, and  
will let you know as soon as I have something for you.

Paul



On Feb 5, 2008, at 3:58 PM, Jain, Kokil wrote:

> Thanks for the reply.
>
> Started rmiregistry on port 1299. Started Mulgara with
>
> java -jar mulgara-1.1.1.jar -n
>
> Get the same exception:
>
> Mulgara Semantic Store Version 1.1.1 (Build 1.1.1.local)
> 2008-02-05 16:49:23,023 INFO  Database - Host name aliases for this
> server are:
> [lt-kjain, localhost, 127.0.0.1, 10.10.10.10]
> 2008-02-05 16:50:06,507 ERROR EmbeddedMulgaraServer - Exception in  
> main
> 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
>
>
> -----Original Message-----
> From: mulgara-general-bounces at mulgara.org
> [mailto:mulgara-general-bounces at mulgara.org] On Behalf Of Paul Gearon
> Sent: Tuesday, February 05, 2008 12:12 PM
> To: Mulgara General
> Subject: Re: [Mulgara-general] RMI port conflict
>
> 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
>>
>>
> _______________________________________________
> Mulgara-general mailing list
> Mulgara-general at mulgara.org
> http://mulgara.org/mailman/listinfo/mulgara-general
> _______________________________________________
> Mulgara-general mailing list
> Mulgara-general at mulgara.org
> http://mulgara.org/mailman/listinfo/mulgara-general