| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Application Activity Trace incorrect queue name on 2085 |
« View previous topic :: View next topic » |
| Author |
Message
|
| tczielke |
 Posted: Wed Apr 26, 2017 8:04 am Post subject: Application Activity Trace incorrect queue name on 2085 |
 |
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
I ran across this issue with the Application Activity Trace. IBM has also opened an APAR for this issue. It can be confusing if you use Activity Traces, so wanted to document it. This applies to all releases of the Activity Trace.
When the Activity Trace has an MQOPEN that returns an rc=MQRC_UNKNOWN_OBJECT_NAME, some of the data that appears in the activity trace can be incorrect. Specifically, the wrong queue name could be displayed. Below is an example for the verbose output (amqsact -v). This issue can also cause an incorrect object name in the summary API one line output (amqsact with no -v) for this MQOPEN/2085 call, as well. The incorrect queue name in the summary API line is what I found most confusing, as you only see the incorrect queue name in that spot.
| Code: |
MonitoringType: MQI Activity Trace
Correl_id:
00000000: XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX 'XXXXXXXXXXXXXXXX'
00000010: XXXX XXXX XXXX XXXX 'XXXXXXXX '
QueueManager: 'QM1'
Host Name: 'server1'
IntervalStartDate: '2017-04-13'
IntervalStartTime: '21:31:17'
IntervalEndDate: '2017-04-13'
IntervalEndTime: '21:31:17'
CommandLevel: 800
SeqNumber: 370
ApplicationName: 'java'
Application Type: MQAT_UNIX
ApplicationPid: 8753
UserId: 'app1'
API Caller Type: MQXACT_EXTERNAL
API Environment: MQXE_OTHER
Application Function: ''
Appl Function Type: MQFUN_TYPE_UNKNOWN
Trace Detail Level: 3
Trace Data Length: 4096
Pointer size: 8
Platform: MQPL_UNIX
MQI Operation: 0
Operation Id: MQXF_OPEN
ApplicationTid: 1
OperationDate: '2017-04-13'
OperationTime: '21:31:16'
Object_type: MQOT_Q
Object_name: 'Q1' <---- Correct Queue Name
Object_Q_mgr_name: ' '
Hobj: 0
QMgr Operation Duration: 1004441
Completion Code: MQCC_FAILED
Reason Code: 2085 <---- Data after this point could be incorrect, per IBM support
Open_options: 8208
Recs_present: 0
Known_dest_count: 0
Unknown_dest_count: 538976288
Invalid_dest_count: 538976288
Object_type: MQOT_Q
Object_name: 'Q2' <---- Incorrect queue name
Object_Q_mgr_name: ' '
Resolved_Q_Name: 'Q2' <---- Incorrect queue name
Resolved_Q_mgr: 'QM1'
Resolved_local_Q_name: 'Q2' <---- Incorrect queue name
Resolved_local_Q_mgr: 'QM1'
Resolved_type: MQOT_Q
Dynamic_Q_name: 'AMQ.*'
|
_________________
Working with MQ since 2010. |
|
| Back to top |
|
 |
| hughson |
| Posted: Tue May 30, 2017 6:04 pm Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
Is it transient data? i.e is it the last thing you had in that storage, the last successful MQOPEN call for example?
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| tczielke |
| Posted: Wed May 31, 2017 4:46 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
Yes, it was previous queue information that the application had opened that was in that data. In some cases, the previous queue name was longer than the current one, so it was an amalgam of both queue names.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
