Hi Robert,
thanks for advice. Please let me know once you resolve your problem.
Unfortunately our issue is bringing a bigger concern and that is how
combination of Jonas/Interbase/our architecture is handling concurrent
modification/access of the same entity bean by multiple clients and I am
really interested in finding out what is the real reason why we are
experiencing the problems we are experiencing since this might happen again
in a different area of our product (different entity beans).
Regards,
Miro Halas
-----Original Message-----
From: Robert Parlett [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 21, 2001 12:23 PM
To: [EMAIL PROTECTED]
Subject: Transaction synchronization problem during unique ID generation
Dear Miroslav
By an odd coincidence I was experiencing just the same
problem you describe, also using Interbase.
My idea was to use an entity bean (one instance giving one
sequence of numbers) with a transaction attribute of
NotSupported, and have the bean persist itself every few
seconds (or at shutdown) using the passivation timeout
attribute. This eliminates the problem of reading the old
used serial number value from another transaction due to
transactional isolation. I have a similar multi-thread test
program to you, and it worked fine... until it came to
persisting the value, and then Jonas always throws an
exception. My post of earlier today explains more. If I
could get over this exception being thrown, I would have a
solution to this problem.
Regards,
Robert P Parlett
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
