|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Incoming MSG automatically splits into 100 bytes messages |
« View previous topic :: View next topic » |
Author |
Message
|
nageshshiv |
Posted: Wed Sep 22, 2010 11:25 pm Post subject: Incoming MSG automatically splits into 100 bytes messages |
|
|
Apprentice
Joined: 09 May 2008 Posts: 30
|
Hi,
When our Upstream system sends message to us, the message split up into 95-100 bytes of messages.
We verified the MAXMSGL is 4194304 for QLOCAL and RCVR Channel.
Sending side XMITQ/SDR Channel have MAXMSGL is 4194304.
Also tried using amqsput/amqsputc sample programs, same pattern observed.
QMGR:
QMNAME(QM.R701912) ACCTCONO(DISABLED)
ACCTINT(1800) ACCTMQI(OFF)
ACCTQ(OFF) ACTIVREC(MSG)
ALTDATE(2009-12-2 ALTTIME(16.48.55)
AUTHOREV(DISABLED) CCSID(819)
CHAD(DISABLED) CHADEV(DISABLED)
CHADEXIT( ) CHLEV(DISABLED)
CLWLDATA( ) CLWLEXIT( )
CLWLLEN(100) CLWLMRUC(999999999)
CLWLUSEQ(LOCAL) CMDLEVEL(600)
COMMANDQ(SYSTEM.ADMIN.COMMAND.QUEUE) CRDATE(2009-04-14)
CRTIME(17.52.57) DEADQ(SYSTEM.DEAD.LETTER.QUEUE)
DEFXMITQ( ) DESCR( )
DISTL(YES) INHIBTEV(DISABLED)
IPADDRV(IPV4) LOCALEV(DISABLED)
LOGGEREV(DISABLED) MAXHANDS(256)
MAXMSGL(4194304)
QLOCAL:
QUEUE(WSS.IBUSMMS.R701912) TYPE(QLOCAL)
ACCTQ(QMGR) ALTDATE(2009-05-10)
ALTTIME(17.45.54) BOQNAME( )
BOTHRESH(0) CLUSNL( )
CLUSTER( ) CLWLPRTY(0)
CLWLRANK(0) CLWLUSEQ(QMGR)
CRDATE(2009-05-10) CRTIME(17.45.54)
CURDEPTH(27) DEFBIND(OPEN)
DEFPRTY(0) DEFPSIST(YES)
DEFSOPT(SHARED) DEFTYPE(PREDEFINED)
DESCR(R701912 MMS Receive Queue from WSS)
DISTL(YES) GET(ENABLED)
NOHARDENBO INITQ(IDMS.WSS.MMS.INITIATION.QUEUE)
IPPROCS(0) MAXDEPTH(50000)
MAXMSGL(4194304) MONQ(QMGR)
RCVR Channel:
dis chl(RARS.R701912)
1 : dis chl(RARS.R701912)
AMQ8414: Display Channel details.
CHANNEL(RARS.R701912) CHLTYPE(RCVR)
ALTDATE(2010-09-23) ALTTIME(11.44.54)
BATCHSZ(50) COMPHDR(NONE)
COMPMSG(NONE) DESCR( )
HBINT(300) KAINT(AUTO)
MAXMSGL(4194304) MCAUSER( )
MONCHL(QMGR) MRDATA( )
MREXIT( ) MRRTY(10)
MRTMR(1000) MSGDATA( )
MSGEXIT( ) NPMSPEED(FAST)
PUTAUT(DEF) RCVDATA( )
RCVEXIT( ) SCYDATA( )
SCYEXIT( ) SENDDATA( )
SENDEXIT( ) SEQWRAP(999999999)
SSLCAUTH(OPTIONAL) SSLCIPH( )
SSLPEER( ) STATCHL(QMGR)
TRPTYPE(TCP)
Pls help to through some light on this. |
|
Back to top |
|
 |
exerk |
Posted: Wed Sep 22, 2010 11:32 pm Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
1. The upstream SDR has a very low MAXMSGL set?
2. The upstream application is deliberately chunking the message?
Just two off-the-cuff possibilities I can think of without any hard thinking...
Are the messages arriving as a group? Are the messages arriving as elements of a segmented message? _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Sep 23, 2010 6:07 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
How do you know that the messages are being split?
What utility/application are you using to make this determination?
Have you looked a message in the queue? Examine the MQMD. Is it part of a message group? _________________ 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 |
|
 |
Vitor |
Posted: Thu Sep 23, 2010 6:10 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
exerk wrote: |
Just two off-the-cuff possibilities I can think of without any hard thinking... |
Here's one off the other cuff; the test data has x0D and/or x0A and amqsput thinks it's an end of line. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
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
|
|
|
|