| Author |
Message
|
| vmanel |
 Posted: Wed Sep 25, 2019 10:55 pm Post subject: IIB Record Replay not working |
 |
|
Acolyte
Joined: 12 Mar 2019
Posts: 57
|
Hi,
We have setup IIB Record Replay in Production(iib 10.0.0.16, WMQ 9.0.0.4), and it was working fine. But from past few days, the messages are getting piled up in the queue SYSTEM.BROKER.DC.RECORD and it is not getting inserted in DB. The input count of the queue is 10. If we check the status of the queue the last put and get time of the queue is always the current time. And it is showing uncommitted messages in status of queue and it keeps changing every second. We tried to replicate this issue in lower environment, but there it is working fine. Any way to figure out and resolve this issue. Would enabling ODBC trace give some idea?
Thanks |
|
| Back to top |
|
 |
| abhi_thri |
| Posted: Thu Sep 26, 2019 12:42 am Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
hi...has anything changed with your DataCaptureStore configuration? Also are messages getting backed out to SYSTEM.BROKER.DC.BACKOUT queue?
Yes, odbc tracing should help but before doing that see whether there are any errors in the syslog...also worth monitoring the sylog for errors after restarting the Integration server configured at 'egForRecord' property |
|
| Back to top |
|
|
| vmanel |
| Posted: Thu Sep 26, 2019 4:12 am Post subject: |
|
|
Acolyte
Joined: 12 Mar 2019
Posts: 57
|
| abhi_thri wrote: |
hi...has anything changed with your DataCaptureStore configuration? Also are messages getting backed out to SYSTEM.BROKER.DC.BACKOUT queue?
Yes, odbc tracing should help but before doing that see whether there are any errors in the syslog...also worth monitoring the sylog for errors after restarting the Integration server configured at 'egForRecord' property |
No, configuration of DataCapture store was not changed, and also messages are not going to SYSTEM.BROKER.DC.BACKOUT queue
In syslog there is only one statement two days back for this, Integration server is 'eg_name' is now recording data for the following data capture stores: 'DataStoreName'
Because we had cleared the messages from this queue at that time, and the messages started piling up again the next minute. |
|
| Back to top |
|
|
| abhi_thri |
| Posted: Thu Sep 26, 2019 6:53 am Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
hi...it is worth checking with your DBAs to see whether any patches or so were applied at database end. If the thread is hanging with queue showing Uncommitted as Yes then it looks like the thread is waiting for database response...try enabling odbctrace and restart the 'egForRecord' integration server.
PS: Also don't you have any timeout settings configured at the Odbc stanza, if so ideally the thread should return a timeout if database operation was unsuccessful |
|
| Back to top |
|
|
| vmanel |
| Posted: Thu Sep 26, 2019 10:29 pm Post subject: |
|
|
Acolyte
Joined: 12 Mar 2019
Posts: 57
|
| abhi_thri wrote: |
| PS: Also don't you have any timeout settings configured at the Odbc stanza, if so ideally the thread should return a timeout if database operation was unsuccessful |
LoginTimeout=0
I see only this property in odbc stanza, apart from this there is no other timeout. |
|
| Back to top |
|
|
| abhi_thri |
| Posted: Thu Sep 26, 2019 11:25 pm Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
|
| Back to top |
|
|
| vmanel |
| Posted: Fri Sep 27, 2019 12:29 am Post subject: |
|
|
Acolyte
Joined: 12 Mar 2019
Posts: 57
|
Hi,
Where will the errors get logged for timeout error? in syslog? And does it say the query that timed out? Or the reason why it failed? |
|
| Back to top |
|
|
| abhi_thri |
| Posted: Fri Sep 27, 2019 1:51 am Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
| vmanel wrote: |
| Where will the errors get logged for timeout error? in syslog? And does it say the query that timed out? Or the reason why it failed? |
that depends...for eg:- if it is the query run from a flow that times out then the error will get reported via the flow's error handling logic (reports to whichever ticketing system that is enabled for the flow, sends to error queue etc) and as long as the flow is rethrowing the error for rollback it will get logged at syslog as well. For the Record/Replay i assume it will get logged just to the syslog and the message should get backed out to the backout queue.
| vmanel wrote: |
| And does it say the query that timed out? |
...I believe it does as sql error do report the failed query but please crosscheck
| vmanel wrote: |
| Or the reason why it failed? |
...Hmmm, the reason is that the query timed out...this setting just a controlled way of handling scenarios where database doesn't respond within a specified time, so all it will say is that the query has timed out. If you think of it, the flow hasn't had any response from the database to know what exactly has gone wrong at this point.
Have you liaised with yours DBAs yet, they should be able to monitor the database sessions and identified any hanging/stuck ones. Also did you try gathering odbc trace? also worth checking with DBAs whether the tables are write locked by some other session (eg:- user session which has issued an insert/update query but hasn't committed/rollbacked) |
|
| Back to top |
|
|
|
|
