| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| ACE trace logs |
« View previous topic :: View next topic » |
| Author |
Message
|
| gappodi |
 Posted: Fri Jan 04, 2019 5:47 am Post subject: ACE trace logs |
 |
|
Voyager
Joined: 05 Sep 2014
Posts: 76
|
I have been using IIB 9 for quite some time for developing flows in our application. When ever I used to get any error/exceptions, I would prefer to check the broker logs with the help of mqsireadlog and mqsiformatlog commands (as it gives details information along with the relevant BIP message).
I have recently installed our application on ACE 11.0.0.2 instance. While running one flow I saw few errors and wanted to analyze the broker logs in a similar way I did it on IIB 9 instance. But I realized that mqsireadlog and mqsiformatlog have got deprecated and I need to use tracing and diagnostics of ACE.
I ran the following command to check the trace.
mqsichangetrace AC11NODE -e eInvExecGroup -u -r -l none --trace /var/mqm/eInvDir/AC11WS/trace.txt
Upon re running the message flow I could not find any useful information. Following is an excerpt from the end of the trace.txt file.
2019-01-04 05:09:42.279216 2260 { ImbDirectory::Cursor::~Cursor
2019-01-04 05:09:42.279228 2260 } ImbDirectory::Cursor::~Cursor
2019-01-04 05:09:42.279244 2260 { ImbReadWriteLockInterface::WriteLock::WriteLock , (*ptr)0x7fff9aaadcd0, 0
2019-01-04 05:09:42.279252 2260 { ImbReadWriteLock::writeLock
2019-01-04 05:09:42.279264 2260 } ImbReadWriteLock::writeLock , 0
2019-01-04 05:09:42.279268 2260 } ImbReadWriteLockInterface::WriteLock::WriteLock
2019-01-04 05:09:42.279288 2260 { ImbReadWriteLockInterface::WriteLock::unlock
2019-01-04 05:09:42.279312 2260 { ImbReadWriteLock::writeUnlock
2019-01-04 05:09:42.279328 2260 } ImbReadWriteLock::writeUnlock , 0
2019-01-04 05:09:42.279348 2260 } ImbReadWriteLockInterface::WriteLock::unlock , 0
2019-01-04 05:09:42.279360 2260 { ImbReadWriteLockInterface::WriteLock::WriteLock , (*ptr)0x7fff9aaadd88, 0
2019-01-04 05:09:42.279380 2260 { ImbReadWriteLock::writeLock
2019-01-04 05:09:42.279388 2260 } ImbReadWriteLock::writeLock , 0
2019-01-04 05:09:42.279396 2260 } ImbReadWriteLockInterface::WriteLock::WriteLock
2019-01-04 05:09:42.279408 2260 { ImbReadWriteLockInterface::WriteLock::unlock
2019-01-04 05:09:42.279412 2260 { ImbReadWriteLock::writeUnlock
2019-01-04 05:09:42.279420 2260 } ImbReadWriteLock::writeUnlock , 0
2019-01-04 05:09:42.279428 2260 } ImbReadWriteLockInterface::WriteLock::unlock , 0
2019-01-04 05:09:42.279440 2260 { ImbReadWriteLockInterface::WriteLock::~WriteLock
2019-01-04 05:09:42.279448 2260 } ImbReadWriteLockInterface::WriteLock::~WriteLock
2019-01-04 05:09:42.279456 2260 { ImbReadWriteLockInterface::WriteLock::~WriteLock
2019-01-04 05:09:42.279464 2260 } ImbReadWriteLockInterface::WriteLock::~WriteLock
2019-01-04 05:09:42.279472 2260 { ImbReadWriteLock::~ImbReadWriteLock
2019-01-04 05:09:42.279480 2260 ImbReadWriteLock::~ImbReadWriteLock , 'Encountered pthread_rwlock_destroy return code ', 0
2019-01-04 05:09:42.279488 2260 } ImbReadWriteLock::~ImbReadWriteLock
2019-01-04 05:09:42.279500 2260 { ImbReadWriteLockInterface::~ImbReadWriteLockInterface
2019-01-04 05:09:42.279516 2260 } ImbReadWriteLockInterface::~ImbReadWriteLockInterface
2019-01-04 05:09:42.279520 2260 { ImbReadWriteLock::~ImbReadWriteLock
2019-01-04 05:09:42.279528 2260 ImbReadWriteLock::~ImbReadWriteLock , 'Encountered pthread_rwlock_destroy return code ', 0
2019-01-04 05:09:42.279536 2260 } ImbReadWriteLock::~ImbReadWriteLock
2019-01-04 05:09:42.279544 2260 { ImbReadWriteLockInterface::~ImbReadWriteLockInterface
2019-01-04 05:09:42.279548 2260 } ImbReadWriteLockInterface::~ImbReadWriteLockInterface
2019-01-04 05:09:42.279564 2260 { ImbThreadManager::~ImbThreadManager
2019-01-04 05:09:42.279576 2260 } ImbThreadManager::~ImbThreadManager
2019-01-04 05:09:42.279584 2260 { ImbReadWriteLock::~ImbReadWriteLock
2019-01-04 05:09:42.279592 2260 ImbReadWriteLock::~ImbReadWriteLock , 'Encountered pthread_rwlock_destroy return code ', 0
2019-01-04 05:09:42.279596 2260 } ImbReadWriteLock::~ImbReadWriteLock
2019-01-04 05:09:42.279604 2260 { ImbReadWriteLockInterface::~ImbReadWriteLockInterface
2019-01-04 05:09:42.279608 2260 } ImbReadWriteLockInterface::~ImbReadWriteLockInterface
Is there any other way of enabling the trace or am I missing something in what I have done to get the trace ? Please provide help here..
Thanks and Regards,
Maneesh Sharma |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Jan 04, 2019 10:08 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
I believe you now need to set the tracing in the Yaml file for the Integration server...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| gappodi |
| Posted: Tue Jan 08, 2019 1:21 am Post subject: |
|
|
Voyager
Joined: 05 Sep 2014
Posts: 76
|
I tried setting traceLevel to service and diagnostic but it still does not give any log information. Any help would be appreciated..
Thanks and Regards,
Maneesh Sharma |
|
| Back to top |
|
|
| martinb |
| Posted: Wed Jan 09, 2019 9:45 am Post subject: |
|
|
Master
Joined: 09 Nov 2006
Posts: 210
Location: UK
|
Hi
ACE v11 produce plain text trace, so you can simply view the files written in the workpath once you have enabled tracing.
To start user tracing of the integration server, use one of the following methods:
In the IBM App Connect Enterprise web user interface, navigate to the top level of the integration server, then select Start user trace from the menu at the top-right corner of the page.
Use the REST API provided by IBM App Connect Enterprise.
For a server managed by an Integration node, use the cmd, eg
mqsichangetrace <node> -e <server> -u -l debug -m safe -r
Set the trace permanently in the "server.conf.yaml" for your server
For an independent integration server, the trace logs are written to the following location:
<workdir>/config/common/log
For an integration server, the trace logs are written to the following location:
MQSI_WORKPATH/Common/log/<node>.<server>.userTrace.0.txt
See https://www.ibm.com/support/knowledgecenter/en/SSTTDS_11.0.0/com.ibm.etools.mft.doc/an01320_.htm
HTH |
|
| Back to top |
|
|
| kennedy |
| Posted: Thu Sep 08, 2022 5:43 am Post subject: Usando tracepath |
|
|
Newbie
Joined: 19 Aug 2022
Posts: 1
|
1 - Inicie um rastreamento de usuário usando o comando abaixo
mqsichangetrace <Integration node> -t -e <Integration Server> -l debug -r -c 200000
2 - Envie uma mensagem através do fluxo de mensagens.
-
3 - Pare o rastreamento usando o comando MQSI abaixo
mqsichangetrace <Integration node> -t -e <Integration Server> -l none
4 - Leia o conteúdo do rastreamento em um arquivo:
mqsireadlog <Integration node> -t -e <Integration Server> -f -o app_date.txt
5 - Formate o arquivo de rastreamento XML em formato legÃvel pelo usuário.
mqsiformatlog -i app_date.xml -o app_date.txt
6 - Examine o arquivo de texto. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Sep 08, 2022 6:17 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9486
Location: US: west coast, almost. Otherwise, enroute.
|
Most of us here use English.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| 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
|
|
|
|
