db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suraj Batuwana <sbatuw...@virtusa.com>
Subject Re: Issue with Derby when using with IBM WebSphere Application Server Community Edition
Date Tue, 31 Oct 2006 05:11:38 GMT

Hi Suresh,

1. I have tested on 1.5 (j9) to check the same error is happening there. And
it does. So the error is not targeted a perticuler JVM. Basically I am using 
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM Windows 32 build cn142ifx-20051115
(SR3 + 94164 + 97403 + 97482) (JIT enabled: jitc))

To WASCE(server side) and to run maven(client side)

2. I am creating the database on the local drive. Not in a network drive

3.I do not see any files with zero length in the <database name> 
seg0 directory of the database.

4) I am able to reproduce this error consistently on a new database also.

5) I have attached my derby.log for your reference.

Looking at that I have found several interesting things.(I am assuming)
While the nightly build tests are happing with derby/WASCE the derby shuting
down and booting its instances. It seems that shuting down of instances are
happening while the live connections are still there.

But when I running the same code base with derby/websphere only one
time boot up is happend. here It tries to shutdown and boot up the instance
several times. Is there a way to stop or controll the  shuting down and boot
up the derby instance.

I also found that error is commong from error message coming from the
derby.org.apache.derby.client.net.NetConnectionReply a class which is in the


Suresh Thalamati wrote:
> Stanley Bradbury wrote:
>> Suraj Batuwana wrote:
>>> Hi Stanley,
>> In addition, if my assumptions about your configuration are correct, the 
>> datasource you  define for WAS CE is trying to connecting to the WAS CE 
>> network server (e.g. localhost:1527) and trying to access the database 
>> of the Maven Network Server - you should be addressing the Maven Network 
>> Server (   <ant:arg line="start -h localhost -p 1530"/>) - this could 
>> result in the "ERROR XSDG3: Meta-data for Container.." error you as 
>> seeing (presumably in the derby.log for WAS CE, the database might 
>> already be locked by the Maven Network Server).
>> It is a shame that WAS CE does allow you to utilize the Network Server 
>> it starts, I assume this is done because of security concerns.
>> If this doesn't help please ...  supply the information from 
>> '....NetworkServerControl sysinfo' as well as any console messages that 
>> may be displayed.  (am referring to the Network Server console messages 
>> for both the WAS CE instance and one started by Maven).
> Hi Stan and Suraj.
> I am bit puzzled about "ERROR XSDG3: Meta-data for Container.." and 
> would like to learn, why this is happening in this setup.  Typically 
> this error occurs, if the container files are corrupted (due to disk 
> corruption or the database is on some kind of network file system 
> where  file syncs are not getting synced.
> Suraj,
> 1)  is this error happening only on a particular JVM  ? ( I saw in 
> your e-mail you were using 1.5(j9) and  1.4 ; On which jvm you saw the 
> error first ?  If once the corruption occurs , it won't go away, so it 
>    does not matter if you change the jvm, unless you created new 
> database , for both runs.
> 2) are you creating the database on a network drive ?
> 3) Are you seeing any files with zero length in the <database name> 
> seg0 directory of the database.
> 4) Are you able to reproduce this error consistently on a new database ?
> Thanks
> -suresh
http://www.nabble.com/file/3919/derby.log derby.log 
View this message in context: http://www.nabble.com/Issue-with-Derby-when-using-with-IBM-WebSphere-Application-Server-Community-Edition-tf2512964.html#a7088449
Sent from the Apache Derby Users mailing list archive at Nabble.com.

View raw message