How to Configure Web Interface 5.4 to Start Java Receiver Deployment

This article is intended for Citrix administrators and technical teams only.Non-admin users must contact their company’s Help Desk/IT support team and can refer to CTX297149 for more information

This article explains how to deploy the Citrix Java Receiver from Web Interface 5.4 and to configure clients to start ICA sessions in Citrix Java Receiver.

Requirements

  • JRE 1.16 32 bit (tested with JRE 1.16 Update 37:32-bit)

  • Pop-up blockers must be enabled and the site must be added to trusted sites

Background

This has been tested from a Windows 7 64-bit OS with Internet Explorer 9, XenApp 6.5, Web Interface 5.4, and Java Runtime Environment 1.16 Update 37 (32-bit).

Related:

  • No Related Posts

Untitled


There are several possible causes for the error, some are listed bellow with suggestions to help fix and/or track them further:

– Cause: Misconfiguration of the JVM heap sizes

Suggestions: Clear any custom settings to the Initial heap size and Max heap size on the properties of the driver set, misc tab. Then try to load the vrdim modules. ****Too large of heap settings accounts for about 90% of these issues****

Additional detail on these errors can be found using the +misc flag in ndstrace. All jvmloader messages come under the MISC flag on Linux/Unix, and under the MISC OTHER flag on dstrace.dlm (Windows). Unfortunately there is no way of seeing them on Netware ( but we can always check the SYS:/ETC/JAVA.CFG file there)

Cause LD_LIBRARY_PATH not set properly causing “error: libjvm.so: cannot open shared object file: No such file or directory” and “JVM interface initialization failed <failed, -299 (0xfffffed5)>, unloading DIRXML” errors.

Verify that echo $LD_LIBRARY_PATH returns a valid path. . /opt/novell/eDirectory/bin/ndspath will get it running for the current session, then restarting ndsd should load vrdim. The path can be set by exporting it after logging in as root, or adding it to an env_idm file in /etc/opt/novell/eDirectory/conf directory.

LD_LIBRARY_PATH=//opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64://opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/server://opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/native_threads::$LD_LIBRARY_PATH:/opt/novell/eDirectory/lib64/apr:/opt/novell/eDirectory/lib64:/opt/novell/lib64:/opt/novell/eDirectory/lib64/nds-modules:$LD_LIBRARY_PATH

Related:

Untitled


There are several possible causes for the error, some are listed bellow with suggestions to help fix and/or track them further:

– Cause: Misconfiguration of the JVM heap sizes

Suggestions: Clear any custom settings to the Initial heap size and Max heap size on the properties of the driver set, misc tab. Then try to load the vrdim modules. ****Too large of heap settings accounts for about 90% of these issues****

Additional detail on these errors can be found using the +misc flag in ndstrace. All jvmloader messages come under the MISC flag on Linux/Unix, and under the MISC OTHER flag on dstrace.dlm (Windows). Unfortunately there is no way of seeing them on Netware ( but we can always check the SYS:/ETC/JAVA.CFG file there)

Cause LD_LIBRARY_PATH not set properly causing “error: libjvm.so: cannot open shared object file: No such file or directory” and “JVM interface initialization failed <failed, -299 (0xfffffed5)>, unloading DIRXML” errors.

Verify that echo $LD_LIBRARY_PATH returns a valid path. . /opt/novell/eDirectory/bin/ndspath will get it running for the current session, then restarting ndsd should load vrdim. The path can be set by exporting it after logging in as root, or adding it to an env_idm file in /etc/opt/novell/eDirectory/conf directory.

LD_LIBRARY_PATH=//opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64://opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/server://opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/native_threads::$LD_LIBRARY_PATH:/opt/novell/eDirectory/lib64/apr:/opt/novell/eDirectory/lib64:/opt/novell/lib64:/opt/novell/eDirectory/lib64/nds-modules:$LD_LIBRARY_PATH

Related:

  • No Related Posts

Untitled


There are several possible causes for the error, some are listed bellow with suggestions to help fix and/or track them further:

– Cause: Misconfiguration of the JVM heap sizes

Suggestions: Clear any custom settings to the Initial heap size and Max heap size on the properties of the driver set, misc tab. Then try to load the vrdim modules. ****Too large of heap settings accounts for about 90% of these issues****

Additional detail on these errors can be found using the +misc flag in ndstrace. All jvmloader messages come under the MISC flag on Linux/Unix, and under the MISC OTHER flag on dstrace.dlm (Windows). Unfortunately there is no way of seeing them on Netware ( but we can always check the SYS:/ETC/JAVA.CFG file there)

Cause LD_LIBRARY_PATH not set properly causing “error: libjvm.so: cannot open shared object file: No such file or directory” and “JVM interface initialization failed <failed, -299 (0xfffffed5)>, unloading DIRXML” errors.

Verify that echo $LD_LIBRARY_PATH returns a valid path. . /opt/novell/eDirectory/bin/ndspath will get it running for the current session, then restarting ndsd should load vrdim. The path can be set by exporting it after logging in as root, or adding it to an env_idm file in /etc/opt/novell/eDirectory/conf directory.

LD_LIBRARY_PATH=//opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64://opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/server://opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/native_threads::$LD_LIBRARY_PATH:/opt/novell/eDirectory/lib64/apr:/opt/novell/eDirectory/lib64:/opt/novell/lib64:/opt/novell/eDirectory/lib64/nds-modules:$LD_LIBRARY_PATH

Related:

Untitled


There are several possible causes for the error, some are listed bellow with suggestions to help fix and/or track them further:

– Cause: Misconfiguration of the JVM heap sizes

Suggestions: Clear any custom settings to the Initial heap size and Max heap size on the properties of the driver set, misc tab. Then try to load the vrdim modules. ****Too large of heap settings accounts for about 90% of these issues****

Additional detail on these errors can be found using the +misc flag in ndstrace. All jvmloader messages come under the MISC flag on Linux/Unix, and under the MISC OTHER flag on dstrace.dlm (Windows). Unfortunately there is no way of seeing them on Netware ( but we can always check the SYS:/ETC/JAVA.CFG file there)

Cause LD_LIBRARY_PATH not set properly causing “error: libjvm.so: cannot open shared object file: No such file or directory” and “JVM interface initialization failed <failed, -299 (0xfffffed5)>, unloading DIRXML” errors.

Verify that echo $LD_LIBRARY_PATH returns a valid path. . /opt/novell/eDirectory/bin/ndspath will get it running for the current session, then restarting ndsd should load vrdim. The path can be set by exporting it after logging in as root, or adding it to an env_idm file in /etc/opt/novell/eDirectory/conf directory.

LD_LIBRARY_PATH=//opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64://opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/server://opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/native_threads::$LD_LIBRARY_PATH:/opt/novell/eDirectory/lib64/apr:/opt/novell/eDirectory/lib64:/opt/novell/lib64:/opt/novell/eDirectory/lib64/nds-modules:$LD_LIBRARY_PATH

Related:

  • No Related Posts

Untitled


There are several possible causes for the error, some are listed bellow with suggestions to help fix and/or track them further:

– Cause: Misconfiguration of the JVM heap sizes

Suggestions: Clear any custom settings to the Initial heap size and Max heap size on the properties of the driver set, misc tab. Then try to load the vrdim modules. ****Too large of heap settings accounts for about 90% of these issues****

Additional detail on these errors can be found using the +misc flag in ndstrace. All jvmloader messages come under the MISC flag on Linux/Unix, and under the MISC OTHER flag on dstrace.dlm (Windows). Unfortunately there is no way of seeing them on Netware ( but we can always check the SYS:/ETC/JAVA.CFG file there)

Cause LD_LIBRARY_PATH not set properly causing “error: libjvm.so: cannot open shared object file: No such file or directory” and “JVM interface initialization failed <failed, -299 (0xfffffed5)>, unloading DIRXML” errors.

Verify that echo $LD_LIBRARY_PATH returns a valid path. . /opt/novell/eDirectory/bin/ndspath will get it running for the current session, then restarting ndsd should load vrdim. The path can be set by exporting it after logging in as root, or adding it to an env_idm file in /etc/opt/novell/eDirectory/conf directory.

LD_LIBRARY_PATH=//opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64://opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/server://opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/native_threads::$LD_LIBRARY_PATH:/opt/novell/eDirectory/lib64/apr:/opt/novell/eDirectory/lib64:/opt/novell/lib64:/opt/novell/eDirectory/lib64/nds-modules:$LD_LIBRARY_PATH

Related:

  • No Related Posts

Untitled


There are several possible causes for the error, some are listed bellow with suggestions to help fix and/or track them further:

– Cause: Misconfiguration of the JVM heap sizes

Suggestions: Clear any custom settings to the Initial heap size and Max heap size on the properties of the driver set, misc tab. Then try to load the vrdim modules. ****Too large of heap settings accounts for about 90% of these issues****

Additional detail on these errors can be found using the +misc flag in ndstrace. All jvmloader messages come under the MISC flag on Linux/Unix, and under the MISC OTHER flag on dstrace.dlm (Windows). Unfortunately there is no way of seeing them on Netware ( but we can always check the SYS:/ETC/JAVA.CFG file there)

Cause LD_LIBRARY_PATH not set properly causing “error: libjvm.so: cannot open shared object file: No such file or directory” and “JVM interface initialization failed <failed, -299 (0xfffffed5)>, unloading DIRXML” errors.

Verify that echo $LD_LIBRARY_PATH returns a valid path. . /opt/novell/eDirectory/bin/ndspath will get it running for the current session, then restarting ndsd should load vrdim. The path can be set by exporting it after logging in as root, or adding it to an env_idm file in /etc/opt/novell/eDirectory/conf directory.

LD_LIBRARY_PATH=//opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64://opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/server://opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/native_threads::$LD_LIBRARY_PATH:/opt/novell/eDirectory/lib64/apr:/opt/novell/eDirectory/lib64:/opt/novell/lib64:/opt/novell/eDirectory/lib64/nds-modules:$LD_LIBRARY_PATH

Related:

  • No Related Posts

Untitled


There are several possible causes for the error, some are listed bellow with suggestions to help fix and/or track them further:

– Cause: Misconfiguration of the JVM heap sizes

Suggestions: Clear any custom settings to the Initial heap size and Max heap size on the properties of the driver set, misc tab. Then try to load the vrdim modules. ****Too large of heap settings accounts for about 90% of these issues****

Additional detail on these errors can be found using the +misc flag in ndstrace. All jvmloader messages come under the MISC flag on Linux/Unix, and under the MISC OTHER flag on dstrace.dlm (Windows). Unfortunately there is no way of seeing them on Netware ( but we can always check the SYS:/ETC/JAVA.CFG file there)

Cause LD_LIBRARY_PATH not set properly causing “error: libjvm.so: cannot open shared object file: No such file or directory” and “JVM interface initialization failed <failed, -299 (0xfffffed5)>, unloading DIRXML” errors.

Verify that echo $LD_LIBRARY_PATH returns a valid path. . /opt/novell/eDirectory/bin/ndspath will get it running for the current session, then restarting ndsd should load vrdim. The path can be set by exporting it after logging in as root, or adding it to an env_idm file in /etc/opt/novell/eDirectory/conf directory.

LD_LIBRARY_PATH=//opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64://opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/server://opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/native_threads::$LD_LIBRARY_PATH:/opt/novell/eDirectory/lib64/apr:/opt/novell/eDirectory/lib64:/opt/novell/lib64:/opt/novell/eDirectory/lib64/nds-modules:$LD_LIBRARY_PATH

Related:

  • No Related Posts

Untitled


There are several possible causes for the error, some are listed bellow with suggestions to help fix and/or track them further:

– Cause: Misconfiguration of the JVM heap sizes

Suggestions: Clear any custom settings to the Initial heap size and Max heap size on the properties of the driver set, misc tab. Then try to load the vrdim modules. ****Too large of heap settings accounts for about 90% of these issues****

Additional detail on these errors can be found using the +misc flag in ndstrace. All jvmloader messages come under the MISC flag on Linux/Unix, and under the MISC OTHER flag on dstrace.dlm (Windows). Unfortunately there is no way of seeing them on Netware ( but we can always check the SYS:/ETC/JAVA.CFG file there)

Cause LD_LIBRARY_PATH not set properly causing “error: libjvm.so: cannot open shared object file: No such file or directory” and “JVM interface initialization failed <failed, -299 (0xfffffed5)>, unloading DIRXML” errors.

Verify that echo $LD_LIBRARY_PATH returns a valid path. . /opt/novell/eDirectory/bin/ndspath will get it running for the current session, then restarting ndsd should load vrdim. The path can be set by exporting it after logging in as root, or adding it to an env_idm file in /etc/opt/novell/eDirectory/conf directory.

LD_LIBRARY_PATH=//opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64://opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/server://opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/native_threads::$LD_LIBRARY_PATH:/opt/novell/eDirectory/lib64/apr:/opt/novell/eDirectory/lib64:/opt/novell/lib64:/opt/novell/eDirectory/lib64/nds-modules:$LD_LIBRARY_PATH

Related:

  • No Related Posts

Untitled


There are several possible causes for the error, some are listed bellow with suggestions to help fix and/or track them further:

– Cause: Misconfiguration of the JVM heap sizes

Suggestions: Clear any custom settings to the Initial heap size and Max heap size on the properties of the driver set, misc tab. Then try to load the vrdim modules. ****Too large of heap settings accounts for about 90% of these issues****

Additional detail on these errors can be found using the +misc flag in ndstrace. All jvmloader messages come under the MISC flag on Linux/Unix, and under the MISC OTHER flag on dstrace.dlm (Windows). Unfortunately there is no way of seeing them on Netware ( but we can always check the SYS:/ETC/JAVA.CFG file there)

Cause LD_LIBRARY_PATH not set properly causing “error: libjvm.so: cannot open shared object file: No such file or directory” and “JVM interface initialization failed <failed, -299 (0xfffffed5)>, unloading DIRXML” errors.

Verify that echo $LD_LIBRARY_PATH returns a valid path. . /opt/novell/eDirectory/bin/ndspath will get it running for the current session, then restarting ndsd should load vrdim. The path can be set by exporting it after logging in as root, or adding it to an env_idm file in /etc/opt/novell/eDirectory/conf directory.

LD_LIBRARY_PATH=//opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64://opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/server://opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/native_threads::$LD_LIBRARY_PATH:/opt/novell/eDirectory/lib64/apr:/opt/novell/eDirectory/lib64:/opt/novell/lib64:/opt/novell/eDirectory/lib64/nds-modules:$LD_LIBRARY_PATH

Related:

  • No Related Posts