Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <2124584872.1237412390854.JavaMail.jira@brutus>
Date: Wed, 18 Mar 2009 14:39:50 -0700 (PDT)
From: "KP Tallapaneni (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4098) ERROR XBM0J: Directory
 /var/db/sw-abc already exists.
In-Reply-To: <311476223.1237273490445.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683183#action_12683183 ] 

KP Tallapaneni commented on DERBY-4098:
---------------------------------------

Thanks Kristian for the support !

This is a system level hung, and we are already investigating for a possible issue with OS patch that might be causing this hung.
Also, this is not a mirrored partition.

We mainly need your help with fixing the Derby error ERROR XBM0J(ERROR XBM0J: Directory /var/db/sw-abc already exists). The directory is not available, but Derby is throwing this error that that directory already exists. Is there any recommended solution(with or without code changes) or work around(without code changes) to prevent this ERROR(XBM0J)? This hung is probably not related to this Derby ERROR(though we need to confirm again from the truss output), but we need to resolve this XBM0J to get things going after resolving the hung issue due to a possible incorrect application of OS patch.

Appreciate your comments on resolving this derby error.


> ERROR XBM0J: Directory /var/db/sw-abc already exists.
> -----------------------------------------------------
>
>                 Key: DERBY-4098
>                 URL: https://issues.apache.org/jira/browse/DERBY-4098
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.4.1.3
>         Environment: Sun Solaris 10
>            Reporter: Peter Schi
>
> We got the folllowing error:
> ERROR XBM0J: Directory /var/db/sw-abc  already exists.
> But I checked that the directory didn't exist before I ran the program.
> Then I deleted this db and then re-ran the program, but I still got the same problem.
> When I got this error then it caused the system hung.
> Any help is appreciated.
> ERROR XBM0J: Directory /var/db/sw-abc 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.<init>(Unknown Source)
>         at org.apache.derby.impl.jdbc.EmbedConnection30.<init>(Unknown Source)
>         at org.apache.derby.jdbc.Driver30.getNewEmbedConnection(Unknown Source)
>         at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
>         at org.apache.derby.jdbc.EmbeddedDataSource.getConnection(Unknown Source)
>         at org.apache.derby.jdbc.EmbedPooledConnection.openRealConnection(Unknown Source)
>         at org.apache.derby.jdbc.EmbedPooledConnection.<init>(Unknown Source)
>         at org.apache.derby.jdbc.Driver30.getNewPooledConnection(Unknown Source)
>         at org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource.createPooledConnection(Unknown Source)
>         at org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource.getPooledConnection(Unknown Source)
>         ................
>         at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:999)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:993)
>         at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:974)
>         at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
>         at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:260)
>         at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:252)
>         at org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._start(FrameworkCommandProvider.java:2
> 60)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.execute(FrameworkCommandInterpreter
> .java:150)
>         at org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(FrameworkConsole.java:291)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.