db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From derby-...@db.apache.org
Subject [jira] Created: (DERBY-15) May get a non-uniue conglomerate id in a very unlikely XA edge case
Date Wed, 29 Sep 2004 18:56:32 GMT
Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DERBY-15

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DERBY-15
    Summary: May get a non-uniue conglomerate id in a very unlikely XA edge case
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Derby
 Components: 
             Store
   Versions:
             10.0.2.0

   Assignee: 
   Reporter: Tulika Agrawal

    Created: Wed, 29 Sep 2004 11:56 AM
    Updated: Wed, 29 Sep 2004 11:56 AM

Description:
Reporting for Mike Matrigali.

If upon reboot of the system a prepared but uncommitted 
transaction contains a drop of the conglomerate in the system 
with the highest Id in the system, and if a create conglomerate is then executed it will reused
the conglomerate id of the dropped conglomerate. The system will work correctly once the outstanding
prepared xact is committed or aborted.

Note:
It seems unlikely for users to in general include ddl in XA 
transactions, 
and even more rare for it to be the last conglomerate created, 
and even
more rare for the offending transaction to be left in prepared 
state across
a system shutdown.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message