db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-15) May get a non-uniue conglomerate id in a very unlikely XA edge case
Date Mon, 15 Oct 2007 19:47:50 GMT

     [ https://issues.apache.org/jira/browse/DERBY-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kathey Marsden resolved DERBY-15.
---------------------------------

    Resolution: Won't Fix

Seems unlikely that this will get fixed. It can be reopened if someone decided to fix it.


> May get a non-uniue conglomerate id in a very unlikely XA edge case
> -------------------------------------------------------------------
>
>                 Key: DERBY-15
>                 URL: https://issues.apache.org/jira/browse/DERBY-15
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.0.2.0
>            Reporter: Tulika Agrawal
>            Priority: Minor
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message