Troubleshooting problems with the Java Proxy

The Java Proxy component and the Password Store component of the Password Synchronizer logs messages to the file that is specified by the JavaLogFile parameter. The default log file is proxy.log.

For more information about the javaLogFile parameter, see javaLogFile configuration parameter.

• Check the initialization status.The plug-in starts the Java proxy on initialization. When the Java Proxy starts, it logs a status message.
  • Verify whether the log file exists, proxy.log.
  • Verify whether the log contains the message of successful initialization.
  • Verify whether the timestamp of the initialization message is recent. There can be some messages that are left in the log from previous run of the proxy.

  Non-availability of recent initialization status in the log indicates that the proxy is not running or failed on initialization before it can write to its log. A general Java Proxy standard or error log is available in the authentication_folder/proxy.stdout.log file. The authentication_folder is the folder that contains the plug-in configuration file pwsync.props. If the log file has a message such as java.lang.NoClassDefFoundException, possible reasons are:

  • The class path of the Proxy is incomplete:

    Verify whether all the third-party libraries that are required to run the Password Store are added to the jars folder of the plug-ins. The default path is TDI_install_dir/pwd_plugins/jars/. If the class path generated by the startProxy script is longer than the length of a shell command, which is allowed by your operating system, the JavaProxy might not run.

  • Errors that you encounter when you run the startProxy.bat or startProxy.sh manually:

    Verify whether the startProxy script runs correctly from a command prompt.

    On Linux or UNIX, make sure that the configuration of the scripts path is valid for your operating system environment. On Windows, the startup scripts of the plug-ins use JScript to gather the class path. Make sure that the Windows Script Host (WSH) is enabled. If the WSH is disabled on your system, you receive the following message:

    Windows Script Host access is disabled on this machine. 
    Contact your administrator for details.

    when you double-click the TDI_install_dir/pwd_plugins/bin/worker.js file.
  • When an unexpected error occurs on initialization:

    Check whether the log file of the plug-in for error messages that are related to the startup of the Java Proxy process.

    Locate the command string that the plug-in uses to start the Java Proxy in the plug-in log, and run it in a command shell.

• Check for execution errors.

Parent topic:

Troubleshooting problems with the Password Synchronizers