The lock is to prevent more than 1 Derby instance to access the same database on Disk - You cannot have 2 Derby engine instances accessing the same database at the same time. Since you're running in client-server mode, you should be good unless you may have attempted to access the database in embedded mode as well, but the database lock should have prevented this...Have you noticed any stack traces related to this reported error in the
Thank for your intest in my problem.
I'm accessing derby through Client-Server mode.
If lock is the cause of the problem, how can I release the lock?
Francois Orsini wrote:
> How are you accessing Netbeans from Netbeans? in Embedded or Client-Server
> mode? You might want to check derby.log file to see if there is any
> stacktrace(s) relevant to this error...Also, are you by any chance
> the same database from some other Derby instance? there should be a lock
> file preventing this but I have issues with this, especially with a
> opened and accessed from different classloaders...Just food for
> On 5/14/07, hk < email@example.com> wrote:
>> While I was trying to delete tables through "Execute command screen" of
>> Netbeans, I got an error message saying
>> "The coglomerate (27265) requested does not exist."
>> View this message in context:
>> Sent from the Apache Derby Users mailing list archive at Nabble.com.
View this message in context: http://www.nabble.com/can%27t-delete-table-tf3754439.html#a10617690
Sent from the Apache Derby Users mailing list archive at Nabble.com.