Troubleshooting

In general, if you experience any problems check the Gems command window for errors.

Gems fails to start

If Gems fails to start check the following:

  • JRE 1.6.0 or higher is installed and the bin directory is in your path. To check this open a command prompt and type java -version
  • TIBCO EMS is installed
  • If EMS is not installed in the standard tibco home directory set the %TIBEMS_ROOT% variable in the rungems.cmd file to the EMS installation directory
  • Gems fails to connect

    If Gems fails to connect to an EMS server check the following:

  • The supplied URL's hostname and TCP port are correct
  • The supplied EMS user name and password is correct
  • The supplied EMS user has administrative rights
  • There is network connectivity to the EMS server machine
  • "Not Permitted" Error when using Destination Monitors

    If you have created a new administrator user for Gems and you also wish to use the Topic/Queue monitor or Request/Reply monitor, you must also grant this user subscribe permission to the $sys.monitor topics. See the Security Permissions section for details.

    "Not Permitted" Error when starting Gems

    If you have created a new administrator user for Gems and you also wish to use the Event Monitor feature you must also grant this user subscribe permission to the $sys.monitor topics that are configured in the EventMonitor section in the servers.xml file. See the Security Permissions section for details.

    Gems display freezes

    If the Gems display appears to be frozen, this may be because an EMS server is in recovery mode.

    When an EMS server activates, either as a result of a failover or on restart, the server has to recover all pending messages that were saved to disk. In exceptional cases, where there are a large number of pending messages, this may take a few moments. During this time the server accepts connections but will not process any requests until the server has fully recovered. Wait for the server to recover, and Gems will continue normally.

    Cannot browse pending messages

    Messages that have been sent to a client application and not yet acknowledged, or messages that have been sent to the EMS client library and held in a prefetch queue CANNOT be browsed. If this condition persists its possible that the client application has stalled and may need to be shutdown.