| Author |
Message
|
| HubertKleinmanns |
 Posted: Fri Oct 24, 2008 12:18 am Post subject: |
 |
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
When you start a channel it loads its configured attributes and compares these with the corresponding attributes of the partner channel. If attributes are different, the channel handles out which will be used (e. g. message length). I only know one exception, which has to be the same - the sequence wrap. The agreed channel attributes are valid as long as the channel stays active.
_________________
Regards
Hubert |
|
| Back to top |
|
 |
| Blomman |
| Posted: Fri Oct 24, 2008 4:29 am Post subject: |
|
|
Master
Joined: 31 Oct 2006
Posts: 230
|
Cant specify which type of channels/s but i have changed channel attributes before without restarting and the attribute has been "implemented"(wrong word, bad english?)
//Michael |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Sun Oct 26, 2008 11:42 pm Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
Blomman,
it is possible, to change attributes without restarting the channel. But these changes are only stored in the channel configuration. A running channel is not affected by these changes. The changed attributes become active when you restart the channel.
Do not mix up the DISPLAY CHANNEL(...) and the DISPLAY CHSTATUS(...) output!
_________________
Regards
Hubert |
|
| Back to top |
|
|
| ruchap |
| Posted: Thu Nov 05, 2009 4:33 am Post subject: All messages are going to the dead letter q |
|
|
Newbie
Joined: 05 Nov 2009
Posts: 3
|
Hello,
All the messages are going on the dead letter q with reason code 2218....
MQGET of message number 1
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 273 CodedCharSetId : 819
Format : 'MQDEAD '
Priority : 4 Persistence : 1
MsgId : X'414D5120514D2E4D544E4120202020204A7FFA7C26548502'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'QM.MTNA '
** Identity Context
UserIdentifier : 'stptqa3 '
AccountingToken :
X'0436353833000000000000000000000000000000000000000000000000000006'
ApplIdentityData : ' '
** Origin Context
PutApplType : '6'
PutApplName : 'java '
PutDate : '20091104' PutTime : '14560640'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 12997 bytes
00000000: 444C 4820 0000 0001 0000 08AA 4349 4E51 'DLH .......ªCINQ'
00000010: 2E49 4D50 4F52 542E 4D54 4E41 3420 2020 '.IMPORT.MTNA4 '
00000020: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000030: 2020 2020 2020 2020 2020 2020 4D51 4533 ' MQE3'
my sender channel ahs the parameter set as MAXMSGL(4194304) .
Am i missing something...wht else needs to be checked...
thanks |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Nov 05, 2009 4:45 am Post subject: Re: All messages are going to the dead letter q |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ruchap wrote: |
Am i missing something...wht else needs to be checked...
|
The receiver channel settings and all the other comments in this slightly dated thread you've reopened.... 
You might also want to give us a few clues about versions, platforms and when this messages comes out. Specifically has this set up ever worked for you or has it just started doing this?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ruchap |
| Posted: Thu Nov 05, 2009 4:48 am Post subject: Re: All messages are going to the dead letter q |
|
|
Newbie
Joined: 05 Nov 2009
Posts: 3
|
[quote="Vitor"][quote="ruchap"]Am i missing something...wht else needs to be checked...
[/quote]
The receiver channel settings and all the other comments in this slightly dated thread you've reopened....
You might also want to give us a few clues about versions, platforms and when this messages comes out. Specifically has this set up ever worked for you or has it just started doing this?[/quote]
The mq version is 6.0.2.0 on solaris 10.
A similar set up is working fine for the same remote q manager...
its just tht this isnt work...no clue...your help will be greatly appreciated ...
thnx |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Nov 05, 2009 4:59 am Post subject: Re: All messages are going to the dead letter q |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ruchap wrote: |
A similar set up is working fine for the same remote q manager...
its just tht this isnt work...no clue...your help will be greatly appreciated ...
thnx |
Then you need to compare the definitions on the 2 set ups. If one queue manager can send messages to a given queue manager, and this queue manager has never been able to send messages to the same given queue manager you have a configuration issue. Even if it's the same remote queue manager, it's not the same channels in use.
My tip - unload the channel definitions with saveqmgr & do a text compare, much easier than checking by eye. Also stop & start the channels to make sure these definitions are the ones in use (see earlier in this thread).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ruchap |
| Posted: Thu Nov 05, 2009 5:11 am Post subject: Re: All messages are going to the dead letter q |
|
|
Newbie
Joined: 05 Nov 2009
Posts: 3
|
thnx for the suggestion...
have already done that i have check the remote q,xmit q and sender channel defination at my end....
a similar set up works for UAT but not in my env 
since its going from xmitq to dead q ..something is seriously wrong...
when i browse message on dead q it gives sum weird error which i have posted earlier...
need serious help |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Nov 05, 2009 8:54 am Post subject: Re: All messages are going to the dead letter q |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
| ruchap wrote: |
thnx for the suggestion...
have already done that i have check the remote q,xmit q and sender channel defination at my end....
a similar set up works for UAT but not in my env
since its going from xmitq to dead q ..something is seriously wrong...
when i browse message on dead q it gives sum weird error which i have posted earlier...
need serious help |
| Quote: |
mqrc 2218
2218 0x000008aa MQRC_MSG_TOO_BIG_FOR_CHANNEL |
is only a weird error if you have verified the maxmsgzs for the qmgr and the channel and the xmitq and the dlq... etc....
Remember to always check on both ends of a channel...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Nov 05, 2009 10:23 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9482
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| is only a weird error if you have verified the maxmsgzs ... |
The reasoncode is specific to message too big for channel (not xmit queue).
This attribute value is part of the channel startup negotiation, and the lowest value specified at both ends of the channel will be the actual max message size for the channel. Changes to this attribute requires channel restart.
_________________
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 |
|
|
| garyprmr |
| Posted: Thu Nov 05, 2009 11:17 am Post subject: |
|
|
Acolyte
Joined: 03 Sep 2005
Posts: 74
|
I changed the MAXMSGLTH on one my cluster sender channels .Now it shows me the increased I did that when the channel is running and it shows me the value.
Do you think it just display that new value and not actually have taken that change. Do I need to stop and start the channel to get that into effect. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Nov 05, 2009 11:55 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9482
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| Now it shows me the increased |
What mq command did you issue to display this?
_________________
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 |
|
|
| fjb_saper |
| Posted: Thu Nov 05, 2009 8:55 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
| garyprmr wrote: |
I changed the MAXMSGLTH on one my cluster sender channels .Now it shows me the increased I did that when the channel is running and it shows me the value.
Do you think it just display that new value and not actually have taken that change. Do I need to stop and start the channel to get that into effect. |
Cluster channel values need to be changed on the manual defined cluster channels i.e. cluster receivers. The primary use of manual defined cluster senders is for cluster control & health communications.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Nov 06, 2009 4:49 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| HubertKleinmanns wrote: |
| bruce2359 wrote: |
| I can think of one channel attribute that doesn't require a stop/start. |
Which one? I do not know about any channel attribute, which does not require channel restart!
And I am pretty sure, that there is no such attribute. |
I can think of one, too. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Nov 06, 2009 6:06 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9482
Location: US: west coast, almost. Otherwise, enroute.
|
A clue: only channel attributes that affect channel operation require that the channel be stoppped and restarted.
_________________
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 |
|
|
|
|
