Protege & Java RMI Issues - Help Please!
Posted: 12 Aug 2010, 10:20
Hi All,
I've been trying to set up essential in a multi-user setup for the last week and am stumped! I've installed Protege 3.4.4 and the latest version of essential, created and moved the project onto the mySQL backend using the migrate project function, created a service to auto-start the protege app, but still can't get the actual protege server to start!
Executing the run_protege_server.bat file gives me the below error message:
executing the RMI executable directly, explicitly refferencing the RMI port 1099 gives me the below:
What is really strange is that I cannot telnet to port 1099, meaning that there is nothing listening on that port.
The question I have is is there anyway to change the default port which is used for rmi when the protege run_protege_server is used? I've tried stating a differing port in the run_protege_server.bat:
where 1100 is the new port number, but I still get an identical error message. Executing the rmi executable from the command line with the 5100 and 5200 ports listed in the run_protege_server.bat file does work and I can telnet successfully. Is this a logical fault analysis or am I completely off tangent here?!
Any help greatly appreciated!
Cheers,
Gary
I've been trying to set up essential in a multi-user setup for the last week and am stumped! I've installed Protege 3.4.4 and the latest version of essential, created and moved the project onto the mySQL backend using the migrate project function, created a service to auto-start the protege app, but still can't get the actual protege server to start!
Executing the run_protege_server.bat file gives me the below error message:
Code: Select all
Protege server is starting...
Protege 3.4.4 Build 579, JVM 1.6.0_20-b02, memory=506M, Windows 2003, encoding=U
TF-8, language=en, country=GB
Server port = 5200, registry port = 5100, compressed stream
Save interval sec=300
Using metaproject from: file:/D:/Program%20Files/Protege_3.4.4/examples/server/m
etaproject.pprj
SEVERE: java.rmi.ConnectException: Connection refused to host: 10.32.5.81; nested exception is:
java.net.ConnectException: Connection refused: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
at sun.rmi.server.UnicastRef.newCall(Unknown Source)
at sun.rmi.registry.RegistryImpl_Stub.rebind(Unknown Source)
at edu.stanford.smi.protege.server.Server.bindName(Unknown Source)
at edu.stanford.smi.protege.server.Server.initialize(Unknown Source)
at edu.stanford.smi.protege.server.Server.<init>(Unknown Source)
at edu.stanford.smi.protege.server.Server.startServer(Unknown Source)
at edu.stanford.smi.protege.server.Server.main(Unknown Source)
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(Unknown S
ource)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Unknown S
ource)
... 10 more
-- Server.bindName()
SEVERE: server startup failed -- java.rmi.ConnectException: Connection refused t
o host: 10.32.5.81; nested exception is:
java.net.ConnectException: Connection refused: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
at sun.rmi.server.UnicastRef.newCall(Unknown Source)
at sun.rmi.registry.RegistryImpl_Stub.rebind(Unknown Source)
at edu.stanford.smi.protege.server.Server.bindName(Unknown Source)
at edu.stanford.smi.protege.server.Server.initialize(Unknown Source)
at edu.stanford.smi.protege.server.Server.<init>(Unknown Source)
at edu.stanford.smi.protege.server.Server.startServer(Unknown Source)
at edu.stanford.smi.protege.server.Server.main(Unknown Source)
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(Unknown S
ource)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Unknown S
ource)
... 10 more
Code: Select all
C:\Program Files\Java\jre6\bin>rmiregistry 1099
java.rmi.server.ExportException: Port already in use: 1099; nested exception is:
java.net.BindException: Address already in use: JVM_Bind
at sun.rmi.transport.tcp.TCPTransport.listen(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.exportObject(Unknown Source)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(Unknown Source)
at sun.rmi.transport.LiveRef.exportObject(Unknown Source)
at sun.rmi.server.UnicastServerRef.exportObject(Unknown Source)
at sun.rmi.registry.RegistryImpl.setup(Unknown Source)
at sun.rmi.registry.RegistryImpl.<init>(Unknown Source)
at sun.rmi.registry.RegistryImpl.main(Unknown Source)
Caused by: java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(Unknown Source)
at java.net.ServerSocket.bind(Unknown Source)
at java.net.ServerSocket.<init>(Unknown Source)
at java.net.ServerSocket.<init>(Unknown Source)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(Unk
nown Source)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(Unk
nown Source)
at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(Unknown Source)
... 8 more
The question I have is is there anyway to change the default port which is used for rmi when the protege run_protege_server is used? I've tried stating a differing port in the run_protege_server.bat:
Code: Select all
start /D %JDKBIN% /min rmiregistry.exe 1100
Any help greatly appreciated!
Cheers,
Gary