Hi Sebastian,
On 2/28/07, Schnabl, Sebastian <[EMAIL PROTECTED]> wrote:
But now I'm getting javax.ejb.DuplicateKeyException on client-side. Aren't
the stored-procedure calls broadcasted to both db-backends anymore? In the
log I'm only seeing that one whole transaction is rollbacked, but I'm seeing
not which and why – but it looks for me, that the {call
nextval('SEQ_QSCATEGORIES')} and an resulting
javax.ejb.DuplicateKeyException (thrown on client-side) could be the cause.
See following log-excerpt of transaction 835.
Can you enable query logging on both PostgreSQL backends? See
http://pgfouine.projects.postgresql.org/tutorial.html for more
information on how to configure it. log_statement is enough in your
case.
You should then have more information about the transaction and we
should be able to understand the problem.
Be sure your sequences are synchronized before the start of Sequoia.
Thanks.
--
Guillaume
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
