Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 43191 invoked from network); 3 Sep 2009 11:37:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Sep 2009 11:37:25 -0000 Received: (qmail 14979 invoked by uid 500); 3 Sep 2009 11:37:24 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 14907 invoked by uid 500); 3 Sep 2009 11:37:24 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 14899 invoked by uid 99); 3 Sep 2009 11:37:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Sep 2009 11:37:24 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [192.18.6.21] (HELO gmp-eb-inf-1.sun.com) (192.18.6.21) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Sep 2009 11:37:12 +0000 Received: from fe-emea-09.sun.com (gmp-eb-lb-1-fe1.eu.sun.com [192.18.6.7] (may be forged)) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n83BaoNJ004326 for ; Thu, 3 Sep 2009 11:36:50 GMT MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KPE00F00812O400@fe-emea-09.sun.com> for derby-user@db.apache.org; Thu, 03 Sep 2009 12:36:42 +0100 (BST) Received: from [129.159.139.223] ([unknown] [129.159.139.223]) by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KPE006JB895Z240@fe-emea-09.sun.com> for derby-user@db.apache.org; Thu, 03 Sep 2009 12:36:41 +0100 (BST) Date: Thu, 03 Sep 2009 13:34:42 +0200 From: Kristian Waagan Subject: Re: LINUX Hang on creation - ERROR XBM0J Directory already exists onsecond load In-reply-to: <61DDA32A5FE34A7C9E4D17FBD37D9B18@PROXIFLEX> Sender: Kristian.Waagan@Sun.COM To: Derby Discussion Message-id: <4A9FA9D2.3050402@Sun.COM> References: <4A9F8A4A.7040606@Sun.COM> <61DDA32A5FE34A7C9E4D17FBD37D9B18@PROXIFLEX> User-Agent: Thunderbird 2.0.0.22 (X11/20090818) X-Virus-Checked: Checked by ClamAV on apache.org dev@xx wrote: > Thanks for so quick answer ! > > Yes I had found the jira issue but as it was not giving any workaround > ;-) > > I am thinking to all your suggestions but it is not so easy to do for > me... (I am quite new to LINUX and my dev machine is under Windows) > > I have tested on another machine with Fedora > (java-1.6.0-openjdk-1.6.0.0-15.b14.fc10) and it is working !! > The non working machine is a Debian (JRE Sun Microsystems Inc. 1.6.0_13). May not be relevant, but is the file system type the same on the two machines? (i.e. ext3 or ReiserFS) Regards, -- Kristian > > For now I am going to make a small application to test only the Derby > feature and will give you the result. > > Sincerely, > > JY LINET > > > ----- Original Message ----- From: "Kristian Waagan" > > To: "Derby Discussion" > Sent: Thursday, September 03, 2009 11:20 AM > Subject: Re: LINUX Hang on creation - ERROR XBM0J Directory already > exists onsecond load > > >> dev@xx wrote: >>> Hi, >>> I have developped my application under Windows XP and everything is >>> working correctly. >>> Now I start testing under LINUX but without success. >>> When I start first time the embedded driver with create=true option, >>> the application hang but the database seams created, except that the >>> service.properties file doesn't exists (compare to Windows files). >> >> Hello, >> >> What you describe looks similar to >> https://issues.apache.org/jira/browse/DERBY-4098 >> >> To start with a few general things: >> - Does creating and then booting the database work when using ij only? >> (ij is the Derby command line tool) >> - Are you sure the application code isn't touching the database >> directory or the services.properties file? >> - Is it possible to limit DBCP to a single connection? >> (rule out race conditions during creation/boot) >> - Is it hard for you to switch to the client driver? >> (for testing only, and remember to start the network server) >> - Have you tried your application on several Linux machines, or only >> one? >> - Are you able to write something that will monitor your system for >> all accesses to the service.properties? >> (i.e something like DTrace on Solaris). >> The fact that the file doesn't exist may be a problem... >> >> >> Regards, >> -- >> Kristian >> >>> The derby.log seams "normal" : >>> ---------------------------------------------------------------- >>> 2009-09-03 08:42:56.580 GMT: >>> Booting Derby version The Apache Software Foundation - Apache Derby >>> - 10.5.1.1 - (764942): instance a816c00e-0123-7f12-1804-00002387de98 >>> on database directory /home/idaxx/demo/srv/db/dataxx >>> Database Class Loader started - derby.database.classpath='' >>> When I restart the application I have the ERROR XBM0J. So it seams >>> that the creation is uncomplete. >>> The derby.log is : >>> 2009-09-03 08:45:04.951 GMT >>> Thread[WrapperListener_start_runner,5,main] Cleanup action starting >>> ERROR XBM0J: Directory >>> /home/idaxx/demo/srv/db//home/idaxx/demo/srv/db/dataxx already exists. >>> at >>> org.apache.derby.iapi.error.StandardException.newException(Unknown >>> Source) >>> at >>> org.apache.derby.impl.services.monitor.StorageFactoryService$9.run(Unknown >>> Source) >>> at java.security.AccessController.doPrivileged(Native Method) >>> at >>> org.apache.derby.impl.services.monitor.StorageFactoryService.createServiceRoot(Unknown >>> Source) >>> at >>> org.apache.derby.impl.services.monitor.BaseMonitor.bootService(Unknown >>> Source) >>> at >>> org.apache.derby.impl.services.monitor.BaseMonitor.createPersistentService(Unknown >>> Source) >>> at >>> org.apache.derby.iapi.services.monitor.Monitor.createPersistentService(Unknown >>> Source) >>> at >>> org.apache.derby.impl.jdbc.EmbedConnection.createDatabase(Unknown >>> Source) >>> at org.apache.derby.impl.jdbc.EmbedConnection.(Unknown >>> Source) >>> at >>> org.apache.derby.impl.jdbc.EmbedConnection30.(Unknown Source) >>> at >>> org.apache.derby.impl.jdbc.EmbedConnection40.(Unknown Source) >>> at >>> org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source) >>> at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source) >>> at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown >>> Source) >>> at >>> org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38) >>> >>> at >>> org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294) >>> >>> at >>> org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1247) >>> >>> at >>> org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1221) >>> >>> at >>> org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880) >>> >>> at >>> fr.proxiflex.axx.db.Pool.getDataSourceConnection(Pool.java:236) >>> at >>> fr.proxiflex.axx.db.PXConnection.(PXConnection.java:45) >>> at fr.proxiflex.axx.db.Pool.getConnection(Pool.java:241) >>> at >>> fr.proxiflex.axx.db.PoolList.getConnection(PoolList.java:136) >>> at fr.proxiflex.axx.db.DBContext.getConn(DBContext.java:111) >>> at fr.proxiflex.axx.db.DBContext.getConn(DBContext.java:93) >>> at fr.proxiflex.axx.Module.beforeInit(Module.java:234) >>> at >>> fr.proxiflex.axx.server.ModuleAbstract.init(ModuleAbstract.java:34) >>> at >>> fr.proxiflex.axx.server.DemuxIoHandler.initModule(DemuxIoHandler.java:353) >>> >>> at >>> fr.proxiflex.axx.server.DemuxIoHandler.initModules(DemuxIoHandler.java:330) >>> >>> at >>> fr.proxiflex.axx.server.DemuxIoHandler.(DemuxIoHandler.java:187) >>> at fr.proxiflex.axx.server.PXServer.start(PXServer.java:232) >>> at >>> org.tanukisoftware.wrapper.WrapperManager$12.run(WrapperManager.java:2979) >>> >>> Cleanup action completed >>> 2009-09-03 08:45:04.973 GMT >>> Thread[WrapperListener_start_runner,5,main] Cleanup action starting >>> java.sql.SQLException: Failed to create database 'directory:dataxx', >>> see the next exception for details. >>> at >>> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown >>> Source) >>> at >>> org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) >>> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown >>> Source) >>> at >>> org.apache.derby.impl.jdbc.EmbedConnection.createDatabase(Unknown >>> Source) >>> at org.apache.derby.impl.jdbc.EmbedConnection.(Unknown >>> Source) >>> at >>> org.apache.derby.impl.jdbc.EmbedConnection30.(Unknown Source) >>> at >>> org.apache.derby.impl.jdbc.EmbedConnection40.(Unknown Source) >>> at >>> org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source) >>> at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source) >>> at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown >>> Source) >>> at >>> org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFacto >>> >>> ry.java:38) >>> at >>> org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory >>> >>> I made searches on internet and tried a lot of differents ways to >>> define the databasename and the home directory but without success. >>> Thanks for help... >>> JY LINET >> >> >