Search Mailing List Archives
[protege-discussion] Unable to connect to remote protege server using Ontology rich client invoked from webprotege
tudorache at stanford.edu
Thu Nov 12 17:32:28 PST 2009
Please enable the Java console, as described here:
and post the messages you see in the console.
Questions: Did you connect to the Protege server from the rich client
from the same machine as the web client?
What Java version are you using?
> Tania Tudorache <tudorache <at> stanford.edu> writes:
>> OK, thanks.
>> It looks like the connection times out. Most likely this is a firewall
>> problem. The Protege client and server communicate using two ports
>> through RMI.
>> If the client is on a different machine it will try to access the
>> server using the two ports. The solution is to open two ports on your
>> server machine (you can choose whichever ports you want), then
>> configure the Protege server to use these ports (see ), and then
>> tell WebProtege about this, too . These are both easy configuration
>> to make (basically just uncomment two lines in a script and a config
>> If you change the ports, you should also edit the jnlp file, and add
>> the port to the server host name in the arguments section. Something
> Thank you Tania,
> I don't think there's a firewall issue - there are no firewalls
> configured between the machines and the
> standard client (Protege 3.4.1) can connect without any
> problem to the server - only the web-start rich
> client has a problem. Any other idea what I could try?
> protege-discussion mailing list
> protege-discussion at lists.stanford.edu
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the protege-discussion