| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Log Scanner to Correct AMQ9526 |
« View previous topic :: View next topic » |
| Author |
Message
|
| belchman |
 Posted: Tue Jun 17, 2008 5:22 am Post subject: Log Scanner to Correct AMQ9526 |
 |
|
Partisan
Joined: 31 Mar 2006
Posts: 386
Location: Ohio, USA
|
I am about to embark on an adventurous journey to write a C process that will be deployed to our MQ hosts. The objective of this journey is to scan the MQ log files for an occurrence of AMQ9526 (sequence out of sequence). If a hit occurs, reset the offending sender channel.
Does anyone here already have something in production that does this? How do you do it? Do you recommend against it? Do you have C code I can use?
_________________
Make three correct guesses consecutively and you will establish a reputation as an expert. ~ Laurence J. Peter |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Jun 17, 2008 6:25 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
...and you are doing this instead of fixing the underlying problem that causes the channels to fail??
_________________
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 |
|
|
| belchman |
| Posted: Tue Jun 17, 2008 6:47 am Post subject: |
|
|
Partisan
Joined: 31 Mar 2006
Posts: 386
Location: Ohio, USA
|
In RE to bruce2359...
Yes. In our B2B relationships, we are not always in control of what our partners do. So, when it occurs, it is better to 1) reset, 2)send notification that reset occurred, 3)complain to partner, 4) get at cause and 5)implement prevention measures instead of 1) take production outage, 2) call B2B partner to find out what happened and 3) manually reset channel to get production flowing while being down entire time.
_________________
Make three correct guesses consecutively and you will establish a reputation as an expert. ~ Laurence J. Peter |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jun 17, 2008 7:05 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| So, when it occurs, it is better to ... |
This is one of those situations where there is no best solution.
Yours is a good technical solution to a technical problem; but given the possibility of message loss - after all, that's what sequence-wrap is there for - what's missing is the best business solution.
I'm hoping that the business applications at both ends keep track of missing or duplicated transactions (that result in missing or duplicated messages).
While not an exact parallel, your technical solution is like the technical solution for the programatic resource deadly embrace : kill one (or the other) of the offending transactions involved. It's a wonderful technical solution; but a poor business solution.
My sympathies. Been there.
_________________
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
|
|
|
|
