Running Gateway Debugging Traces

Edit the rmireg startup script and add the parameter -debug to the Java command line for the Gateway java process, then restart the Gateway and the RMIDs. For example, add the following in rmireg.sh or rmireg.bat:

c:\j2sdk1.4.2_03\bin\java -cp %CLASSURL% -Djava.rmi.server.codebase=file:%CLASSURL% 
-Djava.security.policy=e:\enovia\server\<platform>\docs\security\rmid.policy 
-Djava.rmi.activation.port=1099 com.matrixone.jdl.eMatrix -debug -servers //
localhost:1100,//localhost:1101,//localhost:1102 //localhost:1099

Be sure to add the -debug flag to the Java command line and not the RMID command line as doing so will likely prevent the server from starting successfully.

The trace output will be sent to stdout. The following are examples of the debug gateway messages:

Message		Meaning
returning `RMI SERVER IDENTIFIER`		The gateway will send ENOVIA Live Collaboration operations to this RMI Server.
`RMI SERVER IDENTIFIER` not responding		The Gateway tried to contact this RMI Server, but it failed to respond.
no running server found		The Gateway could not find any RMI server to which it could send ENOVIA Live Collaboration operations.
For Quiesce Mode Only:
	operation count exceeded, ops=`NUMBER`	This RMI Server has exceeded its number of allotted operations; it will be quiesced and the gateway will send ENOVIA Live Collaboration operations to another RMI Server instead.
	timeout interval exceeded, interval=`NUMBER`	This RMI Server has exceeded a specified amount of run time (in microseconds); it will be quiesced and the gateway will send ENOVIA Live Collaboration operations to another RMI Server instead.
	quiescing, prev=`RMI SERVER IDENTIFIER`	This RMI Server is being quiesced and the gateway will send ENOVIA Live Collaboration operations to another RMI Server instead.