Troubleshooting Client Server Connections - Revision history

Csnyulas: /* Java 1.6.0_29 and 1.7 rmiregistry issue */

2012-01-24T23:48:01Z

‎Java 1.6.0_29 and 1.7 rmiregistry issue

TaniaTudorache: /* Java 1.6.0_29 and 1.7 rmiregistry issue */

2012-01-24T21:08:58Z

‎Java 1.6.0_29 and 1.7 rmiregistry issue

TaniaTudorache: /* Java 1.6.0_29 and 1.7 rmiregistry issue */

2012-01-24T21:06:48Z

‎Java 1.6.0_29 and 1.7 rmiregistry issue

TaniaTudorache at 21:00, January 24, 2012

2012-01-24T21:00:34Z

TaniaTudorache at 20:58, January 24, 2012

2012-01-24T20:58:58Z

TaniaTudorache at 23:54, August 19, 2011

2011-08-19T23:54:43Z

TaniaTudorache at 23:41, August 19, 2011

2011-08-19T23:41:44Z

Dustinburke: /* Configuration */

2010-03-05T18:55:18Z

‎Configuration

Dustinburke: /* Configuration */

2010-03-05T18:52:16Z

‎Configuration

Dustinburke: /* Configuration */

2010-03-05T18:51:54Z

‎Configuration

@@ Line 116: / Line 116: @@
 There is a [http://www.oracle.com/technetwork/java/javase/6u29-relnotes-507960.html known bug] in [http://www.oracle.com/technetwork/java/javase/6u29-relnotes-507960.html Java 1.6.0_29] and [http://www.oracle.com/technetwork/java/javase/7u1-relnotes-507962.html Java 1.7] that occurs when a RMI server attempts to bind an exported object which includes codebase annotations using the "file:" URL scheme. There is no workaround for this issue, except using a different scheme (e.g. http or ftp) for specifying the code base, or using a different version of Java.
-If this issue affects you, you will get an exception when starting the Protege server:
+If this issue affects you, you will get an exception when starting the Protege server with a stack trace similar to this:
 <pre>
 SEVERE: server startup failed -- java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
      java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
@@ Line 128: / Line 127: @@
 </pre>
-The workaround is to use a different version of Java. Another workaround is to serve the protege code base from a different location (e.g. http or ftp) and edit the [[Protege_Client_Server_Tutorial_Setup#Starting_the_Protege_server_using_the_run_protege_server_script_.28Recommended.29|run_protege script]] accordingly.
+To avoid getting this exception you can run the Protege server with a different version of Java that does not contain this bug (i.e. until the bug is fixed in one of the upcoming Java versions, you will need to downgrade to Java 1.6.0_26 or earlier). Another workaround is to serve the protege code base from a different location (e.g. http or ftp) and edit the [[Protege_Client_Server_Tutorial_Setup#Starting_the_Protege_server_using_the_run_protege_server_script_.28Recommended.29|run_protege script]] accordingly.
 = Networks, Firewalls and Telnet =

@@ Line 128: / Line 128: @@
 </pre>
-The workaround is to use a different version of Java. Another workaround is to serve the protege code base from a different location (e.g. http or ftp).
+The workaround is to use a different version of Java. Another workaround is to serve the protege code base from a different location (e.g. http or ftp) and edit the [[Protege_Client_Server_Tutorial_Setup#Starting_the_Protege_server_using_the_run_protege_server_script_.28Recommended.29|run_protege script]] accordingly.
 = Networks, Firewalls and Telnet =

@@ Line 114: / Line 114: @@
 = Java 1.6.0_29 and 1.7 rmiregistry issue =
-There is a [http://www.oracle.com/technetwork/java/javase/6u29-relnotes-507960.html known bug] in Java 1.6.0_29 and [http://www.oracle.com/technetwork/java/javase/7u1-relnotes-507962.html Java 1.7] that occurs when a RMI server attempts to bind an exported object which includes codebase annotations using the "file:" URL scheme. There is no workaround for this issue, except using a different scheme (e.g. http or ftp) for specifying the code base, or using a different version of Java.
+There is a [http://www.oracle.com/technetwork/java/javase/6u29-relnotes-507960.html known bug] in [http://www.oracle.com/technetwork/java/javase/6u29-relnotes-507960.html Java 1.6.0_29] and [http://www.oracle.com/technetwork/java/javase/7u1-relnotes-507962.html Java 1.7] that occurs when a RMI server attempts to bind an exported object which includes codebase annotations using the "file:" URL scheme. There is no workaround for this issue, except using a different scheme (e.g. http or ftp) for specifying the code base, or using a different version of Java.
 If this issue affects you, you will get an exception when starting the Protege server:
@@ Line 129: / Line 129: @@
 The workaround is to use a different version of Java. Another workaround is to serve the protege code base from a different location (e.g. http or ftp).
 = Networks, Firewalls and Telnet =

@@ Line 2: / Line 2: @@
 <span class="orangeBoxTitle">Client-Server Troubleshooting</span><br /><br />
-'''This page contains common problems and exceptions that occur when running the Protege client-sever.
+'''This page contains common problems and exceptions that occur when running the Protege client-sever and is part of the [[Protege_Client-Server_Tutorial|Protege client-server tutorial]]. This page is being updated as issues arise.'''
 </div>

← Older revision		Revision as of 20:58, January 24, 2012
Line 111:		Line 111:

	Sometime, not very often, a problem arises where the rmiregistry needs to be restarted. So if the client-server has been running fine and you are suddenly having mysterious problems, try killing the rmiregistry and restarting it. I don't know anyone who understands this issue.		Sometime, not very often, a problem arises where the rmiregistry needs to be restarted. So if the client-server has been running fine and you are suddenly having mysterious problems, try killing the rmiregistry and restarting it. I don't know anyone who understands this issue.
		+
		+
		+	= Java 1.6.0_29 and 1.7 rmiregistry issue =
		+
		+	There is a [http://www.oracle.com/technetwork/java/javase/6u29-relnotes-507960.html known bug] in Java 1.6.0_29 and [http://www.oracle.com/technetwork/java/javase/7u1-relnotes-507962.html Java 1.7] that occurs when a RMI server attempts to bind an exported object which includes codebase annotations using the "file:" URL scheme. There is no workaround for this issue, except using a different scheme (e.g. http or ftp) for specifying the code base, or using a different version of Java.
		+
		+	If this issue affects you, you will get an exception when starting the Protege server:
		+
		+	<pre>
		+
		+	SEVERE: server startup failed -- java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
		+	java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
		+	java.lang.ClassNotFoundException: access to class loader denied
		+	Caused by
		+	.....
		+	Caused by: java.security.AccessControlException: access denied (java.io.FilePermission C:\Users\csnyulas\workspace\Protege-core\build\dist\- read)
		+	</pre>
		+
		+	The workaround is to use a different version of Java. Another workaround is to serve the protege code base from a different location (e.g. http or ftp).

@@ Line 103: / Line 103: @@
 This happens if rmiregistry does not find the path to the protege.jar, which is specified in the CODEBASE_URL in your <code>run_protege_server</code> script. Especially if running the server on a Windows machine, please make sure that you edit this line from your run_protege_server script to match the path to the protege.jar from your Protege installation folder:
-  set CODEBASE_URL=file:/c:/program%20files/protege_3.4.7/protege.jar
+  set CODEBASE_URL=file:/c:/program%%20files/protege_3.4.7/protege.jar
-(space is encoded as %20).
+(space is encoded as %%20).

← Older revision		Revision as of 18:55, March 5, 2010
Line 145:		Line 145:
	$JAVA_PATH/rmiregistry $RMI_REG_PORT &		$JAVA_PATH/rmiregistry $RMI_REG_PORT &
	* Make sure you configure your firewall to allow TCP traffic to the RMI_REG_PORT and RMI_SERV_PORT		* Make sure you configure your firewall to allow TCP traffic to the RMI_REG_PORT and RMI_SERV_PORT
		+
		+	= See Also =
		+	* [[Protege Client Server Tutorial Advanced]]

@@ Line 133: / Line 133: @@
 To resolve configuration issues arising from NAT firewalls, here's a simple walkthrough that hopefully helps someone.
-# In your Protege client application, edit the "protege.properties" file in the installation directory and add the line (or modify if it already exists), where ''hostname'' is the HOSTNAME (not the domain name) and ''RMI_REG_PORT'' is the RMI Registry Port.  By default this is 1099, but can be changed from the server configuration.  The global IP Address of the server also works in place of the hostname, but a common mistake is to set this to the local IP address of the server.
+* In your Protege client application, edit the "protege.properties" file in the installation directory and add the line (or modify if it already exists), where ''hostname'' is the HOSTNAME (not the domain name) and ''RMI_REG_PORT'' is the RMI Registry Port.  By default this is 1099, but can be changed from the server configuration.  The global IP Address of the server also works in place of the hostname, but a common mistake is to set this to the local IP address of the server.
   edu.stanford.smi.protege.server.ServerPanel.host_name=''hostname''\:''RMI_REG_PORT''
-# In your Protege Server installation, make the following changes to "run_protege_server.sh":
+* In your Protege Server installation, make the following changes to "run_protege_server.sh":
-#* For the HOSTNAME_PARAM variable, replace `hostname` with the actual hostname of your machine (same as specified from the client side so you know its globally-routable).  A common mistake is to set this to "localhost" or to a locally routable hostname.
+** For the HOSTNAME_PARAM variable, replace `hostname` with the actual hostname of your machine (same as specified from the client side so you know its globally-routable).  A common mistake is to set this to "localhost" or to a locally routable hostname.
-#* Add the following lines before the PORTOPTS variable is defined:
+** Add the following lines before the PORTOPTS variable is defined:
   RMI_REG_PORT=1099
   RMI_SERV_PORT=5200
-#* Uncomment the line defining the PORTOPTS variable and change it to:
+** Uncomment the line defining the PORTOPTS variable and change it to:
   PORTOPTS="-Dprotege.rmi.server.port=$RMI_SERV_PORT -Dprotege.rmi.registry.port=$RMI_REG_PORT"
-#* Add the RMI_REG_PORT argument to the rmiregistry command, like this:
+** Add the RMI_REG_PORT argument to the rmiregistry command, like this:
   $JAVA_PATH/rmiregistry $RMI_REG_PORT &
-# Make sure you configure your firewall to allow TCP traffic to the RMI_REG_PORT and RMI_SERV_PORT
+* Make sure you configure your firewall to allow TCP traffic to the RMI_REG_PORT and RMI_SERV_PORT