Matthieu Riou wrote:
On Thu, Jun 5, 2008 at 12:38 PM, Mike Edwards <
[EMAIL PROTECTED]> wrote:
Matthieu,
First - many thanks for your hard work on this.
I take no pleasure in saying this, but I am glad that the DB problem was
ODE's problem rather than Tuscany's - it looks like you are far mor
On Thu, Jun 5, 2008 at 12:38 PM, Mike Edwards <
[EMAIL PROTECTED]> wrote:
> Matthieu,
>
> First - many thanks for your hard work on this.
>
> I take no pleasure in saying this, but I am glad that the DB problem was
> ODE's problem rather than Tuscany's - it looks like you are far more
> experience
Matthieu,
First - many thanks for your hard work on this.
I take no pleasure in saying this, but I am glad that the DB problem was ODE's problem rather than
Tuscany's - it looks like you are far more experienced in handling that area of code!
Regarding that remaining error, which is generated
Okay, this took a while because it was actually far trickier than I
expected. Here were the two problems (the first being the serious one):
* When OpenJPA first connects to the DB it initializes its sequence table
and does it using a different connection. It's fine when it's done in
isolation (li
I've started looking at the DbError issue and reproduced it. Digging deeper
it seems it's caused by a lock timeout in Derby on the
OPENJPA_SEQUENCE_TABLE when ODE tries to create a record for the new
deployed process. Here is an excerpt from the logs:
DEBUG - GeronimoLog.debug(66) | Creating proce
