| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| AMQ6047,AMQ9434 ERRORS |
« View previous topic :: View next topic » |
| Author |
Message
|
| adviceid |
 Posted: Wed Mar 28, 2012 12:59 am Post subject: AMQ6047,AMQ9434 ERRORS |
 |
|
Newbie
Joined: 28 Mar 2012
Posts: 7
|
My side of the deployment of three machines, a machine as a gateway, the GW, the two machines for the application server CPG1, CPG2, gateway is responsible for receiving BANK machine external message after message load balancing through dynamic remote queue to send ANYONE send two local queue on the application server.
Are now experiencing a strange problem when I BANK machine configuration
def qr (Q.BANK2CPG) rname (Q.BANK2CPG) rqmname (ANYONE) xmitq (QM000) defpsist (yes) replace
The after of the RNAME changed to any other name, the gateway GW can not forward a message to the application CPG1, CPG2, the message into the dead-letter queue. Only Q.BANK2CPG the name is successfully forwarded.
The CCSID of the few machines we are a unified set to 5488
The MQ version is 7.0.1.6
MQ we have to restart several times, or not.
Attach
Built MQ cluster script
(1) create the MQ queue manager
Create a queue manager on CPG1, CPG2, and GW, respectively, BANK, for the external system machine
CPG1:
crtmqm-q QMTOPCPG1
CPG2:
crtmqm-q QMTOPCPG2
GW:
crtmqm-q QMTOPGW
(2) start the queue manager
CPG1:
strmqm QMTOPCPG1
CPG2:
strmqm QMTOPCPG2
GW:
strmqm QMTOPGW
3 Create and start the listener
MQSC commands
CPG1:
DEFINE LISTENER (LISTENER.TCP) TRPTYPE (TCP) PORT (1414) CONTROL (QMGR)
START LISTENER (LISTENER.TCP)
CPG2:
DEFINE LISTENER (LISTENER.TCP) TRPTYPE (TCP) PORT (1414) CONTROL (QMGR)
START LISTENER (LISTENER.TCP)
GW:
DEFINE LISTENER (LISTENER.TCP) TRPTYPE (TCP) PORT (1414) CONTROL (QMGR)
START LISTENER (LISTENER.TCP)
Set the cluster of full repositories
MQSC commands
CPG1:
ALTER QMGR REPOS (TOP_CLUSTER)
CPG2:
ALTER QMGR REPOS (TOP_CLUSTER)
(4) define the queue manager cluster to send and cluster-receiver channel
MQSC commands
CPG1:
DEFINE CHANNEL (TO.QMTOPCPG1) CHLTYPE (CLUSRCVR) TRPTYPE (TCP) CONNAME ('130 .45.140.169 (1414) ') CLUSTER (TOP_CLUSTER)
DEFINE CHANNEL (TO.QMTOPCPG2) CHLTYPE (CLUSSDR) TRPTYPE (TCP) CONNAME ('130 .45.140.170 (1414) ') CLUSTER (TOP_CLUSTER)
CPG2:
DEFINE CHANNEL (TO.QMTOPCPG2) CHLTYPE (CLUSRCVR) TRPTYPE (TCP) CONNAME ('130 .45.140.170 (1414) ') CLUSTER (TOP_CLUSTER)
DEFINE CHANNEL (TO.QMTOPCPG1) CHLTYPE (CLUSSDR) TRPTYPE (TCP) CONNAME ('130 .45.140.169 (1414) ') CLUSTER (TOP_CLUSTER)
GW:
DEFINE CHANNEL (TO.QMTOPCPG1) CHLTYPE (CLUSSDR) TRPTYPE (TCP) CONNAME ('130 .45.140.169 (1414) ') CLUSTER (TOP_CLUSTER)
DEFINE CHANNEL (TO.QMTOPGW) CHLTYPE (CLUSRCVR) TRPTYPE (TCP) CONNAME ('130 .45.140.168 (1414) ') CLUSTER (TOP_CLUSTER)
(5) to create a cluster member of the shared local queue
MQSC commands
CPG1:
DEFINE QLOCAL (QTOPCPG) CLUSTER (TOP_CLUSTER)
CPG2:
DEFINE QLOCAL (QTOPCPG) CLUSTER (TOP_CLUSTER)
6. Set the dead-letter queue
MQSC commands
CPG1:
The DEFINE QLOCAL (DEADQ)
ALTER QMGR DEADQ (DEADQ)
CPG2:
The DEFINE QLOCAL (DEADQ)
ALTER QMGR DEADQ (DEADQ)
GW:
The DEFINE QLOCAL (DEADQ)
ALTER QMGR DEADQ (DEADQ)
DEFINE QLOCAL (QTOPCLIENT) CLUSTER (TOP_CLUSTER)
define channel (SVRCONN) chltype (SVRCONN) TRPTYPE (TCP) mcauser ('mqm') replace
CPG1
def ql (CNAPS2PBOC) maxdepth (100000) defpsist (yes) maxmsgl (1048576) replace
def ql (HVPSPBOC) maxdepth (100000) defpsist (yes) maxmsgl (1048576) replace
def ql (BEPSPBOC) maxdepth (100000) defpsist (yes) maxmsgl (1048576) replace
def ql (BEPSBANK) maxdepth (100000) defpsist (yes) maxmsgl (1048576) replace
def ql (HVPSBANK) maxdepth (100000) defpsist (yes) maxmsgl (1048576) replace
CPG2
def ql (CNAPS2PBOC) maxdepth (100000) defpsist (yes) maxmsgl (1048576) replace
def ql (HVPSPBOC) maxdepth (100000) defpsist (yes) maxmsgl (1048576) replace
def ql (BEPSPBOC) maxdepth (100000) defpsist (yes) maxmsgl (1048576) replace
def ql (BEPSBANK) maxdepth (100000) defpsist (yes) maxmsgl (1048576) replace
def ql (HVPSBANK) maxdepth (100000) defpsist (yes) maxmsgl (1048576) replace
External BANK machine access --------------------------------------------- ------------------------
CPG1:
def ql (Q.BANK2CPG) maxdepth (100000) defpsist (yes) maxmsgl (1048576) CLUSTER (TOP_CLUSTER) replace
CPG2:
def ql (Q.BANK2CPG) maxdepth (100000) defpsist (yes) maxmsgl (1048576) CLUSTER (TOP_CLUSTER) replace
GW:
DEFINE QR (ANYONE) RNAME ('') RQMNAME ('')
DEFINE QR (Q.CPG2BANK) RNAME (Q.CPG2BANK) RQMNAME (QMBANK) xmitq (QM000) CLUSTER (TOP_CLUSTER)
def ql (QM000) usage (xmitq) defpsist (yes) maxdepth (100000) maxmsgl (1048576) trigger trigtype (first) trigdata (CPG2BANK) initq (system.channel.initq) replace
def chl (CHL.CPG2BANK) chltype (sdr) discint (1800) conname ('130 .45.130.11 (1414) ') xmitq (QM000) trptype (tcp) shortrty (10000) shorttmr (30) longtmr (300) longrty (999999999) batchsz (50) replace
def chl (CHL.BANK2CPG) chltype (rcvr) trptype (tcp) replace
BANK:
crtmqm-lc-lf 4096-lp 2-ls 1-q QMBANK
def ql (Q.CPG2BANK) maxdepth (100000) defpsist (yes) maxmsgl (1048576) replace
def qr (Q.BANK2CPG) rname (Q.BANK2CPG) rqmname (ANYONE) xmitq (QM000) defpsist (yes) replace
def ql (QM000) usage (xmitq) defpsist (yes) maxdepth (100000) maxmsgl (1048576) trigger trigtype (first) trigdata (BANK2CPG) initq (system.channel.initq) replace
def chl (CHL.BANK2CPG) chltype (sdr) discint (1800) conname ('130 .45.140.168 (1414) ') xmitq (QM000) trptype (tcp) shortrty (10000) shorttmr (30) longtmr (300) longrty (999999999) batchsz (50) replace
def chl (CHL.CPG2BANK) chltype (rcvr) trptype (tcp) replace
DEFINE LISTENER (LISTENER.TCP) TRPTYPE (TCP) PORT (1414) CONTROL (QMGR)
START LISTENER (LISTENER.TCP)
alter the 'qmgr' ccsid (5 488)
Error log, / var / mqm / 'qmgr' / errors /03/27/2012 07:14:31 AM - Process (25434.1) User (mqm) Program (amqrrmfa)
Host (apdas141was01)
AMQ6047: Conversion not supported.
EXPLANATION:
WebSphere MQ is unable to convert string data tagged in CCSID 5488 to data in
CCSID 819.
ACTION:
Check the WebSphere MQ Application Programming Reference for Appendix and the
appropriate National Language Support publications to see if the CCSIDs are
supported by your system.
----- Amqvxcca.c: 521 ---------- ------------------------------ ----------------
03/27/2012 07:14:31 AM - Process (25434.1) User (mqm) Program (amqrrmfa)
Host (apdas141was01)
AMQ9434: Unrecognized message on SYSTEM.CLUSTER.COMMAND.QUEUE.
EXPLANATION:
The repository manager found a message on one of its queues having, either a
format that could not be recognized, or that did not come from a queue manager
or repository manager. The message was put on the dead-letter queue.
ACTION:
Examine the message on the dead-letter - the queue to determine the the originator of the
message.
----- Amqrrmfa.c: 4734 ---------------------------------------- ---------------
03/27/2012 07:14:32 AM - Process (26500.50) User (mqm) Program (amqrmppa)
Host (apdas141was01)
AMQ9544: Messages not put to destination queue.
EXPLANATION:
During the processing of channel 'CHL.TREATS2CPG' one or more messages could
not be put to the destination queue and attempts were made to put them to a
dead-letter queue. The location of the queue is 1, where 1 is the local
The dead-letter the queue and 2 is the remote dead-letter queue.
ACTION:
Examine the contents of the dead-letter queue. Each message is contained in a
structure that describes why the message was put to the queue, and to where it
was originally addressed. Also look at previous error messages to see if the
attempt to put messages to a dead-letter queue failed. The program identifier
(PID) of the processing program was '26500 '. |
|
| Back to top |
|
 |
| rekarm01 |
| Posted: Wed Mar 28, 2012 5:13 pm Post subject: Re: AMQ6047, AMQ9434 ERRORS |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| adviceid wrote: |
AMQ6047: Conversion not supported.
EXPLANATION: WebSphere MQ is unable to convert string data tagged in CCSID 5488 to data in CCSID 819.
ACTION: Check the WebSphere MQ Application Programming Reference for Appendix and the appropriate National Language Support publications to see if the CCSIDs are
supported by your system. |
WebSphere MQ does not support direct conversions between ccsids that represent different national-language groups, (such as 819 and 5488). Connected queue managers should use qmgr ccsids from the same national-language group or Unicode (UTF-8), or they should enable default data conversion. |
|
| Back to top |
|
|
| adviceid |
| Posted: Wed Mar 28, 2012 8:50 pm Post subject: |
|
|
Newbie
Joined: 28 Mar 2012
Posts: 7
|
I had thought so,
But I use the same CCSID configuration, message in to Q.BANK2CPG queue is no problem, then just change what Q.BANK2CPG queue name on the die
I just tried to throw a message to the queue in the gateway directly, is also reported that the error code 2085: unable to the open the queue for output |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Mar 31, 2012 8:45 pm Post subject: Re: AMQ6047, AMQ9434 ERRORS |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| rekarm01 wrote: |
| Connected queue managers should use qmgr ccsids from the same national-language group or Unicode (UTF-8 ), or they should enable default data conversion. |
And remember this is especially true in a cluster where each qmgr needs to talk to every other qmgr in the cluster... you might want to set the qmgrs CCSID to UTF-8... It's a safe bet that you would have conversion tables to UTF-8 on the platforms the qmgr is running on. It would also remove the converstion problems you are facing between qmgrs...
Have fun 
_________________
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
|
|
|
|
