| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ Client for Java: long running transations in amqrmppa |
« View previous topic :: View next topic » |
| Author |
Message
|
| Sosed |
 Posted: Wed Dec 25, 2013 4:11 am Post subject: MQ Client for Java: long running transations in amqrmppa |
 |
|
Apprentice
Joined: 24 Aug 2012
Posts: 43
|
Hi,
I use MQ 7.5.0.0 and WMB 8.0.0.2
I have several JMS queue definitions for MQ and one connection factory (CF uses channel SYSTEM.DEF.SVRCONN). There are about 100 flows connected to JMS queues.
Flows stop get mesage from queues after a while, when I run load test.
In QM error log id found:
| Quote: |
AMQ7469: Transactions rolled back to release log space.
EXPLANATION:
The log space for the queue manager is becoming full. One or more long-running
transactions have been rolled back to release log space so that the queue
manager can continue to process requests.
ACTION:
Try to ensure that the duration of your transactions is not excessive. Consider
increasing the size of the log to allow transactions to last longer before the
log starts to become full.
-------------------------------------------------------------------------------
|
| Quote: |
AMQ7486: Transaction 0.8732 was preventing log space from being released.
EXPLANATION:
A long running transaction was detected. Message AMQ7469 or AMQ7485 has been
issued indicating if the transaction was rolled back or rolled forward in the
log to allow the log space to be released. The internal transaction identifier
is 0.8732 which can be correlated with 'dspmqtrn -a' output. The transaction
started at 19.11.41 and first wrote to the queue manager recovery
log at 19.16.35. The following transaction context may be useful
in identifying the application causing this behaviour: TRANNUM(0.8732) . This
message can be correllated with the previous AMQ7469 or AMQ7485 message in the
queue manager error logs.
ACTION:
Identify the application responsible for the long running unit of work and
ensure this application is creating and completing transactions in a timely
manner. If the application is working as expected it may be appropriate to
increase the size of the queue manager recovery log.
|
| Quote: |
AMQ7487: Application WebSphere MQ Client for Java was preventing log space
from being released.
EXPLANATION:
A long running transaction was detected, this message is intended to help
identify the application associated with this long running transaction. Message
AMQ7469 or AMQ7485 has been issued indicating if the transaction was rolled
back or rolled forward in the log to allow the log space to be released.
Message AMQ7486 has been issued identifying the transaction context of the
transaction that was rolled back or rolled forwards. The application associated
with this transaction was running with Pid 26055, Tid 32, under application
name WebSphere MQ Client for Java, and under user identifier mqm. The following
application context may also be useful in identifying the application causing
this behaviour: CHANNEL(SYSTEM.DEF.SVRCONN) CONNAME(127.0.0.1)
APPLDESC(WebSphere MQ Channel). This message can be correllated with the
previous AMQ7486 message in the queue manager error logs.
ACTION:
Identify the application responsible for the long running unit of work and
ensure this application is creating and completing transactions in a timely
manner. If the application is working as expected it may be appropriate to
increase the size of the queue manager recovery log.
|
I had tried to increase the size of QM log by adding extra Secondary log files, but it didn't help - qm logs became full again.
Process, who resposible for log running transaction is amqrmppa.
So, i have several questions:
1. Why it happens? Does it happen because of number of connections through channel?
2. If it is, Should I use several CF (and channels)?
Any advice is appreciated!
Thanks in advance. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Dec 26, 2013 7:34 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20697
Location: LI,NY
|
amqrmppa is not responsible for your problem. It is clearly an application. It could be that the application is doing a put under syncpoint and never issues a commit or rollback.
amqrmppa is just a channel process. So your application is using a channel to connect to the qmgr.
It is never a good idea to have an application use a system channel for connection to the qmgr. Each application should have its own channel. This way you can force shut down a channel that is left hanging open without impacting another app.
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
|
|
|
|
