[ http://jira.jboss.com/jira/browse/JBAS-1368?page=history ]
Scott M Stark resolved JBAS-1368:
---------------------------------
Resolution: Done
The table creation ddl statements in the sybase-jdbc2-service.xml sample have
been updated as suggested by John Majerus.
CREATE_MESSAGE_TABLE = CREATE TABLE dbo.JMS_MESSAGES ( MESSAGEID INTEGER NOT
NULL, \
DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER NULL, TXOP CHAR(1), \
MESSAGEBLOB IMAGE, PRIMARY KEY (MESSAGEID, DESTINATION) ) LOCK DATAROWS
CREATE_TX_TABLE = CREATE TABLE dbo.JMS_TRANSACTIONS ( TXID INTEGER, PRIMARY KEY
(TXID) ) \
LOCK DATAROWS
> Deadlocks in Message Persistence when working with Sybase
> ---------------------------------------------------------
>
> Key: JBAS-1368
> URL: http://jira.jboss.com/jira/browse/JBAS-1368
> Project: JBoss Application Server
> Type: Bug
> Components: JMS service
> Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final
> Environment: JBoss 3.2.6 with Sybase 12.5
> Reporter: Eran Haggiag
> Fix For: JBossAS-4.0.2RC1, JBossAS-3.2.8 Final
>
>
> This problem is new in 3.2.6 and was not in 3.2.3.
> This problem happans on high load.
> Example from the Sybase log :
> ========================= deadlock #1009 =========================
> 00:00000:00223:2005/01/20 09:51:58.82 server Deadlock Id 1009 detected
> Deadlock Id 1009: detected. 1 deadlock chain(s) involved.
> Deadlock Id 1009: Process (Familyid 1752, 1752) (suid 25) was executing a
> UPDATE command at line 1.
> SQL Text: UPDATE JMS_MESSAGES SET [EMAIL PROTECTED], [EMAIL PROTECTED] WHERE
> [EMAIL PROTECTED] AND [EMAIL PROTECTED]
> Deadlock Id 1009: Process (Familyid 223, 223) (suid 25) was executing a
> DELETE command at line 1.
> SQL Text: DELETE FROM JMS_TRANSACTIONS WHERE TXID = @p0?
> Deadlock Id 1009: Process (Familyid 0, Spid 223) was waiting for a 'update
> page' lock on page 12889 of the 'JMS_TRANSACTIONS' table in database 4 but
> process (Familyid 1752, Spid 1752) already held a 'exclusive page' lock on it.
> Deadlock Id 1009: Process (Familyid 0, Spid 1752) was waiting for a 'update
> page' lock on page 12905 of the 'JMS_MESSAGES' table in database 4 but
> process (Familyid 223, Spid 223) already held a 'exclusive page' lock on it.
> Deadlock Id 1009: Process (Familyid 0, 1752) was chosen as the victim. End of
> deadlock information.
> ****************************************************************
> * Resume starts (Deadlock 1009)
> ****************************************************************
> *
> * locked_page-> 12889 locked_table-> 'JMS_TRANSACTIONS'
> * locked_page-> 12905 locked_table-> 'JMS_MESSAGES'
> *
> ****************************************************************
> * Resume ends (Deadlock 1009)
> ****************************************************************
> ========================= deadlock #1009 =========================
> ========================= deadlock #1010 =========================
> 06:00000:00100:2005/01/20 09:51:59.83 server Deadlock Id 1010 detected
> Deadlock Id 1010: detected. 1 deadlock chain(s) involved.
> Deadlock Id 1010: Process (Familyid 223, 223) (suid 25) was executing a
> DELETE command at line 1.
> SQL Text: DELETE FROM JMS_TRANSACTIONS WHERE TXID = @p0?
> Deadlock Id 1010: Process (Familyid 100, 100) (suid 25) was executing a
> UPDATE command at line 1.
> SQL Text: UPDATE JMS_MESSAGES SET [EMAIL PROTECTED], [EMAIL PROTECTED] WHERE
> [EMAIL PROTECTED] AND [EMAIL PROTECTED]
> Deadlock Id 1010: Process (Familyid 0, Spid 100) was waiting for a 'update
> page' lock on page 12905 of the 'JMS_MESSAGES' table in database 4 but
> process (Familyid 223, Spid 223) already held a 'exclusive page' lock on it.
> Deadlock Id 1010: Process (Familyid 0, Spid 223) was waiting for a 'update
> page' lock on page 12889 of the 'JMS_TRANSACTIONS' table in database 4 but
> process (Familyid 100, Spid 100) already held a 'exclusive page' lock on it.
> Deadlock Id 1010: Process (Familyid 0, 223) was chosen as the victim. End of
> deadlock information.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
