| Author |
Message |
 Topic: SIGSEGV address not mapped - issue with process amqrmppa |
parker
Replies: 10
Views: 11312
|
 Forum: General IBM MQ Support Posted: Thu Sep 20, 2012 6:36 pm Subject: SIGSEGV address not mapped - issue with process amqrmppa |
| Fix provided in PMR: Looking at the initial FDC it is possible that part of one of WMQ's data structure has been overwritten by a transmission buffer. Advised to turn *off* all channel shared conversa ... |
| Topic: SIGSEGV address not mapped - issue with process amqrmppa |
parker
Replies: 10
Views: 11312
|
Forum: General IBM MQ Support Posted: Tue Sep 11, 2012 5:18 pm Subject: SIGSEGV address not mapped - issue with process amqrmppa |
| Yes, IBM checked the FDCs from 7.0.1.9, stackit data was not workth for their investigation. they have asked to capture the trace. I am in the process of sending the trace data. |
| Topic: SIGSEGV address not mapped - issue with process amqrmppa |
parker
Replies: 10
Views: 11312
|
Forum: General IBM MQ Support Posted: Mon Sep 10, 2012 1:00 pm Subject: SIGSEGV address not mapped - issue with process amqrmppa |
thanks for yr reply. Sorry for that mess 
Thirdly: the GET failed on object FTS.DATA, so what is QL.A.DATA used for?
ans:my mistake FTS.DATA is QL.A.DATA i missed to change it.
And, lastly: ... |
| Topic: SIGSEGV address not mapped - issue with process amqrmppa |
parker
Replies: 10
Views: 11312
|
Forum: General IBM MQ Support Posted: Mon Sep 10, 2012 2:06 am Subject: SIGSEGV address not mapped - issue with process amqrmppa |
The MQ client versions are 7.0.1.1 and MQ Server version is 7.0.1.9.
Below is the FDC content:
+-----------------------------------------------------------------------------+
| ... |
| Topic: SIGSEGV address not mapped - issue with process amqrmppa |
parker
Replies: 10
Views: 11312
|
Forum: General IBM MQ Support Posted: Mon Sep 10, 2012 2:01 am Subject: SIGSEGV address not mapped - issue with process amqrmppa |
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 c ... |
