Operations Guide=en

User Manual:

Open the PDF directly: View PDF PDF.
Page Count: 266 [warning: Documents this large are best viewed by clicking the View PDF Link!]

Ultra Messaging (Version 6.12)
Operations Guide
Copyright (C) 2004-2019, Informatica Corporation. All Rights Reserved.
Contents
1 Introduction 5
2 UM Installation 7
2.1 UM Package Installer .......................................... 7
2.1.1 Unix Package Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1.2 Windows Package Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1.3 Other Package Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2 Copy UM Runtime Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2.1 Copy Unix Runtime Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2.2 Copy Windows Runtime Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Application Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3 Monitoring 11
3.1 Monitoring Transport Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1.1 LBT-RM and LBT-RU Receiver Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.1.2 LBT-RM and LBT-RU Source Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.1.3 TCP Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.1.4 LBT-IPC Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2 Monitoring Event Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.3 Monitoring Application Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.4 Monitoring the Persistent Store Daemon (umestored) . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.4.1 Monitoring Store Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.4.2 Monitoring a Store's Internal Transport Statistics . . . . . . . . . . . . . . . . . . . . . . . . 14
3.4.3 Persistent Store Web Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.4.4 Persistent Store Daemon Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.4.5 Detecting Persistent Store Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.5 Monitoring the UM Router Daemon (tnwgd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.5.1 Monitoring UM Router Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.5.2 UM Router Transport Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.5.3 UM Router Web Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.5.4 UM Router Daemon Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.5.5 Detecting UM Router Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4 CONTENTS
3.6 Monitoring Messaging System Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.6.1 Persistent Store System Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.6.2 Sources of Latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.6.3 Runtime Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4 Startup/Shutdown Procedures 21
4.1 Topic Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.2 UM Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.3 Indications of Possible Application Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.4 Unicast Topic Resolver (lbmrd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.5 Persistent Store (umestored) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.5.1 Starting a Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.5.2 Restarting a Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.5.3 Common Startup and Shutdown Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.6 UM Router (tnwgd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.6.1 Starting a UM Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.6.2 Restarting a UM Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.7 UM Daemons as Windows Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.7.1 Install the Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.7.2 Configure the Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.7.3 Configure the Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.7.4 Start the Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.7.5 Remove the Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.8 UM Analysis Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.8.1 Packet Capture Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.8.2 Resource Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.8.3 Process Analysis Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.8.4 Network Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.8.5 UM Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.8.6 UM Debug Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5 Monitoring UM with the lbmmon API 31
5.1 Monitoring Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.1.1 Why Monitor? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.1.2 What to Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.2 Monitoring Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.3 UM API Functions and Data Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.3.1 Context Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.3.2 Event Queue Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.3.3 Source or Receiver Transport Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.4 UM Monitoring API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
CONTENTS 5
5.4.1 Monitoring Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.4.2 API Framework Flexibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.4.3 Initial Monitoring Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.4.4 Creating a Monitoring Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.4.5 Specifying the Object to Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.4.6 Receiving Monitoring Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.5 Monitoring Transport Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.5.1 The LBM Transport Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.5.2 The UDP Transport Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.5.3 The SNMP Transport Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.6 Monitoring Format Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.6.1 The CSV Format Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.7 Automatic Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.8 Monitoring Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.8.1 lbmmon.c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.8.2 lbmmonudp.c and lbmmondiag.pl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.9 Interpreting LBT-RM Source Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6 UM Monitoring Statistics 49
6.1 Monitoring Receiving Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.2 Monitoring Sending Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.3 Monitoring Context Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
6.4 Monitoring Event Queue Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
7 Troubleshooting UM Applications 51
7.1 Application Crashes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
7.1.1 Persistent Store Crashed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
7.1.2 UM Router Crashed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
7.1.3 Excessive Resource Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
7.1.4 Crash on deletion of an object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
7.1.5 Datagram size mismatches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
7.2 Assertions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.2.1 Fatal Assertions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.2.2 Non-fatal Assertions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.3 Message Loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.4 Unrecoverable Loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
7.5 High Latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
7.6 Deaf Receivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
7.7 Persistent Sending Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
7.7.1 Flight Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
7.7.2 Persistent Store Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6 CONTENTS
8 Contacting Informatica Support 59
9 UM Log Messages 61
9.1 UM Core Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
9.2 UM Core API Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
9.3 UM SRS Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
9.4 UM Dynamic Routing Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
9.5 UM Lbmrd Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
9.6 UM Persistent Store Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
9.7 UMDS Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Chapter 1
Introduction
This document gives information and guidance for preparing an application system for deployment, and for operating
that system when it is in production.
Attention
See the Documentation Introduction for important information on copyright, patents, infor-
mation resources (including Knowledge Base, and How To articles), Marketplace, Support, and other
information about Informatica and its products.
This document assumes familiarity with the UM Concepts Guide.
See UM Glossary for Ultra Messaging terminology, abbreviations, and acronyms.
8 Introduction
Chapter 2
UM Installation
Different versions of UM have some differences in how the files are offered for download. As of 6.11, the following
zip files are available for download:
• UMS_version.zip - Streaming Edition.
• UMP_version.zip - Persistence Edition.
• UMQ_version.zip - Queuing Edition.
• UMDRO_version.zip - UM Router.
• UM_version_doc.zip - Documentation package.
The first four contain the binary software for that product (all platforms). The last contains HTML and PDF docu-
mentation for all UM products and features.
For the binary software, the zip file contains a set of per-platform package installers, and a set of Java jar files.
The jar files should be copied to wherever you keep your Java jars. The package installers should be installed as
described below.
There are many different ways to install UM on a host, but they can generally be categorized in three groups:
•UM Package Installer from Informatica for the desired products.
•Copy UM Runtime Files to the desired host.
•Application Installer written by the application developer.
2.1 UM Package Installer
Running the UM package installer is typically only done for hosts being prepared for development use. Once an
application system is developed, UM is usually installed by the user's own Application Installer.
Note that the UM Router package installer needs the corresponding version of UM to be already installed and
accessible in the current working directory before it can be installed.
10 UM Installation
2.1.1 Unix Package Installer
A product's Unix Package Installer is an executable file with the file suffix ".sh". It is in the form of a
self-extracting archive, sometimes called a "shell archive".
It is often necessary to set the file permissions to allow execution of the file.
Running the UM Package Installer on a Unix host does nothing more than copy the files under the current working
directory. The installer does not perform any other installation actions.
For example, to install the UMQ base product:
$ chmod +x UMQ_6.12_Linux-glibc-2.17-x86_64.sh
$ ./UMQ_6.12_Linux-glibc-2.17-x86_64.sh
This creates a directory named "UMQ_6.12" which contains all the files and sub-directories needed to develop and
test UM-based applications. It does not contain the documentation, which is shipped in its own zip file.
2.1.2 Windows Package Installer
A product's Windows Package Installer is an executable file with the file suffix ".exe".
Running the UM Package Installer on a Windows host does the following:
• Copies the files into the proper "Program File" folder, depending on whether the package is 32 or 64 bits.
• Updates the system "PATH" environment variable to include UM's "bin" folder.
• Optionally installs one or more daemons as Windows Services (see UM Daemons as Windows Services for
more information).
• Provides a standard Windows uninstaller which can be run from the normal Windows "Add or Remove Pro-
grams" control panel.
To run the installer, simply double-click the package installer icon.
Note that once an application system is developed, UM is usually installed by the user's own Application Installer.
2.1.3 Other Package Installers
Java
The UM Java API is a wrapper around the UM dynamic library (JNI). The jar files are shipped with the package
installers, and should be saved wherever you store your jar files.
Note that the Java jar file version must match the underlying UM library version.
Stratus OpenVOS Package
The Stratus OpenVOS package is a self-extracting archive that contains the Ultra Messaging Streaming Edition
(UMS) for the Stratus OpenVOS platform.
Ultra Messaging supports Stratus OpenVOS Release 17.0.2aq.
RESTRICTIONS:
The following Ultra Messaging components and features do not run on the Stratus OpenVOS platform:
• Ultra Messaging daemons (tnwgd, ummd, stored, lbmrd, SRS).
2.2 Copy UM Runtime Files 11
• Java API and .NET API.
• UM transports LBT-IPC, LBT-RDMA, or LBT-SMX.
• Accelerated Multicast.
• Persistence.
• Queuing (including ULB).
• Ultra Messaging Desktop Services (UMDS).
HP NonStop Package
The HP NonStop package is a self-extracting archive that contains the Ultra Messaging Persistence Edition (UMP)
for the HP NonStop platform.
Ultra Messaging supports HP NonStop Version J06-17.
RESTRICTIONS:
The following components and features do not run on the HP NonStop platform.
• Ultra Messaging daemons (tnwgd, ummd, stored, lbmrd, SRS).
• Java API and .NET API
• UM transports LBT-IPC, LBT-RDMA, or LBT-SMX
• Accelerated Multicast
• Queuing (including ULB).
• Ultra Messaging Desktop Services (UMDS).
2.2 Copy UM Runtime Files
It is generally not necessary to run the UM Package Installer to use UM on a host. For the most part, all you need
to do is copy the runtime files to any desired location on your host. In the case of running UM daemons as Windows
Services, there are some additional steps necessary; see Copy Windows Runtime Files.
2.2.1 Copy Unix Runtime Files
Informatica generally recommends that UM runtime files be stored in the "lib" and "bin" sub-directories in
the structure that the installer creates. If the brokered queuing feature is used, then the "broker" sub-directory
should also be included. For example:
$ ls ~/UMQ_6.12/Linux-glibc-2.12-x86_64/
bin/ broker/ lib/
Notice that the "include" sub-directory is missing. Those files are only needed for development, not for produc-
tion runtime.
For ease of use, users typically include "lib" in their library search path (e.g. "LD_LIBRARY_PATH" environ-
ment variable), and include "bin" in their "PATH".
No other specialized installation steps are needed for UM.
12 UM Installation
Alternatively, the contents of "bin" can be copied to wherever you already store your application executables, and
the contents of "lib" can be copied to wherever you store your application dynamic libraries.
2.2.2 Copy Windows Runtime Files
Informatica generally recommends that UM runtime files be stored in the "bin" sub-folder in the structure that
the installer creates. If the brokered queuing feature is used, then the "broker" sub-directory should also be
included. For example:
> dir "c:\Program Files\Informatica\UMQ_6.12\Win2k-x86_64"
... <DIR> bin
... <DIR> broker
Notice that the "include" and "lib" sub-folders are missing. Those files are only needed for development,
not for production runtime.
For ease of use, users typically include "bin" in their "PATH" environment variable.
No other specialized installation steps are needed for UM applications. However, if you want to run one or more
UM daemons as Windows Services, then there are some additional steps necessary, described in UM Daemons as
Windows Services.
Alternatively, the contents of "bin" can be copied to wherever you already store your application executables.
Note
If it is desired to uninstall UM that was installed by copying files, UM will not show up in the normal Windows
"Add or Remove Programs" control panel. If you have installed UM daemons as Windows Services, then you
must manually remove them as Services before deleting the UM runtime files. See Remove the Windows
Service.
2.3 Application Installer
UM is intended to be integrated into a user's own application system. Each user decides how his application system
is packaged and installed.
UM users typically do not run the UM package installer as part of their application installation procedure. Rather,
the UM runtime files are typically packaged with the user's application files.
The requirements for the user's application installation procedure are the same as outlined in Copy UM Runtime
Files, and for the most part, consist simply of copying the UM files to the host.
In the case of running UM daemons as Windows Services, there are some additional steps necessary; see Copy
Windows Runtime Files.
Chapter 3
Monitoring
It is important to monitor Ultra Messaging to ensure smooth operation. By tracking the changes in UM statistics
over time, you may be able to predict and avoid future overloads. When contacting support to report anomalous
behavior, recording UM statistics can greatly assist the support engineers' root cause analysis.
3.1 Monitoring Transport Statistics
Monitoring the activity on your UM transport sessions is the most important component of your UM monitoring effort.
UM provides the following four methods to monitor your UM activities.
• Use UM API function calls within your applications to retrieve statistics and deliver them to your monitoring
application.
• Use the UM Monitoring API to more easily retrieve and send statistics to your monitoring application.
• Use Automatic Monitoring to easily employ the UM Monitoring API to monitor UM activity at an UM context
level.
• Use the Ultra Messaging SNMP Agent and MIB (purchased separately to monitor statistics through a Network
Management System). See The Ultra Messaging SNMP Agent for detailed information.
Automatic Monitoring is the easiest method to implement using configuration options or environment variables.
Since many topics can use multiple transport sessions, UM Monitoring doesn't provide transport information for
individual topics. From an Operations point of view, however, the health and behavior of your transport sessions is
more correlated to system performance. Although UM Monitoring also provides statistics on event queues, these
statistics are more specific to a single application and not a system wide health indication.
The interval for collecting statistics should be as short as practical. A too-long interval can hide microbursts of
traffic. However, a too-short interval can lead to massive amounts of statistical data which needs to be stored and
processed.
Note that certain statistics are initialized to the maximum unsigned value for the fields, i.e. all bits set (-1 if printed
signed). This special value indicates that the field has not yet been calculated. This is used for the "min" statistic in
a "minimum / maximum" statistics pair. For example, nak_tx_min is initialized to the maximum unsigned long, while
nak_tx_max is initialized to zero.
This section lists some of the more important transport statistics to monitor listed by transport type.
14 Monitoring
3.1.1 LBT-RM and LBT-RU Receiver Statistics
Essentially, aside from msg_rcved and bytes_rcved, if any receiver statistics increment, a problem may exist. The
following lists the most important statistics.
•naks_sent means a transport has a gap in sequence numbers, which can be recoverable or unrecoverable
loss.
•unrecovered_txw and unrecovered_tmo loss statistics. Indicates retransmissions not delivered to a receiver.
(The receiving application will have received a LBM_MSG_UNRECOVERABLE_LOSS or LBM_MSG_UNR←-
ECOVERABLE_LOSS_BURST log message via its receive callback, which should be found in the streaming
or API log file.
•lbm_msgs_no_topic_rcved indicates that receivers may be doing too much topic filtering (wasting CPU
resource) because they are processing messages in which they have no interest. If this statistic is greater
than 25% of msgs_rcvd, a problem may exist or topics may need to be distributed to different transport
sessions.
•dgrams_dropped_∗- Indicates the reception of invalid datagrams, e.g. a non-UM datagram or datagram
from an incompatible version.
For additional information, see Monitoring Receiving Statistics.
3.1.2 LBT-RM and LBT-RU Source Statistics
The following lists the most important statistics.
•rxs_sent indicates that some lost messages are being recovered, but the reason for the loss should be
investigated and corrected.
•naks_shed indicates the number of retransmission requests (NAKs) the source transport has not fulfilled,
sending a NCF instead. This statistics can help pinpoint transport bottlenecks, such as the configuration op-
tions transport_lbtrm_retransmit_rate_limit (context) and transport_lbtru_retransmit_rate_limit (con-
text).
For additional information, see Monitoring Sending Statistics.
3.1.3 TCP Statistics
Receiver statistic lbm_msgs_no_topic_rcvd indicates that receivers may be doing too much topic filtering (wasting
CPU resource) because they are processing messages in which they have no interest. If this statistic is greater than
25% of msgs_rcvd, a problem may exist or topics may need to be distributed to different transport sessions.
3.1.4 LBT-IPC Statistics
Receiver statistic lbm_msgs_no_topic_rcvd indicates that receivers may be doing too much topic filtering (wasting
CPU resource) because they are processing messages in which they have no interest. If this statistic is greater than
25% of msgs_rcvd, a problem may exist or topics may need to be distributed to different transport sessions.
3.2 Monitoring Event Queues 15
3.2 Monitoring Event Queues
The following lists the most important statistics.
• data_msgs & events - Total data messages and events enqueued - check these not growing beyond pre-
defined bounds
• age_mean & age_max - If an application uses a receive-side event queue for message delivery rather than
direct callbacks, this indicates average and longest time messages wait on that queue before the application
starts processing them.
• data_msgs_svc_mean & data_msgs_svc_max - indicates average and longest time the application spends
processing each event-queued message.
For more information, see Monitoring Event Queue Statistics.
3.3 Monitoring Application Log Messages
UM returns log messages to your application when conditions warrant. Your applications can decide what mes-
sages to collect and log. Most UM development teams are concerned with the efficiency and performance of their
applications and therefore will log any messages returned to their applications from UM. It may be helpful to meet
with your UM development team to learn exactly what they log and how best to monitor the log files. Ideally your
UM development team includes a timestamp when they log a message, which can be important for comparison of
disparate data, such as CPU information to transport statistics.
See the UM Log Messages section for individual messages and descriptions.
UM daemons (lbmrd, umestored, tnwgd) automatically log messages to the log files specified in their XML configu-
ration files.
3.4 Monitoring the Persistent Store Daemon (umestored)
With the UMP/UMQ products, the Persistent Store provides persistence services to UM sources and receivers.
Multiple stores are typically configured in Quorum/Consensus. Monitor every store process.
Monitor the following for all stores.
• Store log files
• Application events and log files
• Store's internal transport statistics
• Persistent Store daemon web monitor
3.4.1 Monitoring Store Log File
The store generates log messages that are used to monitor its health and operation. There is some flexibility on
where those log messages are written; see Store Log File. Each store daemon should have its own log file.
16 Monitoring
To prevent unbounded disk file growth, the Persistent Store log file can be configured to automatically roll. See
Store Rolling Logs for more information.
The following lists critical things to monitor in a store log file:
• aio_warnings - may indicate a problem with the disk (disk full, cannot write, etc.)
• Proxy source creation - indicates that a source 'went away'. This may be fine, but could also indicate an error
condition. Discuss with your UM development team when this event is safe and when it indicates a problem.
• Rapid log file growth - Log files growing rapidly or growing much more rapidly than normal, may indicate a
problem. Look at what types of messages are being written to the log at higher-than-normal rates to see
where the issue might be.
In application log files, look for LBM_SRC_EVENT_UME_REGISTRATION_ERROR messages. These can indicate
many different problems that will prevent message persistence. See the UM Log Messages section for details.
3.4.2 Monitoring a Store's Internal Transport Statistics
Since umestored is a proprietary UM application developed with the UM API library, you can configure the daemon
with automatic monitoring and then access transport statistics for the daemon's internal sources and receivers. To
accomplish this, follow the procedure below.
1. Enable Automatic Monitoring in the UM configuration file cited in the umestored XML configuration file's
"<daemon>" element.
2. For each store configured in the umestored XML configuration file, add a "<context-name>" element. Au-
tomatic Monitoring then maintains complete transport statistics for each store at the interval set in the UM
configuration file.
3.4.3 Persistent Store Web Monitoring
For information about umestored statistics see Store Web Monitor.
The web address of th Store Web Monitor is configured in the store XML configuration file. See Daemon Element.
You can monitor the following information on the umestored Web Monitor:
• List of stores the daemon is running.
• List of topics and wildcard topic patterns for each store, along with registration IDs for the sources sending on
the topics.
• Source and receiver information for each topic.
• Ultra Messaging statistics or transport-level statistics for underlying receivers in the store. These are similar
to the transport statistics mentioned earlier, however they indicate how the store is communicating with its
sources for a given topic. For example, a non-zero number of naks_sent indicates that the store is experienc-
ing some loss.
TIP: You can build a script that executes the Linux wget command at a 5 second interval to get a web monitor screen
shot and save it to a directory or file.
3.5 Monitoring the UM Router Daemon (tnwgd) 17
3.4.4 Persistent Store Daemon Statistics
The Persistent Store daemon has a simple web server which provides operational information. However, while the
web-based presentation is convenient for manual, on-demand monitoring, it is not suitable for automated collection
and recording of operational information for historical analysis.
Starting with UM version 6.11, a feature called "Daemon Statistics" has been added to the Store daemon. This
feature supports the background publishing of their operational information via UM messages. System designers
can now subscribe to this information for their own automated monitoring systems.
See Store Daemon Statistics for general information on Daemon Statistics, followed by specific information re-
garding the Store.
3.4.5 Detecting Persistent Store Failures
You can detect the loss of a store with the following.
• Loss of the Persistent Store's Process ID (PID)
• Application log messages stating the loss of connection to the store
Stores can also be "too busy" and therefore cannot service source and receiving applications. Sources declare a
store inactive with the LBM_SRC_EVENT_UME_STORE_UNRESPONSIVE event when the store's activity timeout
expires. This can be caused by the following.
• Disk is too busy (or when the system starts swapping)
• The store is processing an overly-large load of recovery traffic. You may want to recommend that UM admin-
istrators consider a larger quorum / consensus group size.
3.5 Monitoring the UM Router Daemon (tnwgd)
The Ultra Messaging UM Router links disjoint topic resolution domains by forwarding multicast and/or unicast topic
resolution traffic ensuring that receivers on the "other" side of the UM Router receive the topics to which they
subscribe. See the UM Dynamic Routing Guide for more details.
Understand UM Router (tnwgd) output traffic and WAN impacts - especially the use of rate limiters.
• WAN overrun is the number one source of UM Router problems
• Test WAN link throughput to determine the real limits of the UM Router and environment
• Make sure WAN bandwidth can cope with UM and any other traffic
Review and understand loss conditions unique to using a UM Router. Collaborate with your UM development team
to ensure the correct tuning and configurations are applied for your messaging system. Also monitor latency over
the UM Router with the UM sample application lbmpong routinely and monitor output.
Monitor the following for UM Routers.
• UM Router log files
• Application events and log files
18 Monitoring
• UM Router internal transport statistics
• UM Router daemon web monitor
3.5.1 Monitoring UM Router Log File
The UM router generates log messages that are used to monitor its health and operation. There is some flexibility
on where those log messages are written; see UM Router Log Messages. Each UM router should have its own
log file.
To prevent unbounded disk file growth, the UM Router log file can be configured to automatically roll. See UM
Router Rolling Logs for more information.
The following are important UM Router (tnwgd) log messages.
Connection Failure Messages to Monitor:
• peer portal [name] failed to connect to peer at [IP:port] via [interface]
• peer portal [name] failed to accept connection (accept) [err]: reason
Lost Connection Messages to Monitor:
• peer portal [name] lost connection to peer at [IP:port] via [interface]
• peer portal [name] connection destroyed due to socket failure
• peer portal [name] detected dropped inbound connection (read) [err]: reason
• peer portal [name] detected dropped inbound connection (zero-len read)
Peer Messages to Monitor: Dual TCP:
• peer portal [name] received connection from [IP:port]
• peer portal [name] connected to [IP:port]
Single TCP:
• Acceptor: peer portal [name] received connection from [IP:port]
• Initiator: peer portal [name] connected to [IP:port]
• UM Router Transport Statistics
3.5.2 UM Router Transport Statistics
Using the "<monitor>" element in a UM Router's XML configuration file, you can monitor the transport activity
between the UM Router and its Topic Resolution Domain. The configuration also provides Context and Event
Queue statistics. The statistics output identifies individual portals by name.
3.5 Monitoring the UM Router Daemon (tnwgd) 19
3.5.3 UM Router Web Monitoring
The UM Router web monitor provides access to a UM Router's portal and general statistics and information. The
UM Router XML configuration file contains the location of the gateway web monitor. The default port is 15305.
A UM Router Web Monitor provides a web page for each endpoint and peer portal configured for the UM Router.
Peer portals connect UM Routers and communicate only with other peer portals. Endpoint portals communicate
with topic resolution domains. Each statistic display a value for units (messages or fragments) and bytes.
Important statistics you can monitor on the tnwgd Web Monitor include the following.
Endpoint Send Statistics
Increases in the Endpoint Send Statistics values indicate errors and problems. A separate statistic appears for each
of the three types of topic message: transport topic, immediate topic, immediate topicless.
• Fragments/bytes dropped due to blocking - Indicates inability to send due to a transport's rate controller.
Message rates on other portals probably exceed the rate controller limit on the monitored portal. The UM
Router's XML configuration file may need to be adjusted.
• Fragments/bytes dropped due to error - Indicates a possible network socket or memory failure.
• Fragments/Bytes Dropped Due To Fragment Size Error - Indicates a configuration error which should be
corrected. Maximum datagram size for all transports must be the same throughout the network. Nonzero
indicates fragments were received which were larger than the egress portal's maximum datagram size.
• Current/maximum data bytes enqueued - Indicates how much data is currently queued and indicates the
maximum amount of data queued because the incoming rate exceeded what the TCP connection could
handle. Results in a latency penalty. Size of the queue is limited, so if the limit is exceeded, messages are
dropped due to blocking.
Peer Send Statistics
Increases in the Peer Send Statistics values indicate errors and problems.
• Fragments/bytes (or messages/bytes) dropped (blocking) - The result of attempting to send too much data
via the peer link.
• Fragments/bytes (or messages/bytes) dropped (not operational) - Peer connection not yet fully established.
The UM Router peer could be down or starting up.
• Current/maximum data bytes enqueued - Indicates how much data is currently queued and indicates the
maximum amount of data queued because the incoming rate exceeded what the TCP connection could
handle. Results in a latency penalty. Size of the queue is limited, so if the limit is exceeded, messages are
dropped due to blocking.
• Messages or bytes Received / Fragments or bytes Forwarded - Increasing counters indicate communicating
peers. Stagnant counters indicate a lack of traffic flow. A sender could be down, receivers on the remote side
could have no interest for the topics, the peer connection could have failed.
3.5.4 UM Router Daemon Statistics
The UM Router daemon has a simple web server which provides operational information. However, while the web-
based presentation is convenient for manual, on-demand monitoring, it is not suitable for automated collection and
recording of operational information for historical analysis.
Starting with UM version 6.11, a feature called "Daemon Statistics" has been added to the UM Router. This feature
supports the background publishing of their operational information via UM messages. System designers can now
subscribe to this information for their own automated monitoring systems.
20 Monitoring
See Store Daemon Statistics for general information on Daemon Statistics, followed by specific information re-
garding the UM Router.
3.5.5 Detecting UM Router Failures
You can detect the loss of a UM Router by the following.
• Loss of the UM Router's Process ID (PID)
• Loss of the UM Router's Web Monitor (you can poll the UM Router's Web Monitor to be sure it is accessible.)
• Monitoring the performance of applications sending messages through the UM Router.
–Are applications receiving the appropriate volume of data?
–Do you see a high number of retransmissions?
–Are applications generating the expected number of actions? Understanding the expected flow and
actions is critical and requires collaboration with your UM development team.
• Monitoring network performance and behavior in and out of the UM Router. Understanding your network
topology and the expected network traffic through the UM Router is critical and requires collaboration with
your UM development team.
3.6 Monitoring Messaging System Resources
In addition to monitoring UM activity, you must also consider the health and activity of your system resources.
• CPU usage
• Memory Usage
• UDP loss (netstat -s)
• Latency
3.6.1 Persistent Store System Considerations
Consider the following system issues regarding Persistent Store monitoring.
• Make sure that the environment in which a Persistent Store daemon (umestored) is started has enough avail-
able file descriptors for the number of sources in your environment. UM uses a minimum of 2 file descriptors
per UM source in addition to normal UM file descriptors for transports and other objects. You can use ulimit
in Linux and Process Explorer on Microsoft® Windows® to monitor file handles.
Note: The reduced-fd repository type uses 5 File Descriptors for the entire store, regardless of the number of
topics, in addition to normal UM file descriptors for transports and other objects. Use of this repository type
may impact performance.
• Monitor system resources (CPU usage, memory, disk space, wait%, memory swapping).
3.6 Monitoring Messaging System Resources 21
• If the system is about to start swapping, your resources are insufficient for the required system performance.
Reconfiguration and/or additional resources will be required.
3.6.2 Sources of Latency
The following are common sources of latency.
• Loss and recovery
• Slow receivers
• Wildcard receivers with overly broad interest patterns
• High resource utilization
• 'Busy' applications - messages backed up in event queues. Your UM Development Team can tell you if your
UM applications use event queues.
3.6.3 Runtime Diagnostics
Use the following to validate a healthy system.
• UM monitoring metrics are active as a sign of liveness
• Pre-defined thresholds are not breached in the monitoring systems
• Application logs are clear of errors/warnings
• Required processes are running i.e. lbmrd
• General system resources are within pre-defined bounds i.e. CPU, memory, network stats (specific to the
applications)
• Operating system e.g. UDP buffers for loss detection
Use the following to validate the system is operating within acceptable limits.
• Monitor memory usage and growth over time.
–Applications with increasing memory could indicate a future problem
–Could indicate apps are misconfigured for required scalability
–Event queue growth (also UM metrics)
–Theoretical memory limits for 32-bit/64-bit processes, dependent on OS and language choice.
• Spikes in CPU usage across multiple systems indicate a system wide event and could be an indication of a
"crybaby" receiver causing source retransmissions or a rogue wildcard receiver.
• Monitor network activity across the environment.
–Switch failures / unplugged cable
–Network Interface Card (NIC) failures
–Symptoms of NIC bonding failure
22 Monitoring
–Significant changes in overall network traffic could indicate a problem such as loss (discussed later)
• Look for correlated activity. Do CPU spikes and network spikes lead or lag each other?
• Build thresholds based on an established business as usual (BAU) baseline.
• These diagnostics and UM metrics could indicate a general problem with the applications, network or under-
lying hardware.
Chapter 4
Startup/Shutdown Procedures
In a multicast environment, only the applications and monitoring tools need to be started. If using Persistence,
the store daemon (umestored) also needs to be started. Likewise, use of the UM Router requires starting the UM
Router daemon (tnwgd).
In a unicast-only environment, one or more resolver daemons (lbmrd) are typically required. It is recommended that
you start the lbmrd before starting the applications.
Informatica recommends that you shutdown applications using UM sources and receivers cleanly, even though UM
is able to cope with the ungraceful shutdown and restart of applications and UM daemons.
A failed assertion could lead to immediate application shutdown. If opting to restart a UM client or lbmrd, no other
components need be restarted. Failed assertions should be logged with Informatica support.
4.1 Topic Resolution
Your UM development or administration team should anticipate the time and bandwidth required to resolve all topics
when all applications initially start. This team should also establish any restarting restrictions.
Operations staff should not have any direct topic resolution tasks aside from monitoring the increased CPU and
bandwidth usage.
Topic resolution is the discovery of a topic's transport session information by a receiver to enable the receipt of
topic messages. Although in a multicast environment, topic resolution does not need to be started or shutdown, it
does use network resources and can cause deaf receivers and other problems if not operating properly. See Topic
Resolution in the UM Concepts Guide for more detailed information.
Applications cannot deliver messages until topic resolution completes. UM monitoring statistics are active before all
topics resolve. In a large topic space approximately 10,000 topics) topic resolution messages may be 'staggered' or
rate controlled, taking potentially several seconds to complete.
For example, 10,000 topics at the default value of 1,000 for resolver_initial_advertisements_per_second (con-
text) will take 10 seconds to send out an advertisement for every topic. If all receiving applications have been
started first, fully resolving all topics may not take much more than 10 seconds. The rate of topic resolution can also
be controlled with the resolver_initial_advertisement_bps (context) configuration option. Topic advertisements
contain the topic string and approximately 110 bytes overhead. Topic queries from receivers contain no overhead,
only the topic string.
24 Startup/Shutdown Procedures
4.2 UM Applications
Your UM development team should provide you with the application names, resident machines and startup param-
eters, along with a sequence of application/daemon startups and shutdowns.
The following lists typical application startup errors.
• Lack of resources
• License not configured - LOG Level 3: CRITICAL: LBM license invalid [LBM_LICENSE_FILENAME nor LB←-
M_LICENSE_INFO are set]
• Cannot bind port - lbm_context_create: could not find open TCP server port in range.
Too many applications may be running using the UM context's configured port range on this machine. This
possibility should be escalated to your UM development team.
Application is possibly already running. It is possible to start more than one instance of the same UM appli-
cation.
• Invalid network interface name / mask - lbm_config: line 1: no interfaces matching criteria
• Multiple interfaces detected - LOG Level 5: WARNING: Host has multiple multicast-capable interfaces; going
to use [en1][10.10.10.102]
This message appears for multi-homed machines. UM is not explicitly configured to use a single interface. This
may not cause an issue but requires configuration review by your UM development team.
4.3 Indications of Possible Application Shutdown
A UM application shutdown may not be obvious immediately, especially if you are monitoring scores of applications.
The following lists events that may indicate an application has shutdown.
• The Process ID disappears. Consider a method to monitor all process IDs (PIDs).
• You notice the existence of a core dump file on the machine.
• UM statistics appear to reduce in volume or stop flowing.
• In an Application Log, one or more End Of Session (EOS) events signaling the cessation of a transport
session. This may indicate a source application may have shut down. Your UM development team must
explicitly log LBM_MSG_EOS events. Some EOS events may be delayed for some transports.
• In an Application Log, disconnect events (LBM_SRC_EVENT_DISCONNECT) for unicast transports (if im-
plemented) indicate UM receiver applications have shutdown.
4.4 Unicast Topic Resolver (lbmrd)
If not using multicast topic resolution, one or more instances of lbmrd must be started prior to stating applications.
Unicast resolver daemons require an XML configuration file and multiple resolver daemons can be specified by your
UM development team for resiliency. For more information on Unicast Topic Resolution, see Unicast UDP TR.
Execute the following command on the appropriate machine to start a unicast topic resolver (lbmrd) from command
line:
4.5 Persistent Store (umestored) 25
lbmrd --interface=ADDR -L daemon_logfile.out -p PORT lbmrd.cfg
For more information on the lbmrd command-line, see Lbmrd Man Page.
To stop the resolver, use the kill command. If a unicast resolver daemon terminates, you need to restart it.
Observe the lbmrd logfile for errors and warnings
To make the lbmrd a Windows Service, see UM Daemons as Windows Services.
If running multiple lbmrds and an lbmrd in the list becomes inactive, the following message appears in the clients'
log files:
unicast resolver "<ip>:<port>" went inactive
If all unicast resolver daemons become inactive, the following message appears in the clients' log files:
No active resolver instances, sending via inactive instance
After all topics are resolved, daemons do not strictly need to be running unless you restart applications. Resolver
daemons do not cache or persist state and do not require other shutdown maintenance.
4.5 Persistent Store (umestored)
Stores can operate in disk-backed or memory-only mode specified in the store's XML configuration file. Disk backed
stores are subject to the limitations of the disk hardware. Stores should not be run on virtual machines and each
store should have a dedicated disk. UM holds messages in memory until written to disk.
4.5.1 Starting a Store
Execute the following command on the appropriate machine to start a (umestored) from command line:
umestored config-file.xml
For more information on the umestored command-line, see Umestored Man Page.
• Record umestored PID to monitor process presence for failure detection.
• On Microsoft Windows®, monitor the umestored service.
• Observe the umestored logfile for errors and warnings
In disk mode, stores create two types of files.
• Cache file - contains the actual persisted messages, and can grow to be very large over time. It is important
to ensure that there is enough disk space to record the appropriate amount of persisted data.
• State file - contains information about the current state of each client connection and is much smaller.
Stores do not create any files in memory-only mode.
To make the Store a Windows Service, see UM Daemons as Windows Services.
26 Startup/Shutdown Procedures
4.5.2 Restarting a Store
Perform the following procedure to restart a store.
1. If the store is still running, kill the PID (Linux) or use the Windows Service Manager® to stop the Windows
service.
2. If you want a clean "start-of-day" start, delete the cache and state files. The location of these files is specified
in the store's XML configuration file.
3. Wait 20-30 seconds to let timeouts expire. Due to its use of connectionless protocols, Persistence depends
upon timeouts. Therefore, do not rapidly restart the store.
4. Run the command: "umestored config-file.xml". umestored automatically uses the existing cache and state
files after a graceful shutdown and resumes as part of the current messaging stream at its last known position.
4.5.3 Common Startup and Shutdown Issues
• Cache and state directories don't exist.
• Disk space - Cache files contain the actual persisted messages, and can grow to be very large over time. It
is important to ensure that there is enough disk space to record the appropriate amount of persisted data.
• Configuration error - UM parses a store's XML configuration file at startup, reporting errors to standard error.
• Configuration error - UM reports other configuration errors the store's log file.
• Missing license details.
4.6 UM Router (tnwgd)
When a UM Router starts it discovers all sources and receivers in the topic resolution domains to which it connects.
This results in a measurable increase and overall volume of topic resolution traffic and can take some time to
complete depending upon the number of sources, receivers, and topics. The rate limits set on topic resolution also
affect the time to resolve all topics.
See also Topic Resolution.
4.6.1 Starting a UM Router
Execute the following command on the appropriate machine to start a UM Router (tnwgd) from command line:
tnwgd config-file.xml
Informatica recommends:
• Record tnwgd PID to monitor process presence for failure detection.
• Monitor the tnwgd logfile for errors and warnings.
4.7 UM Daemons as Windows Services 27
For more information on the tnwgd command-line, see Tnwgd Man Page. To make the UM Router a Windows
Service, see UM Daemons as Windows Services.
4.6.2 Restarting a UM Router
Perform the following procedure to restart a UM Router.
1. If the UM Router is still running, kill the PID.
2. Wait 20-30 seconds to let timeouts expire. After a restart new proxy sources and receivers must be created
on the UM Router. Applications will not use the new proxies until the transport timeout setting expires for
the old connections. Until this happens, applications may appear to be "deaf" since they are still considering
themselves as connected to the "old" UM Router proxies. Therefore, do not rapidly restart the UM Router.
3. Run the command: tnwgd config-file.xml
4.7 UM Daemons as Windows Services
On the Microsoft Windows platform, the UM daemons can be used either from the command line or as Windows
Services. The available UM Services are:
Executable File Description Service Display Name Man Page
lbmrds.exe UDP-based Unicast Topic Resolver "LBMR Store Daemon" man page
srsds.exe TCP-based Topic Resolver "UM Stateful Topic Resolution Service" man page
storeds.exe Persistent Store "UME Store Daemon" man page
tnwgds.exe UM Router (DRO) "Ultra Messaging Gateway" man page
Note that the Ultra Messaging Manager daemon ("ummd") is not offered as a Windows Service at this time.
As of UM version 6.12, the above UM daemons work similarly with respect to running as a Windows Service. See
the individual man pages for differences.
Before beginning, make sure that the license key is provided in a way that the service will be able to access it. In
particular, if you are using an environment variable to set the license key, it must be a system environment variable,
not user.
There are 4 overall steps to running a UM daemon as a Windows Service:
1. Install the Windows Service
2. Configure the Daemon
3. Configure the Windows Service
4. Start the Windows Service
All 4 steps must be completed before the Service can be used.
28 Startup/Shutdown Procedures
4.7.1 Install the Windows Service
There are two ways to install a UM daemon as a Windows Service:
• Product package installer.
• Command line.
Product package installer
When installing the product using the package installer, the dialog box titled "Choose Components" provides one
or more check boxes for UM daemons to be installed as services. You may check any number of the boxes and
proceed with the installation.
Note that for any box not checked, the software for that daemon is still copied onto the machine. This allows for
installation as a Windows Service at a later time using the Command Line method.
Also note that it is not necessary to use the package installer at all. The UM files can simply be copied to the
machine. In that case, this step is skipped altogether, and the Command Line method must be used to install the
daemons as Windows Services. See Copy Windows Runtime Files for details.
Command line
If a daemon was not installed as a Windows Service from the product's package installer (possibly because the
package installer was not used), daemons can be installed at a later time from the command line. In this case, the
Service install step is combined with the Configure the Windows Service step below.
4.7.2 Configure the Daemon
UM daemons are configured via XML configuration files. These files must be created and managed by the user.
Each individual daemon needs its own separate XML configuration file.
Informatica recommends developing and testing the daemon configuration files interactively, using the command-
line interface of each daemon. Do not run the daemon as a Windows Service until the daemon configuration has
been validated and tested. This provides the fastest test cycle while the configuration is being developed and
finalized.
The configuration files should be located on the hosts that are intended to run the daemons in files/folders of the
user's choosing.
For more information on configuring and running the daemons interactively, see:
Executable File Description Configuration Details Man Page
lbmrds.exe UDP-based Unicast Topic Resolver lbmrd Configuration File man page
srsds.exe TCP-based Topic Resolver SRS Configuration File man page
storeds.exe Persistent Store Configuration Reference for Umestored man page
tnwgds.exe UM Router (DRO) XML Configuration Reference man page
4.7.3 Configure the Windows Service
At this point, you should have the Daemon XML configuration file(s) prepared and available on the host which is to
run the desired daemon(s) (See Configure the Daemon). And you should have tested the configuration using the
daemon interactively to verify is correct operation.
4.7 UM Daemons as Windows Services 29
Each daemon's Windows Service must now be configured so that the Service can find the proper daemon configu-
ration file.
You also need to decide how the daemon writes log messages to the Windows Event Logging system. Log mes-
sages are categorized into different severity levels: "info", "notice", "warning", "err", "alert", "emerg". By default, the
daemons will write log messages of category "warning" and above to the Windows Event Log. If desired, this can
be adjusted with the "-e" flag, shown below. Be aware that setting the severity level below "warning" can result in
very many messages being written to the Windows Event Log. Also be aware that messages of all severity levels
are written to the daemon's log file, independent of the "-e" setting.
Attention
To enter the commands below, you need a Command Prompt window running as Administrator. (One way to
do this is to right-click on the Command Prompt icon and select "More >Run as administrator".)
To perform this step, each daemon service executable must be interactively executed from a command prompt with
the following command-line flags. The exact command-line flag set depends on whether the daemon was already
installed as a Windows Service when the UM package was installed.
Service was previously installed
Use this command if the daemon has already been installed as a Windows Service, perhaps using the product's
Package Installer.
daemonexe -s config -e warn c:\daemon_config_file_path
Where "daemonexe" is the name of the desired daemon's executable (see UM Daemons as Windows Ser-
vices for executable names).
Service was NOT previously installed
Use this command if the daemon has not yet been installed as a Windows Service, perhaps because the
product's package installer was not used.
daemonexe -s install -e warn c:\daemon_config_file_path
Where "daemonexe" is the desired daemon's executable (see UM Daemons as Windows Services for exe-
cutable names).
Some daemons have additional Service settings that should be configured prior to use. For example, the SRS
has two additional log files that can only be set using command-line flags. See the individual daemon's Windows
Service man page for each daemon's details (see UM Daemons as Windows Services for man page links).
4.7.4 Start the Windows Service
Windows Services are controlled by the "Services" control panel. See your Windows documentation for information
on controlling Windows Services.
30 Startup/Shutdown Procedures
4.7.5 Remove the Windows Service
There are several ways to remove the UM daemons as Windows Services:
• Uninstall the software (if it was installed by the Package Installer). This is done using the normal Windows
"Add or Remove Programs" control panel. Performing this step removes the Windows Service, and also
removes the installed files.
• Manually remove the service using the daemon's executable program. Performing this step only removes the
Windows Service; the installed files remain.
Manual Removal
Use this command to remove the daemon as a Windows Service. Note that the software files will remain.
daemonexe -s remove
Where "daemonexe" is the desired daemon's executable (see UM Daemons as Windows Services for exe-
cutable names).
4.8 UM Analysis Tools
Tools available to analyze UM activity and performance.
4.8.1 Packet Capture Tools
• Wireshark® is an open-source network packet analysis tool, for which Informatica provides 'dissectors' de-
scribing our packet formats. It is used to open and sift through packet capture files, which can be gathered by
a variety of both software and hardware tools.
• Tshark is a command-line version of Wireshark.
• Tcpdump is the primary software method for gathering packet capture data from a specific host. It is available
on most Unix-based systems, though generally gathering packet captures with the tool requires super-user
permissions.
For more information about Wireshark please visit https://www.wireshark.org/. (The UM plugins are
part of the current release.)
4.8.2 Resource Monitors
• Top is a system resource monitor available on Linux/Unix that presents a variety of useful data, such as
CPU use (both average and per-CPU), including time spent in user mode, system mode, time processing
interrupts, time spent waiting on I/O, etc.
4.8 UM Analysis Tools 31
• Microsoft ®Windows® System Resource Manager manages Windows Server® 2008 processor and memory
usage with built-in or custom resource policies.
•prstat is a resource manager for Solaris® that provides similar CPU and memory usage information.
4.8.3 Process Analysis Tools
•pstack dumps a stack trace for a process (pid). If the process named is part of a thread group, then
pstack traces all the threads in the group.
•gcore generates a core dump for a Solaris, Linux, and HP-UX process. The process continues after core has
been dumped. Thus, gcore is especially useful for taking a snapshot of a running process.
4.8.4 Network Tools
•netstat provides network statistics for a computer's configured network interfaces. This extensive command-
line tool is available on Linux/Unix based systems and Windows operating systems.
•wget is a Linux tool that captures content from a web interface, such as a UM daemon web monitor. Its
features include recursive download, conversion of links for off-line viewing of local HTML, support for proxies,
and more.
•netsh is a Windows utility that allows local or remote configuration of network devices such as the interface.
4.8.5 UM Tools
• lbmmoncache is a utility that monitors both source notification and source/receiver statistics. Contact UM
Support for more information about this utility.
• lbtrreq restarts the topic resolution process. Contact UM Support for more information about this utility.
4.8.6 UM Debug Flags
The use of UM debug flags requires the assistance of UM Support. Also refer to the following Knowledge Base
articles for more information about using debug flags.
•Using debug flags
•Using debug flags in application code
•Using debug flags with daemons
•Using debug flags with daemons running as windows services
32 Startup/Shutdown Procedures
Chapter 5
Monitoring UM with the lbmmon API
5.1 Monitoring Introduction
Messaging systems often employ real-time monitoring and rapid human intervention to prevent the system from
becoming unstable. The design of UM encourages stable operation by allowing you to pre-configure how UM will
use resources under all traffic and network conditions. Hence manual intervention is not required when those
conditions occur.
Monitoring UM still fills important roles other than maintaining stable operation. Chiefly among these are capacity
planning and a better understanding of the latency added by UM as it recovers from loss. Collecting accumulated
statistics from all sources and all receivers once per day is generally adequate for these purposes.
5.1.1 Why Monitor?
Monitoring can aid different groups within an organization.
• Developers can spot bugs that impact system performance.
• Performance tuning groups can pinpoint under-performing receivers.
• Testing groups can understand the reaction of a system to stresses like random packet loss during pre-
production testing.
• Network or middleware management groups can use monitoring to ensure a production system continues to
operate within its design criteria.
5.1.2 What to Monitor
Before discussing the monitoring statistics that are built into UM, we mention two things that are probably more
important to monitor: connectivity and latency. UM provides some assistance for monitoring these, but the final
responsibility rests with your applications.
34 Monitoring UM with the lbmmon API
Connectivity
If you monitor only one thing, monitor connectivity, defined as the ability of your system components to talk to
each other when needed Connectivity failures generally indicate a software, hardware, or network failure and
generally require prompt attention. UM features like End Of Source (EOS) events, new source notifications,
and receiver connect/disconnect events may help in application connectivity monitoring. See the lbmprice.c
example to see techniques for using these to build an awareness of when components of the system come and
go.
Message Latency
If you monitor only two things, monitor connectivity and the latency of every message. Connectivity monitoring
will catch the hard failures and latency monitoring will catch the soft failures. Many impending hard failures in
hardware, software, and networks show up first as rises in average latency or as latency spikes.
5.2 Monitoring Methods
UM provides the following methods to monitor your UM activities.
• Use UM API function calls within your applications to retrieve statistics and deliver them to your monitoring
application.
• Use the UM Monitoring API to more easily retrieve and send statistics to your monitoring application.
• Use Automatic Monitoring to easily employ the UM Monitoring API to monitor UM activity at an UM context
level.
• Use the Ultra Messaging SNMP Agent and MIB to monitor statistics through a Network Management System.
You purchase the Ultra Messaging SNMP Agent separately.
• Use the Ultra Messaging System Monitoring Option to monitor components of a Ultra Messaging deploy-
ment such as application host, transports, topic resolution domains and application instances. The System
Monitoring Option uses its own user interface. You purchase the Ultra Messaging System Monitoring Option
separately.
5.3 UM API Functions and Data Structures
The UM API contains functions that retrieve various statistics for a context, event queue, source or receiver. This
section lists the functions and constructors you can use to retrieve statistics, along with the data structures UM uses
to deliver the statistics. Refer to the UM API documentation (UM C API, UM Java API or UM .NET API) for specific
information about the functions and constructors. Links to the data structures appear in the tables to provide quick
access to the specific statistics available.
5.3.1 Context Statistics
Context statistics help you monitor topic resolution activity, along with the number of unknown messages received
and the number of sends and responses that were blocked or returned EWOULDBLOCK. Context statistics also
contain transport statistics for Multicast Immediate Messaging (MIM) activity and transport statistics for all the
sources or receivers in a context.
5.3 UM API Functions and Data Structures 35
C API Function Java or .NET API Constructor Data Structure
lbm_context_retrieve_stats() LBMContextStatistics() lbm_context_stats_t
lbm_context_retrieve_rcv_transport_←-
stats()
LBMReceiverStatistics() lbm_rcv_transport_stats←-
_t
lbm_context_retrieve_src_transport_←-
stats()
LBMSourceStatistics() lbm_src_transport_stats←-
_t
lbm_context_retrieve_im_rcv_transport←-
_stats()
LBMMIMReceiverStatistics() lbm_rcv_transport_stats←-
_t
lbm_context_retrieve_im_src_transport←-
_stats()
LBMMIMSourceStatistics() lbm_src_transport_stats←-
_t
5.3.2 Event Queue Statistics
Event Queue statistics help you monitor the number of events currently on the queue, how long it takes to service
them (maximum, minimum and mean service times) and the total number of events for the monitoring period. These
statistics are available for the following types of events.
• Data messages
• Request messages
• Immediate messages
• Wildcard receiver messages
• I/O events
• Timer events
• Source events
• Unblock events
• Cancel events
• Callback events
• Context source events
• Total events
• Age of events
When monitoring Event Queue statistics you must enable the Event Queue UM Configuration Options queue_←-
age_enabled (event_queue),queue_count_enabled (event_queue),queue_service_time_enabled (event_←-
queue). UM disables these options by default, which produces no event queue statistics.
C API Function Java or .NET API Constructor Data Structure
lbm_event_queue_retrieve_stats() LBMEventQueueStatistics() lbm_event_queue_stats←-
_t
36 Monitoring UM with the lbmmon API
5.3.3 Source or Receiver Transport Statistics
You can retrieve transport statistics for different types of transports. In addition, you can limit these transport
statistics to a specific source sending on the particular transport or a specific receiver receiving messages over
the transport. Source statistics for LBT-RM, for example, include the number of message datagrams sent and the
number of retransmissions sent. For receiver LBT-RM, statistics include, for example, the number of message
datagrams received and number of UM messages received.
Note
None of the transport statistics are topic level statistics. Currently UM does not provide statistics that show the
activity of a specific topic on one or more transport sessions.
C API Function Java or .NET API Constructor Data Structure
lbm_rcv_retrieve_transport_stats() LBMReceiverStatistics() lbm_rcv_transport_stats←-
_t
lbm_rcv_retrieve_all_transport_stats() LBMReceiverStatistics() lbm_rcv_transport_stats←-
_t
lbm_src_retrieve_transport_stats() LBMSourceStatistics() lbm_src_transport_stats←-
_t
5.4 UM Monitoring API
The UM Monitoring API (see lbmmon.h or the LBMMonitor classes in the Java API and the .NET API) provides a
framework to easily gather UM transport statistics and send them to a monitoring or reporting application. Transport
sessions for sources and receivers, along with all transport sessions for a given context can be monitored. This API
can be implemented in one of two ways.
• Build monitoring into your application with the UM Monitoring API functions.
• Turn on Automatic Monitoring with UM configuration options. See Automatic Monitoring.
An application requesting transport monitoring is called a monitor source, and an application accepting statistics is
a monitor receiver. These monitoring objects deal only with transport session statistics and should not be confused
with UM sources and UM receivers, which deal with UM messages. Statistics for both UM sources and UM receivers
can be forwarded by a monitor source application.
Both a monitor source and monitor receiver comprise three modules:
• A format module, responsible for serializing and de-serializing the statistics. The proper transmission between
monitor source and monitor receiver requires this serialization.
• A transport module that is responsible for sending and receiving statistics data.
• A control module, responsible for gathering the statistics, and calling the appropriate functions from the format
and transport modules.
5.4 UM Monitoring API 37
You can substitute format and transport modules of your own choosing or creation. UM Monitoring provides the
following sample modules:
• LBMMON CSV format module
• LBMMON UM transport module
• LBMMON UDP transport module
• LBMMON SNMP transport module
To view the source code for all LBMMON transport modules, see LBMMON Example Source Code found on the
Related Pages tab in the C Application Programmer's Interface.
5.4.1 Monitoring Process Flow
The overall process flow appears in the diagram below.
1. Your application creates the monitor source controller, specifying the format and transport modules to use. It
also calls lbmmon functions to start monitoring an UM context, UM source or UM receiver.
2. The monitor source controller passes those statistics to the format module serialization function.
3. The monitor source controller passes the resulting serialized data to the transport module send function.
4. The transport module transmits the data over some transport medium (such as a network).
38 Monitoring UM with the lbmmon API
5. The monitor receiver controller transport module receives the serialized data. (Your monitoring application
has already created the monitor receiver controller specifying the format and transport modules to use, along
with the application callback functions to use upon the receipt of UM source or UM receiver statistics data.)
6. The monitor receiver controller calls the format module's de-serialization function.
7. Finally, the monitor receiver controller passes the statistics to your monitoring application via the specified
application callback functions.
Your applications only calls functions in the controller modules, which calls the appropriate functions in the transport
and format modules.
5.4.2 API Framework Flexibility
The segregation of UM Monitoring into control, format, and transport modules provides flexibility for monitor re-
ceivers in two ways.
• Allows you to use languages for which no UM API or binding exists.
• Allows you to use monitoring products which do not integrate with UM.
As an example, assume you have a Perl application which currently gathers statistics from other network appli-
cations (or, you are simply most comfortable working in Perl for such tasks). There is no Perl binding for UM.
However, Perl can handle UDP packets very nicely, and can pick apart CSV data easily. By implementing a UDP
transport module to be used by the monitor sources, your Perl application can read the UDP packets and process
the statistics.
5.4.3 Initial Monitoring Questions
If you can answer the following questions, you're already on your way.
1. What format module will you use? LBMMON CSV Format module or a different one.
2. What transport module will you use? One of the 3 LBMMON modules or a different one.
3. Do you want to monitor individual sources/receivers, or an entire context? The difference is in how the
statistics are aggregated.
• Monitoring a context aggregates transport statistics for all sources and receivers associated with a
context, by transport. Note that this is not by transport type. The default configuration for TCP, for
example, allocates up to 10 ports, forming up to 10 separate transport sessions. Absent any specific
instructions, UM allocates sources and receivers to these 10 transports in a round-robin fashion. So the
statistics for a specific transport on a context will aggregate all sources and receivers which use that
specific transport.
• Ultra Messaging recommends that you monitor either a context or source/receiver, but not both. For
example if Topic1 and Topic2 are mapped to the same transport session (which is the only transport
session for the context) and you monitor both the receivers and the context, you will get 3 identical sets
of statistics: one for Topic1 reporting the stats for it's transport session, one for Topic2 reporting the
stats for the same transport session, and one for the transport session via the context.
• In the case of wildcard receivers, only the context may be monitored. UM creates wildcard receivers
dynamically as it detects topics which match the wildcard pattern. The application does not have access
to these dynamically-created receivers. So the only way to monitor a wildcard receiver is to monitor the
context on which it was created.
5.4 UM Monitoring API 39
4. Should statistics be sent automatically, or on demand?
• Automatic sending of statistics is by far the simplest approach. You simply indicate how often the
statistics should be gathered and sent. The rest is taken care of.
• On-demand is somewhat more involved. Your application decides when statistics should be gathered
and sent. If you intend to use the arrival of statistics as a type of heartbeat, this is the method you
should use.
The following sections present more discussion and sample source code about starting monitor sources, monitor
receivers and the LBMMON format and transport modules.
5.4.4 Creating a Monitoring Source
The following examples demonstrate how to use the UM Monitoring API to enable monitoring in your application.
First, create a monitoring source controller:
lbm_context_t *ctx;
lbm_src_t *src;
lbm_rcv_t *rcv;
lbmmon_sctl_t *monctl;
if (lbmmon_sctl_create(&monctl, lbmmon_format_csv_module(), NULL,
lbmmon_transport_lbm_module(), NULL) == -1)
{
fprintf(stderr, "lbmmon_sctl_create() failed\n");
exit(1);
}
The above code tacitly assumes that the ctx, src, and rcv variables have been previously assigned via the appropri-
ate UM API calls.
The monitoring source controller object must be passed to subsequent calls to reference a specific source controller.
One implication of this is that it is possible to have multiple monitoring source controllers within a single application,
each perhaps monitoring a different set of objects.
In the above example, the default CSV format module and default UM transport module are specified via the pro-
vided module functions lbmmon_format_csv_module() and lbmmon_transport_lbm_module().
5.4.5 Specifying the Object to Monitor
Once a monitoring source controller is created, the application can monitor a specific context using:
if (lbmmon_context_monitor(monctl, ctx, NULL, 10) == -1)
{
fprintf(stderr, "lbmmon_context_monitor() failed\n");
exit(1);
}
The above example indicates that statistics for all transports on the specified context will be gathered and sent every
10 seconds.
A UM source can be monitored using:
if (lbmmon_src_monitor(monctl, src, NULL, 10) == -1)
{
fprintf(stderr, "lbmmon_src_monitor() failed\n");
40 Monitoring UM with the lbmmon API
exit(1);
}
Finally, an UM receiver can be monitored using:
if (lbmmon_rcv_monitor(monctl, rcv, NULL, 10) == -1)
{
fprintf(stderr, "lbmmon_rcv_monitor() failed\n");
exit(1);
}
The two above examples also request that statistics for all transports on the specified source or receiver be gathered
and sent every 10 seconds.
Statistics can also be gathered and sent in an on-demand manner. Passing 0 for the Seconds parameter to
lbmmon_context_monitor(),lbmmon_src_monitor(), or lbmmon_rcv_monitor() prevents the automatic gath-
ering and sending of statistics. To trigger the gather/send process, use:
lbmmon_sctl_sample(monctl);
Such a call will perform a single gather/send action on all monitored objects (contexts, sources, and receivers) which
were registered as on-demand.
As part of application cleanup, the created monitoring objects should be destroyed. Each individual object can be
de-registered using lbmmon_context_unmonitor(),lbmmon_src_unmonitor(), or lbmmon_rcv_unmonitor().
Finally, the monitoring source controller can be destroyed using:
lbmmon_sctl_destroy(monctl);
Any objects which are still registered will be automatically de-registered by lbmmon_sctl_destroy().
5.4.6 Receiving Monitoring Data
To make use of the statistics, an application must be running which receives the monitor data. This application
creates a monitoring receive controller, and specifies callback functions which are called upon the receipt of source
or receiver statistics data.
Use the following to create a monitoring receive controller:
lbmmon_rctl_t *monctl;
lbmmon_rctl_attr_t *attr;/
*"rcv_statistics_cb" ... "ctx_statistics_cb" are user functions defined elsewhere
*/
lbmmon_rcv_statistics_func_t rcvcb = { rcv_statistics_cb };
lbmmon_src_statistics_func_t srccb = { src_statistics_cb };
lbmmon_evq_statistics_func_t evqcb = { evq_statistics_cb };
lbmmon_ctx_statistics_func_t ctxcb = { ctx_statistics_cb };
if (lbmmon_rctl_attr_create(&attr) != 0)
{
fprintf(stderr, "call to lbmmon_rctl_attr_create() failed, %s\n",
lbmmon_errmsg());
exit(1);
}
if (lbmmon_rctl_attr_setopt(attr, LBMMON_RCTL_RECEIVER_CALLBACK, (void *) &rcvcb,
sizeof(rcvcb)) != 0)
{
fprintf(stderr, "call to lbmmon_rctl_attr_setopt() failed, %s\n",
lbmmon_errmsg());
exit(1);
}
5.4 UM Monitoring API 41
if (lbmmon_rctl_attr_setopt(attr, LBMMON_RCTL_SOURCE_CALLBACK, (void *) &srccb,
sizeof(srccb)) != 0)
{
fprintf(stderr, "call to lbmmon_rctl_attr_setopt() failed, %s\n",
lbmmon_errmsg());
exit(1);
}
if (lbmmon_rctl_attr_setopt(attr, LBMMON_RCTL_EVENT_QUEUE_CALLBACK, (void *)
&evqcb, sizeof(evqcb)) != 0)
{
fprintf(stderr, "call to lbmmon_rctl_attr_setopt() failed, %s\n",
lbmmon_errmsg());
exit(1);
}
if (lbmmon_rctl_attr_setopt(attr, LBMMON_RCTL_CONTEXT_CALLBACK, (void *) &sctxcb,
sizeof(ctxcb)) != 0)
{
fprintf(stderr, "call to lbmmon_rctl_attr_setopt() failed, %s\n",
lbmmon_errmsg());
exit(1);
}
if (lbmmon_rctl_create(&monctl, lbmmon_format_csv_module(), NULL,
lbmmon_transport_lbm_module(), (void *)transport_options, attr) != 0)
{
fprintf(stderr, "call to lbmmon_rctl_create() failed, %s\n", lbmmon_errmsg());
exit(1);
}
if (lbmmon_rctl_attr_delete(attr) != 0)
{
fprintf(stderr, "call to lbmmon_rctl_attr_delete() failed, %s\n",
lbmmon_errmsg());
exit(1);
}
As in the earlier example, the default CSV format module and default UM transport module are specified via the
provided module functions lbmmon_format_csv_module() and lbmmon_transport_lbm_module().
As an example of minimal callback functions, consider the following example:
void rcv_statistics_cb(const void *AttributeBlock, const lbm_rcv_transport_stats_t
*Statistics)
{
lbm_ulong_t source = LBMMON_ATTR_SOURCE_NORMAL;
if (lbmmon_attr_get_source(AttributeBlock, &source) != 0)
{
source = LBMMON_ATTR_SOURCE_NORMAL;
}
switch (Statistics->type)
{
case LBM_TRANSPORT_STAT_TCP:
handle_rcv_tcp_statistics();
break;
case LBM_TRANSPORT_STAT_LBTRM:
switch (source)
{
case LBMMON_ATTR_SOURCE_IM:
handle_rcv_im_lbtrm_statistics();
break;
default:
handle_rcv_lbtrm_statistics();
break;
}
break;
42 Monitoring UM with the lbmmon API
case LBM_TRANSPORT_STAT_LBTRU:
handle_rcv_lbtru_statistics();
break;
}
} / *rcv_statistics_cb */
void src_statistics_cb(const void *AttributeBlock, const lbm_src_transport_stats_t
*Statistics)
{
lbm_ulong_t source = LBMMON_ATTR_SOURCE_NORMAL;
if (lbmmon_attr_get_source(AttributeBlock, &source) != 0)
{
source = LBMMON_ATTR_SOURCE_NORMAL;
}
switch (Statistics->type)
{
case LBM_TRANSPORT_STAT_TCP:
handle_src_tcp_statistics();
break;
case LBM_TRANSPORT_STAT_LBTRM:
switch (source)
{
case LBMMON_ATTR_SOURCE_IM:
handle_src_im_lbtrm_statistics();
break;
default:
handle_src_lbtrm_statistics();
break;
}
break;
case LBM_TRANSPORT_STAT_LBTRU:
handle_src_lbtru_statistics();
break;
}
} / *src_statistics_cb */
void ctx_statistics_cb(const void *AttributeBlock, const lbm_context_stats_t *
Statistics)
{/
*Handle context stats */
}
void evq_statistics_cb(const void *AttributeBlock, const lbm_event_queue_stats_t *
Statistics)
{/
*Handle event queue stats */
}
Upon receipt of a statistics message, the appropriate callback function is called. The application can then do what-
ever is desired with the statistics data, which might include writing it to a file or database, performing calculations,
or whatever is appropriate.
Beyond the actual statistics, several additional pieces of data are sent with each statistics packet. These data are
stored in an attribute block, and are accessible via the lbmmon_attr_get_∗() functions. Currently, these data include
the IPV4 address of machine which sent the statistics data, the timestamp (as a time_t) at which the statistics were
generated, and the application ID string supplied by the sending application at the time the object was registered
for monitoring. See lbmmon_attr_get_ipv4sender(),lbmmon_attr_get_timestamp(), and lbmmon_attr_get_←-
appsourceid() for more information.
5.5 Monitoring Transport Modules 43
5.5 Monitoring Transport Modules
The lbmmon library comes with three pre-written transport modules:
LBM
A normal UM topic is used to send/receive statistics.
UDP
Statistics are sent to a simple multicast or unicast UDP port.
SNMP
Identical to LBM but with some configuration parameters pre-set to be compatible with the UM SNMP agent
component.
5.5.1 The LBM Transport Module
The LBM transport module understands several options which may be used to customize your use of the module.
The options are passed via the TransportOptions parameter to the lbmmon_sctl_create() and lbmmon_rctl_←-
create() functions, as a null-terminated string containing semicolon-separated name/value pairs.
The lbmmon.c example program's command-line option "--transport-opts" is used for the TransportOptions string
for the LBM transport module.
The following name/value pairs are available:
•config=file_name specifies a configuration file. This file is processed in a manner similar to lbm_config().
However, unlike lbm_config(), the current default attributes are not changed. Instead, the options parsed
from the configuration file are applied only to the UM objects created by the module.
•topic=topic_name specifies the topic name to use for sending and receiving statistics. By default, the topic
/29west/statistics is used.
•wctopic=topic_pattern specifies (for monitor receivers only) a wildcard pattern to be used to receive statis-
tics.
•context|option_name=option_value specifies UM a configuration option for the monitoring context.
•source|option_name=option_value specifies UM a configuration option for the source used to publish mon-
itoring data.
•receiver|option_name=option_value specifies UM a configuration option for the receiver used to subscribe
to monitoring data.
•wildcard_receiver|option_name=option_value specifies UM a configuration option for the wildcard receiver
used to subscribe to monitoring data.
As an example, assume your application needs to use a special configuration file for statistics. The following call
allows your application to customize the UM transport module using the configuration file stats.cfg.
lbmmon_sctl_t *monctl;
const char *tropt = "config=stats.cfg";
if (lbmmon_sctl_create(&monctl, lbmmon_format_csv_module(), NULL,
lbmmon_transport_lbm_module(), tropt) == -1)
{
fprintf(stderr, "lbmmon_sctl_create() failed\n");
exit(1);
}
44 Monitoring UM with the lbmmon API
If your application also needs to use a specific topic for statistics, the following code specifies that, in addition to the
configuration file, the topic StatisticsTopic be used for statistics.
lbmmon_sctl_t *monctl;
const char *tropt = "config=stats.cfg;topic=StatisticsTopic";
if (lbmmon_sctl_create(&monctl, lbmmon_format_csv_module(), NULL,
lbmmon_transport_lbm_module(),
tropt) == -1)
{
fprintf(stderr, "lbmmon_sctl_create() failed\n");
exit(1);
}
It is important to use the same topic and configuration for both monitor sources and receivers. Otherwise your
applications may send the statistics, but the monitor receiver won't be able to receive them.
To view the source code for the LBM transport module, see Source code for lbmmontrlbm.c.
5.5.2 The UDP Transport Module
The UDP transport module understands several options which may be used to customize your use of the module.
The options are passed via the TransportOptions parameter to the lbmmon_sctl_create() and lbmmon_rctl_←-
create() functions, as a null-terminated string containing semicolon-separated name/value pairs.
The lbmmon.c example program's command-line option "--transport-opts" is used for the TransportOptions string
for the UDP transport module.
The UDP module supports sending and receiving via UDP unicast, UDP broadcast, and UDP multicast. The
following name/value pairs are available:
•address=dest_ip specifies the unicast IP address to which statistics are sent via UDP. Applicable to sender
only.
•port=port_num is the IP port packets are sent to. Defaults to 2933.
•interface=interface_spec specifies the network interface over which multicast UDP is sent or received. See
Specifying Interfaces for formats.
•mcgroup=ip is the multicast group on which to send and receive UDP packets.
•bcaddress=ip specifies the broadcast address to which UDP packets are sent. Applicable to sender only.
•ttl=val specifies the TTL for each multicast UDP packet. Applicable to sender only.
To view the source code for the UDP transport module, see Source code for lbmmontrudp.c.
5.5.3 The SNMP Transport Module
The SNMP transport modules operates in identical fashion to The LBM Transport Module. Some configuration
options are hard-coded to be compatible with the UM SNMP Agent component.
To view the source code for the UDP transport module, see Source code for lbmmontrlbmsnmp.c.
5.6 Monitoring Format Modules 45
5.6 Monitoring Format Modules
The lbmmon library comes with one pre-written format module:
CSV
Statistics are formatted in textual CSV (Comma-Separated Values) form.
5.6.1 The CSV Format Module
The CSV format module sends the statistics as simple comma-separated values. Options are passed via the
FormatOptions parameter to the lbmmon_sctl_create() and lbmmon_rctl_create() functions, as a null-terminated
string containing semicolon-separated name/value pairs.
The lbmmon.c example program's command-line option "--format-opts" is used for the FormatOptions string for
the CSV format module.
The following name/value pairs are available:
•separator=character specifies a single character to be used as field separator. Defaults to comma.
To view the source code for the CSV format module, see Source code for lbmmonfmtcsv.c.
5.7 Automatic Monitoring
Instead of building a monitoring capability into your application using the UM Monitoring API, automatic monitoring
allows you to easily produce monitoring statistics with the UM Monitoring API by setting a few simple UM configura-
tion options. Automatic monitoring does not require any changes to your application. See Automatic Monitoring
Options for more information.
You can enable Automatic Monitoring for either or both of the following.
• Transport Statistics - Automatic monitoring of transport statistics reflect data for all the transport sessions
within the UM context. You cannot, however, receive statistics for an individual transport session. Essentially,
you turn on automatic monitoring of a context's transport sessions by configuring monitor_interval (context).
The use of the Ultra Messaging SNMP Agent requires configuring monitor_transport (context) to lbmsnmp.
• Event Queue Statistics - Automatic Monitoring of Event Queues provides statistics for all the Event Queues
within the UM context. You turn on automatic monitoring of a context's Event Queues by configuring
monitor_interval (event_queue).
You can also set environment variables to turn on automatic monitoring for all UM contexts (transports and event
queues).
5.8 Monitoring Examples
This section demonstrates the use of the two UM monitoring example applications described in the C examples.
We present advice based on what we have seen productively monitored by customers and our own knowledge of
46 Monitoring UM with the lbmmon API
transport statistics that might be of interest. Of course, what you choose to monitor depends on your needs so
merge these thoughts with your own needs to determine what is best for you.
5.8.1 lbmmon.c
The example application lbmmon.c acts as a Monitor Receiver and is provided in both executable and source
form. It writes monitoring statistics to the screen and can be used in conjunction with other example applications
(which act as the Monitor Sources). The following procedure uses lbmrcv and lbmsrc to create messaging traffic
and adds a configuration file in order to specify the LBT-RM transport instead of the TCP default. (The LBT-RM
transport displays more statistics than TCP.)
Since UM does not generate monitoring statistics by default, you must activate monitoring in your application. For
the example application, use the --monitor-ctx=n option where n is the number of seconds between reports.
The following procedure activates monitoring on the receiver, specifying the context (ctx) to create a complete set
of receiver statistics. You could activate monitoring in a similar fashion on the source and create source statistics.
To use lbmmon to view statistics from sample application output:
1. Create configuration file with the single option of source transport lbtrm and name it LBTRM.cfg.
2. Run lbmmon --transport-opts="config=LBTRM.cfg"
3. Run lbmrcv -c LBTRM.cfg --monitor-ctx="5" Arizona
4. Run lbmsrc -c LBTRM.cfg Arizona
After lbmsrc completes, the final output for lbmmon should closely resemble the following:
...
Source: LBTRM:10.29.1.78:4391:323382d8:224.10.10.10:4400
Transport: LBT-RM
LBT-RM messages received : 45455
Bytes received : 370000000
LBT-RM NAK packets sent : 0
LBT-RM NAKs sent : 0
Lost LBT-RM messages detected : 0
NCFs received (ignored) : 0
NCFs received (shed) : 0
NCFs received (retransmit delay) : 0
NCFs received (unknown) : 0
Loss recovery minimum time : 4294967295ms
Loss recovery mean time : 0ms
Loss recovery maximum time : 0ms
Minimum transmissions per individual NAK : 4294967295
Mean transmissions per individual NAK : 0
Maximum transmissions per individual NAK : 0
Duplicate LBT-RM data messages received : 0
LBT-RM messages unrecoverable (window advance) : 0
LBT-RM messages unrecoverable (NAK generation expiration): 0
LBT-RM LBM messages received : 10000000
LBT-RM LBM messages received with no topic : 0
LBT-RM LBM requests received : 0
Notes:
• The --transport-opt command-line option is a string passed to the desired transport module. The
format of this string depends on the specific transport module selected (defaults to "lbm"). See Monitoring
Transport Modules for details.
5.8 Monitoring Examples 47
• Although not shown above, the --format-opt command-line option is a string passed to the desired
format module. The format of this string depends on the specific format module selected (defaults to "csv").
See Monitoring Format Modules for details.
• Since this procedure was done on a single machine. No packets were lost and therefore lbmrcv did not
generate any NAKs and lbmsrc did not send any NCFs. If you run this procedure across a network, packets
may be lost and you would see statistics for NAKs, NCFs and loss recovery.
• This procedure activates monitoring on the receiver, specifying the context (--monitor-ctx) to create a
complete set of receiver transport statistics. You could activate monitoring in a similar fashion on the source
and create source statistics. Each set of statistics shows one side of the transmission. For example, source
statistics contain information about NAKs received by the source (ignored, shed, retransmit delay, etc.) where
receiver statistics contain data about NCFs received. Each view can be helpful.
• Moreover, as explained earlier in Specifying the Object to Monitor, individual receivers or sources can be
monitored instead of all transport activity for a context. For this procedure, use --monitor-rcv or
--monitor-src.
• You could run this procedure again specifying a different transport (LBT-RU or TCP) in the configuration file
and receive a different set of statistics. For descriptions of all the transport statistics, refer to the transport
statistics data structures in the C Application Programmer's Interface. Click on the Data Structures tab at the
top and click on lbm_rcv_transport_stats_t or lbm_src_transport_stats_t.
5.8.2 lbmmonudp.c and lbmmondiag.pl
The example application, lbmmonudp.c receives UM statistics and forwards them as CSV data over a UDP
transport. The Perl script, lbmmondiag.pl can read UDP packets and process the statistics, reporting Severity
1 and Severity 2 events. This script only reports on LBT-RM transports.
To run lbmmonudp.c with lbmmondiag.pl, use the following procedure.
1. Create configuration file with the single option of source transport lbtrm and name it LBTRM.cfg.
2. Run lbmmonudp -a 127.0.0.1 --transport-opts="config=LBTRM.cfg"
3. Run lbmrcv -c LBTRM.cfg --monitor-ctx="5" Arizona
4. Run lbmsrc -c LBTRM.cfg Arizona
5. Run lbmmondiag.pl
The following sections discuss some of the possible results of this procedure. Your results will vary depending upon
conditions in your network or if you run the procedure on a single machine.
Severity 1 — Monitoring Unrecoverable Loss
The most severe system problems are often due to unrecoverable datagram loss at the reliable transport level.
These are reported as severity 1 events by the lbmmondiag.pl example script. Many of the scalability and latency
benefits of UM come from the use of reliable transport protocols like LBT-RM and LBT-RU. These protocols provide
loss detection, retransmission, and recovery up to the limits specified by an application. Unrecoverable loss is
reported by the transport when loss repair is impossible within the specified limits.
Unrecoverable transport loss often (but not always) leads to unrecoverable message loss so it is very significant to
applications that benefit from lossless message delivery.
Unrecoverable loss can be declared by receivers when the transport_lbtrm_nak_generation_interval (receiver)
has ended without receipt of repair. Each such loss event is recorded by incrementing the unrecovered_tmo field
in lbm_rcv_transport_stats_t. Output from lbmmondiag.pl might look like this:
Sev1: 34 datagrams unrecovered due to NAK generation interval ending
48 Monitoring UM with the lbmmon API
Unrecoverable loss can also be triggered at receivers by notice from a source that the lost datagram has passed
out of the source's transmission window. Each such loss event is recorded by incrementing the unrecovered_txw
field in lbm_rcv_transport_stats_t. Output from lbmmondiag.pl might look like this:
Sev1: 249 datagrams unrecovered due to transmission window advancement
Severity 2 — Monitoring Rate Controller Activity
The data and retransmission rate controllers built into LBT-RM provide for stable operation under all traffic conditions.
These rate controllers introduce some latency at the source since that is generally preferable to the alternative of
NAK storms or other unstable states. The lbmmondiag.pl example script reports this activity as a severity 2 event
since latency is normally the only effect of their operation.
Activity of the rate controller indicates that a source tried to send faster than the configured transport_lbtrm_←-
data_rate_limit (context). Normally, this limit is set to the speed of the fastest receivers. Sending faster than this
rate would induce loss in all receivers so it is generally best to add latency at the source or avoid sending in such
situations.
The current number of datagrams queued by the rate controller is given in the rctlr_data_msgs field in lbm_src←-
_transport_stats_t. No more than 10 datagrams are ever queued. Output from lbmmondiag.pl might look like
this:
Sev2: 10 datagrams queued by data rate controller
Activity of the retransmission rate controller indicates that receivers have requested retransmissions in excess of
the configured transport_lbtrm_retransmit_rate_limit (context). Latency is added to retransmission requests in
excess of the limit to control the amount of latency they may add to messages being sent the first time. This behavior
avoids NAK storms.
The current number of datagrams queued by the retransmission rate controller is given in the rctlr_rx_msgs field
in lbm_src_transport_stats_t. No more than 101 datagrams are ever queued. Output from lbmmondiag.pl might
look like this:
Sev2: 101 datagrams queued by retransmission rate controller
Severity 2 — Monitoring Loss Recovery Activity for a Receiver
It is important to monitor loss recovery activity because it always adds latency if the loss is successfully repaired. UM
defaults generally provide for quite a bit of loss recovery activity before loss would become unrecoverable. Statistics
on such activity are maintained at both the source and receiver. Unrecoverable loss will normally be preceded by a
burst of such activity.
UM receivers measure the amount of time required to repair each loss detected. For each transport session, an
exponentially weighted moving average is computed from repair times and the maximum and minimum times are
tracked.
The total number of losses detected appears in the lost field in lbm_rcv_transport_stats_t. It may be multiplied
by the average repair time given in the nak_stm_mean field in lbm_rcv_transport_stats_t to estimate of the
amount of latency that was added to repair loss. This is probably the single most important metric to track for those
interested in minimizing repair latency. The lbmmondiag.pl script reports this whenever the lost field changes and
the average repair time is nonzero. Output might look like this:
Sev2: 310 datagrams lost
Sev2: 112.236 seconds estimated total latency due to repair of 564 losses
Note
This estimate only includes latency added in the recovery of lost messages. Requiring ordered delivery also
adds latency for all messages that arrive after the time of loss and before the time that repair arrives.
See the ordered_delivery (receiver) option to control this.
In addition to counting losses detected, UM reliable receivers also count the number of NAKs generated in the
naks_sent field in lbm_rcv_transport_stats_t. Output from lbmmondiag.pl might look like this:
Sev2: 58 NAKs sent
5.9 Interpreting LBT-RM Source Statistics 49
Those who are new to reliable multicast protocols are sometimes surprised to learn that losses detected do not
always lead to NAK generation. If a datagram is lost in the network close to the source, it is common for many
receivers to detect loss simultaneously when a datagram following the loss arrives. Scalability would suffer if all
receivers that detected loss reported it by generating a NAK at the same time. To improve scalability, a random
delay is added to NAK generation at each receiver. Since retransmissions are multicast, often only one NAK is
generated to repair the loss for all receivers. Thus it is common for the number of losses detected to be much larger
than the number of NAKs sent, especially when there are many receivers with similar loss patterns.
Severity 2 — Monitoring Loss Recovery Activity for a Source
For sources, the principal concern is often understanding how much the retransmission of messages already sent
at least once slowed down the source. Obviously, bandwidth and CPU time spent servicing retransmission requests
cannot be used to send new messages. This is the way that lossy receivers add latency for lossless receivers.
UM sources track the number of NAKs received in the naks_rcved field in lbm_src_transport_stats_t. The num-
ber of datagrams that they retransmit to repair loss is recorded in the rxs_sent field in lbm_src_transport_stats_t.
The number of retransmitted datagrams may be multiplied by the average datagram size and divided by the wire
speed to estimate the amount of latency added to new messages by retransmission. Output from the example
lbmmondiag.pl script might look like this:
Sev2: 7478 NAKs received
Sev2: 50 retransmissions sent
Sev2: 0.015056 seconds estimated total latency due to retransmissions
5.9 Interpreting LBT-RM Source Statistics
LBT-RM sources maintain many statistics that can be useful in diagnosing reliable multicast problems. See the
UM API documentation lbm_src_transport_stats_lbtrm_t Structure Reference for a description of the fields. The
remainder of this section gives advice on interpreting the statistics.
Divide naks_rcved by msgs_sent to find the likelihood that sending a message resulted in a NAK being received.
Expect no more than a few percent on a network with reasonable loss levels.
Divide rxs_sent by msgs_sent to find the ratio of retransmissions to new data. Many NAKs arriving at a source will
cause many retransmissions.
Divide naks_shed by naks_rcved to find the likelihood that excessive NAKs were ignored. Consider reducing loss
to avoid NAK generation.
Divide naks_rcved by nak_pckts_rcved to find the likelihood that NAKs arrived individually (∼1 ->individual N←-
AKs likely; ∼0 ->NAKs likely to have arrived grouped in a single packet). Individual NAKs often indicate sporadic
loss while grouped NAKs often indicate burst loss.
Divide naks_rx_delay_ignored by naks_ignored to find the likelihood that NAKs arrived during the ignore interval
following a retransmission. The configuration option transport_lbtrm_ignore_interval (source) controls the length
of this interval.
50 Monitoring UM with the lbmmon API
Chapter 6
UM Monitoring Statistics
This section contains links to API documentation pages with detailed descriptions of each UM statistic.
Note that certain statistics are initialized to the maximum unsigned value for the fields, i.e. all bits set (-1 for a signed
value). This special value indicates that the field has not yet been calculated. This is used for the "min" statistic in
a "minimum / maximum" statistics pair. For example, nak_tx_min is initialized to the maximum unsigned long, while
nak_tx_max is initialized to zero.
6.1 Monitoring Receiving Statistics
Although the API suggests that these statistics are on a topic basis, they are actually on a transport session basis.
Receiver objects are sometimes passed in as a means of identifying the desired transport session(s).
Type Stats Structure
LBT-TCP Receiving Stats lbm_rcv_transport_stats_tcp_t_stct
LBT-RM Receiving Stats lbm_rcv_transport_stats_lbtrm_t_stct
LBT-RU Receiving Stats lbm_rcv_transport_stats_lbtru_t_stct
LBT-IPC Receiving Stats lbm_rcv_transport_stats_lbtipc_t_stct
LBT-SMX Receiving Stats lbm_rcv_transport_stats_lbtsmx_t_stct
LBT-RDMA Receiving Stats lbm_rcv_transport_stats_lbtrdma_t_stct
Broker (UMQ) Receiver Stats lbm_rcv_transport_stats_broker_t_stct
6.2 Monitoring Sending Statistics
Although the API suggests that these statistics are on a topic basis, they are actually on a transport session basis.
Source objects are sometimes passed in as a means of identifying the desired transport session.
Type Stats Structure
LBT-TCP Sending Stats lbm_src_transport_stats_tcp_t_stct
52 UM Monitoring Statistics
Type Stats Structure
LBT-RM Sending Stats lbm_src_transport_stats_lbtrm_t_stct
LBT-RU Sending Stats lbm_src_transport_stats_lbtru_t_stct
LBT-IPC Sending Stats lbm_src_transport_stats_lbtipc_t_stct
LBT-SMX Sending Stats lbm_src_transport_stats_lbtsmx_t_stct
LBT-RDMA Sending Stats lbm_src_transport_stats_lbtrdma_t_stct
Broker (UMQ) Sending Stats lbm_src_transport_stats_broker_t_stct
6.3 Monitoring Context Statistics
Type Stats Structure
Context Stats lbm_context_stats_t_stct
6.4 Monitoring Event Queue Statistics
Type Stats Structure
Event Queue Statistics lbm_event_queue_stats_t_stct
Chapter 7
Troubleshooting UM Applications
7.1 Application Crashes
These are common application and daemon liveness issues.
7.1.1 Persistent Store Crashed
Symptom Cause Resolution
umestored process (PID) not running or a core file exists Contact Informatica Support
7.1.2 UM Router Crashed
Symptom Cause Resolution
tnwgd process (PID) not running or a core file exists Contact Informatica Support
7.1.3 Excessive Resource Use
54 Troubleshooting UM Applications
Symptom Cause Resolution
Excessive CPU usage, often 100%
• Application thread may be
deadlocked or spinning.
• Heap fragmentation on
source (with Smartheap)
• Overloaded transports
• Improper allocation of trans-
ports and applications caus-
ing kernel-level copying of
messages
Check "no-topic-messages" statis-
tic.
Check if SI% (time spent process-
ing system interrupts) is high; if so
there may be too many contexts in-
terested in the same transport data
Contact Informatica Support
7.1.4 Crash on deletion of an object
Symptom Cause Resolution
Application doesn't shutdown well
-or-
Application crashes during shutdown or
the deletion of an object
Improper object deletion See LBM Deletion Best
Practices
7.1.5 Datagram size mismatches
7.2 Assertions 55
Symptom Cause Resolution
Log message: endpoint portal
[s] unable to send: datagram
size mismatch. transport_XXX_←-
datagram_max_size must be prop-
erly configured.
Datagram sizes are inconsistently
configured across the system.
Coordinate the maximum datagram
size among the following configura-
tion options.
•resolver_datagram_max←-
_size (context)
•transport_tcp_datagram←-
_max_size (context)
•transport_lbtrm_←-
datagram_max_size
(context)
•transport_lbtru_←-
datagram_max_size
(context)
•transport_lbtipc_←-
datagram_max_size
(context)
•<max-datagram>for the
UM Router's Peer portal.
7.2 Assertions
UM produces assertions for conditions that are not expected to occur. They are not error conditions and indicate
extenuating conditions that we don't handle or don't expect.
7.2.1 Fatal Assertions
Fatal assertions appear for conditions that are not expected to occur and therefore require a shutdown.
Contact Informatica Support.
7.2.2 Non-fatal Assertions
Non-fatal assertions occur for unexpected conditions but do not require shutdown. Normal operation may continue.
Contact Informatica Support.
7.3 Message Loss
UM can recover message loss automatically but any recurring loss situation should be investigated and resolved.
56 Troubleshooting UM Applications
Symptom
The receiving application monitoring statistic, lost, reports the number of datagrams detected as lost.
In addition, NAKing activity also indicates message loss, however, you could turn NAKing off. (If you are concerned
about message loss, however, you should not turn it off.) Your source application monitoring statistics show values
for naks_rcved or nak_pckets_rcved. Receiving application monitoring statistics show values for naks_sent or
nak_pckets_sent. See Monitoring Transport Statistics.
Cause
Message loss in source-paced transports (LBT-RM, LBT-RU) can occur due to the following.
• Slow or overloaded receiver applications drop packets because, for example, the CPU can't service network
interrupts or UDP socket buffers.
• An overloaded network infrastructure drops packets because of, for example, switch buffer overflows or NIC
ring buffer overflows.
• A network component fails.
The following diagram depicts possible locations of message loss.
Resolution
Select the appropriate command from the table below to diagnose UDP socket buffer or NIC ring buffer loss.
Platform Buffer Command Result
Linux UDP socket buffer netstat -s Look for the UDP field, packet
receive errors
Linux NIC ring buffer ifconfig eth0 Look for RX packets ... over-
runs
Windows (7 and beyond) UDP socket buffer netstat -s Look for the UDP field, packet
receive errors
Solaris UDP socket buffer kstat |grep udpInOverflows Look for the UDP field, packet
receive errors
Solaris NIC ring buffer kstat -n bge0 |grep norcvbuf Look for RX packets ... over-
runs
Network component — Refer to the components doc-
umentation.
—
7.4 Unrecoverable Loss 57
Use the following table if you find loss with any of the above actions.
If you find loss in And the loss Resolution
UDP socket buffer occurs in small bursts Increase the UDP buffer size.
UDP socket buffer Is constant Escalate the issue to your UM development team.
NIC ring buffer — Maximize the NIC's receive descriptors. If this doesn't reduce
the loss, escalate the issue to your UM development team.
A network component — Escalate the issue to your network team or UM development
team.
If you do not find loss in any buffers or network components, contact Informatica Support.
Note: Microsoft® Windows® prior to version 7 does not report buffer loss accurately. If you believe you are experi-
encing UDP socket buffer overflows, you can try increasing the UDP buffer size. If you believe you are experiencing
NIC ring buffer overflows, contact your NIC vendor for assistance.
7.4 Unrecoverable Loss
Unrecoverable message loss refers to messages that have not been delivered and are not available for retransmis-
sion.
Symptom Cause Resolution
Monitoring statistics,
unrecovered_txw >zero
Unrecovered messages have been
removed from the source's trans-
mission and cannot be retransmit-
ted.
Identify the source of the loss using
Message Loss.
-or-
Contact Informatica Support.
Monitoring statistics,
unrecovered_tmo >zero
Identify the source of the loss using
Message Loss.
-or-
Contact Informatica Support.
Unrecovered messages that were
not recovered before the NAK gen-
eration interval expired.
Application log messages: LBM_←-
MSG_UNRECOVERABLE_LOSS
or LBM_MSG_UNRECOVERAB←-
LE_LOSS_BURST
Identify the source of the loss using
Message Loss.
-or-
Contact Informatica Support.
Either of the two causes mentioned above for unrecovered_txw or unrecovered_tmo.
See also LBT-RM reports unrecoverable loss. What should I do?
58 Troubleshooting UM Applications
7.5 High Latency
High latency can appear as latency spikes or just slow recovery processes such as Late Join.
Symptom Cause Resolution
Latency spikes Two most common causes:
• Misconfigured implicit batching
settings.
• Message Loss
1. Check implicit batching settings.
If you desire the lowest latency
at all times - which can bring a
penalty of higher CPU utilization
and increased probability for re-
ceivers to experience UDP buffer
overflows - set implicit_batching←-
_minimum_lengthh to 1. The
same effect can be achieved by
using the LBM_MSG_FLUSH flag
inside the lbm_src_send() call.
2. Check for loss in receiver statis-
tics. If loss is occurring, refer to
“Message Loss” on page 68.
If these scenarios are not the problem,
contact Informatica Support.
Slow Late Join operation — Contact Informatica Support
7.6 Deaf Receivers
Receiver deafness is a general term that means receivers are not getting messages. This could be due to messages
not being sent or simply not received. Awareness of this condition can come from many sources, such as business
people complaining that they are not receiving expected data or from your own monitoring of statistics, application
logs or the liveness of processes.
Use the following table to help detect topic or receiver deafness.
Symptom Cause Resolution
All transport monitoring statistics
stop "ticking".
When statistics for the affected
transports stop increasing, it indi-
cates an application has stopped
publishing data for some reason.
As a result the receivers of that
data will go deaf.
Restart the sending applications or
contact Informatica Support
LBT-RM or LBT-RU source mon-
itoring statistics, msgs_sent and
bytes_sent stop increasing
Indicates a source or sources has
gone off-line, resulting in receiver
deafness.
Restart the sending applications or
contact Informatica Support
LBT-RM or LBT-RU receiver mon-
itoring statistics, msgs_rcvd and
bytes_rcvd stop increasing
Indicates a receiver or receivers
have gone off-line.
Restart the receiving applications
or contact Informatica Support
7.7 Persistent Sending Problems 59
Symptom Cause Resolution
LBT-RU or TCP source monitor-
ing statistics, num_clients change
in unusual ways.
LBT-RU and TCP sources are able
to track the number of connected
clients. Unusual changes to the
number of connected LBT-RU or
TCP clients can indicate a prob-
lem. For example, clients dropping
off during trading hours, or rapid
changes in the number of clients.
Restart the sending and/or receiv-
ing applications or contact Infor-
matica Support
End of Session (EOS) messages
appear in applications logs.
When activity intervals expire, UM
issues EOS messages to receiving
applications. These appear in the
application logs.
Restart the receiving applications
or contact Informatica Support
The lbmrd Process ID (PID) disap-
pears on either a sending or receiv-
ing machine(s).
Topic resolution has stopped. May
not result in immediate topic deaf-
ness if topic resolution has already
been completed, but may result in
deafness if a new source or re-
ceiver comes up.
If the receiving context's monitor-
ing statistic tr_rcv_unresolved_←-
topics is zero, all topics are re-
solved and this may not be a prob-
lem. Either restart the receiving
applications or contact Informatica
Support
Deaf Receivers with the UM Gateway
After a receiver-side gateway is shutdown and restarted, receivers will be deaf to any forwarded traffic until EOS is
triggered.
Deaf Wildcard Receivers
Symptom Cause Resolution
Wildcard receivers are not receiving messages. —
• Be sure the resolver_cache (context) is
enabled (set to 1, which is the default.
• Be sure wildcard queries are enabled
by setting resolver_query_minimum_←-
interval (wildcard_receiver) is set to the
default of 50 ms.
7.7 Persistent Sending Problems
UM sources sending from a persistence application can encounter problems with flight size or the persistent store.
7.7.1 Flight Size
A blocked source due to flight size limitations is not a visible problem unless the operator can see all data flows
through the system.
60 Troubleshooting UM Applications
Symptom Cause Resolution
Monitoring statistics show a lower
level of activity for a Persistence
application than expected.
Source not sending because it is
blocked by flight size • Increase flight size by in-
creasing the allowable num-
ber of messages in flight
with the configuration option,
ume_flight_size (source).
• Slow down sources.
• Contact Informatica Support
7.7.2 Persistent Store Connectivity
Symptom Cause Resolution
Store log contains message, LBM_←-
SRC_EVENT_UME_STORE_ UNR←-
ESPONSIVE
Unresponsive store The receiver can track the inability
to complete registration by correlating
the receipt of a new source notifica-
tion with a LBM_MSG_UME_REG←-
ISTRATION_COMPLETE_EX event.
The new source notification is defined
by the option receiver resolver_←-
source_notification_function (con-
text). A timer should be set to log
a message or trigger an alarm if the
completion message is not received
after multiple seconds. To match the
source in the callback to the comple-
tion event, a string comparison should
be used on the lbm_msg->source
field. The timer for each source
should be canceled when its registra-
tion complete event is received.
The source can detect a loss of
quorum by checking the error string
passed in for the event LBM_SRC_←-
EVENT_UME_STORE_UNRESPO←-
NSIVE.
The string will contain "(quorum lost)".
Lost quorum (EUMENOREG) Restart the affected persistent stores.
Chapter 8
Contacting Informatica Support
Please include the following information when contacting Informatica Support.
• The contact information you would like us to use to contact you: email, cell phone number, office phone
number, etc.
• The UM product versions you are running.
• The platforms you run on and whether they are 32-bit or 64-bit.
• The UM components you use, such as store daemons, the UM Gateway, unicast topic resolver (lbmrd), etc.
• Is this problem ongoing / repeatable / reproducible?
• Were your applications starting and stopping?
• Was there a burst of message activity?
• All log files
• Any Wireshark or packet captures or a TCP dump.
62 Contacting Informatica Support
Chapter 9
UM Log Messages
9.1 UM Core Messages
Core-10055-131: could not allo-
cate lu bytes [s:d]
The system was not able to allocate
the amount of memory requested.
If the amount requested was par-
ticularly large, the problem may be
a misconfiguration; however if the
amount requested was relatively
small, the physical memory on the
machine may be over committed;
try moving some applications to an-
other machine.
Core-10055-2986: INFO: Smart
Source "%s" Late Join not set, but
UME store specified. Setting Late
Join.
Late Join must be enabled with U←-
ME stores. Late Join will be auto-
matically enabled if not set.
To prevent this message set Late
Join.
Core-10055-2991: INFO: Smart
Source "%s" specified ume_←-
retention_size_limit; ignoring op-
tion.
Smart Sources preallocate all
buffers so no buffer limit control is
required.
To prevent this message do not
specify ume_retention_size_limit.
Core-10055-2992: INFO: Smart
Source "%s" specified retransmit←-
_retention_size_limit; ignoring op-
tion.
Smart Sources preallocate all
buffers so no buffer limit control is
required.
To prevent this message do not
specify retransmit_retention_size←-
_limit.
Core-10055-2993: INFO: Smart
Source "%s" specified ume_←-
retention_size_threshold; ignoring
option.
Smart Sources preallocate all
buffers so no buffer release control
is required.
To prevent this message do not
specify ume_retention_size_←-
threshold.
Core-10055-2994: INFO: Smart
Source "%s" specified retransmit←-
_retention_size_threshold; ignor-
ing option.
Smart Sources preallocate all
buffers so no buffer release control
is required.
To prevent this message do not
specify retransmit_retention_size←-
_threshold.
Core-10055-2995: INFO: Smart
Source "%s" specified ume_sri_←-
flush_sri_request_response; ignor-
ing option.
Smart Sources do not use the im-
plicit batch buffer so no SRI record
control is required.
To prevent this message do not
specify ume_sri_flush_sri_←-
request_response.
64 UM Log Messages
Core-10055-2996: INFO: Smart
Source "%s" specified ume_sri_←-
immediate_sri_request_response;
ignoring option.
Smart Sources do not allow con-
trol over how quickly a source re-
sponds to a receiver's request for
an SRI record.
To prevent this message do not
specify ume_sri_immediate_sri_←-
request_response.
Core-10055-2997: INFO: Smart
Source "%s" specified ume_sri←-
_request_response_latency; ignor-
ing option.
Smart Sources do not allow con-
trol over how long a source waits
before sending an SRI packet in
response to a request from a re-
ceiver.
To prevent this message do
not specify ume_sri_request_←-
response_latency.
Core-10055-2998: INFO: Smart
Source "%s" specified retransmit←-
_retention_age_threshold; ignoring
option.
Smart Sources do not allow the
user to set the retransmit retention
age threshold.
To prevent this message do not
specify the retransmit_retention_←-
age_threshold.
Core-10055-3038: inflight went
negative - resetting to 0
A call to decrement the number of
inflight messages found the value
to be negative.
Nothing, it is forcibly set to 0 in this
case.
Core-10055-3170: WARNING: re-
ceived ACK with out-of-bounds
StoreID u/u
A UMP Source received an ac-
knowledgment packet with a store
that is not within the range of Store
IDs.
This should not happen and is not
a serious condition.
Core-10055-3171: WARNING: re-
ceived ACK from non-active store
u
UMP received ACK from non-active
store.
This is not a serious condition un-
less it happens frequently and mes-
saging is affected
Core-10055-3172: WARNING←-
: received stability sACK without
StoreID set
UMP received stability ACK or N←-
ACK without StoreID set.
This is not a serious condition un-
less it happens frequently and mes-
saging is affected.
Core-10055-3175: smart source
"%s" received ACK with unknown
type x
The smart source received an ACK
with an unknown type.
This is not a serious condition un-
less it happens frequently and mes-
saging is affected.
Core-10055-666: inflight bytes
would be negative, resetting to 0
A call to decrement the number of
inflight bytes would set it to be neg-
ative.
Nothing, it is forcibly set to 0 in this
case.
Core-10138-100: unable to sched-
ule EOF handling timer: s
EOFs are handled asyncronously
via a scheduled timer. An error
occurred while trying to schedule
this timer. The internals of UM will
continue to operate as though the
transport in question still exists.
Core-10138-110: can not send uni-
cast immediate messages to trans-
port threads. Source s:u.
Transport threads are not equipped
to receive unicast immediate mes-
sages.
Stop sending unicast immediate
messages to transport threads' re-
quest ports.
Core-10138-51: xsp returned from
transport mapping callback was
created on a different context -
choosing default
When an xsp object is created, a
user created context is passed in.
The returned xsp can only be used
with that context.
Core-10160-5564: INFO: Smart
Source "%s" set transport_lbtru_←-
use_session_id to 0; setting back
to 1 as only allowed value.
Smart Sources do not allow the
user to clear the use session ID at-
tribute.
To prevent this message do not
set transport_lbtru_use_session←-
_id to 0.
Core-10162-10: LBMC CNTL S←-
SF ULB creq header size incorrect.
Dropping. Origin: s:d.
The Source Side Filtering U←-
LB Connection Request message
header contains an incorrect size.
Check the source (IP:Port) for pos-
sible version mismatch or service
attack.
9.1 UM Core Messages 65
Core-10162-1: Source Side Filter-
ing ULB request from [s] but this
receiver does not have ordered_←-
delivery configured to -1 so source
side filtering will not be enabled and
this receiver will get all messages.
The user configured "transport_←-
source_side_filtering_behavior ulb"
but the receiver did not config-
ure "ordered_delivery -1" so source
side filtering can't be done.
Source Side Filtering of ULB is only
valid between ULB sources and
ULB receivers who have ordered←-
_delivery configured to -1.
Core-10162-2: Source Side Filter-
ing ULB request from [s] but re-
sponse port set to zero. No source
side filtering from this source so
this receiver will get all messages.
The receiver is registering Source
Side Filtering interest but the
source response port is zero. The
interest will not arrive at the source
and therefore this receiver will get
all messages.
This occurs when the source dis-
ables binding of the request port.
See request_tcp_bind_request_←-
port configuration option.
Core-10164-1: LBMR Topic Res-
olution Remote Domain Route
packet malformed (contains Do-
main ID 0). Dropping. Origin: s:d
LBMR Data received contain in-
valid data.
Check the source (IP:Port) for pos-
sible version mismatch or service
attack.
Core-10178-1: lbm_timer_expire←-
: Exceeded d timer expirations in
one iteration
UM encountered a condition where
the specified number of timers
were expiring at the same time.
This is undesirable and indicates
a CPU burst usage. To prevent
starvation of network processing,
some timers are deferred for pro-
cessing and network processing is
resumed. All timers are eventu-
ally processed with a minor delay -
this is acceptable behaviour. If this
message occurs frequently, contact
Informatica support for further guid-
ance.
Examine the configuration of this
process to determine if there are
timers likely to coincide in their
expirations or if there are many
sources created very quickly. If
there are, it is suggested that the
timers or source creation are stag-
gered.
Core-10190-1: unable to schedule
duplicate regids check timer: s
When new UMP delivery con-
trollers are created, UM checks
other UMP delivery controllers for
duplicates. This is handled asyn-
cronously via a scheduled timer.
An error occurred while trying to
schedule this timer.
Core-10190-6: ume_proactive_←-
keepalive_interval can't be 0 for X←-
SP context. Setting to default d.
Proactive keepalive in XSP con-
text can not be disabled. ume←-
_proactive_keepalive_interval was
set to the default value.
Set the receiver's ume_proactive←-
_keepalive_interval to a non zero
value that is less than the store's
keepalive-interval.
Core-10190-7: unable to schedule
preg response handling timer: s
Preg Response in the receiver
is handled asyncronously via a
scheduled timer. An error occurred
while trying to schedule this timer.
Core-10383-1: WARNING←-
: multiple_receive_maximum←-
_datagrams config could not
be implemented due to buffer
allocation failure
The multiple_receive_maximum←-
_datagrams configuration option
could not be implemented, be-
cause a buffer could not be allo-
cated
The physical memory on the ma-
chine may be over committed; try
moving some applications to an-
other machine.
Core-10383-2: WARNING←-
: multiple_receive_maximum_←-
datagrams or transport_lbtrm_←-
source_timestamp specified but
recvmmsg is NOT supported
The multiple_receive_maximum←-
_datagrams configuration option
could not be implemented, be-
cause recvmmsg is NOT supported
The recvmmsg() is available as of
Linux 2.6.32 and glibc 2.12.
66 UM Log Messages
Core-10383-3: WARNING: Turning
off multiple_receive_maximum←-
_datagrams and/or transport←-
_lbtrm_source_timestamp func-
tionality for socket because OS
returned ENOSYS for recvmmsg()
The multiple_receive_maximum_←-
datagrams configuration option will
not be used for this socket because
recvmmsg is NOT supported
The OS returned ENOSYS after
calling recvmmsg() which indicates
that the functionality is not imple-
mented
Core-10383-4: WARNING←-
: recvmmsg OS error
An error occurred using the
recvmmsg() functionality (en-
abled by setting the multiple←-
_receive_maximum_datagrams
configuration) to retrieve data.
Please use the operating system's
error code and description to fur-
ther understand the circumstances
of the error
Core-10403-01: SRS Controller (p)
is unable to request a stream of
data from the server (s:d)
SRS Controller is unable to request
a data stream from the server.
Make sure the server is running.
Core-10403-02: SRS Controller (p)
received an invalid message from
the SRS Server; dropping (s:d)
Received an invalid message pay-
load from the Server.
Check to make sure the correct
server is running and the correct
port is configured.
Core-10403-03: SRS Controller (p)
got a disconnect from the Server
(s:d)
The SRS Controller got a discon-
nect from the Server.
Check to make sure the correct
server is running and the correct
port is configured.
Core-10403-04: SRS Controller (p)
is unable to connect to the server
(s:d)
The SRS Controller is unable to
connect to the Server.
Check to make sure the server is
running and the correct port is con-
figured.
Core-10403-05: SRS Controller (p)
is unable to send the initial connec-
tion request to the server (s:d)
The SRS Controller is unable to
send the initial connection request
to the Server.
Check to make sure the correct
server is running and the correct
port is configured.
Core-10403-06: SRS Controller (p)
is unable to send data to the server
(s:d)
SRS Controller is unable to send
data to the server.
Make sure the server is running.
Core-10403-07: SRS Controller (p)
is unable to stop the communica-
tions thread to the server (s:d)
SRS Controller got an error trying
to stop the communications thread
upon shutdown.
Make sure the server is running.
Core-10403-08: SRS Controller (p)
received the initial connection from
the Server (s:d)
The SRS Controller got a connec-
tion from the Server.
This is informational only and no
action is required.
Core-10403-09: SRS Controller (p)
is unable to request more data on
the stream from the server (s:d)
SRS Controller is unable to request
more data on the data stream from
the server.
Make sure the server is running.
Core-10403-120: resolver_service
entry (s:u) already exist. Skipping
but continuing.
The lbm_context_attr_setopt/str←-
_setopt() detected duplicate
resolver_service entries. The
duplicate entries will be skipped.
Check the config file or code (if
config set via code) for duplicate
resolver_service entries. Also
check if lbm_config() is loaded
multiple times with the same
resolver_service entries
Core-10403-200: LBM SRS CTLR
(p) received a log msg from RSock
library (Level d: s)
SRS Controller got a log message
from the RSock library.
Check the RSock message for
more information.
Core-10403-20: SRS Controller (p)
could not format source string on
source create; src(s) error(s)
SRS Controller got an error when
formating the source string on a
source create
Refer to the error message in-
cluded at the end of this message.
Core-10403-21: SRS Controller (p)
could not parse the source string
from the server (s:d). Source(s) Er-
ror(s)
SRS Controller got an error trying
parse the source string from the
server.
Make sure the server is running
and is the correct version. Also
make sure no other processes are
sending messages on this IP:Port.
9.1 UM Core Messages 67
Core-10403-22: SRS Controller (p)
received a suspicious topic (s) from
the server (s:d).
SRS Controller got a suspicious
topic from the server.
Make sure the server is running
and is the correct version. Also
make sure no other processes are
sending messages on this IP:Port.
Core-10403-23: SRS Controller (p)
received a suspicious source (s)
from the server (s:d).
SRS Controller got a suspicious
source from the server.
Make sure the server is running
and is the correct version. Also
make sure no other processes are
sending messages on this IP:Port.
Core-10403-24: SRS Controller (p)
could not parse the data from the
server (s:d).
SRS Controller could not parse the
data from the server.
Make sure the server is running
and is the correct version. Also
make sure no other processes are
sending messages on this IP:Port.
Core-10403-25: SRS Controller (p)
received an invalid Message ID (d)
from the server (s:d).
SRS Controller received an invalid
Message ID from the server.
Make sure the server is running
and is the correct version. Also
make sure no other processes are
sending messages on this IP:Port.
Core-10403-31: SRS Controller (p)
could not parse the registration re-
sponse message from the server
(s:d).
SRS Controller could not parse
the registration response message
from the server.
Make sure the server is running
and is the correct version. Also
make sure no other processes are
sending messages on this IP:Port.
Core-10403-32: Domain ID (d)
from SRS (p) is different from ex-
isting Domain ID (d)
The SRS delivered a Domain ID
that does not match the existing
(known) Domain ID.
A Domain ID configuration mis-
match has been detected and
needs to be repaired.
Core-10403-34: Domain ID discov-
ered via SRS Controller (p); context
resides in Domain ID u.
Log message indicates a Domain
ID discovery.
This is not an error.
Core-10489-10: lbm_winevlog_←-
setup(): Unable to Register Event
Source: s
Windows error registering event
source
Contact Informatica Support.
Core-10489-1: <s>is an invalid
value for Windows event log level.
Defaulting to WARN
The value for the LBM service win-
dows event log level was not recog-
nized. The default WARN was as-
signed.
Valid values are ERROR, WARN,
INFO and NONE. Please specify
one of the valid values.
Core-10489-4: lbm_winevlog_←-
setup() CreateThread error: s
Unable to create Windows Thread. Contact Informatica Support.
Core-10489-5: lbm_winevlog_←-
setup() CreateMutex error: s
Unable to create Windows mutex Contact Informatica Support.
Core-10489-6: lbm_winevlog_←-
setup() error creating TL queue: s
Unable to create two-lock queue Contact Informatica Support.
Core-10528-3: The smart source p
will fragment messages when the
send message length plus config-
ured message headers [d bytes]
exceeds the transport's maximum
datagram size [d bytes]
The configured smart_src_max_←-
message_length plus LBM and ap-
plication specified message head-
ers exceeded the transport's data-
gram maximum size.
The smart source will fragment
messages when the send mes-
sage length plus headers exceeds
the transport's maximum message
length.
Core-3398-1: Socket close timed
out before receive buffer drain com-
plete. lu bytes discarded from
source (s).
Socket close timedout, but receive
buffer has not been drained fully
yet. On this close socket you may
see connection resets.
Core-3398-2: Error received while
calling wincompport_recv (s) from
source (s)
The Windows completion port call
to recv returned an error.
Look up the WSA error and take
appropriate action.
Core-5402-1: Hot-failover receiver
ignoring mismatched sequence
number size
A hot failover receiver dropped
a message that had a sequence
number size different than what it
was expecting.
Ensure that all hot failover sources
on the same topic are sending us-
ing the same sequence number
size
68 UM Log Messages
Core-5455-1: epoll_ctl: EPOLL_←-
CTL_DEL returned: errno:d:s
If errno is EBADF or ENOENT, File
descriptor is closed before lbm_←-
cancel_fd call
Core-5455-2: lbm_fd_cancel
epoll_ctl: epoll_op: d returned
errno:d:s
If errno is EBADF or ENOENT, file
desc is closed before lbm_cancel←-
_fd_call
Core-5480-1: OTR Initiated for
[s][s]
OTR has been initiated either for
the first time on this source, or it
has been at least a log_alert_←-
cooldown's length of time since the
last log alert.
Core-5480-2: OTR Repeated for
[s][s] (u times)
OTR has been ongoing for this
source.
Core-5480-3: no response re-
ceived to late join initiation request
- skipping late join
The receiver was unable to get a
response from a source claiming to
provide late join.
Contact Informatica support.
Core-5480-45: message delivery
failed: persrc ctlr p perrcv ctlr p sqn
x
Internal error attempting to process
recovered data.
Contact Informatica support
Core-5480-46: rxr ctlr p request
failed recovering sqns x - x from
perrcv ctlr p
Internal error attempting to initiate
recovery of data.
Contact Informatica support.
Core-5480-47: mtt register failed←-
: (u) [s]
Internal error while attempting to
process a command on an mtt
transport thread.
Contact Informatica support.
Core-5554-2: rsp_ctl received un-
known message from peer s:d with
info flags=[x,x]
A TCP peer received an unknown
control message.
Refer to the peer's IP:Port for the
source of the control message.
Core-5626-1: s: Option s is not rec-
ognized - ignoring.
The option name was not recog-
nized.
If the XML config is being used for
different versions of UM, and the
option is valid on versions of UM
other than the current application,
then this message may be ignored.
Otherwise, check your configura-
tion for invalid option names.
Core-5626-2: s: error parsing de-
fault value - ignoring.
The default-value attribute for this
option was invalid for this platform.
If the XML config is being used for
different versions of UM and/or dif-
ferent platforms, and the default-
value is valid on other installations
of UM, then this message may be
ignored. Otherwise, check your
configuration for invalid default-
value.
Core-5626-3: s: error parsing de-
fault value 's': s
The default-value attribute for this
option was not in the correct for-
mat.
Use the format appropriate for the
specific option.
Core-5626-4: s: error parsing rule
value - ignoring.
The rule value supplied was invalid
for this platform.
If the XML config is being used for
different versions of UM and/or dif-
ferent platforms, and the rule value
is valid on other installations of UM,
then this message may be ignored.
Otherwise, check your configura-
tion for invalid values.
Core-5626-5: s: error parsing rule
value 's': s
The rule value was not in the cor-
rect format.
Use the format appropriate for the
specific option.
9.1 UM Core Messages 69
Core-5626-6: s: error parsing rule
value - ignoring.
The rule value supplied was invalid
for this platform.
If the XML config is being used for
different versions of UM and/or dif-
ferent platforms, and the rule value
is valid on other installations of UM,
then this message may be ignored.
Otherwise, check your configura-
tion for invalid values.
Core-5626-7: s: error parsing rule
value 's': s
The rule value was not in the cor-
rect format.
Use the format appropriate for the
specific option.
Core-5688-1279: WARNING: T←-
CP session exists and uses a differ-
ent transport_session_maximum←-
_buffer [d] than requested [d].
Once a source has created a
transport session a subsequent
source joining the same transport
session cannot configure a differ-
ent transport_session_maximum←-
_buffer setting. Please refer to U←-
MS Objects section of the Design
Concepts in the documentation.
Core-5688-1280: WARNING: TCP
session exists and uses a different
transport_tcp_multiple_receiver←-
_behavior [d] than requested
[d].
Once a source has created a
transport session a subsequent
source joining the same trans-
port session cannot configure a
different transport_tcp_multiple_←-
behavior setting. Please refer to
UMS Objects section of the Design
Concepts in the documentation.
Core-5688-1281: WARNING: TCP
session exists and uses a different
transport_source_side_filtering←-
_behavior [d] than requested
[d].
Once a source has created a
transport session a subsequent
source joining the same trans-
port session cannot configure a
different transport_source_side_←-
filtering_behavior setting. Please
refer to UMS Objects section of the
Design Concepts in the documen-
tation.
Core-5688-1284: WARNING: L←-
BT-RM session for multicast ad-
dress s exists and uses a differ-
ent transport_lbtrm_tgsz [d] than
requested [d].
Once a source has created a
transport session a subsequent
source joining the same transport
session cannot configure a dif-
ferent transport_lbtrm_tgsz setting.
Please refer to UMS Objects sec-
tion of the Design Concepts in the
documentation.
Core-5688-1285: WARNING: L←-
BT-RM session for multicast ad-
dress s exists and uses a different
transport_lbtrm_ignore_interval [d]
than requested [d].
Once a source has created a
transport session a subsequent
source joining the same trans-
port session cannot configure a
different transport_lbtrm_ignore_←-
interval setting. Please refer to U←-
MS Objects section of the Design
Concepts in the documentation.
70 UM Log Messages
Core-5688-1286: WARNING:
LBT-RM session for multicast ad-
dress s exists and uses a different
transport_lbtrm_sm_minimum_←-
interval [d] than requested [d].
Once a source has created a trans-
port session a subsequent source
joining the same transport ses-
sion cannot configure a different
transport_lbtrm_sm_minimum←-
_interval setting. Please refer to
UMS Objects section of the Design
Concepts in the documentation.
Core-5688-1287: WARNING:
LBT-RM session for multicast ad-
dress s exists and uses a different
transport_lbtrm_sm_maximum_←-
interval [d] than requested [d].
Once a source has created a
transport session a subsequent
source joining the same transport
session cannot configure a dif-
ferent transport_lbtrm_maximum←-
_interval setting. Please refer to
UMS Objects section of the Design
Concepts in the documentation.
Core-5688-1288: WARNING: L←-
BT-RM session for multicast ad-
dress s exists and uses a differ-
ent transport_lbtrm_transmission←-
_window_size [d] than requested
[d].
Once a source has created a
transport session a subsequent
source joining the same transport
session cannot configure a differ-
ent transport_lbtrm_transmission←-
_window_size setting. Please re-
fer to UMS Objects section of the
Design Concepts in the documen-
tation.
Core-5688-1289: WARNING: L←-
BT-RM session for multicast ad-
dress s exists and uses a differ-
ent transport_lbtrm_transmission←-
_window_size [d] than requested
[d].
Once a source has created a
transport session a subsequent
source joining the same transport
session cannot configure a differ-
ent transport_lbtrm_transmission←-
_window_size setting. Please re-
fer to UMS Objects section of the
Design Concepts in the documen-
tation.
Core-5688-1290: WARNING: L←-
BT-RM session for multicast ad-
dress s exists and uses a dif-
ferent transport_lbtrm_coalesce_←-
threshold [d] than requested [d].
Once a source has created a
transport session a subsequent
source joining the same transport
session cannot configure a dif-
ferent transport_lbtrm_coalesce_←-
threshold setting. Please refer to
UMS Objects section of the Design
Concepts in the documentation.
Core-5688-1291: WARNING: L←-
BT-RU session exists and uses
a different transport_lbtru_client_←-
map_size [d] than requested [d].
Once a source has created a
transport session a subsequent
source joining the same transport
session cannot configure a differ-
ent transport_lbtru_client_map_←-
size setting. Please refer to UMS
Objects section of the Design Con-
cepts in the documentation.
9.1 UM Core Messages 71
Core-5688-1292: WARNING: LBT-
RU session exists and uses a differ-
ent transport_lbtru_transmission←-
_window_size [d] than requested
[d].
Once a source has created a
transport session a subsequent
source joining the same transport
session cannot configure a differ-
ent transport_lbtru_transmission←-
_window_size setting. Please re-
fer to UMS Objects section of the
Design Concepts in the documen-
tation.
Core-5688-1293: WARNING: LBT-
RU session exists and uses a differ-
ent transport_lbtru_transmission←-
_window_limit [d] than requested
[d].
Once a source has created a
transport session a subsequent
source joining the same transport
session cannot configure a differ-
ent transport_lbtru_transmission←-
_window_limit setting. Please re-
fer to UMS Objects section of the
Design Concepts in the documen-
tation.
Core-5688-1294: WARNING: LBT-
RU session exists and uses a differ-
ent transport_lbtru_ignore_interval
[d] than requested [d].
Once a source has created a
transport session a subsequent
source joining the same transport
session cannot configure a differ-
ent transport_lbtru_ignore_interval
setting. Please refer to UMS Ob-
jects section of the Design Con-
cepts in the documentation.
Core-5688-1295: WARNING: LBT-
RU session exists and uses a differ-
ent transport_lbtru_sm_minimum←-
_interval [d] than requested [d].
Once a source has created a
transport session a subsequent
source joining the same transport
session cannot configure a differ-
ent transport_lbtru_sm_minimum←-
_interval setting. Please refer to
UMS Objects section of the Design
Concepts in the documentation.
Core-5688-1296: WARNING←-
: LBT-RU session exists and
uses a different transport_lbtru←-
_sm_maximum_interval [d] than
requested [d].
Once a source has created a trans-
port session a subsequent source
joining the same transport ses-
sion cannot configure a different
transport_lbtru_sm_maximum←-
_interval setting. Please refer to
UMS Objects section of the Design
Concepts in the documentation.
Core-5688-1297: WARNING: LBT-
RU session exists and uses a differ-
ent transport_lbtru_client_activity←-
_timeout [d] than requested [d].
Once a source has created a
transport session a subsequent
source joining the same transport
session cannot configure a differ-
ent transport_lbtru_client_activity←-
_timeout setting. Please refer to
UMS Objects section of the Design
Concepts in the documentation.
72 UM Log Messages
Core-5688-1298: WARNING: LBT-
RU session exists and uses a dif-
ferent transport_lbtru_coalesce_←-
threshold [d] than requested [d].
Once a source has created a
transport session a subsequent
source joining the same transport
session cannot configure a dif-
ferent transport_lbtru_coalesce_←-
threshold setting. Please refer to
UMS Objects section of the Design
Concepts in the documentation.
Core-5688-1299: WARNING:
LBT-RU session exists and uses
a different transport_source_←-
side_filtering_behavior [d] than
requested [d].
Once a source has created a
transport session a subsequent
source joining the same transport
session cannot configure a differ-
ent transport_lbtru_source_side_←-
filtering_behavior setting. Please
refer to UMS Objects section of the
Design Concepts in the documen-
tation.
Core-5688-1302: WARNING: LBT-
IPC session exists and uses a dif-
ferent transport_lbtipc_sm_interval
[d] than requested [d].
Once a source has created a
transport session a subsequent
source joining the same transport
session cannot configure a dif-
ferent transport_lbtipc_sm_interval
setting. Please refer to UMS Ob-
jects section of the Design Con-
cepts in the documentation.
Core-5688-1303: WARNING:
LBT-IPC session exists and uses
a different transport_lbtipc_←-
transmission_window_size [d] than
requested [d].
Once a source has created a trans-
port session a subsequent source
joining the same transport ses-
sion cannot configure a different
transport_lbtipc_transmission←-
_window_size setting. Please
refer to UMS Objects section
of the Design Concepts in the
documentation.
Core-5688-1305: WARNING: Host
has multiple RDMA-capable inter-
faces; going to use [s][s].
As UMS initializes, it scans for R←-
MDA capable interfaces in the sys-
tem. If more than one is found
and a specific interface has not be
configured, UMS uses the first one
found.
Use "transport_lbtrdma_interface"
to specify the desired RDMA inter-
face.
Core-5688-13: could not allocate lu
bytes [s:d]
The system was not able to allocate
the amount of memory requested.
If the amount requested was par-
ticularly large, the problem may be
a misconfiguration; however if the
amount requested was relatively
small, the physical memory on the
machine may be over committed;
try moving some applications to an-
other machine.
Core-5688-14: could not reallocate
u bytes [s:d]
The system was not able to allocate
the amount of memory requested.
If the amount requested was par-
ticularly large, the problem may be
a misconfiguration; however if the
amount requested was relatively
small, the physical memory on the
machine may be over committed;
try moving some applications to an-
other machine.
9.1 UM Core Messages 73
Core-5688-1793: WARNING: Re-
quested receiver attributes will be
ignored, previous receiver for topic
[s] has already defined the at-
tributes.
Indicates a programming error
where a receiver topic lookup was
performed using different receiver
attributes. In this case the original
attributes are used.
Core-5688-1795: WARNING:
transport_lbtru_activity_timeout
[d] is less than transport_lbtru_←-
nak_generation_interval [d], this
can result in silent data loss if loss
occurs within the activity timeout
interval prior to the end of the
transport session.
If the transport_lbtru_activity_←-
timeout is less than the transport←-
_lbtru_nak_generation_interval it is
possible that a receiver can tear
down the transport session before
it was able to send a NAK for a
lossed message. When this hap-
pens the message is unrecover-
able.
Core-5688-1797: LBT-RU client s.u
sent unknown CREQ request x
UMS received a unicast message
with an invalid message type. The
message is dropped.
Contact Informatica support if this
message occurs frequently or if us-
ing only one version of Ultra Mess-
saging software.
Core-5688-1798: LBMD EV ver-
sion incorrect (u). Dropping.
UMS daemon received a message
with an invalid version number. The
message is dropped.
Contact Informatica support if this
message occurs frequently or if us-
ing only one version of Ultra Mess-
saging software.
Core-5688-1799: LBMD EV type
not support (u). Dropping.
UMS daemon received a message
with an invalid message type. The
message is dropped.
Contact Informatica support if this
message occurs frequently or if us-
ing only one version of Ultra Mess-
saging software.
Core-5688-17: could not allocate u
bytes for string dup [s:d]
The system was not able to allocate
the amount of memory required for
string duplication.
The physical memory on the ma-
chine may be over committed; try
moving some applications to an-
other machine.
Core-5688-1800: LBMD EV source
type support (u). Dropping.
UMS daemon received a message
from an unknown type of source.
The message is dropped.
Contact Informatica support if this
message occurs frequently or if us-
ing only one version of Ultra Mess-
saging software.
Core-5688-1801: LBMD EV un-
known next header x, ignoring
header.
UMS daemon received a message
with a header that was not rec-
ognized. This header will be ig-
nored, but the rest of the message
will be processed. This is poten-
tially due to a newer version of soft-
ware sending messages and is not
harmful.
Contact Informatica support if this
message occurs frequently or if us-
ing only one version of Ultra Mes-
saging.
Core-5688-1802: LBMD EV un-
known next header x, dropping
message.
UMS daemon received a message
with an invalid message type. The
message is dropped.
Contact Informatica support if this
message occurs frequently or if us-
ing only one version of Ultra Mess-
saging.
Core-5688-1804: HF message re-
ceiver function returned -1
An error occurred processing a
message received by a hot failover
receiver. The message was dis-
carded.
If this occurs frequently, contact In-
formatica support.
Core-5688-1807: LBM_DEB←-
UG_MAXSIZE is greater than
4,294,967,295. Limiting to max.
Maximum rollover file size is
capped at 4,294,967,295 (LBM_←-
DEBUG_LOG_ROLLOVER_SIZ←-
E_MAX)
Set LBM_DEBUG_MAXSIZE
and/or the parameter for lbm_←-
debugfile_maxsize() to a lesser
value to avoid this warning
74 UM Log Messages
Core-5688-1811: FATAL: WSA
startup error - d
FATAL: Error in starting Windows
Socket. The specific Windows
Sockets Error Code is returned in
the error message.
Core-5688-1833: WARNING: Host
has multiple multicast-capable in-
terfaces; going to use [s][s].
This warning occurs if the host
machine has multiple multicast-
capable interfaces detected, and
the context attributes do not spec-
ify an interface (via the resolver_←-
multicast_interface option). In this
situation the first interface found is
used.
Core-5688-1836: CRITICAL: DBL
support requested, but s not found.
Ensure s is in the search path to
enable DBL support.
This error results when dbl accel-
eration is specified through context
configuration, but we are unable to
locate the dbl shared library.
Try adding /opt/dbl/lib/ to your LD←-
_LIBRARY_PATH or the dbl.dll lo-
cation to your PATH on Windows.
Core-5688-1841: default thread
stack size is perhaps too small, u
bytes.
The IPC receiver has created a
thread for internal processing and
the default stack size is too small.
The size of the default stack size is
dumped and will then be set to a
larger size automatically.
Core-5688-1842: reset thread
stack size to u bytes.
The IPC receiver has created a
thread for internal processing and
the default stack size is too small
and is reallocated. This message
reports the new size of the stack.
Core-5688-1847: default thread
stack size is perhaps too small, u
bytes.
The IPC receiver has created a
thread for internal processing and
the default stack size is too small.
The size of the default stack size is
dumped and will then be set to a
larger size automatically.
Core-5688-1848: reset thread
stack size to u bytes.
The IPC receiver has created a
thread for internal processing and
the default stack size is too small
and is reallocated. This message
reports the new size of the stack.
Core-5688-1864: dbl thread join←-
: WFSO res=d, GLE=d
An error occurred while waiting for
the DBL thread to terminate.
Contact Informatica support.
Core-5688-1865: lbm_context_←-
delete: WFSO res=d, GLE=d
Error waiting for context thread to
cleanly exit.
Contact Informatica support.
Core-5688-1866: lbm_context_←-
delete: I/O leakage: global_←-
pending_io=d
Small memory leak occurred, prob-
ably due to race condition in Win-
dows.
Ignore, unless this happens many
times per hour.
Core-5688-1879: timer returned
error u [s]
UMS encountered an error expiring
timers while processing events.
Contact Informatica support.
Core-5688-1880: wait returned er-
ror u [s]
UMS encountered an error pro-
cessing an event on a file descrip-
tor. The event is dropped.
Contact Informatica support.
Core-5688-1881: handle events re-
turned error u [s]
The operating system returned er-
ror while processing a File Descrip-
tor
The associated CoreApi log mes-
sage should provide further infor-
mation.
Core-5688-1883: timer returned
error u [s]
UMS encountered an error expiring
timers while processing events.
Contact Informatica support.
9.1 UM Core Messages 75
Core-5688-1888: timer returned
error u [s]
UMS encountered an error expiring
timers while processing events.
Contact Informatica support.
Core-5688-1889: wait returned er-
ror u [s]
UMS encountered an error pro-
cessing an event on a file descrip-
tor. The event is dropped.
Contact Informatica support.
Core-5688-1890: handle events re-
turned error u [s]
Socket returned error while waiting
for context deletion.
Ignore, unless this happens many
times per hour.
Core-5688-1892: timer returned
error u [s]
UMS encountered an error expiring
timers while processing events.
Contact Informatica support.
Core-5688-261: LBT-RDMA: Client
Connection: failed to register client
A client has joined the LBT-RDMA
transport but an error occurred try-
ing to add the client to the client
map.
Core-5688-262: LBT-RDMA: Client
Disconnect: failed to remove client
A client has left the LBT-RDMA
transport but an error occurred try-
ing to remove the client to the client
map.
Core-5688-263: LBT-RDMA: VMS
connection failed event (s)
A connection failed event has been
received from the VRT library (for-
merly VMS library). Please refer to
the description given.
Core-5688-264: LBT-RDMA: un-
known VMS connection event ID: d
(s)
A connection event has been re-
ceived from the VRT library (for-
merly VMS library) but the event is
not understood. Please refer to the
event ID and description given.
Core-5688-265: LBT-RDMA: VMS
Memory error event: (s)
A memory error event has been re-
ceived from the VRT library (for-
merly VMS library). Please refer to
the description given.
Core-5688-266: LBT-RDMA: VMS
Generic library event: (s)
A generic event has been received
from the VRT library (formerly VMS
library). Please refer to the descrip-
tion given.
Core-5688-267: LBT-RDMA: VMS
unknown library event: d (s)
An event was received from the V←-
RT library (formerly VMS library)
that is not understood. Please re-
fer to the event ID and description
given.
Core-5688-270: LBT-RDMA: un-
known VMS log level: d (s)
A log event was received from the
VRT library (formerly VMS library)
that is not understood. Please re-
fer to the event ID and description
given.
Core-5688-271: LBT-RDMA: V←-
MS transport event received but not
expected: d (s)
A transport event was received
from the VRT library (formerly VMS
library) that is not expected. Please
refer to the event ID and description
given.
Core-5688-272: LBT-RDMA: V←-
MS fabric event received but not
expected: d (s)
A fabric event was received from
the VRT library (formerly VMS li-
brary) that is not expected. Please
refer to the event ID and description
given.
76 UM Log Messages
Core-5688-273: LBT-RDMA: VMS
unknown event class received: d
(s)
An event was received from the V←-
RT library (formerly VMS library)
that is not understood. Please re-
fer to the event ID and description
given.
Core-5688-276: lbtrdma_txw_←-
open: failed to subscribe to VMS
store (0xx:s:u)
An error occurred when trying to
join the LBT-RDMA transport given.
This could occur if the Topic Adver-
tisement is stale and the transport
has already been deleted.
Core-5688-277: lbtrdma_init:
Problem loading VMS libraray
The VRT library (formerly VMS li-
brary) required for LBT-RDMA can
not be loaded.
Verify correct installation.
Core-5688-278: lbtrdma_init: Can
not initialize the VMS libary (d)
The VRT library (formerly VMS li-
brary) required for LBT-RDMA re-
ported an initialization error (given).
Verify correct installation.
Core-5688-279: lbtrdma_init: Can
not initialize VMS client (d)
The VRT library (formerly VMS li-
brary) required for LBT-RDMA re-
ported a client initialization error
(given).
Verify correct installation.
Core-5688-27: WARNING: s con-
fig variable s is deprecated. Use s
instead.
Configuration option is deprecated
and has been replaced, Informatica
suggests the config option that can
be used instead.
Core-5688-280: lbtrdma_init: Can
not initialize VMS server (d)
The VRT library (formerly VMS li-
brary) required for LBT-RDMA re-
ported a server initialization error
(given).
Verify correct installation.
Core-5688-281: lbtrdma_init: Can
not register VMS event handler (d)
The VRT library (formerly VMS li-
brary) required for LBT-RDMA re-
ported the given error when regis-
tering an event callback function.
Verify correct installation.
Core-5688-282: lbm_transport_←-
lbtrdma_ctlr_delete: WFSO res=d,
GLE=d
The LBT-RDMA receiver thread
failed to shutdown during context
delete. Refer to the return status
and OS error code given.
Core-5688-283: default thread
stack size is perhaps too small, u
bytes.
The IPC receiver has created a
thread for internal processing and
the default stack size is too small.
The size of the default stack size is
dumped and will then be set to a
larger size automatically.
Core-5688-284: reset thread stack
size to u bytes.
The IPC receiver has created a
thread for internal processing and
the default stack size is too small
and is reallocated. This message
reports the new size of the stack.
Core-5688-285: LBT-RDMA
Error: Creating Receiver Thread
(d)
An error was returned when trying
to create the LBT-RDMA recevier
thread. Please refer to the OS error
number given.
Core-5688-286: CRITICAL: LBM li-
cense invalid [s]
Critical: The UMS license could not
be validated. Contact Informatica
support to verify the license.
9.1 UM Core Messages 77
Core-5688-287: WARNING: LBM
license warning [s]
Warning: The UMS license could
not be validated. Contact Informat-
ica support to verify the license.
Core-5688-288: CRITICAL: LBM
not licensed
Critical: The UMS license could not
be validated. Check the correct li-
cense is being specified. Contact
Informatica support to verify the li-
cense.
Core-5688-28: WARNING: s config
variable s is deprecated. Has no
effect.
Configuration option is deprecated
and has no effect, UMS will ignore
the config options and continue op-
eration.
Core-5688-2947: default thread
stack size is perhaps too small, u
bytes.
The Datagram Acceleration re-
ceiver has created a thread for in-
ternal processing and the default
stack size is too small. The size
of the default stack size is dumped
and will then be set to a larger size
automatically.
Core-5688-2948: reset thread
stack size to u bytes.
The Datagram Acceleration re-
ceiver has created a thread for in-
ternal processing and the default
stack size is too small and is real-
located. This message reports the
new size of the stack.
Core-5688-2950: NOTICE: could
not drain Datagram Acceleration
socket on exit. (Read d datagrams)
Proceeding with cleanup.
During shutdown, the Datagram
Acceleration thread closes all open
sockets and then drains all user-
space buffers.
No action necessary.
Core-5688-2951: WARNING:
Datagram Acceleration enabled,
but transport LBT-RM datagram
max size d >d. Packet larger than
MTU will be dropped.
Datagram Acceleration does not
support fragmentation. Ultra Mes-
saging displays this warning if the
datagram_max_size is greater than
9000 bytes, which is the maximum
frame size supported by Datagram
Acceleration.
To guarantee that no datagrams
are dropped for being too large, in-
struct UMS to fragment messages
itself using the specified attribute.
Core-5688-2952: NOTICE: Data-
gram Acceleration enabled, but
transport LBT-RM datagram max
size d >d. Packets larger than M←-
TU will be dropped.
Datagram Acceleration does not
support fragmentation. Ultra Mes-
saging displays this warning if the
datagram_max_size is greater than
1500 bytes, which is the standard
frame size supported by Datagram
Acceleration.
To guarantee that no datagrams
are dropped for being too large, in-
struct UMS to fragment messages
itself using the specified attribute.
Core-5688-2953: WARNING:
Datagram Acceleration enabled,
but transport LBT-RU datagram
max size d >d. Packet larger than
MTU will be dropped.
Datagram Acceleration does not
support fragmentation. Ultra Mes-
saging displays this warning if the
datagram_max_size is greater than
9000 bytes, which is the maximum
frame size supported by Datagram
Acceleration.
To guarantee that no datagrams
are dropped for being too large, in-
struct UMS to fragment messages
itself using the specified attribute.
Core-5688-2954: NOTICE: Data-
gram Acceleration enabled, but
transport LBT-RU datagram max
size d >d. Packets larger than M←-
TU will be dropped.
Datagram Acceleration does not
support fragmentation. Ultra Mes-
saging displays this warning if the
datagram_max_size is greater than
1500 bytes, which is the standard
frame size supported by Datagram
Acceleration.
To guarantee that no datagrams
are dropped for being too large, in-
struct UMS to fragment messages
itself using the specified attribute.
78 UM Log Messages
Core-5688-2955: WARNING:
Datagram Acceleration enabled,
but resolver datagram max size d
>d. Packet larger than MTU will
be dropped.
Datagram Acceleration does not
support fragmentation. Ultra Mes-
saging displays this warning if the
datagram_max_size is greater than
9000 bytes, which is the maximum
frame size supported by Datagram
Acceleration.
To guarantee that no datagrams
are dropped for being too large, in-
struct UMS to fragment messages
itself using the specified attribute.
Core-5688-2956: NOTICE: Data-
gram Acceleration enabled, but re-
solver datagram max size d >d.
Packets larger than MTU will be
dropped.
Datagram Acceleration does not
support fragmentation. Ultra Mes-
saging displays this warning if the
datagram_max_size is greater than
1500 bytes, which is the standard
frame size supported by Datagram
Acceleration.
To guarantee that no datagrams
are dropped for being too large, in-
struct UMS to fragment messages
itself using the specified attribute.
Core-5688-2959: WARNING:
deleting Datagram Acceleration
device returned d
The DBL device could not be
closed cleanly. DBL currently does
not return failure from the specified
function, but the log message is in-
cluded in case future versions re-
turn failure.
Core-5688-2972: LBT-RDMA←-
: Source Paced, wakeup not
expected
The LBT-RDMA transport is source
paced and no rate limiter is im-
plemented. Therefore, a wake-up
event should not occur.
Contact Informatica support.
Core-5688-3096: Unable to create
dctlr entry: s
This generally means memory
couldn't be allocated. The error
message included should specify
the exact error condition.
Core-5688-3101: NOTICE: UME
receiver has ordered_delivery set
to 0 and ume_explicit_ack_only set
to 1.
This notice is issued when a U←-
MP receiver controller is created
and is intended to warn of a po-
tentially undesireable configuration
setting. The UMP store considers
an explicit ACK for any sequence
number as an implicit ACK for all
prior sequence numbers. Turning
off ordered_delivery in combination
with explicit ACKs has the potential
to acknowledge messages which
have not yet been received by the
application.
Core-5688-3102: NOTICE: UME
group index u/u invalid, will set all
group indices to 0
UMP has received an updated
topic advertisement with an incon-
sistent UMP store group index.
UMP recovers by "flattening" the
stores into a single group.
Core-5688-3103: NOTICE: UME
store has out-of-range group index
u, setting to 0.
UMP has received an updated
topic advertisement specifying a
store with a group index which is
greater than the number of adver-
tised store groups. UMP recovers
by setting the group index for the
store in question to zero.
9.1 UM Core Messages 79
Core-5688-3104: NOTICE: setting
compatibility (UME <= 1.2) mode
for UME receiver. Extended events
will not be delivered.
The UMP receiver controller cre-
ation logic has detected a re-
ceiver utilizing an older style (UMP
version <= 1.2) registration call-
back function and turns off delivery
of any extended UMP registration
events.
Core-5688-3105: Receiver Ses-
sion ID specified. Specified RegID
will be ignored
The system has detected that both
a receiver Session ID and a re-
ceiver Reg ID have been specified
either in the configuration file, via
the configuration API or the RegID
specification callback.
Specify only one of the Session ID
or Reg ID.
Core-5688-3106: NOTICE: UME
group index u/u invalid, will set all
group indices to 0
UMP has received an updated
topic advertisement with an incon-
sistent UMP store group index.
UMP recovers by "flattening" the
stores into a single group.
Core-5688-3107: NOTICE: UME
store has out-of-range group index
u, setting to 0.
UMP has received an updated
topic advertisement specifying a
store with a group index which is
greater than the number of adver-
tised store groups. UMP recovers
by setting the group index for the
store in question to zero.
Core-5688-3108: Receiver Ses-
sion ID specified. Specified RegID
will be ignored
The system has detected that both
a receiver Session ID and a re-
ceiver Reg ID have been specified
either in the configuration file, via
the configuration API or the RegID
specification callback.
Specify only one of the Session ID
or Reg ID.
Core-5688-3117: WARNING: re-
ceived PREG RESP with out-of-
bounds StoreID
A registration response message
was received from a store but the
store ID in the message was in-
valid. The response is discarded.
Core-5688-3118: WARNING: re-
ceived PREG RESP with unused
StoreID
A registration response message
was received from a store, but the
source is not registered to that
store.
Check the source log for more
information. Source may have
restarted
Core-5688-3122: NOTICE: 1.2 U←-
ME store in use, turning off ACK to
source
For compatability, UMP will auto-
matically turn off sending ACKs to
sources when a V1.x UMP store is
used.
Core-5688-3156: NOTICE: setting
compatibility (UME <= 1.2) mode
for UME source. Extended events
will not be delivered.
UMP will tell you when it is setting
compatibility to UMP <= 1.2 mode
for UMP sources. When this setting
is in effect, no extended events will
not be delivered.
Core-5688-3157: NOTICE: ume←-
_message_stability_notification not
set. Setting for compatibility.
UMP will automatically set
the ume_message_stability_←-
notification configuration option
if it is not specified. Check the
configuration guide for more
information.
80 UM Log Messages
Core-5688-3160: WARNING: UME
source for topic "%s" store state ig-
nored (not in initial state)
UME source is not in the expected
state (initial state) when registration
is in progress. No sequence num-
ber adjustment will be performed in
this case.
Core-5688-3165: WARNING: re-
ceived keepalive without StoreID
set
A UMP Source received a keep
alive packet from a store without a
Store ID in the packet.
Core-5688-3166: WARNING:
received keepalive with out-of-
bounds StoreID u/u
A UMP Source received a keep
alive packet from a store that has
an out of range Store ID.
Core-5688-3167: WARNING: re-
ceived keepalive from non-active
store u
A UMP Source received a keep
alive packet from a non registered
store. This may happen if a source
did not successfully register with
the particular store in question.
Core-5688-3168: WARNING: re-
ceived keepalive from store u with
incorrect RegID u
A UMP Source received a keep
alive packet from a store that has
an invalid register ID.
Core-5688-3169: NOTICE: store
u:s:u reports it has not received T←-
IR. Possible misconfiguration?
The UMP store reported it has
not yet received a TIR (topic ad-
vertisement) for a topic which al-
ready has one or more registered
sources.UMP registration happens
via a different mechanism than
topic resolution, and is sometimes
a bit faster. Registration allows
the source to begin sending, but
the store does not actually begin
listening for messages until it re-
ceives a topic advertisement from
the source and sets up receivers for
the appropriate topics.In that brief
interval, the store will send these
notices to the source, just in case
you actually did forget to config-
ure the store to listen to the cor-
rect topic resolution channel.Once
the store receives a topic resolu-
tion advertisement and begins lis-
tening to the topic, the store will
perform a Late Join recovery if the
source has already started send-
ing, and should be able to catch
up unless you have changed your
source's transmission window to a
small value (by default, a source
keeps 24 MB of data for retrans-
mission).Our recommended delay
before sending should prevent you
from seeing this notice most of the
time, but you may occasionally see
it during store failover.
9.1 UM Core Messages 81
Core-5688-3170: WARNING: re-
ceived ACK with out-of-bounds
StoreID u/u
A UMP Source received an ac-
knowledgment packet with a store
that is not within the range of Store
IDs. This should not happen and is
not a serious condition.
Core-5688-3171: WARNING: re-
ceived ACK from non-active store
u
UMP received ACK from non-active
store, this is not a serious condition
unless it happens frequently and
messaging is affected.
Core-5688-3172: WARNING:
received stability sACK without
StoreID set
UMP received stability ACK or N←-
ACK without StoreID set, this is not
a serious condition unless it hap-
pens frequently and messaging is
affected.
Core-5688-3173: source "%s" re-
ceived CDELV without ACK ID set
Source received a delivery confir-
mation without the required identi-
fier for the receiver.
This may indicate corrupted pack-
ets, check the system for network
errors.
Core-5688-3178: WARNING: too
many UME stores specified for
topic resolution (max u)
Too many stores were specified
when creating a source.
Reduce the number of stores in the
ume_store configuration option.
Core-5688-3185: WARNING: too
many UME store groups specified
for topic resolution (max u)
Too many store groups were speci-
fied when creating a source.
Reduce the number of store groups
in the ume_store_group configura-
tion option.
Core-5688-3193: WARNING: too
many UME stores specified for
topic resolution (max u)
Too many stores were specified
when creating a source.
Reduce the number of stores in the
ume_store configuration option.
Core-5688-3203: INFO: OTR en-
abled but receiver is joining source
with late join disabled
A receiver with OTR enabled is
joining a source without late join.
The receiver will not be able to re-
cover any lost messages from this
source. To enable loss recovery,
enable late join at the source.
Core-5688-3228: WARNING←-
: socket reuseaddr and socket
exclusiveaddr set at the same time
The configuration options ∗←-
_tcp_reuseaddr and ∗_tcp_←-
exclusiveaddr (Windows only) can
not be used at the same time.
Check configuration option set-
tings.
Core-5688-3234: WARNING:
could not create TCP connection
socket: s
An error was returned from the OS
while trying to create a socket (T←-
CP). Refer to the OS error number
and message given after the U←-
MS message "could not create T←-
CP connection socket".
Core-5688-3236: WARNING:
could not set nonblock on TCP
connection socket: s
An error was returned from the OS
while trying to set the O_NONBL←-
OCK and O_NDELAY flags on the
socket. Refer to the OS error num-
ber and message given after the
UMS message "could not set non-
block on TCP connection socket".
Core-5688-3238: WARNING:
could not set nonblock on TCP
connection socket: s
An error was returned from the OS
while trying to set the O_NONBL←-
OCK and O_NDELAY flags on the
socket. Refer to the OS error num-
ber and message given after the
UMS message "could not set non-
block on TCP connection socket".
82 UM Log Messages
Core-5688-3240: WARNING:
could not bind, port d, on TCP
connection socket: s
An error was returned from the OS
while trying to bind the socket to
the given port. Refer to the OS er-
ror number and message given af-
ter the UMS message "could not
bind, port xxxxx, on TCP connec-
tion socket".
Core-5688-3244: WARNING:
could not set SO_KEEPALIVE on
TCP connection socket: s
SO_KEEPALIVE was requested on
the receiver end of TCP connec-
tion, but was not able to be set on
the socket. This could be because
the OS is not Windows or Linux, or
because there was an error in the
OS system call to set the socket op-
tions.
Core-5688-3245: WARNING←-
: could not connect on TCP
connection socket: s
An error was returned from the
OS while trying to connect to the
socket. Refer to the OS error num-
ber and message given after the
UMS message "could not connect
on TCP connection socket".
Core-5688-3247: WARNING←-
: could not connect on TCP
connection socket: s
An error was returned from the
OS while trying to connect to the
socket. Refer to the OS error num-
ber and message given after the
UMS message "could not connect
on TCP connection socket".
Core-5688-3263: WARNING:
could not set SO_REUSEADDR
on multicast receive socket: s
An error was returned from the OS
while trying to set the socket option
SO_REUSEADDR per the ∗_tcp←-
_reuseaddr configuration parame-
ter. Refer to the OS error number
and message given after the U←-
MS message "could not set SO_←-
REUSEADDR on multicast receive
socket".
Core-5688-3265: WARNING:
could not set SO_REUSEPORT on
multicast receive socket: s
An error was returned from the OS
while trying to set the socket option
SO_REUSEPORT per the ∗_tcp←-
_reuseaddr configuration parame-
ter. Refer to the OS error number
and message given after the U←-
MS message "could not set SO_←-
REUSEPORT on multicast receive
socket".
Core-5688-3267: WARNING:
could not bind, (port = d, multicast
group = s), on multicast receive
socket: s
An error occurred while trying to
bind to the requested ip and port.
The last part of this message con-
tains the OS error code and asso-
ciated text.
Consult your OS documentation
for resolutions based on the error
code.
Core-5688-3269: WARNING:
could not IP_ADD_MEMBERSHIP
on multicast receive socket: s
An error was returned from the OS
while trying to set the socket op-
tion IP_ADD_MEMBERSHIP. Refer
to the OS error number and mes-
sage given after the UMS message
"could not IP_ADD_MEMBERSH←-
IP on multicast receive socket".
9.1 UM Core Messages 83
Core-5688-3271: WARNING:
could not set nonblock on multicast
receive socket: s
An error was returned from the OS
while trying to set the O_NONBL←-
OCK and O_NDELAY flags on the
socket. Refer to the OS error num-
ber and message given after the
UMS message "could not set non-
block on multicast receive socket".
Core-5688-3272: WARNING:
could not set nonblock on multicast
receive socket: s
An error was returned from the OS
while trying to set the O_NONBL←-
OCK and O_NDELAY flags on the
socket. Refer to the OS error num-
ber and message given after the
UMS message "could not set non-
block on multicast receive socket".
Core-5688-3273: WARNING:
could not set multicast SO_RCV←-
BUF to requested value u
An error was returned from the
OS while trying to set the socket
option SO_RCVBUF per the ∗←-
_receiver_socket_buffer configura-
tion parameter. The requested
buffer size has not been set.
See the Configuration Guide for in-
structions about changing the OS
limits.
Core-5688-3274: INFO: mcast rcv
could only get SO_RCVBUF u (de-
sired u)
The OS has set the socket option
SO_RCVBUF but not to the value
specified per the ∗_receiver_←-
socket_buffer configuration param-
eter. The actual and desired values
are given in the message.
See the Configuration Guide for in-
structions about changing the OS
limits.
Core-5688-3284: WARNING←-
: could not getaddress on dbl
unicast rcv socket: s
An error occurred while creating a
DBL socket, which may prevent the
receiver from proceeding.
Contact Informatica support.
Core-5688-3289: WARNING:
could not set unicast SO_RCVBUF
to requested value u
An error was returned from the
OS while trying to set the socket
option SO_RCVBUF per the ∗←-
_receiver_socket_buffer configura-
tion parameter. The requested
buffer size has not been set.
See the Configuration Guide for in-
structions about changing the OS
limits.
Core-5688-3290: INFO: unicast rcv
could only get SO_RCVBUF u (de-
sired u)
Increase the maximum send buffer
size allowed by your OS. See the
Configuration Guide for instructions
about changing the OS limits.
Core-5688-3292: WARNING:
could not find open unicast port
in range [d-d] on dbl unicast bidir
socket: s
Could not bind a port in the speci-
fied range. The range may need to
be expanded or moved to a range
where less ports are in use.
Core-5688-3294: WARNING←-
: could not bind, port d, on dbl
unicast bidir socket: s
An error occurred while creating a
DBL socket, which may prevent the
receiver from proceeding.
Contact Informatica support.
Core-5688-3296: WARNING←-
: could not getaddress on dbl
unicast bidir socket: s
An error occurred while creating a
DBL socket, which may prevent the
receiver from proceeding.
Contact Informatica support.
Core-5688-3298: WARNING←-
: could not create unicast bidir
socket: s
An error was returned from the OS
while trying to create a socket (U←-
DP). Refer to the OS error number
and message given after the UMS
message "could not create unicast
bidir socket".
84 UM Log Messages
Core-5688-3300: WARNING:
could not find open unicast port
in range [d-d] on unicast bidir
socket: s
There are no ports available in
the given range. Use ∗_port_←-
low and/or ∗_port_high configura-
tion parameters to specify a differ-
ent range of ports to use.
Core-5688-3302: WARNING:
could not bind, port d, on unicast
bidir socket: s
An error was returned from the OS
while trying to bind the socket to the
given port. Refer to the OS error
number and message given after
the UMS message "could not bind,
port xxxxx, on unicast bidir socket".
Core-5688-3304: WARNING:
could not getsockname on unicast
bidir socket: s
An error was returned from the OS
while trying to get the socket name.
Refer to the OS error number and
message given after the UMS mes-
sage "could not getsockname on
unicast bidir socket".
Core-5688-3306: WARNING:
could not set nonblock on unicast
bidir socket: s
An error was returned from the OS
while trying to set the O_NONBL←-
OCK and O_NDELAY flags on the
socket. Refer to the OS error num-
ber and message given after the
UMS message "could not set non-
block on unicast bidir socket".
Core-5688-3307: WARNING:
could not set nonblock on unicast
bidir socket: s
An error was returned from the OS
while trying to set the O_NONBL←-
OCK and O_NDELAY flags on the
socket. Refer to the OS error num-
ber and message given after the
UMS message "could not set non-
block on unicast bidir socket".
Core-5688-3308: WARNING:
could not set bidir SO_RCVBUF to
requested value u
An error was returned from the
OS while trying to set the socket
option SO_RCVBUF per the ∗←-
_receiver_socket_buffer configura-
tion parameter. The requested
buffer size has not been set.
See the Configuration Guide for in-
structions about changing the OS
limits.
Core-5688-3309: INFO: ucast bidir
could only get SO_RCVBUF u (de-
sired u)
The OS has set the socket option
SO_RCVBUF but not to the value
specified per the ∗_receiver_←-
socket_buffer configuration param-
eter. The actual and desired values
are given in the message.
See the Configuration Guide for in-
structions about changing the OS
limits.
Core-5688-3330: lbm_socket_←-
send: msg dropped (EWOULDB←-
LOCK): adjust rate limit or buffers
The combination of the ∗_data_←-
rate_limit and ∗_rate_interval con-
figuration parameters are used to
determine the amount of data that
will be sent at each interval. If that
amount exceeds the configured ∗←-
_socket_buffer setting, each inter-
val may experience an EWOUL←-
DBLOCK status from the OS due
to the fact that the data does not fit
into the OS buffer allocated.
If this message occurs often, re-
view configuration option settings.
9.1 UM Core Messages 85
Core-5688-3331: lbm_socket_←-
send: msg dropped (EWOULDB←-
LOCK): adjust rate limit or buffers
The combination of the ∗_data_←-
rate_limit and ∗_rate_interval con-
figuration parameters are used to
determine the amount of data that
will be sent at each interval. If that
amount exceeds the configured ∗←-
_socket_buffer setting, each inter-
val may experience an EWOUL←-
DBLOCK status from the OS due
to the fact that the data does not fit
into the OS buffer allocated.
If this message occurs often, re-
view configuration option settings.
Core-5688-3335: lbm_socket_←-
sendb: msg dropped (EWOULD←-
BLOCK): adjust rate limit or buffers
The combination of the ∗_data_←-
rate_limit and ∗_rate_interval con-
figuration parameters are used to
determine the amount of data that
will be sent at each interval. If that
amount exceeds the configured ∗←-
_socket_buffer setting, each inter-
val may experience an EWOUL←-
DBLOCK status from the OS due
to the fact that the data does not fit
into the OS buffer allocated.
If this message occurs often, re-
view configuration option settings.
Core-5688-3336: lbm_socket_←-
sendb: msg dropped (EWOULD←-
BLOCK): adjust rate limit or buffers
The combination of the ∗_data_←-
rate_limit and ∗_rate_interval con-
figuration parameters are used to
determine the amount of data that
will be sent at each interval. If that
amount exceeds the configured ∗←-
_socket_buffer setting, each inter-
val may experience an EWOUL←-
DBLOCK status from the OS due
to the fact that the data does not fit
into the OS buffer allocated.
If this message occurs often, re-
view configuration option settings.
Core-5688-3340: lbm_socket_←-
sendtob: msg dropped (EWO←-
ULDBLOCK): adjust rate limit or
buffers
The combination of the ∗_data_←-
rate_limit and ∗_rate_interval con-
figuration parameters are used to
determine the amount of data that
will be sent at each interval. If that
amount exceeds the configured ∗←-
_socket_buffer setting, each inter-
val may experience an EWOUL←-
DBLOCK status from the OS due
to the fact that the data does not fit
into the OS buffer allocated.
If this message occurs often, re-
view configuration option settings.
Core-5688-3341: lbm_socket_←-
sendtob: msg dropped (EWO←-
ULDBLOCK): adjust rate limit or
buffers
The combination of the ∗_data_←-
rate_limit and ∗_rate_interval con-
figuration parameters are used to
determine the amount of data that
will be sent at each interval. If that
amount exceeds the configured ∗←-
_socket_buffer setting, each inter-
val may experience an EWOUL←-
DBLOCK status from the OS due
to the fact that the data does not fit
into the OS buffer allocated.
If this message occurs often, re-
view configuration option settings.
86 UM Log Messages
Core-5688-3345: lbm_socket_←-
sendbv: msg dropped (EWOULD←-
BLOCK): adjust rate limit or buffers
The combination of the ∗_data_←-
rate_limit and ∗_rate_interval con-
figuration parameters are used to
determine the amount of data that
will be sent at each interval. If that
amount exceeds the configured ∗←-
_socket_buffer setting, each inter-
val may experience an EWOUL←-
DBLOCK status from the OS due
to the fact that the data does not fit
into the OS buffer allocated.
If this message occurs often, re-
view configuration option settings.
Core-5688-3346: lbm_socket_←-
sendbv: msg dropped (EWOULD←-
BLOCK): adjust rate limit or buffers
The combination of the ∗_data_←-
rate_limit and ∗_rate_interval con-
figuration parameters are used to
determine the amount of data that
will be sent at each interval. If that
amount exceeds the configured ∗←-
_socket_buffer setting, each inter-
val may experience an EWOUL←-
DBLOCK status from the OS due
to the fact that the data does not fit
into the OS buffer allocated.
If this message occurs often, re-
view configuration option settings.
Core-5688-3351: lbm_socket_←-
sendtobv: msg dropped (EWO←-
ULDBLOCK): adjust rate limit or
buffers
The combination of the ∗_data_←-
rate_limit and ∗_rate_interval con-
figuration parameters are used to
determine the amount of data that
will be sent at each interval. If that
amount exceeds the configured ∗←-
_socket_buffer setting, each inter-
val may experience an EWOUL←-
DBLOCK status from the OS due
to the fact that the data does not fit
into the OS buffer allocated.
If this message occurs often, re-
view configuration option settings.
Core-5688-3352: lbm_socket_←-
sendtobv: msg dropped (EWO←-
ULDBLOCK): adjust rate limit or
buffers
The combination of the ∗_data_←-
rate_limit and ∗_rate_interval con-
figuration parameters are used to
determine the amount of data that
will be sent at each interval. If that
amount exceeds the configured ∗←-
_socket_buffer setting, each inter-
val may experience an EWOUL←-
DBLOCK status from the OS due
to the fact that the data does not fit
into the OS buffer allocated.
If this message occurs often, re-
view configuration option settings.
Core-5688-3365: NOTICE: winc-
port comp routine, invalid op
I/O operation completed on deleted
connection.
Ignore unless this occurs many
times per hour.
Core-5688-3368: NOTICE: WSA←-
SendTo error [send_pending d]: s
I/O operation could not be started
due to socket error.
Ignore unless this occurs many
times per hour.
Core-5688-3370: WARNING:
lbm_sock_delete acc_conn has
unknown optype d
An unexpected I/O operation was
received while deleting a connec-
tion. Only occurs when using Win-
dows completion ports.
Contact Informatica support if this
message occurs frequently.
Core-5688-3375: unicast resolver
s:u went inactive
The process received no com-
munications from the LBMRD at
the specified ip:port within the
resolver_unicast_activity_timeout
and is marked as inactive.
If the LBMRD is running properly,
increasing the resolver_unicast_←-
activity_timeout to account for pos-
sible network congestion or an
overloaded LBMRD can resolve
this issue.
9.1 UM Core Messages 87
Core-5688-3377: LBMR Version
0xx incorrect (s:d len d). [s]. Drop-
ping.
An LBMR packet was droppped be-
cause its version was invalid.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-5688-3378: LBMR packet
malformed. Dropping. Origin: s←-
:d
An LBMR packet was droppped be-
cause its length did not match the
length of the data received.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-5688-3379: LBMR optlen
malformed. Dropping packet.
Origin: s:d
An LBMR packet was droppped be-
cause its length did not match the
length of the data received.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-5688-3380: LBMR optlen
total_len malformed. Dropping
packet. Origin: s:d
An LBMR packet was droppped be-
cause its length did not match the
length of the data received.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-5688-3383: LBMR option in-
valid type [u]. Dropping packet.
Origin: s:d
An LBMR packet was droppped be-
cause of an invalid option type.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-5688-3384: LBMR Type 0xx
incorrect (s:d len d). [s]. Dropping.
An LBMR packet was droppped
due to an invalid type.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-5688-3385: LBMR Topic
Query Record malformed. Drop-
ping remainder. Origin: s:d
An LBMR packet was droppped be-
cause it could not be parsed.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-5688-3386: LBMR Topic Info
Record malformed. Dropping re-
mainder. Origin: s:d
An LBMR packet was droppped be-
cause it could not be parsed.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-5688-3387: LBMR Extended
Type 0xx incorrect (s:d len d). [s].
Dropping.
LBM resolver has encountered
an unknown extended type and
dropped the packet. Each type is
reported only once per resolver.
Can be caused by mixed versions
sharing a topic resolution address
or malformed/forged packets.
Core-5688-3388: LBMR Topic Info
Record Option not Length. Drop-
ping remainder.
UMS encountered a mismatch in
the length of a received message
and its headers, determining the
rest of the message to be invalid.
The remainder of the message is
dropped.
Contact Informatica support if this
message occurs frequently.
Core-5688-3389: LBMR Topic Info
Record Length Option not correct
size. Dropping remainder.
UMS encountered a mismatch in
the length of a received message
and its headers, determining the
rest of the message to be invalid.
The remainder of the message is
dropped.
Contact Informatica support if this
message occurs frequently.
Core-5688-3390: LBMR Topic Info
Record Total Length not large
enough. Dropping remainder.
UMS encountered a mismatch in
the length of a received message
and its headers, determining the
rest of the message to be invalid.
The remainder of the message is
dropped.
Contact Informatica support if this
message occurs frequently.
Core-5688-3391: LBMR Topic Info
Record UME Option not correct
size. Dropping remainder.
UMS encountered a mismatch in
the length of a received message
and its headers, determining the
rest of the message to be invalid.
The remainder of the message is
dropped.
Contact Informatica support if this
message occurs frequently.
88 UM Log Messages
Core-5688-3392: LBMR Topic Info
Record Late Join Option not correct
size. Dropping remainder.
UMS encountered a mismatch in
the length of a received message
and its headers, determining the
rest of the message to be invalid.
The remainder of the message is
dropped.
Contact Informatica support if this
message occurs frequently.
Core-5688-3393: LBMR Topic Info
Record UME Store Option not cor-
rect size. Dropping remainder.
UMS encountered a mismatch in
the length of a received message
and its headers, determining the
rest of the message to be invalid.
The remainder of the message is
dropped.
Contact Informatica support if this
message occurs frequently.
Core-5688-3394: LBMR Topic Info
Record UME Store Group Option
not correct size. Dropping remain-
der.
UMS encountered a mismatch in
the length of a received message
and its headers, determining the
rest of the message to be invalid.
The remainder of the message is
dropped.
Contact Informatica support if this
message occurs frequently.
Core-5688-3397: LBMR Topic Info
Record Option not understood and
does not have ignore. Dropping re-
mainder.
UMS received a message with a
header that was not recognized.
This header and the rest of the
message will be ignored. This is
potentially due to a newer version
of software sending messages and
is not harmful.
Contact Informatica support if this
message occurs frequently or if us-
ing only one version of Ultra Mes-
saging.
Core-5688-3398: LBMR Topic Info
Record Option length incongruent.
Dropping remainder.
UMS encountered a mismatch in
the length of a received message
and its headers, determining the
rest of the message to be invalid.
The remainder of the message is
dropped.
Contact Informatica support if this
message occurs frequently.
Core-5688-3400: LBMR Topic
Mgmt Record Length not correct
size. Dropping remainder.
UMS encountered a mismatch in
the length of a received message
and its headers, determining the
rest of the message to be invalid.
The remainder of the message is
dropped.
Contact Informatica support if this
message occurs frequently.
Core-5688-3401: WARNING:
could not undefine topic from topic
map when deleting
Warning: UMS could not remove a
topic from topic map.
Contact Informatica support if this
message occurs frequently.
Core-5688-3402: LBMR WC TQR
pcre_compile [s] malformed [d][s].
Dropping.
UMS detected a malformed PC←-
RE pattern for a wild card receiver,
it will drop the Topic Query Re-
sponse.
Contact Informatica support if this
message occurs frequently or if
topic resolution appears to be fail-
ing.
Core-5688-3403: LBMR WC TQR
regcomp [s] malformed [s]. Drop-
ping.
In topic resolution process, UMS
detected a malformed registration
complete signal for a wild card re-
ceiver, it will drop the Topic Query
Response.
Contact Informatica support if this
message occurs frequently or if
topic resolution appears to be fail-
ing.
Core-5688-3404: LBMR WC TQR
Type 0xx [s] not understood. Drop-
ping.
In topic resolution process, UMS
detected a malformed type for a
wild card receiver, it will drop the
Topic Query Response.
Contact Informatica support if this
message occurs frequently or if
topic resolution appears to be fail-
ing.
9.1 UM Core Messages 89
Core-5688-3405: LBMR WC TQR
pcre_exec [s][s][d] error d
UMS detected a malformed PCRE
pattern for a wild card receiver dur-
ing topic resolution. It will drop the
Topic Query Response. This is not
a serious condition unless it hap-
pens frequently and the resolution
process is affected.
Core-5688-3415: message re-
ceiver function returned -1
An error occurred processing a
message received by a receiver.
The receiver's delivery controller
was unable to pass the message to
the application. The message was
discarded.
Contact Informatica support if this
message occurs frequently.
Core-5688-3426: WARNING: Join-
ing session [s] which exists and
uses a different transport_lbtrm←-
_nak_backoff_interval [d] than re-
quested [d].
After a receiver has created a
transport session, a subsequent re-
ceiver joining the same transport
session cannot configure a differ-
ent transport_lbtrm_nak_backoff←-
_interval setting.
Core-5688-3427: WARNING: Join-
ing session [s] which exists and
uses a different transport_lbtrm_←-
nak_suppress_interval [d] than re-
quested [d].
After a receiver has created a
transport session, a subsequent
receiver joining the same trans-
port session cannot configure a
different transport_lbtrm_nak_←-
suppress_interval setting.
Core-5688-3428: WARNING: Join-
ing session [s] which exists and
uses a different transport_lbtrm←-
_nak_generation_interval [d] than
requested [d].
After a receiver has created a
transport session, a subsequent
receiver joining the same trans-
port session cannot configure a
different transport_lbtrm_nak_←-
generation_interval setting.
Core-5688-3429: WARNING: Join-
ing session [s] which exists and
uses a different transport_lbtrm←-
_preactivity_timeout [d] than re-
quested [d].
After a receiver has created a
transport session, a subsequent
receiver joining the same trans-
port session cannot configure a dif-
ferent transport_lbtrm_preactivity←-
_timeout setting.
Core-5688-3430: WARNING: Join-
ing session [s] which exists and
uses a different transport_lbtrm_←-
activity_timeout [d] than requested
[d].
After a receiver has created a
transport session, a subsequent
receiver joining the same trans-
port session cannot configure a
different transport_lbtrm_activity←-
_timeout setting.
Core-5688-3431: WARNING: Join-
ing session [s] which exists and
uses a different transport_lbtrm_←-
send_naks [d] than requested [d].
After a receiver has created a
transport session, a subsequent
receiver joining the same trans-
port session cannot configure a dif-
ferent transport_lbtrm_send_naks
setting.
Core-5688-3432: WARNING: Join-
ing session [s] which exists and
uses a different transport_lbtru←-
_nak_backoff_interval [d] than re-
quested [d].
After a receiver has created a
transport session, a subsequent re-
ceiver joining the same transport
session cannot configure a differ-
ent transport_lbtru_nak_backoff_←-
interval setting.
90 UM Log Messages
Core-5688-3433: WARNING: Join-
ing session [s] which exists and
uses a different transport_lbtru_←-
nak_suppress_interval [d] than re-
quested [d].
After a receiver has created a
transport session, a subsequent
receiver joining the same trans-
port session cannot configure a
different transport_lbtru_nak_←-
suppress_interval setting.
Core-5688-3434: WARNING: Join-
ing session [s] which exists and
uses a different transport_lbtru←-
_nak_generation_interval [d] than
requested [d].
After a receiver has created a
transport session, a subsequent
receiver joining the same trans-
port session cannot configure a
different transport_lbtru_nak_←-
generation_interval setting.
Core-5688-3435: WARNING: Join-
ing session [s] which exists and
uses a different transport_lbtru_←-
activity_timeout [d] than requested
[d].
After a receiver has created a
transport session, a subsequent
receiver joining the same trans-
port session cannot configure a
different transport_lbtru_activity_←-
timeout setting.
Core-5688-3439: WARNING: Join-
ing session [s] which exists and
uses a different transport_lbtipc_←-
activity_timeout [d] than requested
[d].
After a receiver has created a
transport session, a subsequent
receiver joining the same trans-
port session cannot configure a
different transport_lbtipc_activity←-
_timeout setting.
Core-5688-3541: PCRE exec
[s][s][d] error d
An error occurred while trying to
match the pattern listed in the first
bracketed expression. The topic
string attempting to be matched
is supplied as the second brack-
eted expression, and its length is
supplied as the third bracketed ex-
pression. The error that occurred
was internal to PCRE, and the er-
ror code is listed in the PCRE
documentation for return values of
pcre_exec.
Core-5688-3546: LBMR WC TQR
pcre_compile [s] malformed [d][s].
Dropping.
UMS detected a malformed PC←-
RE pattern for a wild card receiver,
it will drop the Topic Query Re-
sponse.
Contact Informatica support if this
message occurs frequently or if
topic resolution appears to be fail-
ing.
Core-5688-3547: LBMR WC TQR
regcomp [s] malformed [s]. Drop-
ping.
In topic resolution process, UMS
detected a malformed registration
complete signal for a wild card re-
ceiver, it will drop the Topic Query
Response.
Contact Informatica support if this
message occurs frequently or if
topic resolution appears to be fail-
ing.
Core-5688-3548: LBMR WC TQR
Type 0xx [s] not understood. Drop-
ping.
In topic resolution process, UMS
detected a malformed type for a
wild card receiver, it will drop the
Topic Query Response.
Contact Informatica support if this
message occurs frequently or if
topic resolution appears to be fail-
ing.
9.1 UM Core Messages 91
Core-5688-3549: LBMR WC
Cache pcre_exec [s][s][d] error d
An error occurred while trying to
match the pattern listed in the first
bracketed expression. The topic
string attempting to be matched
is supplied as the second brack-
eted expression, and its length is
supplied as the third bracketed ex-
pression. The error that occurred
was internal to PCRE, and the er-
ror code is listed in the PCRE
documentation for return values of
pcre_exec.
Core-5688-3555: wildcard mes-
sage receiver function returned -1
The callback configured for wild-
card receiver messages returned -
1 while processing an immediate
message.
Core-5688-3691: Sending request
with request port binding disabled.
An lbm request is being sent, but
the request port used to receive
responses is disabled via the
request_tcp_bind_request_port
(context) configuration option.
See the documentation for this
configuration option for more
information.
Core-5688-3698: Response for re-
quest query index u received. No
request known.
A response was received that does
not correspond to an existing re-
quest. This usually indicates that
the responder took too long to re-
spond, and the requestor had al-
ready deleted the request object
when the response was received.
Core-5688-3701: Response for re-
quest query index u received. No
request known.
A response was received that does
not correspond to an existing re-
quest. This usually indicates that
the responder took too long to re-
spond, and the requestor had al-
ready deleted the request object
when the response was received.
Core-5688-3702: WARNING: dele-
tion timeout from s:u while sending
response or UIM
A response or a unicast immediate
message was still being sent when
the corresponding TCP connection
closed.
Contact Informatica support.
Core-5688-3723: Sending unicast
immediate request with request
port binding disabled.
An lbm request is being sent via
unicast immediate messaging, but
the request port used to receive
responses is disabled via the
request_tcp_bind_request_port
(context) configuration option.
See the Ultra Messaging Configu-
ration Guide.
Core-5688-3762: unknown fd_to←-
_be action d
Internal error while handling
socket; probable memory corrup-
tion.
Contact Informatica support.
92 UM Log Messages
Core-5688-3773: epoll_ctl: Tried to
register a bad file descriptor
The fd_management_type is set to
epoll and either the user tried to
register a non-socket file descrip-
tor or a socket that was registered
unexpectedly became invalid be-
tween creating the file descriptor
and registering it. Linux's epoll cur-
rently only supports socket file de-
scriptors, and not normal files or
other file descriptor types.
Contact Informatica support if this
warning occurs frequently.
Core-5688-3774: epoll_ctl: Tried to
perform an operation on a socket
that is already closed
The fd_management_type is set to
epoll and file descriptor registration
was attempted for a socket that was
already closed. This can some-
times happen if a socket is closed
immediately after it is created, but
before it is registered.
Contact Informatica support if this
warning occurs frequently.
Core-5688-3777: s:d: sock=p,
sock->sock=p, handle=p, io_←-
pending=d, op_recv=p, op_acc_←-
conn=p
Pre-assert data: a message which
contains selected internal state in-
formation useful for diagnosing the
cause of certain failed assertions.
Does not occur during normal op-
eration.
Core-5688-3781: s:d: sock=p,
sock->sock=p, handle=p, io_←-
pending=d, op_recv=p, op_acc_←-
conn=p
Pre-assert data: a message which
contains selected internal state in-
formation useful for diagnosing the
cause of certain failed assertions.
Does not occur during normal op-
eration.
Core-5688-3782: s:d: sock=p,
sock->sock=p, handle=p, io_←-
pending=d, op_recv=p, op_acc_←-
conn=p
Pre-assert data: a message which
contains selected internal state in-
formation useful for diagnosing the
cause of certain failed assertions.
Does not occur during normal op-
eration.
Core-5688-3786: s:d: sock=p,
sock->sock=p, handle=p, io_←-
pending=d, op_recv=p, op_acc_←-
conn=p
Pre-assert data: a message which
contains selected internal state in-
formation useful for diagnosing the
cause of certain failed assertions.
Does not occur during normal op-
eration.
Core-5688-3793: s:d: sock=p,
sock->sock=p, handle=p, io_←-
pending=d, op_recv=p, op_acc_←-
conn=p
Pre-assert data: a message which
contains selected internal state in-
formation useful for diagnosing the
cause of certain failed assertions.
Does not occur during normal op-
eration.
Core-5688-3794: s:d: sock=p,
sock->sock=p, handle=p, io_←-
pending=d, op_recv=p, op_acc_←-
conn=p
Pre-assert data: a message which
contains selected internal state in-
formation useful for diagnosing the
cause of certain failed assertions.
Does not occur during normal op-
eration.
9.1 UM Core Messages 93
Core-5688-3804: kevent fatal
error: (d) s
When using the kqueue file de-
scriptor management type on Mac
OS X, an unexpected error was re-
turned from the kevent system call.
This could be caused by a variety
of reasons, including being out of
memory, or trying to register an in-
valid file descriptor, or accessing
memory incorrectly.
Core-5688-3805: mapentry-
>writecb was NULL
A registered file descriptor had a
write or connect event, but the reg-
istered callback was NULL. This
should never happen, and indi-
cates possible application memory
corruption.
Core-5688-3806: Dropping can-
celled write or connect event on
handle d
A write or connect event occurred
on the indicated file descriptor
(handle), but the user's registered
write or connect event callback was
cancelled immediately before the
event happened.
Core-5688-3807: mapentry-
>readcb was NULL
A registered file descriptor had a
read, accept, or close event, but
the registered callback was NULL.
This can happen if the file descrip-
tor had a write or connect event
at about the same time, and the
read, accept, or close event call-
back was cancelled for that file de-
scriptor within its write or connect
event callback. This warning is
usually harmless, but may indicate
improper application design.
Core-5688-3808: Dropping can-
celled read, accept, or close event
on handle d
A read, accept, or close event oc-
curred on the indicated file de-
scriptor (handle), but the user's
registered read, accept, or close
event callback was cancelled im-
mediately before the event hap-
pened.
Core-5688-3809: mapentry-
>exceptcb was NULL
A registered file descriptor had an
exception event, but the registered
exception callback was NULL. This
can happen if the file descriptor had
a write, connect, read, accept, or
close event at about the same time,
and the file descriptor's exception
callback was cancelled within any
of its other callbacks. This warning
is usually harmless, but may indi-
cate improper application design.
Core-5688-3810: Dropping can-
celled except event on handle d
An exception event occurred on the
indicated file descriptor (handle),
but the user's registered exception
event callback was cancelled im-
mediately before the event hap-
pened.
94 UM Log Messages
Core-5688-3811: mapentry-
>writecb was NULL
A registered file descriptor had a
write or connect event, but the reg-
istered callback was NULL. This
should never happen, and indi-
cates possible application memory
corruption.
Core-5688-3812: Dropping can-
celled write or connect event on
handle d
A write or connect event occurred
on the indicated file descriptor
(handle), but the user's registered
write or connect event callback was
cancelled immediately before the
event happened.
Core-5688-3813: mapentry-
>readcb was NULL
A registered file descriptor had a
read, accept, or close event, but
the registered callback was NULL.
This can happen if the file descrip-
tor had a write or connect event
at about the same time, and the
read, accept, or close event call-
back was cancelled for that file de-
scriptor within its write or connect
event callback. This warning is
usually harmless, but may indicate
improper application design.
Core-5688-3815: mapentry-
>exceptcb was NULL
A registered file descriptor had an
exception event, but the registered
exception callback was NULL. This
can happen if the file descriptor had
a write, connect, read, accept, or
close event at about the same time,
and the file descriptor's exception
callback was cancelled within any
of its other callbacks. This warning
is usually harmless, but may indi-
cate improper application design.
Core-5688-3816: Dropping can-
celled except event on handle d
An exception event occurred on the
indicated file descriptor (handle),
but the user's registered exception
event callback was cancelled im-
mediately before the event hap-
pened.
Core-5688-3817: mapentry-
>writecb was NULL
A registered file descriptor had a
write or connect event, but the reg-
istered callback was NULL. This
should never happen, and indi-
cates possible application memory
corruption.
Core-5688-3818: Dropping can-
celled write or connect event on
handle d
A write or connect event occurred
on the indicated file descriptor
(handle), but the user's registered
write or connect event callback was
cancelled immediately before the
event happened.
9.1 UM Core Messages 95
Core-5688-3819: mapentry-
>readcb was NULL
A registered file descriptor had a
read, accept, or close event, but
the registered callback was NULL.
This can happen if the file descrip-
tor had a write or connect event
at about the same time, and the
read, accept, or close event call-
back was cancelled for that file de-
scriptor within its write or connect
event callback. This warning is
usually harmless, but may indicate
improper application design.
Core-5688-3820: Dropping can-
celled read, accept, or close event
on handle d
A read, accept, or close event oc-
curred on the indicated file de-
scriptor (handle), but the user's
registered read, accept, or close
event callback was cancelled im-
mediately before the event hap-
pened.
Core-5688-3821: mapentry-
>exceptcb was NULL
A registered file descriptor had an
exception event, but the registered
exception callback was NULL. This
can happen if the file descriptor had
a write, connect, read, accept, or
close event at about the same time,
and the file descriptor's exception
callback was cancelled within any
of its other callbacks. This warning
is usually harmless, but may indi-
cate improper application design.
Core-5688-3822: Dropping can-
celled except event on handle d
An exception event occurred on the
indicated file descriptor (handle),
but the user's registered exception
event callback was cancelled im-
mediately before the event hap-
pened.
Core-5688-3823: mapentry-
>writecb was NULL
A registered file descriptor had a
write or connect event, but the reg-
istered callback was NULL. This
should never happen, and indi-
cates possible application memory
corruption.
Core-5688-3824: Dropping can-
celled write or connect event on
handle d
A write or connect event occurred
on the indicated file descriptor
(handle), but the user's registered
write or connect event callback was
cancelled immediately before the
event happened.
96 UM Log Messages
Core-5688-3825: mapentry-
>readcb was NULL
A registered file descriptor had a
read, accept, or close event, but
the registered callback was NULL.
This can happen if the file descrip-
tor had a write or connect event
at about the same time, and the
read, accept, or close event call-
back was cancelled for that file de-
scriptor within its write or connect
event callback. This warning is
usually harmless, but may indicate
improper application design.
Core-5688-3826: Dropping can-
celled read, accept, or close event
on handle d
A read, accept, or close event oc-
curred on the indicated file de-
scriptor (handle), but the user's
registered read, accept, or close
event callback was cancelled im-
mediately before the event hap-
pened.
Core-5688-3827: mapentry-
>exceptcb was NULL
A registered file descriptor had an
exception event, but the registered
exception callback was NULL. This
can happen if the file descriptor had
a write, connect, read, accept, or
close event at about the same time,
and the file descriptor's exception
callback was cancelled within any
of its other callbacks. This warning
is usually harmless, but may indi-
cate improper application design.
Core-5688-3828: Dropping can-
celled except event on handle d
An exception event occurred on the
indicated file descriptor (handle),
but the user's registered exception
event callback was cancelled im-
mediately before the event hap-
pened.
Core-5688-3831: mapentry-
>writecb was NULL
A registered file descriptor had a
write or connect event, but the reg-
istered callback was NULL. This
should never happen, and indi-
cates possible application memory
corruption.
Core-5688-3832: Dropping can-
celled write or connect event on
handle d
A write or connect event occurred
on the indicated file descriptor
(handle), but the user's registered
write or connect event callback was
cancelled immediately before the
event happened.
9.1 UM Core Messages 97
Core-5688-3833: mapentry-
>readcb was NULL
A registered file descriptor had a
read, accept, or close event, but
the registered callback was NULL.
This can happen if the file descrip-
tor had a write or connect event
at about the same time, and the
read, accept, or close event call-
back was cancelled for that file de-
scriptor within its write or connect
event callback. This warning is
usually harmless, but may indicate
improper application design.
Core-5688-3835: mapentry-
>exceptcb was NULL
A registered file descriptor had an
exception event, but the registered
exception callback was NULL. This
can happen if the file descriptor had
a write, connect, read, accept, or
close event at about the same time,
and the file descriptor's exception
callback was cancelled within any
of its other callbacks. This warning
is usually harmless, but may indi-
cate improper application design.
Core-5688-3836: Dropping can-
celled except event on handle d
An exception event occurred on the
indicated file descriptor (handle),
but the user's registered exception
event callback was cancelled im-
mediately before the event hap-
pened.
Core-5688-3838: NOTICE: winc-
port p results [d] (d,d,p,p) op x
Internal error handling descriptors;
probable timing race condition.
Contact Informatica support.
Core-5688-3847: NOTICE: winc-
port p line d WSA err d, s (peer s)
(op x)
A Windows Completion port opera-
tion ended with a failure.
Examine the reported WSA Error
code and take the appropriate ac-
tion.
Core-5688-3849: lbm_fd_handle←-
_events line d: wincport recv err (s)
from peer (s)
The Windows completion port call
to recv returned an error.
Look up the WSA error and take
appropriate action.
Core-5688-3864: NOTICE: winc-
port p results [d] (d,d,p,p) op x
Internal error handling descriptors;
probable timing race condition.
Contact Informatica support.
Core-5688-3883: mapentry-
>exceptcb was NULL
A registered file descriptor had an
exception event, but the registered
exception callback was NULL. This
can happen if the file descriptor had
a write, connect, read, accept, or
close event at about the same time,
and the file descriptor's exception
callback was cancelled within any
of its other callbacks. This warning
is usually harmless, but may indi-
cate improper application design.
Core-5688-3884: Dropping can-
celled except event on handle d
An exception event occurred on the
indicated file descriptor (handle),
but the user's registered exception
event callback was cancelled im-
mediately before the event hap-
pened.
98 UM Log Messages
Core-5688-3885: mapentry-
>writecb was NULL
A registered file descriptor had a
write or connect event, but the reg-
istered callback was NULL. This
should never happen, and indi-
cates possible application memory
corruption.
Core-5688-3886: Dropping can-
celled write or connect event on
handle d
A write or connect event occurred
on the indicated file descriptor
(handle), but the user's registered
write or connect event callback was
cancelled immediately before the
event happened.
Core-5688-3887: mapentry-
>readcb was NULL
A registered file descriptor had a
read, accept, or close event, but
the registered callback was NULL.
This can happen if the file descrip-
tor had a write or connect event
at about the same time, and the
read, accept, or close event call-
back was cancelled for that file de-
scriptor within its write or connect
event callback. This warning is
usually harmless, but may indicate
improper application design.
Core-5688-3888: Dropping can-
celled read, accept, or close event
on handle d
A read, accept, or close event oc-
curred on the indicated file de-
scriptor (handle), but the user's
registered read, accept, or close
event callback was cancelled im-
mediately before the event hap-
pened.
Core-5688-3889: kevent returned
event with unknown or unsup-
ported filter type
kevent returned a file descriptor
with a filter type that was not E←-
VFILT_READ or EVFILT_WRITE
(such as EVFILT_SIGNAL, EVF←-
ILT_PROC, etc.). UMS does not
register any file descriptors for any
filters other than EVFILT_READ or
EVFILT_WRITE, so this is very un-
usual and might indicate memory
corruption.
Core-5688-3890: handle events re-
turned error u [s]
Socket returned error while waiting
for context deletion.
Ignore, unless this occurs many
times per hour.
Core-5688-3896: wildcard mes-
sage receiver function returned -1
The callback configured for wild-
card receiver messages returned -
1 while processing an immediate
message.
Core-5688-3897: wildcard mes-
sage receiver function returned -1
The callback configured for wild-
card receiver messages returned -
1 while processing an immediate
message.
Core-5688-390: event dispatch -
unknown event type (d)
The event dispatch loop encoun-
tered an unexpected event type.
This is probably due to an unex-
pected network event occurring.
Check that the network is stable.
Contact Informatica support if this
message occurs frequently.
9.1 UM Core Messages 99
Core-5688-3919: Sending multi-
cast immediate request with re-
quest port binding disabled.
An lbm request is being sent via
multicast immediate messaging,
but the request port used to re-
ceive responses is disabled via the
request_tcp_bind_request_port
(context) configuration option.
See the documentation for this
configuration option for more
information.
Core-5688-3927: New unfragged
message in TCP buffer before first
message is complete.
With transport_tcp_multiple_←-
receiver_behavior set to bounded←-
_latency or source_paced and old
messages are being removed to
make room for new messages,
the first (oldest) message is
fragmented but is incomplete.
Processing will continue anyway.
Core-5688-3928: New message in
TCP buffer before first message is
complete.
With transport_tcp_multiple_←-
receiver_behavior set to bounded←-
_latency or source_paced and old
messages are being removed to
make room for new messages,
the first (oldest) message is
fragmented but is incomplete.
Processing will continue anyway.
Core-5688-3929: No more mes-
sages in TCP buffer before old
message is complete.
With transport_tcp_multiple_←-
receiver_behavior set to bounded←-
_latency or source_paced and old
messages are being removed to
make room for new messages,
the message being removed is
fragmented and only a portion of
it could be found and removed.
Processing will continue anyway.
Core-5688-3930: New unfragged
message in TCP buffer before old
fragged message is complete.
With transport_tcp_multiple_←-
receiver_behavior set to bounded←-
_latency or source_paced and old
messages are being removed to
make room for new messages,
the message being removed is
fragmented and only a portion of
it could be found and removed.
Processing will continue anyway.
Core-5688-3931: New message in
TCP buffer before old message is
complete.
With transport_tcp_multiple_←-
receiver_behavior set to bounded←-
_latency or source_paced and old
messages are being removed to
make room for new messages,
the message being removed is
fragmented and only a portion of
it could be found and removed.
Processing will continue anyway.
100 UM Log Messages
Core-5688-3986: PCRE exec
[s][s][d] error d
An error occurred while trying to
match the pattern listed in the first
bracketed expression. The topic
string attempting to be matched
is supplied as the second brack-
eted expression, and its length is
supplied as the third bracketed ex-
pression. The error that occurred
was internal to PCRE, and the er-
ror code is listed in the PCRE
documentation for return values of
pcre_exec.
Core-5688-4099: multiple inter-
faces match criteria - will use [s][s]
This warning occurs if an interface
is specified by name for any of
the ∗_interface options, and multi-
ple interfaces on the host match the
supplied name. In this case the first
matching interface will be used.
Specify interfaces such that only a
single interface is matched.
Core-5688-4100: multiple inter-
faces match criteria - will use [s][s]
This warning occurs if an interface
is specified by name for any of
the ∗_interface options, and multi-
ple interfaces on the host match the
supplied name. In this case the first
matching interface will be used.
Specify interfaces such that only a
single interface is matched.
Core-5688-4103: multiple inter-
faces match criteria - will use [s][s]
This warning occurs if an interface
is specified by name for any of
the ∗_interface options, and multi-
ple interfaces on the host match the
supplied name. In this case the first
matching interface will be used.
Specify interfaces such that only a
single interface is matched.
Core-5688-4104: multiple inter-
faces match criteria - will use [s][s]
This warning occurs if an interface
is specified by name for any of
the ∗_interface options, and multi-
ple interfaces on the host match the
supplied name. In this case the first
matching interface will be used.
Specify interfaces such that only a
single interface is matched.
Core-5688-4106: WARNING:
could not scan IPv4 interfaces.
As UMS initializes, it scans all the
network cards in the system. This
scan either failed due to a lack of
available resources. For example,
this might be because there are no
network cards that are active or the
system has run out of sockets.
Check the system availability of
network resources. Contact Infor-
matica support if all resources ap-
pear to be available.
Core-5688-4107: WARNING:
could not find a multicast capable,
non-loopback interface.
As UMS initializes, it scans all the
network cards in the system. If
no network card is listed as sup-
porting multicast capabilities, Ultra
Messaging generates this warning.
Check network card capabilities
and configuration.
Core-5688-4108: WARNING: us-
ing first broadcast capable inter-
face instead.
As UMS initializes, it scans all the
network cards in the system. No
multicast capable card was found,
but a broadcast capable card was
found. The first broadcast capable
card will be used.
Check network card configuration
if you expect one of the network
cards to be multicast capable.
9.1 UM Core Messages 101
Core-5688-410: failed to allocate
hypertopic callback vector of u
bytes [s:d]
There was a memory allocation fail-
ure while creating the vector of call-
backs associated with a received
message destined for a HyperTopic
receiver. This means that a mes-
sage will not be delivered to some
subset of registered HyperTopic re-
ceivers.
Core-5688-428: INFO: realloced
max rate controller srcs to u
This occurs when a lbtru source
has a larger than expected number
of clients (10∗number of transports
configured). This may be expected,
in which case this can be ignored.
It could also indicate a misconfigu-
ration.
Verify that the number of clients for
the source in question is correct.
Core-5688-429: WARNING: real-
loced max rate controller srcs to u
This occurs when a lbtru source
has a larger than expected number
of clients (10∗number of transports
configured). This may be expected,
in which case this can be ignored.
It could also indicate a misconfigu-
ration.
Verify that the number of clients for
the source in question is correct.
Core-5688-434: received read indi-
cation on daemon connection - un-
known socket
This message is used for internal
purpose.
Contact Informatica support.
Core-5688-436: daemon control
data received in unknown state d
This message is used for internal
purpose.
Contact Informatica support.
Core-5688-438: daemon control
data received in unknown state d
This message is used for internal
purpose.
Contact Informatica support.
Core-5688-439: invalid action re-
sponse on control channel [s]
This message is used for internal
purpose.
Contact Informatica support.
Core-5688-440: invalid topicname
on control channel [s]
This message is used for internal
purpose.
Contact Informatica support.
Core-5688-441: invalid action re-
sponse on control channel [s]
This message is used for internal
purpose.
Contact Informatica support.
Core-5688-446: lbmc_handle_msg
returned -1.
This message usually indicates
that Ultra Messaging cannot get
the memory required to process in-
coming messages.
Check with your system administra-
tor for possible reasons that Ultra
Messaging is not able to get suffi-
cient memory. Contact Informatica
support if this message keeps oc-
curring.
Core-5688-447: LBMC datagram
malformed. d d Dropping remain-
der. Origin: s:d
UM received a message with the
length field is less than lbm header
size.
Contact Informatica support if this
message occurs frequently.
Core-5688-448: LBMC datagram
malformed, msglen 0. Dropping.
Origin: s:d
UMS received a message with the
length field set to 0. The message
will be dropped.
Contact Informatica support if this
message occurs frequently.
Core-5688-449: LBMC datagram
malformed. d d Dropping remain-
der. Origin: s:d
A datagram's actual and expected
length do not match. If using UM
routers, this difference might occur
if there is a mismatch in the con-
figured values for configuration op-
tion transport_∗_datagram_max←-
_size settings at different portals. It
is also possible that this datagram
may have come from a non-Ultra-
Messaging application.
If using the UM router, check con-
figuration to ensure that values
for transport_∗_datagram_max_←-
size options match across portals.
Otherwise, check network for other
non-UM applications.
102 UM Log Messages
Core-5688-450: LBMC version in-
correct (u). Dropping. Origin: s:d.
The LBMC version value in the re-
ceived message is either corrupted
or not supported by the UM product
receiving messages.
Find the LBMC version value of the
received message in the log line
starting with Core-5688-450 and
check if it is supported in the prod-
uct you are using.
Core-5688-538: NOTICE: Source
"%s" retention_size_limit less than
max message size. Will retain at
least 1 message.
The source retention_size_limit
has been configured to be less
than the maximum message size
of 65536 bytes. It will still retain at
least 1 message.
Set the retention_size_limit to be
equal to or greater than the max
message size
Core-5688-539: NOTICE: Source
"%s" has no retention settings (1
message retained max)
Only 1 message will be retained
max due to default retention set-
tings at the Source.
Core-5688-542: received ACK for
unknown source from s:d
UMS received ACK for unknown
source. This is not a serious
problem but indicates that there is
a mismatch between this process
and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-5688-587: WARNING←-
: transport_lbtrm_activity_timeout
[d] is less than transport_lbtrm←-
_nak_generation_interval [d], this
can result in silent data loss if loss
occurs within the activity timeout
interval prior to the end of the
transport session.
If the transport_lbtrm_activity_←-
timeout is less than the transport←-
_lbtrm_nak_generation_interval it
is possible that a receiver can tear
down the transport session before
it was able to send a NAK for a
lossed message. When this hap-
pens the message is unrecover-
able.
Core-5688-58: loading default con-
fig file failed: s
Loading the config file speci-
fied with the LBM_DEFAULT_C←-
ONFIG_FILE environment variable
failed, due to either a missing file,
inappropriate access privileges, or
an error in the config file itself.
Core-5688-593: IPC Error: Creat-
ing Receiver Signal Semaphore
An error occurred when an IPC
receiver attempted to allocate a
shared signaling semaphore. This
could be caused by a permis-
sion error or no more resources.
Please refer to the documentation
for lbtipc_resource_manager.
Core-5688-594: IPC Error: Initializ-
ing Receiver Signal Semaphore (d)
An error occurred when an I←-
PC receiver attempted to initial-
ize a shared signaling semaphore.
Please refer to the OS error num-
ber given.
Core-5688-595: IPC Error: Creat-
ing Receiver Monitor Semaphore
An error occurred when an I←-
PC receiver attempted to allocate
a shared monitoring semaphore.
This could be caused by a permis-
sion error or no more resources.
Please refer to the documentation
for lbtipc_resource_manager.
9.1 UM Core Messages 103
Core-5688-596: IPC Error: Initial-
izing Receiver Monitor Semaphore
(d)
An error occurred when an I←-
PC receiver attempted to initialize
a shared monitoring semaphore.
Please refer to the OS error num-
ber given.
Core-5688-597: IPC Error: Initial-
izing Receiver Monitor Semaphore
(d)
An error occurred when an I←-
PC receiver attempted to initialize
a shared monitoring semaphore.
Please refer to the OS error num-
ber given.
Core-5688-598: IPC Error: Creat-
ing Shared Event (d) (s)
An IPC receiver could not create
a shared Event. This could be
caused by a permission error or the
resource already exists. Please re-
fer to the OS error number and re-
source name given.
Core-5688-599: IPC Error: Creat-
ing Receiver Monitor Mutex (d) (s)
An IPC receiver could not create
a shared monitoring Mutex. This
could be caused by a permission
error or the resource already exists.
Please refer to the OS error num-
ber and resource name given.
Core-5688-600: IPC Error: Getting
Receiver Monitor Mutex (d) (s)
An IPC receiver could not acquire
the shared monitoring Mutex. This
could be caused by a permission
error. Please refer to the OS error
number and resource name given.
Core-5688-601: lbtipc_rcv_←-
create: can not obtain transport
information
An IPC receiver is attempting to
join an IPC transport but can
not obtain the transport informa-
tion from the IPC shared memory
buffer. This could happen if the IPC
transport has been deleted before
the receiver has joined.
Core-5688-602: IPC Error: Join-
ing transport; no more free receiver
slots
An IPC receiver is attempting to
join an IPC transport that has
no more free slots for receivers.
Please adjust the "transport_←-
lbtipc_maximum_receivers_per_←-
transport" configuration attribute.
Core-5688-603: default thread
stack size is perhaps too small, u
bytes.
The IPC receiver has created a
thread for internal processing and
the default stack size is too small.
The size of the default stack size is
dumped and will then be set to a
larger size automatically.
Core-5688-604: reset thread stack
size to u bytes.
The IPC receiver has created a
thread for internal processing and
the default stack size is too small
and is reallocated. This message
reports the new size of the stack.
Core-5688-605: IPC Error: Creat-
ing Receiver Thread (d)
An error occurred when the IPC re-
ceiver attempted to create a thread
for internal processing. Please re-
fer to the OS error number given.
104 UM Log Messages
Core-5688-614: LBT-IPC: failed to
open shared memory (d)
The IPC shared memory region
could not be opened for read-
ing. This could occur if a re-
ceiver attempts to join an IPC trans-
port after the source has been
deleted. Please reference the OS
error number given.
Core-5688-615: LBT-IPC: failed to
map shared memory (d)
An error occurred trying to map a
pointer to the IPC shared memory
region. Please refer to the OS error
number given.
Core-5688-617: LBT-IPC: failed to
map shared memory (d)
An error occurred trying to map a
pointer to the IPC shared memory
region. Please refer to the OS error
number given.
Core-5688-618: LBT-IPC: can not
open shared semaphore (d)
The shared semaphore used to
ensure mutual exclusion while ac-
cessing IPC shared resources
could not be opened. This could
occur if a receiver attempts to join
an IPC transport after the source
has been deleted. Please refer to
the OS error number given.
Core-5688-619: LBT-IPC: failed to
open shared memory (d)
The IPC shared memory region
could not be opened for read-
ing. This could occur if a re-
ceiver attempts to join an IPC trans-
port after the source has been
deleted. Please reference the OS
error number given.
Core-5688-620: LBT-IPC: failed to
map shared memory (d)
An error occurred trying to map a
pointer to the IPC shared memory
region. Please refer to the OS error
number given.
Core-5688-622: LBT-IPC: failed to
map shared memory (d)
An error occurred trying to map a
pointer to the IPC shared memory
region. Please refer to the OS error
number given.
Core-5688-624: LBT-IPC: locking
problem detected in lbtipc_txw_←-
rcvr_node_alloc (d)
An error occurred with the shared
object used to ensure mutual exclu-
sion when accessing IPC shared
resources. Please refer to the OS
error number given.
Core-5688-625: LBT-IPC: locking
problem detected in lbtipc_txw_←-
rcvr_node_alloc (d)
An error occurred with the shared
object used to ensure mutual exclu-
sion when accessing IPC shared
resources. Please refer to the OS
error number given.
Core-5688-626: LBT-IPC: locking
problem detected in lbtipc_txw_←-
rcvr_node_alloc (d)
An error occurred with the shared
object used to ensure mutual exclu-
sion when accessing IPC shared
resources. Please refer to the OS
error number given.
9.1 UM Core Messages 105
Core-5688-627: LBT-IPC: locking
problem detected in lbtipc_txw_←-
rcvr_node_alloc (d)
An error occurred with the shared
object used to ensure mutual exclu-
sion when accessing IPC shared
resources. Please refer to the OS
error number given.
Core-5688-628: lbm_transport_←-
lbtipc_ctlr_delete: WFSO res=d,
GLE=d
The WaitForSingleObject() Win-
dows call return an error while wait-
ing for the IPC Receiver thread to
exit. Refer to the response and OS
error number given.
Core-5688-630: LBTIPC: error
mapping (initial) resource registry
(d)
An error occurred when attempting
to map memory to the registry file.
The registry is used to store IPC
shared objects that are in use. The
OS error number is given.
Core-5688-632: LBTIPC: error ini-
tializing registry semaphore (d)
The semaphore used to ensure
mutual exclusion while accessing
the registry could not be initialized.
The registry is used to store IPC
shared objects that are in use. Re-
fer to the documentation for lbtipc←-
_resource_manager.
Core-5688-633: LBTIPC: error
opening resource registry (d)
An error occurred when attempting
to open or map memory to the reg-
istry file. The OS error number is
given.
Core-5688-635: LBTIPC: resource
registry version mismatch: use
lbtipc_resource_manager to clean-
up and delete registry.
An IPC registry file existed, and
contained the wrong version.
For this to happen, a registry file
with incorrect version information
would have to be deliberately put in
place. 3.5 and post3.5 use differ-
ent naming schemes for registries,
so this can't happen due to version
mismatch.
Core-5688-636: LBTIPC: error
re-mapping resource registry
(entries: d) (d)
An error occurred when attempting
to re-map memory to the registry
file. The registry is used to store
IPC shared objects that are in use.
The size in entries and OS error
number is given.
Core-5688-637: LBTIPC: er-
ror opening/recreating registry
semaphore (d)
The semaphore used to ensure
mutual exclusion while accessing
the registry could not be created.
The registry is used to store IPC
shared objects that are in use. The
OS error number is given.
Core-5688-638: LBTIPC: error
reinitializing registry semaphore (d)
The semaphore used to ensure
mutual exclusion while accessing
the registry could not be initialized.
The registry is used to store IPC
shared objects that are in use. The
OS error number is given.
Core-5688-639: LBTIPC: error re-
creating resource registry (d)
The registry used to store IPC
shared objects that are in use could
not be created. The OS error num-
ber is given.
106 UM Log Messages
Core-5688-640: LBTIPC: error in
re-sizing resource registry (d)
The registry used to store IPC
shared objects that are in use could
not be re-sized (expanded). The
OS error number is given.
Core-5688-641: LBTIPC: error re-
mapping resource registry (d)
An error occurred when attempting
to re-map memory to the registry
file (file expansion). The registry
is used to store IPC shared objects
that are in use. The OS error num-
ber is given.
Core-5688-642: LBTIPC: No free
semaphores could be found
A free semaphore required for the
LBT-IPC transport could not be
found. Refer to the documentation
for lbtipc_resource_manager.
Core-5688-644: LBTIPC: error
opening semaphore (d)
A free semaphore allocated for the
LBT-IPC transport could not be
opened. The OS error number is
given.
Core-5688-645: LBTIPC: error
freeing semaphore; key 0xx not
found
A semaphore allocated for the L←-
BT-IPC transport could not be freed
due to an invalid internal key.
Contact Informatica support.
Core-5688-646: LBT-IPC unex-
pected send error
An attempt was made to transfer a
message or message fragment to
the IPC shared memory buffer but
that operation failed. This is cause
by a failure with trying to obtain the
lock for the shared memory buffer.
Core-5688-647: LBT-IPC failed to
start stalled timer
The IPC source is blocked waiting
for a receiver but received an error
trying to start the block check timer.
Core-5688-648: LBT-IPC failed to
start stalled timer
The IPC source is blocked waiting
for a receiver but received an error
trying to start the block check timer.
Core-5688-649: LBT-IPC unex-
pected send error
An attempt was made to transfer a
message or message fragment to
the IPC shared memory buffer but
that operation failed. This is cause
by a failure with trying to obtain the
lock for the shared memory buffer.
Core-5688-650: LBT-IPC unex-
pected send error
An attempt was made to transfer a
message or message fragment to
the IPC shared memory buffer but
that operation failed. This is cause
by a failure with trying to obtain the
lock for the shared memory buffer.
Core-5688-651: LBT-IPC Problem
Opening Signal Semaphore (d)
The IPC source has received a
connection request from an IPC re-
ceiver and has failed to open the
shared signaling semaphore. This
could happen if the connection re-
quest is old and the receiver was
already deleted or the source does
not have permission to open the
object. Please reference the OS er-
ror number given.
9.1 UM Core Messages 107
Core-5688-652: LBT-IPC Problem
Opening Event (d)
The IPC source has received a
connection request from an IPC re-
ceiver and has failed to open the
shared Event. This could happen
if the connection request is old and
the receiver was already deleted or
the source does not have permis-
sion to open the object. Please ref-
erence the OS error number given.
Core-5688-653: LBT-IPC Problem
Opening Monitor Semaphore (d)
The IPC source has received a
connection request from an IPC re-
ceiver but has failed to open the
Monitoring Semaphore. This could
happen if the connection request
is old and the receiver was al-
ready deleted or the source does
not have permission to open the
object. Please reference the OS er-
ror number given.
Core-5688-654: LBT-IPC Problem
Opening Monitor Mutex (d) (s)
The IPC source has received a
connection request from an IPC re-
ceiver but has failed to open the
Monitoring Mutex. This could hap-
pen if the connection request is
old and the receiver was already
deleted or the source does not
have permission to open the ob-
ject. Please reference the OS error
number and object name given.
Core-5688-692: topic level retrans-
mission request index, u, not found
A unicast immediate message was
requested for retransmission, but
the message is no longer required.
This is because the message was
already received due a previous
retransmission request or because
the request has already timed out.
Core-5688-694: received retrans-
mit request for unknown source on
a thread/context without a topic re-
solver.
UMS received retransmit request
for unknown source. This is not a
serious problem but indicates that
there is a mismatch between this
process and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-5688-696: received retrans-
mit request for unknown source[u]
from ip:port[s:d]
UMS received retransmit request
for unknown source. This is not a
serious problem but indicates that
there is a mismatch between this
process and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-5688-697: received lji re-
quest for unknown source on a
thread/context without a topic re-
solver in ctx[p] from ip:port[s:d] for
topic[u]
A context without a resolver mod-
ule has received an Late-Join Ini-
tiation REQ.This is not a serious
problem but indicates that there is
a mismatch between this process
and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
108 UM Log Messages
Core-5688-699: received lji re-
quest for unknown source: from
ip:port[s:d] for topic[u]
UMS received Late Join Request
message for unknown source. The
source transport and topic indices
are not mapped to this context.
This may indicate that a source had
been deleted, or there is a mis-
match between this process and
another.
Check the system for port re-use
on application restart and similar
behavior.
Core-5688-701: received PREG
response for unknown source.
Each topic created and registered
by a UMP context has a unique
topic index. The UMP registra-
tion response handler for this con-
text has received a response for
a topic index not contained in the
collection of sources currently be-
ing processed by the context. This
is not a serious condition unless it
continues to occur frequently and
sources being handled by the con-
text are not being successfully reg-
istered.
Core-5688-702: received PREG
response for unknown source.
Each topic created and registered
by a UMP context has a unique
topic index. The UMP registra-
tion response handler for this con-
text has received a response for
a topic index not contained in the
collection of sources currently be-
ing processed by the context. This
is not a serious condition unless it
continues to occur frequently and
sources being handled by the con-
text are not being successfully reg-
istered.
Core-5688-703: received PREG
response for unknown receiver.
Each topic created and registered
by a UMP context has a unique
topic index. The UMP registra-
tion response handler for this con-
text has received a response for
a topic index not contained in the
collection of receivers currently be-
ing processed by the context. This
is not a serious condition unless it
continues to occur frequently and
receivers being handled by the con-
text are not being successfully reg-
istered.
Core-5688-705: received UME
Keepalive with unknown type x
UMP received keepalive signal
which the type cannot be deter-
mined. This is not a serious prob-
lem unless it happens frequently.
Core-5867-19: Message selector
parser error [s]
An error was encountered parsing
the message selector set for a re-
ceiver
Ensure the receiver has a valid
message selector
Core-5867-20: Message selector
parser error [Unterminated string s]
An error was encountered parsing
the message selector set for a re-
ceiver
Ensure the receiver has a valid
message selector
9.1 UM Core Messages 109
Core-5867-21: Message selector
parser error [Invalid character 'c']
An error was encountered parsing
the message selector set for a re-
ceiver
Ensure the receiver has a valid
message selector
Core-5867-22: Message selector
parser error [Error compiling pat-
tern s at offset d: err s]
An error was encountered parsing
the message selector set for a re-
ceiver
Ensure the receiver has a valid
message selector
Core-5867-23: Message selector
parser error [Error compiling pat-
tern s at offset d: err s]
An error was encountered parsing
the message selector set for a re-
ceiver
Ensure the receiver has a valid
message selector
Core-5872-1: LBMR Topic Info
Record Total Length too large.
Dropping remainder.
This error is logged if the options
portion of the received TIR packet
would overflow the stack-allocated
buffer.
This error indicates that packets
with erroneous length fields are be-
ing received by UM. This could be
due to applications sending to the
incorrect IP and port, or by a mali-
cious attack.
Core-5872-2: LBMR Queue Info
Record Total Length too large.
Dropping remainder.
This error is logged if the options
portion of the received QIR packet
would overflow the stack-allocated
buffer.
This error indicates that packets
with erroneous length fields are be-
ing received by UM. This could be
due to applications sending to the
incorrect IP and port, or by a mali-
cious attack.
Core-5894-1: lbm_timer_expire←-
: Exceeded d timer expirations in
one iteration
UM encountered a condition where
the specified number of timers
were expiring at the same time.
This is undesirable and indicates
a CPU burst usage. To prevent
starvation of network processing,
some timers are deferred for pro-
cessing and network processing is
resumed. All timers are eventu-
ally processed with a minor delay -
this is acceptable behaviour. If this
message occurs frequently, contact
Informatica support for further guid-
ance.
Examine the configuration of this
process to determine if there are
timers likely to coincide in their
expirations or if there are many
sources created very quickly. If
there are, it is suggested that the
timers or source creation are stag-
gered.
Core-5894-2: lbm_timer_expire←-
: Exceeded d timer expirations in
one iteration
UM encountered a condition where
the specified number of timers
were expiring at the same time.
This is undesirable and indicates
a CPU burst usage. To prevent
starvation of network processing,
some timers are deferred for pro-
cessing and network processing is
resumed. All timers are eventu-
ally processed with a minor delay -
this is acceptable behaviour. If this
message occurs frequently, contact
Informatica support for further guid-
ance.
Examine the configuration of this
process to determine if there are
timers likely to coincide in their
expirations or if there are many
sources created very quickly. If
there are, it is suggested that the
timers or source creation are stag-
gered.
Core-5927-1: Couldn't establish
immediate message channel for
destination s:d
A connection could not be estab-
lished to send a unicast message.
Check the logs for previous mes-
sages indicating the actual cause,
usually a socket error of some kind.
Core-5935-1: LBMC header with
malformed length field. Dropping.
Origin: s:d
An LBMC header was received
with a malformed length field.
Check the originating IP and port
for applications sending malformed
data.
110 UM Log Messages
Core-5935-2: LBMC header with
malformed length field. Dropping.
Origin: s:d
An LBMC header was received
with a malformed length field.
Check the originating IP and port
for applications sending malformed
data.
Core-5935-3: LBMC header with
malformed length field. Dropping.
Origin: s:d
An LBMC header was received
with a malformed length field.
Check the originating IP and port
for applications sending malformed
data.
Core-5935-4: LBMC header with
malformed length field. Dropping.
Origin: s:d
An LBMC header was received
with a malformed length field.
Check the originating IP and port
for applications sending malformed
data.
Core-5935-5: LBMC header with
malformed length field. Dropping.
Origin: s:d
An LBMC header was received
with a malformed length field.
Check the originating IP and port
for applications sending malformed
data.
Core-5935-6: LBMC header with
malformed length field. Dropping.
Origin: s:d
An LBMC header was received
with a malformed length field.
Check the originating IP and port
for applications sending malformed
data.
Core-5936-1: LBMR optlen total←-
_len malformed. Dropping packet.
Origin: s:d
A topic resolution message was re-
ceived with a length field that did
not match the data received.
Inspect the originating IP and Port
for applications sending malformed
topic resolution messages.
Core-5937-1: Invalid 0-length L←-
BMR option. Dropping packet.
Origin: s:d
An LBMR packet was droppped be-
cause of a 0-length option field.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-5937-2: LBMR Topic Query
Record malformed. Dropping re-
mainder. Origin: s:d
An LBMR packet was droppped be-
cause it could not be parsed.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-5937-3: LBMR Topic Info
Record malformed. Dropping re-
mainder. Origin: s:d
An LBMR packet was droppped be-
cause it could not be parsed.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-5937-4: LBMR Topic Man-
agement Record malformed. Drop-
ping remainder. Origin: s:d
An LBMR packet was droppped be-
cause it could not be parsed.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-5937-5: LBMR Topic Man-
agement Record malformed. Drop-
ping remainder. Origin: s:d
An LBMR packet was droppped be-
cause it could not be parsed.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-5937-6: LBMR Topic Info
Record option length invalid. Drop-
ping Remainder.
UMS encountered a malformed L←-
BMR packet and discarded it.
Core-5937-7: LBMR Queue Info
Record option length invalid. Drop-
ping remainder.
A QIR packet was received that
contained a 0-length option record.
Core-5938-1: Header size is in-
correct for header type. Dropping.
Origin: s:d.
A malformed LBMC header was re-
ceived.
Check the originating IP and port
for an application sending incor-
rectly formed packets.
Core-5938-2: Header size is in-
correct for header type. Dropping.
Origin: s:d.
A malformed LBMC header was re-
ceived.
Check the originating IP and port
for an application sending incor-
rectly formed packets.
Core-5938-3: Received lbmc mes-
sage with incorrect header length.
Dropping. Origin: s:d.
A malformed LBMC header was re-
ceived.
Check the originating IP and port
for an application sending incor-
rectly formed packets.
Core-5957-1: s: XInclude process-
ing failed.
There was error processing XML
includes.
Check your XML configuration file
syntax.
Core-5957-2: XInclude processing
failed.
There was error processing XML
includes.
Check your XML configuration file
syntax.
Core-5957-3: s: Error removing
xml:base attribute
There was error processing XML
includes.
Check your XML configuration file
syntax, or contact Informatica sup-
port.
9.1 UM Core Messages 111
Core-5957-4: Error removing xml←-
:base attribute
There was error processing XML
includes.
Check your XML configuration file
syntax, or contact Informatica sup-
port.
Core-5975-50: LBMC Route Info
Neighbor header size incorrect.
Dropping. Origin: s:d.
Route Info message header con-
tains incorrect size.
Check source (IP:Port) for possible
version mismatch or service attack.
Core-5988-1: Attempting to Re-
spond to a Request from s with port
set to zero.
A response is being generated but
the response port is zero so the
data will not be delivered to the re-
quester.
This occurs when the requester
disables binding of the request
port. See request_tcp_bind_←-
request_port configuration option.
Core-5988-2: Source Side Filtering
request from [s] but response port
set to zero. No messages will be
received from this source.
The receiver is registering Source
Side Filtering interest but the
source response port is zero. The
interest will not arrive at the source
and therefore will not send this re-
ceiver any messages.
This occurs when the source dis-
ables binding of the request port.
See request_tcp_bind_request_←-
port configuration option.
Core-5988-3: Topic Advertisement
[s] contains UME Store info from s
but port is set to zero. Ignoring in-
valid UME Store Info.
A Topic Advertisement was re-
ceived with UME Information but
the store port was zero. The UME
Information is being ignored.
This occurs when the Source
or Store disables binding of the
request port. See request←-
_tcp_bind_request_port configura-
tion option.
Core-5988-4: Topic Advertisement
[s] contains UME Source Info from
s but port is set to zero. Ignoring
invalid UME Source Info.
A Topic Advertisement was re-
ceived with UME Information but
the source port was zero. The UME
Information is being ignored.
This occurs when the Source
or Store disables binding of the
request port. See request←-
_tcp_bind_request_port configura-
tion option.
Core-5988-5: Topic Advertisement
[s] contains Late Join from s but
port is set to zero. Ignoring invalid
Late Join setup.
A Topic Advertisement was re-
ceived with Late Join Information
but the source port was zero. The
Late Join Information is being ig-
nored.
This occurs when the Source dis-
ables binding of the request port.
See request_tcp_bind_request_←-
port configuration option.
Core-5988-6: Topic Advertisement
[s] contains UME Store Info from s
but port is set to zero. Ignoring in-
valid UME Store Info.
A Topic Advertisement was re-
ceived with UME Information but
the store port was zero. The UME
Information is being ignored.
This occurs when the Source
or Store disables binding of the
request port. See request←-
_tcp_bind_request_port configura-
tion option.
Core-5988-7: Topic Advertisement
[s] contains ULB Info from s but
port is set to zero. Ignoring invalid
ULB Info.
A Topic Advertisement was re-
ceived with ULB Information but the
source port was zero. The UME In-
formation is being ignored.
This occurs when the Source dis-
ables binding of the request port.
See request_tcp_bind_request_←-
port configuration option.
Core-5990-1: UMQ command
failed because the REQUIR←-
ED queue authentication failed..
cmd_type=0xx
warning the user credential is not
correct for authentication purpose
Core-6020-6: inflight bytes would
be negative, resetting to 0
A call to decrement the number of
inflight bytes would set it to be neg-
ative.
Nothing, it is forcibly set to 0 in this
case.
Core-6020-7: inflight bytes would
be negative, resetting to 0
Amount of bytes being decre-
mented would cause inflight bytes
to be negative
Current flight size could be incor-
rect due to unknown reasons, use
the set flight size API to reset val-
ues
Core-6033-12: [LBMMON] Invalid
statistics packet received
An invalid statistics packet was re-
ceiver.
Contact Informatica support.
Core-6033-13: [LBMMON] Format
module source deserialize function
returned d, s
A source statistics message was
unable to be parsed.
Contact Informatica support.
112 UM Log Messages
Core-6033-14: [LBMMON] Format
module receiver deserialize func-
tion returned d, s
A receiver transport statistics mes-
sage was unable to be parsed.
Contact Informatica support.
Core-6033-15: [LBMMON] Format
module event queue deserialize
function returned d, s
An event queue statistics message
was unable to be parsed.
Contact Informatica support.
Core-6033-16: [LBMMON] Format
module context deserialize function
returned d, s
A context statistics message was
unable to be parsed.
Contact Informatica support.
Core-6033-17: [LBMMON] Format
module receive function returned d,
s
An error occured while receiving a
statistics message.
Contact Informatica support.
Core-6033-26: [LBMMON] Error
d returned from transport module
send function, s
Failed to send a source transport
statistics packet.
Contact Informatica support.
Core-6033-27: [LBMMON] Error
d returned from format module
source serialize function, s
Failed to format a source transport
statistics packet.
Contact Informatica support.
Core-6033-28: [LBMMON] Error
d returned from transport module
send function, s
Failed to send a receiver transport
statistics packet.
Contact Informatica support.
Core-6033-29: [LBMMON] Error d
returned from format module re-
ceiver serialize function, s
Failed to format a receiver transport
statistics packet.
Contact Informatica support.
Core-6033-30: [LBMMON] Error
d returned from transport module
send function, s
Failed to send an event queue
statistics packet.
Contact Informatica support.
Core-6033-31: [LBMMON] Error d
returned from format module event
queue serialize function, s
Failed to format an event queue
statistics packet.
Contact Informatica support.
Core-6033-32: [LBMMON] Error
d returned from transport module
send function, s
Failed to send a context statistics
packet.
Contact Informatica support.
Core-6033-33: [LBMMON] Error d
returned from format module con-
text serialize function, s
Failed to format a context statistics
packet.
Contact Informatica support.
Core-6033-34: [LBMMON] Error
d returned from transport module
send function, s
Failed to send an IM source trans-
port statistics packet.
Contact Informatica support.
Core-6033-35: [LBMMON] Error
d returned from format module
source serialize function, s
Failed to format an IM source trans-
port statistics packet.
Contact Informatica support.
Core-6033-36: [LBMMON] Error
d returned from transport module
send function, s
Failed to send an IM receiver trans-
port statistics packet.
Contact Informatica support.
Core-6033-37: [LBMMON] Error d
returned from format module re-
ceiver serialize function, s
Failed to format an IM receiver
transport statistics packet.
Contact Informatica support.
Core-6033-881: timer scheduled
<= MIN_CLOCK_RES_MSEC (lu
ms) @ [ld.ld]: Rescheduling for d
ms
The requested timer length was
too small to be accurately applied
based on the clock resolution, and
has been forcibly increased so it
does not execute immediately.
Use 0 for immediate timeout, or
MIN_CLOCK_RES_MSEC for low-
est pause before timeout
Core-6033-998: Requested re-
transmission queue is too big [lu]
The requested retransmission
queue size is too big
Consider reducing retransmission-
request-processing-rate
9.1 UM Core Messages 113
Core-6033-999: malloc failure Malloc failure Box may be out of memory,
consider reducing retransmission-
request-processing-rate
Core-6036-1: LBMC stream cor-
ruption detected. Tearing down
stream. Origin: s:d
Data was received in an incon-
sistent state from an LBMC TCP
stream.
Investigate the listed IP and port for
applications or network hardware
that may be causing message cor-
ruption.
Core-6036-2: LBMC stream cor-
ruption detected. Tearing down
stream. Origin: s:d
Data was received in an incon-
sistent state from an LBMC TCP
stream.
Investigate the listed IP and port for
applications or network hardware
that may be causing message cor-
ruption.
Core-6056-1: Malformed fragment
header detected, discarding.
A fragment header was detected
with a malformed length field.
If this message is seen frequently,
it may indicate that network hard-
ware is corrupting packets, or that
a program is generating spurious
traffic directed at a port used by L←-
BM.
Core-6190-1: LBMR TIR contained
inconsistent transport information.
UM encountered an advertisement
indicating a transport that was al-
ready known, but the OTID did not
match the known OTID.
The advertisement's originating IP
and port will be logged in a subse-
quent message. Investigate that IP
and port for an application generat-
ing spurious traffic.
Core-6190-2: LBMR Topic Info
Record malformed. Dropping re-
mainder. Origin: s:d
An LBMR packet was droppped be-
cause it could not be parsed.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-6238-1: PCRE exec [s][s][d]
error d
A receiver was configured with a in-
valid LIKE expression message se-
lector
Fix the LIKE expression to be JMS
compliant
Core-6238-2: PCRE compile [s][s]
error d
A receiver was configured with a in-
valid LIKE expression message se-
lector
Fix the LIKE expression to be JMS
compliant
Core-6259-10: LBMR Topic Res-
olution Remote Domain Route
packet malformed (d:d). Dropping.
Origin: s:d
LBMR Data received contain in-
valid data.
Check the source (IP:Port) for pos-
sible version mismatch or service
attack.
Core-6259-11: Too many domains
for routing message u; not sending
message.
With the given number of domains,
a domain routing message cannot
be generated and traffic will not be
routed properly.
The customer can increase the
resolver_datagram_max_size.
However, this message indicates
a suspiciously large number of
domains.
Core-6259-12: Failed sending
Response: cannot find route to
Remote Domain u (s:d)
There is no known route to the
given domain. This could hap-
pen momentarily as an LBM con-
text learns the domain routes at
startup.
This will be reported once per
domain. A "route discovered to
domain" should follow soon after.
If not, the Gateway configuration
should be examined for inconsis-
tencies.
Core-6259-13: Failed sending Uni-
cast Buffer: cannot find route to Re-
mote Domain u (s:d)
There is no known route to the
given domain. This could hap-
pen momentarily as an LBM con-
text learns the domain routes at
startup.
This will be reported once per
domain. A "route discovered to
domain" should follow soon after.
If not, the Gateway configuration
should be examined for inconsis-
tencies.
114 UM Log Messages
Core-6259-14: Failed sending Uni-
cast Buffer: cannot find route to Re-
mote Domain: u (s:d)
There is no known route to the
given domain. This could hap-
pen momentarily as an LBM con-
text learns the domain routes at
startup.
This will be reported once per
domain. A "route discovered to
domain" should follow soon after.
If not, the Gateway configuration
should be examined for inconsis-
tencies.
Core-6259-15: Failed sending Uni-
cast Control Message: cannot find
route to Remote Domain u (s:d)
There is no known route to the
given domain. This could hap-
pen momentarily as an LBM con-
text learns the domain routes at
startup.
This will be reported once per
domain. A "route discovered to
domain" should follow soon after.
If not, the Gateway configuration
should be examined for inconsis-
tencies.
Core-6259-16: Failed sending Uni-
cast Message: cannot find route to
Remote Domain u (s:d)
There is no known route to the
given domain. This could hap-
pen momentarily as an LBM con-
text learns the domain routes at
startup.
This will be reported once per
domain. A "route discovered to
domain" should follow soon after.
If not, the Gateway configuration
should be examined for inconsis-
tencies.
Core-6259-19: LBMC Topic Index
header size incorrect. Dropping.
Origin: s:d.
Topic Index message header con-
tains incorrect size.
Check source (IP:Port) for possible
version mismatch or service attack.
Core-6259-1: Re-routing Domain
ID u: old: s:d new: s:d
There was a change in the route to
the given host. This can happen
at startup, when a Gateway goes
down, or when there is connectiv-
ity problem.
This is normal on occasion. Per-
sistent messages could indicate a
network or Gateway issue.
Core-6259-20: Domain ID discov-
ered; context resides in Domain ID
u
Log message indicates a Domain
ID discovery.
This is not an error.
Core-6259-21: Failed sending
Response: cannot find route to
Remote Domain u (s:d)
There is no known route to the
given domain. This could hap-
pen momentarily as an LBM con-
text learns the domain routes at
startup.
This will be reported once per
domain. A "route discovered to
domain" should follow soon after.
If not, the Gateway configuration
should be examined for inconsis-
tencies.
Core-6259-22: Failed sending
Response: cannot find route to
Remote Domain u (s:d)
There is no known route to the
given domain. This could hap-
pen momentarily as an LBM con-
text learns the domain routes at
startup.
This will be reported once per
domain. A "route discovered to
domain" should follow soon after.
If not, the Gateway configuration
should be examined for inconsis-
tencies.
Core-6259-23: Failed sending
Response: cannot find route to
Remote Domain u (s:d)
There is no known route to the
given domain. This could hap-
pen momentarily as an LBM con-
text learns the domain routes at
startup.
This will be reported once per
domain. A "route discovered to
domain" should follow soon after.
If not, the Gateway configuration
should be examined for inconsis-
tencies.
Core-6259-24: Failed sending
Response: cannot find route to
Remote Domain u (s:d)
There is no known route to the
given domain. This could hap-
pen momentarily as an LBM con-
text learns the domain routes at
startup.
This will be reported once per
domain. A "route discovered to
domain" should follow soon after.
If not, the Gateway configuration
should be examined for inconsis-
tencies.
9.1 UM Core Messages 115
Core-6259-25: Deserialize
Response: Context in domain
u received response with no
domain: s:d
A context that knows it's domain
deserialized a response that con-
tained no Domain ID. The response
will likely not get back to the sender.
This could happen momentarily as
an LBM contexts learn their domain
routes at startup.
If the warning persists, the Gate-
way configuration should be exam-
ined for inconsistencies.
Core-6259-26: Route discovered
to Domain ID u through s:d
A new route to the given Domain ID
was discovered.
This is normal upon startup of
Gateways.
Core-6259-27: Unicast message
arrived at Gateway from Local Do-
main via direct path. Source: s:u
A Unicast Message arrived at a
Gateway destined for the local Do-
main.
A user has likely unicast a mes-
sage directly to the Gateway. The
user needs to Unicast the message
to the final application. UMS will
take care of the routing.
Core-6259-28: Unicast message
arrived from Remote Domain (u)
via direct path. Source: s:u
A Unicast Message arrived with the
destination domain different that
the local domain (unicast direct).
A user has likely unicast a mes-
sage directly to an application in a
different domain. If this is desired,
either specify a zero Domain ID or
don't supply a Domain ID. Using the
local Domain ID will not suffice.
Core-6259-29: Unicast message
arrived at Gateway from Local Do-
main via direct path. Source: s:u
A Unicast Message arrived at a
Gateway destined for the local Do-
main.
A user has likely unicast a mes-
sage directly to the Gateway. The
user needs to Unicast the message
to the final application. UMS will
take care of the routing.
Core-6259-2: Route discovered to
Domain ID u through s:d
A new route to the given Domain ID
was discovered.
This is normal upon startup of
Gateways.
Core-6259-30: Unicast message
arrived from Remote Domain (u)
via direct path. Source: s:u
A Unicast Message arrived with the
destination domain different that
the local domain (unicast direct).
A user has likely unicast a mes-
sage directly to an application in a
different domain. If this is desired,
either specify a zero Domain ID or
don't supply a Domain ID. Using the
local Domain ID will not suffice.
Core-6259-3: LBMC DESTINAT←-
ION header size incorrect. Drop-
ping. Origin: s:d.
Destination message header con-
tains incorrect size.
Check source (IP:Port) for possible
version mismatch or service attack.
Core-6259-4: LBMC DESTINAT←-
ION header size incorrect. Drop-
ping. Origin: s:d.
Destination message header con-
tains incorrect size.
Check source (IP:Port) for possible
version mismatch or service attack.
Core-6259-6: LBMR Domain ID
option invalid len [u]. Dropping
packet. Origin: s:d
LBMR Data received contain in-
valid data.
Check the source (IP:Port) for pos-
sible version mismatch or service
attack.
Core-6259-7: Domain ID discov-
ered via s:d; context resides in Do-
main ID u.
Log message indicates a Domain
ID discovery.
This is not an error.
Core-6259-8: LBMR Domain ID
option contains a mismatched do-
main [u:u]. Dropping packet.
Origin: s:d
LBMR Data received contain in-
valid data.
Check the source (IP:Port) for pos-
sible version mismatch or service
attack.
Core-6259-9: LBMR Topic Res-
olution Remote Domain Route
packet malformed (d:d). Dropping.
Origin: s:d
LBMR Data received contain in-
valid data.
Check the source (IP:Port) for pos-
sible version mismatch or service
attack.
116 UM Log Messages
Core-6322-10: ULB receiver index
reserve command response for un-
known receiver.
UMS received a ULB receiver in-
dex reserve command response for
an unknown receiver. This is not a
serious problem but indicates that
there is a mismatch between this
process and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-6322-11: ULB index com-
mand response error for unknown
receiver.
UMS received a ULB index com-
mand response error for an un-
known receiver. This is not a se-
rious problem but indicates that
there is a mismatch between this
process and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-6322-12: ULB index stop as-
signment command for unknown
source.
UMS received a ULB index stop
assignment command for an un-
known source. This is not a serious
problem but indicates that there is
a mismatch between this process
and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-6322-13: ULB index start as-
signment command for unknown
source.
UMS received a ULB index start
assignment command for an un-
known source. This is not a serious
problem but indicates that there is
a mismatch between this process
and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-6322-14: ULB index release
command for unknown source.
UMS received a ULB index release
command for an unknown source.
This is not a serious problem but
indicates that there is a mismatch
between this process and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-6322-15: ULB index reserve
command for unknown source.
UMS received a ULB index reserve
command for an unknown source.
This is not a serious problem but
indicates that there is a mismatch
between this process and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-6322-16: received ULB re-
ceiver registration error response
for unknown receiver.
UMS received a ULB receiver reg-
istration error response, but did not
register as a ULB receiver. This is
not a serious problem but indicates
that there is a mismatch between
this process and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-6322-17: received ULB re-
ceiver registration response for un-
known receiver.
UMS received a ULB receiver reg-
istration response, but did not reg-
ister as a ULB receiver. This is not
a serious problem but indicates that
there is a mismatch between this
process and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-6322-18: received ULB re-
ceiver de-registration response for
unknown receiver.
UMS received a ULB receiver de-
registration response, but did not
register as a ULB receiver. This is
not a serious problem but indicates
that there is a mismatch between
this process and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-6322-19: received ULB RCR
for unknown receiver.
UMS received a ULB RCR, but did
not register as a ULB receiver. This
is not a serious problem but indi-
cates that there is a mismatch be-
tween this process and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
9.1 UM Core Messages 117
Core-6322-1: received liveness
keepalive for unknown source.
UMS received a liveness keepalive
for an unknown source. This is
not a serious problem but indicates
that there is a mismatch between
this process and another. Check
the system for other abnormal be-
haviour (applications restarting etc)
Core-6322-20: received ULB uni-
cast message for unknown re-
ceiver.
UMS received a ULB unicast mes-
sage, but did not register as a U←-
LB receiver. This is not a serious
problem but indicates that there is
a mismatch between this process
and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-6322-21: received UMQ
command response for unknown
command.
UMS received a UMQ command
response for an unknown com-
mand. This is not a serious
problem but indicates that there is
a mismatch between this process
and another. Check the system for
other abnormal behaviour (applica-
tions restarting etc)
Core-6322-22: received UMQ in-
dex command response for un-
known command.
UMS received a UMQ index com-
mand response for an unknown
command. This is not a serious
problem but indicates that there is
a mismatch between this process
and another. Check the system for
other abnormal behaviour (applica-
tions restarting etc)
Core-6322-23: received UMQ reg-
istration response, but did not reg-
ister with a queue.
UMS received a UMQ registration
response, but did not register with
a queue . This is not a serious
problem but indicates that there is
a mismatch between this process
and another. Check the system for
other abnormal behaviour (applica-
tions restarting etc)
Core-6322-24: received UMQ sta-
bility ACK for unknown source.
UMS received a UMQ stability A←-
CK for an unknown source . This is
not a serious problem but indicates
that there is a mismatch between
this process and another. Check
the system for other abnormal be-
haviour (applications restarting etc)
Core-6322-25: received UMQ RCR
for unknown receiver.
UMS received a UMQ RCR for
an unknown receiver . This is
not a serious problem but indicates
that there is a mismatch between
this process and another. Check
the system for other abnormal be-
haviour (applications restarting etc)
118 UM Log Messages
Core-6322-26: received UMQ
keepalive for unknown client.
UMS received a UMQ keepalive
for an unknown client . This is
not a serious problem but indicates
that there is a mismatch between
this process and another. Check
the system for other abnormal be-
haviour (applications restarting etc)
Core-6322-27: received ACK for
unknown source.
UMS received ACK for unknown
source. This is not a serious
problem but indicates that there is
a mismatch between this process
and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-6322-2: received ULB re-
ceiver registration for unknown
source.
UMS received a ULB receiver reg-
istration, but was not configured as
a ULB source. This is not a serious
problem but indicates that there is
a mismatch between this process
and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-6322-3: received ULB re-
ceiver de-registration for unknown
source.
UMS received a ULB receiver de-
registration, but was not configured
as a ULB source. This is not a
serious problem but indicates that
there is a mismatch between this
process and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-6322-4: received ULB re-
ceiver ACK for unknown source.
UMS received a ULB receiver A←-
CK, but was not configured as a
ULB source. This is not a serious
problem but indicates that there is
a mismatch between this process
and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-6322-5: received ULB RXR←-
EQ for unknown source.
UMS received a ULB RXREQ,
but was not configured as a U←-
LB source. This is not a serious
problem but indicates that there is
a mismatch between this process
and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-6322-6: received ULB
keepalive or keepalive response,
but not using ULB
UMS received a ULB keepalive,
but was not configured as a U←-
LB source. This is not a serious
problem but indicates that there is
a mismatch between this process
and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-6322-7: ULB receiver in-
dex stop assignment command re-
sponse for unknown receiver.
UMS received a ULB receiver in-
dex stop assignment command re-
sponse for an unknown receiver.
This is not a serious problem but
indicates that there is a mismatch
between this process and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-6322-8: ULB receiver in-
dex start assignment command re-
sponse for unknown receiver.
UMS received a ULB receiver in-
dex start assignment command re-
sponse for an unknown receiver.
This is not a serious problem but
indicates that there is a mismatch
between this process and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
9.1 UM Core Messages 119
Core-6322-9: ULB receiver index
release command response for un-
known receiver.
UMS received a ULB receiver in-
dex release command response for
an unknown receiver. This is not a
serious problem but indicates that
there is a mismatch between this
process and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-6340-1: Malformed config opt
option encountered. Dropping.
Origin: s:d.
A malformed LBMC header was re-
ceived.
Check the originating IP and port
for an application sending incor-
rectly formed packets.
Core-6340-2: Malformed config opt
option encountered. Dropping.
Origin: s:d.
A malformed LBMC header was re-
ceived.
Check the originating IP and port
for an application sending incor-
rectly formed packets.
Core-6340-3: Malformed config opt
option encountered. Dropping.
Origin: s:d.
A malformed LBMC header was re-
ceived.
Check the originating IP and port
for an application sending incor-
rectly formed packets.
Core-6340-4: Malformed config opt
option encountered. Dropping.
Origin: s:d.
A malformed LBMC header was re-
ceived.
Check the originating IP and port
for an application sending incor-
rectly formed packets.
Core-6361-125: received sri re-
quest for unknown source.
A context without a resolver module
has received an SRI REQ.
This could be caused if a transport
thread's is reusing a previous con-
text's request port
Core-6361-126: received sri
request for unknown source -
transport_idx:topic_idx [u:u]
The context has handled an S←-
RI request for an unknown source.
This is not a serious problem but
indicates that there is a mismatch
between this process and another.
This is typically caused by a U←-
MP receiver attempting to join a
transport for a UMP source that has
been deleted.
This can happen under normal sit-
uations and should cease after sri
request configuration. If they don't,
check the system for other abnor-
mal behavior (applications restart-
ing etc)
Core-6361-127: LBMC CNTL SRI
REQ header size incorrect. Drop-
ping. Origin: s:d.
Source Registration Information
Request message header contains
incorrect size.
Check source (IP:Port) for possible
version mismatch or service attack.
Core-6361-128: LBMC CNTL S←-
RI header size incorrect. Dropping.
Origin: s:d.
Source Registration Information
message header contains incorrect
size.
Check source (IP:Port) for possible
version mismatch or service attack.
Core-6361-129: LBMC CNTL UME
store domain header size incorrect.
Dropping. Origin: s:d.
Store Domain message header
contains incorrect size.
Check source (IP:Port) for possible
version mismatch or service attack.
Core-6361-130: LBMR Topic Info
Record EXFUNC Option not cor-
rect size. Dropping remainder.
UM encountered a mismatch in
the length of a received message
and its headers, determining the
rest of the message to be invalid.
The remainder of the message is
dropped.
Contact Informatica support if this
message occurs frequently.
Core-6361-2: Topic Advertisement
[s] contains EXFUNC Info from s
but port is set to zero. Ignoring in-
valid EXFUNC Info.
A Topic Advertisement was re-
ceived with EXFUNC Information
but the source port was zero. The
EXFUNC Information is being ig-
nored.
This occurs when the Source dis-
ables binding of the request port.
See request_tcp_bind_request_←-
port configuration option.
Core-6361-3: late join available,
but no OTID present
UM has encountered a source with
late join enabled, but that has no
OTID. This is likely caused by a ver-
sion mismatch with an old version
of UM.
Resolve the version mismatch.
120 UM Log Messages
Core-6361-4: OTID version mis-
match - unable to provide late join
UM has encountered a source with
a mismatched OTID version. This
is likely caused by a UM version
mismatch.
Resolve the version mismatch.
Core-6420-10: LBMC header
data too long, dropping message.
Origin: s:d
Parsing data past the end of the
valid buffer.
Check the received message for
possible wrong format or service
attack.
Core-6420-11: LBMC header data
too long. Dropping. Origin: s:d.
Parsing data past the end of the
valid buffer
Check the received control mes-
sage for possible wrong format or
service attack.
Core-6420-12: LBMC basic header
too short. Dropping. Origin: s:d.
Message header is less than the
minimum size of LBMC header
Check the data being parsed for
possbile wrong formats or service
attack.
Core-6420-13: LBMC header data
too long. Dropping. Origin: s:d.
Parsing data past the end of the
valid buffer.
Check the received message for
possible wrong format or service
attack.
Core-6452-0: LBMC tid header
size incorrect. Dropping. Origin←-
: s:d.
The size of the TID header is incor-
rect.
This is an internal error.
Core-6488-1: WARNING: UMQ
queue "%s" context reg ID 0xx,
session ID 0xx queue state ignored
The source application context has
a higher last-sent timestamp than
the queue reports at registration;
this usually means the queue
missed a few messages the source
sent either by being down or being
too busy, etc., and is behind when
the source application re-registers.
Check to see if the queue has failed
or been restarted during operation,
or if it is being reported as inactive
for periods of time due to network
problems, etc.
Core-6675-1: non-UMQ context re-
ceived unicast UMQ message.
A context received a UMQ mes-
sage (unicast immediate message
or control message), but was not a
UMQ context. This is not a serious
problem and normally indicates a
non-UMQ context has re-used a re-
quest port recently held by a UMQ
context.
Check for frequent application
restarts or other behavior that
could cause ports to be re-used
between different types of applica-
tions.
Core-6720-1: IPC Error: Creating
Receiver Monitor Mutex (d) (s)
An IPC receiver could not create
a shared monitoring Mutex. This
could be caused by a permission
error or the resource already exists.
Please refer to the OS error num-
ber and resource name given.
Core-6758-1: LBMC dropping
packet containing deprecated
PSER header. Origin: s:d
A packet containing a UME proxy
source election record (PSER) was
dropped because their use has
been deprecated.
This indicates umestored pro-
cesses of an older version are
attempting to elect a proxy source
on this topic resolution domain.
Core-6758-2: LBMC proxy election
token header size incorrect. Drop-
ping. Origin: s:d.
An LBMC proxy source election to-
ken was received from the spec-
ified Origin that contained the
wrong length. The entire packet
was dropped.
This is caused by malformed or
forged packets. Use the Origin to
detect where they are coming from
to investigate further.
Core-6758-3: LBMR dropping
packet containing deprecated
proxy source election header.
Origin: s:d
LBM resolver has dropped a depre-
cated proxy source election packet.
Reported only once per resolver.
Indicates previous versions of the
UME store hosting proxy elections
on the shared topic resolution ad-
dress, a possible misconfiguration.
9.1 UM Core Messages 121
Core-6759-10: Updated destina-
tion for remote context name 's'.
New destination: DomainID u addr
s:d
An informational message indicat-
ing an updated destination has
been detected for a context name
used by this application.
This message is issued every time
a named context (E.g. a UMP store
daemon) changes the DomainID,
IP, and port for which it resolves
to. Repeated occurances of this
log message for the same con-
text name may indicate that multi-
ple contexts are assigned the same
name and active at the same time,
which is a mis-configuration. If this
occurs, please ensure that context
name usage is unique across all
UM topic resolution domains.
Core-6759-11: Duplicate context
name 's' detected. Origin←-
: DomainID u addr s:d
A named context has detected an-
other context advertising the same
name.
Advertised context names (E.←-
g. store names) must be unique
across topic resolution domains.
Check the configuration to ensure
only one store or named context
with a given name is operational at
any given time. The UM DomainID,
IP address, and port of the adver-
tised duplicate context name are
given.
Core-6759-1: LBMR RCTXIN←-
FO packet malformed. Dropping.
Origin: s:d
An LBMR packet was droppped be-
cause it could not be parsed.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-6759-2: LBMR RCTXINFO
len malformed. Dropping. Origin:
s:d
An LBMR packet was droppped be-
cause it could not be parsed.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-6759-31: Error parsing LB←-
MR RCTXINFO header flags x. Ig-
noring. Origin: s:d
An LBMR RCTXINFO packet
header was ignored because it
could not be parsed, or the appli-
cation failed to allocate memory.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-6759-3: LBMR RCTXINFO
rec len malformed. Dropping.
Origin: s:d
An LBMR packet was droppped be-
cause it could not be parsed.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-6759-4: LBMR RCTXINFO
address opt malformed. Dropping.
Origin: s:d
An LBMR packet was droppped be-
cause it could not be parsed.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-6759-5: LBMR RCTXINFO
instance opt malformed. Dropping.
Origin: s:d
An LBMR packet was droppped be-
cause it could not be parsed.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-6759-6: LBMR RCTXINFO
odomain opt malformed. Dropping.
Origin: s:d
An LBMR packet was droppped be-
cause it could not be parsed.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-6759-7: LBMR RCTXINFO
name opt malformed. Dropping.
Origin: s:d
An LBMR packet was droppped be-
cause it could not be parsed.
Investigate the listed IP and port for
an application generating spurious
traffic.
Core-6759-8: LBMR RCTXINFO
unknown opt 0x%02x. Dropping.
Origin: s:d
An LBMR packet was droppped be-
cause it could not be parsed.
Investigate the listed IP and port for
an application generating spurious
traffic.
122 UM Log Messages
Core-6759-9: Updated destination
for remote context name 's'. New
destination: DomainID u addr s:d
An informational message indicat-
ing an updated destination has
been detected for a context name
used by this application.
This message is issued every time
a named context (E.g. a UMP store
daemon) changes the DomainID,
IP, and port for which it resolves
to. Repeated occurances of this
log message for the same con-
text name may indicate that multi-
ple contexts are assigned the same
name and active at the same time,
which is a mis-configuration. If this
occurs, please ensure that context
name usage is unique across all
UM topic resolution domains.
Core-6837-1: LBMC Route Info
header size incorrect. Dropping.
Origin: s:d.
Route Info message header con-
tains incorrect size.
Check source (IP:Port) for possible
version mismatch or service attack.
Core-6856-0001: LBMC CNTL U←-
ME EXT store header size incor-
rect. Dropping. Origin: s:d.
Header length for a data type←-
: lbmc_cntl_ume_store_ext_hdr_←-
t is not right
The packet might have been cor-
rupted. Please contact customer
support
Core-6937-10: LBMC CNTL TCP
SID header size incorrect. Drop-
ping. Origin: s:d.
An LBMC Session ID control mes-
sage for a TCP transport is the
wrong size.
The IP address and port indicate
the source of the erroneous traffic.
Core-6937-30: FD Register error
when sending of Session ID; vali-
dation skipped (p)(0xx).
FD Register error when send-
ing TCP Session ID to source
for validation (transport_tcp_use←-
_session_id enabled).
There is no immediate action. Val-
idation is not required. If the error
persists, however, check the sys-
tem socket defaults.
Core-6937-31: Buffer allocation
failure when sending Session ID
(p)(0xx).
Buffer allocation error when send-
ing TCP Session ID to source
for validation (transport_tcp_use←-
_session_id enabled).
A buffer allocation error usually is a
symptom of running out of memory.
Core-6937-32: Topic Receiver sent
message data on TCP connection.
Ignoring. Origin: s:d
A TCP source received a data mes-
sage from a client. This was unex-
pected.
Refer to the clients IP:Port for the
source of the message
Core-6937-33: Topic Receiver sent
invalid control message on TCP
connection. Ignoring. Origin: s:d
A TCP source received a control
message from a client that did not
contain the expected information.
Refer to the clients IP:Port for the
source of the message
Core-6938-1: Notice from src (R←-
ID:u: (s)): store u:s:u reports it has
not received SRI (but might have
received TIR). Possible misconfig-
uration?
The UMP store has not yet re-
ceived an SRI from this source,
though it might have received a
TIR. UMP registration sometimes
occurs faster than topic resolution.
This warning might occur during a
store failover. This warning can
also occur if the store is not con-
figured to listen to the correct topic
resolution channel.
If this warning persists, check the
source initial delay and store con-
figuration options.
Core-6959-1: INFO: Receiver on
topic "%s" has its use_late_join op-
tion disabled but has a persistent
source on transport s. To opt out of
Late Join when subscribing to per-
sistent sources, the ume_use_←-
store option also must be disabled.
Enabling use_late_join.
Receiver disabled late join with U←-
MP.
Disabling late join with UMP is not
allowed, so enable late join or dis-
able ume_use_store to avoid this
INFO message.
9.1 UM Core Messages 123
Core-6974-1: LBMC CTXINS←-
TS header received without corre-
sponding UME_STORE or UME←-
_STORE_EXT header. Dropping.
Origin: s:d.
A malformed LBMC packet was re-
ceived.
Check the originating IP and port
for applications sending malformed
data.
Core-6974-2: LBMC STORENA←-
ME header received without corre-
sponding UME_STORE or UME←-
_STORE_EXT header. Dropping.
Origin: s:d.
A malformed LBMC packet was re-
ceived.
Check the originating IP and port
for applications sending malformed
data.
Core-6976-103: WARNING: L←-
BT-SMX session exists and uses
a different transport_lbtsmx←-
_datagram_max_size [d] than
requested [d].
Once a source has created a
transport session a subsequent
source joining the same transport
session cannot configure a differ-
ent transport_lbtsmx_datagram_←-
max_size setting. Please refer to
UMS Objects section of the Design
Concepts in the documentation.
Core-6976-104: WARNING: LB←-
T-SMX session exists and uses
a different transport_lbtsmx_sm_←-
interval [d] than requested [d].
Once a source has created a
transport session a subsequent
source joining the same transport
session cannot configure a dif-
ferent transport_lbtipc_sm_interval
setting. Please refer to UMS Ob-
jects section of the Design Con-
cepts in the documentation.
Core-6976-105: WARNING: L←-
BT-SMX session exists and uses
a different transport_lbtsmx_←-
transmission_window_size [d] than
requested [d].
Once a source has created a
transport session a subsequent
source joining the same trans-
port session cannot configure
a different transport_lbtsmx_←-
transmission_window_size setting.
Please refer to UMS Objects sec-
tion of the Design Concepts in the
documentation.
Core-6976-106: WARNING: L←-
BT-SMX session exists and uses
a different transport_lbtsmx_←-
maximum_receivers_per_transport
[d] than requested [d].
Once a source has created a trans-
port session a subsequent source
joining the same transport ses-
sion cannot configure a different
transport_lbtsmx_maximum_←-
receivers_per_transport setting.
Please refer to UMS Objects sec-
tion of the Design Concepts in the
documentation.
Core-6976-10: NOTICE: LBT-SMX
transport does not support adap-
tive batching; option will be ig-
nored.
The LBT-SMX transport does not
support adaptive batching, but the
user configured the source to use
adaptive batching.
Do not configure an LBT-SMX
source to use adaptive batching.
Core-6976-114: LBT-SMX Error←-
: Joining transport; no more free
receiver slots
The application tried joining a
source's LBT-SMX transport ses-
sion, but could not because no free
receiver slots were available.
Check the transport_lbtsmx_←-
maximum_receivers_per_transport
config option setting on the source
to see if it's large enough for the
intended number of receivers. Also
check for hung receiver clients.
124 UM Log Messages
Core-6976-117: LBTSMX receiver
thread dropping receiver add with
no matching transport
The LBT-SMX control source en-
queued an add of a new receiver
or receiver callback, but the LBT-←-
SMX receiver thread has no knowl-
edge of the transport the receiver
is supposed to be added too; ei-
ther the transport was never cor-
rectly added or it was removed.
Core-6976-118: LBTSMX receiver
thread dropping receiver remove
with no matching transport
The LBT-SMX control source en-
queued a delete of a receiver or
receiver callback, but the LBT-S←-
MX receiver thread has no knowl-
edge of the transport the receiver
is supposed to be removed from;
either the transport was never cor-
rectly added or it was already re-
moved.
Core-6976-11: NOTICE: con-
figured transport_lbtsmx_←-
transmission_window_size (u
bytes) is not large enough to
support at least two datagrams of
the configured transport_lbtsmx←-
_datagram_max_size (u bytes).
Transmission window size will be
rounded up to u bytes.
The configured LBT-SMX trans-
mission window size is not large
enough to accommodate the con-
figured the max datagram size. We
are automatically bumping up the
transmission window size from the
configured size so that it is large
enough.
The user should simply config-
ure their datagram max size and
transmission window sizes appro-
priately; the transmission window
size must be a power of 2, and it
must be at least twice the config-
ured max datagram size.
Core-6976-120: LBT-SMX receiver
thread received unknown message
type 'u' from transport LBTSMX←-
_x_u. Further unknown message
types received from this transport
will not be reported.
The LBT-SMX receiver thread re-
ceived a message type it does not
understand.
Check for thread safety issues
in the application with LBT-SMX-
related API calls.
Core-6976-121: LBT-SMX receiver
thread callback returned d
An internal LBT-SMX control call-
back function failed.
Something has likely gone terribly
wrong; memory corruption, etc.
Core-6976-122: LBT-SMX: locking
problem detected in lbtsmx_txw_←-
rcvr_node_alloc (d)
An error occurred with the shared
object used to ensure mutual exclu-
sion when accessing SMX shared
resources. Please refer to the OS
error number given.
Core-6976-123: LBT-SMX: locking
problem detected in lbtsmx_txw_←-
rcvr_node_alloc (d)
An error occurred with the shared
object used to ensure mutual exclu-
sion when accessing SMX shared
resources. Please refer to the OS
error number given.
Core-6976-124: LBT-SMX: locking
problem detected in lbtsmx_txw_←-
lock_rcvr_nodes (d)
An error occurred with the shared
object used to ensure mutual exclu-
sion when accessing SMX shared
resources. Please refer to the OS
error number given.
Core-6976-125: LBT-SMX: locking
problem detected in lbtsmx_txw_←-
lock_rcvr_nodes (d)
An error occurred with the shared
object used to ensure mutual exclu-
sion when accessing SMX shared
resources. Please refer to the OS
error number given.
9.1 UM Core Messages 125
Core-6976-126: LBT-SMX: failed to
open shared memory (d)
The SMX shared memory region
could not be opened for read-
ing. This could occur if a re-
ceiver attempts to join an SMX
transport after the source has been
deleted. Please reference the OS
error number given.
Core-6976-127: LBT-SMX: failed to
map shared memory (d)
An error occurred trying to map a
pointer to the SMX shared memory
region. Please refer to the OS error
number given.
Core-6976-128: LBT-SMX: Trans-
port Version Mismatch: Joining 0xx
from version 0xx
The SMX shared memory region's
version does not match our own; ei-
ther the shared memory is corrupt
or is not a version of LBT-SMX that
we understand (it may be a newer
or older version).
If different versions of the LBT-SMX
transport have been used on the
same machine, run their respective
lbtsmx_resource_manager tools to
reclaim and delete shared memory
resources. Do not mix versions of
LBT-SMX on the same machine.
Core-6976-129: LBT-SMX: failed to
map shared memory (d)
An error occurred trying to map a
pointer to the SMX shared memory
region. Please refer to the OS error
number given.
Core-6976-12: lbm_transport_←-
lbtsmx_ctlr_delete: WFSO res=d,
GLE=d
The WaitForSingleObject() Win-
dows call return an error while wait-
ing for the SMX Receiver thread to
exit. Refer to the response and OS
error number given.
Core-6976-130: LBT-SMX: can not
open shared semaphore (d)
The shared semaphore used to
ensure mutual exclusion while ac-
cessing SMX shared resources
could not be opened. This could
occur if a receiver attempts to join
an SMX transport after the source
has been deleted. Please refer to
the OS error number given.
Core-6976-131: LBT-SMX: failed to
open shared memory (d)
The SMX shared memory region
could not be opened for read-
ing. This could occur if a re-
ceiver attempts to join an SMX
transport after the source has been
deleted. Please reference the OS
error number given.
Core-6976-132: LBT-SMX: failed to
map shared memory (d)
An error occurred trying to map a
pointer to the SMX shared memory
region. Please refer to the OS error
number given.
Core-6976-133: LBT-SMX: Trans-
port Version Mismatch: Joining 0xx
from version 0xx
The SMX shared memory region's
version does not match our own; ei-
ther the shared memory is corrupt
or is not a version of LBT-SMX that
we understand (it may be a newer
or older version).
If different versions of the LBT-SMX
transport have been used on the
same machine, run their respective
lbtsmx_resource_manager tools to
reclaim and delete shared memory
resources. Do not mix versions of
LBT-SMX on the same machine.
Core-6976-134: LBT-SMX: failed to
map shared memory (d)
An error occurred trying to map a
pointer to the SMX shared memory
region. Please refer to the OS error
number given.
126 UM Log Messages
Core-6976-135: LBT-SMX: can not
open shared Mutex (d)
An error occurred trying to open
the mutex that protects the LBT-←-
SMX shared memory region - see
the OS error code for more informa-
tion.
Core-6976-136: LBT-SMX Error←-
: Getting Receiver Monitor Mutex
(d)
The LBT-SMX monitor thread could
not acquire the shared monitoring
Mutex. This could be caused by a
permission error. Refer to the OS
error number and resource name
given.
Core-6976-137: SMX Error: Creat-
ing Receiver Monitor Mutex (d) (s)
An SMX receiver could not create
a shared monitoring Mutex. This
could be caused by a permission
error or the resource already exists.
Refer to the OS error number and
resource name given.
Core-6976-138: SMX Error: Creat-
ing Receiver Monitor Mutex (d) (s)
An SMX receiver could not create
a shared monitoring Mutex. This
could be caused by a permission
error or the resource already exists.
Refer to the OS error number and
resource name given.
Core-6976-139: Error: Creating
Receiver Thread (d)
An error occurred when the re-
ceiver attempted to create a thread
for internal processing. Refer to the
OS error number given.
Core-6976-13: LBTSMX: error in
sizing resource registry (d)
An error occurred when attempting
to set shared memory registry file
to the correct size. The registry is
used to store SMX shared objects
that are in use. The OS error num-
ber is given.
Core-6976-140: LBT-SMX Error←-
: Joining transport; no more free
receiver slots
An SMX receiver is attempting to
join an SMX transport that has no
more free slots for receivers.
Adjust the "transport_lbtsmx←-
_maximum_receivers_per_←-
transport" configuration attribute.
Core-6976-141: default thread
stack size is perhaps too small, u
bytes.
The LBT-SMX receiver has created
a thread for internal processing and
the default stack size is too small.
The size of the default stack size is
dumped and will then be set to a
larger size automatically.
Core-6976-142: reset thread stack
size to u bytes.
The SMX receiver has created a
thread for internal processing and
the default stack size is too small
and is reallocated. This message
reports the new size of the stack.
Core-6976-143: Error: Creating
Receiver Thread (d)
An error occurred when the S←-
MX receiver attempted to create a
thread for internal processing. Re-
fer to the OS error number given.
Core-6976-144: LBT-SMX Error←-
: Joining transport; no more free
receiver slots
An SMX receiver is attempting to
join an SMX transport that has no
more free slots for receivers.
Adjust the "transport_lbtsmx←-
_maximum_receivers_per_←-
transport" configuration attribute.
9.1 UM Core Messages 127
Core-6976-145: SMX Error: Creat-
ing Receiver Monitor Semaphore
An error occurred when an S←-
MX receiver attempted to allocate
a shared monitoring semaphore.
This could be caused by a permis-
sion error or no more resources.
Refer to the documentation for
lbtsmx_resource_manager.
Core-6976-146: SMX Error: Initial-
izing Receiver Monitor Semaphore
(d)
An error occurred when an SMX
receiver attempted to initialize a
shared monitoring semaphore. Re-
fer to the OS error number given.
Core-6976-147: SMX Error: Initial-
izing Receiver Monitor Semaphore
(d)
An error occurred when an SMX
receiver attempted to initialize a
shared monitoring semaphore. Re-
fer to the OS error number given.
Core-6976-148: LBT-SMX Problem
Opening Signal Semaphore (d)
The SMX source has received a
connection request from an SMX
receiver and has failed to open the
shared signaling semaphore. This
could happen if the connection re-
quest is old and the receiver was
already deleted or the source does
not have permission to open the
object. Please reference the OS er-
ror number given.
Core-6976-149: LBT-SMX Problem
Opening Event (d)
The SMX source has received a
connection request from an SMX
receiver and has failed to open the
shared Event. This could happen
if the connection request is old and
the receiver was already deleted or
the source does not have permis-
sion to open the object. Please ref-
erence the OS error number given.
Core-6976-14: LBTSMX: error
mapping (initial) resource registry
(d)
An error occurred when attempting
to map memory to the registry file.
The registry is used to store SMX
shared objects that are in use. The
OS error number is given.
Core-6976-150: LBT-SMX Problem
Opening Monitor Semaphore (d)
The SMX source has received a
connection request from an SMX
receiver but has failed to open the
Monitoring Semaphore. This could
happen if the connection request
is old and the receiver was al-
ready deleted or the source does
not have permission to open the
object. Please reference the OS er-
ror number given.
128 UM Log Messages
Core-6976-151: LBT-SMX Problem
Opening Monitor Mutex (d) (s)
The SMX source has received a
connection request from an SMX
receiver but has failed to open the
Monitoring Mutex. This could hap-
pen if the connection request is
old and the receiver was already
deleted or the source does not
have permission to open the ob-
ject. Please reference the OS error
number and object name given.
Core-6976-15: LBTSMX: error cre-
ating registry semaphore (d)
The semaphore used to ensure
mutual exclusion while accessing
the registry could not be initial-
ized. The registry is used to store
SMX shared objects that are in
use. Refer to the documentation for
lbtsmx_resource_manager.
Core-6976-160: lbm_transport_←-
lbtsmx_ctlr_delete: WFSO res=d,
GLE=d
The WaitForSingleObject() Win-
dows call return an error while wait-
ing for the SMX Receiver thread to
exit. Refer to the response and OS
error number given.
Core-6976-161: Could not cre-
ate LBT-SMX control source; will
not be able to join any LBT-S←-
MX transports. Check permissions
and reclaim any stale LBT-SMX re-
sources.
The LBT-SMX internal control
source could not be created; this
probably means the user doesn't
have permissions to create shared
mutexes or semaphores, or we
have run out of memory, or we
have run out of our allowed number
of semaphores.
Try running lbtsmx_resource←-
_manager -reclaim to get rid of
stale shared resources, and check
permissions of the application to
see if it is allowed to create shared
mutexes, etc.
Core-6976-162: lbm_lbtsmx_←-
block_wait failed
Waiting for the LBT-SMX receiver
thread to complete an action failed;
the receiver thread may or may not
have completed the action. The ap-
plication may potentially now be in
an unstable state. This may be due
to being out of memory or out of
available semaphores.
Contact Informatica support.
Core-6976-163: lbm_lbtsmx_←-
block_wait failed
Waiting for the LBT-SMX receiver
thread to complete an action failed;
the receiver thread may or may not
have completed the action. The
application may potentially now be
in an unstable state. This is usu-
ally due to being out of memory
or out of available semaphores and
should normally not happen.
Contact Informatica support.
Core-6976-164: lbm_lbtsmx_←-
block_wait failed
Waiting for the LBT-SMX receiver
thread to complete an action failed;
the receiver thread may or may not
have completed the action. The
application may potentially now be
in an unstable state. This is usu-
ally due to being out of memory
or out of available semaphores and
should normally not happen.
Contact Informatica support.
9.1 UM Core Messages 129
Core-6976-165: lbm_lbtsmx_←-
block_wait failed
Waiting for the LBT-SMX receiver
thread to complete an action failed;
the receiver thread may or may not
have completed the action. The
application may potentially now be
in an unstable state. This is usu-
ally due to being out of memory
or out of available semaphores and
should normally not happen.
Contact Informatica support.
Core-6976-166: lbm_lbtsmx_←-
block_wait failed
Waiting for the LBT-SMX receiver
thread to complete an action failed;
the receiver thread may or may not
have completed the action. The
application may potentially now be
in an unstable state. This is usu-
ally due to being out of memory
or out of available semaphores and
should normally not happen.
Contact Informatica support.
Core-6976-167: lbm_lbtsmx_←-
block_wait failed
Waiting for the LBT-SMX receiver
thread to complete an action failed;
the receiver thread may or may not
have completed the action. The
application may potentially now be
in an unstable state. This is usu-
ally due to being out of memory
or out of available semaphores and
should normally not happen.
Contact Informatica support.
Core-6976-16: LBTSMX: error ini-
tializing registry semaphore (d)
The semaphore used to ensure
mutual exclusion while accessing
the registry could not be initial-
ized. The registry is used to store
SMX shared objects that are in
use. Refer to the documentation for
lbtsmx_resource_manager.
Core-6976-17: LBTSMX: error
opening resource registry (d)
An error occurred when attempting
to open or map memory to the reg-
istry file. The OS error number is
given.
Core-6976-18: LBTSMX: error
mapping resource registry (d)
An error occurred when attempting
to open or map memory to the reg-
istry file. The OS error number is
given.
Core-6976-19: LBTSMX: resource
registry version mismatch: use
lbtsmx_resource_manager to
clean-up and delete registry.
An SMX registry file existed, and
contained the wrong version.
For this to happen, a registry file
with incorrect version information
would have to be deliberately put in
place. 3.5 and post3.5 use differ-
ent naming schemes for registries,
so this can't happen due to version
mismatch.
Core-6976-20: LBTSMX: error
re-mapping resource registry
(entries: d) (d)
An error occurred when attempting
to re-map memory to the registry
file. The registry is used to store
SMX shared objects that are in use.
The size in entries and OS error
number is given.
130 UM Log Messages
Core-6976-21: LBTSMX: er-
ror opening/recreating registry
semaphore (d)
The semaphore used to ensure
mutual exclusion while accessing
the registry could not be created.
The registry is used to store SMX
shared objects that are in use. The
OS error number is given.
Core-6976-22: LBTSMX: error
reinitializing registry semaphore (d)
The semaphore used to ensure
mutual exclusion while accessing
the registry could not be initialized.
The registry is used to store SMX
shared objects that are in use. The
OS error number is given.
Core-6976-23: LBTSMX: error re-
creating resource registry (d)
The registry used to store SMX
shared objects that are in use could
not be created. The OS error num-
ber is given.
Core-6976-24: LBTSMX: error in
re-sizing resource registry (d)
The registry used to store SMX
shared objects that are in use could
not be re-sized (expanded). The
OS error number is given.
Core-6976-25: LBTSMX: error re-
mapping resource registry (d)
An error occurred when attempting
to re-map memory to the registry
file (file expansion). The registry is
used to store SMX shared objects
that are in use. The OS error num-
ber is given.
Core-6976-26: LBTSMX: No free
semaphores could be found
A free semaphore required for the
LBT-SMX transport could not be
found.
See the Ultra Messaging Configu-
ration Guide for information about
the lbtsmx_resource_manager op-
tion.
Core-6976-27: LBTSMX: error cre-
ating registry semaphore (d)
An error occurred when attempt-
ing to create the LBT-SMX registry
semaphore set. The OS error num-
ber is given.
Core-6976-28: LBTSMX: error
opening semaphore (d)
A free semaphore allocated for the
LBT-SMX transport could not be
opened. The OS error number is
given.
Core-6976-29: LBTSMX: error
freeing semaphore; key 0xx not
found
A semaphore allocated for the LB←-
T-SMX transport could not be freed
due to an invalid internal key.
Contact Informatica support.
Core-6976-32: specified
transport_lbtsmx_transmission_←-
window_size of u will be ignored in
favor of the next highest power of
two: u
LBT-SMX transmission window
size must be a power of 2; the user
specified a non-power-of-2 size.
Core-6976-6: NOTICE: LBT-SMX
transport does not support UMP;
option will be ignored.
The LBT-SMX transport does not
support UMP, but the user config-
ured the source as a UMP source.
Do not configure an LBT-SMX
source to use UMP.
Core-6976-7: NOTICE: LBT-SMX
transport does not support ULB;
option will be ignored.
The LBT-SMX transport does not
support ULB, but the user config-
ured the source as a ULB source.
Do not configure an LBT-SMX
source to use ULB.
9.1 UM Core Messages 131
Core-6976-84: an error occurred
while canceling source buffers -
possibly due to non thread-safe use
of lbm_src_buffs_cancel; LBT-SMX
shared memory may be in an in-
consistent state
The user probably called a series of
non-thread-safe buffer-based send
API functions concurrently.
Code testing for race conditions &
code inspection is advised.
Core-6976-8: NOTICE: LBT-SMX
transport does not support UMQ;
option will be ignored.
The LBT-SMX transport does not
support UMQ, but the user config-
ured the source as a UMQ source.
Do not configure an LBT-SMX
source to use UMQ.
Core-6976-9: NOTICE: LBT-SMX
transport does not support late join;
option will be ignored.
The LBT-SMX transport does not
support late join, but the user con-
figured the source to use late join.
Do not configure an LBT-SMX
source to use late join.
Core-7007-1: LBMC encountered
more than 2 Destination headers.
Origin: s:d.
Discovered too many duplicate L←-
BMC Destination headers in the
same packet. This should be
harmless, but indicates an error in
packet handling elsewhere.
Contact Informatica support.
Core-7007-2: LBMC encountered
more than 2 Stream headers.
Origin: s:d.
Discovered too many duplicate L←-
BMC Stream headers in the same
packet. This should be harmless,
but indicates an error in packet
handling elsewhere.
Contact Informatica support.
Core-7049-1: NOTICE: Initiating
proactive retransmissions for UME
source on topic "%s" starting at se-
quence number 0xx.
Proactive retransmissions are en-
abled and are being sent for a given
source.
This probably means either stability
ACKs from a store are not reach-
ing the source application or the
source's messages are not reach-
ing the store. In either case,
causes of loss or connectivity is-
sues in each direction between the
source and the store should be in-
vestigated.
Core-7144-1: WARNING: could
not set unicast SO_SNDBUF to re-
quested value u
An error was returned from the OS
while trying to set the socket op-
tion SO_SNDBUF. The requested
buffer size has not been set.
Core-7144-2: INFO: unicast rcv
could only get SO_SNDBUF u (de-
sired u)
An error was returned from the OS
while trying to set the socket op-
tion SO_SNDBUF. The buffer size
that was set is shown in the log
message. Typically the OS will al-
locate the requested value or its
configured maximum, whichever is
smaller.
Increase the maximum send buffer
size allowed by your OS. Refer to
the configuration guide for instruc-
tions about changing the OS limits.
Core-7275-1: INFO: received PR←-
EG RESP that was not a deregis-
tration response while the receiver
is in the deregistering state
A registration response message
that does not have the flag set
to deregister was received from
a store, but the source is in the
deregistration state.
Client deregistered before all
stores were fully registered with.
This is a benign issue because
messages could have crossed on
the wire
Core-7322-1: lbm_unicast_←-
message_buff() failed to reallocate
message buffer to include addi-
tional headers (p:p:p)
When sending a unicast message
buffer, a buffer could not be re-
allocated to include additional infor-
mation.
This is an LBM buffer create error.
This is likely due to running out of
memory.
Core-7421-1: Source Side Filtering
Init message with no return IP, us-
ing transport IP (s)
The request_tcp_interface param-
eter was not configured on the
source.
Configure the source to set
request_tcp_interface.
132 UM Log Messages
Core-7427-1: received TSNI re-
quest for unknown source[u] from
ip:port[s:d].
UMS received a TSNI request for
unknown source. This is not a
serious problem but indicates that
there is a mismatch between this
process and another.
Check the system for other abnor-
mal behavior, such as applications
restarting.
Core-7506-1: Delivery controller
forced loss due to exceeding
delivery_control_maximum_total←-
_map_entries.
The delivery controller forced loss,
because it exceeded the maximum
number of total map entries.
Core-7506-2: Delivery controller
forced loss during late join or
OTR due to exceeding delivery←-
_control_maximum_total_map_←-
entries.
The delivery controller forced loss
during late join or OTR, because it
exceeded the maximum number of
total map entries.
Core-7521-7: Could not close LBT-
SMX shared memory
Closing a shared transmission win-
dow failed; this likely indicates an
internal error and should really
never happen.
Core-7582-2: DRO does not al-
low the LBT-SMX source transport
to be configured; changing source
transport to TCP. Topic (s)
The DRO does not support the
LBT-SMX source transport. The
source transport will automatically
be changed to TCP.
The customer should use a differ-
ent source transport when the D←-
RO is configured. Please reconfig-
ure the source transport type.
Core-7699-2: Socket error setting
SO_EXCLUSIVEADDRUSE: s
An error was returned from the OS
while trying to set the SO_EXCL←-
USIVEADDRUSE (Windows Only)
option on a socket.
Refer to the OS error number and
message given to determine cause
of the failure.
Core-7725-1: WARNING: LBT-S←-
MX source "%s" matches HFX re-
ceiver on topic "%s", but HFX re-
ceivers are not supported for LB←-
T-SMX transports. Messages from
this source will not be delivered to
any HFX receivers.
The LBT-SMX transport does not
support HFX receivers, but the user
has created an HFX receiver on a
topic matching an SMX source.
Core-7839-10: Callback service
time stats for receiver topic "%s"
are disabled because s
Callback service time stats are
enabled for this context, however
this receiver will not be included
in those stats because an event
queue is in use or MTT is enabled.
If callback timing stats are not de-
sired for this receiver, this mes-
sage can be ignored. If stats are
desired and an event queue is in
use, the event queue service time
statistics can be used to monitor
the receiver callback time. Callback
service time stats are not currently
supported with MTT receivers.
Core-7839-11: Callback service
time stats for wildcard receiver pat-
tern "%s" are disabled because s
Callback service time stats are en-
abled for this context, however this
wildcard receiver will not be in-
cluded in those stats because an
event queue is in use or MTT is en-
abled.
If callback timing stats are not de-
sired for this wildcard receiver, this
message can be ignored. If stats
are desired and an event queue
is in use, the event queue ser-
vice time statistics can be used to
monitor the wildcard receiver call-
back time. Callback service time
stats are not currently supported
with MTT wildcard receivers.
9.1 UM Core Messages 133
Core-7839-12: Callback service
time stats for wildcard receiver pat-
tern "%s" are disabled because s
Callback service time stats are en-
abled for this context, however this
wildcard receiver will not be in-
cluded in those stats because an
event queue is in use or MTT is en-
abled.
If callback timing stats are not de-
sired for this wildcard receiver, this
message can be ignored. If stats
are desired and an event queue
is in use, the event queue ser-
vice time statistics can be used to
monitor the wildcard receiver call-
back time. Callback service time
stats are not currently supported
with MTT wildcard receivers.
Core-7839-17: [LBMMON] Format
module receiver topic deserialize
function returned d, s
A receiver topic statistics message
was unable to be parsed.
Contact Informatica support.
Core-7839-18: [LBMMON] Format
module wildcard receiver deserial-
ize function returned d, s
A wildcard receiver statistics mes-
sage was unable to be parsed.
Contact Informatica support.
Core-7839-31: failed to update
monitoring Domain ID
Monitoring failure: could not update
domain id.
This is an internal error and is usu-
ally caused by running out of mem-
ory.
Core-7839-33: failed to remove
source monitoring
Failure to unmonitor a source. This is an internal error and is usu-
ally caused by running out of mem-
ory.
Core-7839-34: [LBMMON] Error
d returned from transport module
send function, s
Failed to send a receiver topic
statistics packet.
Contact Informatica support.
Core-7839-35: [LBMMON] Error d
returned from format module re-
ceiver serialize function, s
Failed to format a receiver topic
statistics packet.
Contact Informatica support.
Core-7839-36: [LBMMON] Error
d returned from transport module
send function, s
Failed to send a wildcard receiver
statistics packet.
Contact Informatica support.
Core-7839-37: [LBMMON] Error d
returned from format module re-
ceiver serialize function, s
Failed to format a wildcard receiver
statistics packet.
Contact Informatica support.
Core-7839-8: Callback service
time stats for hot failover receiver
topic "%s" are disabled because s
Callback service time stats are en-
abled for this context, however this
hot failover receiver will not be in-
cluded in those stats because an
event queue is in use or MTT is en-
abled.
If callback timing stats are not de-
sired for this hot failover receiver,
this message can be ignored. If
stats are desired and an event
queue is in use, the event queue
service time statistics can be used
to monitor the receiver callback
time. Callback service time stats
are not currently supported with
MTT hot failover receivers.
Core-7839-9: Callback service
time stats for receiver topic "%s"
are disabled because s
Callback service time stats are
enabled for this context, however
this receiver will not be included
in those stats because an event
queue is in use or MTT is enabled.
If callback timing stats are not de-
sired for this receiver, this mes-
sage can be ignored. If stats are
desired and an event queue is in
use, the event queue service time
statistics can be used to monitor
the receiver callback time. Callback
service time stats are not currently
supported with MTT receivers.
134 UM Log Messages
Core-7911-1: Onload extensions
API has been dynamically loaded
The Onload library (libonload.so)
was found in the library path and
has been loaded. This library is
required to selectively accelerate
transport sockets via onload_set←-
_stackname.
If you do not wish to use this fea-
ture or automatically load the li-
brary, export LBM_SUPPRESS_←-
ONLOAD=1.
Core-7911-2: [errno:d] Error calling
onload_set_stackname
There was an error setting the on-
load stack name.
Refer to the Solarflare Onload
documentation for onload_set_←-
stackname with the given errno.
Core-7911-3: Attempting to set On-
load Stackname, but Onload is not
available
A source or receiver has set
onload_acceleration_stack_←-
name but the Onload library was
not dynamically loaded by Ultra
Messaging.
If you don't want onload ac-
celeration, ensure that onload_←-
acceleration_stack_name is NU←-
LL. If you do, ensure that the en-
vrionment variable LBM_SUPPR←-
ESS_ONLOAD is unset and that
the Onload library is in your library
path.
Core-8034-1: [LBMMON] Dropping
monitoring message that is larger
than the maximum allowed size of
d (size=d)
The monitoring message received
is larger than the maximum allowed
size given.
This is a hard coded maximum.
Core-8034-2: [LBMMON] Dropping
monitoring message that is larger
than the maximum allowed size of
d (size=d)
The monitoring message received
is larger than the maximum allowed
size given.
This is a hard coded maximum.
Core-8034-3: [LBMMON] Dropping
monitoring message that is larger
than the maximum allowed size of
d (size=d)
The monitoring message received
is larger than the maximum allowed
size given.
This is a hard coded maximum.
Core-8192-4: WARNING: UME
non-blocking receiver "%s" RegID
u attempted to register with a store
that does not support non-blocking
receivers; receiver was converted
to a blocking receiver registration.
The attempt to register with the
store as a non-blocking receiver
was converted to a blocking re-
ceiver registration.
Upgrade the store to a post 6.8 re-
lease.
Core-8243-10: unknown message
type (d) present in message bundle
An unhandled message type was
placed in a message bundle for de-
livery; this is an internal error that
indicates a serious problem.
Contact Informatica support.
Core-8243-12: message receiver
function returned -1
The user's receiver callback re-
turned -1, indicating an error.
User should check their receiver
callback for possible error returns.
Core-8243-13: rcv batching call-
back returned error u [s]
An error ocurred while processing
a batch of messages. This may be
due to an out-of-memory condition.
Contact Informatica support.
Core-8243-15: Multi-threaded
transports (MTT) are not currently
compatible with receive-side batch-
ing; receive-side batching will be
disabled for receivers configured to
use MTT.
The user configured both MTT and
receive-side batching, which do not
currently work together.
Do not enable both MTT and
receive-side batching for the same
receiver.
Core-8243-16: unknown message
type (d) present in message bundle
An unhandled message type was
placed in a message bundle for de-
livery; this is an internal error that
should not happen and indicates a
serious problem.
Contact Informatica support.
9.1 UM Core Messages 135
Core-8243-17: rcv batching event
queue enqueue returned error u [s]
An error ocurred while enqueueing
a batch of messages. This may be
due to an out-of-memory condition.
Contact Informatica support.
Core-8243-18: lbm_context_←-
deliver_waiting_bundles returned
error u [s]
Internal handling of message bun-
dles failed. This indicates a severe
problem (out of memory, etc.).
Contact Informatica support.
Core-8243-19: lbm_context_←-
deliver_waiting_bundles returned
error u [s]
Internal handling of message bun-
dles failed. This indicates a severe
problem (out of memory, etc.).
Contact Informatica support.
Core-8243-20: lbm_context_←-
deliver_waiting_bundles returned
error u [s]
Internal handling of message bun-
dles failed. This likely indicates
a severe problem (out of memory,
etc.).
Contact Informatica support.
Core-8243-21: lbm_context_←-
deliver_waiting_bundles returned
error u [s]
Internal handling of message bun-
dles failed. This likely indicates
a severe problem (out of memory,
etc.).
Contact Informatica support.
Core-8243-22: lbm_context_←-
deliver_waiting_bundles returned
error u [s]
Internal handling of message bun-
dles failed. This likely indicates
a severe problem (out of memory,
etc.).
Contact Informatica support.
Core-8243-23: rcv batching event
queue enqueue returned error u [s]
An error ocurred while enqueueing
a batch of messages. This may be
due to an out-of-memory condition.
Contact Informatica support.
Core-8243-40: semaphore_←-
timedwait failure
Waiting on a queue size
semaphore failed; this proba-
bly means the size is incorrect.
Contact Informatica support.
Core-8243-9: message receiver
function returned -1
The user's receiver callback re-
turned -1, indicating an error.
User should check their receiver
callback for possible error returns.
Core-8321-1: lbm_context_←-
deliver_waiting_bundles returned
error u [s]
Internal handling of message bun-
dles failed. This indicates a severe
problem (out of memory, etc.).
Contact Informatica support.
Core-8321-2: lbm_context_←-
deliver_waiting_bundles returned
error u [s]
Internal handling of message bun-
dles failed. This indicates a severe
problem (out of memory, etc.).
Contact Informatica support.
Core-8321-3: lbm_context_←-
deliver_waiting_bundles returned
error u [s]
Internal handling of message bun-
dles failed. This indicates a severe
problem (out of memory, etc.).
Contact Informatica support.
Core-8321-4: lbm_context_←-
deliver_waiting_bundles returned
error u [s]
Internal handling of message bun-
dles failed. This indicates a severe
problem (out of memory, etc.).
Contact Informatica support.
Core-8342-1: HFX receivers are
not currently compatible with
receive-side batching; receive-side
batching will be disabled for all
HFX receivers.
The user is creating an HFX re-
ceiver with receive-side batching
turned on, which is not currently
supported.
This is not really an error; if
the user doesn't need receive-side
batching for non-HFX receivers,
suggest turning it off.
Core-8562-1: INFO: could not set
SO_SNDBUF u for UDP socket
The desired socket send buffer
could not be set on a UDP socket.
Check configured system limits or
permissions to make sure the re-
quest socket buffer size is allowed.
Core-8562-2: INFO: could not set
SO_SNDBUF u for UDP socket
The desired socket send buffer
could not be set on a UDP socket.
Check configured system limits or
permissions to make sure the re-
quest socket buffer size is allowed.
Core-8562-3: could not set SO_←-
SNDBUF u for UDP socket
The desired socket send buffer
could not be set on a UDP socket.
Check configured system limits or
permissions to make sure the re-
quest socket buffer size is allowed.
136 UM Log Messages
Core-8576-1: Reducing otr_←-
message_caching_threshold [u] to
ume_application_outstanding_←-
maximum [u] for topic [s]
The OTR message caching thresh-
old cannot be higher than the
configured "ume_application_←-
outstanding_maximum".
Update the configuration (either
increase ume_application_←-
outstanding_maximum or de-
crease otr_message_caching_←-
threshold so that otr_message←-
_caching_threshold <= ume←-
_application_outstanding_←-
maximum.
Core-8576-2: Throttled recovery is
requested but OTR is disabled for
topic [s]. Only initial recovery will
be throttled.
Throttled recovery only works for
receivers configured to use OTR.
Turn on OTR for the receiver, or
turn off throttled recovery.
Core-8576-3: OTR enabled and
otr message caching threshold is
less than cache proximity. Reduc-
ing retransmit_message_caching←-
_proximity [u] to half of otr_←-
message_caching_threshold [u] for
topic [s].
When OTR is enabled, cache prox-
imity must be set to a smaller value
than message caching threshold.
Set cache proximity less than mes-
sage caching threshold
Core-8781-1: late join info destina-
tion index u is invalid, dropping
A Late Join Info message with an
invalid destination index was re-
ceived for an outstanding rx re-
quest. This indicates that ports
may be re-used between applica-
tion restarts. It may also indicate
non-UM traffic is being directed at
UM applications.
Try disabling tcp reuseaddr and/or
segregating application request_←-
tcp_port ranges.
Core-8781-2: late join info low_←-
sqn u is invalid for loss rec sqn u,
dropping
A Late Join Info message with an
invalid sequence number was re-
ceived for an outstanding rx re-
quest. This indicates that ports
may be re-used between applica-
tion restarts. It may also indicate
non-UM traffic is being directed at
UM applications.
Try disabling request_tcp_←-
reuseaddr and/or segregating
application request_tcp_port
ranges.
Core-8787-1: WARNING: could
not set SO_KEEPALIVE on TCP
connection socket: s
SO_KEEPALIVE was requested on
the source end of TCP connection,
but was not able to be set on the
socket. This could be because the
OS is not Windows or Linux, or be-
cause there was an error in the OS
system call to set the socket op-
tions.
Core-8787-7: Source TCP activity
timeout set, but TCP keepalives are
not supported on this platform; op-
tion will have no effect.
The source's transport_tcp_←-
activity_interval option is set, but
SO_KEEPALIVE is not supported
on this OS.
Don't set the transport_tcp_←-
activity_interval option on this
OS.
Core-8787-8: Source TCP activ-
ity timeout set lower than minimum
supported value; increasing to u
milliseconds.
The source's configured
transport_tcp_activity_interval
option is lower than the minimum
supported value on this OS.
Set the TCP activity interval option
to a higher value.
Core-8840-3: Could not create au-
tomon controller: s
Automatic monitoring could not be
turned on for a context.
Check automatic monitoring con-
figuration for errors; if none are
found, contact support.
Core-8901-01: BROKER: Failed to
create a Proton library driver ob-
ject.
Error in creating Proton Driver. Call support.
9.1 UM Core Messages 137
Core-8901-02: BROKER: Failed to
create a Proton library connector
object (s:s).
Error in creating Proton Connector. Call support.
Core-8901-03: BROKER: Discon-
nect detected while establishing
broker connection (s:s).
A broker disconnect was detected. Make sure the broker is running.
If HA is used, a new active broker
should be elected.
Core-8901-04: BROKER: Security
failure (s:s).
Error in authorizing connection to
broker.
Check permissions.
Core-8901-05: BROKER: No an-
swer from broker (s:s).
Error in trying to connect to broker;
no answer.
Check to make sure the broker
daemon is running and that no er-
rors have been reported by the bro-
ker.
Core-8913-10: Explicit ACK fea-
ture is not supported, disabling
Explicit Ack feature is turned on Explicit Ack feature is not sup-
ported, and should be turned off.
Core-8913-1: NULL ptr [s:d] Null pointer detected Contact Informatica Support
Core-8913-8: INFO: Source "%s"
Late join set, but source is config-
ured as broker source. Turning off
late join.
Late Join is turned on for broker
source
Turn Off Late Join option
Core-8979-6: No activity from D←-
RO domain id u for u seconds, dis-
abling active domain id propagation
The DRO servicing the specified
domain id has not been heard from
for the given timeout, so the domain
id will no longer be propagated to
new applications in the Topic Res-
olution Domain.
Ensure all DROs are up and run-
ning and configured with the cor-
rect domain id for the Topic Reso-
lution Domain.
Core-8979-7: Detected activity
from DRO domain id u, enabling
active domain id propagation
The DRO servicing the specified
domain id has been heard from
again, so the domain id will be
propagated to new applications in
the Topic Resolution Domain.
Ensure all DROs are up and run-
ning and configured with the cor-
rect domain id for the Topic Reso-
lution Domain.
Core-9003-1: brokered contexts do
not batch consumption reports.
The user configured "umq_←-
delayed_consumption_report_←-
interval" which is not supported on
a brokered context.
The user should be informed of this
limitation and set the configuration
appropriately.
Core-9008-1: brokered contexts
do not allow the use of transport
threads, disabling
The user configured "use_←-
transport_thread" which is not
supported on a brokered context.
The user should be informed of this
limitation and set the configuration
appropriately.
Core-9012-01: BROKER: Encod-
ing error; vendor private format
found in message property: (s)
Customer has named a property
using the LBM internal format.
Support needs to advise against
using internal names. We will drop
them.
Core-9012-02: BROKER: Decod-
ing error; proton NULL type not
handled; dropping (s)
LBM received an unhandled proton
type.
The customer needs to assess the
usage of JMS.
Core-9012-03: BROKER: Decod-
ing error; proton TIMESTAMP type
not handled; dropping (s)
LBM received an unhandled proton
type.
The customer needs to assess the
usage of JMS.
Core-9012-04: BROKER: Decod-
ing error; proton DECIMAL128 type
not handled; dropping (s)
LBM received an unhandled proton
type.
The customer needs to assess the
usage of JMS.
Core-9012-05: BROKER: Decod-
ing error; proton UUID type not
handled; dropping (s)
LBM received an unhandled proton
type.
The customer needs to assess the
usage of JMS.
Core-9012-06: BROKER: Decod-
ing error; proton BINARY type not
handled; dropping (s)
LBM received an unhandled proton
type.
The customer needs to assess the
usage of JMS.
138 UM Log Messages
Core-9012-07: BROKER: Decod-
ing error; proton SYMBOL type not
handled; dropping (s)
LBM received an unhandled proton
type.
The customer needs to assess the
usage of JMS.
Core-9012-08: BROKER: Decod-
ing error; proton DESCRIBED type
not handled; dropping (s)
LBM received an unhandled proton
type.
The customer needs to assess the
usage of JMS.
Core-9012-09: BROKER: Decod-
ing error; proton ARRAY type not
handled; dropping (s)
LBM received an unhandled proton
type.
The customer needs to assess the
usage of JMS.
Core-9012-10: BROKER: Decod-
ing error; proton LIST type not han-
dled; dropping (s)
LBM received an unhandled proton
type.
The customer needs to assess the
usage of JMS.
Core-9012-11: BROKER: Decod-
ing error; proton MAP type not han-
dled; dropping (s)
LBM received an unhandled proton
type.
The customer needs to assess the
usage of JMS.
Core-9012-12: BROKER: Decod-
ing error; encountered Vendor spe-
cific property that is not understood
(s)
LBM received an unhandled proton
type.
The customer needs to assess the
usage of JMS.
Core-9012-13: BROKER: Decod-
ing error; encountered JMS prop-
erty that will not pass through (s)
LBM received an unhandled proton
type.
The customer needs to assess the
usage of JMS.
Core-9012-14: BROKER: Mes-
sage type (d) not handled; default-
ing to Byte Message
Customer has set a JMS_UM_←-
MessageType that is not under-
stood or not supported. Defaulting
to Byte Message.
The customer needs to check their
settings for JMS_UM_Message←-
Type.
Core-9012-16: BROKER: Mes-
sage type (d) not handled; default-
ing to Byte Message
Customer has set a JMS_UM_←-
MessageType that is not under-
stood or not supported. Defaulting
to Byte Message.
The customer needs to check their
settings for JMS_UM_Message←-
Type.
Core-9012-17: BROKER: Text
Message string length (d) does not
match user message length (d); us-
ing string length.
The Text Message string lenght
does not match the msg_len that
the user supplied.
The customer needs to check the
parameters passed when sending
messages.
Core-9012-18: BROKER: Proton
message type (d) not handled;
dropping.
The Proton message type is not
handled.
This can happen when JMS ap-
plications generate messages not
handled by LBM.
Core-9013-8: Unicast resolver in-
stance for lbmrd s received data-
gram from unknown source s -
dropping
A UDP datagram was received on
a topic resolution socket that was
not from the IP and port of the
lbmrd that the socket was config-
ured to use, and so this datagram
was dropped. This can happen if
an application acquires a port that
was recently used by a different ap-
plication and lbmrd.
Configure separate resolver uni-
cast port ranges for each lbmrd.
Core-9045-1: brokered contexts do
not allow the use of late-join for re-
ceivers, disabling.
The user configured "use_late_←-
join" which is not supported on a
brokered context.
The user should be informed of this
limitation and set the configuration
appropriately.
Core-9045-2: brokered contexts do
not allow the use of off-transport re-
covery, disabling.
The user configured "use_otr"
which is not supported on a
brokered context.
The user should be informed of this
limitation and set the configuration
appropriately.
Core-9047-1: Cannot use explicit
batching when sending messages
to a queue, ignoring.
Sending a message with the Ex-
plicit Batching flags is not sup-
ported on a brokered context.
The user should be informed of this
limitation.
9.1 UM Core Messages 139
Core-9053-2: UMQ participant only
option has no effect with broker
source, ignoring.
The user configured "umq_←-
queue_participants_only" which
is not supported on a brokered
context.
The user should be informed of this
limitation and set the configuration
appropriately.
Core-9089-1: brokered contexts do
not support channels, disabling.
The user configured "null_←-
channel_behavior" which is not
supported on a brokered context.
The user should be informed of this
limitation and set the configuration
appropriately.
Core-9089-2: brokered contexts do
not support channels, disabling.
The user configured "lbm_rcv←-
_topic_attr_recv_unrec_chan_←-
behavior" which is not supported
on a brokered context.
The user should be informed of this
limitation and set the configuration
appropriately.
Core-9106-110: WARNING: could
not set SO_TIMESTAMPING on
multicast source socket: s
An error was returned from the OS
while trying to set the SO_TIM←-
ESTAMPING flag on the source
socket.".
SO_TIMESTAMPING is not sup-
ported by this platform.
Core-9106-112: WARNING←-
: Context configuration op-
tion transport_lbtrm_source←-
_timestamp not valid on this
platform.
Context configuration option
transport_lbtrm_source_←-
timestamp requires recvmmsg()
which is only available as of Linux
2.6.32 and glibc 2.12.
Need to update to at least Linux
2.6.32 and glibc 2.12.
Core-9106-120: WARNING: could
not set SO_TIMESTAMPING on
multicast receive socket: s
An error was returned from the OS
while trying to set the SO_TIM←-
ESTAMPING flag on the receive
socket.".
SO_TIMESTAMPING is not sup-
ported by this platform.
Core-9106-122: WARNING←-
: Context configuration option
transport_lbtrm_receiver_←-
timestamp not valid on this
platform.
Context configuration option
transport_lbtrm_receiver_←-
timestamp requires recvmmsg()
which is only available as of Linux
2.6.32 and glibc 2.12.
Need to update to at least Linux
2.6.32 and glibc 2.12.
Core-9113-1: The configured fd_←-
management_type is ignored when
using a brokered context
The user set the "fd_←-
management_type" configuration
option which is not supported on a
brokered context.
The user should be informed of the
limitation with brokered contexts.
Core-9160-1: INFO: Attempted I←-
P_ADD_MEMBERSHIP on multi-
cast receive socket returned EN←-
OBUFS, retrying.
ENOBUFS was returned from the
OS while trying to set the socket
option IP_ADD_MEMBERSHIP. I←-
BM recommends that in this situ-
ation, retrying the request will re-
solve the situation. UM will con-
tinue to retry the request.
This is only an informational mes-
sage and no further action is re-
quired.
Core-9160-2: WARNING: could
not IP_ADD_MEMBERSHIP on
multicast receive socket: s
An error was returned from the OS
while trying to set the socket option
IP_ADD_MEMBERSHIP.
Refer to the OS error number
and message given after the UMS
message "could not IP_ADD_M←-
EMBERSHIP on multicast receive
socket".
Core-9222-1: WARNING: The
umq_queue_activity_timeout can
only be set to zero at this time,
ignoring the configured value.
umq_queue_activity_timeout is
configured with non-zero value
umq_queue_activity_timeout can
not be configured with non-zero
value at this time. Zero means no
timeout.
Core-9222-2: WARNING: The
umq_queue_activity_timeout can
only be set to zero at this time,
ignoring the configured value.
umq_queue_activity_timeout is
configured with non-zero value
umq_queue_activity_timeout can
not be configured with non-zero
value at this time. Zero means no
timeout.
Core-9230-01: BROKER: Error
while establishing broker connec-
tion (s:s), error (d).
Error trying to establish a connec-
tion to the broker.
Make sure the broker is running.
If HA is used, this might happen
when trying to find the active bro-
ker.
140 UM Log Messages
Core-9313-1: WARNING: could
not find a broadcast capable, non-
loopback interface.
As UMS initializes, it scans all the
network cards in the system. If no
network card is listed as supporting
broadcast capabilities, Ultra Mes-
saging generates this warning.
Check network card capabilities
and configuration.
Core-9313-2: WARNING: using
first unicast capable interface in-
stead.
As UMS initializes, it scans all
the network cards in the system.
No broadcast or multicast capable
card was found, but a unicast ca-
pable card was found. The first uni-
cast capable card will be used.
Check network card configuration
if you expect one of the network
cards to be multicast capable.
Core-9313-3: WARNING: could
not find a non-loopback interface.
As UMS initializes, it scans all the
network cards in the system. If no
network card is found, Ultra Mes-
saging generates this warning.
Check network card capabilities
and configuration.
Core-9336-1: INFO: ULB Receiver
on topic "%s" has use_late_join or
use_otr enabled but these are not
compatible with ULB and will be
disabled.
Late Join and OTR are not compat-
ible with ULB.
Set use_otr and use_late_join to 0
for ULB receivers.
Core-9354-1: ume_store_behavior
round-robin(rr) is no longer a
valid value. Setting to quorum-
consensus(qc).
The value of LBM_SRC_TO←-
PIC_ATTR_UME_STORE_B←-
EHAVIOR_RR (round-robin) is
no longer valid for option ume←-
_store_behavior. The value
will be overridden and set to
LBM_SRC_TOPIC_ATTR_U←-
ME_STORE_BEHAVIOR_QC
(quorum-consensus).
No further action is required as the
value is correctly set. In order
to avoid this message, change the
configuration file(s) or user code to
no longer set this value for ume_←-
store_behavior.
Core-9354-2: ume_store_behavior
round-robin(rr) is no longer a
valid value. Setting to quorum-
consensus(qc).
The values round-robin or rr are
no longer valid for option ume←-
_store_behavior. The value will
be overridden and set to quorum-
consensus.
No further action is required as the
value is correctly set. In order
to avoid this message, change the
configuration file(s) or user code to
no longer set this value for ume_←-
store_behavior.
Core-9401-4: WARNING: default←-
_interface for a context should be
set to a valid network interface.
This warning occurs if default_←-
interface was not specified as a
context attribute.
Set default_interface to a valid net-
work interface to avoid the possi-
bility of defaulting to the wrong in-
terface should the interface order
change in the future on this ma-
chine.
Core-9565-109: lbm_openssl_←-
init: OpenSSL library could not be
loaded; TLS will not be available for
data transports
The OpenSSL shared library could
not be loaded.
Check the version of OpenSSL in
use. Contact Informatica support.
Core-9565-24: Could not get Diffie-
Hellman parameters; anonymous
cipher suites will not be supported.
Diffie-Hellman parameters could
not be set; anonymous DH cipher
suites will not work.
OpenSSL might be out of date or
the wrong version. Contact Infor-
matica support.
Core-9565-25: lbm_openssl_init←-
: TLS 1.1 not supported by Open←-
SSL library [s]; TLS will not be
available for data transports
The version of OpenSSL in use
does not support TLS 1.1, which is
required.
Check the version of OpenSSL in
use. Contact Informatica support.
9.1 UM Core Messages 141
Core-9565-26: LBM_OPENSS←-
L_CONTEXT_OPTIONS environ-
ment variable was set to "%s",
which was not understood. De-
fault OpenSSL context options will
be used instead.
The content of the LBM_OPENS←-
SL_CONTEXT_OPTIONS environ-
ment variable was not understood.
Check the LBM_OPENSSL_C←-
ONTEXT_OPTIONS environment
variable to make sure it specifies
valid options.
Core-9565-27: TLS: Peer certifi-
cate verification failed; error d
("%s"), depth d, s, s
A peer certificate failed a verifica-
tion check.
Check SSL certificate chain for er-
rors.
Core-9565-28: TLS: Peer certifi-
cate verification failed; error d
("%s"), depth d, s
A peer certificate failed a verifica-
tion check.
Check SSL certificate chain for er-
rors.
Core-9565-29: TLS certificate key
file "%s" is encrypted and requires
a password, but no password was
configured.
An encrypted private key file was
used, but the password to decrypt
it was not provided.
Set the private key file's password
via the context tls_∗_certificate_←-
key_password options.
Core-9565-30: TLS: Using system
default paths for trusted certificates
FAILED.
The Windows system certificate
store could not be opened.
Contact Informatica support.
Core-9565-31: lbm_openssl_ctx←-
_set_certificates: certificate file
set, but no certificate key file spec-
ified; certificate file will be ignored
If a certificate is configured, the
certificate's private key must also
be configured.
Make sure the context_∗_←-
certificate_key options are set.
Core-9565-32: lbm_openssl_ctx←-
_set_certificates: certificate key file
set, but no certificate file specified;
key file will be ignored
A certificate key file was config-
ured, but not a corresponding cer-
tificate.
Make sure the appropriate context
tls_∗_certificate option is set.
Core-9565-33: SSL socket had un-
expected WANT_WRITE
An unexpected OpenSSL error oc-
curred.
Contact Informatica support.
Core-9565-34: lbm_openssl_←-
socket_read: sock fd d could only
write d bytes out of d
An unexpected OpenSSL error oc-
curred.
Contact Informatica support.
Core-9565-35: SSL socket had un-
expected WANT_WRITE
An unexpected OpenSSL error oc-
curred.
Contact Informatica support.
Core-9565-36: SSL socket had un-
expected error
An unexpected OpenSSL error oc-
curred.
Contact Informatica support.
Core-9565-37: Attempted to nego-
tiate protocol "%s" with peer s:d,
but peer refused. Now trying pro-
tocol "%s".
The other side of a TCP connection
actively refused a proposed proto-
col; usually this means the other
application is not configured to sup-
port the protocol or is an older ver-
sion that does not understand it.
Check for version or configuration
mismatches.
Core-9565-38: Attempted to nego-
tiate protocol "%s" with peer s:d,
but peer refused. Unable to com-
municate with peer.
The other side of a TCP connection
actively refused a proposed proto-
col; usually this means the other
application is not configured to sup-
port the protocol or is an older ver-
sion that does not understand it.
Check for version or configuration
mismatches.
Core-9565-39: LBMC CNTL trans-
port security header size incorrect.
Dropping. Origin: s:d.
An a transport security header with
an incorrect length was received.
Check the reported IP address and
port for non-UM applications.
Core-9565-40: Peer "PRI_BUF←-
F_IP" configured with no allowed
protocols in common; any further
messages from peer will not be re-
ceived.
The other side of a TCP connection
is explicitly configured to not allow
any protocols that we can speak.
Check for version or configuration
mismatches.
142 UM Log Messages
Core-9565-41: Creating source T←-
LS context failed; TLS will not be
available for sending data.
Creating a TLS context failed; this
could be due to running out of
memory.
Contact Informatica support.
Core-9565-42: Creating receiver
TLS context failed; TLS will not be
available for receiving data.
Creating a TLS context failed; this
could be due to running out of
memory.
Contact Informatica support.
Core-9565-43: WARNING: TCP
session exists but has different se-
curity protocol preferences ("%s");
security protocol preferences "%s"
were requested but will not be
used.
Once a source has created a trans-
port session a subsequent source
joining the same transport session
cannot configure different TLS set-
tings. Please refer to UMS Objects
section of the Design Concepts in
the documentation.
Make sure all sources on the same
transport session have matching
security settings.
Core-9566-11: could not allocate u
bytes [s:d]
The system was not able to allocate
the amount of memory requested.
If the amount requested was par-
ticularly large, the problem may be
a misconfiguration; however if the
amount requested was relatively
small, the physical memory on the
machine may be over committed;
try moving some applications to an-
other machine.
Core-9566-12: could not allocate u
bytes for string dup [s:d]
The system was not able to allocate
the amount of memory required for
string duplication.
The physical memory on the ma-
chine may be over committed; try
moving some applications to an-
other machine.
Core-9566-1: could not allocate u
bytes for string dup [s:d]
The system was not able to allocate
the amount of memory required for
string duplication.
The physical memory on the ma-
chine may be over committed; try
moving some applications to an-
other machine.
Core-9566-2: could not allocate u
bytes [s:d]
The system was not able to allocate
the amount of memory requested.
If the amount requested was par-
ticularly large, the problem may be
a misconfiguration; however if the
amount requested was relatively
small, the physical memory on the
machine may be over committed;
try moving some applications to an-
other machine.
Core-9566-3: could not allocate u
bytes [s:d]
The system was not able to allocate
the amount of memory requested.
If the amount requested was par-
ticularly large, the problem may be
a misconfiguration; however if the
amount requested was relatively
small, the physical memory on the
machine may be over committed;
try moving some applications to an-
other machine.
Core-9566-8: could not allocate u
bytes [s:d]
The system was not able to allocate
the amount of memory requested.
If the amount requested was par-
ticularly large, the problem may be
a misconfiguration; however if the
amount requested was relatively
small, the physical memory on the
machine may be over committed;
try moving some applications to an-
other machine.
Core-9571-10: Domain name
interface: s resolved to ip: s
CIDR: d
The provide domain name interface
was resolved via DNS lookup.
Core-9571-16: Domain name
address: s resolved to ip: s
The provide domain name was re-
solved via DNS lookup.
9.1 UM Core Messages 143
Core-9586-1: Attempted to negoti-
ate protocol "%s" with peer s:d, but
peer refused. Now trying protocol
"%s".
The other side of a TCP connection
actively refused a proposed proto-
col; usually this means the other
application is not configured to sup-
port the protocol or is an older ver-
sion that does not understand it.
Check for version or configuration
mismatches.
Core-9586-2: Attempted to negoti-
ate protocol "%s" with peer s:d, but
peer refused. Unable to communi-
cate with peer.
The other side of a TCP connection
actively refused a proposed proto-
col; usually this means the other
application is not configured to sup-
port the protocol or is an older ver-
sion that does not understand it.
Check for version or configuration
mismatches.
Core-9588-01: Negotiation timeout
with peer s:d.
Security negotiation timed out. Check for version or configuration
mismatches.
Core-9588-02: Negotiation timeout
with peer s:d.
Security negotiation timed out. Check for version or configuration
mismatches.
Core-9588-03: Request negotiate
timeout with peer s:d.
Security negotiation timed out. Check for version or configuration
mismatches.
Core-9588-04: Response negoti-
ate timeout with peer s:d.
Security negotiation timed out. Check for version or configuration
mismatches.
Core-9592-1: WARNING: Re-
quested receiver attributes for
receiver on topic [s] do not allow
any messages to be delivered.
Receiver will not receive any
messages.
The receiver is configured in a way
that won't allow it to receive any
messages.
Check configuration and make sure
a receiver that cannot receive any
messages was what was intended.
Core-9592-2: WARNING: Request
port configuration settings do not
allow any messages to be deliv-
ered. Context will not be able to re-
ceive certain message types.
The context's request port is con-
figured in a way that won't allow it
to receive any messages.
Check configuration and make sure
a context that cannot receive any
messages on its request port was
what was intended.
Core-9592-3: WARNING: Re-
quested wildcard receiver at-
tributes for wildcard receiver on
pattern [s] do not allow any mes-
sages to be delivered. Receiver
will not receive any messages.
The wildcard receiver is configured
in a way that won't allow it to re-
ceive any messages.
Check configuration and make sure
a wildcard receiver that cannot re-
ceive any messages was what was
intended.
Core-9600-01: Setting mim_←-
address on a security/compression
context is not supported. Disabling
MIM.
Multicast Immediate Messages are
not supported on a Security and/or
Compression context. Setting MIM
options is not allowed.
Do not set MIM options on a secu-
rity/compression context.
Core-9612-2: received lji request,
but Late-Join not configured: from
ip:port[s:d] for topic[u]
UMS received Late Join Request
message however late-join is not
configured for this source. This is
not a serious problem but indicates
that there is a mismatch between
this process and another.
Check the system for port re-use
on application restart and similar
behavior.
Core-9625-1: WARNING←-
: resovler_unicast_daemon entry
(s:u) already exist. Skipping...
The lbm_context_attr_set/sset()
detected duplicate unicast resolver
entries. The duplicate entries will
be skipped.
Check the config file or code (if
config set via code) for dupli-
cate resolver_unicast_daemon en-
tries. Also check if lbm_←-
config() is loaded multiple times
with the same resolver_unicast_←-
daemon entries
144 UM Log Messages
Core-9626-1: WARNING: ume_←-
store entry (u:s:u:u:u) already exist.
Skipping...
The lbm_src_topic_attr_setopt()
detected duplicate ume_store en-
tries. The duplicate entries will be
skipped.
Check the config file or code (if
config set via code) for duplicate
ume_store entries. Also check
if lbm_config() is loaded multiple
times with the same ume_store en-
tries
Core-9626-2: WARNING: ume_←-
store_name entry (s:u:u) already
exist. Skipping...
The lbm_src_topic_attr_setopt()
detected duplicate ume_store_←-
name entries. The duplicate en-
tries will be skipped.
Check the config file or code (if
config set via code) for duplicate
ume_store_name entries. Also
check if lbm_config() is loaded
multiple times with the same ume←-
_store_name entries
Core-9640-1: WARNING: broker
entry (s:u) already exist. Skipping...
The lbm_context_attr_setopt/str_←-
setopt() detected duplicate broker
entries. The duplicate entries will
be skipped.
Check the config file or code (if
config set via code) for duplicate
broker entries. Also check if lbm←-
_config() is loaded multiple times
with the same broker entries
Core-9709-1: epoll_ctl: EPOLL_←-
CTL_DEL returned: errno:d:s
epoll returned an error during lbm←-
_cancel_fd call
Core-9726-1: WARNING: Context
configuration option transport_←-
lbtrm_source_timestamp not valid
with the installed version of Onload.
Context configuration option
transport_lbtrm_source_←-
timestamp requires OpenOnload-
201509 or later.
Need to update the installed ver-
sion of Open Onload.
Core-9728-10: Problem detected
trying to setup a TLS context.
Creating the TLS context failed due
to an error with strdup(). There
could be a memory issue.
Check memory utilization and
availability.
Core-9728-11: Problem detected
trying to setup a TLS context.
Creating the TLS context failed due
to an error with strdup(). There
could be a memory issue.
Check memory utilization and
availability.
Core-9728-12: Problem detected
trying to setup a TLS context.
Creating the TLS context failed due
to an error with strdup(). There
could be a memory issue.
Check memory utilization and
availability.
Core-9728-13: Problem detected
trying to setup a TLS context.
Creating the TLS context failed due
to an error with strdup(). There
could be a memory issue.
Check memory utilization and
availability.
Core-9728-14: Problem detected
trying to setup a TLS context. No
configured ciphers were available.
An error occurred when parsing
and creating the configured TLS
suite.
Check the parameters for the tls←-
_cipher_suites option or check the
OpenSSL version.
Core-9728-15: Problem detected
trying to setup a TLS context. TLS
initialization failed or no configured
ciphers were available.
An error occurred when creating
the OpenSSL context.
Check the OpenSSL version to
make sure it is the version de-
livered with LBM. Also check the
tls_cipher_suites configuration op-
tion.
Core-9729-1: Unexpected EWO←-
ULDBLOCK while receiving Topic
Resolution packets. Dropping.
An EWOULDBLOCK was returned
on a Topic Resolution socket. That
is typically not expected since L←-
BM does a "select" on the socket
and only reads if data is ready. This
could be a data error such as a
checksum issue.
The user should find the source
of the corruption and resolve the
source of the issue.
Core-9729-2: Unexpected EWO←-
ULDBLOCK while receiving source
LBT-RM packets. Dropping.
An EWOULDBLOCK was returned
on the LBT-RM source socket. That
is typically not expected since L←-
BM does a "select" on the socket
and only reads if data is ready. This
could be a data error such as a
checksum issue.
The user should find the source
of the corruption and resolve the
source of the issue.
9.1 UM Core Messages 145
Core-9729-3: Unexpected EWO←-
ULDBLOCK while receiving LBT-←-
RM packets. Dropping.
An EWOULDBLOCK was returned
on the LBT-RM receive socket.
That is typically not expected since
LBM does a "select" on the socket
and only reads if data is ready. This
could be a data error such as a
checksum issue.
The user should find the source
of the corruption and resolve the
source of the issue.
Core-9729-4: Unexpected EWO←-
ULDBLOCK while receiving source
LBT-RU packets. Dropping.
An EWOULDBLOCK was returned
on the LBT-RU source socket. That
is typically not expected since L←-
BM does a "select" on the socket
and only reads if data is ready. This
could be a data error such as a
checksum issue.
The user should find the source
of the corruption and resolve the
source of the issue.
Core-9729-5: Unexpected EWO←-
ULDBLOCK while receiving LBT-←-
RU packets. Dropping.
An EWOULDBLOCK was returned
on the LBT-RU receive socket. That
is typically not expected since L←-
BM does a "select" on the socket
and only reads if data is ready. This
could be a data error such as a
checksum issue.
The user should find the source
of the corruption and resolve the
source of the issue.
Core-9729-6: Unexpected EWO←-
ULDBLOCK while receiving Wild-
card LBT-RM packets. Dropping.
An EWOULDBLOCK was returned
on a Wildcard LBT-RM socket. That
is typically not expected since L←-
BM does a "select" on the socket
and only reads if data is ready. This
could be a data error such as a
checksum issue.
The user should find the source
of the corruption and resolve the
source of the issue.
Core-9743-08: WARNING: proac-
tive keepalive is not supported by
the store. See the Operations
Guide for configuration advice.
The store registration response in-
dicates that the store does not sup-
port receiver proactive keepalive.
This is determined by the registra-
tion handshake between the topic
receiver and the UME store dae-
mon.
This warning will occur for every
registration and does not indicate
a misconfiguration between the
store and topic receiver. Since the
receiver does support proactive
keepalive, the benefits of that
feature can be realized by setting
the store keepalive-interval option
to be greater than the context
ume_proactive_keepalive_interval
in this receiver. This prevents
the store's ume_activity_timer for
this receiver from expiring and
initiating keepalive messages to
the receiver. This message can
appear until both the store and all
topic receivers are upgraded to a
6.9.1 or later release.
Core-9779-101: WARNING: Join-
ing session [s] which exists and
uses a different transport_lbtrm←-
_nak_init_backoff_interval [d] than
requested [d].
After a receiver has created a
transport session, a subsequent
receiver joining the same trans-
port session cannot configure a
different transport_lbtrm_nak_init←-
_backoff_interval setting.
Core-9779-102: WARNING: Join-
ing session [s] which exists and
uses a different transport_lbtru←-
_nak_init_backoff_interval [d] than
requested [d].
After a receiver has created a
transport session, a subsequent
receiver joining the same trans-
port session cannot configure a
different transport_lbtru_nak_init←-
_backoff_interval setting.
146 UM Log Messages
Core-9829-1: all sources must be
deleted before deleting the context
You cannot delete a context while it
still has active sources.
Delete all sources first then delete
the context.
Core-9829-2: all receivers must be
deleted before deleting the context
You cannot delete a context while it
still has active receivers.
Delete all receivers first then delete
the context.
Core-9941-1212: specified smart
source user buffer count of d will be
increased to the next highest power
of two: d
The smart_src_user_buffer_count
value is not a power of two
Increase the smart_src_user_←-
buffer_count value to a power of
two
Core-9941-2212: specified smart
source retention buffer count of d
will be increased to the next high-
est power of two: d
The smart_src_retention_buffer_←-
count value is not a power of two
Increase the smart_src_retention←-
_buffer_count value to a power of
two
Core-9941-3131: specified smart
source transmission window buffer
count of d will be increased to the
next highest power of two: d
The transport Smart Source trans-
mission window buffer value is not
a power of two.
To avoid this message round up all
transport Smart Source transmis-
sion window buffer count values to
a power of two.
Core-9941-4444: WARNING:
LBM_SMART_SOURCE_CHECK
logic enabled.
LBM_SMART_SOURCE_CHE←-
CK logic enabled. This is useful
and recommended for debug-
ging but may seriously degrade
performance.
Unset LBM_SMART_SOURCE_←-
CHECK for best performance in
your system.
Core-9941-6002: JNI: Source
event callback threw an exception.
An exception occurred while pro-
cessing an event callback.
Check the logs for specific details
of the exception.
Core-9950-1: Critical Windows
Completion Port error (d) (s): the
Receive I/O operation could not be
started. No data will be received (s)
The Receive operation for Win-
dows Completion Ports did not
start. Deafness will likely occur.
The user needs to fix the issue with
the communications and restart
their process.
Core-9951-1: Topic Resolution
socket send error (s).
A socket error occurred when
sending a Topic Resolution mes-
sage. The Topic Resolution mes-
sage will not be retried.
The socket error is included. The
user needs to resolve the error and
restart the process.
Core-9951-2: Topic Resolution
socket send error (s).
A socket error occurred when
sending a Topic Resolution mes-
sage. The Topic Resolution mes-
sage will not be retried.
The socket error is included. The
user needs to resolve the error and
restart the process.
Core-9954-50: User defined data-
gram acceleration will override DBL
library pre-loaded functions
The Datagram Acceleration feature
is being used which will override
the DBL libraries loaded.
The user needs to be aware that
Datagram Acceleration and DBL
cannot be used at the same time.
9.2 UM Core API Messages
CoreApi-10055-10: optval must be
0 or greater than 0
The smart_src_message_←-
property_int_count did not contain
a positive integer
The smart_src_message_←-
property_int_count must be zero 0
or greater
CoreApi-10055-1177: optlen incor-
rect size
The memory management call-
backs structure is expected to
be the size of lbm_mem_mgt_←-
callbacks_t
The user needs to pass the correct
size to the option setter
9.2 UM Core API Messages 147
CoreApi-10055-1178: malloc call-
back function must be valid
The memory allocation callback is
required to acquire memory re-
gions
Supply an application-specific
memory allocation function
CoreApi-10055-1179: free callback
function must be valid
The memory deallocation callback
is required to return memory re-
gions
Supply an application-specific
memory deallocation function
CoreApi-10055-1180: str_setopt
not supported for option
String set option is not supported
for memory management callbacks
CoreApi-10055-1181: optlen incor-
rect size
The memory management call-
backs structure is expected to
be the size of lbm_mem_mgt_←-
callbacks_t
The user needs to pass the correct
size to the option getter
CoreApi-10055-1182: str_getopt
not supported for option
String get option is not supported
for memory management callbacks
CoreApi-10055-118: corrupted
user buffer pointer structure
A smart source call specified what
appears to be a corrupted user
buffer pointer structure.
Ensure that writes using the user
buffer pointer do not exceed the
range of addresses bounded by the
source scoped smart_src_max_←-
message_length configuration op-
tion.
CoreApi-10055-119: user mes-
sage len exceeds the configured
maximum
A smart source call specified a
message length greater than the
configured maximum.
Ensure that the message length
is less than or equal to the
source scoped smart_src_max_←-
message_length configuration op-
tion.
CoreApi-10055-11: optval too large The smart_src_message_←-
property_int_count is larger than
the maximum allowed size
Decrease the size of smart_src_←-
message_property_int_count
CoreApi-10055-1200: cannot up-
date spectrum channel
A smart source send call specified
a Spectrum channel update with-
out specifying the LBM_SSRC_S←-
END_EX_FLAG_CHANNEL send
flag.
Only set LBM_SSRC_SEND_EX←-
_FLAG_UPDATE_CHANNEL with
the LBM_SSRC_SEND_EX_FL←-
AG_CHANNEL flag set.
CoreApi-10055-1201: cannot up-
date spectrum channel
A smart source send call specified
a Spectrum channel update of a
buffer that has never been format-
ted.
Only set LBM_SSRC_SEND_←-
EX_FLAG_UPDATE_CHANNEL if
the buffer has been previously
formatted with a send specify-
ing LBM_SSRC_SEND_EX_FLA←-
G_CHANNEL.
CoreApi-10055-1202: cannot send
on a spectrum channel without
message properties
A smart source send call attempted
to send on a spectrum channel
without message properties.
With both spectrum channel and
message properties configured you
have the option to either send a
message with both spectrum chan-
nel and message properties, or
without both, i.e., you cannot selec-
tively send one without the other.
CoreApi-10055-120: spectrum
channel is not configured
A smart source send call specified
a Spectrum channel that has not
been configured.
Either clear the LBM_SSRC_S←-
END_EX_FLAG_CHANNEL flag
or set the source scoped smart←-
_src_enable_spectrum_channel
configuration option.
CoreApi-10055-121: integer mes-
sage properties are not configured
A smart source send call specified
Message Properties that have not
been configured.
Either clear the LBM_SSRC_SE←-
ND_EX_FLAG_PROPERTIES flag
or set the source scoped smart_←-
src_message_property_int_count
configuration option.
148 UM Log Messages
CoreApi-10055-1221: cannot up-
date property values
A smart source send call specified
a message property values update
with a non-positive number of inte-
ger message properties.
Only set LBM_SSRC_SEND_EX←-
_FLAG_UPDATE_PROPERTY_←-
VALUES with a positive number of
integer message properties that is
less than or equal to the configured
smart_src_message_property_←-
int_count.
CoreApi-10055-1222: integer mes-
sage properties count not positive
A smart source send call specified
a non-positive number of integer
Message Properties.
Either clear the LBM_SSRC_S←-
END_EX_FLAG_PROPERTIES
flag, or set message properties in-
teger count to be a positive integer
that is less than or equal to the
configured smart_src_message_←-
property_int_count.
CoreApi-10055-1227: cannot up-
date property values
A smart source send call speci-
fied a message property values
update without specifying the
LBM_SSRC_SEND_EX_FLAG_←-
PROPERTIES send flag.
Only set LBM_SSRC_SEND_EX←-
_FLAG_UPDATE_PROPERTY_←-
VALUES with the LBM_SSRC_←-
SEND_EX_FLAG_PROPERTIES
flag set.
CoreApi-10055-122: integer mes-
sage properties exceed the config-
ured maximum
A smart source send call specified
more integer Message Properties
than the configured maximum.
Either clear the LBM_SSRC_S←-
END_EX_FLAG_PROPERTIES
flag, or increase the source scoped
smart_src_message_property_←-
int_count, or reduce the number
integer message properties.
CoreApi-10055-123: invalid pointer
to integer message property values
array
A smart source send call specified
a NULL pointer to an array of inte-
ger message property values.
Either clear the LBM_SSRC_S←-
END_EX_FLAG_PROPERTIES
flag, or specify a pointer to an
array of integer message property
values.
CoreApi-10055-124: invalid pointer
to integer message property key
names array
A smart source send call specified
a NULL pointer to an array of inte-
ger message property key names.
Either clear the LBM_SSRC_S←-
END_EX_FLAG_PROPERTIES
flag, or specify a pointer to an array
of integer message property key
names.
CoreApi-10055-125: invalid pointer
to integer message property key
name #d
A smart source send call specified
a NULL pointer to an integer mes-
sage property key name.
Specify pointers to integer mes-
sage property key names for the
number of specified message prop-
erty integers.
CoreApi-10055-126: invalid pointer
to integer message property key
name #d
A smart source send call specified
a pointer to a zero-length integer
message property key name.
Specify pointers to non-NULL inte-
ger message property key names
for the number of specified mes-
sage property integers.
CoreApi-10055-127: integer mes-
sage property key name #d too
long
A smart source send call specified
a pointer to an integer message
property key name greater than 7
characters.
Specify pointers to integer mes-
sage property key names that are
between 1 and 7 characters in
length.
CoreApi-10055-128: cannot up-
date property values
A smart source send call specified
a message property values update
of a buffer that has never been for-
matted.
Only set LBM_SSRC_SEND_E←-
X_FLAG_UPDATE_PROPERT←-
Y_VALUES if the buffer has been
previously formatted with a send
specifying LBM_SSRC_SEND_←-
EX_FLAG_PROPERTIES.
9.2 UM Core API Messages 149
CoreApi-10055-129: cannot send
message properties without a
spectrum channel
A smart source send call attempted
to send message properties with-
out specifying a spectrum channel.
With both spectrum channel and
message properties configured you
have the option to either send a
message with both spectrum chan-
nel and message properties, or
without both, i.e., you cannot selec-
tively send one without the other.
CoreApi-10055-12: optval not nu-
meric
The smart_src_message_←-
property_int_count value is not
numeric
The smart_src_message_←-
property_int_count must be a
numeric value
CoreApi-10055-130: inflight pa-
rameter must be a valid pointer
The inflight parameter was NULL. The inflight parameter must be a
valid pointer.
CoreApi-10055-13: optval must be
0 or greater than 0
The smart_src_message_←-
property_int_count did not contain
a positive integer
The smart_src_message_←-
property_int_count must be zero or
greater
CoreApi-10055-140: smart source
could not deregister from store
Smart Source failed trying to
deregister from a store.
Try again, unicast control channel
between smart source and store
may be down.
CoreApi-10055-14: optval too large The smart_src_message_←-
property_int_count is larger than
the maximum allowed size
Decrease the size of smart_src_←-
message_property_int_count
CoreApi-10055-150: smart source
is already deregistering from the
stores
Smart Source is already deregis-
tered.
Don't call lbm_ssrc_ume_←-
deregister multiple times passing
in the same smart source.
CoreApi-10055-15: optlen incor-
rect size
The size of the option was too large
or too small
The smart_src_message_←-
property_int_count must be
sizeof(int)
CoreApi-10055-16: optlen too
small
The size of the option buffer was
too small to contain the option
The smart_src_message_←-
property_int_count optlen must be
at least 80
CoreApi-10055-1: optlen incorrect
size
The smart_src_enable_spectrum←-
_channel value contained an incor-
rect length
The smart_src_enable_spectrum←-
_channel should be of sizeof(int)
CoreApi-10055-2985: event
queues are not supported
Smart sources do not support
event queues at this time.
evq parameter must be NULL.
CoreApi-10055-2987: Smart
sources do not support receive
delivery confirmation notifications
Smart sources do not support re-
ceive delivery confirmation notifica-
tions.
Set source option ume_←-
confirmed_delivery_notification
to 0.
CoreApi-10055-2988: Smart
sources do not support unique
confirmation notification
Smart sources do not support re-
ceive unique confirmation notifica-
tion.
Set source option ume_retention←-
_unique_confirmations to 0.
CoreApi-10055-2989: Smart
sources do not accept stability
notification for message fragments
Smart sources do not support sta-
bility notification for message frag-
ments.
Either ignore this option and rely
on the default (LBM_SRC_TOP←-
IC_ATTR_UME_STABLE_EVE←-
NT_PER_MESSAGE), or explicitly
specify message notification at-
tribute LBM_SRC_TOPIC_ATT←-
R_UME_STABLE_EVENT_NONE
or LBM_SRC_TOPIC_ATTR_U←-
ME_STABLE_EVENT_PER_ME←-
SSAGE.
CoreApi-10055-2999: INFO←-
: Smart source smart_src_←-
retention_buffer_count is less than
ume_flight_size.
Setting the retention buffer count
less than the UME flight size could
force unacknowledged messages
from the retention buffer.
Specify the smart_src_retention←-
_buffer_count to be greater than
ume_flight_size.
150 UM Log Messages
CoreApi-10055-2: optval must be 0
or 1
The smart_src_enable_spectrum←-
_channel did not contain a positive
integer
The smart_src_enable_spectrum←-
_channel must be zero or 1
CoreApi-10055-3012: send would
block because of flight size
The flight size behavior is "Block" &
flight size will be exceeded.
Increase the flight size
CoreApi-10055-3040: Can not
specify a negative number for in-
flight messages
Attempting to set the flight size of
messages to a negative number
Ensure a positive integer for inflight
messages is returned from the set
flight size callback
CoreApi-10055-3041: Cannot in-
crease inflight messages or bytes
while decreasing the other
Attempting to increase the flight
size messages or bytes and de-
crease the other.
Ensure that the inflight set callback
returns a valid inflight structure, or
call the method twice to set each
one individually.
CoreApi-10055-3042: ssrc must be
valid
The ssrc parameter was NULL. The ssrc parameter must be a valid
pointer.
CoreApi-10055-3043: inflight must
be valid
The inflight parameter was NULL. The inflight parameter must be a
valid pointer.
CoreApi-10055-3044: ssrc is not
using UME flight size
The Smart Source did not specify
flight size.
Specify a UME flight size.
CoreApi-10055-3047: invalid flight
size type d
The flight size type is invalid. Specify a valid flight size type of L←-
BM_FLIGHT_SIZE_TYPE_UME.
CoreApi-10055-3: optval too large The smart_src_enable_spectrum←-
_channel must be zero or 1
The smart_src_enable_spectrum←-
_channel must be zero or 1
CoreApi-10055-4395: Message
stability notification is not enabled
Per-send client object specified but
message stability notification was
not enabled.
Either enable message stability or
remove the per-send client object.
CoreApi-10055-4397: Can't allo-
cate per-send object node; mes-
sage not sent [s:d]
Unable to allocate memory for the
per-send object node.
The physical memory on the ma-
chine may be over committed; try
moving some applications to an-
other machine.
CoreApi-10055-4522: Can't allo-
cate message properties of u bytes
[s:d]
The system was not able to allocate
the amount of memory requested.
The physical memory on the ma-
chine may be over committed; try
moving some applications to an-
other machine.
CoreApi-10055-4523: The number
of Message Properties is larger
than the maximum allowed size d
[s:d]
The smart_src_message_←-
property_int_count is larger than
the maximum allowed size
Decrease the size of smart_src_←-
message_property_int_count
CoreApi-10055-4524: Can't ac-
cess message property key string
d [s:d]
An exception occurred while pro-
cessing a message property key
string.
Check the logs for specific details
of the exception.
CoreApi-10055-4525: Can't con-
vert message property key string s
[s:d]
Ran out of memory while creating
a message property key string
The physical memory on the ma-
chine may be over committed; try
moving some applications to an-
other machine.
CoreApi-10055-4: optval not nu-
meric
The smart_src_enable_spectrum←-
_channel value is not numeric
The smart_src_enable_spectrum←-
_channel must be a numeric value
of 0 or 1
CoreApi-10055-5: optval must be 0
or 1
The smart_src_enable_spectrum←-
_channel did not contain a positive
integer
The smart_src_enable_spectrum←-
_channel must be zero or 1
CoreApi-10055-6: optval too large The smart_src_enable_spectrum←-
_channel must be zero or 1
The smart_src_enable_spectrum←-
_channel must be zero or 1
CoreApi-10055-7: optlen incorrect
size
The size of the option was too large
or too small
The smart_src_enable_spectrum←-
_channel must be sizeof(int)
CoreApi-10055-8: optlen too small The size of the option buffer was
too small to contain the option
The smart_src_enable_spectrum←-
_channel optlen must be at least 80
9.2 UM Core API Messages 151
CoreApi-10055-9: optlen incorrect
size
The smart_src_message_←-
property_int_count value contained
an incorrect length
The smart_src_message_←-
property_int_count should be of
sizeof(int)
CoreApi-10115-3320: lbm_←-
socket_recv recv/recvfrom: s
An error was returned from the
OS while trying a recv or recvfrom
socket call. Refer to the OS error
number and message.
Please use the appended operat-
ing system's WSA error message
to further understand the circum-
stances of the error.
CoreApi-10115-3321: lbm_←-
socket_recv recv/recvfrom: s
An error was returned from the
OS while trying a recv or recvfrom
socket call. Refer to the OS error
number and message.
This is a platform specific error;
please use the operating system's
error code and description to fur-
ther understand the circumstances
of the error.
CoreApi-10115-3337: lbm_←-
socket_sendb send/sendto: s
An error occurred while sending.
The message will contain addition
specific information, supplied by
the operating system.
Please use the appended operat-
ing system's WSA error message
to further understand the circum-
stances of the error.
CoreApi-10115-3338: lbm_←-
socket_sendb send/sendto: s
An error occurred while sending.
The message will contain addition
specific information, supplied by
the operating system.
This is a platform specific error;
please use the operating system's
error code and description to fur-
ther understand the circumstances
of the error.
CoreApi-10115-3342: lbm_←-
socket_sendtob send/sendto:
s
socket_sendtob: Error on socket
send to destination. The message
will contain addition specific infor-
mation, supplied by the operating
system.
Please use the appended operat-
ing system's WSA error message
to further understand the circum-
stances of the error.
CoreApi-10115-3343: lbm_←-
socket_sendtob send/sendto:
s
socket_sendtob: Error on socket
send to destination. The message
will contain addition specific infor-
mation, supplied by the operating
system.
This is a platform specific error;
please use the operating system's
error code and description to fur-
ther understand the circumstances
of the error.
CoreApi-10115-3353: lbm_←-
socket_sendbv : s
lbm_socket_sendtobv: Error on
socket send to destination. The
message will contain addition spe-
cific information, supplied by the
operating system.
Please use the appended operat-
ing system's WSA error message
to further understand the circum-
stances of the error.
CoreApi-10115-3354: lbm_←-
socket_sendbv: s
lbm_socket_sendtobv: Error on
socket send to destination. The
message will contain addition spe-
cific information, supplied by the
operating system.
This is a platform specific error;
please use the operating system's
error code and description to fur-
ther understand the circumstances
of the error.
CoreApi-10138-10: optval not sup-
ported
optval must either be LBM_CTX_←-
ATTR_OP_EMBEDDED or LBM←-
_CTX_ATTR_OP_SEQUENTIAL
CoreApi-10138-11: optval not un-
derstood
optval must either be LBM_CTX_←-
ATTR_OP_EMBEDDED or LBM←-
_CTX_ATTR_OP_SEQUENTIAL
CoreApi-10138-12: optlen incor-
rect size
optlen must be the size of an 'int'
CoreApi-10138-13: optlen too
small
optval must either be 'embedded'
or 'sequential'
CoreApi-10138-14: optlen incor-
rect size
optlen must be the size of an lbm←-
_xsp_zero_transports_func_t
CoreApi-10138-15: zero transports
callback must be valid
optval must be a pointer to an lbm←-
_xsp_zero_transports_func_t
152 UM Log Messages
CoreApi-10138-16: str_setopt not
supported for option
The lbm_xsp_attr_str_setopt API
can not be used to set the zero
transports func
Use lbm_xsp_attr_setopt instead
CoreApi-10138-17: optlen incor-
rect size
optlen must be the size of an lbm←-
_xsp_zero_transports_func_t
CoreApi-10138-18: str_getopt not
supported for option
The lbm_xsp_attr_str_getopt API
can not be used to get the zero
transports func
Use lbm_xsp_attr_getopt instead
CoreApi-10138-1: attr, optname,
and optval must not be NULL
attr, optname, and optval must all
be valid pointers
CoreApi-10138-20: attr must be
valid
Must supply a valid pointer to a
pointer to an lbm_xsp_attr_t
CoreApi-10138-21: attr must be
valid
Must supply a valid pointer to an
lbm_xsp_attr_t
CoreApi-10138-2: option s un-
known
The specified xsp config option was
not found
CoreApi-10138-30: xspp must be
valid
Must supply a valid pointer to a
pointer that will be filled in with the
xsp being created
CoreApi-10138-31: ctx must be
valid
Must supply a valid pointer to a
context
CoreApi-10138-37: xsp must be
valid
Must supply a pointer to a valid xsp
CoreApi-10138-38: xsp must be
valid
Must supply a pointer to a valid xsp
CoreApi-10138-39: xsp must be
valid
Must supply a pointer to a valid xsp
CoreApi-10138-3: attr, optname,
and optval must not be NULL
attr, optname, and optval must all
be valid pointers
CoreApi-10138-4: option s un-
known
The specified xsp config option was
not found
CoreApi-10138-5: attr, optname,
optval, and optlen must not be N←-
ULL
attr, optname, optval, and optlen
must all be valid pointers
CoreApi-10138-6: option s un-
known
The specified xsp config option was
not found
CoreApi-10138-70: optlen incor-
rect size
optlen must be the size of an lbm←-
_transport_mapping_func_t
CoreApi-10138-71: mapping func-
tion must be valid
optval must be a pointer to an lbm←-
_transport_mapping_func_t
CoreApi-10138-72: str_setopt not
supported for option
The lbm_context_attr_str_setopt
API can not be used to set the
xport mapping func
Use lbm_context_attr_setopt in-
stead
CoreApi-10138-73: optlen incor-
rect size
optlen must be the size of an lbm←-
_transport_mapping_func_t
CoreApi-10138-75: str_getopt not
supported for option
The lbm_context_attr_str_getopt
API can not be used to set the
xport mapping func
Use lbm_context_attr_getopt in-
stead
CoreApi-10138-7: attr, optname,
optval, and optlen must not be N←-
ULL
attr, optname, optval, and optlen
must all be valid pointers
CoreApi-10138-81: Can't allocate
memory [s:d]
Java is unable to allocate memory
CoreApi-10138-82: Can't allocate
memory [s:d]
Java is unable to allocate memory
9.2 UM Core API Messages 153
CoreApi-10138-83: Can't allocate
memory [s:d]
Java is unable to allocate memory
CoreApi-10138-8: option s un-
known
The specified xsp config option was
not found
CoreApi-10138-90: optlen incor-
rect size
optlen must be the size of an 'lbm←-
_ulong_t'
CoreApi-10138-91: optval not nu-
meric
optval must be able to be converted
into an lbm_ulong_t
CoreApi-10138-92: opval not a
number
optval must be able to be converted
into an lbm_ulong_t
CoreApi-10138-93: optlen incor-
rect size
optlen must be the size of an 'lbm←-
_ulong_t'
CoreApi-10138-94: optlen too
small
optlen must be the size of an 'lbm←-
_ulong_t''
CoreApi-10138-95: optlen too
small
optlen must be the size of an 'lbm←-
_ulong_t''
CoreApi-10138-9: optlen incorrect
size
optlen must be the size of an 'int'
CoreApi-10160-31: optlen incor-
rect size
transport_lbtru_smart_src_←-
transmission_window_buffer_←-
count value contained an incorrect
length
transport_lbtru_smart_src_←-
transmission_window_buffer_←-
count should be of sizeof(int)
CoreApi-10160-32: optval must be
greater than 0
transport_lbtru_smart_src_←-
transmission_window_buffer_←-
count did not contain a positive
integer
transport_lbtru_smart_src_←-
transmission_window_buffer_←-
count must be a positive integer
CoreApi-10160-33: optval too large transport_lbtru_smart_src_←-
transmission_window_buffer_←-
count is larger than the maximum
allowed size
Decrease the size of transport_←-
lbtru_smart_src_transmission_←-
window_buffer_count
CoreApi-10160-34: optval not nu-
meric
transport_lbtru_smart_src_←-
transmission_window_buffer_←-
count value was not numeric
transport_lbtru_smart_src_←-
transmission_window_buffer_←-
count must be a numeric value
CoreApi-10160-35: optval must be
greater than 0
transport_lbtru_smart_src_←-
transmission_window_buffer_←-
count did not contain a positive
integer
transport_lbtru_smart_src_←-
transmission_window_buffer_←-
count must be a positive integer
CoreApi-10160-36: optval too large transport_lbtru_smart_src_←-
transmission_window_buffer_←-
count is larger than the maximum
allowed size
Decrease the size of transport_←-
lbtru_smart_src_transmission_←-
window_buffer_count
CoreApi-10160-37: optlen incor-
rect size
The size of the option was too large
or too small
transport_lbtru_smart_src_←-
transmission_window_buffer_←-
count must be sizeof(int)
CoreApi-10160-38: optlen too
small
The size of the option buffer was
too small to contain the option
transport_lbtru_smart_src_←-
transmission_window_buffer_←-
count optlen must be at least
80
CoreApi-10160-5565: Smart
source may not use the same
transport as a standard source
An lbm smart source may not re-
side with a standard source on the
same transport.
Configure the smart source on an
LBT-RU transport that only con-
tains smart sources.
154 UM Log Messages
CoreApi-10160-5566: smart_src←-
_max_message_length exceeds
the configured maximum message
length for this transport session.
The first Smart Source to create
a transport session establishes the
maximum message length for all
subsequent Smart Sources on that
transport.
Decrease the size of smart_←-
src_max_message_length for this
Smart Source or increase the
size of smart_src_max_message←-
_length for the first Smart Source
created on this transport session.
CoreApi-10160-5574: Could not
allocate lu bytes. The product
of transport_lbtru_smart_src←-
_transmission_window_buffer←-
_count and smart_src_max_←-
message_length exceeds available
memory on your system.
The product of transport_lbtru_←-
smart_src_transmission_window←-
_buffer_count and smart_src_←-
max_message_length specifies
more memory than is available on
your system.
Decrease the size of transport←-
_lbtru_smart_src_transmission←-
_window_buffer_count and/or the
smart_src_max_message_length.
CoreApi-10160-5575: Smart
source may not use the same
transport as a standard source
An lbm standard source may not
reside with a smart source on the
same transport.
Configure the standard source on
an LBT-RU transport that only con-
tains standard sources.
CoreApi-10160-5674: Could not
allocate lu bytes. The product
of transport_lbtru_smart_src←-
_transmission_window_buffer←-
_count and smart_src_max_←-
message_length exceeds available
memory on your system.
The product of transport_lbtru_←-
smart_src_transmission_window←-
_buffer_count and smart_src_←-
max_message_length specifies
more memory than is available on
your system.
Decrease the size of transport←-
_lbtru_smart_src_transmission←-
_window_buffer_count and/or the
smart_src_max_message_length.
CoreApi-10190-2: optlen incorrect
size
optlen must be the size of an 'lbm←-
_ulong_t'
CoreApi-10190-3: optval not nu-
meric
optval must be able to be converted
into an lbm_ulong_t
CoreApi-10190-4: opval not a num-
ber
optval must be able to be converted
into an lbm_ulong_t
CoreApi-10190-5: optlen incorrect
size
optlen must be the size of an 'lbm←-
_ulong_t'
CoreApi-10193-1: optlen incorrect
size
Attempted to set option round_←-
robin_xsp_count with an incorrect
optlen size.
Optlen must be size of int.
CoreApi-10193-2: optval not nu-
meric
Attempted to set option round←-
_robin_xsp_count with a non-
numeric value.
Optval must be a numeric value,
greater than or equal to 0.
CoreApi-10193-3: optlen incorrect
size
Attempted to get option round_←-
robin_xsp_count with an incorrect
optlen size.
Optlen must be size of int.
CoreApi-10193-4: optlen too small The size of the buffer passed in was
less than the minimum buffer size
required.
Make sure the buffer is large
enough - at least LBM_MIN_SG←-
ET_OPTLEN bytes in size.
CoreApi-10193-5: optval must be
greater than or equal to 0
Attempted to set option round←-
_robin_xsp_count with an invalid
optval.
Optval must be a numeric value,
greater than or equal to 0.
CoreApi-10193-6: optval must be
greater than or equal to 0
Attempted to set option round←-
_robin_xsp_count with an invalid
optval.
Optval must be a numeric value,
greater than or equal to 0.
CoreApi-10337-1: ULB Receiver
on topic "%s" has ordered_delivery
set to 0 but this is not compat-
ible with ULB. Change value of
ordered_delivery to 1 or -1 and try
again.
Ordered delivery of 0 is not com-
patible with ULB.
You must set ordered_delivery to 0
or -1 for ULB receivers.
9.2 UM Core API Messages 155
CoreApi-10339-01: lbm_xsp_←-
register_fd: xsp must be valid
Must supply a pointer to a valid xsp The user must supply a valid xsp
CoreApi-10339-02: lbm_xsp_←-
cancel_fd: xsp must be valid
Must supply a pointer to a valid xsp The user must supply a valid xsp
CoreApi-10347-10: optlen incor-
rect size
Size of optlen was incorrect for set-
ting integer option
optlen must be size of int
CoreApi-10347-11: optval must be
0 or 1
Invalid value for optval optval must be 0 or 1
CoreApi-10347-12: optval not nu-
meric
Option string was not a number Provide number as a string
CoreApi-10347-13: optval must be
0 or 1
Invalid value for optval optval must be 0 or 1
CoreApi-10347-14: optlen incor-
rect size
Size of optlen was incorrect optlen size must be size of int
CoreApi-10347-15: optlen too
small
Size of optlen was too small Size of optlen must be at least 80
CoreApi-10347-20: optlen incor-
rect size
Size of optlen was incorrect for set-
ting integer option
optlen must be size of int
CoreApi-10347-21: optval must be
0 or 1
Invalid value for optval optval must be 0 or 1
CoreApi-10347-22: optval not nu-
meric
Option string was not a number Provide number as a string
CoreApi-10347-23: optval must be
0 or 1
Invalid value for optval optval must be 0 or 1
CoreApi-10347-24: optlen incor-
rect size
Size of optlen was incorrect optlen size must be size of int
CoreApi-10347-25: optlen too
small
Size of optlen was too small Size of optlen must be at least 80
CoreApi-10347-30: optlen incor-
rect size
Size of optlen was incorrect for set-
ting integer option
optlen must be size of int
CoreApi-10347-31: optval must be
0 or 1
Invalid value for optval optval must be 0 or 1
CoreApi-10347-32: optval not nu-
meric
Option string was not a number Provide number as a string
CoreApi-10347-33: optval must be
0 or 1
Invalid value for optval optval must be 0 or 1
CoreApi-10347-34: optlen incor-
rect size
Size of optlen was incorrect optlen size must be size of int
CoreApi-10347-35: optlen too
small
Size of optlen was too small Size of optlen must be at least 80
CoreApi-10358-01: timeout (msec)
must be zero when LBM_PROC←-
_EVENT_EX_FLAG_USER_TIME
is enabled
When setting the LBM_PROC_←-
EVENT_EX_FLAG_USER_TIME
flag, the user must set the timeout
(msec) to zero to ensure that LBM
gets needed time value updates.
Calls to lbm_context_process←-
_events_ex() need to set the
timeout to zero when the LBM_P←-
ROC_EVENT_EX_FLAG_USER←-
_TIME is set.
CoreApi-10369-10: optlen incor-
rect size
Size of optlen was incorrect for set-
ting integer option
optlen must be size of int
CoreApi-10369-11: optval must be
0 or 1
Invalid value for optval optval must be 0 or 1
CoreApi-10369-12: optval not nu-
meric
Option string was not a number Provide number as a string
CoreApi-10369-13: optval must be
0 or 1
Invalid value for optval optval must be 0 or 1
CoreApi-10369-14: optlen incor-
rect size
Size of optlen was incorrect optlen size must be size of int
156 UM Log Messages
CoreApi-10369-15: optlen too
small
Size of optlen was too small Size of optlen must be at least 80
CoreApi-10386-1: Debug message
was null [s:d]
The debug message sent through
the LBM JNI library was NULL.
Ensure that the String specified in
the Debug message is not null.
CoreApi-10386-2: Can't allocate
memory [s:d]
The LBM JNI library could not cre-
ate a message string.
This usually indicates a severe out
of memory condition.
CoreApi-10403-1000: error re-
turned from pthread_create: d
An error was returned from
pthread_create.
The error number is shown. Check
the error status for pthread_create.
CoreApi-10403-1001: error re-
turned from CreateThread: d
An error was returned from
CreateThread.
The error number is shown. Check
the error status for CreateThread.
CoreApi-10403-100: resolver_←-
service optlen incorrect size
The option size is incorrect for the
resolver_service (context) configu-
ration option
Make sure the user specifies the
correct option size: sizeof(lbm_←-
resolver_service_entry_t)
CoreApi-10403-101: resolver_←-
service optval too long
The resolver_service (context)
string setter option length is too
long
The user should check the param-
eters passed to the setter
CoreApi-10403-102: resolver_←-
service ServiceIP:RemotePort is
malformed
The resolver_service specifica-
tion string format is as follows:
ServiceIP:RemotePort where the
ServiceIP refers to the service's IP
address and the RemotePort refers
to the Services's port.
Provide a valid resolver_service
specification.
CoreApi-10403-103: resolver_←-
service optval is malformed
The resolver_service option is mal-
formed
The user needs to check the
resolver_service configuration op-
tion
CoreApi-10403-104: resolver_←-
service optval is malformed
The resolver_service (context) op-
tion is malformed
The user needs to check the
resolver_service (context) configu-
ration option
CoreApi-10403-105: resolver_←-
service optval is too small to hold
information, optlen set to required
value
The user needs to allocate enough
room for all resolver_service (con-
text) options set
The user needs to check their get
option usage
CoreApi-10403-106: resolver_←-
service optval is too small to hold
information, optlen set to required
value
The user needs to allocate enough
room for all resolver_service (con-
text) options set
The user needs to check their get
option usage
CoreApi-10403-110: resolver_←-
service option is not supported at
this time
The context option resolver_←-
service is not yet supported.
Do not use the context option
resolver_service at this time.
CoreApi-10403-111: resolver_←-
service option is not supported at
this time
The context option resolver_←-
service is not yet supported.
Do not use the context option
resolver_service at this time.
CoreApi-10403-112: resolver_←-
service option is not supported at
this time
The context option resolver_←-
service is not yet supported.
Do not use the context option
resolver_service at this time.
CoreApi-10403-113: resolver_←-
service option is not supported at
this time
The context option resolver_←-
service is not yet supported.
Do not use the context option
resolver_service at this time.
CoreApi-10403-300: The context is
configured to use a Resolver Ser-
vice which requires the respective
transport interface to be specified.
When using the Resolver Service,
the user must configure the trans-
port interface for the transport be-
ing used.
Check the configuration to make
sure the transport interface is set
for the source transport in use.
CoreApi-10403-400: lbmLicense←-
Bytes not enough buffer space to
hold u [s:d]
There was not enough buffer space
to hold the passed in binary license
key.
The maximum length to pass in is
1024. Please make sure that the
license key is in a valide buffer.
9.2 UM Core API Messages 157
CoreApi-10403-401: Can't allocate
memory for buffer of u bytes [s:d]
Memory could not be allocated for
the decode buffer.
Please free up system resources
and try the call again.
CoreApi-10403-402: License byte
array invalid [s:d]
The passed in license key was in-
valid.
The license key parser should have
more detail. See the error mes-
sage and fix the license key and try
again.
CoreApi-10489-11: lbm_←-
winevlog_thread_main(): Error
while dequeueing
Error while dequeueing from TL
queue
Contact Informatica Support.
CoreApi-10489-12: lbm_←-
winevlog_report_event(): Invalid
event level d
Invalid Windows Event Level Contact Informatica Support.
CoreApi-10489-13: lbm_←-
winevlog_report_event(): could
not ReportEvent
Windows error while sending to
event log
Contact Informatica Support.
CoreApi-10489-20: lbm_winevlog()
buffer is NULL
Error no buffers available for sub-
mitting event log messages
Contact Informatica Support.
CoreApi-10489-7: lbm_winevlog()
Couldn't grab mutex
Error waiting for mutex Contact Informatica Support.
CoreApi-10489-8: lbm_←-
winevlog(): Unable to release
mutex
Error releasing Mutex Contact Informatica Support.
CoreApi-10489-9: lbm_←-
winevlog(): Unable to release
mutex
Error releasing mutex Contact Informatica Support.
CoreApi-10492-2: address string
conversion with CIDR format (IP/←-
Mask) is not yet supported by lbm←-
_resolve_ipv4_addr_str()
IP adresses in quad-dotted nota-
tion is supported however, CIDR
(Classless Inter-Domain Routing)
IP/Mask notation is not currently
supported.
Use a different function to parse
CIDR strings
CoreApi-10528-1: ssrc must be
valid
The ssrc parameter supplied to a
smart source get available data
space call was NULL.
The ssrc parameter must be a
pointer to a valid lbm smart source
object.
CoreApi-10528-2: The smart
source p transport's maximum
datagram size is too small
The configured LBM and appli-
cation specified message headers
exceeds the transport's datagram
maximum size.
Increase the transport's data max-
imum size, or reduce the number
of message properties, or eliminate
spectrum channel.
CoreApi-10528-5: user supplied
buffer pointer is invalid
A smart source call specified a N←-
ULL user supplied buffer pointer.
Ensure that the pointer to the user
supplied buffer is valid.
CoreApi-10558-1: optlen incorrect
size
The smart_src_enable_transport←-
_compatibility value contained an
incorrect length
The smart_src_enable_transport←-
_compatibility should be of
sizeof(int)
CoreApi-10558-2: optval must be 0
or 1
The smart_src_enable_transport←-
_compatibility did not contain a
positive integer
The smart_src_enable_transport←-
_compatibility must be zero or 1
CoreApi-10558-3: optval too large The smart_src_enable_transport←-
_compatibility must be zero or 1
The smart_src_enable_transport←-
_compatibility must be zero or 1
CoreApi-10558-4: optval not nu-
meric
The smart_src_enable_transport←-
_compatibility value is not numeric
The smart_src_enable_transport←-
_compatibility must be a numeric
value of 0 or 1
CoreApi-10558-5: optval must be 0
or 1
The smart_src_enable_transport←-
_compatibility did not contain a
positive integer
The smart_src_enable_transport←-
_compatibility must be zero or 1
CoreApi-10558-6: optval too large The smart_src_enable_transport←-
_compatibility must be zero or 1
The smart_src_enable_transport←-
_compatibility must be zero or 1
158 UM Log Messages
CoreApi-10558-7: optlen incorrect
size
The size of the option was too large
or too small
The smart_src_enable_transport←-
_compatibility must be sizeof(int)
CoreApi-10558-8: optlen too small The size of the option buffer was
too small to contain the option
The smart_src_enable_transport←-
_compatibility optlen must be at
least 80
CoreApi-3288-1: optlen incorrect
size
Attempted to set wildcard receiver
attribute "hf_receiver" using the
wrong size optlen.
The parameter "optlen" must be the
size of an integer.
CoreApi-3288-2: optval must be 0
or 1
Attempted to set wildcard receiver
attribute "hf_receiver" using an in-
valid value.
The only valid values are 0 and 1.
CoreApi-3288-3: optval not nu-
meric
Attempted to set wildcard re-
ceiver attribute "hf_receiver" using
a string that is not a number.
The parameter "optval" must be a
string representation of a number.
CoreApi-3288-4: optval must be 0
or 1
Attempted to set wildcard receiver
attribute "hf_receiver" using an in-
valid value.
The only valid values are 0 and 1.
CoreApi-3288-5: optlen incorrect
size
Attempted to get wildcard receiver
attribute "hf_receiver" using the
wrong size optlen.
The parameter "optlen" must be the
size of an integer.
CoreApi-3288-6: optlen too small Attempted to get wildcard re-
ceiver attribute "hf_receiver" using
a string length that is too long.
The parameter "optlen" must be
less than 80.
CoreApi-5230-10: invalid ume←-
_message_stability_timeout_←-
behavior specified
invalid ume_message_stability_←-
timeout_behavior setting
currently the only valid setting is 0
CoreApi-5230-11: optval not nu-
meric
optval not numeric optval is not a number
CoreApi-5230-12: invalid ume←-
_message_stability_timeout_←-
behavior specified
invalid ume_message_stability_←-
timeout_behavior setting
currently the only valid setting is 0
CoreApi-5230-13: optlen incorrect
size
optlen incorrect size optlen should be of size lbm_←-
uint8_t
CoreApi-5230-14: optlen too small optlen too small optlen should be at least LBM_M←-
IN_SGET_OPTLEN
CoreApi-5230-1: optlen incorrect
size
optlen incorrect size Should have passed in a lbm_←-
uint32_t.
CoreApi-5230-2: optval not nu-
meric
optval not numeric optval must be a number.
CoreApi-5230-3: optlen incorrect
size
optlen incorrect size optlen must be a lbm_uint32_t.
CoreApi-5230-4: optlen too small optlen too small optlen should be at least LBM_M←-
IN_SGET_OPTLEN
CoreApi-5230-5: optlen incorrect
size
optlen incorrect size should have passed in a lbm_←-
uint32_t
CoreApi-5230-6: optval not nu-
meric
optval not numeric optval must be a number.
CoreApi-5230-7: optlen incorrect
size
optlen incorrect size optlen must be a lbm_uint32_t
CoreApi-5230-8: optlen too small optlen too small optlen should be at least LBM_M←-
IN_SGET_OPTLEN
CoreApi-5230-9: optlen incorrect
size
optlen incorrect size optlen should be a lbm_uint8_t
9.2 UM Core API Messages 159
CoreApi-5243-1: TCP server
socket: s
An error was returned from the OS
while trying to create a socket (T←-
CP). Refer to the OS error number
and message given after the UMS
message "TCP server socket".
CoreApi-5243-2: TCP server
listen: s
An error was returned from the OS
while trying to listen to a socket (T←-
CP). Refer to the OS error number
and message given after the UMS
message "TCP server listen".
CoreApi-5243-3: TCP server
getsockname: s
An error was returned from the OS
while trying to get the name of a
socket (TCP). Refer to the OS er-
ror number and message given af-
ter the UMS message "TCP server
getsockname".
CoreApi-5333-1: ttl value d invalid,
must be between 0 and 255.
Value passed in for resolver_←-
multicast_ttl was not a valid value.
Review the configuration file and
specify a valid value (0 - 255).
CoreApi-5402-2: src must be valid Send was called using a NULL src
pointer.
Use a valid source pointer to send
calls.
CoreApi-5402-3: exinfo flags can-
not have both HF 32 and HF 64 set
Hot failover send was called using
an exinfo that had both HF 32 and
HF 64 bit flags set.
Ensure exinfo is valid and has one
or neither HF bit size flag set before
calling send
CoreApi-5402-4: 32 bit hf src can-
not send non-32bit sequence num-
ber
A source that previously sent 32 bit
hot failover sequence numbers is
attempting to send a non-32 bit hot
failover sequence number.
Ensure that the parameter "exinfo"
has the correct HF flags set
CoreApi-5402-5: 64 bit hf src can-
not send non-64bit sequence num-
ber
A source that previously sent 64 bit
hot failover sequence numbers is
attempting to send a non-64 bit hot
failover sequence number.
Ensure that the parameter "exinfo"
has the correct HF flag set
CoreApi-5434-1: Can't allocate
memory [s:d]
UMQ ran out of memory while cre-
ating a queue name string.
CoreApi-5434-2: Can't allocate
memory [s:d]
UMQ ran out of memory while cre-
ating a queue message list callback
object.
CoreApi-5434-3: Can't allocate
memory [s:d]
UMQ ran out of memory while cre-
ating a queue name string.
CoreApi-5434-4: Can't allocate
memory [s:d]
UMQ ran out of memory while cre-
ating a queue message retrieve
callback object.
CoreApi-5434-5: Could not create
source string [s:d]
UMQ ran out of memory while cre-
ating a source string.
CoreApi-5434-6: Could not create
topic string [s:d]
UMQ ran out of memory while cre-
ating a topic string.
CoreApi-5434-7: Can't allocate
memory [s:d]
UMQ ran out of memory while cre-
ating a queue name string.
CoreApi-5434-8: Can't allocate
memory [s:d]
UMQ ran out of memory while cre-
ating a queue topic list callback ob-
ject.
CoreApi-5480-10: could not create
inactive_loss_rec_queue [s:d]
Internal error while attempting to
create an internal data structure.
Most likely the result of insufficient
memory.
Contact Informatica support.
160 UM Log Messages
CoreApi-5480-11: could not create
active_loss_rec_queue [s:d]
Internal error while attempting to
create an internal data structure.
Most likely the result of insufficient
memory.
Contact Informatica support.
CoreApi-5480-12: could not create
unavailable_loss_rec_queue [s:d]
Internal error while attempting to
create an internal data structure.
Most likely the result of insufficient
memory.
Contact Informatica support.
CoreApi-5480-13: rxr_ctlr destina-
tion list is NULL
Internal error. Specified rxr_ctlr has
not been fully created.
Contact Informatica support.
CoreApi-5480-14: lbm_rxr_←-
request_t already cancelled
Internal error. Attempted duplicate
request cancellation.
Contact Informatica support.
CoreApi-5480-15: unable to insert
loss_rec into loss_rec_map
Internal error while attempting to
create an internal data structure.
Most likely the result of insufficient
memory.
Contact Informatica support.
CoreApi-5480-16: unable to in-
sert loss_rec into inactive loss rec
queue
Internal error while attempting to
create an internal data structure.
Most likely the result of insufficient
memory.
Contact Informatica support.
CoreApi-5480-17: unable to in-
sert loss_rec into inactive loss rec
queue
Internal error while attempting to
create an internal data structure.
Most likely the result of insufficient
memory.
Contact Informatica support.
CoreApi-5480-18: unable to insert
loss_rec into loss_rec_map
Internal error while attempting to
create an internal data structure.
Most likely the result of insufficient
memory.
Contact Informatica support.
CoreApi-5480-19: unable to in-
sert loss_rec into inactive loss rec
queue
Internal error while attempting to
create an internal data structure.
Most likely the result of insufficient
memory.
Contact Informatica support.
CoreApi-5480-20: unable to in-
sert loss_rec into inactive loss rec
queue
Internal error while attempting to
create an internal data structure.
Most likely the result of insufficient
memory.
Contact Informatica support.
CoreApi-5480-21: unable to in-
sert loss_rec into inactive loss rec
queue
Internal error while attempting to
create an internal data structure.
Most likely the result of insufficient
memory.
Contact Informatica support.
CoreApi-5480-22: unable to in-
sert loss_rec into inactive loss rec
queue
Internal error while attempting to
create an internal data structure.
Most likely the result of insufficient
memory.
Contact Informatica support.
CoreApi-5480-23: unable to insert
loss_rec into loss rec queue
Internal error while attempting to
create an internal data structure.
Most likely the result of insufficient
memory.
Contact Informatica support.
CoreApi-5480-24: unable to in-
sert loss_rec into inactive loss rec
queue
Internal error while attempting to
create an internal data structure.
Most likely the result of insufficient
memory.
Contact Informatica support.
CoreApi-5480-25: unable to
reschedule rxr_ctlr timer
Internal error while attempting to
create an internal data structure.
Most likely the result of insufficient
memory.
Contact Informatica support.
9.2 UM Core API Messages 161
CoreApi-5480-26: unable to insert
loss_rec into unavailable loss rec
queue
Internal error while attempting to
create an internal data structure.
Most likely the result of insufficient
memory.
Contact Informatica support.
CoreApi-5480-27: could not create
loss ASL [s:d]
Internal error while attempting to
create an internal data structure.
Most likely the result of insufficient
memory.
Contact Informatica support.
CoreApi-5480-28: could not insert
rcvdc_loss_rec ASL map [s:d]
Internal error while handling a de-
tected gap in data.
Contact Informatica support.
CoreApi-5480-5: unable to insert
o_entry into omap->asl
Internal error while attempting to
handle an out of order message.
Contact Informatica support.
CoreApi-5480-7: unable to insert
o_entry into omap->asl
Internal error while attempting to
handle detected loss.
Contact Informatica support.
CoreApi-5480-8: min_←-
unavailable_delay must be smaller
than the request_generation_ivl
Internal error while creating an
rxr_ctlr. Should never happen.
Contact Informatica support.
CoreApi-5480-9: could not create
rxr_loss_rec_map ASL [s:d]
Internal error while attempting to
create an internal data structure.
Most likely the result of insufficient
memory.
Contact Informatica support.
CoreApi-5539-1: Can't allocate
per-send object node; message not
sent [s:d]
Could not set up source per send
data in jni when calling HF send re-
set.
Ensure that correct exinfo is being
used and that sufficient memory is
available.
CoreApi-5688-1246: session id not
a number
The provided session ID was in-
valid.
Specify a session ID that fits one of
the following formats: A hexadec-
imal value prefixed by 0x, an oc-
tal value prefixed by 0, or a dec-
imal value. The value must be
smaller than 0xFFFFFFFFFFFFF←-
FFF regardless of representation.
CoreApi-5688-1390: session id not
a number
The provided session ID was in-
valid.
Specify a session ID that fits one of
the following formats: A hexadec-
imal value prefixed by 0x, an oc-
tal value prefixed by 0, or a dec-
imal value. The value must be
smaller than 0xFFFFFFFFFFFFF←-
FFF regardless of representation.
CoreApi-5688-1885: opmode must
be sequential
This is an invalid use of the
lbm_context_process_events()
or lbmContextProcessEvents().
Calling lbm_context_process_←-
events() or lbmContextProcess←-
Events() for a context running in
embedded mode. This will simply
print the log message and return
immediately.
lbm_context_process_events()
or lbmContextProcessEvents()
should get called only for se-
quential mode. See the UM
Configuration Guide for high level
guidance on configuring Ultra
Messaging objects.
CoreApi-5688-2014: optval not nu-
meric
Value passed in for resolver_←-
multicast_ttl was not numeric.
Review the configuration file and
specify a valid numeric value for the
option (0 - 255).
162 UM Log Messages
CoreApi-5688-2767: session id not
a number
The provided session ID was in-
valid.
Specify a session ID that fits one of
the following formats: A hexadec-
imal value prefixed by 0x, an oc-
tal value prefixed by 0, or a dec-
imal value. The value must be
smaller than 0xFFFFFFFFFFFFF←-
FFF regardless of representation.
CoreApi-5688-2859: context name
too long
The supplied context name is in-
valid because it is too long.
Context names must not exceed
128 characters in length.
CoreApi-5688-2874: optval is mal-
formed
The unicast resolver daemon spec-
ification string format is as follows:
[Interface[:LocalPort]->]Daemon←-
IP:RemotePort where Interface
and LocalPort refer the local host
interface and port, the DaemonIP
refers to the resolver daemon's
IP address, and the RemotePort
refers to the resolver daemon's
UDP port.
Provide a valid resolver daemon
specification.
CoreApi-5688-2875: optval is mal-
formed
The unicast resolver daemon spec-
ification string format is as follows:
[Interface[:LocalPort]->]Daemon←-
IP:RemotePort where Interface
and LocalPort refer the local host
interface and port, the DaemonIP
refers to the resolver daemon's
IP address, and the RemotePort
refers to the resolver daemon's
UDP port.
Provide a valid resolver daemon
specification.
CoreApi-5688-3040: Can not spec-
ify a negative number for inflight
messages
Attempting to set the flight size of
messages to a negative number
Ensure a positive integer for inflight
messages is returned from the set
flight size callback
CoreApi-5688-3041: Cannot spec-
ify a negative number for inflight
messages
Attempting to set the flight size of
messages to a negative number
Ensure a positive integer for inflight
messages is returned from the set
flight size callback
CoreApi-5688-3043: inflight must
be valid
inflight parameter was NULL inflight must be a valid pointer
CoreApi-5688-3139: Round-Robin
must have no groups specified
Store groups have been specified,
but the ume_store_behavior option
is set to Round-Robin.
Change the ume_store_behavior
option to quorum-consensus or
remove any settings specifying
ume_store_group.
CoreApi-5688-3140: Store u has
invalid address
INADDR_ANY (0.0.0.0) was set for
the ume_store configuration option.
Specify a valid IP address as con-
figured in the umestored daemon's
config file.
CoreApi-5688-3151: Group u does
not have enough stores specified
UMP source configured "source
ume_store_group GroupIDX:←-
GroupSZ" with certain number of
GroupSZ (stores) but did not spec-
ify enough stores for GroupIDX
with the "source ume_store_←-
name" or "source ume_store"
configuration options.
Correct configuration file to match
the GroupSZ with the actual num-
ber of stores specified for that
GroupIDX.
9.2 UM Core API Messages 163
CoreApi-5688-3226: TCP server
socket: s
An error was returned from the OS
while trying to create a socket (T←-
CP). Refer to the OS error number
and message given after the U←-
MS message "could not create T←-
CP server socket".
CoreApi-5688-3227: TCP server
SO_REUSEADDR: s
An error was returned from the OS
while trying to set option of a socket
(TCP). Refer to the OS error num-
ber and message given after the
UMS message "TCP server SO←-
_REUSEADDR".
CoreApi-5688-3229: TCP server
SO_EXCLUSIVEADDR: s
An error was returned from the OS
while trying to set option of a socket
(TCP). Refer to the OS error num-
ber and message given after the
UMS message "TCP server SO←-
_EXCLUSIVEADDR".
CoreApi-5688-3230: could not find
open TCP server port in range [d-d]
An error was returned from the OS
while trying to bind a socket (T←-
CP). This error indicates that there
are no free ports in the range of
ports denoted by the transport_←-
tcp_port_low and transport_tcp_←-
port_high configuration options.
If the range of ports is small, con-
sider increasing the range of ports
available to this UM application by
making the appropriate configura-
tion changes. If the range of ports
is large, consider moving some ap-
plications which use ports in this
port range to another system.
CoreApi-5688-3231: TCP server
bind (port=d): s
An error was returned from the OS
while trying to bind a socket (T←-
CP). This error indicates that the
port specified by the transport_←-
tcp_port configuration option is in
use.
If this error was encountered on
a restart, consider specifying tcp←-
_reuseaddr (Windows users are
recommended to the configuration
guide for transport_tcp_reuseaddr
(source))
CoreApi-5688-3232: TCP server
getsockname: s
An error was returned from the OS
while trying to get the name of a
socket (TCP). Refer to the OS er-
ror number and message given af-
ter the UMS message "TCP server
getsockname".
CoreApi-5688-3233: TCP server
listen: s
An error was returned from the OS
while trying to listen to a socket (T←-
CP). Refer to the OS error number
and message given after the UMS
message "TCP server listen".
CoreApi-5688-3268: multicast re-
ceive bind (port = d, multicast
group = s): s
An error occurred while trying to
bind to the requested ip and port.
The last part of this message con-
tains the OS error code and asso-
ciated text.
Consult your OS documentation
for resolutions based on the error
code.
CoreApi-5688-3287: could not find
open unicast source port in range
[d-d]
Could not bind to a unicast port due
to ports already being used in the
given range.
Update the UM configuration file
to modify or include different ports
for the options transport_lbtrm_←-
source_port_low and/or transport←-
_lbtrm_source_port high.
CoreApi-5688-3320: lbm_socket←-
_recv recv/recvfrom: s
An error was returned from the
OS while trying a recv or recvfrom
socket call. Refer to the OS error
number and message.
164 UM Log Messages
CoreApi-5688-3337: lbm_socket←-
_sendb send/sendto: s
An error occurred while sending.
The message will contain addition
specific information, supplied by
the operating system.
This is a platform specific error;
please use the operating system's
error code and description to fur-
ther understand the circumstances
of the error.
CoreApi-5688-3468: could not find
the given source transport session.
The transport session for which
statistics were requested is no
longer valid.
The receiving application should
monitor the LBM_MSG_EOS mes-
sage for EOS on the transport ses-
sion. EOS indicates the transport
session is no longer valid. Please
see KB 234278 for a more detailed
explanation.
CoreApi-5688-3545: wildcard pat-
tern type d not supported
The specified pattern type for the
wildcard receiver was invalid.
Refer to pattern_type in the config-
uration guide, set the appropriate
value and retry the application.
CoreApi-5688-3772: FD event al-
ready defined
Trying to register a handle with
event flag(s) (LBM_FD_EVENT_←-
∗) already registered for that same
handle.
If using lbm_register_fd/lbm_←-
cancel_fd APIs in UM application,
review usage logic. Otherwise,
contact Informatica support.
CoreApi-5688-4087: XML configu-
ration has already been loaded.
An XML configuration has already
been loaded via UMM and can not
be overridden by loading a different
XML configuration.
Modify the application to not at-
tempt to load a second XML con-
figuration.
CoreApi-5688-4092: XML configu-
ration has already been loaded.
An XML configuration has already
been loaded via UMM and can not
be overridden by loading a different
XML configuration.
Modify the application to not at-
tempt to load a second XML con-
figuration.
CoreApi-5688-4093: error parsing
XML data
The XML configuration received
from UMM could not be parsed.
Previous error messages should
contain the reason for the error.
Correct the configuration in UMM
and retry the application.
CoreApi-5688-4094: error parsing
application name 's'
The XML configuration for the ap-
plication received from UMM could
not be parsed.
Previous error messages should
contain the reason for the error.
Correct the configuration in UMM
and retry the application.
CoreApi-5688-4110: no default
multicast interface available
Application exits when multicast in-
terface is not specified in configura-
tion file.
To avoid the application exiting, a
default multicast interface must be
specified and if there is none, set-
ting it to 127.0.0.1 allows the appli-
cation to continue to work.
CoreApi-5688-4243: lbm_src_←-
topic_attr_" #name "_set:s
An error was returned when an at-
tempt was made to set an attribute.
The error message returned is in-
cluded in the text of this message.
CoreApi-5688-4251: could not in-
sert lbm_umq_rcvdc_t rcv list ASL
[s:d]
Internal error while inserting a new
receiver into the receiver ASL list.
Contact Informatica support.
CoreApi-5688-4554: Can't allocate
memory [s:d]
The LBM JNI library could not allo-
cate a string object.
This usually indicates a severe out
of memory condition.
CoreApi-5688-606: LBT-IPC: failed
to allocate shared memory (d)
A shared memory object for the I←-
PC transport could not be created.
This could be caused by a permis-
sion error or no more resources.
Please refer to the OS error num-
ber given.
9.2 UM Core API Messages 165
CoreApi-5688-608: LBT-IPC: failed
to map shared memory (d)
An error occurred trying to map a
pointer to the IPC shared memory
region. Please refer to the OS error
number given.
CoreApi-5688-610: LBT-IPC: can
not initialize shared semaphore (d)
An error occurred when initializ-
ing the shared semaphore used to
ensure mutual exclusion while ac-
cessing the IPC shared memory re-
gion. Please refer to the OS error
number given.
CoreApi-5688-611: LBT-IPC: failed
to allocate shared memory (d)
A shared memory object for the I←-
PC transport could not be created.
This could be caused by a permis-
sion error or no more resources.
Please refer to the OS error num-
ber given.
CoreApi-5688-612: LBT-IPC: failed
to map shared memory (d)
An error occurred trying to map a
pointer to the IPC shared memory
region. Please refer to the OS error
number given.
CoreApi-5688-613: LBT-IPC: can
not create shared Mutex (d)
The shared Mutex used to ensure
mutual exclusion while accessing
the IPC shared memory region
could not be created. Please refer
to the OS error number given.
CoreApi-5688-64: config file: s line
d: s
The supplied configuration option is
not recognized by the system.
UM executes a case insensitive
comparison for an exact match of
configuration options. Check for
correct spelling and proper use of
underscore characters.
CoreApi-5688-706: Not currently
registered with enough UME stores
The source tried to send a mes-
sage while not registered with a
quorum of stores.
Monitor the source_event_function
for changes in quorum status.
Please see KB article 304595 for
more details.
CoreApi-5688-708: UMQ queue is
marked inactive
Every source and receiver period-
ically checks that every queue it
is registered with is still active, by
checking if it has received a recent
advertisement from the queue. If
the activity timeout for the queue
is exceeded before an advertise-
ment is received and checked by
the source, the source will mark
the queue as inactive, and will
no longer attempt to publish mes-
sages to that queue until it be-
comes active again.
Check why the source has not
marked that is has received an ad-
vertisement. It could be a delay on
the queue, on the network, or on
the source itself.
CoreApi-5760-1: receiver must be
an observer receiver (set umq_←-
queue_participation to 2)
lbm_rcv_umq_queue_msg_←-
retrieve was called using a normal
receiver for the rcv parameter.
Only observer receivers (receivers
with the "receiver umq_queue_←-
participation" option set to "2") may
be used with this API.
166 UM Log Messages
CoreApi-5760-2: receiver must be
an observer receiver (set umq_←-
queue_participation to 2)
lbm_rcv_umq_queue_msg_←-
list was called using a normal
receiver for the rcv parameter.
Only observer receivers (receivers
with the "receiver umq_queue_←-
participation" option set to "2") may
be used with this API.
CoreApi-5867-14: error occurred
parsing message selector string
<s>
The message selector string is in-
valid or could not be parsed.
Check the UM Documenation for
valid syntax.
CoreApi-5867-15: error occurred
evaluating message selector string
due to unknown property type [d]
for property [s]
Message property type was invalid. Verify that the message properties
have not been corrupted.
CoreApi-5867-16: rcv cannot be
configured with both message se-
lector and spectrum channel be-
havior
A receiver was configured with both
a message selector and channel
behavior
Remove either the message selec-
tor or the channel behavior from the
receiver attributes
CoreApi-5867-17: rcv cannot be
configured with both message se-
lector and spectrum channel
A receiver was configured with both
a message selector and channel
Remove either the message selec-
tor or the channel
CoreApi-5867-18: rcv cannot be
configured with both message se-
lector and spectrum channel be-
havior
A receiver was configured with both
a message selector and channel
behavior
Remove either the message selec-
tor or the channel behavior from the
receiver attributes
CoreApi-5867-1: optval must not
be NULL
The optval passed in was a NULL
pointer.
Ensure NULL is not passed as the
value of the optval pointer because
this is where the data will be copied
CoreApi-5867-2: optlen must not
be NULL
The optlen passed in was a NULL
pointer.
Ensure NULL is not passed as the
value of the optlen pointer because
this is needed to make sure the
data can be copied
CoreApi-5867-3: optval is not long
enough
Based on the optlen passed in, the
data cannot be copied into optval
due to its size
Ensure optval is large enought to
hold the data (check the update
optlen for the needed size)
CoreApi-6001-10: async operation
canceled because connection with
queue was lost
An outstanding asynchronous op-
eration was canceled because the
connection with the queue was lost,
rendering the outstanding async
operation unlikely to ever complete
on its own.
This is normal behavior if a queue
has been brought down on pur-
pose; otherwise, check to see if
the queue is overloaded and unre-
sponsive or if there is a connectivity
problem between the client applica-
tion and the queue.
CoreApi-6001-11: could not al-
locate lbm_umq_rcvdc_t waiting
command list [s:d]
The UMQ delivery controller's wait-
ing command list could not be cre-
ated.
This usually indicates severe re-
source exhaustion; check for out of
memory errors.
CoreApi-6001-1: optlen incorrect
size
The size of the option passed in is
not the correct size for this option.
This is usually a coding mistake;
check that the correct type is being
used for this option.
CoreApi-6001-2: optval must be
greater than 0
The UMQ command outstanding
max passed in was 0, which is not
a valid value.
Make sure the value given is >0.
CoreApi-6001-3: UMQ command
outstanding max not a number
The string representing the UMQ
command outstanding max could
not be parsed to find a number.
Check the string being passed in,
make sure it's a number >0.
CoreApi-6001-4: optval must be
greater than 0
The string representing the UMQ
command outstanding max was 0,
which is not a valid value.
Check the string being passed in,
make sure it's a number >0.
9.2 UM Core API Messages 167
CoreApi-6001-5: optlen incorrect
size
The size of the option passed in is
not the correct size for this option.
This is usually a coding mistake;
check that the correct type is being
used for this option.
CoreApi-6001-6: optlen too small The size of the buffer passed in was
less than the minimum buffer size
required.
Make sure the buffer is large
enough - at least LBM_MIN_SG←-
ET_OPTLEN bytes in size.
CoreApi-6001-7: could not allocate
lbm_umq_queue_t waiting cmd ID
list [s:d]
UMS could not allocate a queue
controller waiting command list.
This probably means malloc failed
or the system is otherwise out of re-
sources.
This is likely the result of severe
resource exhaustion; contact Infor-
matica support.
CoreApi-6001-8: could not insert
lbm_umq_queue_t CMD WAITING
LIST [s:d]
A waiting command could not be
enqueued onto the queue's waiting
command list.
This is a severe problem and usu-
ally indicates resource exhaustion;
check for out of memory conditions.
CoreApi-6001-9: could not insert
lbm_umq_queue_t CMD ASL [s:d]
Attemping to take a waiting com-
mand off the waiting command list
and put it in the active commands
list failed.
This usually indicates resource ex-
haustion; check for out of memory
conditions.
CoreApi-6020-10: Cannot increase
inflight messages or bytes while
decreasing the other
Attempting to increase the flight
size messages or bytes and de-
crease the other.
Ensure that the inflight set callback
returns a valid inflight structure, or
call the method twice to set each
one individually.
CoreApi-6020-11: Cannot increase
inflight messages or bytes while
decreasing the other
Attempting to increase the flight
size messages or bytes and de-
crease the other.
Ensure that the inflight set callback
returns a valid inflight structure, or
call the method twice to set each
one individually.
CoreApi-6020-12: Payload ex-
ceeds flight size bytes maximum,
can not send.
Attempted to send a single mes-
sage with payload length greater
than the configured maximum al-
lowed limit
Send smaller messages or in-
crease source ume_flight_size_←-
bytes
CoreApi-6020-13: inflight parame-
ter must be a valid pointer
inflight parameter was NULL inflight must be a valid pointer
CoreApi-6020-14: RPP sources
must also configure a non-zero
value for ume_flight_size_bytes
Attempted to create a RPP enabled
source without specifying a valid
flight size bytes
Set "source ume_flight_size_←-
bytes" to be non-zero
CoreApi-6020-1: optlen incorrect
size
optlen parameter is not the correct
size
optlen should be the size of an
lbm_uint64_t
CoreApi-6020-2: opval not numeric optval parameter was not a string
representation of a number
Ensure that the optval string is a
unsigned number
CoreApi-6020-3: optval not a num-
ber
optval parameter was not a string
representation of a number
Ensure that the optval string is a
unsigned number
CoreApi-6020-4: optlen incorrect
size
optlen parameter is not the correct
size
optlen should be size of lbm_←-
uint64_t
CoreApi-6020-5: optlen too small optlen parameter too small Increase optlen size
CoreApi-6020-8: exinfo properties
must be valid when LBM_SRC_S←-
END_EX_FLAG_PROPERTIES is
set
Attempted send with message
properties flag set, but exinfo-
>properties was NULL
Turn off message properties flag or
set exinfo->properties correctly.
CoreApi-6020-9: Payload exceeds
flight size bytes maximum, unable
to send.
Attempted to send a single mes-
sage with payload length greater
than the maximum limit while using
UMP flight size blocking behavior
Send smaller messages or in-
crease source ume_flight_size_←-
bytes
168 UM Log Messages
CoreApi-6034-2: session id not a
number
The provided session ID was in-
valid.
Specify a session ID that fits one of
the following formats: A hexadec-
imal value prefixed by 0x, an oc-
tal value prefixed by 0, or a dec-
imal value. The value must be
smaller than 0xFFFFFFFFFFFFF←-
FFF regardless of representation.
CoreApi-6111-0: optlen incorrect
size
optlen is not the correct size optlen should be the size of a lbm←-
_uint8_t
CoreApi-6111-10: optlen too small optlen too small optlen should be at least LBM_M←-
IN_SGET_OPTLEN
CoreApi-6111-11: optlen incorrect
size
optlen too small optlen should be size_t
CoreApi-6111-12: optval not nu-
meric
optval is not numeric optval needs to be numeric
CoreApi-6111-13: optval not a
number
optval not a number optval needs to be a number
CoreApi-6111-14: optlen incorrect
size
optlen incorrect size optlen should be size_t
CoreApi-6111-15: optlen too small optlen too small optlen should be at least LBM_M←-
IN_SGET_OPTLEN
CoreApi-6111-16: optlen incorrect
size
optlen incorrect size optlen should be of size lbm_←-
uint64_t
CoreApi-6111-17: optval not nu-
meric
optval not numeric optval should be numeric
CoreApi-6111-18: optval not a
number
optval not a number optval needs to be a number
CoreApi-6111-19: optlen incorrect
size
optlen incorrect size optlen incorrect size.. should be a
lbm_uint64_t
CoreApi-6111-1: invalid ume←-
_receiver_paced_persistence set-
ting
Invalid setting for rpp Valid settings are 0 and 1
CoreApi-6111-20: optlen too small optlen too small optlen should be LBM_MIN_SGE←-
T_OPTLEN
CoreApi-6111-21: optlen incorrect
size
optlen incorrect size optlen should be lbm_uint32_t
CoreApi-6111-22: optval not nu-
meric
optval not numeric optval is not a number
CoreApi-6111-23: optlen incorrect
size
optlen incorrect size optlen should be lbm_uint32_t
CoreApi-6111-24: optlen too small optlen too small optlen should be at least LBM_M←-
IN_SGET_OPTLEN
CoreApi-6111-25: optlen incorrect
size
optlen incorrect size optlen should be size of lbm_←-
uint8_t
CoreApi-6111-26: invalid ume←-
_repository_ack_on_reception set-
ting
invalid ume_repository_ack_on_←-
recepeption setting
value should be 0 or 1
CoreApi-6111-27: optval not nu-
meric
optval not numeric optval is not a number
CoreApi-6111-28: invalid ume←-
_repository_ack_on_reception set-
ting
invalid ume_repository_ack_on_←-
reception setting
optval should be 0 or 1
CoreApi-6111-29: optlen incorrect
size
optlen incorrect size optlen should be of size lbm_←-
uint8_t
CoreApi-6111-2: optval not nu-
meric
optval is not numeric optval must be numeric
9.2 UM Core API Messages 169
CoreApi-6111-30: optlen too small optlen too small optlen should be at least LBM_M←-
IN_SGET_OPTLEN
CoreApi-6111-31: optlen incorrect
size
size of the option is incorrect optlen must be a lbm_uint8_t
CoreApi-6111-32: invalid ume←-
_receiver_paced_persistence set-
ting
ume_receiver_paced_persistence
set to invalid value
ume_receiver_paced_persistence
must be 0 - 2
CoreApi-6111-33: optval not nu-
meric
optval is not a number optval needs to be numeric only
CoreApi-6111-34: invalid ume←-
_receiver_paced_persistence set-
ting
ume_receiver_paced_persistence
set to invalid value
ume_receiver_paced_persistence
must be 0 - 2
CoreApi-6111-35: optlen incorrect
size
optlen is not a lbm_uint8_t optlen should be a lbm_uint8_t
CoreApi-6111-36: optlen too small optlen is too small optlen needs to be at least 80
CoreApi-6111-3: invalid ume←-
_receiver_paced_persistence set-
ting
optval not a valid value optval must be 0 or 1
CoreApi-6111-4: optlen incorrect
size
optval is incorrect size optval must be a lbm_uint8_t size
CoreApi-6111-5: optlen too small optlen is too small optlen must be at least LBM_MIN←-
_SGET_OPTLEN
CoreApi-6111-6: optlen incorrect
size
optlen incorrect size optlen must be a size_t
CoreApi-6111-7: optval not nu-
meric
optval is not numeric optval must be a number
CoreApi-6111-8: optval not a num-
ber
optval is not a number optval needs to be a number
CoreApi-6111-9: optlen incorrect
size
optlen incorrect size optlen should be a size_t
CoreApi-6117-100: rcv must be
valid
lbm_rcv_ume_deregister was
called with a null rcv.
Don't deregister your receiver after
you've deleted it.
CoreApi-6117-101: not registered
with any stores.
Tried to deregister from stores
when you were never registered
with any.
Don't call deregister if you've never
registered to any stores.
CoreApi-6186-1: ctx must be valid Passed NULL for lbm_context_←-
t∗argument of lbm_deserialize_←-
response API.
lbm_deserialize_response API
lbm_context_t∗argument must not
be NULL.
CoreApi-6186-2: serialized re-
sponse must be valid
Passed NULL for lbm_serialized←-
_response_t∗argument of lbm_←-
deserialize_response API.
lbm_deserialize_response A←-
PI lbm_serialized_response_t∗
argument must not be NULL.
CoreApi-6254-20: Can't allocate
memory [s:d]
UMQ ran out of memory while cre-
ating a message selector string.
CoreApi-6254-21: Can't allocate
memory [s:d]
UMQ ran out of memory while cre-
ating a message selector.
CoreApi-6259-17: Unicast Imme-
diate Message failed: cannot find
route to Remote Domain: u:s:d
There is no known route to the
given domain. This could hap-
pen momentarily as an LBM con-
text learns the domain routes at
startup.
If the warning persists, the Gate-
way configuration should be exam-
ined for inconsistencies.
CoreApi-6259-18: Unicast Imme-
diate Request failed: cannot find
route to Remote Domain: u:s:d
There is no known route to the
given domain. This could hap-
pen momentarily as an LBM con-
text learns the domain routes at
startup.
If the warning persists, the Gate-
way configuration should be exam-
ined for inconsistencies.
170 UM Log Messages
CoreApi-6273-1: Cannot enable
RPP with round-robin stores
Cannot enable receiver-paced per-
sistence with round-robin stores
Only use Q/C with RPP
CoreApi-6298-1: src could not
deregister from store
source failed trying to deregister
from a store.
try again, unicast control channel
between source and store may be
down
CoreApi-6298-2: src is already
deregistering from the stores
source is already deregistered. don't call lbm_src_ume_deregister
multiple times passing in the same
source.
CoreApi-6435-1: msg must be
valid
Message Pointer is NULL
CoreApi-6435-2: msg has no frag-
ment information
Message doesn't have any frag-
ment information
CoreApi-6452-10: optval must 0 or
1
The auto_create_transaction_mgr
passed in value was not 0 or 1,
which is not a valid value.
Make sure the value given is 0 or 1.
CoreApi-6452-11: auto_create_←-
transaction_mgr optval must 0 or 1
The string representing the auto←-
_create_transaction_mgr could not
be parsed to find a number.
Check the string being passed in,
make sure it's a number 0 or 1.
CoreApi-6452-12: auto_create_←-
transaction_mgr optval must be 0
or 1
The string representing the auto←-
_create_transaction_mgr was not 0
or 1, which is not a valid value.
Check the string being passed in,
make sure it's a number 0 or 1.
CoreApi-6452-13: optlen incorrect
size
The size of the option passed in is
not the correct size for this option.
This is usually a coding mistake;
check that the correct type is being
used for this option.
CoreApi-6452-14: optval must be
between 0 or 3
The transaction_mgr_role passed
in value was not between 0 and 3,
which is not a valid value.
Make sure the value given between
0 and 3.
CoreApi-6452-15: optlen incorrect
size
The string representing the
transaction_mgr_role could not
be parsed.
Check the string being passed in,
make sure it's one of the following←-
: PROPOSER, ACCEPTOR, LE←-
ARNER, NONE
CoreApi-6452-16: optlen incorrect
size
The size of the option passed in is
not the correct size for this option.
This is usually a coding mistake;
check that the correct type is being
used for this option.
CoreApi-6452-17: optlen too small The size of the buffer passed in was
less than the minimum buffer size
required.
Make sure the buffer is large
enough - at least LBM_MIN_SG←-
ET_OPTLEN bytes in size.
CoreApi-6452-18: optlen incorrect
size
The size of the option passed in is
not the correct size for this option.
This is usually a coding mistake;
check that the correct type is being
used for this option.
CoreApi-6452-19: optval must be
between 0 or 2
The transaction_mgr_type passed
in value was between 0 and 2,
which is not a valid value.
Make sure the value given be be-
tween 0 and 2.
CoreApi-6452-20: optlen incorrect
size
The string representing the
transaction_mgr_type could not be
parsed.
Check the string being passed in,
make sure it's one of the following←-
: PROPOSER, ACCEPTOR, LE←-
ARNER, NONE
CoreApi-6452-21: optlen incorrect
size
The size of the option passed in is
not the correct size for this option.
This is usually a coding mistake;
check that the correct type is being
used for this option.
CoreApi-6452-22: optlen too small The size of the buffer passed in was
less than the minimum buffer size
required.
Make sure the buffer is large
enough - at least LBM_MIN_SG←-
ET_OPTLEN bytes in size.
CoreApi-6452-3: optlen too small Invalid Attribute Change attribute to a valide value.
CoreApi-6452-4: optlen incorrect
size
Invalid Attribute Change attribute to a valide value.
9.2 UM Core API Messages 171
CoreApi-6452-5: optval must be -1,
0 or 1
Invalid Attribute Change attribute to a valide value.
CoreApi-6452-6: optval not nu-
meric
Invalid Attribute Change attribute to a valide value.
CoreApi-6452-7: optval must be -1,
0 or 1
Invalid Attribute Change attribute to a valide value.
CoreApi-6452-8: optlen incorrect
size
Invalid Attribute Change attribute to a valide value.
CoreApi-6452-9: optlen incorrect
size
The size of the option passed in is
not the correct size for this option.
This is usually a coding mistake;
check that the correct type is being
used for this option.
CoreApi-6755-1: ip string is mal-
formed
The ip string passed into ume_←-
store is malformed.
The ume_store ip_string must be in
an a.b.c.d dotted decimal format.
CoreApi-6759-12: context name
too long
The supplied context name is in-
valid because it is too long.
Context names must not exceed
128 characters in length.
CoreApi-6759-13: optlen incorrect
size
The oplen parameter is incorrect. Optlen must be sizeof(lbm_ulong←-
_t).
CoreApi-6759-14: optval not nu-
meric
Optval is not numeric. The optval string must consist of
numbers only.
CoreApi-6759-15: optlen incorrect
size
The oplen parameter is incorrect. Optlen must be sizeof(lbm_ulong←-
_t).
CoreApi-6759-16: optlen too small Optlen is too small. Optlen should be at least LBM_M←-
IN_SGET_OPTLEN.
CoreApi-6759-17: optlen incorrect
size
The oplen parameter is incorrect. Optlen must be sizeof(lbm_ulong←-
_t).
CoreApi-6759-18: optval not nu-
meric
Optval is not numeric. The optval string must consist of
numbers only.
CoreApi-6759-19: optlen incorrect
size
The oplen parameter is incorrect. Optlen must be sizeof(lbm_ulong←-
_t).
CoreApi-6759-20: optlen too small Optlen is too small. Optlen should be at least LBM_M←-
IN_SGET_OPTLEN.
CoreApi-6759-21: optlen incorrect
size
The oplen parameter is incorrect. Optlen must be sizeof(lbm_←-
uint64_t).
CoreApi-6759-22: optval not nu-
meric
Optval is not numeric. The optval string must consist of
numbers only.
CoreApi-6759-23: optval not a valid
value
Optval is not numeric. The optval string must consist of
numbers only and fit in a 64 bit
value.
CoreApi-6759-24: optlen incorrect
size
The oplen parameter is incorrect. Optlen must be sizeof(lbm_←-
uint64_t).
CoreApi-6759-25: optlen too small Optlen is too small. Optlen should be at least LBM_M←-
IN_SGET_OPTLEN.
CoreApi-6759-26: optlen incorrect
size
The oplen parameter is incorrect. Optlen must be sizeof(lbm_←-
uint64_t).
CoreApi-6759-27: optval not nu-
meric
Optval is not numeric. The optval string must consist of
numbers only.
CoreApi-6759-28: optval not a valid
value
Optval is not numeric. The optval string must consist of
numbers only and must fit in a 64
bit value.
CoreApi-6759-29: optlen incorrect
size
The oplen parameter is incorrect. Optlen must be sizeof(lbm_←-
uint64_t).
CoreApi-6759-30: optlen too small Optlen is too small. Optlen should be at least LBM_M←-
IN_SGET_OPTLEN.
CoreApi-6856-10: optlen incorrect
size
optlen incorrect size optlen should be lbm_uint32_t
172 UM Log Messages
CoreApi-6856-11: optval not nu-
meric
optval not numeric optval is not a number
CoreApi-6856-12: optlen incorrect
size
optlen incorrect size optlen should be lbm_uint32_t
CoreApi-6856-13: optlen too small optlen too small optlen should be at least LBM_M←-
IN_SGET_OPTLEN
CoreApi-6856-2: optlen incorrect
size
optlen incorrect size optlen should be lbm_uint16_t
CoreApi-6856-3: optval not nu-
meric
optval not numeric optval is not a number
CoreApi-6856-4: optlen incorrect
size
optlen incorrect size optlen should be lbm_uint16_t
CoreApi-6856-5: optlen too small optlen too small optlen should be at least LBM_M←-
IN_SGET_OPTLEN
CoreApi-6856-6: optlen incorrect
size
optlen incorrect size optlen should be lbm_uint32_t
CoreApi-6856-7: optval not nu-
meric
optval not numeric optval is not a number
CoreApi-6856-8: optlen incorrect
size
optlen incorrect size optlen should be lbm_uint32_t
CoreApi-6856-9: optlen too small optlen too small optlen should be at least LBM_M←-
IN_SGET_OPTLEN
CoreApi-6898-0: optlen incorrect
size
umq_explicit_ack_only needs to be
0 or 1.:
Set umq_explicit_ack_only to 0 or
1.
CoreApi-6898-1: optval must be 0
or 1
umq_explicit_ack_only needs to be
0 or 1.
Set umq_explicit_ack_only to 0 or
1.
CoreApi-6898-2: optval not nu-
meric
umq_explicit_ack_only needs to be
0 or 1.
Set umq_explicit_ack_only to 0 or
1.
CoreApi-6898-3: optval must be 0
or 1
umq_explicit_ack_only needs to be
0 or 1.
Set umq_explicit_ack_only to 0 or
1.
CoreApi-6898-4: optlen incorrect
size
lbm_rcv_topic_attr_umq_exack_←-
only_get requires an Interger.
Pass a pointer to a Integer to
lbm_rcv_topic_attr_umq_exack_←-
only_get
CoreApi-6898-5: optlen too small lbm_rcv_topic_attr_umq_exack_←-
only_sget requires an Interger.
Pass a pointer to a Integer to
lbm_rcv_topic_attr_umq_exack_←-
only_sget
CoreApi-6898-6: must have explicit
acks enabled
Explicit Acks must be set to 1 be-
fore calling sendExplicitAck.
Set umq_explicit_ack_only to 1.
CoreApi-6898-7: msg must be
valid
Invalid Message. lbm_msg_umq_send_explicit_←-
ack must be called with a valid
message.
CoreApi-6898-8: msg must be
valid
Invalid Message. lbm_msg_umq_can_send_←-
explicit_ack must be called with a
valid message.
CoreApi-6932-11: optlen incorrect
size
The size of the option was too large
and/or too small
sri_request_interval is an lbm_←-
ulong_t
CoreApi-6932-12: optval must be
greater than 0
The option value submitted was
zero (0); this value must be greater
than 0.
While 1 is an acceptable mini-
mum; a larger value provides re-
dundancy.
CoreApi-6932-13: optval not nu-
meric
The option value string submitted
contains non numeric characters.
Be sure there are no trailing non
numeric characters such as spaces
and that the number is not in hex-
adecimal.
CoreApi-6932-14: optval not a
number
The option value string submitted
could not be converted into a num-
ber
Be sure that the size (magnitude)
of the value is correct for an lbm_←-
ulong_t
9.2 UM Core API Messages 173
CoreApi-6932-15: optval must be
greater than 0
The option value submitted was
zero (0); this value must be greater
than 0.
While 1 is an acceptable mini-
mum; a larger value provides re-
dundancy.
CoreApi-6932-16: optlen incorrect
size
The size of the option was too large
and/or too small
sri_request_interval is an lbm_←-
ulong_t
CoreApi-6932-17: optlen too small The size of the option buffer was
too small to contain the option.
sri_request_interval is an lbm_←-
ulong_t
CoreApi-6932-1: optlen incorrect
size
The size of the option was too large
and/or too small
sri_request_interval is an lbm_←-
ulong_t
CoreApi-6932-21: optlen incorrect
size
The size of the option was too large
and/or too small
sri_request_interval is an lbm_←-
ulong_t
CoreApi-6932-22: optval must be
greater than 0
The option value submitted was
zero (0); this value must be greater
than 0.
While 1 is an acceptable mini-
mum; a larger value provides re-
dundancy.
CoreApi-6932-23: optval not nu-
meric
The option value string submitted
contains non numeric characters.
Be sure there are no trailing non
numeric characters such as spaces
and that the number is not in hex-
adecimal.
CoreApi-6932-24: optval not a
number
The option value string submitted
could not be converted into a num-
ber
Be sure that the size (magnitude)
of the value is correct for an lbm_←-
ulong_t
CoreApi-6932-25: optval must be
greater than 0
The option value submitted was
zero (0); this value must be greater
than 0.
While 1 is an acceptable mini-
mum; a larger value provides re-
dundancy.
CoreApi-6932-26: optlen incorrect
size
The size of the option was too large
and/or too small
sri_request_interval is an lbm_←-
ulong_t
CoreApi-6932-27: optlen too small The size of the option buffer was
too small to contain the option.
sri_request_interval is an lbm_←-
ulong_t
CoreApi-6932-2: optval must be
greater than 0
The option value submitted was
zero (0); this value must be greater
than 0.
While 1 is an acceptable mini-
mum; a larger value provides re-
dundancy.
CoreApi-6932-31: optlen incorrect
size
The size of the option was too large
and/or too small
sri_request_interval is an lbm_←-
ulong_t
CoreApi-6932-32: optval must be
greater than 0
The option value submitted was
zero (0); this value must be greater
than 0.
While 1 is an acceptable mini-
mum; a larger value provides re-
dundancy.
CoreApi-6932-33: optval not nu-
meric
The option value string submitted
contains non numeric characters.
Be sure there are no trailing non
numeric characters such as spaces
and that the number is not in hex-
adecimal.
CoreApi-6932-34: optval not a
number
The option value string submitted
could not be converted into a num-
ber
Be sure that the size (magnitude)
of the value is correct for an lbm_←-
ulong_t
CoreApi-6932-35: optval must be
greater than 0
The option value submitted was
zero (0); this value must be greater
than 0.
While 1 is an acceptable mini-
mum; a larger value provides re-
dundancy.
CoreApi-6932-36: optlen incorrect
size
The size of the option was too large
and/or too small
sri_request_interval is an lbm_←-
ulong_t
CoreApi-6932-37: optlen too small The size of the option buffer was
too small to contain the option.
sri_request_interval is an lbm_←-
ulong_t
CoreApi-6932-3: optval not nu-
meric
The option value string submitted
contains non numeric characters.
Be sure there are no trailing non
numeric characters such as spaces
and that the number is not in hex-
adecimal.
174 UM Log Messages
CoreApi-6932-41: optlen incorrect
size
The size of the option was too large
and/or too small
sri_request_interval is an lbm_←-
ulong_t
CoreApi-6932-42: optval must be
greater than 0
The option value submitted was
zero (0); this value must be greater
than 0.
While 1 is an acceptable mini-
mum; a larger value provides re-
dundancy.
CoreApi-6932-43: optval not nu-
meric
The option value string submitted
contains non numeric characters.
Be sure there are no trailing non
numeric characters such as spaces
and that the number is not in hex-
adecimal.
CoreApi-6932-44: optval not a
number
The option value string submitted
could not be converted into a num-
ber
Be sure that the size (magnitude)
of the value is correct for an lbm_←-
ulong_t
CoreApi-6932-45: optval must be
greater than 0
The option value submitted was
zero (0); this value must be greater
than 0.
While 1 is an acceptable mini-
mum; a larger value provides re-
dundancy.
CoreApi-6932-46: optlen incorrect
size
The size of the option was too large
and/or too small
sri_request_interval is an lbm_←-
ulong_t
CoreApi-6932-47: optlen too small The size of the option buffer was
too small to contain the option.
sri_request_interval is an lbm_←-
ulong_t
CoreApi-6932-4: optval not a num-
ber
The option value string submitted
could not be converted into a num-
ber
Be sure that the size (magnitude)
of the value is correct for an lbm_←-
ulong_t
CoreApi-6932-51: optlen incorrect
size
The size of the option was too large
and/or too small
sri_request_interval is an lbm_←-
ulong_t
CoreApi-6932-52: optval must be
greater than 0
The option value submitted was
zero (0); this value must be greater
than 0.
While 1 is an acceptable mini-
mum; a larger value provides re-
dundancy.
CoreApi-6932-53: optval not nu-
meric
The option value string submitted
contains non numeric characters.
Be sure there are no trailing non
numeric characters such as spaces
and that the number is not in hex-
adecimal.
CoreApi-6932-54: optval not a
number
The option value string submitted
could not be converted into a num-
ber
Be sure that the size (magnitude)
of the value is correct for an lbm_←-
ulong_t
CoreApi-6932-55: optval must be
greater than 0
The option value submitted was
zero (0); this value must be greater
than 0.
While 1 is an acceptable mini-
mum; a larger value provides re-
dundancy.
CoreApi-6932-56: optlen incorrect
size
The size of the option was too large
and/or too small
sri_request_interval is an lbm_←-
ulong_t
CoreApi-6932-57: optlen too small The size of the option buffer was
too small to contain the option.
sri_request_interval is an lbm_←-
ulong_t
CoreApi-6932-5: optval must be
greater than 0
The option value submitted was
zero (0); this value must be greater
than 0.
While 1 is an acceptable mini-
mum; a larger value provides re-
dundancy.
CoreApi-6932-6: optlen incorrect
size
The size of the option was too large
and/or too small
sri_request_interval is an lbm_←-
ulong_t
CoreApi-6932-7: optlen too small The size of the option buffer was
too small to contain the option.
sri_request_interval is an lbm_←-
ulong_t
CoreApi-6937-1: optlen incorrect
size
The size of the option was too large
or too small
transport_tcp_use_session_id is
an int
CoreApi-6937-2: optval must be 0
or 1
transport_tcp_use_session_id can
either be set "ON" or "OFF"
Please use "0" to indicate "OFF"
and "1" to indicate "ON"
9.2 UM Core API Messages 175
CoreApi-6937-3: optval not nu-
meric
The option value string submitted
contains non numeric characters.
Be sure there are no trailing non
numeric characters such as spaces
and that the number is not in hex-
adecimal.
CoreApi-6937-4: optval must be 0
or 1
transport_tcp_use_session_id can
either be set "ON" or "OFF"
Please use "0" to indicate "OFF"
and "1" to indicate "ON"
CoreApi-6937-5: optlen incorrect
size
The size of the option was too large
or too small
transport_tcp_use_session_id is
an int
CoreApi-6937-6: optlen too small The size of the option buffer was
too small to contain the option.
transport_tcp_use_session_id is
an int
CoreApi-6976-100: optval not un-
derstood
The value is not a supported oper-
ational mode - either embedded or
sequential.
CoreApi-6976-101: optlen incor-
rect size
The value of optlen passed in does
not match the size of the option
type.
CoreApi-6976-102: optlen too
small
The value of optlen passed in is too
small to hold the option type.
CoreApi-6976-107: optlen incor-
rect size
Value of optlen passed in is not
equal to the size of the option.
CoreApi-6976-108: optval not nu-
meric
Value of the option passed in does
not appear to be a number - and it
needs to be.
CoreApi-6976-109: optval not a
number
Value of the option passed in does
not appear to be a number - and it
needs to be.
CoreApi-6976-110: optlen incor-
rect size
Value of optlen passed in is not
equal to the size of the option.
CoreApi-6976-111: optlen too
small
Value of optlen passed in is not big
enough to store the option type.
CoreApi-6976-112: lbm_imbq_←-
create CreateMutex
We failed to create a mutex on Win-
dows; this probably indicates re-
source exhaustion.
Check machine for excessive mem-
ory use or excessive open handles
(both can be viewed in Task Man-
ager)
CoreApi-6976-113: lbm_imbq_←-
create CreateSemaphore
We failed to create a semaphore on
Windows; this probably indicates
resource exhaustion.
Check machine for excessive mem-
ory use or excessive open handles
(both can be viewed in Task Man-
ager)
CoreApi-6976-115: The LBT-SMX
transport type does not support Hot
Failover sources
User attempted to create a hot
failover source with an LBT-SMX
transport, which is not supported.
CoreApi-6976-116: optval either
not a number or a negative number
The value passed in does not ap-
pear to be a number, or it is a neg-
ative number.
CoreApi-6976-119: Configured
LBT-SMX transport_lbtsmx_id_low
(u) is greater than configured
transport_lbtsmx_id_high (u)
The configured "context transport←-
_lbtsmx_id_low" option is higher
than the configured "context
transport_lbtsmx_id_high" option,
which is not allowed.
CoreApi-6976-152: LBT-SMX:
failed to allocate shared memory
(d)
A shared memory object for the S←-
MX transport could not be created.
This could be caused by a permis-
sion error or no more resources.
Please refer to the OS error num-
ber given.
176 UM Log Messages
CoreApi-6976-153: LBT-SMX:
failed to allocate shared memory of
size configured d, rcvrs: d (d)
A shared memory object for the S←-
MX transport could not be created.
This could be caused by a permis-
sion error or no more resources.
Please refer to the OS error num-
ber given.
CoreApi-6976-154: LBT-SMX:
failed to map shared memory (d)
An error occurred trying to map a
pointer to the SMX shared memory
region. Please refer to the OS error
number given.
CoreApi-6976-155: LBT-SMX: can
not get shared semaphore
A shared memory object for the S←-
MX transport could not be created.
This could be caused by a permis-
sion error or no more resources.
Please refer to the OS error num-
ber given.
CoreApi-6976-156: LBT-SMX: can
not initialize shared semaphore (d)
An error occurred when initializ-
ing the shared semaphore used to
ensure mutual exclusion while ac-
cessing the SMX shared memory
region. Please refer to the OS er-
ror number given.
CoreApi-6976-157: LBT-SMX:
failed to allocate shared memory
(d)
A shared memory object for the S←-
MX transport could not be created.
This could be caused by a permis-
sion error or no more resources.
Please refer to the OS error num-
ber given.
CoreApi-6976-158: LBT-SMX:
failed to map shared memory (d)
An error occurred trying to map a
pointer to the SMX shared memory
region. Please refer to the OS error
number given.
CoreApi-6976-159: LBT-SMX: can
not create shared Mutex (d)
The shared Mutex used to ensure
mutual exclusion while accessing
the SMX shared memory region
could not be created. Please refer
to the OS error number given.
CoreApi-6976-1: buff_acquire
would block
A non-blocking lbm_src_buff_←-
acquire would block.
This is perfectly normal from time to
time. If it happens every send call
or very frequently, a receiver may
be still alive, but hung.
CoreApi-6976-2: requested buffer
length plus headers is higher
than configured transport_lbtsmx←-
_datagram_max_size (u bytes) for
source
A length parameter was passed
to lbm_src_buff_acquire that was
greater than the configured maxi-
mum datagram size; this is a user
error.
Application code should be fixed to
not call buff_acquire with a length
parameter that is too big.
CoreApi-6976-30: LBT-SMX not
supported
The user is trying to set a config op-
tion or perform a function with a li-
brary that does not support the L←-
BT-SMX transport.
CoreApi-6976-31: lbm_send_←-
request and lbm_send_request_ex
are not supported with transport
type LBT-SMX
User tried to send a request via a
source set to use the SMX trans-
port; this is not currently supported.
Don't send requests on LBT-SMX
sources.
9.2 UM Core API Messages 177
CoreApi-6976-33: optlen incorrect
size
The optlen parameter passed in
does not match the size of the op-
tion type.
CoreApi-6976-34: LBT-SMX trans-
mission window size must be at
least d bytes
The user tried to configure the L←-
BT-SMX transmission window size
smaller than the minimum required
size.
Change configuration to specify a
larger LBT-SMX transmission win-
dow size.
CoreApi-6976-35: optval not nu-
meric
The value passed in does not ap-
pear to be a number - and it should
be.
CoreApi-6976-36: optval not a
number
The value passed in does not ap-
pear to be a number - and it should
be.
CoreApi-6976-37: LBT-SMX trans-
mission window size must be at
least d bytes
The user tried to configure the L←-
BT-SMX transmission window size
smaller than the minimum required
size.
Change configuration to specify a
larger LBT-SMX transmission win-
dow size.
CoreApi-6976-38: optlen incorrect
size
The optlen parameter passed in
does not match the size of the op-
tion type.
CoreApi-6976-39: optlen too small The optlen parameter passed in
specifies a size that is too small to
hold the option value.
CoreApi-6976-3: LBT-SMX: too
many outstanding buffs; call lbm_←-
src_buffs_complete before acquir-
ing more
The LBT-SMX transport session
currently has too many outstand-
ing buffers; if another was acquired
now, the receivers could never
catch up and the buff_acquire call
would block forever.
Application code should be fixed
to not call buff_acquire too many
times without calling buffs_←-
complete.
CoreApi-6976-40: optlen incorrect
size
The optlen parameter passed in
does not match the size of the op-
tion type.
CoreApi-6976-41: LBT-SMX max-
imum receivers optval not a valid
size
LBT-SMX max receivers must be
set to at least 1; 0 is not supported
(or sensible).
CoreApi-6976-42: optval not nu-
meric
The value passed in does not ap-
pear to be a number - and it should
be.
CoreApi-6976-43: LBT-SMX max-
imum receivers optval not a valid
size
LBT-SMX max receivers must be
set to at least 1; 0 is not supported
(or sensible).
CoreApi-6976-44: optlen incorrect
size
The optlen parameter passed in
does not match the size of the op-
tion type.
CoreApi-6976-45: optlen too small The optlen parameter passed in
does not match the size of the op-
tion type.
CoreApi-6976-46: optlen incorrect
size
The optlen parameter passed in
does not match the size of the op-
tion type.
CoreApi-6976-47: optval not a valid
interval
The LBT-SMX session message in-
terval must be >0; zero is not a
valid value.
CoreApi-6976-48: optval not nu-
meric
The value passed in does not ap-
pear to be a number - and it should
be.
178 UM Log Messages
CoreApi-6976-49: optval not a
number
The value passed in does not ap-
pear to be a number - and it should
be.
CoreApi-6976-4: LBT-SMX: too
many outstanding buffs; call lbm_←-
src_buffs_complete before acquir-
ing more
The LBT-SMX transport session
currently has too many outstand-
ing buffers; if another was acquired
now, the receivers could never
catch up and the buff_acquire call
would block forever.
Application code should be fixed
to not call buff_acquire too many
times without calling buffs_←-
complete.
CoreApi-6976-50: optval not a valid
interval
The LBT-SMX session message in-
terval must be >0; zero is not a
valid value.
CoreApi-6976-51: optlen incorrect
size
The optlen parameter passed in
does not match the size of the op-
tion type.
CoreApi-6976-52: optlen too small The optlen parameter passed in
specifies a size that is too small to
hold the option value.
CoreApi-6976-53: optlen incorrect
size
The optlen parameter passed in
does not match the size of the op-
tion type.
CoreApi-6976-54: optval not nu-
meric
The value passed in does not ap-
pear to be a number - and it should
be.
CoreApi-6976-55: optlen incorrect
size
The optlen parameter passed in
does not match the size of the op-
tion type.
CoreApi-6976-56: optlen too small The optlen parameter passed in
specifies a size that is too small to
hold the option value.
CoreApi-6976-57: LBT-SMX is not
supported
User is trying to configure the
lbtsmx_datagram_max_size on a
build that doesn't support LBT-S←-
MX.
CoreApi-6976-58: optlen incorrect
size
The optlen parameter passed in
does not match the size of the op-
tion type.
CoreApi-6976-59: value must be
greater than or equal to d
The datagram max size for LB←-
T-SMX must be >= the maximum
header size.
CoreApi-6976-5: LBT-SMX: too
many outstanding buffs; call lbm_←-
src_buffs_complete before acquir-
ing more
The LBT-SMX transport session
currently has too many outstand-
ing buffers; if another was acquired
now, the receivers could never
catch up and the buff_acquire call
would block forever.
Application code should be fixed
to not call buff_acquire too many
times without calling buffs_←-
complete.
CoreApi-6976-60: LBT-SMX is not
supported
The user tried to set or get lbtsmx←-
_datagram_max_size using a build
that does not support LBT-SMX.
CoreApi-6976-61: datagram size
not a number
The value passed in does not ap-
pear to be a number - and it should
be.
CoreApi-6976-62: value must be
greater than or equal to d
The datagram max size for LB←-
T-SMX must be >= the maximum
header size.
9.2 UM Core API Messages 179
CoreApi-6976-63: LBT-SMX is not
supported
The user tried to set or get lbtsmx←-
_datagram_max_size using a build
that does not support LBT-SMX.
CoreApi-6976-64: optlen incorrect
size
The optlen parameter passed in
does not match the size of the op-
tion type.
CoreApi-6976-65: LBT-SMX is not
supported
The user tried to set or get lbtsmx←-
_datagram_max_size using a build
that does not support LBT-SMX.
CoreApi-6976-66: optlen too small The optlen parameter passed in
specifies a size that is too small to
hold the option value.
CoreApi-6976-67: could not allo-
cate new buffer to retain lbm_←-
msg_t
A buffer to hold message data
could not be allocated; usually this
means malloc failed due to being
out of memory.
Check machine for excessive mem-
ory use.
CoreApi-6976-68: src cannot be
NULL
User passed NULL for the source
parameter. NULL is not a valid
source.
CoreApi-6976-69: LBT-SMX
sources do not lbm_src_send_←-
ex_info_t options; exinfo must be
NULL
LBT-SMX does not support any of
the options that can be specified
with an lbm_src_send_ex_info_←-
t object. Therefore, the exinfo pa-
rameter when sending with an L←-
BT-SMX source should always be
NULL.
CoreApi-6976-70: source transport
type does not support sending with
lbm_src_buff_acquire
The current build does not support
LBT-SMX, but the user is trying to
call the new LBT-SMX-related send
API calls.
CoreApi-6976-71: src must not be
NULL
The user specified a NULL pointer
for the source argument to lbm_←-
src_buff_acquire, which is invalid.
CoreApi-6976-72: bufp must not be
NULL
The user specified a NULL pointer
for the bufp argument to lbm_src←-
_buff_acquire, which is invalid.
CoreApi-6976-73: only LBT-S←-
MX sources support sending with
lbm_src_buff_acquire
The user called a new LBT-SM←-
X-related send API call using a
source that is not LBT-SMX source;
this is unsupported.
CoreApi-6976-74: source transport
type does not support sending with
lbm_src_buffs_complete
The current build does not support
LBT-SMX, but the user is trying to
call the new LBT-SMX-related send
API calls.
CoreApi-6976-75: src must not be
NULL
The user specified a NULL pointer
for the source argument to lbm←-
_src_buffs_complete, which is in-
valid.
CoreApi-6976-76: only LBT-S←-
MX sources support sending with
lbm_src_buffs_complete
The user called a new LBT-SM←-
X-related send API call using a
source that is not LBT-SMX source;
this is unsupported.
CoreApi-6976-77: source trans-
port type does not support send-
ing with lbm_src_buffs_complete←-
_and_acquire
The current build does not support
LBT-SMX, but the user is trying to
call the new LBT-SMX-related send
API calls.
180 UM Log Messages
CoreApi-6976-78: src must not be
NULL
The user specified a NULL pointer
for the source argument to lbm_←-
src_buffs_complete_and_acquire,
which is invalid.
CoreApi-6976-79: bufp must not be
NULL
The user specified a NULL pointer
for the bufp argument to lbm_←-
src_buffs_complete_and_acquire,
which is invalid.
CoreApi-6976-80: only LBT-SMX
sources support sending with
lbm_src_buffs_complete_and_←-
acquire
The user called a new LBT-SM←-
X-related send API call using a
source that is not LBT-SMX source;
this is unsupported.
CoreApi-6976-81: source transport
type does not support lbm_src_←-
buffs_cancel
The current build does not support
LBT-SMX, but the user is trying to
call the new LBT-SMX-related send
API calls.
CoreApi-6976-82: src must not be
NULL
The user specified a NULL pointer
for the source argument to lbm_←-
src_buffs_cancel, which is invalid.
CoreApi-6976-83: only LBT-S←-
MX sources support canceling out-
standing buffers with lbm_src_←-
buffs_cancel
The user called a new LBT-SM←-
X-related send API call using a
source that is not LBT-SMX source;
this is unsupported.
CoreApi-6976-85: an error oc-
curred while canceling source
buffers - possibly due to non
thread-safe use of lbm_src_buffs←-
_cancel; LBT-SMX shared memory
may be in an inconsistent state
The user probably called a series of
non-thread-safe buffer-based send
API functions concurrently.
Code testing for race conditions &
code inspection is advised.
CoreApi-6976-86: optlen incorrect
size
The value of optlen passed in does
not match the size of the option
type.
CoreApi-6976-87: optval not a valid
ID
Transport ID 0 is reserved for inter-
nal use for LBT-SMX, so configur-
ing a 0 is not allowed.
CoreApi-6976-88: optval not nu-
meric
The value given does not appear to
be a number - and it needs to be.
CoreApi-6976-89: optval not a valid
ID
Transport ID 0 is reserved for inter-
nal use for LBT-SMX, so configur-
ing a 0 is not allowed.
CoreApi-6976-90: optlen incorrect
size
The value of optlen passed in does
not match the size of the option
type.
CoreApi-6976-91: optlen too small The value of optlen passed in is too
small to hold the option type.
CoreApi-6976-92: optlen incorrect
size
The value of optlen passed in does
not match the size of the option
type.
CoreApi-6976-93: optval not a valid
ID
Transport ID 0 is reserved for inter-
nal use for LBT-SMX, so configur-
ing a 0 is not allowed.
CoreApi-6976-94: optval not nu-
meric
The value given does not appear to
be a number - and it needs to be.
CoreApi-6976-95: optval not a valid
ID
Transport ID 0 is reserved for inter-
nal use for LBT-SMX, so configur-
ing a 0 is not allowed.
9.2 UM Core API Messages 181
CoreApi-6976-96: optlen incorrect
size
The value of optlen passed in does
not match the size of the option
type.
CoreApi-6976-97: optlen too small The value of optlen passed in is too
small to hold the option type.
CoreApi-6976-98: optlen incorrect
size
The value of optlen passed in does
not match the size of the option
type.
CoreApi-6976-99: optval not sup-
ported
The value is not a supported oper-
ational mode - either embedded or
sequential.
CoreApi-6986-1: ume_sri_inter_←-
sri_interval can not be zero
ume_sri_inter_sri_interval is set to
zero
ume_sri_inter_sri_interval can not
be zero
CoreApi-6986-2: ume_sri_inter_←-
sri_interval can not be zero
ume_sri_inter_sri_interval is set to
zero
ume_sri_inter_sri_interval can not
be zero
CoreApi-6986-3: optlen incorrect
size
optlen incorrect size optlen should be lbm_uint32_t
CoreApi-6986-4: ume_source_←-
timer_minimum_interval can not be
zero
ume_src_timer_min_ivl is set to
zero
ume_src_timer_min_ivl can not be
zero
CoreApi-6986-5: optval not nu-
meric
optval not numeric optval is not a number
CoreApi-6986-6: ume_source_←-
timer_minimum_interval can not be
zero
ume_src_timer_min_ivl is set to
zero
ume_src_timer_min_ivl can not be
zero
CoreApi-6986-7: optlen incorrect
size
optlen incorrect size optlen should be lbm_uint32_t
CoreApi-6986-8: optlen too small optlen too small optlen should be at least LBM_M←-
IN_SGET_OPTLEN
CoreApi-6993-1: optval not nu-
meric
optval not numeric optval is not a number
CoreApi-6993-2: optlen incorrect
size
optlen incorrect size optlen should be lbm_uint32_t
CoreApi-6993-3: optlen too small optlen too small optlen should be at least LBM_M←-
IN_SGET_OPTLEN
CoreApi-6993-4: optval not nu-
meric
optval not numeric optval is not a number
CoreApi-6993-5: optlen incorrect
size
optlen incorrect size optlen should be lbm_uint32_t
CoreApi-6993-6: optlen too small optlen too small optlen should be at least LBM_M←-
IN_SGET_OPTLEN
CoreApi-6993-7: optlen incorrect
size
optlen incorrect size optlen should be lbm_uint32_t
CoreApi-6993-8: optlen incorrect
size
optlen incorrect size optlen should be lbm_uint32_t
CoreApi-7160-10: optval not nu-
meric
Attempted to set receiver otr←-
_request_message_timeout to a
non numeric value
optval must be a string representa-
tion of a number
CoreApi-7160-11: optval not a
number
Could not parse string optval into a
number
optval must be a number
CoreApi-7160-12: optval must be
greater than 0
timeout value cannot be negative Change configuration to provide a
positive value
CoreApi-7160-13: optlen incorrect
size
optlen contained an incorrect size optlen should be sizeof(lbm_←-
ulong_t)
CoreApi-7160-14: optlen too small optlen was too small increase size of optlen
182 UM Log Messages
CoreApi-7160-1: optlen incorrect
size
optlen value contained the incor-
rect length
optlen should be sizeof(lbm_←-
ulong_t)
CoreApi-7160-2: optval must be
greater than 0
optval contained a negative integer optval must be a positive integer
CoreApi-7160-3: optval not nu-
meric
Attempted to set receiver
retransmit_request_message←-
_timeout to a non numeric value
optval must be a string representa-
tion of a number
CoreApi-7160-4: optval not a num-
ber
Could not parse string optval into a
number
optval must be a number
CoreApi-7160-5: optval must be
greater than 0
receiver retransmit_request←-
_message_timeout cannot be
negative
Change configuration to provide a
positive value
CoreApi-7160-6: optlen incorrect
size
optlen contained an incorrect size optlen should be sizeof(lbm_←-
ulong_t)
CoreApi-7160-7: optlen too small optlen was too small increase size of optlen
CoreApi-7160-8: optlen incorrect
size
optlen value contained the incor-
rect length
optlen should be sizeof(lbm_←-
ulong_t)
CoreApi-7160-9: optval must be
greater than 0
optval contained a negative integer optval must be a positive integer
CoreApi-7175-10: optlen too small The size of the option buffer was
too small to contain the option.
ume_application_outstanding_←-
maximum is an lbm_ulong_t
CoreApi-7175-1: optlen incorrect
size
The size of the option was too large
and/or too small
otr_message_caching_threshold is
an lbm_ulong_t
CoreApi-7175-2: optval not nu-
meric
The option value string submitted
contains non numeric characters.
Be sure there are no trailing non
numeric characters such as spaces
and that the number is not in hex-
adecimal.
CoreApi-7175-3: optval not a num-
ber
The option value string submitted
could not be converted into a num-
ber
Be sure that the size (magnitude)
of the value is correct for an lbm_←-
ulong_t
CoreApi-7175-4: optlen incorrect
size
The size of the option was too large
and/or too small
otr_message_caching_threshold is
an lbm_ulong_t
CoreApi-7175-5: optlen too small The size of the option buffer was
too small to contain the option.
otr_message_caching_threshold is
an lbm_ulong_t
CoreApi-7175-6: optlen incorrect
size
The size of the option was too large
and/or too small
ume_application_outstanding_←-
maximum is an lbm_ulong_t
CoreApi-7175-7: optval not nu-
meric
The option value string submitted
contains non numeric characters.
Be sure there are no trailing non
numeric characters such as spaces
and that the number is not in hex-
adecimal.
CoreApi-7175-8: optval not a num-
ber
The option value string submitted
could not be converted into a num-
ber
Be sure that the size (magnitude)
of the value is correct for an lbm_←-
ulong_t
CoreApi-7175-9: optlen incorrect
size
The size of the option was too large
and/or too small
ume_application_outstanding_←-
maximum is an lbm_ulong_t
CoreApi-7521-1: optlen incorrect
size
Incorrect length used for setting in-
teger options
length must be sizeof int
CoreApi-7521-2: optval must be 0
or 1
Invalid value for optval optval must be 0 or 1
CoreApi-7521-3: optval not nu-
meric
Option string was not a number Provide number as a string
CoreApi-7521-4: optval must be 0
or 1
Invalid value for optval optval must be 0 or 1
CoreApi-7521-5: optlen incorrect
size
Size of optlen was incorrect optlen size must be size of int
9.2 UM Core API Messages 183
CoreApi-7521-6: optlen too small Size of optlen was too small Size of optlen must be at least 80
CoreApi-7563-1: optlen incorrect
size
The size of the option passed in is
not the correct size for this option
CoreApi-7563-2: Resolver Event
function must be valid
The function pointer the the func-
tion is invalid.
Check parameters.
CoreApi-7563-3: str_setopt not
supported for option
str_setopt is not supported
CoreApi-7563-4: optlen incorrect
size
The size of the option passed in is
not the correct size for this option
CoreApi-7563-5: str_getopt not
supported for option
String Get option is not supported
CoreApi-7699-1: Socket error set-
ting SO_EXCLUSIVEADDRUSE: s
An error was returned from the OS
while trying to set the SO_EXCL←-
USIVEADDRUSE (Windows Only)
option on a socket.
Refer to the OS error number and
message given to determine cause
of the failure.
CoreApi-7839-13: optlen incorrect
size
The size of the option buffer was
too small to contain the option.
monitor_interval is an lbm_ulong←-
_t
CoreApi-7839-14: optval not nu-
meric
The option value string submitted
could not be converted into a num-
ber
Be sure that the size (magnitude)
of the value is correct for an lbm_←-
ulong_t
CoreApi-7839-15: optlen incorrect
size
The size of the option was too large
and/or too small
monitor_interval is an lbm_ulong←-
_t
CoreApi-7839-16: optlen too small The size of the option buffer was
too small to contain the option.
monitor_interval is an lbm_ulong←-
_t
CoreApi-7839-19: receiver must be
valid
An internal error was encountered
while auto-monitoring a receiver
topic.
Contact Informatica support.
CoreApi-7839-1: optlen incorrect
size
Attempted to set option receiver←-
_callback_service_time_enabled
with an incorrect optlen size.
Optlen must be size of int.
CoreApi-7839-20: receiver must be
valid
An internal error was encountered
while auto-monitoring a receiver
topic.
Contact Informatica support.
CoreApi-7839-21: receiver must be
valid
An internal error was encountered
while auto-monitoring a receiver
topic.
Contact Informatica support.
CoreApi-7839-22: receiver must be
valid
An internal error was encountered
while auto-monitoring a receiver
topic.
Contact Informatica support.
CoreApi-7839-23: Error initializing
auto-monitoring
An internal error was encountered
while auto-monitoring a receiver
topic.
Contact Informatica support.
CoreApi-7839-24: automatic moni-
toring of receiver failed [d] [s]
Unable to monitor receiver. This is an internal error usually
caused by running out of memory.
CoreApi-7839-25: automatic un-
monitoring of receiver failed [d] [s]
Unable to unmonitor receiver. This is an internal error usually
caused by running out of memory.
CoreApi-7839-26: wildcard re-
ceiver must be valid
An internal error was encountered
while auto-monitoring a wildcard
receiver.
Contact Informatica support.
CoreApi-7839-27: wildcard re-
ceiver must be valid
An internal error was encountered
while auto-monitoring a wildcard
receiver.
Contact Informatica support.
CoreApi-7839-28: Error initializing
auto-monitoring
An internal error was encountered
while auto-monitoring a wildcard
receiver.
Contact Informatica support.
184 UM Log Messages
CoreApi-7839-29: automatic moni-
toring of wildcard receiver failed [d]
[s]
Unable to monitor receiver. This is an internal error usually
caused by running out of memory.
CoreApi-7839-2: optval must be 0
or 1
Attempted to set option receiver←-
_callback_service_time_enabled
with an invalid optval.
Optval must be 0 or 1.
CoreApi-7839-30: automatic un-
monitoring of wildcard receiver
failed [d] [s]
Unable to unmonitor wildcard re-
ceiver.
This is an internal error usually
caused by running out of memory.
CoreApi-7839-32: automatic moni-
toring of source failed [d] [s]
Unable to monitor source. This is an internal error usually
caused by running out of memory.
CoreApi-7839-38: Context must be
valid
An internal error was encountered
while updating the domain ID for an
auto-monitored context.
Contact Informatica support.
CoreApi-7839-39: context must be
valid
An internal error was encountered
while auto-monitoring a context.
Contact Informatica support.
CoreApi-7839-3: optval not nu-
meric
Attempted to set option receiver←-
_callback_service_time_enabled
with an invalid optval.
Optval must be numeric.
CoreApi-7839-40: monitor_←-
transport option is not supported
Invalid monitor_transport is config-
ured.
User needs to select a valid option
for monitor_transport
CoreApi-7839-41: optlen incorrect
size
Attempted to set wildcard receiver
attribute "monitor_interval" using
the wrong size optlen.
The parameter "optlen" must be the
size of an lbm_ulong_tr.
CoreApi-7839-42: optval not nu-
meric
Attempted to set wildcard receiver
attribute "monitor_interval" using a
string that is not a number.
The parameter "optval" must be a
string representation of a number.
CoreApi-7839-43: optlen incorrect
size
Attempted to get wildcard receiver
attribute "monitor_interval" using
the wrong size optlen.
The parameter "optlen" must be the
size of an lbm_ulong_t.
CoreApi-7839-44: optlen too small Attempted to get wildcard receiver
attribute "monitor_interval" using a
string length that is too short.
The parameter "optlen" must be at
least 80.
CoreApi-7839-45: Error initializing
auto-monitoring
An internal error was encountered
while auto-monitoring a context.
Contact Informatica support.
CoreApi-7839-4: optval not a num-
ber
Attempted to set option receiver←-
_callback_service_time_enabled
with an invalid optval.
Optval must be numeric.
CoreApi-7839-5: optval must be 0
or 1
Attempted to set option receiver←-
_callback_service_time_enabled
with an invalid optval.
Optval must be 0 or 1.
CoreApi-7839-6: optlen incorrect
size
Attempted to retrieve option
receiver_callback_service_time←-
_enabled with an incorrect optlen
size.
Optlen must be size of int.
CoreApi-7839-7: optlen too small Attempted to retrieve option
receiver_callback_service_time←-
_enabled with an incorrect optlen
size.
Optlen must be greater than LBM←-
_MIN_SGET_OPTLEN.
CoreApi-7863-1: could not allocate
new buffer to retain lbm_msg_t
A buffer to hold message data
could not be allocated; usually this
means malloc failed due to being
out of memory.
Check machine for excessive mem-
ory use.
9.2 UM Core API Messages 185
CoreApi-7875-1: optval cannot
contain multiple values
The value for resolver_unicast←-
_daemon contained a separator.
Each call to set resolver_unicast←-
_daemon can contain only a single
value.
Remove the separator and ex-
tra values. Additional values for
resolver_unicast_daemon can be
added with repeated sets of the op-
tion.
CoreApi-7911-10: optval must not
be NULL
optval parameter cannot be NULL
CoreApi-7911-11: optlen must not
be NULL
optlen parameter cannot be NULL
CoreApi-7911-12: optval is not
large enough
Provided optlen was not large
enough to contain stackname
string
optlen now contains the minimum
necessary size.
CoreApi-7911-13: Onload stack-
name is not supported
This platform does not support set-
ting the onload stackname.
Check documentation for list of
platforms that support onload.
CoreApi-7911-14: Onload stack
name must be 8 characters or less
Onload stackname is limited to 8
characters or less.
Optlen value must be 8 or less.
CoreApi-7911-15: optval must not
be NULL
optval parameter cannot be NULL
CoreApi-7911-16: optlen must not
be NULL
optlen parameter cannot be NULL
CoreApi-7911-17: optval is not
large enough
Provided optlen was not large
enough to contain stackname
string
optlen now contains the minimum
necessary size.
CoreApi-7911-4: Onload stack-
name is not supported
This platform does not support set-
ting the onload stackname.
Check documentation for list of
platforms that support onload.
CoreApi-7911-5: Onload stack
name must be 8 characters or less
Onload stackname is limited to 8
characters or less.
Optlen value must be 8 or less.
CoreApi-8209-1: optlen incorrect
size
Setting of the compatibility_←-
include_pre_um_6_0_behavior
configuration option is using the
wrong size. Size is "int".
User needs to use the correct size
when setting the configuration op-
tion.
CoreApi-8209-2: optval must be 0
or 1
The compatibility_include_pre←-
_um_6_0_behavior configuration
option must be a 0 or 1.
The user should set the option to 0
or 1.
CoreApi-8209-3: optval not nu-
meric
Setting of the compatibility_←-
include_pre_um_6_0_behavior
configuration option is using a
string value that is not a number.
The user needs to pass a number
in the string.
CoreApi-8209-4: optval must be 0
or 1
The compatibility_include_pre←-
_um_6_0_behavior configuration
option must be a 0 or 1.
The user should set the option to 0
or 1.
CoreApi-8209-5: optlen incorrect
size
Getting the compatibility_include←-
_pre_um_6_0_behavior configura-
tion option is using the wrong size.
Size is "int".
User needs to use the correct size
when getting the configuration op-
tion.
CoreApi-8209-6: optlen too small Getting the compatibility_include←-
_pre_um_6_0_behavior configura-
tion option is using a string that is
too small. Minimum string size is
80 bytes.
User needs to use the correct string
size when getting the configuration
option.
CoreApi-8243-1: optlen incorrect
size
Attempted to set option delivery_←-
control_message_batching with an
incorrect optlen size.
Optlen must be size of int.
CoreApi-8243-29: Can't allocate
memory [s:d]
The LBM JNI library could not cre-
ate a new jni_rcv_t.
This usually indicates a severe out
of memory condition.
186 UM Log Messages
CoreApi-8243-2: optval must be 0
or 1
Attempted to set option delivery_←-
control_message_batching with an
invalid optval.
Optval must be 0 or 1.
CoreApi-8243-30: Can't allocate
memory [s:d]
The LBM JNI library could not cre-
ate a managed ref to a receiver ob-
ject.
This usually indicates a severe out
of memory condition.
CoreApi-8243-31: Can't allocate
memory [s:d]
The LBM JNI library could not cre-
ate a receiver clientd object.
This usually indicates a severe out
of memory condition.
CoreApi-8243-32: Can't allocate
memory [s:d]
The LBM JNI library could not allo-
cate a client callback object.
This usually indicates a severe out
of memory condition.
CoreApi-8243-33: Can't allocate
memory [s:d]
The LBM JNI library could not allo-
cate a client callback object.
This usually indicates a severe out
of memory condition.
CoreApi-8243-34: Can't allocate
memory [s:d]
The LBM JNI library could not allo-
cate global reference.
This usually indicates a severe out
of memory condition.
CoreApi-8243-35: Can't allocate
memory [s:d]
The LBM JNI library could not allo-
cate a client callback object.
This usually indicates a severe out
of memory condition.
CoreApi-8243-36: Can't allocate
memory [s:d]
The LBM JNI library could not allo-
cate a client callback object.
This usually indicates a severe out
of memory condition.
CoreApi-8243-37: Can't allocate
memory [s:d]
The LBM JNI library could not allo-
cate a jni_rcv_t object.
This usually indicates a severe out
of memory condition.
CoreApi-8243-38: Can't allocate
memory [s:d]
The LBM JNI library could not cre-
ate a new global reference.
This usually indicates a severe out
of memory condition.
CoreApi-8243-39: Can't allocate
memory [s:d]
The LBM JNI library could not cre-
ate a new global reference.
This usually indicates a severe out
of memory condition.
CoreApi-8243-3: optval not nu-
meric
Attempted to set option delivery_←-
control_message_batching with an
invalid optval.
Optval must be numeric.
CoreApi-8243-41: Can't allocate
memory [s:d]
The LBM JNI library could not allo-
cate a client callback object.
This usually indicates a severe out
of memory condition.
CoreApi-8243-42: Can't allocate
memory [s:d]
The LBM JNI library could not allo-
cate a client callback object.
This usually indicates a severe out
of memory condition.
CoreApi-8243-43: Can't allocate
memory [s:d]
The LBM JNI library could not allo-
cate global reference.
This usually indicates a severe out
of memory condition.
CoreApi-8243-44: Can't allocate
memory [s:d]
The LBM JNI library could not allo-
cate global reference.
This usually indicates a severe out
of memory condition.
CoreApi-8243-45: Can't allocate
memory [s:d]
The LBM JNI library could not allo-
cate receiver clientd.
This usually indicates a severe out
of memory condition.
CoreApi-8243-46: Can't allocate
receiver topic attributes [s:d]
Receiver topic attributes could not
be created; this probably indicates
an out of memory condition.
This usually indicates a severe out
of memory condition; check appli-
cation memory use.
CoreApi-8243-4: optval not a num-
ber
Attempted to set option delivery_←-
control_message_batching with an
invalid optval.
Optval must be numeric.
CoreApi-8243-5: optval must be 0
or 1
Attempted to set option delivery_←-
control_message_batching with an
invalid optval.
Optval must be 0 or 1.
CoreApi-8243-6: optlen incorrect
size
Attempted to retrieve option
delivery_control_message_←-
batching with an incorrect optlen
size.
Optlen must be size of int.
CoreApi-8243-7: optlen too small Attempted to retrieve option
delivery_control_message_←-
batching with an incorrect optlen
size.
Optlen must be greater than LBM←-
_MIN_SGET_OPTLEN.
9.2 UM Core API Messages 187
CoreApi-8608-1: could not insert
lbm_hf_order_rec_t sqn x into or-
der ASL [s:d]
An attempt to update an internal
data structure resulted in an error,
probably due to lack of available
memory.
Please contact Informatica Support
and ensure your application has
enough memory available to it.
CoreApi-8756-130: send would
block
LBM_EWOULDBLOCK handling
for the broker transport
This is not an error. The user needs
to handle LBM_EWOULDBLOCK.
CoreApi-8787-2: optlen incorrect
size
The user passed in a value of
optlen that did not match up to the
option's expected type's size.
Check the application code to be
sure the correct option type (int,
long, etc.) is being passed in.
CoreApi-8787-3: optval not nu-
meric
A number was expected for this
config option, but something else
was pased in.
Check the code or config file that
sets this option; make sure it is
passing in a string with a number
in it.
CoreApi-8787-4: optval not a num-
ber
A number was expected for this
config option, but something else
was pased in.
Check the code or config file that
sets this option; make sure it is
passing in a string with a number
in it.
CoreApi-8787-5: optlen incorrect
size
The user passed in a value of
optlen that did not match up to the
option's expected type's size.
Check the application code to be
sure the correct option type (int,
long, etc.) is being passed in.
CoreApi-8787-6: optlen too small The buffer given is too small to
write the option value to.
Check that the size of the buffer be-
ing passed in is at least LBM_MI←-
N_SGET_OPTLEN bytes.
CoreApi-8812-1: Configured
request_tcp_port_low (u) is greater
than configured request_tcp_←-
port_high (u)
The configured "context request_←-
tcp_port_low" option is higher than
the configured "context request_←-
tcp_port_high" option, which is not
allowed.
Correct configuration to specify
"context request_tcp_port_low" <=
"context request_tcp_port_high"
CoreApi-8812-2: Configured LBT-
TCP transport_tcp_port_low (u) is
greater than configured transport←-
_tcp_port_high (u)
The configured "context transport←-
_tcp_port_low" option is higher
than the configured "context
transport_tcp_port_high" option,
which is not allowed.
Correct configuration to specify
"context transport_tcp_port_low"
<= "context transport_tcp_port_←-
high"
CoreApi-8812-3: Configured LB←-
MD resolver_unicast_port_low (u)
is greater than the configured
resolver_unicast_port_high (u)
The configured "context resolver←-
_unicast_port_low" option is
higher than the configured "con-
text resolver_unicast_port_high"
option, which is not allowed.
Correct configuration to specify
"context resolver_unicast_port←-
_low" <= "context resolver_←-
unicast_port_high"
CoreApi-8812-4: Configured L←-
BT-RM transport_lbtrm_source_←-
port_low (u) is greater than con-
figured transport_lbtrm_source_←-
port_high (u)
The configured "context transport←-
_lbtrm_source_port_low" option is
higher than the configured "con-
text transport_lbtrm_source_port←-
_high" option, which is not allowed.
Correct configuration to specify
"context transport_lbtrm_source←-
_port_low" <= "context transport←-
_lbtrm_source_port_high"
CoreApi-8812-5: Configured LB←-
T-RM transport_lbtrm_multicast←-
_address_low (s) is greater than
configured transport_lbtrm_←-
multicast_address_high (s)
The configured "context transport←-
_lbtrm_multicast_address_low"
option is higher than the config-
ured "context transport_lbtrm_←-
multicast_address_high" option,
which is not allowed.
Correct configuration to spec-
ify "context transport_lbtrm_←-
multicast_address_low" <= "con-
text transport_lbtrm_multicast_←-
address_high"
CoreApi-8812-6: Configured LB←-
T-RU transport_lbtru_port_low (u)
is greater than the configured
transport_lbtru_port_high (u)
The configured "context transport←-
_lbtru_port_low" option is higher
than the configured "context
transport_lbtru_port_high" option,
which is not allowed.
Correct configuration to specify
"context transport_lbtru_port_low"
<= "context transport_lbtru_port←-
_high"
188 UM Log Messages
CoreApi-8812-7: Configured LB←-
T-IPC transport_lbtipc_id_low (u) is
greater than configured transport←-
_lbtipc_id_high (u)
The configured "context transport←-
_lbtipc_id_low" option is higher
than the configured "context
transport_lbtipc_id_high" option,
which is not allowed.
Correct configuration to specify
"context transport_lbtipc_id_low"
<= "context transport_lbtipc_id_←-
high"
CoreApi-8812-8: Configured LB←-
T-RDMA transport_lbtrdma_port←-
_low (u) is greater than configured
transport_lbtrdma_port_high (u)
The configured "context transport←-
_lbtrdma_port_low" option is
higher than the configured "con-
text transport_lbtrdma_port_high"
option, which is not allowed.
Correct configuration to specify
"context transport_lbtrdma_port←-
_low" <= "context transport_←-
lbtrdma_port_high"
CoreApi-8812-9: Configured LB←-
T-RU transport_lbtru_port_low (u)
is greater than the configured
transport_lbtru_port_high (u)
The configured "receiver
transport_lbtru_port_low" option
is higher than the configured "re-
ceiver transport_lbtru_port_high"
option, which is not allowed.
Correct configuration to specify
"receiver transport_lbtru_port_low"
<= "receiver transport_lbtru_port←-
_high"
CoreApi-8840-1: event queue
monitor transport opts value
cannot start with a '"'
The event queue monitor transport
options string is malformed.
Remove the quote marks from the
event queue monitor transport op-
tions string, if any.
CoreApi-8840-2: event queue
monitor transport opts value
cannot start with a '"'
The event queue monitor transport
options string is malformed.
Remove the quote marks from the
event queue monitor transport op-
tions string, if any.
CoreApi-8840-4: context monitor
transport opts value cannot start
with a '"'
The context monitor transport op-
tions string is malformed.
Remove the quote marks from the
context monitor transport options
string, if any.
CoreApi-8840-5: context monitor
transport opts value cannot start
with a '"'
The context monitor transport op-
tions string is malformed.
Remove the quote marks from the
context monitor transport options
string, if any.
CoreApi-8901-100: invalid Broker
configuration: need to configure
broker (context) location to use bro-
ker transport (source)
The transport (source) is broker but
the broker location has not be set
The user needs to check their con-
figuration
CoreApi-8901-101: invalid Broker
configuration: transport (source)
must be broker with broker (con-
text) location
Setting broker location restricts
transport (source) to broker
The user needs to check their con-
figuration
CoreApi-8901-102: Source trans-
port Broker not supported in non-
Broker build
To use the Broker transport, the
build needs to be Broker enabled.
Call sales.
CoreApi-8901-112: lbm_imbq_←-
create CreateMutex
We failed to create a mutex on Win-
dows; this probably indicates re-
source exhaustion.
Check machine for excessive mem-
ory use or excessive open handles
(both can be viewed in Task Man-
ager)
CoreApi-8901-113: lbm_imbq_←-
create CreateSemaphore
We failed to create a semaphore on
Windows; this probably indicates
resource exhaustion.
Check machine for excessive mem-
ory use or excessive open handles
(both can be viewed in Task Man-
ager)
CoreApi-8901-61: Broker has been
configured with non-Broker capa-
ble build
To use the Broker transport, the
build needs to be Broker enabled.
Call sales to get broker capable
build.
CoreApi-8904-50: optlen incorrect
size
The option size is incorrect for the
broker (context) configuration op-
tion
Make sure the user specifies the
correct option size: sizeof(lbm_←-
transport_broker_entry_t)
CoreApi-8904-51: optval too long The broker (context) string setter
option length is too long
The user should check the param-
eters passed to the setter
CoreApi-8904-52: optval is mal-
formed
The broker (context) interface op-
tion is malformed
The user needs to check the broker
(context) configuration option
9.2 UM Core API Messages 189
CoreApi-8904-53: optval is mal-
formed
The broker (context) IP addess op-
tion is malformed
The user needs to check the broker
(context) configuration option
CoreApi-8904-54: optval is mal-
formed
The broker (context) IP addess op-
tion is malformed
The user needs to check the broker
(context) configuration option
CoreApi-8904-55: optval is mal-
formed
The broker (context) interface op-
tion is malformed
The user needs to check the broker
(context) configuration option
CoreApi-8904-56: optval is mal-
formed
The broker (context) IP addess op-
tion is malformed
The user needs to check the broker
(context) configuration option
CoreApi-8904-57: optval is mal-
formed
The broker (context) option is mal-
formed
The user needs to check the broker
(context) configuration option
CoreApi-8904-58: optval is mal-
formed
The broker (context) option is mal-
formed
The user needs to check the broker
(context) configuration option
CoreApi-8904-59: optval is too
small to hold information, optlen set
to required value
The user needs to allocate enough
room for all broker (context) options
set
The user needs to check their get
option usage
CoreApi-8904-60: optval is too
small to hold information, optlen set
to required value
The user needs to allocate enough
room for all broker (context) options
set
The user needs to check their get
option usage
CoreApi-8913-11: Explicit ACK
feature is not supported for mes-
sages received via broker receiver
Explicit ACK is called for message
received from broker receiver.
lbm_msg_umq_send_explicit_ack
can not be called for messages
from broker receiver.
CoreApi-8913-20: msg must be
valid
Invalid Message. lbm_msg_umq_can_send_←-
explicit_ack must be called with a
valid message.
CoreApi-8913-2: Source is not
connected to broker, and it has not
initiated logical connection.
Application tried to send before log-
ical connection to broker is estab-
lished
Wait for source event that signals
registration complete
CoreApi-8913-3: Source in the pro-
cess of establishing connection to
broker and it has not been estab-
lished the connection yet
Application tried to send before log-
ical connection to broker is estab-
lished
Wait for source event that signals
registration complete
CoreApi-8913-5: Source can not
be configured as broker and ume
source
An lbm source can not be config-
ured as broker and UME source
concurrently
Configure lbm source as UME or
Broker source but not both
CoreApi-8913-6: Source can not
be configured as broker and ulb
source
An lbm source can not be config-
ured as broker and ulb source con-
currently
Configure lbm source as ULB or
Broker source but not both
CoreApi-8913-7: Broker source
can not be in a daemon
Broker source is created in DRO Contact Informatica Support
CoreApi-8913-9: lbm_msg_umq←-
_reassign function is called without
DISCARD flag
lbm_msg_umq_reassign function
is called without DISCARD flag
lbm_msg_umq_reassign can only
be called to discard a message at
broker
CoreApi-8979-1: optlen incorrect
size
The oplen parameter is incorrect. Optlen must be sizeof(int).
CoreApi-8979-2: optval not nu-
meric
Optval is not numeric. The optval string must consist of
numbers and an optional sign only.
CoreApi-8979-3: timeout value d
invalid, must be between -1 and
2,147,483,647 (inclusive).
Optval is out of range. The optval must be within the range
specified.
CoreApi-8979-4: optlen incorrect
size
The oplen parameter is incorrect. Optlen must be sizeof(int).
CoreApi-8979-5: optlen too small Optlen is too small. Optlen should be at least LBM_M←-
IN_SGET_OPTLEN.
190 UM Log Messages
CoreApi-9000-1: brokered context
cannot support wildcards
Wildcard Receivers are not sup-
ported with brokered contexts.
Inform the user of the restriction
when using brokered context.
CoreApi-9001-1: brokered context
cannot send MIM messages
A context configured exclusively for
the broker transport does not sup-
port Immediate Messaging
The user could create multiple
contexts and selectively configure
them as brokered
CoreApi-9001-2: brokered context
cannot send MIM requests
A context configured exclusively for
the broker transport does not sup-
port Immediate Requests
The user could create multiple
contexts and selectively configure
them as brokered
CoreApi-9001-3: lbm_queue_←-
immediate_message is no longer
supported
Queue Immediate Messaging is no
longer supported.
The user needs to use the new Ac-
tive MQ broker features.
CoreApi-9001-4: brokered context
cannot send UIM messages
A context configured exclusively for
the broker transport does not sup-
port Immediate Messaging
The user could create multiple
contexts and selectively configure
them as brokered
CoreApi-9001-5: brokered context
cannot send UIM requests
A context configured exclusively for
the broker transport does not sup-
port Immediate Requests
The user could create multiple
contexts and selectively configure
them as brokered
CoreApi-9011-1: Hot-Failover Re-
ceivers are not allowed with a bro-
kered context
User attempted to create a Hot
Failover receiver with a Broker
Context, which is not supported.
The user will not be able to use Hot
Failover receivers
CoreApi-9013-1: optlen incorrect
size
Attempted to set option resolver←-
_unicast_ignore_unknown_source
with an incorrect optlen size.
Optlen must be size of int.
CoreApi-9013-2: optval must be 0
or 1
Attempted to set option resolver←-
_unicast_ignore_unknown_source
with an invalid optval.
Optval must be 0 or 1.
CoreApi-9013-3: optval not nu-
meric
Attempted to set option resolver←-
_unicast_ignore_unknown_source
with an invalid optval.
Optval must be numeric.
CoreApi-9013-4: optval not a num-
ber
Attempted to set option resolver←-
_unicast_ignore_unknown_source
with an invalid optval.
Optval must be numeric.
CoreApi-9013-5: optval must be 0
or 1
Attempted to set option resolver←-
_unicast_ignore_unknown_source
with an invalid optval.
Optval must be 0 or 1.
CoreApi-9013-6: optlen incorrect
size
Attempted to retrieve option
resolver_unicast_ignore_←-
unknown_source with an incorrect
optlen size.
Optlen must be size of int.
CoreApi-9013-7: optlen too small Attempted to retrieve option
resolver_unicast_ignore_←-
unknown_source with an incorrect
optlen size.
Optlen must be greater than LBM←-
_MIN_SGET_OPTLEN.
CoreApi-9021-1: optval not nu-
meric
The option value string submitted
contains non numeric characters.
Be sure there are no trailing non
numeric characters such as spaces
and that the number is not in hex-
adecimal.
CoreApi-9021-2: optval must be 0
or 1
ume_quasar_flight_size_behavior
can either be set "ON" or "OFF"
Please use "0" to indicate "OFF"
and "1" to indicate "ON"
CoreApi-9021-3: optlen incorrect
size
The space provided to store the op-
tion was insufficient.
Increase the size of the buffer to 4
bytes.
CoreApi-9021-4: Optlen must
equal sizeof(int).
The optlen parameter must equal
sizeof(int).
Ensure that optval buffer has at
least sizeof(int) space available
and that oplet is set to sizeof(int)
9.2 UM Core API Messages 191
CoreApi-9021-5: optval must be 1
or 0.
The optval must be 1 or 0. Ensure that optval is either set to 1
or 0.
CoreApi-9021-6: optlen not large
enough to hold value
The optlen parameter indicated
that optval was not large enough to
hold the entire value.
Ensure that optval buffer has at
least 2 bytes available and that
optlen is greater than 2.
CoreApi-9044-1: Call to s is not al-
lowed for broker receivers, ignoring
the function call
Deprecated UMQ Index Queuing
function is called
Don't use deprecated UMQ Index
Queuing API
CoreApi-9047-2: src cannot be N←-
ULL
Calling lbm_src_unblock with a N←-
ULL source is not allowed.
The user should make sure a valid
source is passed as a parameter.
CoreApi-9048-1: brokered con-
texts do not support channel
sources
Creating Source Channels is not
supported on a brokered context.
The user should be informed of this
limitation.
CoreApi-9074-1: Queue deregis-
tration is no longer allowed when
using a brokered context
No longer allowed to deregister
from a queue.
Remove function call.
CoreApi-9082-2: lbm_umq_ctx←-
_msg_stable() API is deprecated
The lbm_umq_ctx_msg_stable is
deprecated and no longer sup-
ported.
Remove this API call from the ap-
plication.
CoreApi-9082-3: lbm_ctx_umq←-
_get_inflight() API is deprecated
The lbm_ctx_umq_get_inflight is
deprecated and no longer sup-
ported.
Remove this API call from the ap-
plication.
CoreApi-9087-1: send would block
because of flight size
This send would cause the config-
ured flight size to exceed the con-
figured value for this source.
Delay sending until the number in-
flight messages is reduced.
CoreApi-9089-4: Call to s is not al-
lowed for broker receivers, ignoring
the function call
Deprecated API is called for Bro-
kered receivers
Don't use deprecated API for Bro-
kered receivers
CoreApi-9089-5: Call to s is not ex-
pected for broker receivers, ignor-
ing the function call
Call to the function is not expected
for broker receivers
Contact Informatica Support
CoreApi-9106-10: optval must be 0
or 1
Invalid value for optval optval must be 0 or 1
CoreApi-9106-111: WARNING←-
: could not set SO_TIMESTAMPI←-
NG on multicast source socket: s
An error was returned from the OS
while trying to set the SO_TIM←-
ESTAMPING flag on the source
socket.
SO_TIMESTAMPING is not sup-
ported by this platform.
CoreApi-9106-11: optlen incorrect
size
Size of optlen was incorrect optlen size must be size of int
CoreApi-9106-121: WARNING←-
: could not set SO_TIMESTAMPI←-
NG on multicast receive socket: s
An error was returned from the OS
while trying to set the SO_TIM←-
ESTAMPING flag on the receive
socket.
SO_TIMESTAMPING is not sup-
ported by this platform.
CoreApi-9106-12: optlen too small Size of optlen was too small Size of optlen must be at least 80
CoreApi-9106-1: optlen incorrect
size
Size of optlen was incorrect for set-
ting integer option
optlen must be size of int
CoreApi-9106-2: optval must be 0
or 1
Invalid value for optval optval must be 0 or 1
CoreApi-9106-30: High Resolution
Timestamps are only supported on
Linux platforms for LBT-RM.
Option not valid on this platform. Requires LBT-RM and at least
Linux 2.6.32 and glibc 2.12.
CoreApi-9106-31: High Resolution
Timestamps are only supported on
Linux platforms for LBT-RM.
Option not valid on this platform. Requires LBT-RM and at least
Linux 2.6.32 and glibc 2.12.
192 UM Log Messages
CoreApi-9106-32: High Resolution
Timestamps are only supported on
Linux platforms for LBT-RM.
Option not valid on this platform. Requires LBT-RM and at least
Linux 2.6.32 and glibc 2.12.
CoreApi-9106-33: High Resolution
Timestamps are only supported on
Linux platforms for LBT-RM.
Option not valid on this platform. Requires LBT-RM and at least
Linux 2.6.32 and glibc 2.12.
CoreApi-9106-3: optval not nu-
meric
Option string was not a number Provide number as a string
CoreApi-9106-4: optval must be 0
or 1
Invalid value for optval optval must be 0 or 1
CoreApi-9106-5: optlen incorrect
size
Size of optlen was incorrect optlen size must be size of int
CoreApi-9106-6: optlen too small Size of optlen was too small Size of optlen must be at least 80
CoreApi-9106-7: optlen incorrect
size
Size of optlen was incorrect for set-
ting integer option
optlen must be size of int
CoreApi-9106-8: optval must be 0
or 1
Invalid value for optval optval must be 0 or 1
CoreApi-9106-9: optval not nu-
meric
Option string was not a number Provide number as a string
CoreApi-9160-3: multicast receive
IP_ADD_MEMBERSHIP: s
An error was returned from the OS
while trying to set the socket option
IP_ADD_MEMBERSHIP.
Refer to the OS error number and
message given after the UMS mes-
sage "multicast receive IP_ADD←-
R_MEMBERSHIP".
CoreApi-9170-1: optlen incorrect
size
The oplen parameter is incorrect. Optlen must be sizeof(int).
CoreApi-9170-2: optval not nu-
meric
Optval is not numeric. The optval string must consist of
numbers and an optional sign only.
CoreApi-9170-3: value must be
greater than or equal to zero
Optval is out of range. The optval must be within the range
specified.
CoreApi-9170-4: optlen incorrect
size
The oplen parameter is incorrect. Optlen must be sizeof(int).
CoreApi-9170-5: optlen too small Optlen is too small. Optlen should be at least LBM_M←-
IN_SGET_OPTLEN.
CoreApi-9206-1: Broker source
does not support application chain
headers
Broker source send call is called
with application chain headers
Broker sources does not support
application chain headers
CoreApi-9277-01: registering a file
descriptor/socket event is not al-
lowed with a brokered context
A brokered context does not sup-
port user File Descriptors
The customer can create a sepa-
rate non-brokered context to man-
age File Descriptors
CoreApi-9278-01: Hot-Failover
Sources are not allowed with a
brokered context
User attempted to create a Hot
Failover source with a Broker Con-
text, which is not supported.
The user should not use Hot
Failover sources
CoreApi-9279-1: Round-Robin
cannot be used with flight size in
fragments and in order stability
Flight size in fragments and in or-
der stability enabled, but the ume←-
_store_behavior option is set to
Round-Robin.
Change the ume_store_behavior
option to quorum-consensus to use
this feature.
CoreApi-9280-01: lbm_send_←-
request and lbm_send_request_ex
are not supported with transport
type BROKER
User tried to send a request via
a source set to use the BROKER
transport; this is not currently sup-
ported.
Don't send requests on BROKER
sources.
CoreApi-9289-1: Broker source
can not send messages with nu-
merical index, use named UMQ in-
dex instead
Send call is called with arguments
to send numerical index.
Numerical Index feature is not sup-
ported, use named UMQ index in-
stead
9.2 UM Core API Messages 193
CoreApi-9310-1: XML configura-
tion has already been loaded.
An XML configuration has already
been loaded via UMM and can not
be overridden by loading a different
XML configuration.
Modify the application to not at-
tempt to load a second XML con-
figuration.
CoreApi-9310-2: XML configura-
tion has already been loaded.
An XML configuration has already
been loaded via UMM and can not
be overridden by loading a different
XML configuration.
Modify the application to not at-
tempt to load a second XML con-
figuration.
CoreApi-9346-1: ack must be valid Tried to call api with NULL ack
pointer.
Pass a valid ack pointer instead of
NULL
CoreApi-9352-1: Use of ume_←-
recovery_complete_event requires
ordered delivery to be enabled.
An invalid configuration combina-
tion of the ume recovery com-
plete event and non-ordered deliv-
ery was encountered.
Configure this receiver with or-
dered delivery or disable the ume
recovery complete event.
CoreApi-9352-31: optlen incorrect
size
size of the option is incorrect optlen must be a lbm_uint8_t
CoreApi-9352-32: invalid ume_←-
recovery_complete_event setting
ume_recovery_complete_event set
to invalid value
ume_recovery_complete_event
should be 0 or 1
CoreApi-9352-33: optval not nu-
meric
optval is not a number optval needs to be numeric only
CoreApi-9352-34: invalid ume_←-
recovery_complete_event setting
ume_recovery_complete_event set
to invalid value
ume_recovery_complete_event
must be 0 or 1
CoreApi-9352-35: optlen incorrect
size
optlen is not a lbm_uint8_t optlen should be a lbm_uint8_t
CoreApi-9352-36: optlen too small optlen is too small optlen needs to be at least 80
CoreApi-9401-1: optlen incorrect
size
The size of the optlen given does
not match the size of this option
type.
Provide an optlen the size of a
lbm_ipv4_address_mask_t.
CoreApi-9401-2: optlen incorrect
size
The size of the optlen given does
not match the size of this option
type.
Provide an optlen the size of lbm←-
_ipv4_address_mask_t.
CoreApi-9401-3: optlen too small The size of the buffer passed in was
less than the minimum buffer size
required.
Make sure the buffer is at least L←-
BM_MIN_SGET_OPTLEN bytes in
size.
CoreApi-9524-1: Can't convert
applicationName, out of memory
[s:d]
An attempt to allocate memory
failed.
Check for memory leaks or other
aberrent program behavior. Oth-
erwise, ensure the applicaiton has
adequate resources available.
CoreApi-9524-2: Can't convert ap-
plication name, out of memory [s:d]
An attempt to allocate memory
failed.
Check for memory leaks or other
aberrent program behavior. Oth-
erwise, ensure the applicaiton has
adequate resources available.
CoreApi-9561-1: No response
struct in message [s:d]
The application tried to retrieve a
serialized response but there is no
response structure in the message.
The message type must be a re-
quest message (not data). Do not
call this method on any other type
of message.
CoreApi-9561-2: Error serializing
response [s:d]
The application tried to retrieve a
serialized response but failed while
serializing the response.
This usually indicates a severe out
of memory condition.
CoreApi-9561-3: Byte array not
large enough to hold serialized re-
sponse [s:d]
The application tried to retrieve a
serialized response but failed while
serializing the response.
The provided byte array was not
large enough to hold the serialized
response. Provide a large byte ar-
ray
194 UM Log Messages
CoreApi-9561-4: Serialized re-
sponse length of d was larger than
expected length of d JNI layer [s:d]
Serialized response length was
bigger than expected value for a
serialized response.
Ensure byte array being passed
contains the serialized response of
expected length.
CoreApi-9561-5: Context pointer
was null in JNI layer [s:d]
Context pointer was null in JNI layer
while sending response.
Ensure responses are not being
sent after closing a context.
CoreApi-9561-6: Can't allocate re-
sponse data buffer of u bytes [s:d]
Could not malloc a data buffer. This usually indicates a severe out
of memory condition.
CoreApi-9565-100: optlen incor-
rect size
The size of the optval given does
not match the size of this option
type.
Provide an optval of the appropri-
ate size for this option type.
CoreApi-9565-101: unrecognized
compression algorithm not sup-
ported
An unsupported or unknown com-
pression algorithm name was spec-
ified.
Check configuration for typos and
make sure the UM version supports
any algorithms specified.
CoreApi-9565-102: optval not un-
derstood
An unsupported or unknown com-
pression algorithm was specified.
Check configuration for typos and
make sure the UM version supports
any algorithms specified.
CoreApi-9565-103: optlen incor-
rect size
The size of the optval given does
not match the size of this option
type.
Provide an optval of the appropri-
ate size for this option type.
CoreApi-9565-104: optlen too
small
The provided buffer is too small to
hold the option value.
Provide a larger buffer.
CoreApi-9565-105: Security proto-
col string must be at least u bytes
in length
Security protocols string is too
short.
Check configuration for typos.
CoreApi-9565-106: optlen incor-
rect size
Buffer passed in is too small to hold
the string value of the option.
Pass in a larger buffer.
CoreApi-9565-107: optlen incor-
rect size
Buffer passed in is too small to hold
the string value of the option.
Pass in a larger buffer.
CoreApi-9565-108: The OpenS←-
SL library failed to initialize, so TLS
cannot be used.
The OpenSSL library failed to ini-
tialize correctly, so the TLS security
protocol cannot be supported.
Check OpenSSL library version;
contact Informatica support.
CoreApi-9565-10: optlen too small Provided buffer is too small for the
list of protocols returned.
Pass in a larger buffer.
CoreApi-9565-11: The TLS secu-
rity protocol is not supported with
source transports other than LB←-
T-TCP
The TLS security protocol is not
supported on any transport other
than LBT-TCP; in order to avoid a
false sense of security, we do not
allow TLS to be specified for non-←-
TCP sources.
The user needs to check their con-
figuration
CoreApi-9565-12: If late join is en-
abled, source security and/or com-
pression settings must match those
of the context request port.
Security and compression settings
between the TCP source and the
context's request port differ. This is
not supported for security reasons.
The user needs to check their
configuration and make sure TCP
source and request port security
and compression settings match.
CoreApi-9565-13: Too many secu-
rity protocols specified in list.
Too many protocols were specified
in a protocol list.
Check configuration and make sure
there are no duplicate protocols
specified.
CoreApi-9565-14: Malformed se-
curity protocol name.
A security protocol name was for-
matted incorrectly.
Check configuration files for typos.
CoreApi-9565-15: Security proto-
col "%s" unknown or not supported
An unknown security protocol was
specified.
Check configuration for mistakes or
typos. Make sure the version of UM
used supports the protocols speci-
fied.
CoreApi-9565-16: Duplicate secu-
rity protocols in list.
A duplicate protocol was specified
in a protocol list.
Check configuration and remove
any duplicate protocols.
9.2 UM Core API Messages 195
CoreApi-9565-17: Too many secu-
rity protocols specified.
Too many protocols were specified
in a protocol list.
Check configuration to see if extra
protocols were specified; check UM
version to make sure it supports all
specified protocols.
CoreApi-9565-18: Unknown or un-
supported security protocol speci-
fied.
An unknown protocol was specified
in a protocol list.
Check configuration to see if extra
protocols were specified; check UM
version to make sure it supports all
specified protocols.
CoreApi-9565-19: Security proto-
col list contains duplicate entries.
A duplicate protocol was present in
a protocol list.
Check configuration to see if extra
protocols were specified; check UM
version to make sure it supports all
specified protocols.
CoreApi-9565-20: At least one se-
curity protocol must be specified.
No protocols were specified in a
protocol list.
Make sure at least one protocol is
specified.
CoreApi-9565-21: LZ4 could not
compress data of length u; set
datagram max size option to a
smaller value.
LZ4 compression would expand
the data given to a size greater than
the configured max datagram size.
This should usually not happen un-
less the max datagram size for TCP
transports is set to something very
small; check the value of the max
datagram option.
CoreApi-9565-22: LZ4 could not
compress data of length u; an in-
ternal error occurred
LZ4 compression failed somehow. Contact Informatica support.
CoreApi-9565-23: LZ4 com-
pressed data appears corrupt;
decompressed u bytes, but ex-
pected u bytes
LZ4 decompression failed. This could happen due to corrup-
tion of the data in a TCP stream or
an internal LZ4 error. Contact Infor-
matica support.
CoreApi-9565-3: Too many secu-
rity protocols specified.
Too many security protocols were
specified in the security protocol
list.
Make sure no duplicate protocols
were specified.
CoreApi-9565-44: Could not allo-
cate cipher name.
Allocating the cipher name string
failed; this probably means UM is
out of memory.
Contact Informatica support.
CoreApi-9565-45: optlen incorrect
size
Buffer provided was too small to
hold the configured value.
Pass in a larger buffer.
CoreApi-9565-47: optlen incorrect
size
Buffer passed in is too small to hold
the string value of the option.
Pass in a larger buffer.
CoreApi-9565-48: optlen incorrect
size
Buffer passed in is too small to hold
the string value of the option.
Pass in a larger buffer.
CoreApi-9565-49: optlen incorrect
size
Buffer passed in is too small to hold
the string value of the option.
Pass in a larger buffer.
CoreApi-9565-4: Unknown or un-
supported security protocol speci-
fied.
An unknown protocol was speci-
fied.
Check configuration for typos and
check UM library version to make
sure it supports the specified pro-
tocol.
CoreApi-9565-50: optlen incorrect
size
Buffer passed in is too small to hold
the string value of the option.
Pass in a larger buffer.
CoreApi-9565-51: optlen incorrect
size
Buffer passed in is too small to hold
the string value of the option.
Pass in a larger buffer.
CoreApi-9565-52: optlen incorrect
size
Buffer passed in is too small to hold
the string value of the option.
Pass in a larger buffer.
CoreApi-9565-53: optlen incorrect
size
Buffer passed in is too small to hold
the string value of the option.
Pass in a larger buffer.
CoreApi-9565-54: optlen incorrect
size
Buffer passed in is too small to hold
the string value of the option.
Pass in a larger buffer.
196 UM Log Messages
CoreApi-9565-55: optlen incorrect
size
Buffer passed in is too small to hold
the string value of the option.
Pass in a larger buffer.
CoreApi-9565-56: optlen incorrect
size
Buffer passed in is too small to hold
the string value of the option.
Pass in a larger buffer.
CoreApi-9565-57: optlen incorrect
size
The provided buffer is too small to
hold the option value.
Provide a larger buffer.
CoreApi-9565-58: optlen incorrect
size
The provided buffer is too small to
hold the option value.
Provide a larger buffer.
CoreApi-9565-59: optlen incorrect
size
The provided buffer is too small to
hold the option value.
Provide a larger buffer.
CoreApi-9565-5: Security protocol
list contains duplicate entries.
Specified protocol list has one or
more duplicate values.
Remove duplicate entries from the
protocol list.
CoreApi-9565-60: optlen incorrect
size
The provided buffer is too small to
hold the option value.
Provide a larger buffer.
CoreApi-9565-61: optlen incorrect
size
The provided buffer is too small to
hold the option value.
Provide a larger buffer.
CoreApi-9565-62: optlen incorrect
size
The size of the optval given does
not match the size of this option
type.
Provide an optval of the appropri-
ate size for this option type.
CoreApi-9565-63: optval must be 0
or 1
This option can only be set to 0 or
1, but something else was speci-
fied.
Check configuration options for ty-
pos.
CoreApi-9565-64: optval not nu-
meric
This option is a numeric type, but
a non-numeric string was given in
optval.
Check configuration options for ty-
pos.
CoreApi-9565-65: optval not a
number
This option is a numeric type, but
a non-numeric string was given in
optval.
Check configuration options for ty-
pos.
CoreApi-9565-66: optlen incorrect
size
The size of the optval given does
not match the size of this option
type.
Provide an optval of the appropri-
ate size for this option type.
CoreApi-9565-67: optlen too small The provided buffer is too small to
hold the option value.
Provide a larger buffer.
CoreApi-9565-68: optlen incorrect
size
The size of the optval given does
not match the size of this option
type.
Provide an optval of the appropri-
ate size for this option type.
CoreApi-9565-69: unrecognized
compression algorithm not sup-
ported
Option was set to an unsupported
value.
Check configuration and UM ver-
sion for support of the value con-
figured.
CoreApi-9565-6: Sources may not
support both "none" and any other
security protocols at the same time.
A source must have only one secu-
rity protocol configured.
Change the security protocol list to
have only one entry.
CoreApi-9565-70: optval not un-
derstood
Option was set to an unsupported
value.
Check configuration and UM ver-
sion for support of the value con-
figured.
CoreApi-9565-71: optlen incorrect
size
The size of the optval given does
not match the size of this option
type.
Provide an optval of the appropri-
ate size for this option type.
CoreApi-9565-72: optlen too small The provided buffer is too small to
hold the option value.
Provide a larger buffer.
CoreApi-9565-73: optlen incorrect
size
The size of the optval given does
not match the size of this option
type.
Provide an optval of the appropri-
ate size for this option type.
9.2 UM Core API Messages 197
CoreApi-9565-74: optval not nu-
meric
This option is a numeric type, but
a non-numeric string was given in
optval.
Check configuration options for ty-
pos.
CoreApi-9565-75: optval not a
number
This option is a numeric type, but
a non-numeric string was given in
optval.
Check configuration options for ty-
pos.
CoreApi-9565-76: optlen incorrect
size
The size of the optval given does
not match the size of this option
type.
Provide an optval of the appropri-
ate size for this option type.
CoreApi-9565-77: optlen too small The provided buffer is too small to
hold the option value.
Provide a larger buffer.
CoreApi-9565-78: optlen incorrect
size
The size of the optval given does
not match the size of this option
type.
Provide an optval of the appropri-
ate size for this option type.
CoreApi-9565-79: optval not nu-
meric
This option is a numeric type, but
a non-numeric string was given in
optval.
Check configuration options for ty-
pos.
CoreApi-9565-7: At least one secu-
rity protocol must be specified.
No protocols were specified at all -
not even the "none" protocol.
At least one protocol must be spec-
ified.
CoreApi-9565-80: optval not a
number
This option is a numeric type, but
a non-numeric string was given in
optval.
Check configuration options for ty-
pos.
CoreApi-9565-81: optlen incorrect
size
The size of the optval given does
not match the size of this option
type.
Provide an optval of the appropri-
ate size for this option type.
CoreApi-9565-82: optlen too small The provided buffer is too small to
hold the option value.
Provide a larger buffer.
CoreApi-9565-84: optlen incorrect
size
Size of optval passed in is not cor-
rect for this option.
Check the size of the optval to
make sure it is the correct size for
this configuration option type.
CoreApi-9565-85: optval not nu-
meric
Option value must be a number and
is not.
Check configuration.
CoreApi-9565-86: optval not a
number
Option value must be a number and
is not.
Check configuration.
CoreApi-9565-87: optlen incorrect
size
Size of optval passed in is not cor-
rect for this option.
Check the size of the optval to
make sure it is the correct size for
this configuration option type.
CoreApi-9565-88: optlen too small Buffer is too small to hold the string
value of the option.
Pass in a larger buffer.
CoreApi-9565-89: optlen incorrect
size
Size of optval passed in is not cor-
rect for this option.
Check the size of the optval to
make sure it is the correct size for
this configuration option type.
CoreApi-9565-8: Sources may not
support both "none" and any other
security protocols at the same time.
A source must have only one secu-
rity protocol configured.
Change the security protocol list to
have only one entry.
CoreApi-9565-90: optval not nu-
meric
Option must be a number and is
not.
Check configuration.
CoreApi-9565-91: optval not a
number
Option must be a number and is
not.
Check configuration.
CoreApi-9565-92: optlen incorrect
size
Size of optval passed in is not cor-
rect for this option.
Check the size of the optval to
make sure it is the correct size for
this configuration option type.
CoreApi-9565-93: optlen too small Buffer is too small to hold the string
value of the option.
Pass in a larger buffer.
198 UM Log Messages
CoreApi-9565-94: optlen incorrect
size
The size of the optval given does
not match the size of this option
type.
Provide an optval of the appropri-
ate size for this option type.
CoreApi-9565-95: optval must be 0
or 1
Option is numeric and must be set
to either 0 or 1.
Check config for typos.
CoreApi-9565-96: optval not nu-
meric
Option is numeric and must be set
to either 0 or 1.
Check config for typos.
CoreApi-9565-97: optval must be 0
or 1
Option is numeric and must be set
to either 0 or 1.
Check config for typos.
CoreApi-9565-98: optlen incorrect
size
The size of the optval given does
not match the size of this option
type.
Provide an optval of the appropri-
ate size for this option type.
CoreApi-9565-99: optlen too small The provided buffer is too small to
hold the option value.
Provide a larger buffer.
CoreApi-9565-9: At least one secu-
rity protocol must be specified.
No protocols were specified at all -
not even the "none" protocol.
At least one protocol must be spec-
ified.
CoreApi-9566-10: Can't allocate u
bytes [s:d]
The system was not able to allocate
the amount of memory requested.
If the amount requested was par-
ticularly large, the problem may be
a misconfiguration; however if the
amount requested was relatively
small, the physical memory on the
machine may be over committed;
try moving some applications to an-
other machine.
CoreApi-9566-4: Can't allocate u
bytes [s:d]
The system was not able to allocate
the amount of memory requested.
If the amount requested was par-
ticularly large, the problem may be
a misconfiguration; however if the
amount requested was relatively
small, the physical memory on the
machine may be over committed;
try moving some applications to an-
other machine.
CoreApi-9566-5: Can't allocate u
bytes [s:d]
The system was not able to allocate
the amount of memory requested.
If the amount requested was par-
ticularly large, the problem may be
a misconfiguration; however if the
amount requested was relatively
small, the physical memory on the
machine may be over committed;
try moving some applications to an-
other machine.
CoreApi-9566-6: Can't allocate u
bytes [s:d]
The system was not able to allocate
the amount of memory requested.
If the amount requested was par-
ticularly large, the problem may be
a misconfiguration; however if the
amount requested was relatively
small, the physical memory on the
machine may be over committed;
try moving some applications to an-
other machine.
CoreApi-9566-7: Can't allocate
callback vector of u bytes [s:d]
The system was not able to allocate
the amount of memory requested.
The physical memory on the ma-
chine may be over committed; try
moving some applications to an-
other machine.
9.2 UM Core API Messages 199
CoreApi-9566-9: Can't allocate u
bytes [s:d]
The system was not able to allocate
the amount of memory requested.
If the amount requested was par-
ticularly large, the problem may be
a misconfiguration; however if the
amount requested was relatively
small, the physical memory on the
machine may be over committed;
try moving some applications to an-
other machine.
CoreApi-9571-01: network inter-
face specification is too long
The network interface specifica-
tion is limited to 258 characters in
length and has the format "host_←-
domain_name[/num]" where "num"
is the optional number of leading 1
bits in the netmask applied to the
resolved IP address.
Provide a specification that is less
than 258 characters in length.
CoreApi-9571-02: malformed net-
work interface specification
The network interface specifica-
tion is limited to 258 characters in
length and has the format "host_←-
domain_name[/num]" where "num"
is the optional number of leading 1
bits in the netmask applied to the
resolved IP address.
Provide a valid interface specifica-
tion. See RFCs 952 and 1123 for
DNS naming conventions.
CoreApi-9571-03: malformed net-
work interface specification
The network interface specifica-
tion is limited to 258 characters in
length and has the format "host_←-
domain_name[/num]" where "num"
is the optional number of leading 1
bits in the netmask applied to the
resolved IP address.
Provide a valid interface specifica-
tion. See RFCs 952 and 1123 for
DNS naming conventions.
CoreApi-9571-04: malformed net-
work interface specification with
network mask
The CIDR (Classless Inter-Domain
Routing) notation is a syntax for
specifying IP addresses and their
associated routing prefix. It ap-
pends a slash character to the ad-
dress and the decimal number of
leading bits of the routing prefix,
e.g., host_domain_name/24. The
valid range of values is 0-32 inclu-
sive.
Provide a valid interface specifica-
tion.
CoreApi-9571-05: invalid netmask
value
The CIDR (Classless Inter-Domain
Routing) notation is a syntax for
specifying IP addresses and their
associated routing prefix. It ap-
pends a slash character to the ad-
dress and the decimal number of
leading bits of the routing prefix,
e.g., host_domain_name/24. The
valid range of values is 0-32 inclu-
sive.
Specify a valid decimal value to de-
fine the number of bits in the mask
prefix.
CoreApi-9571-06: hostname is too
short
The domain host name must be at
least 2 characters long.
Provide a host domain name that is
at least 2 characters in length.
CoreApi-9571-07: unknown host
name: s
The DNS lookup, using gethostby-
name() with supplied host name,
failed to resolve to an IP address.
Verify the host domain name.
CoreApi-9571-08: unknown IPv4
host name: s
The DNS lookup, using gethostby-
name() with supplied host name,
failed to resolve to an IPv4 address.
Verify the host domain name refers
to an IPv4 address.
200 UM Log Messages
CoreApi-9571-09: invalid address The IP address returned by the
DNS lookup failed to convert the
Internet host address character
string from the IPv4 dotted-decimal
notation into binary form (in net-
work byte order).
Contact Informatica customer sup-
port.
CoreApi-9571-11: domain name is
too long
The domain name is limited to 258
characters in length.
Provide a domain name that is less
than 258 characters in length.
CoreApi-9571-12: malformed do-
main name
The domain name is a text string of
2 to 80 characters in length drawn
from a mix of alphbetic (a-z), digit
(0-9), the minus sign (-), and period
(.) characters.
Provide a valid name. See RFCs
952 and 1123 for DNS naming con-
ventions.
CoreApi-9571-13: hostname is too
short
The name must be at least 2 char-
acters long.
Provide a name that is at least 2
characters in length.
CoreApi-9571-14: unknown host
name: s
The DNS lookup, using gethostby-
name() with supplied name, failed
to resolve to an IP address.
Verify the host name.
CoreApi-9571-15: unknown IPv4
name: s
The DNS lookup, using gethostby-
name() with supplied name, failed
to resolve to an IPv4 address.
Verify the name refers to an IPv4
address.
CoreApi-9571-21: BrokerIP←-
:RemotePort is malformed
The broker specification string
format is as follows: [Interface[←-
:LocalPort]->]BrokerIP:Remote←-
Port where Interface and LocalPort
refer the local host interface and
port, the BrokerIP refers to the
broker's IP address, and the
RemotePort refers to the broker's
UDP port.
Provide a valid broker specification.
CoreApi-9571-22: DaemonIP←-
:RemotePort is malformed
The unicast resolver daemon spec-
ification string format is as follows:
[Interface[:LocalPort]->]Daemon←-
IP:RemotePort where Interface
and LocalPort refer the local host
interface and port, the DaemonIP
refers to the resolver daemon's
IP address, and the RemotePort
refers to the resolver daemon's
UDP port.
Provide a valid resolver daemon
specification.
CoreApi-9605-1: Brokered Con-
text does not support security/com-
pression
A context can not be a Security
and/or Compression and Brokered
context concurrently.
Configure context either as Secure
and/or Compression or Brokered
context, but not both. Turning
on security/compression won't se-
cure/compress connections to bro-
ker.
CoreApi-9650-01: optlen incorrect
size
The size of the optval given does
not match the size of this option
type.
Provide an optval of the appropri-
ate size for this option type.
CoreApi-9650-02: unrecognized
compression algorithm not sup-
ported
Option was set to an unsupported
value.
Check configuration and UM ver-
sion for support of the value con-
figured.
CoreApi-9650-03: optval not un-
derstood
Option was set to an unsupported
value.
Check configuration and UM ver-
sion for support of the value con-
figured.
9.2 UM Core API Messages 201
CoreApi-9650-04: optlen incorrect
size
The size of the optval given does
not match the size of this option
type.
Provide an optval of the appropri-
ate size for this option type.
CoreApi-9650-05: optlen too small The provided buffer is too small to
hold the option value.
Provide a larger buffer.
CoreApi-9666-01: optlen incorrect
size
The size of the optval given does
not match the size of this option
type.
Provide an optval of the appropri-
ate size for this option type.
CoreApi-9666-02: optval not nu-
meric
This option is a numeric type, but
a non-numeric string was given in
optval.
Check configuration options for ty-
pos.
CoreApi-9666-03: optval not a
number
This option is a numeric type, but
a non-numeric string was given in
optval.
Check configuration options for ty-
pos.
CoreApi-9666-04: optlen incorrect
size
The size of the optval given does
not match the size of this option
type.
Provide an optval of the appropri-
ate size for this option type.
CoreApi-9666-05: optlen too small The provided buffer is too small to
hold the option value.
Provide a larger buffer.
CoreApi-9720-01: Sending mul-
ticast immediate message on a
Security/Compression Context is
not allowed.
A context configured for security
and/or compression is not allowed
to use multicast.
The user could create multiple
contexts and selectively configure
them as security and/or compres-
sion
CoreApi-9720-02: Sending mul-
ticast immediate message on a
Security/Compression Context is
not allowed.
A context configured for security
and/or compression is not allowed
to use multicast.
Configuration error with DRO's.
CoreApi-9720-03: Sending mul-
ticast immediate request on a
Security/Compression Context is
not allowed.
A context configured for security
and/or compression is not allowed
to use multicast.
The user could create multiple
contexts and selectively configure
them as security and/or compres-
sion
CoreApi-9721-10: Source [p] UME
is not supported with the LBM_M←-
SG_BUFF_ALLOC flag.
A call to lbm_src_alloc_msg_buff
was passed a UME source.
UME sources are not supported at
this time.
CoreApi-9721-1: src cannot be N←-
ULL
A call to lbm_src_alloc_msg_buff
was passed a NULL src.
Specify a valid LBTRM src. Only
LBTRM sources are supported at
this time.
CoreApi-9721-2: usr_bufp cannot
be NULL
A call to lbm_src_alloc_msg_buff
was passed a NULL usr_bufp.
Pass a valid pointer that will contain
the pointer to be used to fill in the
caller's message data.
CoreApi-9721-3: lbm_hdl cannot
be NULL
A call to lbm_src_alloc_msg_buff
was passed a NULL lbm_hdl.
Pass a valid pointer that will contain
the pointer to the returned lbm_←-
hdl. This is what will be passed to a
subsequent lbm_src_send() call.
CoreApi-9721-4: transport for src
must be LBTRM.
A call to lbm_src_alloc_msg_buff
was passed a non LBTRM src.
Specify a valid LBTRM src. Only
LBTRM sources are supported at
this time.
CoreApi-9721-5: length (d) too
long, must be less than d.
A call to lbm_src_alloc_msg_buff
was passed a length that would
cause fragmentation of a message.
Specify a length less than the maxi-
mum length shown in the message.
202 UM Log Messages
CoreApi-9721-6: Passed buffer in-
valid, sqn [d] invalid
The message buffer supplied to a
source send call with the LBM_←-
MSG_BUFF_ALLOC flag set, does
not contain valid identifiers.
Check to make sure that the sup-
plied message buffer was allocated
with a call to lbm_src_alloc_←-
msg_buff() and is the handle to the
buffer and not the actual message
data pointer. See the documenta-
tion for the lbm_src_alloc_msg←-
_buff() call.
CoreApi-9721-7: Passed buffer in-
valid, tidx [d] invalid
The message buffer supplied to a
source send call with the LBM_←-
MSG_BUFF_ALLOC flag set, does
not contain valid identifiers.
Check to make sure that the sup-
plied message buffer was allocated
with a call to lbm_src_alloc_←-
msg_buff() and is the handle to the
buffer and not the actual message
data pointer. See the documenta-
tion for the lbm_src_alloc_msg←-
_buff() call.
CoreApi-9721-8: Source [p] type
[u] is not LBTRM. LBTRM is re-
quired with the LBM_MSG_BUF←-
F_ALLOC flag.
The source supplied to a source
send call with the LBM_MSG_BU←-
FF_ALLOC flag set was not an L←-
BTRM source.
At this time, only LBTRM sources
are supported when using the LB←-
M_MSG_BUFF_ALLOC flag. Use
only LBTRM sources when speci-
fying the LBM_MSG_BUFF_ALL←-
OC flag.
CoreApi-9721-9: Source [p] UM←-
Q/ULB is not supported with the L←-
BM_MSG_BUFF_ALLOC flag.
A call to lbm_src_alloc_msg_buff
was passed a UMQ (or ULB)
source.
UMQ sources are not supported at
this time.
CoreApi-9722-1: UMQ functional-
ity requested but the library does
not support UMQ.
The option umq_queue_←-
participation is only included in
the UM Queuing edition. An at-
tempt to enable this option was
made with either the UM Streaming
edition or UM Persistence edition
library.
If queuing is not required in the
application, then modify either the
configuration file that sets this op-
tion, or modify the code that is pro-
grammatically attempting to set this
option.
CoreApi-9722-2: UMQ functional-
ity requested but the library does
not support UMQ.
The option umq_queue_←-
participation is only included in
the UM Queuing edition. An at-
tempt to enable this option was
made with either the UM Streaming
edition or UM Persistence edition
library.
If queuing is not required in the
application, then modify either the
configuration file that sets this op-
tion, or modify the code that is pro-
grammatically attempting to set this
option.
CoreApi-9722-3: UMP functionality
requested but the library does not
support UMP.
The option ume_use_store is only
included in the UM Persistence edi-
tion. An attempt to enable this op-
tion was made with the UM Stream-
ing edition library.
If persistence is not required in the
application, then modify either the
configuration file that sets this op-
tion, or modify the code that is pro-
grammatically attempting to set this
option.
CoreApi-9722-4: UMP functionality
requested but the library does not
support UMP.
The option ume_use_store is only
included in the UM Persistence edi-
tion. An attempt to enable this op-
tion was made with the UM Stream-
ing edition library.
If persistence is not required in the
application, then modify either the
configuration file that sets this op-
tion, or modify the code that is pro-
grammatically attempting to set this
option.
CoreApi-9727-01: Compression is
not supported with source trans-
ports other than LBT-TCP
Compression is not supported on
any transport other than LBT-TCP.
The user needs to check their con-
figuration
CoreApi-9728-01: Context config-
ured to use TLS, but TLS is not
available.
Creating the TLS context failed, but
the user configured the LBM con-
text to use TLS.
Check OpenSSL library version.
Contact Informatica support.
9.2 UM Core API Messages 203
CoreApi-9728-02: Context config-
ured to use TLS, but TLS is not
available.
Creating the TLS context failed, but
the user configured the LBM con-
text to use TLS.
Check OpenSSL library version.
Contact Informatica support.
CoreApi-9743-01: optlen incorrect
size
The size of the optlen given does
not match the size of this option
type.
Provide an optlen the size of a
lbm_ulong_t.
CoreApi-9743-02: invalid proactive
keepalive interval setting
Invalid setting for the proactive
keepalive interval
Valid settings are >= 1500 (the ef-
fective minimum), or 0 to disable
keepalive
CoreApi-9743-03: optval not nu-
meric
This option is a numeric type, but
a non-numeric string was given in
optval.
Check configuration options for ty-
pos.
CoreApi-9743-04: optval not a
number
This option is a numeric type, but
a non-numeric string was given in
optval.
Check configuration options for ty-
pos.
CoreApi-9743-05: invalid proactive
keepalive interval setting
Invalid setting for the proactive
keepalive interval
Valid settings are >= 1500 (the ef-
fective minimum), or 0 to disable
keepalive
CoreApi-9743-06: optlen incorrect
size
The size of the optlen given does
not match the size of this option
type.
Provide an optlen of the appropri-
ate size for this option type.
CoreApi-9743-07: optlen too small The provided buffer is too small to
hold the option value.
Provide a larger buffer.
CoreApi-9779-1: optlen incorrect
size
Checks whether optlen is an appro-
priate size and returns to caller if
opten is an incorrect size.
Set the optlen value to the size of
lbm_ulong_t
CoreApi-9779-2: optval not nu-
meric
Checks whether optval points to a
numeric value and returns to caller
if optval points to a non numeric
value.
Setup optval to a numeric value.
CoreApi-9779-3: optval not a num-
ber
Checks whether optval points to a
numeric value and returns to caller
if optval points to a non numeric
value.
Setup optval to a numeric value.
CoreApi-9779-4: optlen incorrect
size
Checks whether optlen is an appro-
priate size and returns to caller if
optlen size is incorrect.
Set the optlen value to the size of
lbm_ulong_t
CoreApi-9779-5: optlen too small Checks whether optlen is an appro-
priate size and returns to caller if
optlen size is incorrect.
Set the optlen value to the size of
lbm_ulong_t
CoreApi-9798-10: optlen too small Checks whether optlen is an appro-
priate size and returns to caller if
optlen size is incorrect.
Set the optlen value to the size of
lbm_ulong_t
CoreApi-9798-1: optlen incorrect
size
Checks whether optlen is an appro-
priate size and returns to caller if
opten is an incorrect size.
Set the optlen value to the size of
lbm_ulong_t
CoreApi-9798-2: optval not nu-
meric
Checks whether optval points to a
numeric value and returns to caller
if optval points to a non numeric
value.
Setup optval to a numeric value.
CoreApi-9798-3: optval not a num-
ber
Checks whether optval points to a
numeric value and returns to caller
if optval points to a non numeric
value.
Setup optval to a numeric value.
204 UM Log Messages
CoreApi-9798-4: optlen incorrect
size
Checks whether optlen is an appro-
priate size and returns to caller if
optlen size is incorrect.
Set the optlen value to the size of
lbm_ulong_t
CoreApi-9798-5: optlen too small Checks whether optlen is an appro-
priate size and returns to caller if
optlen size is incorrect.
Set the optlen value to the size of
lbm_ulong_t
CoreApi-9798-6: optlen incorrect
size
Checks whether optlen is an appro-
priate size and returns to caller if
opten is an incorrect size.
Set the optlen value to the size of
lbm_ulong_t
CoreApi-9798-7: optval not nu-
meric
Checks whether optval points to a
numeric value and returns to caller
if optval points to a non numeric
value.
Setup optval to a numeric value.
CoreApi-9798-8: optval not a num-
ber
Checks whether optval points to a
numeric value and returns to caller
if optval points to a non numeric
value.
Setup optval to a numeric value.
CoreApi-9798-9: optlen incorrect
size
Checks whether optlen is an appro-
priate size and returns to caller if
optlen size is incorrect.
Set the optlen value to the size of
lbm_ulong_t
CoreApi-9890-01: optlen for
transport_lbtipc_pend_behavior_←-
linger_loop_count incorrect size
The correct size when setting the
transport_lbtipc_pend_behavior_←-
linger_loop_count option is sizeof
lbm_ulong_t
Make sure the correct size is allo-
cated
CoreApi-9890-02: optval for
transport_lbtipc_pend_behavior_←-
linger_loop_count not numeric
The string for transport_lbtipc_←-
pend_behavior_linger_loop_count
is not a numeric
Make sure a numeric value is
passed in the string
CoreApi-9890-03: optval for
transport_lbtipc_pend_behavior_←-
linger_loop_count not a number
The string for transport_lbtipc_←-
pend_behavior_linger_loop_count
is not a number
Make sure a number value is
passed in the string
CoreApi-9890-04: optlen for
transport_lbtipc_pend_behavior_←-
linger_loop_count incorrect size
The correct size when getting the
transport_lbtipc_pend_behavior_←-
linger_loop_count option is sizeof
lbm_ulong_t
Make sure the correct size is allo-
cated
CoreApi-9890-05: optlen for
transport_lbtipc_pend_behavior←-
_linger_loop_count string too
small
The correct size when getting the
string value for the transport_←-
lbtipc_pend_behavior_linger_←-
loop_count is LBM_MIN_SGET_←-
OPTLEN
Make sure the correct string size is
allocated
CoreApi-9901-01: target SOURCE
type: transport found but return ad-
dress is not available (s)
An attempt to Unicast a message
or request using a SOURCE that
does not contain the return ad-
dress.
This is likely a result of using an
older version of LBM at the source
which does not necessarily include
the return address.
CoreApi-9901-02: target SOURCE
type: transport not found (s)
An attempt to Unicast a message
or request using a SOURCE string
that is not found in the Topic Cache.
The customer should check the
source string and possibly manage
EOS.
CoreApi-9901-03: target mal-
formed (SOURCE type not valid
(s))
An attempt to Unicast a messaging
or request using a SOURCE string
that is not valid.
The customer should check the
source string.
CoreApi-9901-04: target SOURCE
type: transport found but return ad-
dress is not available (s)
An attempt to Unicast a message
or request using a SOURCE that
does not contain the return ad-
dress.
This is likely a result of using an
older version of LBM at the source
which does not necessarily include
the return address.
CoreApi-9922-01: lbm_flush_all
ctx cannot be NULL
User passed NULL for the context
parameter. NULL is not a valid con-
text.
The user needs to check their im-
plementation.
9.2 UM Core API Messages 205
CoreApi-9923-01: optlen incorrect
size
The option receive_batch_←-
notification_function setopt size
must be sizeof lbm_rcv_batch_←-
notify_func_t
Use the correct size for the op-
tion receive_batch_notification_←-
function
CoreApi-9923-02: receive batch
notification start function must be
valid
The option receive_batch_←-
notification_function setopt must
have a valid start function callback
defined
Define the start function for op-
tion receive_batch_notification_←-
function
CoreApi-9923-03: receive batch
notification end function must be
valid
The option receive_batch_←-
notification_function setopt must
have a valid end function callback
defined
Define the end function for op-
tion receive_batch_notification_←-
function
CoreApi-9923-04: str_setopt not
supported for option
str_setopt on receive_batch_←-
notification_function not supported
the customer needs to use the non-
string setopt function
CoreApi-9923-05: optlen incorrect
size
The option receive_batch_←-
notification_function getopt size
must be sizeof lbm_rcv_batch_←-
notify_func_t
Use the correct size for the op-
tion receive_batch_notification_←-
function
CoreApi-9923-06: str_getopt not
supported for option
str_getopt on receive_batch_←-
notification_function not supported
the customer needs to use the non-
string getopt function
CoreApi-9938-1: optlen incorrect
size
Attempted to set option
compatibility_pre_um_6_0_←-
context_ad_ivl with an incorrect
optlen size.
Optlen must be size of unsigned
long.
CoreApi-9938-2: invalid pre60 con-
text ad interval setting
Attempted to set option
compatibility_pre_um_6_0_←-
context_ad_ivl to an invalid value.
Option must be set to 0 or a value
>500 milliseconds.
CoreApi-9938-3: optval not nu-
meric
Attempted to set option
compatibility_pre_um_6_0_←-
context_ad_ivl with an invalid
optval
Optval must be numeric.
CoreApi-9938-4: optval not a num-
ber
Attempted to set option
compatibility_pre_um_6_0_←-
context_ad_ivl with an invalid
optval
Optval must be numeric.
CoreApi-9938-5: optlen incorrect
size
Attempted to retrieve option
compatibility_pre_um_6_0_←-
context_ad_ivl with an incorrect
optlen size.
Optlen must be size of unsigned
long.
CoreApi-9938-6: optlen too small Attempted to set option
compatibility_pre_um_6_0_←-
context_ad_ivl with an incorrect
optlen size.
Optlen must be greater than LBM←-
_MIN_SGET_OPTLEN.
CoreApi-9941-115: usr_bufp offset
is not valid.
A smart source call specified a user
buffer with an invalid offset.
Supply the exact pointer supplied
by lbm_ssrc_buff_get().
CoreApi-9941-116: usr_bufp base
address is not valid.
A smart source call specified a user
buffer with an invalid base address.
Return buffer with the exact pointer
supplied by lbm_ssrc_buff_get().
CoreApi-9941-117: user buffer is
on the free list.
A smart source call specified a user
buffer that is on the free list.
Don't be stupid! Invoke lbm_←-
ssrc_buff_get() to allocate a user
buffer.
CoreApi-9941-118: corrupted user
buffer pointer structure
A smart source call specified what
appears to be a corrupted user
buffer pointer structure.
Ensure that writes using the user
buffer pointer do not exceed the
range of addresses bounded by the
source scoped smart_src_max_←-
message_length configuration op-
tion.
206 UM Log Messages
CoreApi-9941-11: optlen incorrect
size
smart_src_user_buffer_count
value contained an incorrect length
smart_src_user_buffer_count
should be of sizeof(int)
CoreApi-9941-12: optval must be
greater than 0
smart_src_user_buffer_count did
not contain a positive integer
smart_src_user_buffer_count must
be a positive integer
CoreApi-9941-13: optval too large smart_src_user_buffer_count is
larger than the maximum allowed
size
Decrease the size of smart_src_←-
user_buffer_count
CoreApi-9941-14: optval not nu-
meric
smart_src_user_buffer_count
value is not numeric
smart_src_user_buffer_count must
be a numeric value
CoreApi-9941-15: optval must be
greater than 0
smart_src_user_buffer_count did
not contain a positive integer
smart_src_user_buffer_count must
be a positive integer
CoreApi-9941-16: optval too large smart_src_user_buffer_count is
larger than the maximum allowed
size
Decrease the size of smart_src_←-
user_buffer_count
CoreApi-9941-17: optlen incorrect
size
The size of the option was too large
or too small
smart_src_user_buffer_count must
be sizeof(int)
CoreApi-9941-18: optlen too small The size of the option buffer was
too small to contain the option
smart_src_user_buffer_count
optlen must be at least 80
CoreApi-9941-1: optlen incorrect
size
smart_src_max_message_length
value contained an incorrect length
smart_src_max_message_length
should be of sizeof(int)
CoreApi-9941-21: optlen incorrect
size
smart_src_retention_buffer_count
value contained an incorrect length
smart_src_retention_buffer_count
should be of sizeof(int)
CoreApi-9941-22: optval must be
greater than 0
smart_src_retention_buffer_count
did not contain a positive integer
smart_src_retention_buffer_count
must be a positive integer
CoreApi-9941-23: optval too large smart_src_retention_buffer_count
is larger than the maximum allowed
size
Decrease the size of smart_src_←-
retention_buffer_count
CoreApi-9941-24: optval not nu-
meric
smart_src_retention_buffer_count
value was not numeric
smart_src_retention_buffer_count
must be a numeric value
CoreApi-9941-25: optval must be
greater than 0
smart_src_retention_buffer_count
did not contain a positive integer
smart_src_retention_buffer_count
must be a positive integer
CoreApi-9941-26: optval too large smart_src_retention_buffer_count
is larger than the maximum allowed
size
Decrease the size of smart_src_←-
retention_buffer_count
CoreApi-9941-27: optlen incorrect
size
The size of the option was too large
or too small
smart_src_retention_buffer_count
is sizeof(int)
CoreApi-9941-28: optlen too small The size of the option buffer was
too small to contain the option
smart_src_retention_buffer_count
optlen must be at least 80
CoreApi-9941-2900: Smart Source
not supported on this platform
Smart Source is not supported on
this platform
Smart Source is supported on 64-
bit Linux and Windows platforms
CoreApi-9941-2980: ssrcp must be
valid
ssrcp parameter was NULL ssrcp must be a valid pointer
CoreApi-9941-2981: ctx must be
valid
ctx parameter was NULL ctx must be a pointer to a valid con-
text
CoreApi-9941-2982: topic must be
valid
topic parameter was NULL topic must be a pointer to a valid
topic
CoreApi-9941-2983: ctx is reactor
only
The context passed as a parame-
ter is a reactor context used for re-
trieving statistics for a monitoring
source controller.
Do not create an lbm smart source
on a reactor context.
CoreApi-9941-2984: topic passed
to lbm_ssrc_create was not cre-
ated on the same context
topic parameter was not created on
the same context as the ctx param-
eter
topic parameter must have been
created on the context in the ctx pa-
rameter
9.2 UM Core API Messages 207
CoreApi-9941-2985: topic already
associated with a source
The application attempted to create
a smart source on a topic that is al-
ready associated with a source.
Delete the associated source and
try again.
CoreApi-9941-2988: transport type
unknown
The context is associated with an
unknown transport type.
Contact support.
CoreApi-9941-2989: ssrc must be
valid
ssrc parameter was NULL ssrc must be a pointer to a valid lbm
smart source.
CoreApi-9941-2996: ssrc must be
valid
The ssrc parameter supplied to a
smart source send call was NULL.
ssrc must be a pointer to a valid lbm
smart source.
CoreApi-9941-2997: usr_bufp
must be valid
The usr_bufp parameter supplied
to a smart source send call was N←-
ULL.
usr_bufp must be a pointer to a
valid user buffer.
CoreApi-9941-2: optval must be
greater than 0
smart_src_max_message_length
did not contain a positive integer
smart_src_max_message_length
must be a positive integer
CoreApi-9941-3000: lbm_ssrc_←-
send_ex() thread does not match
thread used by other smart source
sends on this transport session
The smart source send call thread
does not match the thread used by
other smart source sends on this
transport session.
The smart source send call thread
must be the same thread used
by all smart source sends on this
transport session.
CoreApi-9941-3001: lbm_ssrc_←-
send_ex() thread does not match
thread used by other smart source
sends on this transport session
The smart source send call thread
does not match the thread used by
other smart source sends on this
transport session.
The smart source send call thread
must be the same thread used
by all smart source sends on this
transport session.
CoreApi-9941-3025: ssrc must be
valid
The Smart Source object is not
valid.
Provide a valid Smart Source ob-
ject.
CoreApi-9941-3026: stats must be
valid
The transport statistics object is not
valid.
Provide a valid object.
CoreApi-9941-3027: ssrc must be
valid
The Smart Source object is not
valid.
Provide a valid Smart Source ob-
ject.
CoreApi-9941-31: optlen incorrect
size
transport_lbtrm_smart_src_←-
transmission_window_buffer_←-
count value contained an incorrect
length
transport_lbtrm_smart_src_←-
transmission_window_buffer_←-
count should be of sizeof(int)
CoreApi-9941-32: optval must be
greater than 0
transport_lbtrm_smart_src_←-
transmission_window_buffer_←-
count did not contain a positive
integer
transport_lbtrm_smart_src_←-
transmission_window_buffer_←-
count must be a positive integer
CoreApi-9941-33: optval too large transport_lbtrm_smart_src_←-
transmission_window_buffer_←-
count is larger than the maximum
allowed size
Decrease the size of transport_←-
lbtrm_smart_src_transmission_←-
window_buffer_count
CoreApi-9941-34: optval not nu-
meric
transport_lbtrm_smart_src_←-
transmission_window_buffer_←-
count value was not numeric
transport_lbtrm_smart_src_←-
transmission_window_buffer_←-
count must be a numeric value
CoreApi-9941-35: optval must be
greater than 0
transport_lbtrm_smart_src_←-
transmission_window_buffer_←-
count did not contain a positive
integer
transport_lbtrm_smart_src_←-
transmission_window_buffer_←-
count must be a positive integer
CoreApi-9941-36: optval too large transport_lbtrm_smart_src_←-
transmission_window_buffer_←-
count is larger than the maximum
allowed size
Decrease the size of transport_←-
lbtrm_smart_src_transmission_←-
window_buffer_count
CoreApi-9941-37: optlen incorrect
size
The size of the option was too large
or too small
transport_lbtrm_smart_src_←-
transmission_window_buffer_←-
count must be sizeof(int)
208 UM Log Messages
CoreApi-9941-38: optlen too small The size of the option buffer was
too small to contain the option
transport_lbtrm_smart_src_←-
transmission_window_buffer_←-
count optlen must be at least
80
CoreApi-9941-3996: ssrc must be
valid
ssrc parameter was NULL ssrc must be a pointer to a valid lbm
smart source.
CoreApi-9941-3997: usr_bufp
must be valid
usr_bufp parameter was NULL usr_bufp must be a valid pointer
CoreApi-9941-3999: Smart Source
[p] does not support UMQ/ULB at
this time.
A call to lbm_ssrc_buff_get was
passed a UMQ (or ULB) source.
UMQ sources are not supported at
this time.
CoreApi-9941-3: optval too large smart_src_max_message_length
is larger than the maximum allowed
size
Decrease the size of smart_src_←-
max_message_length
CoreApi-9941-4001: All d Smart
Source [p] user buffers have been
allocated.
A call to lbm_ssrc_buff_get failed
due to user buffer exhaustion.
Return unused user buffers via
lbm_ssrc_buff_put() or restart the
application with a larger user buffer
count.
CoreApi-9941-4020: ssrc must be
valid
ssrc parameter was NULL ssrc must be a pointer to a valid lbm
smart source.
CoreApi-9941-4021: usr_bufp
must be valid
usr_bufp parameter was NULL usr_bufp must be a pointer to a
valid user buffer.
CoreApi-9941-4022: usr_bufp off-
set is not valid.
A call to lbm_ssrc_buff_put speci-
fied a user buffer with an invalid off-
set.
Return buffer with the exact pointer
supplied by lbm_ssrc_buff_get().
CoreApi-9941-4023: usr_bufp
base address is not valid.
A call to lbm_ssrc_buff_put spec-
ified a user buffer with an invalid
base address.
Return buffer with the exact pointer
supplied by lbm_ssrc_buff_get().
CoreApi-9941-4024: user buffer is
already on the free list.
A call to lbm_ssrc_buff_put speci-
fied a user buffer the is already on
the free list.
Don't be stupid! A buffer can only
be returned once.
CoreApi-9941-4: optval not nu-
meric
smart_src_max_message_length
value is not numeric
smart_src_max_message_length
must be a numeric value
CoreApi-9941-5551: Smart source
can not be configured as broker
source
An lbm smart source can not be
configured as broker.
Do not configure lbm smart source
as Broker.
CoreApi-9941-5552: Smart source
can not be configured as ulb source
An lbm smart source can not be
configured as ulb source.
Do not configure lbm smart source
as ULB.
CoreApi-9941-5554: Smart source
can not be configured to be pre-
6.0 compatible
An lbm smart source can not be
configured to be pre-6.0 compati-
ble.
Do not configure lbm smart source
to inter-operate with pre-6.0 appli-
cations.
CoreApi-9941-5555: Smart source
cannot be configured for TCP
transport
An lbm smart source can not be
configured for TCP transport.
Smart source can only be config-
ured with a LBT-RM transport.
CoreApi-9941-5557: Smart source
can not be configured for LBT-IPC
transport
An lbm smart source can not be
configured for LBT-IPC transport.
Smart source can only be config-
ured with a LBT-RM transport.
CoreApi-9941-5558: Smart source
can not be configured for LBT-SMX
transport
An lbm smart source can not be
configured for LBT-SMX transport.
Smart source can only be config-
ured with a LBT-RM transport.
CoreApi-9941-5559: Smart source
can not be configured for LBT-RD←-
MA transport
An lbm smart source can not be
configured for LBT-RDMA trans-
port.
Smart source can only be config-
ured with a LBT-RM transport.
CoreApi-9941-5560: Smart source
can not be configured as Broker
An lbm smart source can not be
configured as Broker.
Smart source can only be config-
ured with a LBT-RM transport.
9.2 UM Core API Messages 209
CoreApi-9941-5565: Smart source
may not use the same transport as
a standard source
An lbm smart source may not re-
side with a standard source on the
same transport.
Configure the smart source on an
LBT-RM transport that only con-
tains smart sources.
CoreApi-9941-5566: smart_src←-
_max_message_length exceeds
the configured maximum message
length for this transport session.
The first Smart Source to create
a transport session establishes the
maximum message length for all
subsequent Smart Sources on that
transport.
Decrease the size of smart_←-
src_max_message_length for this
Smart Source or increase the
size of smart_src_max_message←-
_length for the first Smart Source
created on this transport session.
CoreApi-9941-5571: Could not
allocate lu bytes. The mem-
ory needed for smart_src_user←-
_buffer_count exceeds available
memory on your system.
The memory needed for smart←-
_src_user_buffer_count is more
memory than is available on your
system.
Decrease the size of smart_src_←-
user_buffer_count.
CoreApi-9941-5572: Could not
allocate lu bytes. The product of
smart_src_user_buffer_count and
smart_src_max_message_length
exceeds available memory on your
system.
The product of smart_src_user_←-
buffer_count and smart_src_max←-
_message_length specifies more
memory than is available on your
system.
Decrease the size of smart_←-
src_user_buffer_count and/or the
smart_src_max_message_length.
CoreApi-9941-5573: Could not
allocate lu bytes. The product of
smart_src_retention_buffer_count
and smart_src_max_message_←-
length exceeds available memory
on your system.
The product of smart_src←-
_retention_buffer_count and
smart_src_max_message_length
specifies more memory than is
available on your system.
Decrease the size of smart_src←-
_retention_buffer_count and/or the
smart_src_max_message_length.
CoreApi-9941-5574: Could not
allocate lu bytes. The product
of transport_lbtrm_smart_src←-
_transmission_window_buffer←-
_count and smart_src_max_←-
message_length exceeds available
memory on your system.
The product of transport_lbtrm_←-
smart_src_transmission_window←-
_buffer_count and smart_src_←-
max_message_length specifies
more memory than is available on
your system.
Decrease the size of transport←-
_lbtrm_smart_src_transmission←-
_window_buffer_count and/or the
smart_src_max_message_length.
CoreApi-9941-5575: Smart source
may not use the same transport as
a standard source
An lbm standard source may not
reside with a smart source on the
same transport.
Configure the standard source on
an LBT-RM transport that only con-
tains standard sources.
CoreApi-9941-5: optval must be
greater than 0
smart_src_max_message_length
did not contain a positive integer
smart_src_max_message_length
must be a positive integer
CoreApi-9941-6000: Can't allocate
config options of u bytes [s:d]
The system was not able to allocate
the amount of memory requested.
The physical memory on the ma-
chine may be over committed; try
moving some applications to an-
other machine.
CoreApi-9941-6001: Failed to call
dump [s:d]
The call to lbm_ssrc_topic_←-
dump() failed.
Check that ssrc and opts are valid
and that the value at size is greater
than 0.
CoreApi-9941-6003: Can't allocate
JNI source object of u bytes [s:d]
The system was not able to allocate
the amount of memory requested.
The physical memory on the ma-
chine may be over committed; try
moving some applications to an-
other machine.
CoreApi-9941-6004: Can't allocate
memory [s:d]
The system was not able to allocate
the amount of memory requested.
The physical memory on the ma-
chine may be over committed; try
moving some applications to an-
other machine.
CoreApi-9941-6005: Can't allocate
memory [s:d]
The system was not able to allocate
the amount of memory requested.
The physical memory on the ma-
chine may be over committed; try
moving some applications to an-
other machine.
210 UM Log Messages
CoreApi-9941-6006: Can't allocate
memory [s:d]
The system was not able to allocate
the amount of memory requested.
The physical memory on the ma-
chine may be over committed; try
moving some applications to an-
other machine.
CoreApi-9941-6007: Can't get ad-
dress of ByteBuffer [s:d] - may not
be a direct ByteBuffer
The ByteBuffer was not valid for
this SmartSource.
The ByteBuffer must be a buffer
retrieved via the buffGet() method
from this SmartSource.
CoreApi-9941-6008: Can't get ad-
dress of ByteBuffer [s:d] - may not
be a direct ByteBuffer
The ByteBuffer was not valid for
this SmartSource.
The ByteBuffer must be a buffer
retrieved via the buffGet() method
from this SmartSource.
CoreApi-9941-6009: Can't allocate
memory [s:d]
The system was not able to allocate
the amount of memory requested.
The physical memory on the ma-
chine may be over committed; try
moving some applications to an-
other machine.
CoreApi-9941-6: optval too large smart_src_max_message_length
is larger than the maximum allowed
size
Decrease the size of smart_src_←-
max_message_length
CoreApi-9941-710: ssrc must be
valid
The Smart Source object is not
valid.
Provide a valid Smart Source ob-
ject.
CoreApi-9941-711: topic must be
valid
The topic associated with the
Smart Source is not valid.
Provided a valid topic.
CoreApi-9941-7: optlen incorrect
size
The size of the option was too large
or too small
smart_src_max_message_length
must be sizeof(int)
CoreApi-9941-8: optlen too small The size of the option buffer was
too small to contain the option
smart_src_max_message_length
optlen must be at least 80
CoreApi-9954-01: datagram accel-
eration init function must be valid
The datagram acceleration option
requires that all callbacks be pop-
ulated with valid function pointers.
The user needs to pass the correct
size to the option setter
CoreApi-9954-02: datagram accel-
eration open function must be valid
The datagram acceleration option
requires that all callbacks be pop-
ulated with valid function pointers.
The user needs to pass the correct
size to the option setter
CoreApi-9954-03: datagram accel-
eration close function must be valid
The datagram acceleration option
requires that all callbacks be pop-
ulated with valid function pointers.
The user needs to pass the correct
size to the option setter
CoreApi-9954-04: datagram accel-
eration bind function must be valid
The datagram acceleration option
requires that all callbacks be pop-
ulated with valid function pointers.
The user needs to pass the correct
size to the option setter
CoreApi-9954-05: datagram accel-
eration unbind function must be
valid
The datagram acceleration option
requires that all callbacks be pop-
ulated with valid function pointers.
The user needs to pass the correct
size to the option setter
CoreApi-9954-06: datagram accel-
eration multicast join function must
be valid
The datagram acceleration option
requires that all callbacks be pop-
ulated with valid function pointers.
The user needs to pass the correct
size to the option setter
CoreApi-9954-07: datagram ac-
celeration multicast leave function
must be valid
The datagram acceleration option
requires that all callbacks be pop-
ulated with valid function pointers.
The user needs to pass the correct
size to the option setter
CoreApi-9954-08: datagram accel-
eration recvfrom function must be
valid
The datagram acceleration option
requires that all callbacks be pop-
ulated with valid function pointers.
The user needs to pass the correct
size to the option setter
CoreApi-9954-09: datagram accel-
eration send connect function must
be valid
The datagram acceleration option
requires that all callbacks be pop-
ulated with valid function pointers.
The user needs to pass the correct
size to the option setter
CoreApi-9954-10: datagram accel-
eration send disconnect function
must be valid
The datagram acceleration option
requires that all callbacks be pop-
ulated with valid function pointers.
The user needs to pass the correct
size to the option setter
9.2 UM Core API Messages 211
CoreApi-9954-11: datagram accel-
eration send function must be valid
The datagram acceleration option
requires that all callbacks be pop-
ulated with valid function pointers.
The user needs to pass the correct
size to the option setter
CoreApi-9954-12: datagram accel-
eration sento function must be valid
The datagram acceleration option
requires that all callbacks be pop-
ulated with valid function pointers.
The user needs to pass the correct
size to the option setter
CoreApi-9954-13: datagram accel-
eration get address function must
be valid
The datagram acceleration option
requires that all callbacks be pop-
ulated with valid function pointers.
The user needs to pass the correct
size to the option setter
CoreApi-9954-14: datagram accel-
eration optlen incorrect size
The datagram acceleration option
length is expected to be the size
of lbm_datagram_acceleration_←-
func_t
The user needs to pass the correct
size to the option setter
CoreApi-9954-15: str_setopt not
supported for the datagram accel-
eration option
The datagram acceleration option
does not support string set/get op-
tion functions.
The user needs to use the structure
set/get option functions.
CoreApi-9954-16: datagram accel-
eration optlen incorrect size
The datagram acceleration option
length is expected to be the size
of lbm_datagram_acceleration_←-
func_t
The user needs to pass the correct
size to the option setter
CoreApi-9954-17: str_getopt not
supported for the datagram accel-
eration option
The datagram acceleration option
does not support string set/get op-
tion functions.
The user needs to use the structure
set/get option functions.
CoreApi-9954-60: Datagram Ac-
celeration not supported
The datagram acceleration option
requires an LBM build that sup-
ports it.
Contact support to get the proper
LBM build.
CoreApi-9954-61: Datagram Ac-
celeration not supported
The datagram acceleration option
requires an LBM build that sup-
ports it.
Contact support to get the proper
LBM build.
CoreApi-9954-62: Datagram Ac-
celeration not supported
The datagram acceleration option
requires an LBM build that sup-
ports it.
Contact support to get the proper
LBM build.
CoreApi-9954-63: Datagram Ac-
celeration not supported
The datagram acceleration option
requires an LBM build that sup-
ports it.
Contact support to get the proper
LBM build.
CoreApi-9972-1: unsubscribe may
only be performed on a subscribed
channel.
The call to discontinue an existing
channel subscription was invoked
on an unsubscribed channel.
Ensure the channel has been sub-
scribed before calling unsubscribe.
CoreApi-9972-2: unsubscribe may
only be performed on a subscribed
channel.
The call to discontinue an existing
channel subscription was invoked
on an unsubscribed channel.
Ensure the channel has been sub-
scribed before calling unsubscribe.
CoreApi-9972-3: unsubscribe may
only be performed on a subscribed
channel.
The call to discontinue an existing
channel subscription was invoked
on an unsubscribed channel.
Ensure the channel has been sub-
scribed before calling unsubscribe.
CoreApi-9972-4: unsubscribe may
only be performed on a subscribed
channel.
The call to discontinue an existing
channel subscription was invoked
on an unsubscribed channel.
Ensure the channel has been sub-
scribed before calling unsubscribe.
CoreApi-9972-5: unsubscribe may
only be performed on a subscribed
channel.
The call to discontinue an existing
channel subscription was invoked
on an unsubscribed channel.
Ensure the channel has been sub-
scribed before calling unsubscribe.
212 UM Log Messages
9.3 UM SRS Log Messages
SRS-10385-98: Registration
protocolVersion[" + reg.protocol←-
Version + "] received for client["
+ reg.client_addr + ":" + reg.←-
client_port + "] sessionID[" +
reg.session_id + "]
A client registration request was re-
ceived.
No resolution needed; Supplied for
informational purposes only.
SRS-10385-99: TCP Disconnect
received for client[" + registration.←-
client_addr + ":" + registration.←-
client_port + "] sessionID[" +
registration.session_id + "]
TCP Disconnect was received from
a client.
No resolution needed; Supplied for
informational purposes only.
SRS-10386-1000: Unable to es-
tablish connection due to unknown
protocolVersion[" + registration.←-
protocolVersion + "]
A client attempted to register with
an unsupported SRS protocol ver-
sion.
Reconcile versions and try again.
SRS-10386-1001: Unable to es-
tablish connection for sessionID["
+ registration.session_id + "] due
to unsupported protocolVersion["
+ registration.protocolVersion + "].
Only supported protocolVersion["
+ SRSMessage.LBM_SRS_PRO←-
TOCOL_VERSION + "]
A client with an unsupported ver-
sion attempted to establish a con-
nection with the SRS.
Reconcile versions and try again.
SRS-10386-1002: Received reg-
istration request for clientID[" +
clientId + "] with invalid message
id[" + srsMessage.id + "]
A client attempted to register with
an invalid request/response mes-
sage ID.
Reconcile SRS protocol versions
and try again.
SRS-10386-1003: Received an in-
valid stream request for clientID[" +
clientId + "]
A client attempted to register with
an invalid stream request message
ID.
Reconcile SRS protocol versions
and try again.
SRS-10386-1004: SRSSubscriber
will not update monitor info be-
cause SRSRegistration is null
The registration associated with
an SRS subscriber could not be
found. Consequently, associated
monitored information can not be
provided.
No resolution required. If this hap-
pens frequently, contact Informat-
ica support.
SRS-10386-1005: Received in-
valid SRS message for clientID[" +
clientId + "] with message id:
The SRS received an invalid SRS
message.
Contact Informatica support.
SRS-10386-1014: Received
SourceDeleteRecord for clientID["
+ clientId + "] with invalid OTID[" +
otidString + "]
The SRS received an invalid SDR. Contact Informatica support.
SRS-10386-10: Debugging en-
abled; file path: [" + debugState.←-
getDebugFilePath() + "] mask: ["
+ String.format("0x%08X", debug←-
State.getDebugMask()) + "]
The debugger is enabled. This is for informational purposes
only and can be ignored.
SRS-10386-1300: Failed to initial-
ize SRS application:
The SRS application failed to initial-
ize.
Contact Informatica support.
SRS-10386-1301: Failed to load
properties file " + APPLICATION←-
_PROPERTIES_FILE_NAME + ".
Reason:
The SRS application properties file
could not be found.
Contact Informatica support.
9.3 UM SRS Log Messages 213
SRS-10386-1302: Failed to pro-
cess SRS default configuration file.
Reason:
The SRS application default config-
uration XML file could not be pro-
cessed.
Contact Informatica support.
SRS-10386-1303: Failed to pro-
cess SRS user configuration X←-
ML file " + configFilename.get←-
AbsolutePath() + ". Reason:
The SRS application user config-
uration XML file could not be pro-
cessed.
The file may be missing, have inap-
propriate access privileges, or an
error in the config file itself.
SRS-10386-1304: Failed to config-
ure logback:
An internal error was encountered.
The server was unable to configure
the logger.
Contact Informatica support.
SRS-10386-1305: Unable to write
pid file:
The SRS was unable to write the
Processes ID file.
Check the Process ID path and di-
rectory access privileges.
SRS-10386-1306: The configura-
tion file must be specified with -v
option
The configuration file must be
specified with -v option.
Specify the configuration file and
try again.
SRS-10386-1307: Could not cre-
ate LBM context [" + ex.get←-
Message() + "]
The SRS was unable to create
the LBM context used for monitor-
ing. Daemon monitoring will be dis-
abled.
Contact Informatica support.
SRS-10386-1310: Configuration
warning: environment variable L←-
BM_DEBUG_MASK must be a
valid number between 0 and 0x←-
FFFFFFFF; debugging disabled
An internal error was encountered.
The server was unable to set the
LBM debug mask.
Contact Informatica support.
SRS-10386-1311: Error setting L←-
BM license:
An internal error was encountered.
The server was unable to set the
LBM license.
Contact Informatica support.
SRS-10386-1312: Exception in-
stantiating LBM object:
An internal error was encountered.
The server failed to instantiate LBM
due to run time exception.
Contact Informatica support.
SRS-10386-1320: The running
server attempted to restart
An internal ambiguity was encoun-
tered. The running server at-
tempted to restart.
Contact Informatica support.
SRS-10386-1321: Attempt to start
TCP Server failed; Server IP
address[" + host + "] port[" + port
+ "] failed:
The SRS TCP server failed to start
due to an exception identified in the
log message.
Contact Informatica support.
SRS-10386-1322: The server
failed to start
An internal error was encountered.
The server failed to start.
Contact Informatica support.
SRS-10386-1400: Failed to instan-
tiate LBMSource. Reason:
An internal error was encountered. Contact Informatica support.
SRS-10386-1401: Failed to add
immediate message receiver to " +
"LBMContext. Reason:
An internal error was encountered. Contact Informatica support.
SRS-10386-1402: MonitorInfo:
getUMClientMonitorInfoMessage:
Failed to cast value to Monitor←-
InfoConfigOption " + "for config
option " + configOptionName +
" in category " + monitorInfo←-
Category.getName() + ". Reason:
An internal error was encountered. Contact Informatica support.
SRS-10386-1403: Daemon moni-
tor sending monitor info messages
on topic:
Successfully instantiated an LBM
source to send monitor info mes-
sages.
No resolution needed; Supplied for
informational purposes only.
214 UM Log Messages
SRS-10386-1404: Debug monitor
listening for monitor info requests
on IP address: " + config.get←-
DebugMonitorHost() + " port:
The SRS debug monitor is open for
monitor info requests.
No resolution needed; Supplied for
informational purposes only.
SRS-10386-1405: Daemon moni-
tor listening for command requests
on IP address: " + requestTcp←-
Interface + " port:
The SRS command messages
channel is open for remote snap-
shot or config changes requets (or
both).
No resolution needed; Supplied for
informational purposes only.
SRS-10386-7: Connection to client
lost:
A connection to a registered LBM
client was lost perhaps due to net-
work interruption or client failure.
Check that the network is stable.
Contact Informatica support if this
message occurs frequently.
SRS-10563-10: Received a
SourceDeleteRecord without
having first received a Source←-
InfoRecord
An unexpected internal state was
encountered, but was handled.
No resolution required. If this hap-
pens frequently, contact Informat-
ica support.
SRS-10563-11: Received a
SourceDeleteRecord without
having first received a Source←-
InfoRecord
An unexpected internal state was
encountered, but was handled.
No resolution required. If this hap-
pens frequently, contact Informat-
ica support.
SRS-10563-12: Received dupli-
cate SourceInformationRecord for
topic[" + siRec.getDisplayTopic() +
"] source[" + siRec.getDisplay←-
Source() + "] OTID[" + siRec.get←-
DisplayOTID() + "]
Anrare internal state was encoun-
tered, but was handled. This state
typically results from DROs briefly
having more than one proxy source
for a given originating source, usu-
ally due to a re-routing operation.
This state normally resolves itself
after a short time.
No resolution required. If this hap-
pens frequently, contact Informat-
ica support.
SRS-10563-13: topic hasher re-
ceived unexpected object:
An unexpected internal state was
encountered, but was handled.
No resolution required. If this hap-
pens frequently, contact Informat-
ica support.
SRS-10563-14: Got an unex-
pected message: {}
An unexpected internal state was
encountered, but was handled.
No resolution required. If this hap-
pens frequently, contact Informat-
ica support.
SRS-10563-15: attempting to set
the ping interval for {} above the
maximum of {}. Setting to the max-
imum
An attempt was made to configure
ping-interval, which should typically
not be modified by users except un-
der direction and supervision of In-
formatica Support.
Remove the ping-interval configu-
ration, or contact Informatica sup-
port.
SRS-10563-16: attempting to set
the ping interval for {} below the
minimum of {}. Setting to the mini-
mum
An attempt was made to configure
ping-interval, which should typically
not be modified by users except un-
der direction and supervision of In-
formatica Support.
Remove the ping-interval configu-
ration, or contact Informatica sup-
port.
SRS-10563-17: attempted to mon-
itor actor with duplicate name: {}
An internal error was encountered. Contact Informatica support.
SRS-10563-18: MonitoredActor←-
TrackerActor: handleGetMonitor←-
Info: failed to process monitor info.
" + "Reason:
An unexpected internal state was
encountered, but was handled.
No resolution required. If this hap-
pens frequently, contact Informat-
ica support.
9.3 UM SRS Log Messages 215
SRS-10563-19: Received unex-
pected immediate LBM message←-
: " + lbmMessage.type() + " from
client:
The SRS was sent a unicast im-
mediate message that it does not
recognize. This might happen be-
cause a client is using a newer ver-
sion of UM than this SRS. There
are also some unlikely scenarios
related to a non-SRS process ex-
iting and the SRS starting and us-
ing the same TCP port; a different
UM program may be sending mes-
sages intended for the old exited
process.
Ensure the SRS is from the same
or newer version of UM as its
clients. Ensure that that the SRS
is given a unique port.
SRS-10563-20: Failed to send
command message response: " +
responseMessage + ". Reason:
An unexpected internal state was
encountered, but was handled.
No resolution required. If this hap-
pens frequently, contact Informat-
ica support.
SRS-10563-21: Control message
error: " + "failed to deserialize
command message from JSON.
Reason:
An internal error was encountered. Contact Informatica support.
SRS-10563-2: Unknown LBM log
level: " + logLevel + " for log
message:
An internal error (unknown LBM log
level) was encountered.
Contact Informatica support.
SRS-10563-31: Failed to serialize
a MonitorInfoMessage from cate-
gory " + monitorInfoMessage.get←-
MonitorInfoCategory().getName()
+ ". Reason:
An internal error was encountered. Contact Informatica support.
SRS-10563-32: Failed to send a
MonitorInfoMessage. Reason:
An internal error was encountered. Contact Informatica support.
SRS-10563-3: SRSClient←-
ManagerImpl: handleClientActor←-
Terminated: Received a Client←-
ActorTerminated message with null
client actor SRS registration
An internal error was encountered. Contact Informatica support.
SRS-10563-40: Failed to close L←-
BMSource. Reason:
An internal error was encountered. Contact Informatica support.
SRS-10563-41: MonitoredActor←-
Info: updateFrom: Failed to update
monitor info. Reason:
An internal error was encountered. Contact Informatica support.
SRS-10563-42: MonitorInfo←-
Message: getInPrintFormat: failed
to sort stats. Reason:
An internal error was encountered. Contact Informatica support.
SRS-10563-43: MonitorInfo←-
Message: getInPrintFormat:
monitorInfoCategoryName " +
monitorInfoCategory.getName() +
": SRSRegistrationInfo is null
An internal error was encountered. Contact Informatica support.
SRS-10563-44: MonitorInfo←-
Message: getInPrintFormat:
monitorInfoCategoryName " +
monitorInfoCategory.getName()
+ "; connectionEventType: " +
connectionEventType + " invalid
event state
An internal error was encountered. Contact Informatica support.
216 UM Log Messages
SRS-10563-45: MonitorInfo←-
Message: getInPrintFormat:
monitorInfoCategoryName " +
monitorInfoCategory.getName()
+ "; connectionEventType: " +
connectionEventType + " invalid
event state
An internal error was encountered. Contact Informatica support.
SRS-10563-46: MonitorInfo←-
Message: getInPrintFormat:
monitorInfoCategoryName " +
monitorInfoCategory.getName() +
": " + connectionEventType.get←-
Name() + " is not expected
An internal error was encountered. Contact Informatica support.
SRS-10563-47: MonitorInfo←-
Message: getInPrintFormat:
monitorInfoCategoryName " +
monitorInfoCategory.getName() +
": SRSRegistrationInfo is null
An internal error was encountered. Contact Informatica support.
SRS-10563-48: GetActorInfo:
setInfo: Failed to cast value to
MonitorInfoRecord for stat in " +
monitorInfoCategory.getName() + "
category
An internal error was encountered. Contact Informatica support.
SRS-10563-49: MonitorInfo: get←-
SRSMonitorInfoMessage: Failed to
cast value to MonitorInfoRecord" +
" for stat " + statName + " in cate-
gory " + monitorInfoCategory.get←-
Name() + ". Reason:
An internal error was encountered. Contact Informatica support.
SRS-10563-4: RSocket generated
an exception:
An internal error was encountered. Contact Informatica support.
SRS-10563-50: MonitorInfo: get←-
UMClientMonitorInfoMessage:
Failed to set value for stat " +
statName + " in category " +
monitorInfoCategory.getName() +
". Reason: its SRSRegistrationInfo
is null
An internal error was encountered. Contact Informatica support.
SRS-10563-51: MonitorInfo: get←-
UMClientMonitorInfoMessage:
Failed to cast value to Monitor←-
InfoRecord " + "for stat " +
statName + " in category " +
monitorInfoCategory.getName() +
". Reason:
An internal error was encountered. Contact Informatica support.
SRS-10563-52: MonitorInfo:
getConnectionEventsMonitor←-
InfoMessage: Failed to process "
+ " event " + connectionEvent←-
Type.getName() + " in category " +
monitorInfoCategory.getName() +
". Reason: its SRSRegistrationInfo
is null
An internal error was encountered. Contact Informatica support.
9.4 UM Dynamic Routing Log Messages 217
SRS-10563-53: MonitorInfo:
getConnectionEventsMonitorInfo←-
Message: Failed to cast value "
+ "to Queue<ConnectionEvent←-
Info>for events " + eventsName
+ " in category " + monitorInfo←-
Category.getName() + ". Reason:
An internal error was encountered. Contact Informatica support.
SRS-10563-5: Received a {}
whose topic doesn't match the ex-
isting topic for this OTID. Found [{}].
Expected [{}]
An internal error was encountered. Contact Informatica support.
SRS-10563-7: Received a Discon-
nect without having first received
a SourceInfoRecord for session←-
ID[" + dRec.getSessionId() + "]
topic[" + dRec.getDisplayTopic() +
"] source[" + dRec.getDisplay←-
Source() + "] OTID[" + dRec.get←-
DisplayOTID() + "]
An unexpected internal state was
encountered, but was handled.
No resolution required. If this hap-
pens frequently, contact Informat-
ica support.
SRS-10563-8: Received a Discon-
nect without having first received
a SourceInfoRecord for session←-
ID[" + dRec.getSessionId() + "]
topic[" + dRec.getDisplayTopic() +
"] source[" + dRec.getDisplay←-
Source() + "] OTID[" + dRec.get←-
DisplayOTID() + "]
An unexpected internal state was
encountered, but was handled.
No resolution required. If this hap-
pens frequently, contact Informat-
ica support.
SRS-10612-1: Failed to resched-
ule timer " + rescheduleSend←-
MonitorInfoTimer.keyName + ".
Reason:
Failed to reschedule a sending
monitor info timer.
Contact Informatica support.
SRS-10612-2: Failed to start timer
" + keyName + ". Reason:
Failed to start a sending monitor
info timer.
Contact Informatica support.
SRS-10612-3: Failed to cancel
timer " + keyName + ". Reason←-
:
Failed to cancel a sending monitor
info timer.
Contact Informatica support.
SRS-10612-4: SRS monitor info
update was to be sent, but the LBM
source is null
Cannot send SRS monitor info with
null LBM source. The source was
likely instantiated successfully, but
then an unrelated error occurred
which forced the closing of the
source.
Contact Informatica support.
9.4 UM Dynamic Routing Log Messages
Gwd-10163-01: LBMR Topic Res-
olution TNWG Interest packet mal-
formed (d:d). Dropping remainder.
Origin: s:d
LBMR Data received contain in-
valid data.
Check the source (IP:Port) for pos-
sible version mismatch or service
attack.
218 UM Log Messages
Gwd-10163-02: LBMR Topic Res-
olution TNWG Interest packet mal-
formed (d:d). Dropping remainder.
Origin: s:d
LBMR Data received contain in-
valid data.
Check the source (IP:Port) for pos-
sible version mismatch or service
attack.
Gwd-10163-03: LBMR Topic Res-
olution TNWG Interest packet mal-
formed (d:d). Dropping remainder.
Origin: s:d
LBMR Data received contain in-
valid data.
Check the source (IP:Port) for pos-
sible version mismatch or service
attack.
Gwd-10163-04: LBMR Topic Res-
olution TNWG Interest packet mal-
formed (d:d). Dropping remainder.
Origin: s:d
LBMR Data received contain in-
valid data.
Check the source (IP:Port) for pos-
sible version mismatch or service
attack.
Gwd-10163-05: LBMR Topic Res-
olution TNWG Interest packet mal-
formed. Dropping remainder.
Origin: s:d
LBMR Data received contain in-
valid data.
Check the source (IP:Port) for pos-
sible version mismatch or service
attack.
Gwd-10163-06: LBMR Topic Res-
olution TNWG Interest packet mal-
formed (d:d). Dropping remainder.
Origin: s:d
LBMR Data received contain in-
valid data.
Check the source (IP:Port) for pos-
sible version mismatch or service
attack.
Gwd-10163-07: LBMR Topic Res-
olution TNWG Interest packet mal-
formed. Dropping remainder.
Origin: s:d
LBMR Data received contain in-
valid data.
Check the source (IP:Port) for pos-
sible version mismatch or service
attack.
Gwd-10163-08: LBMR Topic Res-
olution TNWG Interest packet mal-
formed (d). Dropping remainder.
Origin: s:d
LBMR Data received contain in-
valid data.
Check the source (IP:Port) for pos-
sible version mismatch or service
attack.
Gwd-10163-09: LBMR Topic Res-
olution TNWG Interest packet mal-
formed (d). Dropping remainder.
Origin: s:d
LBMR Data received contain in-
valid data.
Check the source (IP:Port) for pos-
sible version mismatch or service
attack.
Gwd-10185-100: unknown group
name: "%s"
The group name chosen is not a
valid group.
Choose a valid group.
Gwd-10185-101: monitor section
lbm-config must have a value
Expecting a string that contains the
path to the config file.
Please specify a string that con-
tains the path to the config file.
Gwd-10185-102: monitor section
xml-config must have a value
Expecting a string that contains the
path to the config file.
Please specify a string that con-
tains the path to the config file.
Gwd-10185-103: undefined pub-
lishing interval (s) for group: "%s"
The publishing interval needs to be
a valid number, greater than (or
equal to) 0.
Specify a valid number.
Gwd-10185-104: bad portal num-
ber returned from tnwg_getportal←-
_fromstring()
Unable to find portal based on por-
tal name specified by user
Verify that the portal name is spec-
ified in the DRO XML file
Gwd-10185-10: unable to create
gateway cfg stat group: s
Failure when creating daemon
monitor gateway config stats group
Gwd-10185-11: unable to create
mallinfo stat group: s
Failure created while creating dae-
mon monitor malloc info stat group
Gwd-10185-12: unable to create
portals stat group:
Failure while creating daemon
monitor portal stats stat group
Gwd-10185-13: unable to create
portal config stat group: s
Failure while creating daemon
monitor portal config stats group
Gwd-10185-14: error reading mal-
loc info record
Error attempting to read daemon
stats malloc info record
9.4 UM Dynamic Routing Log Messages 219
Gwd-10185-15: unable to sched-
ule timer for mallinfo stat group
callback: s
Failure creating mallinfo stat group
callback timer
Gwd-10185-16: error reading mal-
loc info record
Error attempting to read daemon
stats malloc info record
Gwd-10185-17: unable to sched-
ule timer for mallinfo stat group call
back, s
failure scheduling timer for mallinfo
stat group callback timer
Gwd-10185-18: error reading mal-
loc info record
Error attempting to read daemon
stats malloc info record
Gwd-10185-19: unable to schedule
timer for gateway config stat group
call back, s
Error setting up gateway config stat
group callback timer
Gwd-10185-1: unable to create
context attributes: s
Failure while creating context at-
tributes
Gwd-10185-20: error trying to pub-
lish gateway config record
Failure publishing gateway config
record
Gwd-10185-21: unable to schedule
timer for gateway config stat group
call back, s
Failure setting up gateway config
stat group callback timer
Gwd-10185-22: error trying to read
portal stats record for portal d
Failure reading portal stats record
Gwd-10185-23: error trying to ini-
tialize portal stats record
Failure initializing portal stats
record
Gwd-10185-24: unable to sched-
ule timer for portalstats stat group
callback: s
Error scheduling callback timer for
portal stats stat group
Gwd-10185-25: bad portal type in
tnwg_portstat_msg_init, d
Bad portal type in portal structure
Gwd-10185-26: error trying to find
portal structure from portal number
d
Unable to find portal based on in-
dex stored in daemon stats monitor
global array
Gwd-10185-27: error trying to read
endpoint portal record
Error reading stat record for end-
point
Gwd-10185-28: error trying to read
peer portal record
Error reading stat record for peer
Gwd-10185-29: unknown portal
type, d
Bad portal type specified in portal
global structure
Gwd-10185-2: lbmaux_context←-
_attr_setopt_from_file() failed, s
Failure while setting up extra config
opts for DRO daemon monitor
Check attributes in "lbm-config"
config file specified in the DRO's
xml file
Gwd-10185-30: error trying to re-
trieve endpoint portal stats data
Error trying to copy portal stats
Gwd-10185-31: error trying to re-
trieve peer portal stats record
Error trying to retrieve endpoint
portal stats data
Gwd-10185-32: unable to sched-
ule timer for portalstats stat group
callback: s
Error setting up timer for daemon
stats portal stats stat group call-
back
Gwd-10185-33: error trying to read
portal stats record
Error reading portal stats stat group
record
Gwd-10185-34: error trying to
retrieve route manager topology
record
Failure reading route manager
topology stat group record
Gwd-10185-35: unable to schedule
timer for rm stat group callback: s
Failure setting up route manager
stat group callback timer
220 UM Log Messages
Gwd-10185-36: error trying to
retrieve route manager topology
record
Failure reading route manager stat
group record
Gwd-10185-37: tnwg_rm_stat_←-
grp_read() returned a null pointer
Received null pointer while assem-
bling route manager stat group
record
Gwd-10185-38: unable to schedule
timer for rm stat group callback: s
Error scheduling callback timer for
route manager stat group
Gwd-10185-39: tnwg_rm_info() re-
turned an error
Failure accessing route manager
info for route manager stat group
Gwd-10185-3: lbm_context_←-
attr_setopt() failed, s
Failure setting up attributes for dae-
mon monitor remote control han-
dler
Gwd-10185-40: tnwg_rm_stat←-
_grp_collect_portal_info() returned
an error
Failure collecting portal info for
route manager stat group
Gwd-10185-41: error from tnwg_←-
rm_others_collect_info()
Failure collecting info for other
gateways for route manager stat
group
Gwd-10185-42: error trying to build
the rm topology record
Failure building route manager stat
group record
Gwd-10185-43: passed in null
pointer to tnwg_rm_stat_grp_←-
read()
Attempt to build rm stat group
record resulted in null pointer re-
turned
Gwd-10185-44: error returned
from tnwg_rm_stat_grp_buffer_←-
cleanup()
Failure encountered returning mal-
loc'd buffers for route manager stat
group
Gwd-10185-45: bad record type
passed to tnwg_rm_stat_grp_←-
insert_item_into_record() d
Bad route manager stat group sub
group type
Gwd-10185-46: bad magic 0x04x Route manager stat group record
header corruption
Gwd-10185-47: error returned
from lbm_src_send(), s
Failure attempting to sending send
route manager stat group record
through lbm_src_send()
Gwd-10185-48: error returned
from tnwg_rm_stat_grp_read()
Failure reading route manager stat
group record
Gwd-10185-49: bad recptr re-
turned from tnwg_rm_stat_grp_←-
read()
Read of route manager stat group
record resulted in null pointer re-
turned
Gwd-10185-4: unable to create
context attributes: s
Failure creating lbm context for
daemon stats monitor
Gwd-10185-50: error returned
from tnwg_dstat_publish()
Failure attempting to publish route
manager stat group record
Gwd-10185-51: unable to sched-
ule timer for portal cfg stat group
callback: s
Failure scheduling callback timer
for route manager stat group
Gwd-10185-52: unable to sched-
ule timer for portal cfg stat group
callback: s
Failure scheduling callback timer
for portal config stat group
Gwd-10185-53: error from tnwg_←-
portal_find() for portal number d
Null pointer returned when obtain-
ing pointer to portal structure
Gwd-10185-54: error returned
from tnwg_portalcfg_stat_grp_←-
read()
Failure reading record for portal
config stat group
9.4 UM Dynamic Routing Log Messages 221
Gwd-10185-55: error returned
from tnwg_dstat_publish()
Failure attempting to publish portal
config stat group record
Gwd-10185-56: bad pointer to por-
tal passed to tnwg_portalcfg_stat←-
_grp_read()
Null pointer passed to tnwg_←-
portalcfg_stat_grp_read()
Gwd-10185-57: lbm_context_←-
attr_dump() failed, s
Failure attempting to access por-
tal config source context attributes
from config tables
Gwd-10185-58: lbm_context_←-
attr_dump() failed, s
Failure attempting to access por-
tal config receiver context attributes
from config tables
Gwd-10185-59: lbm_event_←-
queue_attr_dump() failed, s
Failure attempting to access portal
config event queue attributes from
config tables
Gwd-10185-5: unable to create src
topic attributes: s
Error creating source attributes for
daemon stats monitor
Gwd-10185-60: bad config type in
tnwg_portalcfg_stat_grp_read() d
Invalid config type specified for
Peer portal
Gwd-10185-61: lbm_context_←-
attr_dump() failed, s
Failure attempting to access portal
config source context for endpoint
portal
Gwd-10185-62: lbm_context_←-
attr_dump() failed, s
Failure attempting to access end-
point portal config receiver context
attributes from config table
Gwd-10185-63: lbm_src_topic_←-
attr_dump() failed, s
Failure attempting to access end-
point portal config source attributes
from config table
Gwd-10185-64: lbm_rcv_topic_←-
attr_dump() failed, s
Failure attempting to access end-
point portal config receiver at-
tributes from config table
Gwd-10185-65: lbm_wildcard_←-
rcv_attr_dump() failed, s
Failure attempting to access end-
point portal wildcard receiver at-
tributes from config table
Gwd-10185-66: lbm_event_←-
queue_attr_dump() failed, s
Failure attempting to access end-
point portal event queue attributes
from config table
Gwd-10185-67: bad portal type d Invalid portal type
Gwd-10185-68: Failure from lbm←-
_src_send(), s
Failure trying to publish portal con-
fig stats group record
Gwd-10185-69: Invalid record type
d
Attempt to publish invalid stats
group record type
Gwd-10185-6: unable to alloc src
topic: s
Error allocating src topic for dae-
mon stats monitor
Gwd-10185-70: error from tnwg_←-
mallinfo_stat_grp_snapshot()
Failure reading malloc info stat
group record
Gwd-10185-71: error from tnwg_←-
rm_stat_grp_snapshot()
Failure reading route manager stat
group record
Gwd-10185-72: bad portal num-
ber returned from tnwg_getportal←-
_fromstring()
Unable to find portal based on por-
tal name specified by user
Verify that the portal name is spec-
ified in the DRO XML file
Gwd-10185-73: error returned
from tnwg_portalstats_stat_grp_←-
snapshot()
Failure reading a portal stats stat
group record
222 UM Log Messages
Gwd-10185-74: error returned
from tnwg_gatewaycfg_stat_grp←-
_snapshot()
Failure reading a gateway config
stats group record
Gwd-10185-76: error returned
from tnwg_portalcfg_stat_grp-
snapshot()
Unable to read portal config stat
group record
Gwd-10185-77: bad stat grp d Attempt to obtain snapshot of
record for invalid stat group
Gwd-10185-78: error returned
from tnwg_dstat_setinterval()
Failure changing the publishing in-
terval for route manager stat group
Gwd-10185-79: bad portal num-
ber returned from tnwg_getportal←-
_fromstring()
Unable to find portal based on por-
tal name specified by user
Verify that the portal name is spec-
ified in the DRO XML file
Gwd-10185-7: unable to create
src: s
Error creating source for daemon
stats monitor
Gwd-10185-80: error returned
from tnwg_dstat_setinterval()
Failure changing the publishing in-
terval for portal stats stat group
Gwd-10185-81: error returned
from tnwg_dstat_setinterval()
Failure changing the publishing in-
terval for gateway config stat group
Gwd-10185-82: error returned
from tnwg_getportal_fromstring()
Unable to find portal based on por-
tal name specified by user
Verify that the portal name is spec-
ified in the DRO XML file
Gwd-10185-83: error returned
from tnwg_dstat_setinterval()
Failure changing the publishing in-
terval for portal config stat group
Gwd-10185-84: error returned
from tnwg_dstat_setinterval()
Failure changing the publishing in-
terval for mallinfo stat group
Gwd-10185-85: bad group type, d Invalid stat group type specified for
request to change publishing inter-
val
Gwd-10185-86: unable to schedule
timer
Failure to schedule callback timer
Gwd-10185-87: bad portal number
passed to tnwg_dstat_setinterval←-
_for_portals(), d
Bad portal number specified in re-
quest to change the publishing in-
terval
Gwd-10185-88: unable to schedule
timer for portal stats stat group s
Failure rescheduling callback timer
for a portal type (cfg or stat) stat
group
Gwd-10185-89: Unable to start
daemon stats monitor
unable to start daemon stats moni-
tor for gateway
Verify all daemon monitor related
attributes are correct in xml and
config files
Gwd-10185-8: unable to create per
portal info
Failure returned while creating per
portal info in daemon stats monitor
Gwd-10185-90: tnwg_dstat_←-
publish: s
UM was unable to publish dmon
message.
Contact Informatica Support.
Gwd-10185-91: tnwg_publish_←-
mallinfo: s
UM was unable to publish dmon
message.
Contact Informatica Support.
Gwd-10185-92: tnwg_publish_←-
gatewaycfg: s
UM was unable to publish dmon
message.
Contact Informatica Support.
Gwd-10185-93: invalid DRO dmon
message [s] from s [s]
UM dmon received an invalid/cor-
rupted immediate message.
Verify that messages sent on the
request port are valid.
Gwd-10185-94: DRO dmon failed
to send error response [s]
UM could not respond to a dmon
immediate message.
Contact Informatica Support.
Gwd-10185-95: DRO dmon failed
to send success response [s]
UM could not respond to a dmon
immediate message.
Contact Informatica Support.
9.4 UM Dynamic Routing Log Messages 223
Gwd-10185-96: DRO dmon re-
ceived control message exceeding
255 bytes
UM daemon monitor received an
invalid control message exceeding
255 bytes.
Verify that messages sent on the
control channel are <= 255 bytes.
Gwd-10185-97: DRO dmon failed
to send error response [s]
UM could not respond to a dmon
immediate message.
Contact Informatica Support.
Gwd-10185-98: DRO received un-
known lbm_msg_t type x [s][s]
UM daemon monitor received un-
known lbm_msg_t type.
Stop the source of unknown mes-
sages to the daemon monitor.
Gwd-10185-99: Bad config type =
d
Invalid config type specified
Gwd-10185-9: unable to create
route manager stat group
Failure returned while creating dae-
mon monitor route manager stats
group
Gwd-10434-1: Portal [s] removed
enqueued messages due to Proxy
Source delete
The named portal removed queued
messages upon deleting the Proxy
Source.
This is an informational message
only. The Proxy Source was no
longer needed and the queued
messages were removed.
Gwd-5688-4813: could not allocate
u bytes [s:d]
The system was not able to allocate
the amount of memory requested.
If the amount requested was par-
ticularly large, the problem may be
a misconfiguration; however if the
amount requested was relatively
small, the physical memory on the
machine may be over committed;
try moving some applications to an-
other machine.
Gwd-5975-1: error in PCRE pat-
tern offset d: s
UMS detected a malformed PCRE
expression while handling a wild-
card receiver pattern.
Contact Informatica support if this
message occurs frequently or if
topic resolution appears to be fail-
ing.
Gwd-5975-2: illegal regex: s UMS detected a malformed RE←-
GEX expression while handling a
wildcard receiver pattern.
Contact Informatica support if this
message occurs frequently or if
topic resolution appears to be fail-
ing.
Gwd-5975-3: peer portal [s] failed
to create control buffer (send EOS)
[d]: s
Failed to create a control buffer
needed to indicate EOS across the
Peer link.
Failure to create buffers usually
indicates a serious memory is-
sue. Configuration settings may be
causing excessive memory alloca-
tion.
Gwd-5975-4: tnwg_peer_←-
propagate_cb: portal [s] failed to
create buffer [d]: s
Failed to create a control buffer
needed to propagate route informa-
tion through the Peer link.
Failure to create buffers usually
indicates a serious memory is-
sue. Configuration settings may be
causing excessive memory alloca-
tion.
Gwd-5975-5: peer portal [s] failed
to schedule recalc timer [d]: s
An error occurred while attempting
to schedule an internal timer.
Contact Informatica Support
Gwd-5975-6: peer portal [s] failed
to create raw buffer (send frag-
ment) [d]: s
Failed to create a control buffer
needed to propagate MIM traffic
through the Peer link.
Failure to create buffers usually
indicates a serious memory is-
sue. Configuration settings may be
causing excessive memory alloca-
tion.
Gwd-5975-7: peer portal [s] failed
to schedule peer shutdown timer
[d]: s
An error occurred while attempting
to schedule an internal timer.
Contact Informatica Support
Gwd-5975-8: TMgr [s] sourcemap
size of zero is not allowed, using
default (d).
The sourcemap size config option
can not be zero. Setting it to the
default.
User should update their configura-
tion file.
224 UM Log Messages
Gwd-5975-9: TMgr [s] sourcemap
size must be a power of two, ad-
justing size from d to d
The sourcemap size config option
must be a power of two. Setting it
to the next highest power of two.
User should update their configura-
tion file.
Gwd-6033-353: endpoint portal [s]
received one or more UIM control
messages with no stream informa-
tion - these will be dropped
This gateway has received mes-
sages from a client using an earlier
version of the library that does not
include stream information.
If this is expected behavior, this
message can be ignored; other-
wise the client should have its li-
brary upgraded.
Gwd-6033-367: endpoint portal
[s] source context lbm_context_←-
process_events() failed [d]: s
The call to lbm_context_←-
process_events() for the source
context has returned an error. The
LBM error number and message
has been supplied in the output.
Use the LBM error number and
message as a cross reference to
determine cause and resolution.
Gwd-6033-368: endpoint portal
[s] receive context lbm_context←-
_process_events() failed [d]: s
The call to lbm_context_←-
process_events() for the receive
context has returned an error. The
LBM error number and message
has been supplied in the output.
Use the LBM error number and
message as a cross reference to
determine cause and resolution.
Gwd-6033-593: peer portal [s] re-
ceived one or more UIM control
messages with no stream informa-
tion - these will be dropped
This gateway has received mes-
sages from a client using an earlier
version of the library that does not
include stream information.
If this is expected behavior, this
message can be ignored; other-
wise the client should have its li-
brary upgraded.
Gwd-6033-618: peer portal [s] s A Peer connection error occurred.
The error message has been sup-
plied in the output.
Use the error message as a cross
reference to determine cause and
resolution.
Gwd-6259-50: Message received
with no routing information; drop-
ping. Topic (s) Source (s)
A message was received by a
Gateway that contains no rout-
ing information and therefore was
dropped.
This is likely due to a version mis-
match. The Topic and Source
string are given in the message.
Gwd-6259-51: Message received
with unusually high hop count (d).
Topic (s) Source (s)
A message was received by a
Gateway that contains a high hop
count (given in message).
The customer needs to evaluate
their network topology.
Gwd-6259-52: Control message
received with no routing informa-
tion; dropping. Origin: s:d
A control message was received by
a Gateway that contains no rout-
ing information and therefore was
dropped.
This is likely due to a version mis-
match. The origin is given in the
message.
Gwd-6259-53: Control message
received with unusually high hop
count (d). Origin: s:d
A message was received by a
Gateway that contains a high hop
count (given in message).
The customer needs to evaluate
their network topology.
Gwd-6259-54: endpoint portal [s]
failed to send unicast [d]: s to u←-
:s:d
A failure occured trying to send a
unicast message.
This failure is usually a result of
not being able to connect to the
destination or an unexpected dis-
connect which could indicate net-
work issues. The specific LBM er-
ror message is given.
Gwd-6259-55: Message received
with too many hops (255); dropping
. Topic (s) Source (s)
A message was received by a
Gateway that contains a high hop
count (given in message).
The customer needs to evaluate
their network topology.
Gwd-6259-56: Control message
received with too many hops (255);
dropping . Origin: s:d
A message was received by a
Gateway that contains a high hop
count (given in message).
The customer needs to evaluate
their network topology.
Gwd-6259-57: endpoint portal [s]
failed to create buffer (send topic
control packet) [d]: s
When forwarding Topic Control
Data, a buffer could not be allo-
cated.
This is an LBM buffer create error.
The LBM error number and mes-
sage is given. Please cross refer-
ence this information.
9.4 UM Dynamic Routing Log Messages 225
Gwd-6259-58: endpoint portal [s]
failed to send raw (send topic con-
trol packet) [d]: s
An error occurred while attempting
to send a message fragment.
This is an LBM send error. The L←-
BM error number and message is
given. Please cross reference this
information.
Gwd-6259-59: tnwg_peer_psm_←-
deliver_uim_packet_cb: portal [s]
failed to create buffer [d]: s
Failed to create a control buffer
needed to send UIM across the
Peer link.
Failure to create buffers usually
indicates a serious memory is-
sue. Configuration settings may be
causing excessive memory alloca-
tion.
Gwd-6259-60: tnwg_peer_psm_←-
deliver_cntl_packet_cb: portal [s]
failed to create buffer [d]: s
Failed to create a control buffer
needed to send UIM across the
Peer link.
Failure to create buffers usually
indicates a serious memory is-
sue. Configuration settings may be
causing excessive memory alloca-
tion.
Gwd-6361-100: failed to schedule
the source delete timer: s
An error occurred while attempting
to schedule an internal timer.
Contact Informatica Support.
Gwd-6361-101: Unable to en-
queue a source entry onto the
blocked queue: s
An error occurred while attempting
to enqueue data on to an internal
queue.
Contact Informatica Support.
Gwd-6361-102: Unable to en-
queue a source entry onto the
wakeup queue: s
An error occurred while attempting
to enqueue data on to an internal
queue.
Contact Informatica Support.
Gwd-6361-103: An error oc-
curred while processing a source
notification: s
An error occurred while attempting
to process a source create/delete
notification.
Contact Informatica Support.
Gwd-6361-104: An error occurred
while attempting to create a source
on topic [s]
An error occurred while creating a
proxy source. No data will be for-
warded for that source.
Look for a prior error in the gateway
log indicating what may have gone
wrong.
Gwd-6361-105: Unable to en-
queue a source entry onto the
delete queue: s
An error occurred while attempting
to enqueue data on to an internal
queue.
Contact Informatica Support.
Gwd-6361-106: psm p failed to cre-
ate sqn set [d]: s
An error occurred while attempting
to create a sqn set, used for dupli-
cate detection.
Contact Informatica Support.
Gwd-6361-10: endpoint portal [s]
remote domain topic interest check
failed [d]: s
An error occurred while checking
topic interest from remote domains.
Contact Informatica Support
Gwd-6361-111: an error occurred
while processing link state informa-
tion from another gateway: s
An error occurred while process-
ing an incoming route information
packet.
Contact Informatica Support.
Gwd-6361-112: unable to set pdm
field [node_name] for link state
propagation: [s]
An error occurred while setting P←-
DM field in an internal PDM mes-
sage.
Contact Informatica Support.
Gwd-6361-116: failed to create an
internal domain list: s
An error occurred while creating an
internal domain list.
Contact Informatica Support.
Gwd-6361-117: unable to read
pdm field [s]: [s]
An error occurred while reading a
PDM field in a PDM message.
Contact Informatica Support.
Gwd-6361-118: unable to read
pdm field vec [s]: [s]
An error occurred while reading a
PDM field vec in a PDM message.
Contact Informatica Support.
Gwd-6361-119: unable to set pdm
field [s] for link state forwarding: [s]
An error occurred while setting a
PDM field in a PDM message.
Contact Informatica Support.
Gwd-6361-11: endpoint portal [s]
failed to schedule remote domain
topic check timer [d]: s
An error occurred while attempting
to schedule an internal timer.
Contact Informatica Support
226 UM Log Messages
Gwd-6361-123: portal [s] could not
find path to domain u. Dropping
UIM packet.
UIM traffic destined for a particular
domain arrived at a portal that is
not setup to forward to the domain
in question.
Contact Informatica Support.
Gwd-6361-124: Received UIM
packet before initial route calcula-
tions completed. Dropping.
UIM traffic was sent to the gate-
way before it had completed it's first
round of route calculations.
This can happen briefly when a
gateway is restarted. If the mes-
sage persists, contact Informatica
Support.
Gwd-6361-12: endpoint portal [s]
remote domain PCRE pattern inter-
est check failed [d]: s
An error occurred while checking
pattern interest from remote do-
mains.
Contact Informatica Support
Gwd-6361-132: endpoint portal [s]
failed to schedule rcv_ctx recalc
timer [d]: s
An error occurred while attempting
to schedule an internal timer.
Contact Informatica Support
Gwd-6361-133: Received MIM
packet with no odomain header.
Dropping.
MIM traffic was sent to the gateway
without an ODOMAIN header.
This is likely caused by running an
older version of UM.
Gwd-6361-134: Received MIM
packet with no odomain header.
Dropping.
MIM traffic was sent to the gateway
without an ODOMAIN header.
This is likely caused by a gateway
version mismatch.
Gwd-6361-13: endpoint portal [s]
remote domain REGEX pattern in-
terest check failed [d]: s
An error occurred while checking
pattern interest from remote do-
mains.
Contact Informatica Support
Gwd-6361-14: endpoint portal [s]
failed to schedule remote domain
pattern check timer [d]: s
An error occurred while attempting
to schedule an internal timer.
Contact Informatica Support
Gwd-6361-15: endpoint portal [s]
failed to dup rcv attributes (rcv cre-
ate) [d]: s
An error occurred while attempting
to duplicate receiver attributes dur-
ing receiver creation.
Contact Informatica Support
Gwd-6361-16: endpoint portal [s]
failed to set rcv attribute [source←-
_notification_function] (rcv create)
[d]: s
An error occurred while attempting
to set receiver attributes during re-
ceiver creation.
Contact Informatica Support
Gwd-6361-17: endpoint portal [s]
failed to lookup topic (rcv create)
[d]: s
An error occurred while attempting
to lookup a topic during receiver
creation.
Contact Informatica Support
Gwd-6361-18: endpoint portal [s]
failed to create receiver (rcv create)
[d]: s
An error occurred while attempting
to create a receiver.
Contact Informatica Support
Gwd-6361-19: endpoint portal [s]
failed to alloc resolver topic mes-
sage [d]: s
UM has failed to allocate required
memory for the purposes of con-
structing an interest list message.
Acquire more memory
Gwd-6361-20: endpoint portal [s]
failed to delete receiver (rcv delete)
[d]: s
An error occurred while attempting
to delete a receiver.
Contact Informatica Support
Gwd-6361-21: endpoint portal [s]
failed to dup wrcv attributes (wrcv
create) [d]: s
An error occurred while attempt-
ing to duplicate wildcard receiver
attributes during wildcard receiver
creation.
Contact Informatica Support
Gwd-6361-22: endpoint portal
[s] failed to set wrcv attribute
[receiver_create_callback] (wrcv
create) [d]: s
An error occurred while attempting
to set wildcard receiver attributes
during receiver creation.
Contact Informatica Support
9.4 UM Dynamic Routing Log Messages 227
Gwd-6361-23: endpoint portal
[s] failed to set wrcv attribute
[receiver_delete_callback] (wrcv
create) [d]: s
An error occurred while attempting
to set wildcard receiver attributes
during receiver creation.
Contact Informatica Support
Gwd-6361-24: endpoint portal
[s] failed to set wrcv attribute
[pattern_type] (wrcv create) [d]: s
An error occurred while attempting
to set wildcard receiver attributes
during receiver creation.
Contact Informatica Support
Gwd-6361-25: endpoint portal [s]
failed to create wildcard receiver
(wrcv create) [d]: s
An error occurred while attempting
to create a wildcard receiver.
Contact Informatica Support
Gwd-6361-26: endpoint portal [s]
failed to delete wildcard receiver
(wrcv delete) [d]: s
An error occurred while attempting
to delete a wildcard receiver.
Contact Informatica Support
Gwd-6361-27: endpoint portal [s]
failed to properly handle wildcard
receiver receiver create [d]: s
An error occurred while attempting
to process a wildcard receiver re-
ceiver create.
Contact Informatica Support
Gwd-6361-28: endpoint portal [s]
failed to properly handle wildcard
receiver receiver delete [d]: s
An error occurred while attempting
to process a wildcard receiver re-
ceiver delete.
Contact Informatica Support
Gwd-6361-29: endpoint portal [s]
received TransportOpts with no O←-
TID for SourceName [s] topic [s],
source ignored (rcvdc create)
UM encountered a source with no
OTID. This is likely caused by a ver-
sion mismatch with an old versin of
UM.
Resolve the version mismatch.
Gwd-6361-30: endpoint portal
[s] failed to create prm o_entry
(rcvdc_create) [d]: [s]
An error occurred while attempting
to process a delivery controller cre-
ate.
Contact Informatica Support
Gwd-6361-31: endpoint portal [s]
unable to delete NULL src_clientd
(rcvdc_delete)
UM encountered an unexpected
NULL source clientd while attempt-
ing to handle a delivery controller
delete.
Contact Informatica Support
Gwd-6361-32: endpoint portal [s]
failed to properly handle a delivery
controller delete [d]: s
An error occurred while attempt-
ing to process a delivery controller
delete.
Contact Informatica Support
Gwd-6361-33: endpoint portal [s]
received advertisement for topic [s]
source [s] with no transport op-
tions - this source will never be for-
warded
UM encountered a source with no
transport opts. This is likely caused
by a version mismatch with an old
version of UM.
Resolve the version mismatch.
Gwd-6361-34: endpoint portal [s]
received advertisement for topic [s]
source [s] with no OTID - this
source will never be forwarded
UM encountered a source with no
OTID. This is likely caused by a ver-
sion mismatch with an old version
of UM.
Resolve the version mismatch.
Gwd-6361-35: endpoint portal [s]
failed to schedule src_ctx recalc
timer [d]: s
An error occurred while attempting
to schedule an internal timer.
Contact Informatica Support
Gwd-6361-36: endpoint portal [s]
failed to duplicate src attr (src cre-
ate) [d]: s
An error occurred while attempting
to duplicate source attributes dur-
ing source creation.
Contact Informatica Support
Gwd-6361-37: endpoint portal [s]
failed to allocate source topic (src
create) [d]: s
An error occurred while attempting
to allocate a topic during source
creation.
Contact Informatica Support
Gwd-6361-38: endpoint portal [s]
failed to create source (src create)
[d]: s
An error occurred while attempting
to create a source.
Contact Informatica Support
228 UM Log Messages
Gwd-6361-39: endpoint portal [s]
failed to flush source (src delete)
[d]: s
An error occurred while attempting
to flush a source prior to source
deletion.
Contact Informatica Support
Gwd-6361-40: endpoint portal [s]
failed to delete source (src delete)
[d]: s
An error occurred while attempting
to delete a source.
Contact Informatica Support
Gwd-6361-41: endpoint portal [s]
failed to create raw buffer (send
fragment) [d]: s
An error occurred while attempt-
ing to create a message buffer for
sending.
Contact Informatica Support
Gwd-6361-42: endpoint portal
[s] unable to send: datagram
size mismatch. transport_XXX_←-
datagram_max_size must be prop-
erly configured. This is a configura-
tion error.
Attempting to send a fragment that
is larger than this egress portal's
max size.
Resolve the datagram max size
mismatch
Gwd-6361-43: endpoint portal [s]
failed to send raw (send fragment)
[d]: s
An error occurred while attempting
to send a message fragment.
Contact Informatica Support
Gwd-6361-44: endpoint portal [s]
failed to create raw buffer (IM)
(send fragment) [d]: s
An error occurred while attempt-
ing to create a message buffer for
sending.
Contact Informatica Support
Gwd-6361-45: endpoint portal [s]
unable to multicast immediate←-
: datagram size mismatch.
transport_lbtrm_datagram_max_←-
size must be properly configured.
This is a configuration error.
Attempting to send a fragment that
is larger than this egress portal's
max size.
Resolve the datagram max size
mismatch
Gwd-6361-46: endpoint portal [s]
failed to multicast immediate raw
(send fragment) [d]: s
An error occurred while attempting
to send a message fragment.
Contact Informatica Support
Gwd-6361-47: endpoint portal [s]
failed to handle topic/pattern leave
entry [d]: [s]
An error occurred while attempting
to process local interest.
Contact Informatica Support
Gwd-6361-48: endpoint portal [s]
failed to handle pattern interest en-
try [d]: [s]
An error occurred while attempting
to process remote interest.
Contact Informatica Support
Gwd-6361-49: endpoint portal [s]
failed to enqueue topic interest en-
try [d]: [s]
An error occurred while attempting
to process remote interest.
Contact Informatica Support
Gwd-6361-50: endpoint portal [s]
failed to allocate resolver buffer
[d]: s
An error occurred while attempting
to allocate a topic resolution buffer.
Contact Informatica Support
Gwd-6361-51: endpoint portal [s]
failed to generate portal list (topic
res req) [d]: s
An error occurred while attempting
to generate a list of portals.
Contact Informatica Support
Gwd-6361-52: endpoint portal [s]
failed to allocate resolver buffer
[d]: s
An error occurred while attempting
to allocate a topic resolution buffer.
Contact Informatica Support
Gwd-6361-56: rm failed to join ctx
thread, s
UM was unable to join an internal
thread.
Contact Informatica Support.
Gwd-6361-57: rm failed to join evq
thread, s
UM was unable to join an internal
thread.
Contact Informatica Support.
Gwd-6361-5: endpoint portal [s]
failed to schedule remote domain
topic check timer [d]: s
An error occurred while attempting
to schedule an internal timer.
Contact Informatica Support
9.4 UM Dynamic Routing Log Messages 229
Gwd-6361-61: overriding 'interest'
based route decisions on portal d
Route decisions are now overriden
regarding whether or not to propa-
gate interest on the specified por-
tal.
Don't set the TNWG_PORTAL_R←-
OUTE_OVERRIDE env variable.
Gwd-6361-62: overriding 'receiver'
based route decisions on portal d
Route decisions are now overriden
regarding whether or not to create
a receiver on the specified portal.
Don't set the TNWG_PORTAL_R←-
OUTE_OVERRIDE env variable.
Gwd-6361-63: overriding 'source'
based route decisions on portal d
Route decisions are now overriden
regarding whether or not to propa-
gate sources on the specified por-
tal.
Don't set the TNWG_PORTAL_R←-
OUTE_OVERRIDE env variable.
Gwd-6361-67: portal [s] failed to
join psm evq thread, s
UM has failed to join an event
queue dispatch thread.
Contact Informatica Support.
Gwd-6361-69: portal [s] psm evq
lbm_event_dispatch() failed, s
An error occurred while attempting
to process events off an internal
event queue.
Contact Informatica Support.
Gwd-6361-6: endpoint portal [s]
failed to schedule remote domain
topic check timer [d]: s
An error occurred while attempting
to schedule an internal timer.
Contact Informatica Support
Gwd-6361-71: portal [s] failed to
join prm evq thread, s
UM has failed to join an internal
event queue dispatch thread.
Contact Informatica Support.
Gwd-6361-72: TNWG PRM pro-
cessing failed [d]: s
An error occurred while attempting
to process an internal interest noti-
fication.
Contact Informatica Support.
Gwd-6361-73: portal [s] prm evq
lbm_event_dispatch() failed, s
An error occurred while attempting
to process events off an internal
event queue.
Contact Informatica Support.
Gwd-6361-74: route recalculation
took u.%06u seconds
Running route recalculations took
the indicated amount of time to
complete.
Nothing. This is purely informa-
tional.
Gwd-6361-75: route recalculation
backoff has exceeded the specified
threshold
Your network topology has failed
to converge within the specified
threshold.
Attempt to identify the gateway or
peer link that is causing the insta-
bility in your topology.
Gwd-6361-77: loop count == d You're running a build of the gate-
way with TNWG_RM_LOOP_CO←-
UNT defined in tnwgrm.c.
Contact Informatica Support
Gwd-6361-78: rm evq lbm_←-
event_dispatch() failed, s
An error occurred while attempting
to process events off an internal
event queue.
Contact Informatica Support
Gwd-6361-79: rm ctx lbm_←-
context_process_events() failed,
s
An error occurred while attempting
to process events on an internal
context.
Contact Informatica Support
Gwd-6361-7: endpoint portal [s]
failed to schedule remote domain
pattern check timer [d]: s
An error occurred while attempting
to schedule an internal timer.
Contact Informatica Support
Gwd-6361-81: TNWG PRM do-
main processing failed [d]: s
An error occurred while attempting
to process an internal domain noti-
fication.
Contact Informatica Support.
Gwd-6361-84: unable to parse link
state buffer
An error occurred while deserializ-
ing an incoming link state packet.
Contact Informatica Support.
Gwd-6361-85: unable to read pdm
field [node_name] for link state
forwarding: [s]
An error occurred while reading a
field in an internal PDM message.
Contact Informatica Support.
Gwd-6361-86: unable to create
neighbor asl: s
UM was unable to create an inter-
nal data structure.
Contact Informatica Support.
230 UM Log Messages
Gwd-6361-87: unable to set pdm
field [s] for link state propagation:
[s]
An error occurred while setting P←-
DM field in an internal PDM mes-
sage.
Contact Informatica Support.
Gwd-6361-88: unable to set
pdm field vec [s] for link state
propagation: [s]
An error occurred while setting P←-
DM field vec in an internal PDM
message.
Contact Informatica Support.
Gwd-6361-89: unable to cre-
ate pdm message for link state
propagation: [s]
An error occurred while creating in-
ternal PDM message.
Contact Informatica Support.
Gwd-6361-8: endpoint portal [s]
failed to schedule remote domain
pattern check timer [d]: s
An error occurred while attempting
to schedule an internal timer.
Contact Informatica Support
Gwd-6361-91: route recalculation
is taking longer than the route info
propagation interval
Running route recalculations took
longer than the specified route info
propagation interval.
Adjust appropriate configuration
options
Gwd-6361-93: shortest path from u
to u not found
Unable to find an expected internal
data structure.
Contact Informatica Support.
Gwd-6361-94: failed to add node
[u] to an internal domain list: s
An error occurred while creating an
internal domain list.
Contact Informatica Support.
Gwd-6361-97: psm p failed to prop-
agate a message [d]: s
An error occurred while attempting
to forward a message.
Contact Informatica Support.
Gwd-6361-98: Unable to enqueue
a source entry onto the wakeup
queue: s
An error occurred while attempting
to enqueue data on to an internal
queue.
Contact Informatica Support.
Gwd-6361-99: Unable to enqueue
a source wakeup event on to an
event queue: s
An error occurred while attempting
to enqueue a wakeup event on to
an internal event queue.
Contact Informatica Support.
Gwd-6361-9: endpoint portal [s] re-
mote domain s check ivl dropped
below threshold of d. Reseting to
d
Desired configuration for the inter-
est timeout threshold in conjunc-
tion with the current number of
symbols has caused UM to calcu-
late a check interval lower than the
threshold of 50 milliseconds.
Adjust the appropriate configura-
tion parameters to check each
symbol less often.
Gwd-6814-10: invalid ingress-cost
value [s]
The specified value is either non-
numeric or the value is out of range.
Please specify a valid value.
Gwd-6814-11: egress-cost must
not be blank
Must specify a valid numeric value.
Gwd-6814-12: invalid egress-cost
value [s]
The specified value is either non-
numeric or the value is out of range.
Please specify a valid value.
Gwd-6814-13: source-deletion-
delay must not be blank
Must specify a valid numeric value.
Gwd-6814-14: invalid source-
deletion-delay value [s]
The specified value is either non-
numeric or the value is out of range.
Please specify a valid value.
Gwd-6814-15: The late-join ele-
ment has been deprecated and will
be ignored
The specified element has been
deprecated.
Remove the element from the con-
fig file.
Gwd-6814-16: The topic-purge ele-
ment has been deprecated and will
be ignored
The specified element has been
deprecated.
Remove the element from the con-
fig file.
Gwd-6814-17: The topic-interest-
generate element has been depre-
cated and will be ignored
The specified element has been
deprecated.
Remove the element from the con-
fig file.
Gwd-6814-18: The topic-domain-
activity element has been depre-
cated and will be ignored
The specified element has been
deprecated.
Remove the element from the con-
fig file.
9.4 UM Dynamic Routing Log Messages 231
Gwd-6814-19: The pattern-purge
element has been deprecated and
will be ignored
The specified element has been
deprecated.
Remove the element from the con-
fig file.
Gwd-6814-20: The pattern-
interest-generate element has
been deprecated and will be
ignored
The specified element has been
deprecated.
Remove the element from the con-
fig file.
Gwd-6814-21: The pattern-
domain-activity element has been
deprecated and will be ignored
The specified element has been
deprecated.
Remove the element from the con-
fig file.
Gwd-6814-22: size value [s] for
sourcemap is invalid
The specified value is either non-
numeric or the value is out of range.
Please specify a valid value.
Gwd-6814-23: check interval value
[s] for remote-topic is invalid
The specified value is either non-
numeric or the value is out of range.
Please specify a valid value.
Gwd-6814-24: max topics value [s]
for remote-topic is invalid
The specified value is either non-
numeric or the value is out of range.
Please specify a valid value.
Gwd-6814-25: timeout value [s] for
remote-topic is invalid
The specified value is either non-
numeric or the value is out of range.
Please specify a valid value.
Gwd-6814-26: check interval value
[s] for remote-pattern is invalid
The specified value is either non-
numeric or the value is out of range.
Please specify a valid value.
Gwd-6814-27: max patterns value
[s] for remote-pattern is invalid
The specified value is either non-
numeric or the value is out of range.
Please specify a valid value.
Gwd-6814-28: timeout value [s] for
remote-pattern is invalid
The specified value is either non-
numeric or the value is out of range.
Please specify a valid value.
Gwd-6814-29: The topic-use-
check element has been depre-
cated and will be ignored
The specified element has been
deprecated.
Remove the element from the con-
fig file.
Gwd-6814-30: The pattern-use-
check element has been depre-
cated and will be ignored
The specified element has been
deprecated.
Remove the element from the con-
fig file.
Gwd-6814-3: invalid min-interval
value [s]
The specified value is either non-
numeric or the value is out of range.
Please specify a valid value.
Gwd-6814-4: invalid max-interval
value [s]
The specified value is either non-
numeric or the value is out of range.
Please specify a valid value.
Gwd-6814-5: invalid min-interval
value [s]
The specified value is either non-
numeric or the value is out of range.
Please specify a valid value.
Gwd-6814-6: invalid max-interval
value [s]
The specified value is either non-
numeric or the value is out of range.
Please specify a valid value.
Gwd-6814-7: invalid min-interval
value [s]
The specified value is either non-
numeric or the value is out of range.
Please specify a valid value.
Gwd-6814-8: invalid max-interval
value [s]
The specified value is either non-
numeric or the value is out of range.
Please specify a valid value.
Gwd-6814-9: ingress-cost must not
be blank
Must specify a valid numeric value.
Gwd-6873-1: endpoint portal [s]
failed to allocate resolver buffer
[d]: s
An error occurred while attempting
to allocate a topic resolution buffer.
Contact Informatica Support
Gwd-6945-1: Portal [s] began en-
queueing data
The named portal began enqueue-
ing data due to LBM_EWOULDB←-
LOCK.
This is an informational message
only. The message traffic is higher
than can be handled. Check config
or network load.
232 UM Log Messages
Gwd-6945-2: Portal [s] dropping
data due to high volume
The named portal is dropping data.
This is due to the message queue
being full or disabled. Message is
throttled and code may be dropping
at a higher rate than indicated by
log message. Check Web Monitor
stats.
This is an informational message
only. The message traffic is higher
than can be handled. Check config
or network load.
Gwd-6945-3: Portal [s] completed
flushing queue
The named portal completed de-
queueing the data previoused en-
queued.
This is an informational message
only. The message traffic has
slowed so that the queue could be
emptied.
Gwd-7079-5: unable to create
route manager [d]: s
An error occurred while attempting
to create an internal component.
Contact Informatica Support.
Gwd-7097-1: peer portal [s] has
just established a connection to
gateway named: [s] with node id:
u
A peer connection has just been
established to the specified gate-
way.
Gwd-7097-3: peer portal [s] failed
to properly connect to gateway with
node id: u [d]: s
The gateway failed to establish a
logical connection to the gateway at
the other end of the peer link. The
link will remain up, but no traffic will
flow.
This is usually caused by having
more than one peer connection to
the same gateway, which is an un-
supported configuration.
Gwd-7097-4: peer portal [s] failed
to properly connect to gateway
named: [s] with node id: u [d]: s
The gateway failed to establish a
logical connection to the gateway at
the other end of the peer link. The
link will remain up, but no traffic will
flow.
This is usually caused by having
more than one peer connection to
the same gateway, which is an un-
supported configuration.
Gwd-7122-1: Gateway named [s]
with node id: u has started.
Your gateway has just started.
Gwd-7136-1: Ultra Messaging
Gateway version s
Printed at startup.
Gwd-7136-2: s Printed at startup.
Gwd-7136-3: EXPERIMENTAL
BUILD - NOT FOR PRODUCTION
USE
Printed at startup.
Gwd-7155-1: Gateways can not
have more than d portals
The gateway had too many portals
specified.
Specify fewer portals.
Gwd-8239-1: peer portal [s] failed
to enqueue connect abort [d]: s
An error occurred while handling a
peer connection failure.
Contact Informatica Support
Gwd-8851-1: datagram max size
mismatch max_datagram_size[d]
msg buffer length [d] - Dropping
message.
A message is larger than the con-
figured maximum datagram size for
the outgoing port.
This implies that there is a data-
gram max size configuration error
with in the system. All max_←-
datagram_size settings must be set
to the same value through out the
entire system.
Gwd-8851-2: datagram max size
mismatch max_datagram_size[d]
msg buffer length [d] - Dropping
message.
A message is larger than the con-
figured maximum datagram size for
the outgoing port.
This implies that there is a data-
gram max size configuration error
with in the system. All max_←-
datagram_size settings must be set
to the same value through out the
entire system.
Gwd-8955-8: failed to join logging
thread during shutdown error=i
Attempt to shutdown logging thread
failed
Contact support, this should not
happen and may be the result of
corruption
9.4 UM Dynamic Routing Log Messages 233
Gwd-9175-10: failed to register FD
read callback [d]: s
An error occurred attempting to
register the FD read callback.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-11: failed to register FD
write callback [d]: s
An error occurred attempting to
register the FD write callback.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-12: failed to create send
queue [d]: s
An error occurred attempting to
create the send queue.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-13: failed to create
batcher [d]: s
An error occurred attempting to
create the send batcher.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-14: failed to cancel re-
ceive timer [d]: s
An error occurred attempting to
cancel the receive timer.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-15: failed to create send
queue [d]: s
An error occurred attempting to
create the send queue.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-16: failed to create
batcher [d]: s
An error occurred attempting to
create the send batcher.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-17: connected to [s:u] The DRO has connected to a peer
portal.
No action required.
Gwd-9175-18: error on send [d]: s Error sending. The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-19: error on send [d]: s Error sending. The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-1: lbm_implicit_←-
batcher_send failed [d]: s
An attempt to send batched mes-
sages has failed.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-20: error enqueuing
message [d]: s
An error occurred enqueuing a
message to be sent.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-21: failed to create peer
accept socket [d]: s
Failure creating peer accept
socket.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-22: failed to register FD
accept callback [d]: s
Failure registering th FD accept
callback.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-23: lbm_implicit_←-
batcher_send failed [d]: s
An error occured sending batched
messages.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-24: failed to accept con-
nection (accept) [d]: s
An error occurred accepting a con-
nection.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-25: failed to create send
queue [d]: s
An error occurred attempting to
create the send queue.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-26: failed to create
batcher [d]: s
An error occurred attempting to
create the send batcher.
The error message includes the er-
ror number and text pertaining to
the specific error.
234 UM Log Messages
Gwd-9175-27: failed to register FD
read callback [d]: s
An error occurred attempting to
register the FD read callback.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-28: failed to register FD
write callback [d]: s
An error occurred attempting to
register the FD write callback.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-29: error on socket re-
ceive [d]: s
An error occurred reading the
socket
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-2: error on socket re-
ceive [d]: s
An error occurred reading the
socket
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-30: error on socket re-
ceive [d]: s
An error occurred reading the
socket
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-31: detected dropped
connection (zero-len read)
Connection Closed due to a zero
byte read.
Ensure the peer DRO is running
Gwd-9175-32: received connection
from [s:u]
Received new connection No action required
Gwd-9175-34: error on send [d]: s Error sending. The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-35: error on send [d]: s Error sending. The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-36: error enqueuing
message [d]: s
An error occurred enqueuing a
message to be sent.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-37: failed to cancel s FD
ALL event [d]: s
An error canceling all events for an
FD.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-38: failed to cancel FD
WRITE event [d]: s
An occurred canceling the FD write
event.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-39: failed to register FD
write callback [d]: s
An error occurred attempting to
register the FD write callback.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-3: error on socket re-
ceive [d]: s
An error occurred reading the
socket
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-40: connection de-
stroyed due to shutdown
Connection removed during shut-
down
No action required.
Gwd-9175-41: failed to connect to
peer at [s:u] via [s]
An attempt to connect to a peer
failed.
This message indicates that a con-
figured peer is not responding.
Check that the peer is operational.
Gwd-9175-42: connection de-
stroyed due to socket failure
The connection to a peer due to a
socket error.
Gwd-9175-43: lost connection to
peer at [s:u] via [s]
The stated peer is no longer con-
nected.
This message indicates that a con-
figured peer is not responding.
Check that the peer is operational.
Gwd-9175-44: lost connection with
peer at [s:u] via [s]
The stated peer is no longer con-
nected.
This message indicates that a con-
figured peer is not responding.
Check that the peer is operational.
9.4 UM Dynamic Routing Log Messages 235
Gwd-9175-4: failed to schedule
socket connect [d]: s
The attempt to schedule the socket
connect timer failed.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-5: failed to cancel con-
nect timer [d]: s
The attempt to cancel the socket
connect timer failed.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-6: failed to connect to
peer at [s:u] via [s] [d]: s
An error occurred connecting to the
peer.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-7: failed to register FD
connect callback [d]: s
An error occurred attempting to
register the FD connect callback.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-8: failed to cancel FD
connect event [d]: s
An error occurred attempting to
cancel the FD connect event.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9175-9: failed to schedule re-
ceive timer [d]: s
An error occurred attempting to
register the receive timer.
The error message includes the er-
ror number and text pertaining to
the specific error.
Gwd-9565-1: Attempted to negoti-
ate protocol "%s" with peer s:d, but
peer refused. Now trying protocol
"%s".
The other side of a TCP connection
actively refused a proposed proto-
col; usually this means the other
application is not configured to sup-
port the protocol or is an older ver-
sion that does not understand it.
Check for version or configuration
mismatches.
Gwd-9565-2: Attempted to negoti-
ate protocol "%s" with peer s:d, but
peer refused. Unable to communi-
cate with peer.
The other side of a TCP connection
actively refused a proposed proto-
col; usually this means the other
application is not configured to sup-
port the protocol or is an older ver-
sion that does not understand it.
Check for version or configuration
mismatches.
Gwd-9571-31: error resolving
source IP ACE: s
The supplied source IP ACE could
not resolve the provided IPv4
dotted-decimal address or domain
name
Provide a valid name. See RFCs
952 and 1123 for DNS naming con-
ventions.
Gwd-9571-32: error resolving mul-
ticast group ACE: s
The supplied multicast ACE could
not resolve the provided IPv4
dotted-decimal address or domain
name
Provide a valid name. See RFCs
952 and 1123 for DNS naming con-
ventions.
Gwd-9574-01: RecalcTrigger:LINK
CAME UP:Version = d:NodeId = u
A link has come up. This is an information message
only. An event has occured that
may trigger a route table recalcula-
tion
Gwd-9574-02: RecalcTrigger:LINK
WENT DOWN:Version = d:NodeId
= u
A link has gone down. This is an information message
only. An event has occured that
may trigger a route table recalcula-
tion
Gwd-9574-03: RecalcTrigger:FO←-
RCED RECALC:Version = d
A route recalculation was forced
from the Web monitor.
This is an information message
only. An event has occured that
may trigger a route table recalcula-
tion
Gwd-9574-04: RecalcTrigger:NEW
DRO DISCOVERED:Version = d←-
:NodeId = u:Node Name = s
A new DRO within the network has
been discovered.
This is an information message
only. An event has occured that
may trigger a route table recalcula-
tion
236 UM Log Messages
Gwd-9574-05: RecalcTrigger:NO←-
DE UPDATED:Version = d:NodeId
= u:Node Name = s
A DRO within the network has ad-
vertised a route change.
This is an information message
only. An event has occured that
may trigger a route table recalcula-
tion
Gwd-9574-06: RecalcTrigger:DRO
TIMED OUT:Version = d:NodeId =
u:Node name = s
A DRO within the network has
not delivered a heartbeat message
within the necessary interval.
This is an information message
only. An event has occured that
may trigger a route table recalcula-
tion
Gwd-9588-11: Negotiation timeout
with peer s:d.
A Peer portal failed to complete
the security/compression negotia-
tion within a reasonable timeout.
Negotiation failures are typically a
result of mis-configuration. Please
check the configuration.
Gwd-9597-1: compression value
[s] is invalid
The compression algorithm speci-
fied is unknown or unsupported.
Check configuration for typos and
check version for support of the
specified compression algorithm.
Gwd-9597-2: compression value
[s] is invalid
The compression algorithm speci-
fied is unknown or unsupported.
Check configuration for typos and
check version for support of the
specified compression algorithm.
Gwd-9597-3: unable to allocate
portal peer TLS info [d]: s
Can't allocate memory for Security. Check memory allocator or avail-
able memory.
Gwd-9815-1: Dual Channel Peer
links are no longer supported.
Please re-configure using Single
Channel.
Dual Channel Peer links are no
longer supported.
The customer needs to update their
configuration to use Single Chan-
nel Peer links instead.
Gwd-9932-01: smart-batch must
not be blank
Bad configuration for smart-batch Customer needs to check the con-
figuration file.
Gwd-9932-02: invalid smart-batch
value [s]
Bad configuration for smart-batch Customer needs to check the con-
figuration file.
GwdApi-5688-4702: failed to set
portal source option [s] to [s]: s
The portal was unable to set a
source option
GwdApi-5688-4703: failed to set
portal receiver option [s] to [s]: s
The portal was unable to set a re-
ceiver option
GwdApi-6103-0001: failed to set
portal source option [s] to [s]: s
The portal was unable to set a
source option
GwdApi-6103-0002: failed to set
portal receiver option [s] to [s]: s
The portal was unable to set a re-
ceiver option
GwdApi-6361-110: unable to cre-
ate pdm definition: s
An error occurred while creating an
internal PDM definition.
Contact Informatica Support.
GwdApi-6361-113: unable to add
pdm field definition [s]: [s]
An error occurred while adding a
PDM field to an internal PDM def-
inition.
Contact Informatica Support.
GwdApi-6361-114: failed to create
psm delete q
UM has failed to create an internal
queue.
Contact Informatica Support.
GwdApi-6361-120: must not set
the route recalculation backoff in-
terval greater than the route recal-
culation warning interval
The backoff interval must be less
than the warning interval, other-
wise the warning will fire at least
once for each recalculation.
Adjust the configuration.
GwdApi-6361-121: failed to propa-
gate source creation: s
An error occurred while attempting
to propagate the need to create a
proxy source to another portal.
Contact Informatica Support.
GwdApi-6361-122: failed to propa-
gate source creation: s
An error occurred while attempting
to propagate the need to create a
proxy source to another portal.
Contact Informatica Support.
9.4 UM Dynamic Routing Log Messages 237
GwdApi-6361-53: failed to create
rm ctx attr: s
UM was unable to create context
attributes.
Contact Informatica Support.
GwdApi-6361-54: failed to set rm
context option [s] to [s]: s
UM was unable to set the specified
context attributes.
Contact Informatica Support.
GwdApi-6361-55: failed to create
rm ctx: s
UM was unable to create an inter-
nal reactor only context.
Contact Informatica Support.
GwdApi-6361-58: failed to create
rm evq thread [d]
UM was unable to create an inter-
nal thread.
Contact Informatica Support.
GwdApi-6361-59: failed to create
rm ctx thread [d]
UM was unable to create an inter-
nal thread.
Contact Informatica Support.
GwdApi-6361-60: unable to sched-
ule rm timer
UM was unable to schedule an in-
ternal timer.
Contact Informatica Support.
GwdApi-6361-64: failed to create
psm evq thread [d]
UM has failed to create an internal
thread.
Contact Informatica Support.
GwdApi-6361-65: failed to create
psm wakeup q
UM has failed to create an internal
queue.
Contact Informatica Support.
GwdApi-6361-66: failed to create
psm blocked q
UM has failed to create an internal
queue.
Contact Informatica Support.
GwdApi-6361-70: failed to create
prm evq thread [d]
UM has failed to create an internal
event queue dispatch thread.
Contact Informatica Support.
GwdApi-6361-76: unable to sched-
ule rm timer
An error occurred while attempting
to schedule an internal timer.
Contact Informatica Support
GwdApi-6361-80: could not insert
o_entry into otid_list [s:d]
An error occurred while attempting
to insert a data entry into an inter-
nal data structure.
Contact Informatica Support.
GwdApi-6361-82: unable to finalize
pdm definition: [s]
An error occurred while finalizing
an internal PDM definition.
Contact Informatica Support.
GwdApi-6361-83: unable to cre-
ate pdm message for link state
forwarding: [s]
An error occurred while creating an
internal PDM message.
Contact Informatica Support.
GwdApi-6361-90: the specified
gateway name exceeds the max
name length of d
The gateway name is too long. Pick a shorter name.
GwdApi-6361-92: failed to propa-
gate source creation: s
An error occurred while attempting
to propagate the need to create a
proxy source to another portal.
Contact Informatica Support.
GwdApi-6361-95: received a
source delete for an unknown
source on topic [s]
Unable to locate the source entry
for the topic in question.
Contact Informatica Support.
GwdApi-6814-1: topic interest max
interval must be greater than the
min interval
The topic-interest min-interval must
be less than the topic-interest max-
interval.
Set the min/max intervals appropri-
ately.
GwdApi-6814-2: pattern interest
max interval must be greater than
the min interval
The pattern-interest min-interval
must be less than the topic-interest
max-interval.
Set the min/max intervals appropri-
ately.
GwdApi-7097-2: duplicate adja-
cent node id detected: u
A portal is adjacent to either a topic
resolution domain or another gate-
way to which another portal on this
gateway is already adjacent.
Adjust configuration so that no two
portals on any gateway are adja-
cent to the same topic resolution
domain or the same gateway.
GwdApi-7582-10: failed to get por-
tal source transport option (s)
The portal was unable to get a
source transport option.
This is an LBM error. Please refer
to the given LBM error message.
GwdApi-7582-3: the DRO does not
allow LBT-SMX to be the default
source transport.
The DRO does not support the L←-
BT-SMX source transport. This is
a configuration failure and the DRO
will exit.
The customer should use a differ-
ent source transport when the D←-
RO is configured. Please reconfig-
ure the source transport type.
238 UM Log Messages
GwdApi-8955-5: callback process
for logging thread must not be N←-
ULL
Callback function argument for
rolling logfile thread is NULL
The argument is likely corrupted;
this should never happen, contact
support
GwdApi-8955-6: could not allocate
tl queue for logging thread
Attempt to create a queue to sup-
port the thread for rolling log files
failed
Check if system resources are
available such as memory or locks
GwdApi-8955-7: olog Create←-
Thread: s
Could not create utility thread for
rolling log files
Check if adequate system thread-
ing resources are available
GwdApi-9932-10: failed to set
portal receiver context option
[receive_batch_notification_←-
function]: s
An error internal to LBM was en-
countered.
Check the LBM Error string for de-
tails of the LBM specific error.
9.5 UM Lbmrd Log Messages
Lbmrd-10492-1: Using interface [s] An interface was specified for the
lbmrd and the IP address it will bind
to is indicated.
The message is for your informa-
tion
Lbmrd-5466-1: LBMR Extended
Type 0xx incorrect (s.d len d). [s].
Dropping.
Received a LBMR message with
an unrecognized value in the ex-
tended type field.
Check if the port range of other L←-
BM protocols like RU overlaps with
those used by LBMR.
Lbmrd-5688-4674: LBMR Topic
Query Record malformed. Drop-
ping remainder.
UMS encountered a mismatch in
the length of a received message
and its headers, determining the
rest of the message to be invalid.
The remainder of the message is
dropped.
Contact Informatica support if this
message occurs frequently.
Lbmrd-5688-4675: LBMR Topic
Info Record malformed. Dropping
remainder.
UMS encountered a mismatch in
the length of a received message
and its headers, determining the
rest of the message to be invalid.
The remainder of the message is
dropped.
Contact Informatica support if this
message occurs frequently.
Lbmrd-5688-4676: LBMR error
sending TIRs to (s.d len d)(s).
An error occurred forwarding the
TIR packets to the clients.
This error message will contain an
additional internal lbm error mes-
sage which will give details of the
exact problem encountered.
9.6 UM Persistent Store Log Messages
9.6 UM Persistent Store Log Messages 239
Store-10184-08: dmon evq lbm_←-
event_dispatch() failed, s
An error occurred while attempting
to process events off an internal
event queue.
Contact Informatica Support.
Store-10184-100: failed to create
dmon ctx attr: s
UM was unable to create context
attributes.
Contact Informatica Support.
Store-10184-101: failed to delete
dmon ctx attr: s
UM was unable to delete an in-
ternal context attributes structure.
Some memory has been leaked.
Contact Informatica Support.
Store-10184-102: failed to delete
dmon ctx attr: s
UM was unable to delete an in-
ternal context attributes structure.
Some memory has been leaked.
Contact Informatica Support.
Store-10184-103: failed to delete
src attr: s
UM was unable to delete an in-
ternal source attributes structure.
Some memory has been leaked.
Contact Informatica Support.
Store-10184-104: failed to delete
src: s
UM was unable to delete an inter-
nal source structure. Some mem-
ory has been leaked.
Contact Informatica Support.
Store-10184-105: failed to delete
dmon ctx: s
UM was unable to delete an inter-
nal context structure. Some mem-
ory has been leaked.
Contact Informatica Support.
Store-10184-10: failed to join dmon
evq thread, s
UM failed to join an internal event
queue dispatch thread.
Contact Informatica Support.
Store-10184-144: could not en-
queue repo create
In a reduced-fd RPP repository,
during the re-start( following a shut-
down, or crash), UM could not en-
queue repo create.
Contact customer support with the
log file.
Store-10184-60: WARNING: in-
valid store dmon message [s] from
s [s]
UM dmon received an invalid/cor-
rupted immediate message.
Verify that messages sent on the
request port are valid.
Store-10184-61: Store dmon failed
to send error response [s]
UM could not respond to a dmon
immediate message.
Contact Informatica Support.
Store-10184-62: Store dmon failed
to send success response [s]
UM could not respond to a dmon
immediate message.
Contact Informatica Support.
Store-10184-63: Store dmon re-
ceived control message exceeding
255 bytes
UM daemon monitor received an
invalid control message exceeding
255 bytes.
Verify that messages sent on the
control channel are <= 255 bytes.
Store-10184-64: Store dmon failed
to send error response [s]
UM could not respond to a dmon
immediate message.
Contact Informatica Support.
Store-10184-65: Store received
unknown lbm_msg_t type x [s][s]
UM daemon monitor received un-
known lbm_msg_t type.
Stop the source of unknown mes-
sages to the daemon monitor.
Store-10184-70: lbmaux_context←-
_attr_setopt_from_file: s error: s
UM was unable to set context at-
tributes from specified file.
Verify the path to the configuration
file.
Store-10184-71: failed to set dmon
context option [s] to [s]: s
UM was unable to set speci-
fied daemon monitoring context at-
tributes.
Contact Informatica Support.
Store-10184-72: lbm_src_topic_←-
attr_create: s
UM was unable to create dmon
source attribute.
Contact Informatica Support.
Store-10184-73: failed to set dmon
source option [s] to [s]: s
UM was unable to set speci-
fied daemon monitoring source at-
tributes.
Contact Informatica Support.
Store-10184-74: lbm_context_←-
create: s
UM was unable to create dmon
context.
Contact Informatica Support.
Store-10184-75: lbm_context_←-
create: s
UM was unable to create dmon
context.
Contact Informatica Support.
240 UM Log Messages
Store-10184-76: lbm_context_str←-
_getopt(request_tcp_port): s
UM was unable to get request tcp
port.
Contact Informatica Support.
Store-10184-77: lbm_src_topic_←-
alloc: s
UM was unable to allocate dmon
publishing topic.
Contact Informatica Support.
Store-10184-78: lbm_src_create: s UM was unable to create dmon
source.
Contact Informatica Support.
Store-10184-79: Daemon monitor
accepting requests on tcp port [s]
publishing to topic [s]
The store has successfully com-
pleted initialization of the daemon
publishing monitor.
This message for informational pur-
poses only and can be ignored.
Store-10184-80: umestore_←-
dmon_publish: s
UM was unable to publish dmon
message.
Contact Informatica Support.
Store-10190-10: lbm_context_←-
attr_str_setopt - round_robin_xsp←-
_count 0: s
Failed to turn off the xsp round
robin behavior.
Check for resource exhaustion, out
of memory errors, etc.
Store-10196-5: store "%s" topic
"%s" repository-disk-async-
buffer-length is greater than
the repository-disk-file-size-limit
repository-disk-async-buffer-length
is greater than the repository-disk-
file-size-limit
Change repository-disk-async-
buffer-length so that it is less than
the repository-disk-file-size-limit
Store-10366-1: Created daemon
monitor thread: id[s]
The store created the daemon
monitor thread with the reported
thread id.
This is for informational purposes
only and can be ignored.
Store-5116-2: WARNING: aio_←-
proactor aio_error u
An AIO system error encountered.
This could happen when asyn-
chronous read or write to the disk
fails.
Check the store log file for a de-
tailed error description.
Store-5230-15: Store "%s" re-
ceived retransmission from s for
unknown regid 0xx
The UMP store received a unicast
proactive retransmission for an un-
known reg ID.
Depending on timing, this could just
mean the source has been timed
out and cleaned up by the store
before the proactive retransmission
was sent or handled. This is usu-
ally not a serious issue and can
usually be ignored, however it may
indicate a UMP store or source that
is overloaded.
Store-5230-16: Store "%s" re-
ceived retransmission from s for
RCV regid u
The UMP store received a unicast
proactive retransmission for a reg
ID that doesn't belong to a source.
Find out where the proactive re-
transmissions are being sent from;
a duplicate reg ID could be in use
between a source and a receiver.
Store-5688-4914: queue "%s"
ReadFile read u nbytes u u
The Store has attempted to read
the sinc file for the specified num-
ber of bytes but was unable to read
the entire amount.
Please check the errno and take
appropriate actions.
Store-5688-4915: queue "%s"
aio_read returned u nbytes u u
The Store has attempted to read
the sinc file for the specified num-
ber of bytes but was unable to read
the entire amount.
Please check the errno and take
appropriate actions.
Store-5688-5070: default thread
stack size is perhaps too small, u
bytes.
The IPC receiver has created a
thread for internal processing and
the default stack size is too small.
The size of the default stack size is
dumped and will then be set to a
larger size automatically.
Store-5688-5071: reset thread
stack size to u bytes.
The IPC receiver has created a
thread for internal processing and
the default stack size is too small
and is reallocated. This message
reports the new size of the stack.
9.6 UM Persistent Store Log Messages 241
Store-5688-5243: store "%s" aio←-
_write returned u nbytes u u
Number of bytes returned by AIO
write is different than expected
Store-5688-5247: rotating file
cache offset d
The disk file cache has wrapped
around to the starting offset of 0.
This is an informational message
that requires no action on part of
the user.
Store-5688-5261: default thread
stack size is perhaps too small, u
bytes.
The store has created a thread for
internal processing and the default
stack size is too small. The size
of the default stack size is dumped
and will then be set to a larger size
automatically.
Store-5688-5262: reset thread
stack size to u bytes.
The store has created a thread for
internal processing and the default
stack size is too small and is real-
located. This message reports the
new size of the stack.
Store-5688-5290: store "%s" Ses-
sion ID u RegID u repository-type
forced to disk
Enforcing disk repository. It is cur-
rently configured as not disk.
Store-5688-5292: store "%s" new
receiver for topic "%s" Session ID u
SRC RegID u created. RCV Ses-
sion ID u RCV RegID u s s store
keepalives s Indices u.u s[u s.u]
The store has created a new re-
ceiver for the topic.
This is an informational message.
No further action is required. The
indicies describe the transport and
topic.
Store-5688-5293: store "%s" exist-
ing receiver for topic "%s" Session
ID u RegID u recreated. Session ID
u RegID u Indices u.u [u s.u]s
The store has recreated an existing
receiver for the topic.
This is an informational message.
No further action is required. The
indicies describe the transport and
topic.
Store-5688-5294: store "%s" RCV
Session ID u RegID u Indices u.u
[u s.u] deleted
The receiver with the specified ses-
sion ID and registration ID has
been deleted. This can be due
to several different things: the re-
ceiver's state-lifetime timing out,
the state-lifetime for the source the
receiver is subscribed to timing out,
or the receiver using the "deregis-
ter" API.
This message is encountered dur-
ing normal operation, and does not
need to be addressed.
Store-5688-5296: store "%s"
source Session ID u RegID u Re-
Registered and moved to Indices
u.u [u s.u]s
An old UMP source re-registered
with the store on new transport and
topic indices.
No action required.
Store-5688-5297: store "%s" re-
ceiver Session ID u RegID u Re-
Registered and moved to Indices
u.u [u s.u]s
An old UMP receiver re-registered
with the store on new transport and
topic indices.
No action required.
Store-5688-5332: AUDIT: queue
"%s" topic "%s" enqueued " UM←-
Q_MSGID_FORMAT "
A message was written to disk
that was received directly from a
source.
This is an info message and pro-
vided for informational purposes
when 'log audit trail' is enabled.
Store-5688-5333: AUDIT: queue
"%s" topic "%s" resubmitted " U←-
MQ_MSGID_FORMAT "
A message was written to disk that
was not received directly from a
source.
This is an info message and pro-
vided for informational purposes
when 'log audit trail' is enabled.
Store-5688-5382: store "%s" topic
"%s" Failed to cancel election timer,
s
The store could not cancel a proxy
election interval timer due to an in-
ternal lbm error.
This error message will contain an
additional internal lbm error mes-
sage which will give the exact prob-
lem encountered in the library.
242 UM Log Messages
Store-5688-5383: store "%s" topic
"%s" Session ID u RegID u Failed
to delete proxy source, s
The store has failed to delete a
proxy source due to internal lbm er-
rors.
The log message will contain ad-
ditional information about the exact
reason, investigate those errors.
Store-5688-5384: store "%s" topic
"%s" Session ID u RegID u Proxy
source deleted
Information log entry that states the
store has successfully deleted a
proxy source.
This log is expected under normal
operation when proxy sources are
enabled.
Store-5688-5385: store "%s" topic
"%s" Failed to schedule election
timer, s
The store could not schedule a
proxy source election timer due to
an internal lbm error.
The error message of this log con-
tains additional information as to
the specific reason the timer sched-
ule failed.
Store-5688-5442: An error was
encountered. See the message
above for details.
An error was encountered in the
ume configuration. See the "CR←-
ITICAL" error message before this
line for details.
Store-5688-5478: WARNING:
store "%s" existing Session ID u
RegID u cache file could not be
recreated. Renaming files.
Failure to recreate repository, pos-
sible data corruption or insufficient
memory on the machine
Look at the Store log for additional
information
Store-5688-5480: NOTICE: store
"%s" topic "%s" SRC Session ID u
RegID u duplicate sqn us; dropping
duplicates
The UMP store daemon received a
duplicate copy of a message frag-
ment it had already previously re-
ceived.
If the log message contains "re-
ceived via retransmission", the du-
plicate sequence number is likely
due to a proactive retransmission
being sent by the source; this most
likely means the store received the
message, but the source never got
the store's stability ACK for it. If this
happens frequently, check for TCP
connectivity or firewall issues from
the store back to the source's re-
quest port. If the log does not end
with "received via retransmission",
something more serious is wrong;
the source and the store may be
out of sync with each other with
respect to what sequence number
the source should be sending.
Store-5688-5481: store "%s" topic
"%s" SRC Session ID u RegID
u unrecoverable loss u (u not re-
ported)
A messages was declared unre-
coverably lost by the store's re-
ceiver's underlying delivery con-
troller.
See store log for more details.
Store-5688-5483: NOTICE: store
"%s" topic "%s" SRC Session ID u
RegID u sqn u (UL insert)
A message fragment was declared
unrecoverably lost by the store's re-
ceiver, but an entry for the fragment
was already present in the store's
repository.
This can happen if there has been
data loss on an original source
transport and a new or proxy
source has re-registered with the
store.
Store-5688-5484: store "%s" topic
"%s" SRC Session ID u RegID u
unrecoverable loss burst u
A burst of messages were declared
unrecoverably lost by the store's
receiver's underlying delivery con-
troller.
See store log for more details.
Store-5688-5562: WARNING:
Store "%s" existing state file [s]
malformed. Renaming files.
While reading in the store's state
file for a source, the store detected
the file to be corrupt. The file will
be renamed and the store will con-
tinue to initialize.
The state and cache files can be
corrupt if the store was improperly
shutdown.
9.6 UM Persistent Store Log Messages 243
Store-5688-5571: Store "%s" SRC
Session ID u RegID u source per-
sistence registration received while
in unknown state d
Source registration received in un-
known state
no resolution
Store-5688-5574: Store "%s" Re-
ceiver Persistence Registration re-
ceived before the SRI from source.
Source RegID u
Received Receiver registration re-
quest before any SRI has been
seen from the Persistent Source.
This can be due to not receiving the
TIR from the source, not joining the
transport, or not seeing the SRI on
the transport
Store-5688-6526: umestore_retx←-
_create failed: shutting down s
Possible Malloc Failure or too big
queue size requested
Look at the log file for other failures
Store-5820-1: releasing sinc msg
ID [ x : x ] but could not find in SINC
queue msg list
A message was previously added
to an internal list for queue brows-
ing support, but was not found in
that list upon dequeueing the mes-
sage.
Store-5820-2: msg [ x : x ] was al-
ready present in SINC msg list; re-
moving old
A newly received message was al-
ready present in an internal mes-
sage list used for queue browsing
support.
Store-5820-3: msg [ x : x ] was al-
ready present in SINC msg list; re-
moving old
A newly received message was al-
ready present in an internal mes-
sage list used for queue browsing
support.
Store-5867-4: could not create
skipped msg list
An internal error occurred during
ASL creation
Look for previous error messages
in the log such as a malloc error
Store-5867-5: could not create
skipped msg list
An internal error occurred during
ASL creation
Look for previous error messages
in the log such as a malloc error
Store-5867-8: error occurred while
evaluating message selector s
An error occurred while evaluating
the message selector during as-
signment for this receiver and mes-
sage
Look for previous error messages
in the log regarding message se-
lector evaluation problems
Store-5867-9: error occurred while
evaluating message selector s
An error occurred while evaluating
the message selector during as-
signment for this receiver and mes-
sage
Look for previous error messages
in the log regarding message se-
lector evaluation problems
Store-5891-12: source RegID u
disk-cache file contains duplicate
sqn x
Duplicate sequence number is de-
tected for the repository being pro-
cessed
Store-5891-13: Could not initialize
s Repository: s
Key Value Store subsystem failed
to start
Store-5891-14: Store "%s" could
not shutdown s subsystem prop-
erly.
Store could not shutdown reduced-
fd subsystem
Contact customer support with the
log file.
Store-5891-15: Store "%s" could
not activate the s subsystem
Reduced-fd subsystem is initial-
ized, but can not be activated due
to failure activation message send
error.
Contact customer support.
Store-5891-17: could not create
disk_info_t for the repo[Session ID
u RegID u]
If the log message is preceded by
NULL ptr errors, Store is attempting
to create a structure when it should
not. Otherwise, system is out of
memory.
Report a bug report if the message
is preceded by NULL ptr error. Oth-
erwise, root cause of memory prob-
lem should be investigated.
244 UM Log Messages
Store-5891-18: WARNING: store
"%s" existing Session ID u Reg←-
ID u disk metadata and/or msgs in
repository(for non-shutdown) can
be removed in a clean way
Store can not delete reduced-fd
repository from disk. Error oc-
curred during the submission of
delete requests of the messages
that belong to repository being
deleted to the thread responsible
for deleting messages from the
disk.
Contact customer support.
Store-5891-21: sanity check failed
[s:d]
Function is called in state that is not
expected by the function.
Contact customer support
Store-5891-22: sanity check failed
[s:d]
Function is called in state that is not
expected by the function.
Contact customer support
Store-5891-23: store "%s" s store
write returned: s with error code: d
Reduced-fd subsystem can not
persist message(s) to disk. Return
message and error code give more
details.
Contact customer support with the
log message printed.
Store-5891-24: store "%s" s store
write returned error code: d
Reduced-fd subsystem can not
persist message(s) to disk. Error
code give more details.
Contact customer support with the
log message printed
Store-5891-2: could not submit to
control-queue 0xx [s:d]
Can not enqueue control event to
key/value worker threads control
queue
Store-5891-30: error in closing the
state_fd after re-start is completed
for the repo
Reduced-fd repository state file de-
scriptor can not be closed. This is
an operating system error.
Contact customer support with the
store log file.
Store-5891-32: Store Recovery←-
: key length mismatch read key
length: u does not match 8-byte
key
While recovering reduced-fd repos-
itory, corrupted message is read
from the disk. The length of the key
that is used to store messages to
disk is always 8 bytes. Store is go-
ing to discard this message.
Contact customer support with the
store log file.
Store-5891-33: Store Recovery←-
: value pointer is null
While recovering reduced-fd repos-
itory, message contents are miss-
ing for a key value.
Contact customer support with the
store log file.
Store-5891-34: key pointer is NU←-
LL
While recovering reduced-fd repos-
itory, a message without a key
value is detected. Store is going to
discard this message.
Contact customer support with the
store log file.
Store-5891-35: Store Recovery←-
: Duplicate sequence # is detected,
deleting the entry with key: u
During the re-start ( following a
crash or shutdown ), for reduced-fd
repositories, while processing mes-
sages previously written to disk,
the message being processed has
a duplicate sequence number—
another message with the same
sequence number was processed
previously. Store is going to discard
this message.
Contact customer support with the
store log file.
Store-5891-36: Store Recovery←-
: internal error when processing the
entry with key: u
During the re-start ( following a
crash or shutdown), for reduced-fd
repositories, while processing mes-
sages previously written to disk, an
internal error ( resource creation, or
memory error) occurred.
Contact customer support with the
store log file.
9.6 UM Persistent Store Log Messages 245
Store-5891-38: Can not create s
repo thread
On windows platform, creation of
the thread responsible for process-
ing reduced-fd I/O requests failed.
Contact customer support with
store log file.
Store-5891-39: Can not open s
repository
The reduced-fd store can not
open/create reduced-fd folder. This
error is FATAL.
Contact customer support. Please
provide the execution environment,
i.e. OS details.
Store-5891-40: Can not create s
worker thread info holder structure
The thread information structure
that holds vital information that is
needed for reduced-fd I/O requests
can not be created due to lack of
memory
The root cause of the low memory
needs to be found, store can not
function in this state.
Store-5891-41: Can not get s
repository attribute values
The function responsible for gath-
ering reduced-fd subsystem pa-
rameters failed.
Contact customer support with the
store log file.
Store-5891-42: Can not create s
dispatch thread
The thread responsible for calling
callback functions for the previously
submitted reduced-fd I/O requests
can not created.
Contact customer support with
store log file.
Store-5891-43: FATAL: Can not
open s repository: s: Error s
The reduced-fd store can not
open/create the reduced-fd folder.
This error is FATAL.
Contact customer support. Please
provide the execution environment,
i.e. OS details.
Store-5891-44: Rename/or Delete
the repository directory: s
The reduced-fd store can not
open/create the reduced-fd folder
within the cache folder.
Failure to open reduced-fd folder is
a serious error. Try running store
with an empty cache folder, if error
persists, contact customer support
Store-5891-45: s worker thread
can not pass the read record to dis-
patch thread
Reduced-fd subsystem error. Re-
quested message writes requests
are processed, i.e. either mes-
sages are persisted to disk, or error
code is returned, however, request
call back is not going to be called
due to error in sending the status
code to call back dispatch thread
Contact customer support with the
store log file.
Store-5891-46: s worker thread
can not commit message deletes:
err: s
When store is shutting down,
the reduced-fd subsystem can not
delete messages from disk. Pos-
sible failure reasons are reduced-
fd-api error, memory error, or NULL
pointer might have been passed to
delete function.
Contact customer support with the
store log file.
Store-5891-47: s worker thread
can not commit message deletes
during shutdown: err: s
When store is shutting down,
reduced-fd subsystem can not
delete messages from disk. Pos-
sible failure reasons are leveldb-
api error, memory error, or NULL
pointer might have been passed to
delete function.
Contact customer support with the
store log file.
Store-5891-48: s worker thread
can not commit batch deletes: err:
s
Reduced-fd subsystem can not
delete messages from disk. Pos-
sible failure reasons are reduced-
fd-api error, memory error, or NULL
pointer might have been passed to
delete function.
Contact customer support with the
store log file.
246 UM Log Messages
Store-5891-49: s worker thread
can not commit batch deletes: err:
s
Reduced-fd subsystem can not
delete messages from disk. Pos-
sible failure reasons are reduced-
fd-api error, memory error, or NULL
pointer might have been passed to
delete function.
Contact customer support with the
store log file.
Store-5891-4: NULL ptr [s:d] Null pointer detected
Store-5891-50: s worker thread
can not read msg from s repository
err_code: u
A message belonging to a reduced-
fd repository can not be retrieved
from the disk. There are multiple
causes that lead to this error.
The error code in this log message
provides more information regard-
ing to why message can not be re-
trieved. Contact customer support
with the store log file.
Store-5891-51: s worker thread
can not pass write request status to
dispatch thread err_code: u
Reduced-fd subsystem error. Re-
quested message writes requests
are processed, i.e. either mes-
sages are persisted to disk, or error
code is returned, however, request
call back is not going to be called
due to error in sending the status
code to call back dispatch thread
Contact custormer support with the
store log file.
Store-5891-52: s worker thread
can not commit the write request
err_code: u err: s
Reduced-fd repository can not per-
sist message(s) to disk due to inter-
nal failure. Error code is printed to
log file.
Contact custormer support with the
store log file.
Store-5891-54: Can not delete
repository from s repository
Store can not delete reduced-fd
repository from disk. Error oc-
curred during the submission of
delete requests of the messages
that belong to repository being
deleted to the thread responsible
for deleting messages from the
disk.
Contact customer support with
store log file.
Store-5891-55: Can not delete half
constructed repository
This error is reported when a
reduced-fd repository is being
deleted. The function that deletes
a part of the repository resources
has been called in a wrong state,
i.e. the function must have been
asked to clean a resource that
does not exist.
Contact customer support with
store log file.
Store-5891-56: Can not create
msg info for sqn: u msgid: u regid:
u
During the re-start ( following a
crash or shutdown ), while pro-
cessing messages written to disk
for reduced-fd repositories, store
can not allocate memory for hold-
ing message information. System
is low in memory.
The root cause of the low memory
needs to be found, store can not
function in this state.
Store-5891-57: Delete a repository
from s repository failed
Store can not delete reduced-fd
repository from disk. Error oc-
curred during the submission of
delete requests of the messages
that belong to repository being
deleted to the thread responsible
for deleting messages from the
disk.
Contact customer support with
store log file.
9.6 UM Persistent Store Log Messages 247
Store-5891-58: s repository delete
failed
Store can not delete reduced-fd
repository from disk. This error
might have occured during the sub-
mission of delete requests of the
messages that belong to repository
being deleted to the thread respon-
sible for deleting messages from
the disk. This error might also have
occured if the function that deletes
reduced-fd repository in a wrong
state.
Contact customer support with the
store log file.
Store-5891-59: s worker thread
can not commit deletes: err: s
The thread that is responsible for
processing reduced-fd I/O requests
can not delete messages from the
disk. The logged message pro-
vides more information regarding to
nature of the error.
Contact customer support with the
store log file.
Store-5891-5: NULL ptr [s:d] Null pointer detected
Store-5891-6: NULL ptr [s:d] Null pointer detected
Store-5891-7: default thread stack
size is perhaps too small, u bytes.
The IPC receiver has created a
thread for internal processing and
the default stack size is too small.
The size of the default stack size is
dumped and will then be set to a
larger size automatically.
Store-5891-8: reset thread stack
size to u bytes.
The IPC receiver has created a
thread for internal processing and
the default stack size is too small
and is reallocated. This message
reports the new size of the stack.
Store-5892-1: retx thread de-
queued node of unknown type: u
An unexpected internal value was
encountered.
Please contact support.
Store-5892-2: retx thread error
occurred while processing node
type: u, s
An error was encountered while
sending a retransmission or unicast
control message.
Check store machine for over-
subscription.
Store-6007-1: Reclaiming Mes-
sage Event: store "%s" topic "%s"
SRC Session ID u RegID u
display the information on the re-
claimed message: the topic name
and source ID
Store-6007-2: Reclaiming Mes-
sage Event: store "%s" topic "%s"
SRC Session ID u RegID u RCV
Session ID u RegID u
display the information on the re-
claimed message: the topic name
and source ID and receiver IDs
Store-6007-4: unknown type of log-
ging message: type=d
unknown logging messages.
Store-6007-5: [umestore
repository] reclamation apply←-
_criteria() failed.
errors occur when applying the cri-
teria to log reclaimed messages
Store-6034-11: queue "%s" client
re-create error: client reg ID x could
not be re-created
A client could not be re-created
upon reading a context registration
event from the SINC log. Some-
thing probably went really wrong -
malloc failed, etc.
Contact Informatica support.
Store-6034-3: queue "%s" receiver
registration error: topic "%s" could
not create receiver
A UMQ receiver could not be cre-
ated - this probably means malloc
failed or something else went terri-
bly wrong.
Contact Informatica support.
248 UM Log Messages
Store-6034-4: could not create
queue SID ctlr
The UMQ session ID controller
could not be created; this probably
means malloc failed.
Contact Informatica support.
Store-6034-5: queue "%s" log read
RCV REG topic RCR_IDX x un-
known
A receiver registration event was
read in from the SINC log file that is
for a topic that is not currently con-
figured in the queue.
Did the configured topics change
in between runs of the queue?
Changing queue configuration in
between runs without clearing out
old SINC log files is not supported.
If configured topics did not change,
contact Informatica support.
Store-6034-6: queue "%s" receiver
recreate error: registration ID not
found
A receiver registration event was
read in from the SINC log file with-
out a corresponding initial client
registration - most likely the SINC
log file is corrupt.
Contact Informatica support.
Store-6034-7: queue "%s" receiver
re-create error: topic "%s" receiver-
type ID u not understood
A receiver registration event was
read in from the SINC log file that
is for a receiver type ID that is not
currently configured in the queue.
Did the configured receiver type I←-
Ds change in between runs of the
queue? Changing queue config-
uration in between runs without
clearing out old SINC log files is not
supported. If configured receiver
type IDs did not change, contact In-
formatica support.
Store-6034-8: queue "%s" receiver
re-create error: topic "%s" receiver
assign ID x could not be re-created
A receiver could not be re-created
upon reading a receiver registration
event from the SINC log. Some-
thing probably went really wrong -
malloc failed, etc.
Contact Informatica support.
Store-6199-1: ldb disp thread de-
queued node of unknown type: u
An unexpected internal value was
encountered.
Please contact support.
Store-6199-2: ldb disp thread er-
ror occurred while processing node
type: u, s
An error was encountered while
sending stability ack or retransmis-
sion
Check store machine for oversub-
scription.
Store-6199-3: lbm_shutdown_←-
log: WFSO res=d, GLE=d
An unexpected error encountered
while shutdown
Contact support
Store-6233-1: Store p "%s" read
error: message with id u does not
exist.
An asynchronous reduced-fd repo
read error occurred because the
message could not be found.
Store-6233-2: Store p "%s" read
error: message had an unexpected
length.
An asynchronous reduced-fd repo
error occurred because the mes-
sage had an unexpected length.
Store-6233-3: Store p "%s" generic
read error.
An asynchronous reduced-fd repo
generic read error occurred.
Store-6233-4: Store p "%s" un-
known asynchronous read error (u)
An asychronous reduced-fd repo
read reported an unknown error
code, possible memory corruption
or garbage pointer.
Store-6241-3: error occurred while
evaluating message selector s
An error occurred while evaluating
the message selector during as-
signment for this receiver and mes-
sage
Look for previous error messages
in the log regarding message se-
lector evaluation problems
Store-6246-100: Store "%s" topic
"%s" SRC Session ID u RegID u
registering with an invalid ume_←-
flightsz_bytes value.
registration with invalid ume_←-
flightsz_bytes value
check config
9.6 UM Persistent Store Log Messages 249
Store-6246-1: Store "%s" topic
"%s" SRC Session ID u RegID u re-
registering with a different ume_←-
flightsz_bytes value.
reregistration with invalid ume_←-
flightsz_bytes value
cannot change config values and
re-register
Store-6246-2000: store "%s" topic
"%s" source SesnID 0xx RegID u
repository-size-threshold is greater
than repository-size-limit
Repository size threshold is greater
than repository size limit
Check config
Store-6246-200: store "%s" topic
"%s" source SesnID 0xx RegID u
registering with an invalid ume_←-
repository_size_threshold value.
Reregistration with invalid ume_←-
repository_size_threshold value
Check config
Store-6246-2100: store "%s" topic
"%s" source SesnID 0xx Reg←-
ID u repository-size-limit is greater
than 90% of repository-disk-file-
size-limit
Repository size limi tis greather
than 90% repository disk file size
limit
Check config
Store-6246-2200: store "%s" topic
"%s" source SesnID 0xx Reg←-
ID u registering and trying to
set the ume_repository_disk_file←-
_size_limit when the repository is
not a disk repository.
Reregistration with disk file size
limit when repo is memory
Check config
Store-6246-22: store "%s" topic
"%s" source SesnID 0xx Reg←-
ID u reregistering and trying to
set the ume_repository_disk_file←-
_size_limit when the repository is
not a disk repository.
Reregistration with ume_←-
repository_size_threshold value
but not a disk store
Cannot change config values and
reregister
Store-6246-2: Store "%s" topic
"%s" SRC Session ID u RegID u
registering as a rpp source but rpp
is not allowed.
rpp source registering to a non-rpp
repo.
check configs.
Store-6246-3000: store "%s" topic
"%s" source SesnID 0xx RegID u
repository-size-threshold must be
greater than the ume_flight_size
Repository size threshold less than
flight size in bytes
Check config
Store-6246-300: Store "%s" topic
"%s" SRC Session ID u RegID u
registering with an invalid ume_←-
repository_size_limit value.
registration with invalid ume_←-
repository_size_limit value
check config
Store-6246-3: Store "%s" topic
"%s" SRC Session ID u RegID u re-
registering with a different ume_←-
repository_size_limit value.
reregistration with invalid ume_←-
repository_size_limit value
cannot change config values and
re-register
Store-6246-400: Store "%s" topic
"%s" SRC Session ID u RegID u
registering with an invalid ume←-
_repository_disk_file_size_limit
value.
registering with invalid ume←-
_repository_disk_file_size_limit
value
check config
Store-6246-4: Store "%s" topic
"%s" SRC Session ID u Reg←-
ID u re-registering with a dif-
ferent ume_repository_disk_file_←-
size_limit value.
reregistration with invalid ume←-
_repository_disk_file_size_limit
value
cannot change config values and
re-register
250 UM Log Messages
Store-6246-500: Store "%s" topic
"%s" SRC Session ID u RegID u
registering with an invalid ume_←-
write_delay value.
registering with invalid ume_write←-
_delay value
check config
Store-6246-5: Store "%s" topic
"%s" SRC Session ID u RegID u re-
registering with a different ume_←-
write_delay value.
reregistering with invalid ume_←-
write_delay value
cannot change config values and
re-register
Store-6246-600: Store "%s" topic
"%s" SRC Session ID u Reg←-
ID u registering with an invalid
ume_repository_ack_on_reception
value.
registering with an invalid ume_←-
repository_ack_on_reception value
check config
Store-6246-6: Store "%s" topic
"%s" SRC Session ID u Reg←-
ID u re-registering with a dif-
ferent ume_repository_ack_on_←-
reception value.
reregistering with invalid ume_←-
repository_ack_on_reception value
cannot change config values and
re-register
Store-6246-700: store "%s" topic
"%s" source SesnID 0xx RegID u
registering with an unknown config-
uration option "%s".
Reregistration with unknown config
options
Version mismatch
Store-6246-7: Store "%s" topic
"%s" SRC Session ID u RegID u
registering with an unknown config-
uration option "%s".
registering with an unknown config-
uration option
version mismatch
Store-6246-8: store "%s" topic
"%s" source SesnID 0xx RegID u
registering with as a RPP source
but RPP is not allowed.
Registering as RPP but RPP is not
allowed
Check configs
Store-6246-900: Store "%s" topic
"%s" SRC Session ID u RegID u
registering with an invalid ume_←-
repository_size_threshold value.
registration with invalid ume_←-
repository_size_threshold value
check config
Store-6246-9: Store "%s" topic
"%s" SRC Session ID u RegID u
re-registering with a differnt ume←-
_repository_size_threshold value.
reregistration with invalid ume_←-
repository_size_threshold value
cannot change config values and
re-register
Store-6254-0001: queue "%s" re-
ceived message list request with
message selector string, but can
not create message selector ob-
ject.
can not create internal msg selec-
tor object.
Store-6298-10: Store "%s" SRC
Session ID u RegID u deregistered
s.u
source has deregistered source deregistered
Store-6298-11: Store "%s" at-
tempting to deregister a SRC Ses-
sion ID u RegID u that has already
deregistered
source is trying to deregister even
though it was already deregistered
preg response for deregistration
may have been lost.
Store-6298-12: Store "%s" RCV
Session ID u RegID u deregistered
s.u
receiver is deregistering receiver has deregistered
9.6 UM Persistent Store Log Messages 251
Store-6298-13: Store "%s" at-
tempting to deregister a RCV Ses-
sion ID u RegID u that has already
deregistered
a deregistered receiver is trying to
deregister
preg response for deregistration
may have been lost.
Store-6298-14: Store "%s" at-
tempting to deregister a client Ses-
sion ID u RegID u that does not ex-
ist
deregistering something that does
not exist
a client is attempting to deregister
even after it's lifetime / activity time-
out has expired.
Store-6300-1: Store "%s" Non-R←-
PP receiver attempting to register
to a RPP topic
non-RPP receiver registering to a
rpp topic
check receiver config and turn on
rpp
Store-6301-1: Store "%s" topic
"%s" SRC Session ID u RegID u
re-registering as a normal source
when it was previously registered
as a rpp source.
spp source re-registering when
previously registered as rpp
turn on rpp at the source
Store-6301-2: Store "%s" topic
"%s" RPP SRC Session ID u Reg←-
ID u re-registering when previously
registered as a non-rpp source.
rpp source re-registering when pre-
viously registered as spp
turn off rpp at the source
Store-6318-4: Unmap error: s An operating system error was
encountered when attempting to
clean up the state file mapping
Check the log message for the sys-
tem error code and investigate fur-
ther.
Store-6353-1: store "%s" Original
Receiver Paced Persistence (RPP)
receiver attempting to re-register to
a RPP topic as a non-RPP receiver
A receiver that has registered as an
RPP receiver is currently attempt-
ing to re-register as a non-RPP re-
ceiver. This is not allowed.
The receiver is misconfigured.
Store-6356-1: store "%s" topic
"%s" Proxy creation failed to set re-
ceiver paced persistence options, s
An error occurred setting receiver
paced options on proxy source at-
tributes which are required for reg-
istration. Proxy source cannot be
created.
Check error message for exact
cause and consult the configuration
guide.
Store-6375-1: Can not commit the
special delete request
Key value worker thread can not
commit the special delete request
Store-6375-2: Can not commit the
special delete request
Key value worker thread can not
commit the special delete request
Store-6375-3: s worker thread can
not commit the special delete re-
quest err_code: u
A message belongs to reduced-fd
repository can not be deleted from
the disk.
The error code in this log message
provides more information regard-
ing to why message can not be
deleted. Contact customer support
with the store log file.
Store-6375-4: s worker thread can
not commit the special delete re-
quest err: s
A message belongs to reduced-fd
repository can not be deleted from
the disk.
The error code ( followed by err:)
in this log message provides more
information regarding to why mes-
sage can not be deleted. Contact
customer support with the store log
file.
Store-6395-116: Ack adjustment
failed
In a reduced-fd RPP repository,
during the re-start( following a shut-
down, or crash), the function that
calculates, for each message in the
repository, number of receivers that
need that message failed.
Contact customer support with the
log file.
252 UM Log Messages
Store-6397-1: store "%s" source
Session ID u [RegID u] [s repo]
[message-sqn x] CKSUM failed
x[cksum on recovered msg]
During the re-start ( following
crash, or a re-start), for a reduced-
fd repository message read from
the disk, checksum failed. Mes-
sage must have been corrupted.
Contact customer support with the
store log file.
Store-6397-2: Repository check-
sum check function failed on src
regid: u
The function resposible for check
sum processing is called in a wrong
state, i.e., one or many of the re-
source are missing (NULL). The
checksum of the messages is not
checked.
Contact customer support with the
store log file.
Store-6417-2: INFO: Store "%s"
could not open existing cache file
[s]
The store can not open repository
cache file. The file might have been
deleted, or for some other reason
store can not open it.
Contact customer support with the
store log file, and list of files in state
and cache directory.
Store-6417-3: Can not find the max
sqn of rcv [regid: u]
The function that is responsible for
finding maximum sequence num-
ber of the current receivers failed.
Contact customer support with the
store log file.
Store-6417-4: Repo:u has no mes-
sages on disk, and sqn adjustment
failed
During the re-start ( following shut-
down, or crash), sequence num-
ber adjustment of empty repository
failed. Note that, in RPP mode,
if all the receivers are keeping up
with the source, repository can be
empty.
This error message is preceded
with other related error messages.
Contact customer support with the
store log file.
Store-6417-5: could not initialize s
repository: s
Reduced-fd subsystem can not be
initialized.
This error message is preceded
with other related error messages.
Contact customer support with the
store log file.
Store-6417-6: INFO: Store
"%s"cache file [s] exist, and
repo is marked as reduced fd repo
in state file. invalid repo state
Inconsistent state has been de-
tected. For a particular reposi-
tory, there is cache file, and the
repository is marked as reduced-fd
repository.
Contact customer support with
store log file, and the list of files in
state and cache directory.
Store-6417-7: INFO: Store "%s"
RegID: u triggered late reduced-fd
system initialization
This is an information message.
Late initialization is triggered when
a configuration file is changed such
that all the reduced-fd repositories
are deleted or changed to disk. If
there is a state file for the reposi-
tories whose type is changed from
reduced-fd to disk, then original
repository type–reduced-fd– is en-
forced, and late initialization is trig-
gered.
Remove the disk cache file or re-
store the configured repository type
to reduced-fd
Store-6425-1: store "%s" Session
ID u RegID u Configured repo
type: u is different than the original
type: u Forcing the original type
During the restart (following crash
or shutdown), a repository type is
changed, however, this is not al-
lowed before the source deregistra-
tion. Store is going to enforce orig-
inal repository type.
Remove the store's state and
cache files or restore the config-
ured repository type to the original
value.
Store-6492-1: Store "%s" topic
"%s" SRC Session ID u Reg←-
ID u registering and trying to
set the ume_repository_disk_file←-
_size_limit when the repository is
not a disk or reduced_fd repository.
registration setting disk size limit
when you aren't a disk or a
reduced_fd store
Check configuration.
9.6 UM Persistent Store Log Messages 253
Store-6492-2: Store "%s" topic
"%s" SRC Session ID u Reg←-
ID u registering and trying to
set the ume_repository_disk_file←-
_size_limit when the repository is
not a disk or reduced_fd repository.
registration setting disk size limit
when you aren't a disk or a
reduced_fd store
Check configuration.
Store-6492-3: Store "%s" topic
"%s" SRC Session ID u RegID u
repository-size-threshold is greater
than repository-size-limit
Repository size threshold is greater
than repository size limit
Check config
Store-6492-4: Store "%s" topic
"%s" SRC Session ID u RegID u
repository-size-limit is greater than
90%% of repository-disk-file-size-
limit
Repository size limit is greater than
90% repository disk file size limit
Check config
Store-6492-5: Store "%s" topic
"%s" SRC Session ID u RegID u
repository-size-threshold must be
greater than ume_flight_size_bytes
Repository size threshold less than
flight size in bytes
Check config
Store-6524-1: msg_size_on_disk
is called for a unrecoverable lost
sqn: u
The function that calculates the
message size in disk for reduced-
fd repositories is called for a loss
message. Function handles the
case correctly, however, this func-
tion is not supposed to be called for
the loss messages.
Contact customer support.
Store-6543-1: could not lseek
cache file RegID u: s
During the creation of repository
cache file, system call to change
the file offset to the beginning of the
cache file failed.
Contact customer support
Store-6543-2: could not write
cache file RegID u: s
During the creation of repository
cache file, special marker can not
be written to the cache file.
Contact customer support
Store-6557-1: store "%s" source
SesnID 0xx RegID u Re-←-
Registered and moved to Indices
u.u [s.u] RPP
RPP source reregistered RPP source reregistered
Store-6557-2: store "%s" receiver
SesnID 0xx RegID u Re-←-
Registered and moved to Indices
u.u [s.u] RPP
RPP receiver re-registered RPP receiver re-registered
Store-6589-2: WARNING: msync
EIO from umestore_state_←-
update_rcv_timers
write all modified data to the disk.
Store-6607-1: queue "%s" ob-
server receiver registration error←-
: topic "%s" could not create ob-
server receiver
A UMQ observer receiver could not
be created - this probably means
malloc failed or something else
went terribly wrong.
Contact Informatica support.
Store-6607-2: queue "%s" receiver
registration error: assign ID 0xx
could not re-create receiver
A UMQ receiver could not be re-
created - this probably means mal-
loc failed or something else went
terribly wrong.
Contact Informatica support.
Store-6620-1: INFO: Could not re-
name file [s] to [s]: s
The system failed to rename a cor-
rupted cache or state file.
Review the system error string and
resolve the system issue before
restarting the store.
254 UM Log Messages
Store-6652-1: umestore_retx_←-
timer_check : retx_ctrl is not allo-
cated
Retransmission Control Structure
is not allocated
View Store log for errors
Store-6807-1: lbm_shutdown_←-
log: WFSO res=d, GLE=d
An error was encountered while
Shutting Down Umestore
Check store log of other errors
Store-6975-1: source registered
with zero RegID or no store infor-
mation was found - proxy source
disabled
A source attempted to register to
a store with proxy sources enabled
but did not have explicit registration
IDs or session IDs enabled, or did
not send store configuration infor-
mation with the registration.
Check the source to make sure reg-
istration IDs or session IDs are ex-
plicitly specified, or check that com-
patible versions of source and store
applications are used.
Store-7000-1: lbm_context_attr_←-
str_setopt - context_name: s
Failed to set the context name on
the main store context.
Check for resource exhaustion, out
of memory errors, etc.
Store-7000-2: lbm_context_attr_←-
str_setopt - context_name: s
Failed to set the context name on
the proxy store context.
Check for resource exhaustion, out
of memory errors, etc.
Store-7046-1: store "%s" topic
"%s" transport s tidx u SesnID 0xx
RegID u RA
A repository has gained associa-
tion (RA) with a source and will now
retain that source's messages.
None
Store-7049-2: NOTICE: store "%s"
topic "%s" SRC Session ID u Reg←-
ID u sqn u reported as unrecover-
ably lost via normal transport, but
was successfully received earlier
via retransmission
A message fragment was declared
unrecoverably lost by the store's
receiver's underlying delivery con-
troller, but the fragment was al-
ready previously recovered (proba-
bly by proactive retransmission).
Check for data loss on the source's
transport between the source and
the store. This message indicates
that the store did actually receive
the message data (it did NOT lose
it), it just didn't do so through the
preferred means.
Store-7049-3: Store "%s" received
retransmission of SQN: u for SRC
RegID u from s
The UMP store received a unicast
proactive retransmission.
This probably indicates loss of ei-
ther the message data from the
source to the store, or of stability
ACKs from the store to the source.
Sources of loss should be investi-
gated.
Store-7216-1: For: s queue-
management-join-request-timeout
[u] can not be less than twice
the queue-management-master-
activity-timeout [u]. Overriding
queue-management-join-request-
timeout value to u
queue-management-join-request-
timeout is configured less than its
minimum value, i.e. 2 x queue-
management-master-activity-
timeout, this configuration can lead
to multiple master queues.
Configure queue-management-
join-request-timeout value
greater than twice the queue-
management-master-activity-
timeout.
Store-7239-1: Store "%s" [ Source
Session ID u Source RegID u
Receiver Session ID: u Receiver
RegID: u ] failed to define
Store can not assign receiver its
previous RegID. This can happen
(i) State file corruption leads to ear-
lier assignment of receiver's RegID
(ii) Memory error
Contact customer support
Store-7239-2: Store "%s" can not
re-create Receiver [ Session ID: u
RegID u ] for Source [ Session ID u
RegID u]
Store can not recreate a receiver
due to a memory error from state
file.
Contact customer support
Store-7256-1: Store "%s" source
RegID u Keepalive ignored, client
invalid
The store received a keepalive that
could not be associated with a
source or receiver client
This may indicate some internal
errors regarding managing source
and receiver clients.
Store-7256-2: LBMC Error han-
dling registration request. s
There was an error handling a per-
sistent registration request at the
store
Look in the store log for previous
errors that might indicate why this
would fail.
Store-7256-3: LBMC Error han-
dling retransmit request. s
There was an error handling a re-
transmit request at the store
Look in the store log for previous
errors that might indicate why this
would fail.
9.6 UM Persistent Store Log Messages 255
Store-7256-4: LBMC Error han-
dling acknowledgment. s
There was an error handling a mes-
sage acknowledgment at the store
Look in the store log for previous
errors that might indicate why this
would fail.
Store-7256-5: LBMC Error han-
dling keepalive. s
There was an error handling a
source or receiver keepalive at the
store
Look in the store log for previous
errors that might indicate why this
would fail.
Store-7297-1: store "%s" topic
"%s" Received proxy source PR←-
EG from self with invalid topic and
transport indicies, ignoring.
A PREG request from a proxy
source was received with an elec-
tion token matching the proxy
source hosted by this store. This
PREG request is ignored.
This can occur if the store con-
text thread has fallen behind in pro-
cessing incoming PREG requests
from the socket buffer, to the point
where the store is processing PR←-
EG requests for proxy sources that
no longer exist. Take steps to re-
duce the load on the store such
as reducing the number of sources
registered.
Store-8000-100: store [s] PREG
marker 0xx RegID u Session ID u
Indices u.u [s.d] StoreID x L/T <d -
d>s
A Source registered with the store. No Further action is required.
Store-8000-101: store [s] PREG
marker 0xx RegID u Session ID u
idx u.u [s.d] StoreID x L/T <d - d>
s
A Receiver registered with the
store.
No further action is required.
Store-8079-10: Starting store "%s" Beginning the initialization process
for the named store.
This is for informational purposes
only and can be ignored.
Store-8079-1: Created context
thread: id[s]
The store created a context with
the reported thread id.
This is for informational purposes
only and can be ignored.
Store-8079-2: Created proxy con-
text thread: id[s]
The store created a proxy context
with the reported thread id.
This is for informational purposes
only and can be ignored.
Store-8079-3: Created retransmis-
sion thread: id[s]
The store created the retrans-
mission thread with the reported
thread id.
This is for informational purposes
only and can be ignored.
Store-8079-4: Created the log of-
fload thread: id[s]
The store created the log offload
thread with the reported thread id.
This is for informational purposes
only and can be ignored.
Store-8079-5: Created blocked io
thread: id[s]
The store created the blocked io
thread with the reported thread id.
This is for informational purposes
only and can be ignored.
Store-8079-6: Created level db
thread: id[s]
The store created the level db dis-
patcher thread with the reported
thread id.
This is for informational purposes
only and can be ignored.
Store-8079-7: Created proactor
thread: id[s]
The store created the proactor
thread with the reported thread id.
This is for informational purposes
only and can be ignored.
Store-8079-8: Created reduced-fd
I/O thread: id[s]
The store created the reduced-fd
I/O thread with the reported thread
id.
This is for informational purposes
only and can be ignored.
Store-8079-9: Created umq send
thread: id[s]
The store created a umq send
thread with the reported thread id.
This is for informational purposes
only and can be ignored.
Store-8106-1: Store "%s" using
port u from range context request←-
_tcp_port_low (u) - request_tcp_←-
port_high (u).
User specified 0 for the store port.
This means that it will be started
on a port selected from within
the context request_tcp_port_low -
request_tcp_port_high range.
Normal operation, no action
needed.
256 UM Log Messages
Store-8192-1: store "%s" Origi-
nal Source Paced Persistence(←-
SPP) receiver attempting to re-
register to a non-RPP topic as a
RPP receiver
A receiver that has registered as an
non-RPP receiver is currently at-
tempting to re-register as an RPP
receiver. This is not allowed.
The receiver is misconfigured.
Store-8192-2: store "%s" Orig-
inal blocking Receiver Paced
Persistence(RPP) receiver at-
tempting to re-register as a
non-blocking RPP receiver
A receiver that has registered as a
blocking RPP receiver is currently
attempting to re-register as a non-
blocking RPP receiver. This is not
allowed.
The receiver is misconfigured.
Store-8192-3: store "%s" Origi-
nal non-blocking Receiver Paced
Persistence(RPP) receiver at-
tempting to re-register as a
blocking RPP receiver
A receiver that has registered as an
non-blocking RPP receiver is cur-
rently attempting to re-register as a
blocking RPP receiver. This is not
allowed.
The receiver is misconfigured.
Store-8223-1: Could not add new
regid x to ctlr: s
The store was unable to add a new
source to its list of clients.
Typically this message indicates
that something else has gone
wrong previously. Check for addi-
tional error messages.
Store-8223-2: Could not create A←-
SL: s
The store was unable to create a
client list for a source.
Typically this message indicates
that something else has gone
wrong previously. Check for errors
indicating that the system is out of
memory.
Store-8223-3: Could not create
add new topic entry for regid d: s
The store was unable to create a
new entry for a source.
Typically this message indicates
that something else has gone
wrong previously. Check for errors
indicating that the system is out of
memory.
Store-8223-4: Set RegID seed to u The next RegID the store will as-
sign has been set to the specified
value.
This is purely an informational mes-
sage, and requires no action on the
user's part.
Store-8223-5: Reset RegID seed
to u
The next RegID the store will as-
sign has been set to the specified
value.
This is purely an informational mes-
sage, and requires no action on the
user's part.
Store-8223-6: Could not cleanly
unwind client p when attempting
source registration.
The store was unable to clean up
after a source failed to register.
Typically this message indicates
that something else has gone
wrong previously. Check for previ-
ous error messages.
Store-8269-1: lbm_context_attr←-
_setopt - compatibility_include_←-
pre_um_6_0_behavior: s
Failed to turn off pre 6.0 compatibil-
ity mode on the proxy store context.
Check for resource exhaustion, out
of memory errors, etc.
Store-8269-2: store "%s" topic
"%s" proxy creation failed to set
transport_tcp_use_session_id 0: s
An error occurred setting
transport_tcp_use_session_id
for a proxy source being created
with pre 6.0 compatibility enabled.
Check the error message for exact
cause and consult the configuration
guide
Store-8764-1: Store "%s" failed to
register source: s
A source attempted to register, but
an error occurred while trying to
add it to the store's list of known
clients.
Check for included log message for
details.
Store-8808-1: settings other than
1 for repository-disk-max-write-
async-cbs are no longer allowed
due to the possibility of data cor-
ruption. Ignoring requested value
of d
Multiple outstanding async IO call-
backs have been found to cause
cache file corruption in some cases
and are no longer allowed as a re-
sult.
Change the store's XML config-
uration file to specify a value
of 1 for repository-disk-max-write-
async-cbs .
9.6 UM Persistent Store Log Messages 257
Store-9115-01: store "%s" topic
"%s" source [s] BOS
Informational message indicating
that a BOS has been received on
the given topic and source.
No action required.
Store-9115-02: store "%s" topic
"%s" source [s] Session ID u RegID
u SRI
Informational message indicating
that a source has completed regis-
tration with the store.
No action required.
Store-9115-03: store "%s" topic
"%s" source [s] Session ID u RegID
u EOS
Informational message indicating
that an EOS has been received on
the given topic and source.
No action required.
Store-9302-1: Store "%s": Existing
state file [s] in use by another pro-
cess
The existing state file is locked by
another process
Ensure that other store processes
are not running with the same con-
figured state and cache directories.
Store-9302-2: Store "%s": Existing
cache file [s] in use by another pro-
cess
The existing cache file is locked by
another process
Ensure that other store processes
are not running with the same con-
figured state and cache directories.
Store-9462-1: Received Keepalive
Message that is not type STO←-
RE : [s:u] Originating Domain : u
Keepalive Type : d
The store received a Keepalive re-
quest, but of a type that was not ex-
pected. The message written to the
log includes the originating domain
id, the Keepalive type, and the IP
address and port of the requester.
Normally, this message can be ig-
nored as the UMP Store is logging
the existence of a stray keepalive.
However, if this is a recurring mes-
sage, examine the IP and port to
determine the source of the unex-
pected Keepalive request.
Store-9462-2: Received Keepalive
Message that is not type STORE :
[s:u] Keepalive Type : d
The store received a Keepalive re-
quest, but of a type that was not ex-
pected. The message written to the
log includes the Keepalive type as
well as the IP address and port of
the requester.
Normally, this message can be ig-
nored as the UMP Store is logging
the existence of a stray keepalive.
However, if this is a recurring mes-
sage, examine the IP and port to
determine the source of the unex-
pected Keepalive request.
Store-9462-3: Received Keepalive
Message that is not type STORE :
[s:u] Keepalive Type : d
The store received a Keepalive re-
quest, but of a type that was not ex-
pected. The message written to the
log includes the Keepalive type as
well as the IP address and port of
the requester.
Normally, this message can be ig-
nored as the UMP Store is logging
the existence of a stray keepalive.
However, if this is a recurring mes-
sage, examine the IP and port to
determine the source of the unex-
pected Keepalive request.
Store-9462-4: Received Keepalive
Message that is not type STO←-
RE : Source of Keepalive Message
could not be determined Keepalive
Type : d
The store received a Keepalive re-
quest, but of a type that was not
expected. The message written
to the log includes the Keepalive
type. The requester IP and port are
not available and, consequently, re-
quest IP and port will not be written
to the log.
For this unexpected Keepalive re-
quest the source of the message
could not be determined.
Store-9689-1: Default application
specified for LBM XML configura-
tion file [s]
The application name for XML con-
figuration files was set to NULL.
Log notification that NULL applica-
tion name will be used
Store-9689-2: LBM XML config-
uration file [s] specified, but no
application-name provided. Setting
application name to "umestored"
The application name for XML con-
figuration files defaults to "ume-
stored" .
Specify the optional "application-
name" sub-configuration to refer-
ence a different application in the
XML file
Store-9753-01: Store "%s" leveldb
delete event failed with return: d
repo->trail_sqn: u repo->mem_←-
trail_sqn: u
An attempt to delete messages
from the LevelDB store repository
failed.
Contact customer support with the
log file.
258 UM Log Messages
StoreApi-10184-01: could not cre-
ate dmon event queue
UM could not create an dmon event
queue.
Contact Informatica Support.
StoreApi-10184-02: could not cre-
ate store list
UM could not create a list of config-
ured stores.
Contact Informatica Support.
StoreApi-10184-03: failed to create
dmon evq thread [d]
UM failed to create an internal
event queue dispatch thread.
Contact Informatica Support.
StoreApi-10184-04: failed to create
dmon ctx attr: s
UM was unable to create context
attributes.
Contact Informatica Support.
StoreApi-10184-06: failed to create
dmon ctx: s
UM was unable to create an inter-
nal reactor only context.
Contact Informatica Support.
StoreApi-10184-07: unable to
schedule dmon timer
UM was unable to schedule an in-
ternal timer.
Contact Informatica Support.
StoreApi-10184-09: unable to
schedule dmon timer
UM failed to schedule an internal
timer.
Contact Informatica Support
StoreApi-10184-107: failed to set
dmon context option [operational←-
_mode] to [embedded]: s
UM was unable to set speci-
fied daemon monitoring context at-
tributes.
Contact Informatica Support.
StoreApi-10184-112: could not en-
queue disk delete
UM could not enqueue disk delete. Contact Informatica Support.
StoreApi-10184-143: could not cre-
ate repo dmon block receiver list
UM could not create repo dmon
block receiver list.
Contact Informatica Support.
StoreApi-10184-30: could not cre-
ate topic dmon block repo list
UM could not create topic dmon
block repo list.
Contact Informatica Support.
StoreApi-10184-31: could not in-
sert topic block into store topic list
UM could not insert topic block into
store topic list.
Contact Informatica Support.
StoreApi-10184-32: could not
delete repo
UM could not delete repo because
the receive list was not empty.
Contact Informatica Support.
StoreApi-10184-33: could not in-
sert receive dmon block into re-
ceive list
UM could not insert receive dmon
block into receive list.
Contact Informatica Support.
StoreApi-10184-34: attempted to
delete an invalid repository dmon
block
UM attempted to delete an invalid
repository dmon block.
Contact Informatica Support.
StoreApi-10184-35: could not find
receiver regid to delete
UM could not find receiver regid to
delete.
Contact Informatica Support.
StoreApi-10184-40: could not in-
sert store dmon into store list
UM could not insert store dmon into
store list.
Contact Informatica Support.
StoreApi-10184-41: could not
delete store dmon block
UM could not delete store dmon
block since the topic_list was not
empty.
Contact Informatica Support.
StoreApi-10184-43: could not cre-
ate repo dmon block receiver list
UM could not create repo dmon
block receiver list.
Contact Informatica Support.
StoreApi-10184-44: could not en-
queue repo create
UM could not enqueue repo create. Contact Informatica Support.
StoreApi-10184-45: could not en-
queue repo delete
UM could not enqueue rcv delete. Contact Informatica Support.
StoreApi-10184-47: could not en-
queue rcv create
UM could not enqueue rcv create. Contact Informatica Support.
StoreApi-10184-48: could not en-
queue rcv delete
UM could not enqueue rcv delete. Contact Informatica Support.
StoreApi-5867-10: error occurred
parsing message selector string
<s>
The message selector string is in-
valid or could not be parsed.
Please check the UM Documenta-
tion for valid syntax.
9.6 UM Persistent Store Log Messages 259
StoreApi-5867-11: parsing error
occurred while updating the mes-
sage selector with string <s>
The message selector string is in-
valid or could not be parsed.
Please check the UM Documenta-
tion for valid syntax.
StoreApi-5867-12: parsing error
occurred while creating a message
selector with string <s>
The message selector string is in-
valid or could not be parsed.
Please check the UM Documenta-
tion for valid syntax.
StoreApi-5867-6: could not in-
sert umq_topic_appset_t skipped
rcv list ASL [s:d]
An internal error occurred during
ASL insertion
Look for previous error messages
in the log such as a malloc error
StoreApi-5867-7: could not in-
sert umq_topic_appset_t skipped
rcv list ASL [s:d]
An internal error occurred during
ASL insertion
Look for previous error messages
in the log such as a malloc error
StoreApi-5891-10: could not create
recovery asl
Memory error during the ASL cre-
ation
StoreApi-5891-11: could not create
repo ASL
Memory error: repository message
asl creation is failed
StoreApi-5891-19: Repository
async read submit error
There was an error submitting an
async read operation to the queue.
This usually results from malloc
failure, ensure host machine has
sufficient resources.
StoreApi-5891-1: could not create
tl queue [s:d]
Key value repo worker thread's
queue creation failed
StoreApi-5891-28: umestore_←-
state_new_rcv re-opening state file
failed. s
Can not re-open state file
StoreApi-5891-29: umestore_←-
state_new_rcv closing fd after re-
opening failed. s
Can not close the file descriptor af-
ter reopening it.
StoreApi-5891-37: could not create
repo ASL
Memory error: repository message
asl creation is failed
StoreApi-5891-3: could not allo-
cate u bytes [s:d]
MALLOC error
StoreApi-5891-53: could not create
repo rcv_ack_cache
Repo rcv ack cache creation failed
StoreApi-5891-60: umestore_←-
state_create closing fd failed: s
Can not close the file descriptor
StoreApi-5891-9: pthread_create←-
: d
Key value repo worker thread cre-
ation failed
StoreApi-6007-12: could not create
repo log
some errors occurred when creat-
ing the reclamation log.
StoreApi-6034-10: could not in-
sert umq_topic_rcv_t into appset
active_rcv_assign_q [s:d]
A UMQ receiver could not be
placed in an application set's inter-
nal list of receivers with non-empty
per-receiver assignment queues.
This probably means malloc failed.
Contact Informatica support.
StoreApi-6034-9: could not create
receiver assign_q [s:d]
The per-receiver assignment
queue could not be created - this
probably means malloc failed.
Contact Informatica support.
StoreApi-6118-100: could not cre-
ate repo rcv_ack_cache
Could not create rcv ack cache out of memory
StoreApi-6318-1: Failed to unmap
file. System error (d)
The operating system call to un-
map the state file returned an error.
Check the system error code and
determine why it would happen
StoreApi-6318-2: Failed to close
state file mapping handle. System
error (d)
The operating system call to close
the state file mapping handle re-
turned an error.
Check the system error code and
determine why it would happen
260 UM Log Messages
StoreApi-6318-3: Failed to unmap
state file. System error (d)
The operating system call to un-
map the state file returned an error.
Check the system error code and
determine why it would happen
StoreApi-6333-1: Attempting to
delete NULL disk info, file was not
created.
The store was deleting a repository
and the disk info holder was NU←-
LL. There were most likely errors
when the store attempted to create
the disk.
Investigate why the store could not
create the disk info properly. Usu-
ally this occurs when the process
has hit the file descriptor limit.
StoreApi-6333-2: Attempting to
delete NULL state file. State file
was not created.
The store was deleting a repository
and the state file was NULL. There
were most likely errors when the
store attempted to create the file.
Investigate why the store could not
create the state file properly. Usu-
ally this occurs when the process
has hit the file descriptor limit.
StoreApi-6417-1: could not create
repo ASL
Memory error: repository message
asl creation is failed
StoreApi-6543-3: umestore←-
_repository_write_rec_marker
CreateEvent: s
Can not create event for rec marker There is not resolution to this
StoreApi-6543-4: umestore←-
_repository_write_rec_marker:
WriteFile: s
umestore_repository_write_rec_←-
marker: GetLastError Failed
Get last error failed
StoreApi-6543-5: umestore←-
_repository_write_rec_marker
GetOverlappedResult: s
GetOverlappedResult function
failed
no resolution
StoreApi-6589-1: umestore_←-
state_update_rcv_timers Flush←-
ViewOfFile: s
write to disk the mapping view of
the state file.
StoreApi-6589-3: umestore_←-
state_update_rcv_timers msync:
s
write to disk the mapping view of
the state file.
StoreApi-8000-10: . A Receiver Registration request
was denied because of an internal
error.
StoreApi-8000-11: . A Receiver Registration request
was denied because of an internal
error.
Contact customer support with the
log file.
StoreApi-8000-12: . A Receiver Registration request
was denied because of an internal
error.
Contact customer support with the
log file.
StoreApi-8000-13: . A Receiver Registration request
was denied because of an internal
error.
Contact customer support with the
log file.
StoreApi-8000-14: . A Receiver Registration request
was denied because of an internal
error.
Contact customer support with the
log file.
StoreApi-8000-15: . A Receiver Registration request
was denied because of an internal
error.
Contact customer support with the
log file.
StoreApi-8000-1: RegID is already
in use.
A Source Registration request was
denied because the requested
RegID was already in use.
Contact customer support with the
log file.
StoreApi-8000-20: Internal error←-
: re-registration to a NULL receiver.
A Receiver Registration request
was denied because of an internal
error.
Contact customer support with the
log file.
StoreApi-8000-21: Internal error←-
: preg src_reg_id mismatch
A Receiver Registration request
was denied because of an internal
error.
Contact customer support with the
log file.
9.6 UM Persistent Store Log Messages 261
StoreApi-8000-22: Receiver activ-
ity Timeout has not expired.
Registration attempt is rejected be-
cause the receiver activity timeout
has not expired
Another receiver with the same
RegID/sessionID is trying to regis-
ter with the store within the activity
period .
StoreApi-8000-23: . A Receiver Registration request
was denied because of an internal
error.
Contact customer support with the
log file.
StoreApi-8000-24: . A Receiver Registration request
was denied because of an internal
error.
Contact customer support with the
log file.
StoreApi-8000-2: src topic does
not match the info topic.
A Source Registration request was
denied because the src topic does
not match the info topic.
Contact customer support with the
log file.
StoreApi-8000-30: . A Source Registration request was
denied because of an internal error.
Contact customer support with the
log file.
StoreApi-8000-31: . A Source Registration request was
denied because of an internal error.
Contact customer support with the
log file.
StoreApi-8000-32: . A Source Registration request was
denied because of an internal error.
Contact customer support with the
log file.
StoreApi-8000-33: . A Source Registration request was
denied because of an internal error.
Contact customer support with the
log file.
StoreApi-8000-34: . A Source Registration request was
denied because of an internal error.
Contact customer support with the
log file.
StoreApi-8000-35: . A Source Registration request was
denied because of an internal error.
Contact customer support with the
log file.
StoreApi-8000-36: . A Source Registration request was
denied because of an internal error.
Contact customer support with the
log file.
StoreApi-8000-37: . A Source Registration request was
denied because of an internal error.
Contact customer support with the
log file.
StoreApi-8000-38: . A Source Registration request was
denied because of an internal error.
Contact customer support with the
log file.
StoreApi-8000-39: . A Source Registration request was
denied because of an internal error.
Contact customer support with the
log file.
StoreApi-8000-3: Source Activity
timeout has not expired.
A Source Registration request was
denied because the Source Activity
timeout has not yet expired.
Contact customer support with the
log file.
StoreApi-8000-40: . A Source Registration request was
denied because of an internal error.
Contact customer support with the
log file.
StoreApi-8000-41: . A Source Registration request was
denied because of an internal error.
Contact customer support with the
log file.
StoreApi-8000-4: Problem with R←-
PP configs.
A Source Registration request was
denied because of a problem with
the RPP configuration.
Contact customer support with the
log file.
StoreApi-8000-5: . A Source Registration request was
denied because of an internal error.
Contact customer support with the
log file.
StoreApi-8000-6: . A Source Registration request was
denied because of an internal error.
Contact customer support with the
log file.
StoreApi-8000-7: . A Source Registration request was
denied because of an internal error.
Contact customer support with the
log file.
StoreApi-8000-8: . A Source Registration request was
denied because of an internal error.
Contact customer support with the
log file.
262 UM Log Messages
StoreApi-8804-1: umestore_←-
state_update_rcv_timers index
of receiver entry in state file was
negative
The store attempted to update the
activity and state lifetime of a re-
ceiver, but that receiver's entry in-
dex in the state file was negative.
This can be seen when there is a
problem writing or reading the state
file. Check the store log for disk er-
ror log messages.
StoreApi-8840-11: Could not reg-
ister client [x:u] on topic s. RegID
mismatch with [x:u]
A duplicate session ID is in use
between two clients on the same
topic.
Check for duplication session IDs in
application configuration files. Ap-
plications should usually explicitly
specify a session ID rather than re-
lying on the store to generate one.
StoreApi-9569-1: Can't convert
configuration file name [s:d]
The system was not able to allocate
the amount of memory required to
convert the configuration file name.
The physical memory on the ma-
chine may be over committed; try
moving some applications to an-
other machine.
9.7 UMDS Log Messages
Umds-4892-1: Attempt to set use←-
_late_join failed for attrs p err(d)
ERROR: Attempt to turn use_late←-
_join ON in the rcvr attrs failed.
Umds-4892-2: Attempt to set
ume_use_store failed for attrs p
err(d)
ERROR: Attempt to turn ume←-
_use_store ON in the rcvr attrs
failed.
Umds-4892-3: Error creating Topic
Queue: No Hash function found.
FATAL: A hash function is required
to create a Topic Queue. This
is set from the resolver_string_←-
hash_function in the topic queue
map init function.
Check that the Hash function for
Topic Resolution has been set cor-
rectly.
Umds-4892-4: Attempt to get
ume_session_id failed or session
id is zero: lu
ERROR: Trying to create a persis-
tent receiver but the session id is
either zero, or reading the attribute
failed.
Check that session ID sent by the
UMDS client is not zero
Umds-4892-5: Attempt to set
ume_explicit_ack_only failed for at-
trs p err(d)
ERROR: The attempt to set ume←-
_explicit_ack_only (to ON) failed
while creating a persistent receiver.
Umds-5688-5609: umdsd_←-
worker_api_mim_loss_advisory:
worker(p<d>) not running
The indicated worker is not in the
RUNNING state
Contact Informatica support with all
relevant log files
Umds-5688-5617: PCRE exec
[s][s][d] error d
An error occurred while trying to
match the pattern listed in the first
bracketed expression. The topic
string attempting to be matched
is supplied as the second brack-
eted expression, and its length is
supplied as the third bracketed ex-
pression. The error that occurred
was internal to PCRE, and the er-
ror code is listed in the PCRE
documentation for return values of
pcre_exec.
9.7 UMDS Log Messages 263
Umds-6033-635: Ultra Messaging
UMDS server version " UMDS_V←-
ERSION " Build s, s (s)
Reports the version of UMDS, build
time and date, and version of the
underlying UM library.
No resolution, this in formation is
provided for audit and debugging
purposes.
Umds-6033-637: umdsd_main←-
: webmon interface not found (s)
The interface specified for the web
monitor could not be found.
Review the setting in the <web-
monitor>tag in the server's xml
configuration file.
Umds-6033-638: umdsd_main←-
: client interface not found (s)
The interface specified for the client
connections could not be found.
Review the setting for the bind-addr
attribute in the <server>tag in the
server's xml configuration file.
Umds-6033-641: umdsd_main: Er-
ror opening pidfile 's' (s)
Opening (creating) the pid file
failed.
The error message includes the OS
error message associated with the
open attempt. Check that files can
be created in the target directory
and that the device is not full.
Umds-6033-656: umdsd_worker←-
_cont_sending_cntl: sendb header
error (s)
Sending a UMDS Control message
to the client resulted in an UM error.
A description of the UM error is in-
cluded in the message text.
Umds-6033-657: umdsd_worker←-
_cont_sending_data: sendb data
error (s)
Sending on the client socket en-
countered an error.
Included in the message text is a
description of the particular error
encountered.
Umds-6033-664: umdsd_←-
webmon_api_create: failed to init
web server (ip=s, port=s)
The web monitor subsystem failed
to start.
The web server library will have re-
ported additional details to the con-
sole.
Umds-6033-685: s: worker p<d>
connection p<d>invalid conn_←-
state (d)
The indicated state for the client
connection is inappropriate for the
requested operation.
The client connection will be
deleted and if configured, the client
will retry. If this error repeats,
call Informatica support with all
relevant server and client log files.
Umds-6033-705: umdsd_worker←-
_internal_cmd_del_conn: worker
p<d>connection p<d>(s:u)
deleted, bytes_in=lld, bytes_←-
out=lld
The indicated connection has been
deleted
No resolution is required.
Umds-6033-706: umdsd_←-
worker_internal_cmd_mim_loss←-
_advisory: worker(p<d>) not
running
The indicated worker is not in the
RUNNING state
Contact Informatica support with all
relevant log files
Umds-6033-708: umdsd_worker←-
_keepalive_tmr_cb: worker(p<d>)
not running
The indicated worker is not in the
RUNNING state
Contact Informatica support with all
relevant log files
Umds-6033-709: umdsd_worker←-
_keepalive_tmr_cb: send_←-
period=d, disconnecting worker
p<d>connection p<d>
The keep alive state has been PE←-
NDING for too long; it is being dis-
connected as unresponsive.
This can occur if the client appli-
cation is spending long periods of
time in any of the library call back
functions and preventing the client
sid socket from being read.
Umds-6033-710: umdsd_worker←-
_keepalive_tmr_cb: rcv_period=d,
disconnecting worker p<d>con-
nection p<d>
The keep alive timer has expired for
the indicated worker connection; it
is being disconnected as unrespon-
sive.
This can occur if the keep alive
threshold and intervals are not ap-
propriate for the connection or if the
client application is spending long
periods of time in any of the library
call back functions.
Umds-6033-711: umdsd_worker←-
_api_conn_add: worker(p<d>)
not running
The indicated worker is not in the
RUNNING state
Contact Informatica support with all
relevant log files
264 UM Log Messages
Umds-6033-712: umdsd_worker←-
_api_conn_add: worker p<d>
waiting to add new connection
The client request to add a connec-
tion to this worker is still pending.
The main UM context thread is un-
usually busy at this time but will
eventually serve this request.
Umds-6033-715: umdsd_worker←-
_api_delete: quit skipped (ctx=p,
thrd_running=d)
The context or worker thread has
already shutdown
Shutdown is already in progress
Umds-6033-716: umdsd_worker←-
_api_delete: error joining worker
(p<d>) thread (d)
An error occurred joining the
worker thread during shutdown.
It is likely this is a result of multiple
shutdown requests. However if this
error is seen on multiple occasions,
please report it along with any ap-
plicable configuration and log files
to GCS.
Umds-8218-1: s: error: 's', appl_←-
name='s'
The UMDS client failed to authenti-
cate.
Check authentication credentials
and server auth configuration.
Umds-8366-1: Unknown receiver
type deleting umdsd_rcv <p>
An unknown receiver type was en-
countered while deleting a UMDS
receiver object.
This is an internal error and should
be reported to customer support;
please include all appropriate ver-
sion numbers (UM and UMDS), as-
sociated configuration files and any
other pertinent details.
Umds-8366-2: failed to free umds
unique receiver p
The UMDS server (umdsd) en-
countered an error deleting the
UM receiver associated with the
umds_rcv object
This is an internal error and should
be reported to customer support;
please include all appropriate ver-
sion numbers (UM and UMDS), as-
sociated configuration files and any
other pertinent details.
Umds-8366-3: failed to free umds
wc receiver p
The UMDS server (umdsd) en-
countered an error deleting the UM
wildcard receiver associated with
the umds_rcv object
This is an internal error and should
be reported to customer support;
please include all appropriate ver-
sion numbers (UM and UMDS), as-
sociated configuration files and any
other pertinent details.
Umds-8366-4: Unknown receiver
type deleting umdsd_rcv <p>
An unknown receiver type was en-
countered while freeing a UMDS
receiver object.
This is an internal error and should
be reported to customer support;
please include all appropriate ver-
sion numbers (UM and UMDS), as-
sociated configuration files and any
other pertinent details.
Umds-8366-5: Unknown receiver
type deleting umdsd_rcv <p>
An unknown receiver type was en-
countered while deleting a UMDS
receiver object.
This is an internal error and should
be reported to customer support;
please include all appropriate ver-
sion numbers (UM and UMDS), as-
sociated configuration files and any
other pertinent details.
Umds-8406-1: umdsd_stats←-
_queue_internal_cmd_cb: src
create before delete. is <d>
The webmon statistics subsystem
got a source create for an already
existing source id (the intended
src structure was not NULL in the
source array).
It is possible for creation and dele-
tion to happen out of order.
Umds-8406-2: umdsd_stats←-
_queue_internal_cmd_cb: src
delete before create. id <d>
The webmon statistics subsystem
got a source delete for an already
deleted source id (the intended src
structure was NULL in the source
array).
It is possible for creation and dele-
tion to happen out of order.
9.7 UMDS Log Messages 265
Umds-8406-3: umdsd_stats←-
_queue_internal_cmd_cb: rcv
create before delete. id <d>
The webmon statistics subsystem
got a receiver create for an already
existing receiver id (the intended
rcv structure was not NULL in the
receiver array).
It is possible for creation and dele-
tion to happen out of order.
Umds-8406-4: umdsd_stats←-
_queue_internal_cmd_cb: rcv
delete before create. id <d>
The webmon statistics subsystem
got a receiver delete for an already
deleted source id (the intended rcv
structure was NULL in the receiver
array).
It is possible for creation and dele-
tion to happen out of order.
Umds-8408-1: umdsd_worker_←-
api_delete: waiting for worker
p<d>to quit
The request to remove a worker is
still pending.
The worker thread is unusually
busy at this time but will eventually
serve this request.
Umds-8447-1: umdsd_worker_←-
handle_blocked_msg: Parse Error
The client connection parser en-
countered an unrecoverable error.
This is an internal error, if it recurs,
please report it along with any rela-
vant log files to GCS.
Umds-8499-1: LBM error while
sending request: s
LBM returned an unhandled error
code.
The LBM error code is given in the
log message. Please refer to the
LBM error code.
Umds-8499-2: LBM error while
sending message: s
LBM returned an unhandled error
code.
The LBM error code is given in the
log message. Please refer to the
LBM error code.
Umds-8499-3: LBM error while
sending response: s
LBM returned an unhandled error
code.
The LBM error code is given in the
log message. Please refer to the
LBM error code.
Umds-8519-1: Attempt to send
without a valid source created←-
: conn p
The UMDS client has sent a mes-
sage before the umdsd server has
created the corresponding source.
This will result in the loss of the
client message. Please notify G←-
CS with all suitable logs (client and
server).
Umds-8519-2: Attempt to send
without a valid source created←-
: conn p
The UMDS client has sent a mes-
sage before the umdsd server has
created the corresponding source.
This will result in the loss of the
client message. Please notify G←-
CS with all suitable logs (client and
server).
Umds-8519-3: Attempt to send
without a valid source created←-
: conn p
The UMDS client has sent a mes-
sage before the umdsd server has
created the corresponding source.
This will result in the loss of the
client message. Please notify G←-
CS with all suitable logs (client and
server).
Umds-8542-1: umdsd_worker_←-
client_src_create: transport <s>
not allowed, using TCP instead
The UMDS server configuration file
specified the use of LBT-SMX as
a transport type, which is not sup-
ported. The server will use TCP in-
stead.
Change the server configuration
file to specify one of the supported
transport types.
Umds-8544-11: Error creating
source: <d>: s
An error occurred creating the re-
quest source.
The text of the warning will provide
additional information for the reso-
lution of the problem.
Umds-8544-1: Error creating
source: <d>: s
An error occurred creating the re-
quest source.
The text of the warning will provide
additional information for the reso-
lution of the problem.
Umds-8697-1: umdsd_worker_←-
api_create: Error creating R←-
O-Contex while creating worker
p<d>
Creating the reactor only context
for a worker failed.
This fatal error is usually due to
specifying too many workers.
Umds-8697-2: umdsd_worker_←-
api_create: Error creating thread
while creating worker p<d>
Creating the worker application
thread failed.
This fatal error is usually due to
specifying too many workers.
266 UM Log Messages
Umds-8753-1: Attempt to send
without a valid source created←-
: conn p
The UMDS client has sent a mes-
sage with a wrong or garbage tidx;
either the client is buggy or t he
server is receiving garbage data.
This will result in the loss of the
client message. Please notify G←-
CS with all suitable logs (client and
server).
Umds-8753-2: Attempt to send
without a valid source created←-
: conn p
The UMDS client has sent a mes-
sage with a wrong or garbage tidx;
either the client is buggy or the
server is receiving garbage data.
This will result in the loss of the
client message. Please notify G←-
CS with all suitable logs (client and
server).
Umds-8757-1: s: malformed con-
nect capabilities
The UMDS client sent a malformed
capabilities string.
Make sure the client and server
versions are compatible and that
data from another application isn't
being erroneously sent to the UM←-
DS server.
Umds-8796-100: Error creating
umdsd_rcv_topic: <d>: s
An internal error occurred while
creating a receiver in the UMDS
server.
Contact Informatica support.
Umds-8894-1: umdsd_worker←-
_internal_cmd_add_sock←-
: worker(p<d>) not running
The indicated worker is not in the
RUNNING state
Contact Informatica support with all
relevant log files
Umds-8894-2: umdsd_worker_←-
internal_cmd_add_sock: worker
p<d>connection p<d>(s:u) cre-
ated
Notification that a new client con-
nection has been added.
No resolution is required.
Umds-8896-1: umdsd_webmon_←-
api_create: failed to init web server
(ip=s, port=s)
The web monitor subsystem failed
to start.
The web server library will have re-
ported additional details to the con-
sole.
Umds-8909-1: UMDS Permissions
are no longer applied
Permissions are no longer sup-
ported in the UMDS server XML
configuration file.
Remove any permissions sections
from the server's XML config file.
Umds-8909-2: get_application←-
: UMDS Permissions are no longer
applied
Permissions are no longer sup-
ported in the UMDS server XML
configuration file.
Remove any permissions sections
from the server's XML config file.
Umds-8909-3: get_user: UMDS
Permissions are no longer applied
Permissions are no longer sup-
ported in the UMDS server XML
configuration file.
Remove any permissions sections
from the server's XML config file.
Umds-8947-1: Error creating
umdsd_rcv_topic: <d>: s
An underlying regular receiver for
a topic could not be created for a
wildcard receiver.
This would usually imply an out
of memory problem or some other
internal error; contact Informatica
support.

Navigation menu