Known Issues and Recommendations
iWD History Node
The Known Issues and Recommendations section is a cumulative list for all 9.0.x releases of iWD History Node. This section provides the latest information on known issues and recommendations associated with this product. It includes information on when individual items were found and, if applicable, corrected. The Resolved Issues section for each release describes the corrections and may list additional issues that were corrected without first being documented as Known Issues.
See also Internationalization Issues.
An incorrect version is shown in the corresponding META-INF/MANIFEST.MF and iwd_history.lms files. For example, the version 9.0.019.11 is shown instead of the correct version 9.0.019.12.
| ID: IWD-10076 | Found In: 9.0.019.10 | Fixed In: 9.0.019.13 |
iWD History Node fails to write new events in its database when it is configured to use Kafka Event Logger along with Oracle DB.
| ID: IWD-10103 | Found In: 9.0.019.06 | Fixed In: 9.0.019.13 |
The installer for Windows does not include a countersignature. Windows will consider this installer as unsigned after the Genesys certificate expires.
| ID: IWD-9972 | Found In: 9.0.017.04 | Fixed In: 9.0.018.06 |
When iWD History Node is configured using Kafka and a database failure occurs, Kafka Event Log Reader stops working and does not restart.
| ID: IWD-9981 | Found In: 9.0.012.07 | Fixed In: 9.0.019.03 |
iWD History Node does not start and it displays an exception when there is no auto.offset.reset parameter in the consumer-option section.
To ensure this does not happen, add the auto.offset.reset parameter in the consumer-option section.
| ID: IWD-9860 | Found In: 9.0.012.07 | Fixed In: 9.0.018.02 |
If a new History Node database is created without any defined schema and the migrate-schema option is set to false, History Node extracts events from the JMS queue but fails to write them to the blank database, resulting in loss of all the event data. The only error message generated for this scenario appears in logs.
To ensure this does not happen, either ensure that migrate-schema is set to true before attempting automated migration to a blank database, or manually migrate the schema using the instructions here.
| ID: IWD-9860 | Found In: 9.0.012.07 | Fixed In: 9.0.018.02 |
If you are migrating data from iWD 8.5.1 to iWD 9.0 (as documented in Data Migration from iWD 8.5.1x to iWD 9.0 ), iWD History Node migrates events stored in the GMT+0 time zone offset, but the migration uses the system time zone. Running on a system with a time zone other than GMT+0 causes events to be saved with an incorrect offset.
Workaround: You must specify that iWD History Node is running in the GMT time zone.
- To do this for Windows, add -Duser.timezone=GMT to JavaServerStarter.ini under the [JavaArgs] section.
- To do this for UNIX, add -Duser.timezone=GMT to JAVA_OPTS in iwd_history.sh.
| ID: IWD-10037 | Found In: 9.0.002.20 | Fixed In: 9.0.019.08 |
You cannot use spaces in Application names on Linux platforms.
| ID: IWD-5867 | Found In: 8.5.106.04 | Fixed In: |
Genesys recommends that you use a version of the ActiveMQ client that satisfies your organization's security policies, and in any event no earlier than 5.15.4.
| ID: IWD-7848 | Found In: | Fixed In: |
Internationalization Issues
Information in this section is included for international customers. Release numbers in the Found In and Fixed In fields refer to the English (US) release of iWD History Node unless otherwise noted in the issue description.
There are no internationalization issues for this product.