[MAGNOLIA-818] Buggy bundled derby version Created: 20/Apr/06  Updated: 23/Jan/13  Resolved: 10/Oct/06

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 2.1.5
Fix Version/s: 3.0 RC3

Type: Bug Priority: Major
Reporter: Dave Avent Assignee: Boris Kraft
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

FreeBSD, TomCat 5.5.15, JRE 1.5


Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

The bundled derby.jar file contains a known bug as reported/fixed here:

http://issues.apache.org/jira/browse/DERBY-1



 Comments   
Comment by Oliver Lietz [ 07/Jul/06 ]

I can confirm this bug on:

FreeBSD 6.1-RELEASE, UFS2 with softupdates enabled/disabled
Tomcat 5.5.17
JDK 1.5 (diablo-jdk-1.5.0.06.00 Java Development Kit 1.5.0_06.00/diablo-jdk-1.5.0.07.00 Java Development Kit 1.5.0_07.00)

It happens when bootstrapping. Replacing bundled derby.jar with derby-10.1.3.1 fixes this bug.

No problems on:

Mac OS X 10.4.7 (8J135) Darwin 8.7.0, Mac OS Extended (Journaled)
Tomcat 5.5.17
JDK 1.5 (java version "1.5.0_06", Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-112),
Java HotSpot(TM) Client VM (build 1.5.0_06-64, mixed mode, sharing))

ERROR info.magnolia.jackrabbit.ProviderImpl ProviderImpl.java(init:117) [...] Unable to initialize repository: Cannot instantiate persistence manager org.apache.jackrabbit.core.state.db.DerbyPersistenceManager: Failed to create database '/[...]/repositories/website/version/db', see the next exception for details.
javax.jcr.RepositoryException: Cannot instantiate persistence manager org.apache.jackrabbit.core.state.db.DerbyPersistenceManager: Failed to create database '/[...]/repositories/website/version/db', see the next exception for details.: Failed to create database '/[...]/repositories/website/version/db', see the next exception for details.
[...]
Caused by: SQL Exception: Failed to create database '/[...]/repositories/website/version/db', see the next exception for details.
[...]
SQL Exception: Failed to create database '/[...]/repositories/website/version/db', see the next exception for details.
[...]

Comment by Philipp Bracher [ 10/Oct/06 ]

we use: 10.1.3.1

Comment by ashapochka [ 23/Nov/07 ]

The failure to create a database can also occur due to the too low open file limit on some Unix/Linux systems. For instance Ubuntu has this limit set to around 200000 open files by default which turned out to be insufficient. The issue can be identified by looking for a 'too many open files' exception in derby.log created in $CATALINA_HOME/bin by default.

One solution to this issue is to increase the open file limit system-wide:

1) Set fs.file-max = 400000 (or similarly high number) in /etc/sysctl.conf
2) Apply the changes by executing sysctl -p

Comment by ashapochka [ 23/Nov/07 ]

Also see this: http://www.xenoclast.org/doc/benchmark/HTTP-benchmarking-HOWTO/node7.html

Generated at Mon Feb 12 03:20:57 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.