This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
The MQ client on Windows logs everything by default. It all goes to Windows
Eventlog. Every MQ Client connection attempt that has a failure is logged as
error.
Here is our issue:
- client application connects with a channel table.
- channel table has 4 entries, for the 4 hosts on which the queue may be active
at any given time (active/passive).
- the first three connection attempts are unsuccessful, since the queue manager
is not active on those 3 hosts.
- the fourth connection attempt is successful.
We are seeing in AMQERR01.LOG that the first three failures are logged. While
these individual attempts are indeed unsuccessful, in the bigger picture the
MQCONN call by the application is successful.
The monitoring agent (HPOV) reads the 3 errors and reports them as failed
connections. This is misleading since the application connected successfully,
and is generating superfluous and misleading alarms.
We are looking for a modification to the MQ Client API behavior such that we
can reduce or eliminate these unnecessary connection errors being reported in
the log, and only report an unsuccessful connection when all appropriate
connection entries in the CCDT are not able to satisfy the initial MQCONN
request.
We do not wish to suppress these error messages using the "ExcludeMessage"
or "SuppressMessage" attributes under the "QMErrorLog" stanza in qm.ini, since
that will eliminate all such messages, including otherwise valid ones.
Idea priority | Medium |
RFE ID | 124877 |
RFE URL | |
RFE Product | IBM MQ |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
We recognise that this is a valid requirement. However it doesn't fit with our delivery plans for the next couple of years.
As a result we are declining this Idea. While declined the Idea can still be voted, and commented, upon.