ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Queue depth increasing at Transmission Queue

Post new topic  Reply to topic Goto page Previous  1, 2
 Queue depth increasing at Transmission Queue « View previous topic :: View next topic » 
Author Message
Vitor
PostPosted: Fri Mar 25, 2016 4:04 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

gag_nm wrote:
Application is WMB 8.0.0.3. It is using Mqoutput node to put message on transmission queue.


You might have mentioned that before. That rather sinks my theory; unless you've done something preternaturally stupid in your flow WMB will always commit the message it puts.

gag_nm wrote:

It is some issue using Remote Queues??..


As others have mentioned, if we discount the message not being committed by the putting application (see above) then we're left with the transmission problem as described.

gag_nm wrote:
I don't understand how to solve this uncommitted messages.


Well you don't solve it. The problem is most likely at the receiving end not your end. They need to fix it.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
gag_nm
PostPosted: Fri Mar 25, 2016 4:16 am    Post subject: Reply with quote

Centurion

Joined: 16 Oct 2008
Posts: 102

When their were uncommitted messages on queue, i have run follow command.

Code:

DISPLAY QSTATUS(B2.XMITQ) TYPE(HANDLE) ALL
     6 : DISPLAY QSTATUS(B2.XMITQ) TYPE(HANDLE) ALL
AMQ8450: Display queue status details.
   QUEUE(B2.XMITQ)                    TYPE(HANDLE)
   APPLDESC( )                             APPLTAG(DataFlowEngine)
   APPLTYPE(USER)                          BROWSE(NO)
   CHANNEL( )                              CONNAME( )
   ASTATE(NONE)                            HSTATE(INACTIVE)
   INPUT(NO)                               INQUIRE(YES)
   OUTPUT(YES)                             PID(13107346)
   QMURID(0.379370499)                     SET(NO)
   TID(22)
   URID(XA_FORMATID[] XA_GTRID[] XA_BQUAL[])
   URTYPE(QMGR)                            USERID(wbimbprd)
AMQ8450: Display queue status details.
   QUEUE(B2.XMITQ)                    TYPE(HANDLE)
   APPLDESC( )                             APPLTAG(DataFlowEngine)
   APPLTYPE(USER)                          BROWSE(NO)
   CHANNEL( )                              CONNAME( )
   ASTATE(NONE)                            HSTATE(INACTIVE)
   INPUT(NO)                               INQUIRE(YES)
   OUTPUT(YES)                             PID(13107346)
   QMURID(0.379371600)                     SET(NO)
   TID(20)
   URID(XA_FORMATID[] XA_GTRID[] XA_BQUAL[])
   URTYPE(QMGR)                            USERID(wbimbprd)
AMQ8450: Display queue status details.
   QUEUE(B2.XMITQ)                    TYPE(HANDLE)
   APPLDESC(WebSphere MQ Channel)          APPLTAG(runmqchl)
   APPLTYPE(SYSTEM)                        BROWSE(NO)
   CHANNEL(A2.B2)                   CONNAME(172.XXX.4.YYY(1414))
   ASTATE(NONE)                            HSTATE(INACTIVE)
   INPUT(EXCL)                             INQUIRE(YES)
   OUTPUT(YES)                             PID(5636192)
   QMURID(0.379369572)                     SET(YES)
   TID(1)
   URID(XA_FORMATID[] XA_GTRID[] XA_BQUAL[])
   URTYPE(QMGR)


when their were no Uncommited messages ,i got following output.

Code:
 DISPLAY QSTATUS(B2.XMITQ) TYPE(HANDLE) ALL
     4 : DISPLAY QSTATUS(B2.XMITQ) TYPE(HANDLE) ALL
AMQ8450: Display queue status details.
   QUEUE(B2.XMITQ)                    TYPE(HANDLE)
   APPLDESC(WebSphere MQ Channel)          APPLTAG(runmqchl)
   APPLTYPE(SYSTEM)                        BROWSE(NO)
   CHANNEL(A2.B2)                   CONNAME(172.XXX.4.YYY(1414))
   ASTATE(NONE)                            HSTATE(ACTIVE)
   INPUT(EXCL)                             INQUIRE(YES)
   OUTPUT(YES)                             PID(5636192)
   QMURID(0.379367447)                     SET(YES)
   TID(1)
   URID(XA_FORMATID[] XA_GTRID[] XA_BQUAL[])
   URTYPE(QMGR)
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Mar 25, 2016 4:50 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

And remember that if your flow is transactional and your mqoutput node do not specify to work outside of the transaction, it is expected that the message will be in uncommitted state until the flow commits. Usually that is a very short time.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
gag_nm
PostPosted: Fri Mar 25, 2016 4:57 am    Post subject: Reply with quote

Centurion

Joined: 16 Oct 2008
Posts: 102

i have run below command when Uncommitted messages are in queue.
Code:

DISPLAY CHSTATUS(A2.B2) ALL
     8 : DISPLAY CHSTATUS(A2.B2) ALL
AMQ8417: Display Channel Status details.
   CHANNEL(A2.B2)                   CHLTYPE(SDR)
   BATCHES(20)                             BATCHSZ(1)
   BUFSRCVD(22)                            BUFSSENT(23)
   BYTSRCVD(1032)                          BYTSSENT(20755)
   CHSTADA(2016-03-25)                     CHSTATI(16.23.20)
   COMPHDR(NONE,NONE)                      COMPMSG(NONE,NONE)
   COMPRATE(0,0)                           COMPTIME(0,0)
   CONNAME(172.XXX.4.YYY(1414))            CURLUWID(56F424AC1000B314)
   CURMSGS(1)                              CURRENT
   CURSEQNO(314608)                        EXITTIME(0,0)
   HBINT(300)                              INDOUBT(YES)
   JOBNAME(00F5005200000001)               LOCLADDR(172.XX.17.YY(50327))
   LONGRTS(999999999)                      LSTLUWID(56F424AC1000B313)
   LSTMSGDA(2016-03-25)                    LSTMSGTI(16.29.01)
   LSTSEQNO(314607)                        MCASTAT(RUNNING)
   MONCHL(OFF)                             MSGS(20)
   NETTIME(0,0)                            NPMSPEED(FAST)
   RQMNAME(B2)                             SHORTRTS(10)
   SSLCERTI( )                             SSLKEYDA( )
   SSLKEYTI( )                             SSLPEER( )
   SSLRKEYS(0)                             STATUS(RUNNING)
   STOPREQ(NO)                         SUBSTATE(RECEIVE)
   XBATCHSZ(0,0)                           XMITQ(B2.XMITQ)
   XQTIME(0,0)                             RVERSION(07050002)
   RPRODUCT(MQMM)


I have run Same Command when No Uncommited messages in Queue.


Code:

DISPLAY CHSTATUS(A2.B2) ALL
     7 : DISPLAY CHSTATUS(A2.B2) ALL
AMQ8417: Display Channel Status details.
   CHANNEL(A2.B2)                   CHLTYPE(SDR)
   BATCHES(13)                             BATCHSZ(1)
   BUFSRCVD(16)                            BUFSSENT(16)
   BYTSRCVD(864)                           BYTSSENT(13642)
   CHSTADA(2016-03-25)                     CHSTATI(16.02.20)
   COMPHDR(NONE,NONE)                      COMPMSG(NONE,NONE)
   COMPRATE(0,0)                           COMPTIME(0,0)
   CONNAME(172.17.4.86(1428))              CURLUWID(56F424AC1000B10E)
   CURMSGS(0)                              CURRENT
   CURSEQNO(314564)                        EXITTIME(0,0)
   HBINT(300)                              INDOUBT(NO)
   JOBNAME(0116001000000001)               LOCLADDR(172.XX.17.YY(49927))
   LONGRTS(999999999)                      LSTLUWID(56F424AC1000B10D)
   LSTMSGDA(2016-03-25)                    LSTMSGTI(16.05.34)
   LSTSEQNO(314564)                        MCASTAT(RUNNING)
   MONCHL(OFF)                             MSGS(13)
   NETTIME(0,0)                            NPMSPEED(FAST)
   RQMNAME(B2)                             SHORTRTS(10)
   SSLCERTI( )                             SSLKEYDA( )
   SSLKEYTI( )                             SSLPEER( )
   SSLRKEYS(0)                             STATUS(RUNNING)
   STOPREQ(NO)                             SUBSTATE(MQGET)
   XBATCHSZ(0,0)                           XMITQ(B2.XMITQ)
   XQTIME(0,0)                             RVERSION(07050002)
   RPRODUCT(MQMM)


difference i could see mainly on INDOUBT and SUBSTATE.

The channel goes in to INDOUBT(YES) status and automatically it comes back to INDOUBT(NO).

I guess something to do with Network or Sequence Number.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Mar 25, 2016 5:10 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

gag_nm wrote:
...

difference i could see mainly on INDOUBT and SUBSTATE.

The channel goes in to INDOUBT(YES) status and automatically it comes back to INDOUBT(NO).

I guess something to do with Network or Sequence Number.


Not necessarily. If the channel is not in retrying status, it is normal for it to cycle through those states.
Did you check that you were not sending any messages to a full queue?
Are there any messages in the target's queue manager's Dead Letter Queue??
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » General IBM MQ Support » Queue depth increasing at Transmission Queue
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.