XIC: "nohup: java: File name too long" error running ./startup.sh - XIC fails to start and deployment log is empty

XIC: "nohup: java: File name too long" error running ./startup.sh - XIC fails to start and deployment log is empty

The JAVA installation location should be added to the PATH environment variable. The syntax below should be used, specifying the location of JAVA. In the example, JAVA is installed at /usr/tandem/nssjava/jdk180_l80/bin.

Syntax: export PATH="$PATH:/usr/tandem/nssjava/jdk180_h80/bin"


If you are unable to locate the solution needed or if you need additional assistance please Click Here to open a case from our Customer Care Portal.


    • Related Articles

    • XIC: Updating certificates in the XIC_HPE.jks

      1. Grant WRITE permissions on the XIC_HPE.jks and its related files, such as XIC_HPE_EP.ssl, XIC_HPE_PrivatePair.pem, and XIC_HPE_PubKey.pem 2. Execute the 'importCert.sh' script in the XIC installation's base directory, for example, ...

    • XIC: Where can the XIC log files be found?

      There are three XIC log files: access.log error.log http.log The full log name will be in the following format: xic_<instance>_xxxx.log Where: <instance> is the name of the XIC instance provided at the time of installation. Usually, this is the name ...

    • XIC 1.36 or below release is not working with Java 11.

      XIC has to be reinstalled after setting up PATH for Java version 1.80 1. Shutdown XIC 2. Remove the XIC or rename the XIC directory, for example, mv ./webservices ./webservices_bak 3. Set PATH to Java version 1.80, for example, ...

    • XMA: Cannot Start $XMA Pathway - Startup attempt fails with no errors

      Check the HOMETERM value in the MACONF file. The MACONF file is found in the XYGATEMA installation subvolume. The HOMETERM value must be a valid / existing home terminal process name. Sample MACONF file: PATHMON_NAME $XMA PRIORITY 030 PERUSE_OBJECT ...

    • XMA: Can't start iTP Webserver Mover - SQL Error

      Probable cause is that the iTP webserver mover is attempting to process a file type that is not yet supported. Several file formats are not currently supported by the iTP mover: HTTPD log support. The format is not CLF format but a hybrid of access ...