[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-700:
-
Attachment: releaseNote.html
Attaching a new release note. The old one referred to the original
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-700:
-
Attachment: releaseNote.html
Looks good, but there were 2 typos...uploading a corrected
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-700:
-
Affects Version/s: (was: 10.4.1.3)
(was: 10.3.1.4)
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-700:
Attachment: derby-700-02-aa-testCleanup.diff
Thanks for those good suggestions, Knut. They are
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-700:
Attachment: derby-700-01-ab-catchOverlappingFileLockException.diff
Attaching
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-700:
-
The new code looks ok to me. Maybe the comment could say what we expect to
throw the
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-700:
Attachment: derby-700-01-aa-catchOverlappingFileLockException.diff
Attaching
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-700:
Issue fix info: [High Value Fix, Patch Available] (was: [High Value Fix])
Derby does not prevent
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-700:
Attachment: DualBootRepro.java
It appears to me that a workaround for this bug is to upgrade to
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-700:
Description:
Derby does not prevent dual boot from two different classloaders on Linux and
Mac OS
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-700:
-
Derby Categories: [Data corruption, High Value Fix] (was: [High Value Fix])
Derby does not
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-700:
-
Derby Info: [Existing Application Impact, Release Note Needed] (was:
[Release Note Needed,
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel John Debrunner updated DERBY-700:
Derby Info: [Existing Application Impact, Release Note Needed]
(was:
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-700:
-
Derby Info: [Existing Application Impact, Release Note Needed] (was:
[Release Note
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-700:
-
Derby Info: [Existing Application Impact, Release Note Needed] (was:
[Release Note
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-700:
-
Attachment: derby-700_06_19_2007
Mike asked me to post the patch that has changes from Dan's
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-700:
Attachment: releaseNote.html
Scrubbing release note so that it can be digested by the SAX parser in
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-700:
-
Derby Info: [Existing Application Impact, Release Note Needed] (was:
[Release Note Needed,
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-700:
-
Derby Info: [Existing Application Impact, Release Note Needed]
Applications will need to set a
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-700:
-
Attachment: releaseNote.html
release note
Derby does not prevent dual boot of database from
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-700:
-
Attachment: derby-700_06_07_07_diff.txt
Here is the latest patch for this issue. I think we are
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-700:
-
Attachment: derby-700_06_07_07_stat.txt
Derby does not prevent dual boot of database from
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-700:
-
keep in mind that if we make setting/reading the property optional it presents
a very mixed set of
Kathey Marsden wrote:
Francois Orsini wrote:
I haven't looked at the absolute latest changes and I was wondering
if the case of a database being opened in a separate classloader and
not having been shut down properly (due to unexpected exception in
the application) could impede some other
Kathey Marsden wrote:
Kathey Marsden wrote:
Francois Orsini wrote:
I haven't looked at the absolute latest changes and I was wondering
if the case of a database being opened in a separate classloader and
not having been shut down properly (due to unexpected exception in
the application)
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-700:
-
Fix Version/s: 10.3.0.0
Derby does not prevent dual boot of database from different
Yes, you are right - This is quite a corner case anyway and if it does
happen, proper action (such as removing the file physically) would have to
be done manually as in the case today (if running pre-1.4.2) which should
not be the case with 10.3 (if am not mistaken) - Hence, Derby will remove a
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-700:
-
Attachment: derby-700_with_NPE_fix_diff.txt
Attached is a patch that fixes the NPE, but there are
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-700:
-
Attachment: derby-700_with_NPE_fix_stat.txt
Derby does not prevent dual boot of database from
Kathey Marsden (JIRA) wrote:
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-700:
-
Attachment: derby-700_with_NPE_fix_diff.txt
Attached is a patch
Kathey Marsden (JIRA) wrote:
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-700:
-
Attachment: derby-700_with_NPE_fix_diff.txt
If
Mike Matrigali wrote:
Kathey Marsden (JIRA) wrote:
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-700:
-
Attachment: derby-700_with_NPE_fix_diff.txt
Daniel John Debrunner wrote:
Actually string constants are by definition interned, so
synchronized(DERBY_JVM_ID) is the same as
synchronized(DERBY_JVM_ID.intern()) since DERBY_JVM_ID is a reference
to a string constant. Though using intern() wouldn't harm and might
make the code more
Kathey Marsden wrote:
Daniel John Debrunner wrote:
Actually string constants are by definition interned, so
synchronized(DERBY_JVM_ID) is the same as
synchronized(DERBY_JVM_ID.intern()) since DERBY_JVM_ID is a reference
to a string constant. Though using intern() wouldn't harm and might
Daniel John Debrunner wrote:
Kathey Marsden wrote:
Daniel John Debrunner wrote:
Actually string constants are by definition interned, so
synchronized(DERBY_JVM_ID) is the same as
synchronized(DERBY_JVM_ID.intern()) since DERBY_JVM_ID is a
reference to a string constant. Though using
I haven't looked at the absolute latest changes and I was wondering if the
case of a database being opened in a separate classloader and not having
been shut down properly (due to unexpected exception in the application)
could impede some other classloader to open the very same database due to
Francois Orsini wrote:
I haven't looked at the absolute latest changes and I was wondering if
the case of a database being opened in a separate classloader and not
having been shut down properly (due to unexpected exception in the
application) could impede some other classloader to open the
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-700:
-
Attachment: derby-700_stat.txt
Derby does not prevent dual boot of database from different
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-700:
-
Attachment: derby-700_diff.txt
This patch is not yet ready for commit. The multithreaded test
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-700:
-
Attachment: derby.log
When the multithreaded failure occurs there is an NPE accessing the
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Thalamati updated DERBY-700:
---
Attachment: derby700_singleproperty_v1.stat
derby700_singleproperty_v1.diff
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-700:
-
Here is a description of a possible solution - any feedback is appreciated:
I would like to see some
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-700:
-
With respect to a global state in the jdbc driver when 2 class loaders are
involved, how would that
[ http://issues.apache.org/jira/browse/DERBY-700?page=all ]
Rick Hillegas updated DERBY-700:
Fix Version/s: 10.2.3.0
(was: 10.2.2.0)
Move to 10.2.3.0.
Derby does not prevent dual boot of database from different classloaders on
Rick Hillegas (JIRA) wrote:
It appears that fixing this bug will require us to agree on some mechanism for
caching VM-global Derby state. This seems to be an architectural decision which
requires careful thought and experiment. I think we should defer this to a
future release. I am moving
Yes, please! If I knew the JIRA magic to do this, I would mumble it.
Could someone teach me the magic, and if necessary, give me karma to mumble?
Thanks,
-Rick
Kathey Marsden wrote:
Rick Hillegas (JIRA) wrote:
It appears that fixing this bug will require us to agree on some
mechanism for
Rick Hillegas (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-700?page=all ]
Rick Hillegas updated DERBY-700:
Fix Version/s: 10.3.0.0
(was: 10.2.0.0)
It appears that fixing this bug will require us to agree on some
Mike Matrigali wrote:
If anyone has ideas on this one, please post them. I have been stumped
by this one so far. As I posted earlier I think one approach simply
needs a way to uniquely identify the current JVM, and also some way
to coordinate a sync block across 2 class loaders.
A Java
great, sounds like the sync part is a non-issue. I was stuck trying
to come up with something specific to the db shared across both
classloaders that we could sync on. Using this will single thread
opens of different dbs, but I think that is ok.
Daniel John Debrunner wrote:
Mike Matrigali
Mike Matrigali wrote:
great, sounds like the sync part is a non-issue. I was stuck trying
to come up with something specific to the db shared across both
classloaders that we could sync on. Using this will single thread
opens of different dbs, but I think that is ok.
Then I think you would
On 8/3/06, Rick Hillegas [EMAIL PROTECTED] wrote:
Yes, please! If I knew the JIRA magic to do this, I would mumble it.
Could someone teach me the magic, and if necessary, give me karma to mumble?
granted. the admin pages are your friends.
Kathey Marsden wrote:
Sounds like a reasonable move
Hi Rick,
Currently both Andrew and myself have JIRA-admin access, though Andrew
has been doing all the work lately.
I have been thinking of giving up my JIRA-admin access... May be the
right time now to switch it over to you, since you are the release
manager for 10.2.
Satheesh
Rick Hillegas
Hi,
Andrew McIntyre [EMAIL PROTECTED] writes:
Yep, that's right. I've added this version to JIRA. We need this also
to track the inevitable removal of our early-access language around
the JDBC 4 bits. Which reminds me...
Could you please also add an entry for version 11? Cf my need
Andrew McIntyre wrote:
On 8/3/06, Rick Hillegas [EMAIL PROTECTED] wrote:
Yes, please! If I knew the JIRA magic to do this, I would mumble it.
Could someone teach me the magic, and if necessary, give me karma to
mumble?
granted. the admin pages are your friends.
Can you please take me off
On 8/3/06, Satheesh Bandaram [EMAIL PROTECTED] wrote:
Can you please take me off from JIRA-admin group? JIRA says I can't
remove my own membership to this group!
done.
[ http://issues.apache.org/jira/browse/DERBY-700?page=all ]
Rick Hillegas updated DERBY-700:
Fix Version/s: 10.2.2.0
(was: 10.3.0.0)
Thanks for creating the new 10.2.2.0 option, Andrew! I've reassigned this issue
to that release.
Andrew McIntyre wrote:
On 8/3/06, Rick Hillegas [EMAIL PROTECTED] wrote:
Yes, please! If I knew the JIRA magic to do this, I would mumble it.
Could someone teach me the magic, and if necessary, give me karma to
mumble?
granted. the admin pages are your friends.
Thanks, Andrew. Where can
[ http://issues.apache.org/jira/browse/DERBY-700?page=all ]
V.Narayanan updated DERBY-700:
--
Attachment: DERBY-700_v1_use_to_run_DualBootrepro_multithreaded.diff
DERBY-700_v1_use_to_run_DualBootrepro_multithreaded.stat
Hi,
Thanx a ton for the issues you have highlighted. I am sorry to have
missed on the earlier chain of emails regarding proposal of single
system property. I was just proposing the system property as a possible
solution and I see the arguments against it as valid. My attempt at
creating a
[ http://issues.apache.org/jira/browse/DERBY-700?page=all ]
V.Narayanan updated DERBY-700:
--
Attachment: DERBY-700.diff
DERBY-700.stat
Hi,
We could solve this problem by setting a System property before booting a
database and checking for
I haven't looked at this yet, just wanted to say that when I proposed a
single system property (vs. one system prop per database), there was
opposition in the community.
Some things to think about:
o can the same database ever have 2 names - ie. if the location is
/x/y/wombat and one person
[ http://issues.apache.org/jira/browse/DERBY-700?page=all ]
Rick Hillegas updated DERBY-700:
Fix Version/s: 10.2.0.0
Derby does not prevent dual boot of database from different classloaders on
Linux
[ http://issues.apache.org/jira/browse/DERBY-700?page=all ]
Rick Hillegas updated DERBY-700:
Urgency: Urgent
Bumping urgency.
Derby does not prevent dual boot of database from different classloaders on
Linux
[ http://issues.apache.org/jira/browse/DERBY-700?page=all ]
Kathey Marsden updated DERBY-700:
-
Priority: Critical (was: Major)
Marking this issue Critical as it is a corruption issue that has in the past
and surely will in the future affect users and
[ http://issues.apache.org/jira/browse/DERBY-700?page=all ]
Kathey Marsden updated DERBY-700:
-
Attachment: DualBootRepro2.zip
Here is an updated repro with a classloader that should not require the
classpath remove other derby jars
Derby does not
[ http://issues.apache.org/jira/browse/DERBY-700?page=all ]
Kathey Marsden updated DERBY-700:
-
Attachment: DualBootRepro.java
DualBootRepro Program to reproduce dual boot from two classloaders in Linux.
Change DERBY_LIB_DIR to derby directory and
[ http://issues.apache.org/jira/browse/DERBY-700?page=all ]
Kathey Marsden updated DERBY-700:
-
Component: Store
Fix Version: (was: 10.1.3.0)
Environment:
ava -version
java version 1.4.2_08
Java(TM) 2 Runtime Environment, Standard Edition
Derby uses java file locking to prevent dual booting, does anyone
know if there are bugs outstanding with filelocking from 2
different classloaders in the same jvm.
I suggest anyone looking at this first write a java specific test
outside of derby to verify that the filelocking behavior that
I think the scope of file lock is for the whole JVM , not specific to
a class loader. This is what I found in the java doc for
java.nio.channels.FileChannel.tryLock() that is used by the Derby.
File locks are held on behalf of the entire Java virtual machine.
They are not suitable for
69 matches
Mail list logo
