Deadlock error is seen while system job (NJAMS_DATA

Products	Versions
TIBCO BusinessWorks ProcessMonitor	-
Not Applicable	-

Description

Description:
TIBCO BusinessWorks™ ProcessMonitor (BWPM) system job 'NJAMS_DATA_MANAGEMENT' is responsible for deleting older data from the database. A 'Data Retention' period setting in the BWPM Server GUI instructs the server how much data needs to be preserved. A deadlock can be reported by a system job when another TIBCO BusinessWorks™ (BW) process is trying to insert data into the same database partition area.

Symptoms:
A deadlock with the following stack trace can be seen in the server.log while the system job 'NJAMS_DATA_MANAGEMENT' is running.

**
2014-10-17 12:53:24.880 spid74       DBCC TRACEON 1222, server process ID (SPID) 74. This is an informational message only; no user action is required.
2014-10-17 12:53:34.500 spid20s      deadlock-list
2014-10-17 12:53:34.500 spid20s       deadlock victim=process5c3bb88
2014-10-17 12:53:34.500 spid20s        process-list
2014-10-17 12:53:34.500 spid20s         process id=process5c3bb88 taskpriority=10 logused=12028 waitresource=METADATA: database_id = 9 DATA_SPACE(data_space_id = 65601) waittime=4390 ownerId=680807826 transactionname=user_transaction lasttranstarted=2014-10-17T12:53:28.633 XDES=0x69d4ac780 lo
2014-10-17 12:53:34.500 spid20s          executionStack
2014-10-17 12:53:34.500 spid20s           frame procname=adhoc line=1 stmtstart=40 sqlhandle=0x01000900a628d726b0fef908070000000000000000000000
2014-10-17 12:53:34.500 spid20s      ALTER PARTITION FUNCTION PF_dbo_NJAMS_T_MONITOR_MAIN() MERGE RANGE (@DayParam)
2014-10-17 12:53:34.500 spid20s           frame procname=mssqlsystemresource.sys.sp_executesql line=1 sqlhandle=0x0400ff7fbe80662601000000000000000000000000000000
2014-10-17 12:53:34.500 spid20s      sp_executesql
2014-10-17 12:53:34.500 spid20s           frame procname=tibco_bwpmprod.dbo.PROC_DROP_PARTITION line=65 stmtstart=3346 stmtend=3500 sqlhandle=0x0300090087480f16839d0701bea300000100000000000000
2014-10-17 12:53:34.500 spid20s      EXECUTE sp_executesql @sql
****

Cause:
When another TIBCO BusinessWorks(BW) process is running longer than the set Data Retention period, it will try to insert its data into the BWPM database. The system job ''NJAMS_DATA_MANAGEMENT' tries to delete the database partition as per the set 'Data Retention' period.

For example, if Data Retention is set to 3 days but the TIBCO BusinessWorks™ (BW) process has been running for more than 3 days, then it is possible to see the deadlock while the system ''NJAMS_DATA_MANAGEMENT' is running.

Resolution

The TIBCO BusinessWorks™ ProcessMonitor (BWPM) GUI can be used to identify a running process for more than Data Retention days. A main view shows the currently running processes. Sort by Start Date to see the oldest process running in the BWPM environment. Once the TIBCO BusinessWorks™ (BW) process has been identified, it can be determined if the BW process running time meets the requirement as per the Design or BW process requirement. Correct to avoid longer running process times. Alternatively, the 'Data Retention' setting can be increased to avoid this conflict.

Issue/Introduction

Deadlock error is seen while system job (NJAMS_DATA_MANAGEMENT) is running.

Additional Information

NA

Welcome to "KB Articles"