On 5/23/05, David J. M. Karlsen [EMAIL PROTECTED] wrote:
Oliver Zeigermann wrote:
On 5/21/05, David J. M. Karlsen [EMAIL PROTECTED] wrote:
Hmm, yeah, but still - I cannot see why txId should be unique, the code is:
public String generatedUniqueTxId() throws ResourceManagerSystemException
Oliver Zeigermann wrote:
Hmm, yeah, but still - I cannot see why txId should be unique, the code is:
public String generatedUniqueTxId() throws ResourceManagerSystemException {
assureRMReady();
String txId;
synchronized (globalTransactions) {
do {
txId
Oliver Zeigermann wrote:
On 5/20/05, David J. M. Karlsen [EMAIL PROTECTED] wrote:
Hi!
I keep getting ResourceManagerExceptions with Duplicate transaction
id. I took a look at the implementation of FileResourceManager - and
generatedUniqueID only returns system.getCurrentMillis() - which
Hi!
I keep getting ResourceManagerExceptions with Duplicate transaction
id. I took a look at the implementation of FileResourceManager - and
generatedUniqueID only returns system.getCurrentMillis() - which isn't
random enough in a multithreaded environment.
This should probably be changed into
On 5/20/05, David J. M. Karlsen [EMAIL PROTECTED] wrote:
Hi!
I keep getting ResourceManagerExceptions with Duplicate transaction
id. I took a look at the implementation of FileResourceManager - and
generatedUniqueID only returns system.getCurrentMillis() - which isn't
random enough in a
