| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Dynamic queue with different names |
« View previous topic :: View next topic » |
| Author |
Message
|
| thipe |
 Posted: Mon Feb 02, 2009 9:49 am Post subject: Dynamic queue with different names |
 |
|
Novice
Joined: 24 Jun 2003
Posts: 19
Location: Brasil - São Paulo
|
Hi all , couple days ago we faced a problem with the dynamic queues here .
I've opened a PMR to IBM , and they told that its quite normal behavior... but I can't agree with this.
Checking the "dis ql" output , we can see that the QUEUE field is different that the real name .
dis ql(QD_MW_S.EP0110330111480000000000)
1: dis ql(QD_MW_S.EP0110330111480000000000)
AMQ8409: Display Queue details.
DESCR(to trigger delivery xxxxxxx )
PROCESS(P_DS_SERIAL) BOQNAME( )
INITQ(I_MW_INITQ) TRIGDATA( )
CLUSTER( ) CLUSNL( )
QUEUE(QD_MW_S.EP0110354003680000000000)
CRDATE(2008-04-0 CRTIME(16.57.29)
ALTDATE(2008-04-0 ALTTIME(16.57.29)
GET(ENABLED) PUT(ENABLED)
DEFPRTY(0) DEFPSIST(NO)
MAXDEPTH(500000) MAXMSGL(104857600)
BOTHRESH(0) NOSHARE
DEFSOPT(EXCL) HARDENBO
MSGDLVSQ(PRIORITY) RETINTVL(999999999)
USAGE(NORMAL) TRIGGER
TRIGTYPE(FIRST) TRIGDPTH(1)
TRIGMPRI(0) QDEPTHHI(80)
QDEPTHLO(20) QDPMAXEV(ENABLED)
QDPHIEV(DISABLED) QDPLOEV(DISABLED)
QSVCINT(999999999) QSVCIEV(NONE)
DISTL(NO) NPMCLASS(NORMAL)
DEFTYPE(PERMDYN) TYPE(QLOCAL)
SCOPE(QMGR) DEFBIND(OPEN)
IPPROCS(0) OPPROCS(0)
Some important details , we're still runnning 5.3 - CSD 12 , there is a special contract assigned with IBM to keep some support ...
Some help will be very appreciated.
_________________
Adriano Alves
São Paulo - Brasil
Websphere MQSeries v5.3 Adm Certified
Websphere MQSeries v 6 Adm Certified |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Feb 02, 2009 10:20 am Post subject: Re: Dynamic queue with different names |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| thipe wrote: |
| Some important details , we're still runnning 5.3 - CSD 12 , there is a special contract assigned with IBM to keep some support ... |
And on this basis they've answered the PMR.
| thipe wrote: |
| Some help will be very appreciated. |
With what? You've not articulated a problem, other than the output from the display command looks odd. Is an application getting a 2085? If so, under what circumstances and have you determined (via diagnostic techniques) which queue it's using?
If not 2085, then what? Help us to help you. More information, more advice.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| thipe |
| Posted: Tue Feb 03, 2009 12:45 pm Post subject: |
|
|
Novice
Joined: 24 Jun 2003
Posts: 19
Location: Brasil - São Paulo
|
Hi Vitor.
Regarding the MQ version , yes we have a special contract with IBM in France that will cover us till the end of MQ ( we are migrating to X i ) .
About that queue , yes the output looks odd . Actually this queue appears to be Ghost queue , since the messages were read by the application before the problem . What I mean by problem , we have a broker opening dynamic queues , reading the messages and then closing / discard the queue.
There is a very critical application that send the file to the broker , that needs the messages being stored in a sequence , otherwise we will have some error at the end of the process , when another adapter get's the messages from another queue ( not dynamic this time ) and sent it to Legacy or another SAP box.
We also saw some error 2085 on the broker logs and I believe that its due to the different names ... application was trying to read the last messages from that queue that has the name changed.
The information we got from FDCs that were generated are:
Probe Id :- ZL006026
Major Errorcode :- xecF_E_UNEXPECTED_RC
Minor Errorcode :- OK
Probe Type :- MSGAMQ6118
Probe Severity :- 2
Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred
Probe Id :- ZL043050
Major Errorcode :- xecF_E_UNEXPECTED_RC
Minor Errorcode :- OK
Probe Type :- MSGAMQ6118
Probe Severity :- 2
Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred
Hope this can help
Thank you;
_________________
Adriano Alves
São Paulo - Brasil
Websphere MQSeries v5.3 Adm Certified
Websphere MQSeries v 6 Adm Certified |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Feb 03, 2009 1:25 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| thipe wrote: |
| There is a very critical application that send the file to the broker , that needs the messages being stored in a sequence , otherwise we will have some error at the end of the process , when another adapter get's the messages from another queue ( not dynamic this time ) and sent it to Legacy or another SAP box. |
Ok, there are 2 points here. One is that needing messages to be sent in sequence is called "message affinity" and is a bad design. The second is that running message affinity via dynamic queues isnt a really good idea.
You've not mentioned a platform, but from the ProbeIds I'll theorise Windows. I'll also point out the "unexpected rc" messages, common with Windows.
Check and see if either a) something interesting happened to the server or b) something relevent was done to the server.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| thipe |
| Posted: Tue Feb 03, 2009 2:08 pm Post subject: |
|
|
Novice
Joined: 24 Jun 2003
Posts: 19
Location: Brasil - São Paulo
|
Yeah... we had to "eat" this solution , since we're just a finger of the whole structure .
Anyway , we are running over AIX , we are 100% based in mq clustering , except for this queue I told you .
From the history I got , we had an controlled outage for a maintenance on the both boxes ( we also have HACMP ) . When the system comes up , we started Full repository first , and then the others partial . During the first hour our broker worked fine , with no errors however when the first large message comes ( 82 Mb ) that problem happened.
_________________
Adriano Alves
São Paulo - Brasil
Websphere MQSeries v5.3 Adm Certified
Websphere MQSeries v 6 Adm Certified |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 04, 2009 1:14 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| thipe wrote: |
| Yeah... we had to "eat" this solution , since we're just a finger of the whole structure . |
That happens a lot.
| thipe wrote: |
| Anyway , we are running over AIX |
Shows what I know..
| thipe wrote: |
| When the system comes up , we started Full repository first , and then the others partial . During the first hour our broker worked fine , with no errors however when the first large message comes ( 82 Mb ) that problem happened. |
Where is the 2nd FR hosted?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Feb 04, 2009 4:11 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Looks like you have some issues... in the design
- you should not be using dynamic temporary queues with messages you can't afford to loose.
- you should not be using any dynamic queues while messages are in transit and you can't afford to loose them. How is the next process going to know the queue name if you use dynamic persistent queues??
Enjoy 
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
