MQSeries.net :: View topic - SIGSEGV address not mapped

parker · Posted: Mon Sep 10, 2012 2:06 am Post subject:

Hello All,
The issue occurs after MQ 6.0 upgrade to version 7.0.1.4
Initially the PMR said to try upgrade to 7.0.1.9 But it didn't help. also asked to reduce TRIGINT to 99999.
We tought of considering to reduce TRIGINT to 99999 but I
found the situation where extra trigger message generation is not going to be help in this issue.
Let me put togather my investigation:

1) There comes a message to queue QL.A.DATA but message
did not get processed by the attached trigger process FTS.A.DELIVER

2) Found the application a.exe connected to the queue but it did not process the message (later I found the process is dead already at time of FDC). a.exe is appeared in the Window task manager in
the client machine. But it did not process the messages from queue.

3) Found the process id 32137 attached to the queue (found from Q's usage) is running in the MQ server machine.
mqm@somehost~:> ps -ef| grep 32137
mqm 6205 3015 0 08:16 pts/0 00:00:00 grep 32137
mqm 32137 30808 0 05:00 ? 00:00:12 /opt/mqm/bin/amqrmppa -
m SOMEQMGR
But there is AMQ32137.0.FDC file generated by the process 32317 at
the time of issue.

4) At the time there is event error for client trigger monitor (also in client's AMQERR01.LOG) in the client machine:
Starting: a.cmd XXXXX "TMC 2QL.A.DATA FTS.A.DELIVER d:\...\..\a.cmd XXXXX XXXXX SOMEQMGR " .
---
The description for Event ID ( 3 ) in Source ( YYYY ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: KFT0003, Failed: MQSeries comp code 2, reason 2009. Function MQGET, on object FTS.DATA.
---
Channel 'SO-CALLED-SVRCONN-CHL' timed out.

A timeout occurred while waiting to receive from the other end of channel 'SO-CALLED-SVRCONN-CHL'. The address of the remote end of the connection was 'aa.bb.cc.dd(1414)'.

The return code from the select() [TIMEOUT] 60 seconds call was 0 (X'0'). Record these values and tell the systems administrator.
---
Remote host 'someclienthost (ee.ff.gg.hh) (1414)' not available, retry later.

The attempt to allocate a conversation using TCP/IP to host 'someclienthost (ee.ff.gg.hh) (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.

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 10061 (X'274D'). 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 'someclienthost (ee.ff.gg.hh) (1414)' was not running. If this is the case, perform the relevant operations to start the TCP/IP listening program, and try again.

5) Retriggering did not work for the queue QL.A.DATA with
curdepth 1
Because the broken application has the queue open for input (
IPPROCS(1) )and is still appearing in the queue's usage (never ended).

6) When trig type is changed from FIRST to EVERY, then retriggered
the queue - a new a.exe appeared in the usage and message got
processed and the new process disappeared shortly but the broken
process still there to stop the next initiation message.

in short form the client's connection getting
broken and worse is not leaving from the queue's usage. Could anyone help me on this?