db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Waagan <Kristian.Waa...@Sun.COM>
Subject Re: [jira] Updated: (DERBY-1280) Derby throws "ERROR XSDG1: Page could not be written to disk, please check if disk is full" when there is 20+ gigs of free space ibm 1.5 JVM
Date Tue, 19 Sep 2006 16:19:27 GMT
Mike Matrigali (JIRA) wrote:
>      [ http://issues.apache.org/jira/browse/DERBY-1280?page=all ]
> Mike Matrigali updated DERBY-1280:
> ----------------------------------
>     Derby Info: [Release Note Needed]
> What is the right way of "closing" an issue that we have verified is a JVM bug.  


I would also like to know this, as I know of a few other Jiras that 
could be closed with the same conclusion. I was leaning towards using 
"Won't fix" or 'Invalid', but none of them seemed quite right so I 
postponed the closing.

> Fixed definitely seems wrong.  In other bug tracking systems I have used there has been
a category that indicates that it is a real problem, but not with the product but instead
the OS/JVM.  It would be nice to get a release note out there indicating that on this version
of the JVM derby will not be able to access files greater than 2 gig.
[ snip DERBY-1280 details ]

View raw message