db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Waagan <Kristian.Waa...@Sun.COM>
Subject Re: Derby regression
Date Tue, 04 Aug 2009 15:25:42 GMT
Kathey Marsden wrote:
> Kristian Waagan wrote:
>> Brett Wooldridge wrote:
>>> Anyone have some suggestions for debugging direction?  I hate the 
>>> thought that I'm stuck on <10.5 forever.  Any other environment 
>>> details, logging options, etc?
> Did you try setting the properties outlined here:
> http://www.nabble.com/Derby-
> to see if we get more information in the derby.log?
> I tend to think the stack trace when you get the XCL30/XJ001 errors 
> will be very helpful.
> If you still do not see them in the derby.log, it might be helpful to 
> get a fix for DERBY-1191, but it does look to me like this error 
> should be logged in derby.log.
> You might also try with  as there were Clob fixes there and 
> another user recently found his Clob issue was resolved there.  Note: 
> Although passed the vote and is posted to the website, we 
> just found a wrong results regression DERBY-4331 which  we are 
> investigating.

I may be able to help debug this, but since XA is involved, I don't have 
that much context.
Especially, I don't know if the "transfer of parameters" is valid, or 
happening at a valid time.

The error seen for the Clob object on the server is apparently caused by 
attempting to read the source stream twice (without resetting it). I 
don't have the code in front of me at the moment, but if Derby always 
chooses to materialize the Clob to "transfer the value", we have another 
issue for XA that needs attention.
However, since I don't know if the actions related to the Clob are taken 
as part of normal processing or due to a DRDA protocol error, I'm at a 
loss at the moment.

Another thing that may help at this point, is to enable the client 
tracing, see 
However, this is just a shot in the dark at the moment, and depending on 
the application the data volume may simply be too large to make sense of.

> Kathey

View raw message