suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT39263 Status: Closed

NOSQLBOOSTER TOOL FAILS TO CONNECT TO WIRE LISTENER DUE TO MISSING SUPPORT
FOR GETFREEMONITORINGSTATUS COMMAND

product:
DB2 CONNECT / DB2CONNCT / B50 - DB2
Problem description:
NoSQLBooster tool fails to connect to wire listener due to
missing support for getFreeMonitoringStatus command.

When NoSQLBooster GUI tool is trying to connect to Db2
NoSQL/JSON Wire Listener, the tool sends getFreeMonitoringStatus
() command to wirelistener. But, Db2 JSON Wire Listener do not
have support for this command yet. Hence, we need to update wire
listener code to add support for this command so that
NoSQLBooster can connect to Wire Listener.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* When NoSQLBooster client is used to connect to IBM           *
* NoSQL/JSON Wire Listener.                                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* NoSQLBooster tool fails to connect to wire listener due to   *
* missing support for getFreeMonitoringStatus command.         *
*                                                              *
* When NoSQLBooster GUI tool is trying to connect to Db2       *
* NoSQL/JSON Wire Listener, the tool sends                     *
* getFreeMonitoringStatus                                      *
* () command to wirelistener. But, Db2 JSON Wire Listener do   *
* not                                                          *
* have support for this command yet. Hence, we need to update  *
* wire                                                         *
* listener code to add support for this command so that        *
* NoSQLBooster can connect to Wire Listener.                   *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to db2 version 11.5.7.1 or later releases.           *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* When NoSQLBooster client is used to connect to IBM           *
* NoSQL/JSON Wire Listener.                                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* NoSQLBooster tool fails to connect to wire listener due to   *
* missing support for getFreeMonitoringStatus command.         *
*                                                              *
* When NoSQLBooster GUI tool is trying to connect to Db2       *
* NoSQL/JSON Wire Listener, the tool sends                     *
* getFreeMonitoringStatus                                      *
* () command to wirelistener. But, Db2 JSON Wire Listener do   *
* not                                                          *
* have support for this command yet. Hence, we need to update  *
* wire                                                         *
* listener code to add support for this command so that        *
* NoSQLBooster can connect to Wire Listener.                   *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to db2 version 11.5.7.1 or later releases.           *
****************************************************************
Comment
db2_v11571 contains fix of this issue. After the fix,
NoSQLBooster GUI tool is able to connect with IBM JSON Wire
Listener.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.11.2021
15.12.2021
24.10.2022
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)