Message from discussion Problem with QMUX Asynch Request - Expired msg doesn't get called

MIME-Version: 1.0
Received: by 10.151.128.8 with SMTP id f8mr757590ybn.20.1245983898493; Thu, 25 
	Jun 2009 19:38:18 -0700 (PDT)
Date: Thu, 25 Jun 2009 19:38:16 -0700 (PDT)
X-IP: 121.122.43.149
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) 
	AppleWebKit/530.5 (KHTML, like Gecko) Chrome/2.0.172.33 Safari/530.5,gzip(gfe),gzip(gfe)
Message-ID: <68dadd49-6c90-4cca-87f7-c86d45871ecc@p5g2000pre.googlegroups.com>
Subject: Problem with QMUX Asynch Request - Expired msg doesn't get called
From: LiNa <lyn...@gmail.com>
To: jPOS Users <jpos-users@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi,

I am currently working on SAF process. I am modifying jpos-ee SAF from
QMUX synch request to QMUX asynch request and integrate with
ISOResponseListener. The ISOResponseListener class extends QBean so
that it will get deployed during Q2 startup and configurable.

Everything works fine until there are messages in QMUX waiting to get
expired and there is new messages put in the QMUX request. Once that
happens, the ISOResponseListener expired method get called later and
later. I have configured the timeout to be 50 seconds, but once this
happens it gets timeout like after 5 min, 13 min, 30 min...

Has anyone experiencing this problem before? I am suspecting it is
something to do with synchronized(ar) function in QMux request method.
Please share.

Thanks

Regards,