| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| channels keep aborting for one particular QMGR MQ V6 SunOS |
« View previous topic :: View next topic » |
| Author |
Message
|
| John89011 |
 Posted: Tue Aug 25, 2009 7:32 am Post subject: channels keep aborting for one particular QMGR MQ V6 SunOS |
 |
|
Voyager
Joined: 15 Apr 2009
Posts: 94
|
My sender channels keep aborting for one particular QMGR and this is what I see the QMGR erorr log files:
08/25/09 06:31:51 AM - Process(24868.1) User(mqm) Program(runmqchl_nd)
AMQ9202: Remote host '10 (00.000.000.000) (0000)' not available, retry later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host '10
(00.000.000.000) (0000)' was not successful. However the error may be a
transitory one and it may be possible to successfully allocate a TCP/IP
conversation later.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
145 (X'91'). The reason for the failure may be that this host cannot reach the
destination host. It may also be possible that the listening program at host
'10 (00.000.000.000) (0000)' was not running. If this is the case, perform the
relevant operations to start the TCP/IP listening program, and try again.
----- amqccita.c : 1088 -------------------------------------------------------
08/25/09 06:31:51 AM - Process(24868.1) User(mqm) Program(runmqchl_nd)
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'xx.xx' ended abnormally.
ACTION:
Look at previous error messages for channel program 'xx.xx' in the
error files to determine the cause of the failure.
----- amqrccca.c : 777 --------------------------------------------------------
08/25/09 06:32:32 AM - Process(16131.22507) User(mqm) Program(amqrmppa)
AMQ9202: Remote host '10 (00.000.0.00) (1414)' not available, retry later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host '10 (00.000.0.000)
(1414)' was not successful. However the error may be a transitory one and it
may be possible to successfully allocate a TCP/IP conversation later.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
145 (X'91'). The reason for the failure may be that this host cannot reach the
destination host. It may also be possible that the listening program at host
'10 (00.000.0.00) (1414)' was not running. If this is the case, perform the
relevant operations to start the TCP/IP listening program, and try again.
----- amqccita.c : 1088 -------------------------------------------------------
08/25/09 06:32:32 AM - Process(16131.22507) User(mqm) Program(amqrmppa)
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program ‘xx.xx' ended abnormally.
ACTION:
Look at previous error messages for channel program ‘xx.xx’ in the
error files to determine the cause of the failure.
----- amqrccca.c : 777 --------------------------------------------------------
08/25/09 06:32:46 AM - Process(16076.5) User(mqm) Program(amqzmuc0)
AMQ7467: The oldest log file required to start queue manager XX is
S0341476.LOG.
EXPLANATION:
The log file S0341476.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 S0341476.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.
-------------------------------------------------------------------------------
08/25/09 06:32:46 AM - Process(16076.5) User(mqm) Program(amqzmuc0)
AMQ7468: The oldest log file required to perform media recovery of queue
manager XX 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:
You can move log files older than S0000000.LOG to an archive medium to release
space in the log directory.
-------------------------------------------------------------------------------
08/25/09 06:32:46 AM - Process(16076.5) User(mqm) Program(amqzmuc0)
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.
-------------------------------------------------------------------------------
08/25/09 06:34:21 AM - Process(16131.22508) User(mqm) Program(amqrmppa)
AMQ9002: Channel ‘xx.xx’ is starting.
EXPLANATION:
Channel ‘xx.xx’ is starting.
Any suggestion where to start looking first?
Thanks! |
|
| Back to top |
|
 |
| Sam Uppu |
| Posted: Tue Aug 25, 2009 7:40 am Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
Is this a new setup?.
Did you check whether the firewall/ port is opened between the two QMgrs if they are running on different machines?.
May be try telnet <remoteHost> <remoteqmgr's port#>
It should show "connected" if the port is opened(the listener should be up and running on remote qmgr).
Thanks. |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Tue Aug 25, 2009 7:41 am Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
| From the Qmgr logs, it shows that you dont have enough space for the logs. Try to increase the number of logs as they are filled up with the long running transactions. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Aug 25, 2009 7:48 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
THIS may (or may not) be of some help to you, and as Sam Uppu has observed, your linear-logged queue manager is running out of space in its log directory. Hit the SupportPac page for linear log management tools.
_________________
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 |
|
|
| sumit |
| Posted: Tue Aug 25, 2009 7:49 am Post subject: Re: channels keep aborting for one particular QMGR MQ V6 Sun |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
| John89011 wrote: |
08/25/09 06:31:51 AM - Process(24868.1) User(mqm) Program(runmqchl_nd)
AMQ9202: Remote host '10 (00.000.000.000) (0000)' not available, retry later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host '10
(00.000.000.000) (0000)' was not successful. However the error may be a
transitory one and it may be possible to successfully allocate a TCP/IP
conversation later.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
145 (X'91'). The reason for the failure may be that this host cannot reach the
destination host. It may also be possible that the listening program at host
'10 (00.000.000.000) (0000)' was not running. If this is the case, perform the
relevant operations to start the TCP/IP listening program, and try again.
----- amqccita.c : 1088 ------------------------------------------------------- |
I have seen that most of the time, listener is the culprit. check if it is running or not.
MQ logs generally contains the exact/near to exact reason of failure. Try reading the logs properly and you will be able to rectify the problem.
_________________
Regards
Sumit |
|
| 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
|
|
|
|
