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

Enforce Server: Custom attribute lookup failed Code 2115

I need a solution

This stops the controller service and the whole production come to a stop and you have to recycle the services on Enforce to get eveything back. I don’t have access to the server itself, only the web console, so I’m trying to troubleshoot this based on the logs and events I have access to. I have read some articles that seem to be related to this, but the event descriptions are different while the event Code is the same: 2115, and they are very old from like 2011. so I think this issue may be a good to revisit. 

Here are the error descriptions:

com.vontu.lookup.script.ScriptLookup

Failed to instantiate lookup plug-in com.vontu.lookup.script.ScriptLookup

IncidentPersister_0.log

 

10:14:29 AM (SEVERE) Thread: 111 [com.vontu.enforce.workflow.attributes.DeferredUpdateLookupRequest.doLookup] unable to create new native thread

java.lang.OutOfMemoryError: unable to create new native thread

at java.lang.Thread.start0(Native Method)

at java.lang.Thread.start(Thread.java:714)

at com.vontu.lookup.script.ExecCommand.execute(ExecCommand.java:95)

at com.vontu.lookup.script.ExecLauncher.launch(ExecLauncher.java:137)

at com.vontu.lookup.script.ScriptLookup.invokeScript(ScriptLookup.java:116)

at com.vontu.lookup.script.ScriptLookup.lookupAttributeValues(ScriptLookup.java:71)

at com.vontu.enforce.workflow.attributes.CustomAttributeLookup$1.call(CustomAttributeLookup.java:441)

at edu.oswego.cs.dl.util.concurrent.FutureResult$1.run(FutureResult.java:75)

at com.vontu.util.concurrent.TimedCallablePool$Worker.run(TimedCallablePool.java:414)

Oct 22, 2019

VontuManager.log

2019/10/22 10:11:15 |         at java.lang.Thread.run(Thread.java:745)

STATUS | wrapper  | 2019/10/22 10:15:09 | TERM trapped.  Shutting down.

ERROR  | wrapper  | 2019/10/22 10:17:13 | Shutdown failed: Timed out waiting for signal from JVM.

ERROR  | wrapper  | 2019/10/22 10:17:14 | JVM did not exit on request, termination requested.

STATUS | wrapper  | 2019/10/22 10:17:17 | JVM received a signal SIGKILL (9).

STATUS | wrapper  | 2019/10/22 10:17:17 | JVM process is gone.

STATUS | wrapper  | 2019/10/22 10:17:17 | JVM exited after being requested to terminate.

STATUS | wrapper  | 2019/10/22 10:17:17 | <– Wrapper Stopped

STATUS | wrapper  | 2019/10/22 10:18:04 | –> Wrapper Started as Daemon

STATUS | wrapper  | 2019/10/22 10:18:04 | Java Service Wrapper Standard Edition 64-bit 3.5.26

STATUS | wrapper  | 2019/10/22 10:18:04 |   Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.

STATUS | wrapper  | 2019/10/22 10:18:04 |     http://wrapper.tanukisoftware.com

STATUS | wrapper  | 2019/10/22 10:18:04 |   Licensed to Symantec Corp. for VontuManager

STATUS | wrapper  | 2019/10/22 10:18:04 |

STATUS | wrapper  | 2019/10/22 10:18:04 | Launching a JVM…

INFO   | jvm 1    | 2019/10/22 10:18:04 | Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0

INFO   | jvm 1    | 2019/10/22 10:18:04 | Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0

INFO   | jvm 1 

Symantec Data Loss Prevention Home Incidents
System > Servers and Detectors > Events >
Event Detail
Manage
System
General
Type
Server or Detector
Message
2115
Severe
Enforce Server
Time
Host
Oct 22, 2019 AM
127.0.0.1
Summary Custom attribute bokup failed
Detail
Failed to nstantlate bokup plug-in com.vontu.lookup.liveldap.LweLdapLookup. It was unloaded. Error message: No group 2 ” src=”file:///C:/Users/ZHINSD~1/AppData/Local/Temp/msohtmlclip1/02/clip_image001.png” style=”width:930px; height:401px” />

0

Related:

Trying to install remote indexers…JRE path??????

I need a solution

Once again no instructions…just run this and fail…

Trying to install the indexers.msi. Picked path to where it needs to go but next question is to “Select the directory of the JRE you wish to use.” I picked a JRE and get a “Could not find the location of jvm.dll. Please ensure that the JRE directory path is correct.”.

THE FILE IS THERE! DO I NEED A DIFFERENT VERSION OR IS THIS JUST A WASTED APPLICATION! Supposed to be stand alone.

This was easy in 14.5.

0

Related:

  • No Related Posts

7023600: IDM and 2019 Oracle Java Licensing Requirements

Questions and answers:

1. Will Micro Focus release updates for Oracle JDK 8 or JDK 11 for Identity Manager?

Answer: No, Identity Manager will be distributing the Azul Open JDK moving forward. Any improvements, fixes and security concerns will be addressed based on the Azul Open JDK.

2. What if you are using an older version of Java (release prior to January 2019) in Identity Manager? Will you be responsible for any additional license fees?

Answer: No. Only newer updates specific to Oracles JDK that are post January 2019 require and licensing. Further, the vendor that redistributes the Oracle JDK is responsible for the licensing. If you are using a version of Oracle JDK prior to January 2019, no additional licensing is required

Related:

7023355: ‘execstack -c ‘, or link it with ‘-z noexecstack’ message in log files

This document (7023355) is provided subject to the disclaimer at the end of this document.

Environment


eDirectory

Identity Manager

iManager

Situation

Messages in ndsd.log

Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /opt/novell/lib64/libnpkit.so which might have disabled stack guard. The VM will try to fix the stack guard now.
It’s highly recommended that you fix the library with ‘execstack -c <libfile>’, or link it with ‘-z noexecstack’.
NetIQ JClient 2.08.0403-2.8.403. (c) 2013 NetIQ Corporation and its affiliates. All Rights Reserved.
Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /opt/novell/eDirectory/lib64/libdhutilj.so.3.0.500 which might have disabled stack guard. The VM will try to fix the
stack guard now.
It’s highly recommended that you fix the library with ‘execstack -c <libfile>’, or link it with ‘-z noexecstack’.
Message in Catalina.out
NetIQ JClient 4.00.0130-4.0.130. (c) 2013 NetIQ Corporation and its affiliates. All Rights Reserved.
Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /var/opt/novell/iManager/nps/WEB-INF/bin/linux/libnpkiapi.so which might have disabled stack guard. The VM will try t
o fix the stack guard now.
It’s highly recommended that you fix the library with ‘execstack -c <libfile>’, or link it with ‘-z noexecstack’.

Resolution

Analysis of this message has determined the process isn’t effect and it is cosmetic in nature.

Cause

Messages will be generated when a java process tries to load a native library.

It is been introduced by Oracle after java 1.7 onward.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

Class sharing in Eclipse OpenJ9

Memory footprint and startup time are important performance metrics for
a Java virtual machine (JVM). The memory footprint becomes especially
important in the cloud environment since you pay for the memory your
application uses. This tutorial shows you how to use the shared classes feature in Eclipse OpenJ9 to reduce the memory footprint and improve your JVM startup time.

Related:

Cannot start vontu monitor service

I need a solution

I can’t find a solution for a install Detection server 15.0

STATUS | wrapper  | 2018/05/07 15:55:16 | Launching a JVM…
INFO   | jvm 1    | 2018/05/07 15:55:17 | WrapperManager: Initializing…
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp: 
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp Error: Encountered an error running main:
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp Error: java.lang.UnsatisfiedLinkError: C:SymantecDLPProtectlibnativeWin32ProcessControl.dll: Can’t find dependent libraries
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp Error: at java.lang.ClassLoader$NativeLibrary.load(Native Method)
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp Error: at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1941)
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp Error: at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1824)
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp Error: at java.lang.Runtime.load0(Runtime.java:809)
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp Error: at java.lang.System.load(System.java:1086)
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp Error: at com.vontu.util.process.Win32ProcessControl.<init>(Win32ProcessControl.java:36)
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp Error: at com.vontu.util.process.NativeProcessControl.newInstance(NativeProcessControl.java:82)
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp Error: at com.vontu.boxmonitor.MonitorProcessCleanup.<init>(MonitorProcessCleanup.java:47)
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp Error: at com.vontu.boxmonitor.MonitorProcessCleanup.killProcesses(MonitorProcessCleanup.java:57)
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp Error: at com.vontu.boxmonitor.BoxMonitor.killProcessesOnStartup(BoxMonitor.java:321)
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp Error: at com.vontu.boxmonitor.BoxMonitor.main(BoxMonitor.java:286)
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp Error: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp Error: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp Error: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp Error: at java.lang.reflect.Method.invoke(Method.java:498)
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp Error: at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:325)
INFO   | jvm 1    | 2018/05/07 15:55:18 | WrapperSimpleApp Error: at java.lang.Thread.run(Thread.java:748)
STATUS | wrapper  | 2018/05/07 15:55:20 | on_exit trigger matched.  Restarting the JVM.  (Exit code: 1)
0

Related:

7021829: Java Memory Management in Reflection X Advantage

Memory Use Overview

Attachmate Java applications rely on the Java Virtual Machine (JVM) to manage memory. The JVM allocates a pool of memory at startup and applications running in that JVM share that memory. Each Attachmate application that uses Java sets a maximum value for the size of the JVM memory pool. (This is also called the Java heap size.) The JVM can use memory, as required, up to this specified limit. As memory use approaches this limit, the JVM will recycle unused memory so that it remains available to applications running in the JVM.

When viewing memory used by a Java application, note the following:

  • All applications running in a JVM draw memory from the JVM memory pool, not from the Windows operating system memory. The memory used by all applications running in the JVM will never exceed the specified heap size for that JVM.
  • The JVM will recycle available memory back to the applications running in that JVM as needed, but this doesn’t happen until the memory use approaches the heap limit. Because of this, applications running in a JVM may not actually require all the memory reported in the Windows Task Manager at any given time.

In the Windows Task Manager, some Java applications create processes that use an application-specific image name. (For example Reflection X Manager and Reflection X Manager for Domains create processes listed under rxmgr.exe and rxmgrdomains.exe). Other applications (including the Reflection X Service) create processes that use java.exe as the image name.

If you also run other applications that consume a lot of memory, you may see performance issues. As Windows runs out of the random access memory (RAM) needed to run your applications, it uses something called virtual memory to compensate. When the available RAM runs low, Windows moves data from RAM to disk storage in a file called the paging file. Moving data to and from the paging file frees up RAM so your computer can complete its work, but reading data from the disk is slower than reading data directly from memory.

Memory Troubleshooting

On most systems, you will not need to modify your settings using any of the following troubleshooting techniques. The Reflection X Advantage default JVM settings provide sufficient memory to address the memory demands created by most X clients and servers. The default maximum heap size also ensures sufficient memory will be available on most systems for your Windows applications that don’t use this JVM. However, in some cases, contention for memory may prevent Reflection X Advantage applications from launching, or affect the performance of other applications on your system.

If your system’s memory is limited or fragmented, you may see one of the following indications that memory limits are preventing Reflection X Advantage applications from running.

  • In version 5.0 or later, you see a message saying “Application failed to start due to insufficient memory.”
  • In version 4.2 or earlier, the Reflection X Advantage application fails to launch, and the Windows Event log shows a message like the following:

“The description for Event ID (1025) in Source (RXAdvantage) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: The event log file is corrupt.”

If memory limits prevent Reflection X Advantage from running, or you have determined that contention for memory is affecting performance of other applications, consider the following approaches.

Install Reflection X Advantage using the 64-bit Installer

If you have installed Reflection X Advantage using the 32-bit installer on a 64-bit system, and Reflection X Advantage applications fail to launch, reinstall using the 64-bit installer. The memory limit on 64-bit processes is much larger than the limit on a 32-bit processes.

Add RAM

The more RAM your computer has, the faster your programs will generally run. If a lack of RAM is slowing your computer, you may have success using the following adjustments. However, if none of these solutions result in better performance, adding additional RAM is the best solution.

Reduce the Maximum Memory Available to the JVM

Reducing the maximum memory limit for Reflection X Advantage (also called the Java heap size) can resolve the problem of Reflection X Applications failing to launch and can also increase the amount of memory available to other applications.

Note: This solution may affect performance in Reflection X Advantage. If memory is available Reflection X Advantage sessions cache images, the results of certain calculations, and other data. These actions can improve drawing performance and compression over low-bandwidth networks. If changing the Java heap size results in slow performance or X client failures, the value is probably set too low.

To change the maximum memory available to the Reflection X Advantage JVM:

  1. Close X Manager if it is running.
  2. Navigate to the Reflection X Advantage installation folder. (The default location for most installs is C:Program FilesAttachmateReflection).
  3. Locate rxmgr.alp (if you use standalone X Manager) or rxmgrdomains.alp (if you use X Manager for Domains) and remove the read-only attribute from this file. (Right-click, select Properties, clear the “Read-only” checkmark, then click OK.)
  4. Open the *.alp file in a text editor, such as Notepad.
  5. In the line that begins “alp.java.command.options=” locate the -Xmx setting. (The default value is -Xmx900m in version 5.0 and -Xmx1024m in version 4.2 and earlier.) Change this to a smaller value (for example: -Xmx700m).

Note: The *.alp files are replaced by newer, default files when you upgrade your Reflection X Advantage product. If memory problems reappear after an upgrade, see Technical Note 2530, “Installing Newer Versions of Reflection X Advantage If You Have Edited Rxmgr.alp.”

Increase Virtual Memory

You can increase the amount of virtual memory available by increasing the minimum and maximum sizes of the paging file.

This change can result in slower performance in Reflection X Advantage and other applications because of excessive disk paging. This solution may work for you if there are idle applications that can be paged out at times.

To modify virtual memory in Windows:

  1. Open the System Properties dialog box. (In Windows 7: Start menu > right-click Computer > Properties > Advanced system settings.)
  2. On the Advanced tab, under Performance, click Settings.
  3. Click the Advanced tab, and then, under Virtual memory, click Change.
  4. Click Custom size and set values for Initial size (MB) and/or Maximum size (MB).

Increases in size usually don’t require a restart, but if you decrease the size, you will need to restart Windows.

Add Additional Reflection X Advantage Nodes

If you are running Reflection X Advantage in domain mode and are experiencing memory contention on the domain node, you can experiment with using multiple nodes to help alleviate memory problems. Reflection X Advantage supports creating multiple nodes on the same system. This change effectively increases the allowed memory available to run sessions. You can also add nodes on remote systems. This increases both the number of CPU cores available and amount of available memory.

To add nodes to a domain, use the rxsconfig command line utility. For details, see “Set Up Domain Nodes” in the Reflection X Advantage product Help.

The number of sessions that a node can support depends on what kind of domain services are configured for the session (such as whether the session has a headless server running on the node) and how active the clients of the session are. You can monitor the load on your nodes using the Administrative Console. As an initial approximation, a session without a headless server can be expected to require about 1MB, and with a headless server about 25MB of heap space. For a 1GB heap (the default), this can be anything from about 30-1000 sessions. With a large number of sessions, resources such as cores and network bandwidth become a bigger concern.

Related: