Posted: Tue Apr 22, 2014 12:22 am Post subject: JMS app is getting delayed in consuming messages from MQ
Apprentice
Joined: 11 Apr 2013 Posts: 37
Hi Folks,
I have a scenario where JMS application is picking message from MQ. The issue is it is getting delayed in consuming messages like for 250 messages are picked in 2 hours which is very slow.
The connection is fine as application is able to pick messages. I have checked the mq logs and did nt find anything regarding the SVRCONN channel being used.
The mq version is : WebSphere MQ 7.0.1.1.
Type of logging is Linear.
I found the below in the logs :
----- amqrmrsa.c : 525 --------------------------------------------------------
04/20/14 13:26:32 - Process(12320914.7) User(mqm) Program(amqzmuc0)
Host(appcona)
AMQ7467: The oldest log file required to start queue manager ETDW_B2B_PROD_QM1
is S0000091.LOG.
EXPLANATION:
The log file S0000091.LOG contains the oldest log record required to restart
the queue manager. Log records older than this may be required for media
recovery.
ACTION:
You can move log files older than S0000091.LOG to an archive medium to release
space in the log directory. If you move any of the log files required to
recreate objects from their media images, you will have to restore them to
recreate the objects. An older log file is one with a numerically smaller log
number (but allowing for log number wrapping at 9999999).
-------------------------------------------------------------------------------
04/20/14 13:26:32 - Process(12320914.7) User(mqm) Program(amqzmuc0)
Host(appcona)
AMQ7468: The oldest log file required to perform media recovery of queue
manager ETDW_B2B_PROD_QM1 is S0000000.LOG.
EXPLANATION:
The log file S0000000.LOG contains the oldest log record required to recreate
any of the objects from their media images. Any log files prior to this will
not be accessed by media recovery operations.
ACTION:
Use this information together with the information in the most recent AMQ7467
message. Archivable log files are all those older than BOTH S0000000.LOG and
the log file mentioned in the AMQ7467 message.
-------------------------------------------------------------------------------
Kindly let me know if I can give any input.
Kindly suggest.
[/b]
MQ 7.0.1.1 is very old - maybe four/five years old?
Apply fixpack 11 before going any further. _________________ Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
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