Skip to main content

Known Issues and Notes

This chapter describes issues that InterSystems is aware of in InterSystems IRIS® 2021.2 and notes related to this version of the product. These issues will be addressed in future releases.

Issue Upgrading InterSystems Cloud Manager with Service Discovery

Using Service Discovery to upgrade ICM will not work if there are 10 or more nodes or if nodes have ever been scaled. Consequently, Service Discovery (as a means to share or upgrade ICM containers) is not fully supported in this release.

Embedded Python Issues

Embedded Python has the following issues:

  • Memory issue — in some circumstances, an object returned from a Python method to ObjectScript may not have its reference count correctly decremented upon object destruction. The resources used by these objects will not be deallocated until the InterSystems IRIS process is terminated. This issue will be addressed in the next release.

  • AIX — Embedded Python is not supported on AIX in this release. This issue will be addressed in the next release.

  • Terminal output — on all platforms, ObjectScript code in methods or routines invoked from the irispython binary will not produce terminal output. Additionally, on Windows, such ObjectScript terminal output can cause the irispython process to become temporarily unresponsive to keypress input. This issue will be addressed in the next release.

  • 8-bit instances — there are known issues using Embedded Python with 8-bit InterSystems IRIS instances; consequently, in this release, InterSystems recommends that Embedded Python be used only with Unicode instances. This issue will be addressed in the next release.

8-Bit Windows callin Authentication Issue

There is an issue where authentication fails in the callin interface on 8-bit Windows instances. This issue will be addressed in the next release.

Issue with Journal Compression on Windows

In some circumstances, InterSystems IRIS on Windows may fail to open a journal for use in transaction rollback if it is simultaneously being compressed, resulting in unreported rollback failure. InterSystems recommends against use of journal compression on Windows installations in a production deployment. This issue will be addressed in the next release.

Incorrect Warning About Number of Compute Nodes Needed in Sharded Cluster

Under some circumstances, when you successfully deploy a mirrored sharded cluster with async members in the mirrors, you may get the following warning indicating that the number of compute nodes exceeds the number of data nodes, even though this is not the case:

Warning: Number of shards exceeds the number of Compute nodes; please ensure you provision at least one compute node per data node

If you receive this warning, confirm that your cluster adheres to the best practice of having at least one compute node for each data node; if so, you can ignore the warning. Even if you do not have enough compute nodes, the sharded system will work correctly. The message only indicates that your configuration does not match our recommendations.

This issue will be fixed in the next release.

Apple macOS Issues

The MacOS is supported only as a development system. In this release, there are the following issues running on the MacOS:

  • LDAP does not work on MacOS running on Mac M1 Apple silicon processors.

  • You cannot use the node.js external language on MacOS.

  • On Apple macOS, InterSystems IRIS does not have a requirements checker, but there are required dependencies. See Installing the Required Dependencies.

Changing sysctl Setting for net.ipv4.tcp_syncookies on Linux

On Linux systems, if the sysctl setting for net.ipv4.tcp_syncookies is changed while your instance is running, you should invoke the following method $system.INetInfo.SetListenQSize() to set the TCP listen queue size for the /CLOSELISTEN option. If the queue size is changed there will be a message logged in the message log.

Issue Using MultiValue Feature

InterSystems has identified some issues with InterSystems IRIS MultiValue. We are investigating those and will fix them in a future release. If you are upgrading a MultiValue based application from Caché or Ensemble to InterSystems IRIS, you should thoroughly test your application on InterSystems IRIS before upgrading a production system. If you encounter any issues or want more information about the issues we have encountered, contact your sales engineer or the InterSystems Worldwide Response Center.

Management Portal Web Applications May Time Out Despite User Activity

In InterSystems IRIS 2018.1 and later, an automatic logout feature was implemented and enabled by default. When the feature is enabled and a user is inactive on an InterSystems IRIS Management Portal web application for longer than the Session Timeout value for the web application, then the user is logged out. However, InterSystems IRIS only registers actions that result in a call to the server as activity. Consequently, a user may be modifying a Management Portal page immediately before an automatic logout and lose any unsaved changes. For example, if a user is editing a business process, but has not clicked Save for longer than Session Timeout threshold, then the user's session expires and any unsaved changes are discarded. After an automatic logout, the login page appears or the current page is refreshed.

You can take several steps to prevent users from losing work:

  • Remind users to save their work on a regular basis.

  • Extend the Session Timeout value for web applications where users are performing time-intensive configuration tasks such as modifying data transformations. The default Session Timeout value is 15 minutes.

  • Disable automatic logouts for the Interoperability pages in the Management Portal by modifying the ^EnsPortal global as follows:

    set ^EnsPortal("DisableInactivityTimeout","Portal") = 1 

InterSystems recommends that you consider the possible security implications before you make any changes.

For more information, see Automatic Logout Behavior in the Management Portal.

Multiple Files Created from a Single X12 Document

When an interoperability production uses the default X12 business operation to write to a file, a single X12 document can result in multiple files. In this scenario, an extra file is created for each Functional Group in the original X12 batch document. This error occurs with certain File Name options when the Auto Batch Parent Segs setting is enabled.

DTL Creates Empty Target Segment

A DTL includes an option called Ignore missing source segments and properties. When enabled, errors caused by a missing source segment are suppressed. However, in this release, an empty segment is created in the target when the DTL encounters a missing source segment.

Feedback