Resolution:
Description:
==========
Deadlock message and subsequent retry while using SQL Server with TIBCO BusinessEvents.

Environment:
==========
TIBCO BusinessEvents 5.x
All Operating Systems
SQL server

Symptoms:
=========

Warning 1 (deadlock)
2013 Jun 11 15:07:04:158 GMT -4 ODS-cache1 Warning [Thread-7] - [jdbcstore] Attempt 0, failed to get Object of id=THAE-826-2013-06-10 error=Transaction (Process ID 134) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction., try again...

Resolution:
==========
To avoid the above deadlock message make the following changes to your database .

- Set Isolation levels.

    ALTER DATABASE MyDatabase
    SET ALLOW_SNAPSHOT_ISOLATION ON

    ALTER DATABASE MyDatabase
    SET READ_COMMITTED_SNAPSHOT ON

- Verify snapshot transaction isolation.

select sys.databases.snapshot_isolation_state,
       sys.databases.snapshot_isolation_state_desc
    from sys.databases
       where (sys.databases.[name] = '&ltMyDatabase>')

- Verify read committed transactions to use snapshots select.

sys.databases.is_read_committed_snapshot_on
    from sys.databases
       where (sys.databases.[name] = '&ltMyDatabase>')

Note: These changes increases the size of tempdb.

References :
==========
http://msdn.microsoft.com/en-us/library/tcbchxcb(v=VS.80).aspx
http://msdn.microsoft.com/en-us/library/ms188277.aspx