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] Reopened: (DERBY-555) Unable to restart after disk is full
Date Tue, 03 Mar 2009 17:42:56 GMT

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

Kathey Marsden reopened DERBY-555:
----------------------------------


reopening to backport to 10.1. I need the read only boot message there and it will be good
to have this fixed in 10.1 anyway.



> Unable to restart after disk is full
> ------------------------------------
>
>                 Key: DERBY-555
>                 URL: https://issues.apache.org/jira/browse/DERBY-555
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.2.1.6
>         Environment: Sun Sparc Solaris, 1.4 JDK, Derby Client/Server
>            Reporter: Øystein Grøvlen
>            Assignee: Øystein Grøvlen
>            Priority: Critical
>             Fix For: 10.2.1.6
>
>         Attachments: derby-555a.diff
>
>
> 1. Inserted data into the database until the disk was full. (5 clients inserting into
5 different tables in parallel.)
> 2. Shut down the server
> 3. Start the database again without freeing any disk space.
> When I try to start the database again, I get Null-pointer-exception, regardless of how
I connect (have tried embedded, client server, ij, jdbc applications).  I have not tried to
free some space on the disk before starting.  
> The call stack is not available right now (the computer I used had to be shut down due
to problems with our cooling system), but the exception comes from the following line in RawStore.java:
>      properties.put(Attribute.LOG_DEVICE, logFactory.getCanonicalLogPath());
> getCanonicalLogPath() returns null which results in a NPE in the hash table.
> A quick debug before the computer was stopped, showed that the logFactory was an instance
of org.apache.derby.impl.store.raw.log.ReadOnly which always returns null in its  getCanonicalLogPath().
> I suspect this may be related to the fact that I ran with the log in a non-default location.

-- 
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