Hi Suraj,
In my last e-mail , i mentioned ; error may be due to file descriptot
leaks. Did you get chance to find if that is the case ?
I assume you are running on Windows , long time ago I used filemon to
track some leak. But it is very tedious work, filemon program
can help you track files opened by a process.
http://www.microsoft.com/technet/sysinternals/processesandthreads/processmonitor.mspx
http://www.microsoft.com/technet/sysinternals/utilities/filemon.mspx
--
If you can provide stand alone reproduction with Derby, then it will
be possible to debug. Otherwise I am just shooting theories in dark,
I know it is hard.
Are you seeing this error if you use derby in plain embedded mode not
as networdk server embedded ?
One another thing I would double check is if the security policy files
have right permissions for derby ? if you are running with security
manager enabled.
Thanks
-suresh
Suraj Batuwana wrote:
Also in client side i am getting the folloing error
Error when executing query:com.ibm.websphere.ce.cm.StaleConnectionException:
Meta-data for Container
[EMAIL PROTECTED] could not be
accessed
junit.framework.AssertionFailedError: Error when executing
query:com.ibm.websphere.ce.cm.StaleConnectionException: Meta-data for
Container [EMAIL PROTECTED] could
not be accessed
Suraj Batuwana wrote:
Hi ,
Thanx for the answer. I have used the Embbeded network server as you have
told. But now when i am running junit test cases
in the nightly build i am getting folloing client side errors in my test
classes
Error when executing
query:com.ibm.websphere.ce.cm.StaleConnectionException: Meta-data for
Container [EMAIL PROTECTED] could
not be accessed
junit.framework.AssertionFailedError: Error when executing
query:com.ibm.websphere.ce.cm.StaleConnectionException: Meta-data for
Container [EMAIL PROTECTED] could
not be accessed
also I have attached the derby.log for your reference.
Note: I have used IBM JDK 1.4.2 and cloudscape 10.2.1.6 with Websphere
6.0.2.5
Also in my seg0(E:\Cloud_Branch\TestDB\seg0\) folder there were 3854 dat
files were there.
why does it says as
[EMAIL PROTECTED] could not be accessed ?
-Suraj
Suraj Batuwana wrote:
I am not sure I got what you tring to say.
What is embedded network server ?
When I am creating the datasource in Websphere I have used the
implementing class as
"org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource"
implementing class for XA as
"org.apache.derby.jdbc.EmbeddedXADataSource"
dataSource helper class as
"com.ibm.websphere.rsadapter.DerbyDataStoreHelper"
and add derby.jar,derbynet.jar and derbytools.jar to the class
path.
"client application could use the client driver"
Is this means to use the org.apache.derby.jdbc.ClientDriver ?,
but it is a Derby Network Client driver. At the moment
I am using org.apache.derby.jdbc.EmbeddedDriver as my client driver.
-Suraj
Daniel John Debrunner-2 wrote:
Suraj Batuwana wrote:
Hi All,
I am a derby user but for my application I need some improved version
of
Derby.
So I thought of writing to this group.
For my application I need to access a single Derby database(using
Embedded
mode) from
1. Data source( In a Websphere 6.0.2.5)
2. Client application
But when try to access the database it will throw exceptions like
"Caused
by: java.sql.SQLException: Failed to start database
'E:\source\database\TestDB'" from a one of the place.
I know this happens because Embedded, a Derby database can be booted
only
from a single JVM, In my case , it is trying to boot from 2 JVMs(client
JVM
and server JVM), but when I used the Network mode there is no such an
issue.Is there a way future Derby (Embedded mode) version can handle
the
above issue or It will remain as it is ?
You can mix embedded and the network server, so in your case the
WebSphere could be running embedded with an embedded network server.
Then the client application could use the client driver.
Dan.
http://www.nabble.com/file/4136/derby.log derby.log