Troubleshooting
Problem
This document helps collect and share data required to diagnose MQ Queue configuration issues in Sterling Order Management System (OMS).
Diagnosing The Problem
Collecting Data
When opening a case with IBM support, please share the following:
- Is it a remote queue or local queue?
- A local queue is a queue that belongs to the same queue manager where it is defined. It is accessible to local applications that connect to the same queue manager. Messages are put to and retrieved from a local queue using the MQ API or other messaging interfaces.
- A remote queue belongs to a different queue manager and is accessed through a communication channel. Remote queues are used to send and receive messages between queue managers. A message is put to a remote queue by an application running on one queue manager, and it is retrieved from the queue by an application running on a different queue manager.
- If it is a remote queue, please share the Name/Alias, Channel Definition, Transmission Queue, and Remote Queue Definition.
- Is this a newly created queue? (Y/N)
- What is the time/date of your last successful connection to the queue?
- Were there any recent changes to the affected environments?
- Is this issue happening with other queues? Please share the name of all affected queues.
- Is this issue happening on any other environments? (Dev/QA/PreProd/Prod)
- What is the date/time of your weekly scheduled maintenance window?
- What is the business impact of this issue?
- If your message is not reaching the queue, please share the following diagnostic data:
- Queue name(s)
- Architecture (e.g., ESB implementation)
- Agent/Integration server logs
- Please provide the date/time of when the message was sent or seen
- XML message being sent
- Frequency (i.e., is the issue consistent? Are some messages flowing or is it completely failing?)
- Share the date/time and Input XML of the last successful message
Please share the following diagnostic data respective to the error you're seeing:
The log space for the queue manager is becoming full. One or more long-running transactions have been rolled back to release log space so that the queue manager can continue to process requests.
- MQ Client Details (Name/Version)
- MQ library version
- Java version
- MQ server log size may be too low for existing flows
- Please share a date/time for rolling restart of agent/integration servers to apply log size upgrade
| How to submit diagnostic data to IBM Support |
|
After you collect the information, and case is opened, see: |
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"ARM Category":[{"code":"a8m0z000000cy06AAA","label":"Services and MQ"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"SaaS"}]
Was this topic helpful?
Document Information
Modified date:
01 July 2023
UID
ibm16605175