Search Mailing List Archives


Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-discussion] Unable to connect to remote protege server using Ontology rich client invoked from webprotege

Timothy Redmond tredmond at stanford.edu
Mon Nov 16 13:24:53 PST 2009


> Any ideas?

The 1099 and the no port  cases both represent  significant  progress  
in the right direction.

What has happened is that you have successfully connected to the  
rmiregistry and picked up an address for the server.   Then something  
goes wrong in the conversation with the server.  The rmiregistry says   
that the server is located at the ip address 66.116.103.187 and the  
port 5200.  Can you confirm that this is correct?   What happens if  
you telnet to the address 66.116.103.187 and port 5200?  Does it  
connect?

If so then we have a new problem to debug but we have made a lot of  
forward progress.

-Timothy


On Nov 16, 2009, at 12:57 PM, Kai wrote:

> Timothy Redmond <tredmond <at> stanford.edu> writes:
>
>>
>> It sounds like that is the problem.   I don't know why you can't  
>> hit the
>> ok button without the :5200.   Try :1099 instead.
>>
>> -Timothy
>
> Here is the log I get from no port:
> Nov 16, 2009 12:53:43 PM edu.stanford.smi.protege.server.ServerPanel
> createSession
> INFO: Server ref = Server_Stub[UnicastRef2 [liveRef:
> [endpoint:[66.116.103.187:5200,edu.stanford.smi.protege.server.socket.
> RmiSocketFactory at 2](remote),objID:[-723b6d2e:124fe974856:-8000, 0]]]]
>
>
> Here's the log I get from using :1099:
> Nov 16, 2009 12:53:50 PM edu.stanford.smi.protege.server.ServerPanel
> createSession
> INFO: Server ref = Server_Stub[UnicastRef2 [liveRef:
> [endpoint:[66.116.103.187:5200,edu.stanford.smi.protege.server.socket.
> RmiSocketFactory at 2](remote),objID:[-723b6d2e:124fe974856:-8000, 0]]]]
>
> with the 5200 I get the:
> SEVERE: java.rmi.ConnectIOException: error during JRMP connection
> establishment; nested exception is:
> 	java.io.EOFException
> 	at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.
> java:273)
> 	at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.
> java:171)
> 	at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
> 	at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
> 	at java.rmi.Naming.lookup(Naming.java:84)
> ...
>
> Any ideas?
>
> Kai.
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03




More information about the protege-discussion mailing list