Noel J. Bergman wrote:
>>For a) I assume there are functional tests for James, but from looking
>>at the wiki I couldn't see any instructions.
>
>
> We have unit tests. You can find them in the source code, and you can see
> the results in the nightly build report. Perhaps we need more unit t
Over in Derby land we are gearing up for a new feature release, I
thought that running James with the new release would a good test. The
goals would be to:
a) see if James (as a database application) works with derby 10.2 with
no changes, as desired
b) see how the performance is with 10.2 compar
Danny Angus wrote:
>>A better datatype would be CLOB, then you could have up to 2Gb character
>
> limit.
>
>>I don't believe this would require any application changes (moving to a
>
> CLOB).
>
>
>>We've seen some odd behavior dealing with CLOBs with some drivers, hence
>
> the
>
>>useBlob v
Noel J. Bergman wrote:
> I have spent much of ApacheCon working on testing JAMES. Ran into some
> little bits, but generally OK. Ran with Derby for about 48 hours stably,
I'm looking at how James uses Derby and I see for the message repository
the create table statement is:
CREATE TA
Noel J. Bergman wrote:
> Danny Angus wrote:
>
>>Daniel John Debrunner wrote:
>>
>>>Thanks for all the info. At ApacheCon Europe I discussed with Noel (in
>>>his presentation) some of the possiblilities of integrating Derby and
>>>James, the first
Danny Angus wrote:
> Dan Debrunner wrote:
>
>
>>... bug fixes include much better performance on streaming
>>BLOB/CLOB data into Derby, and reduced memory usage during those
>
> operations.
>
> Have a Cigar :-)
>
> It might be worth you guys knowing what our requirements are, although I
> thin
Noel J. Bergman wrote:
> jta wrote:
>
>
>>1) What version of derby is being used? Posting the output
>>from this command would be the most helpful:
>>java org.apache.derby.tools.sysinfo
>
> - Derby Information
> JRE - JDBC: J2SE 1.4.2 - JDBC 3.0
> [/home/noel/ASF/james/s
Bernd Fondermann wrote:
> I set up a local test environment and eventually saw
> (a) OutOfMemorys (but only after a longer period of time, with -Xmx64M)
It may be that the Derby page cache is too big for this memory size. By
default the page cache is 1000 pages, and the default page size is 4k.
H
