SIGSEGV abends in WMB Execution Group - XaJDBCSwitchInitialise

Technote (troubleshooting)


Problem(Abstract)

Your WebSphere Message Broker (WMB) Execution Group(s) is/are abending during startup.

Symptom

Abend files show a Signal 11 (SIGSEGV) was received with the following method on the stack:

updateSharedServerPortMemory
Java_com_ibm_broker_jdbctype4_xahandler_JDBCType4XAHandler_XaJDBCSwitchInitialise
[/opt/IBM/mqsi/6.1/lib/libXAJdbcJni64.so]

Cause

There is a contention on the server/port file: '/var/mqm/JDBC_XA_SWITCH_SPMF2'.

Environment

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:

XAJdbcJni.initializeSharedMemoryLocks
'ipcKeyForGlobalSem_SP_W = <#>'

XAJdbcJni.GetSharedServerPortMemory
'Attached shared memory pre-allocated by different process at <#>, Number rows <#>'

XAJdbcJni.updateSharedServerPortMemory
'clearing the shared server memory row=<#>'


Resolving the problem

Stop your Broker(s).

  1. Move the file 'JDBC_XA_SWITCH_SPMF2' from /var/mqm/ to a safe, backup location.
  2. Restart your Broker(s).

Note: During startup, a new copy of 'JDBC_XA_SWITCH_SPMF2' should be created.

Product Alias/Synonym

WMB MB WebSphere Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI

Rate this page:

(0 users)Average rating

Document information


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:

2013-02-15

Translate my page

Machine Translation

Content navigation