SIGSEGV abends in WMB Execution Group - XaJDBCSwitchInitialise
Your WebSphere Message Broker (WMB) Execution Group(s) is/are abending during startup.
Abend files show a Signal 11 (SIGSEGV) was received with the following method on the stack:
There is a contention on the server/port file: '/var/mqm/JDBC_XA_SWITCH_SPMF2'.
This issue was reported on a machine which had lost the SAN Volume Controller (SVC) for the Storage Area Network (SAN), and on which /var/mqsi/ had been restored from backup.
Diagnosing the problem
A WMB Startup Trace will show:
'ipcKeyForGlobalSem_SP_W = <#>'
'Attached shared memory pre-allocated by different process at <#>, Number rows <#>'
'clearing the shared server memory row=<#>'
Resolving the problem
Stop your Broker(s).
- Move the file 'JDBC_XA_SWITCH_SPMF2' from /var/mqm/ to a safe, backup location.
- Restart your Broker(s).
Note: During startup, a new copy of 'JDBC_XA_SWITCH_SPMF2' should be created.
|Business Integration||IBM Integration Bus||AIX, Linux, Solaris||9.0|
WMB MB WebSphere Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI
More support for:
WebSphere Message Broker
DB Connectivity / ODBC / JDBC
Software version: 6.1, 7.0, 8.0
Operating system(s): AIX, Linux, Solaris
Reference #: 1516243
Modified date: 16 January 2015
Translate this page: