Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
[JBTM-3138] XTS bridge 1PC consistency failure

When TxBridge is used to inbound the transaction and call the WS

which do some transactional work and the WS is the only one

resource then onePhase is used. But onePhase causes data is not saved

to object store and recovery after JVM crash goes to rollback.

This is a follow-up to JBTM-3079 where active xids were considered

to not be processed by recovery manager

    • -2
    • +2
    ./arjuna/recovery/PeriodicRecovery.java
  1. … 20 more files in changeset.
Updated javadoc for driver classes

postgres_driver ought to extend postgresql_driver

[WFLY-11739] add support for PostgreSQL Plus 10.1

    • -0
    • +29
    ./arjuna/objectstore/jdbc/drivers/edb_driver.java
    • -1
    • +1
    ./arjuna/recovery/PeriodicRecovery.java
  1. … 7 more files in changeset.
Adding inbound txbridge commit crashrec test

follow-up to JBTM-3079 where active xids were considered

to not be processed by recovery manager

    • -2
    • +2
    ./arjuna/recovery/PeriodicRecovery.java
  1. … 4 more files in changeset.
[JBTM-3079] adding test and improving logging

    • -1
    • +1
    ./arjuna/recovery/PeriodicRecovery.java
  1. … 4 more files in changeset.
[JBTM-3047] adjusting stopping listener for avoid deadlock on client scan request while conainer is about shutdown

    • -2
    • +7
    ./arjuna/recovery/PeriodicRecovery.java
  1. … 1 more file in changeset.
JBTM-3017 Report periodic recovery problems

    • -5
    • +23
    ./arjuna/recovery/WorkerService.java
  1. … 8 more files in changeset.
JBTM-3017 Report periodic recovery problems

    • -5
    • +23
    ./arjuna/recovery/WorkerService.java
  1. … 8 more files in changeset.
[JBTM-3025] Xid created from imported transaction should not change node name

reasoning of the change JBTM-2893 were issues on JCA inflow transactions

which did not work when inflowed from more resources. The fix of 2893

fixed the issue but itroduced issue with the node name of subordinate

transaction differs.

    • -0
    • +49
    ./arjuna/FormatConstants.java
  1. … 7 more files in changeset.
[JBTM-2983] Returning a correct error code for LRCO one phase resource

JBTM-2956 Added a simple pooling datasource wrapper

  1. … 2 more files in changeset.
Revert "JBTM-2865 write to _work inside _workList lock"

This reverts commit 021cd85b85cca1411b358dc60efaea47c561fc79.

JBTM-2865 write to _work inside _workList lock

JBTM-2786 Order clauses to prevent deadlock in MySQL

    • -34
    • +34
    ./arjuna/objectstore/jdbc/JDBCImple_driver.java
JBTM-2673 Updated so that the threadId is not removed by other threads but is simply stored weakly

  1. … 3 more files in changeset.
[JBTM-2758] object instance as synchronized lock instead of interned string

String literals are centrally interned and could also be locked on by a

library, causing you to potentially have deadlocks or lock collisions

with other code.

[JBTM-2730] Not using system default encoding but UTF-8

Fix of static analysis bug

21994 Dm: Dubious method used In org.jboss.narayana.osgi.jta.internal.ObjStoreBrowserImpl.ObjStoreBrowserImpl

(com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser):

Found a call to a method which will perform a byte to String (or String

to byte) conversion, and will assume that the default platform encoding

is suitable)

Any conversion from byt and char should not use default platform

encoding. With default encoding code behaves differently depending

platform it runs on. Especially it's harmfull when data flows from one

platform to another.

Using UTF-8 as default.

  1. … 28 more files in changeset.
JBTM-2720 added a facility to allow a user to provide an initial offset to starting recovery

    • -0
    • +26
    ./arjuna/recovery/PeriodicRecovery.java
  1. … 2 more files in changeset.
JBTM-2720 added a facility to allow a user to provide an initial offset to starting recovery

    • -0
    • +26
    ./arjuna/recovery/PeriodicRecovery.java
  1. … 2 more files in changeset.
JBTM-2720 added a facility to allow a user to provide an initial offset to starting recovery

    • -0
    • +26
    ./arjuna/recovery/PeriodicRecovery.java
  1. … 2 more files in changeset.
JBTM-2720 added a facility to allow a user to provide an initial offset to starting recovery

    • -0
    • +26
    ./arjuna/recovery/PeriodicRecovery.java
  1. … 2 more files in changeset.
JBTM-2696 Added some more logging when read_state fails

    • -1
    • +5
    ./arjuna/objectstore/jdbc/JDBCImple_driver.java
  1. … 1 more file in changeset.
JBTM-2673 Updated to use a map for storing the thread IDs rather than a thread local - this corrects a defect where the Thread parameter was ignored

  1. … 4 more files in changeset.
Updated to 4.17.33.Final

    • -1
    • +1
    ./arjuna/recovery/ExpiredEntryMonitor.java
    • -1
    • +1
    ./arjuna/tools/log/EditableAtomicAction.java
  1. … 452 more files in changeset.
JBTM-2655 Updated so that if a state is not able to be written the prepare will fail

    • -7
    • +15
    ./arjuna/objectstore/jdbc/JDBCImple_driver.java
  1. … 5 more files in changeset.
JBTM-2649 Updated to make sure we overwrite the record

JBTM-2649 Updated to make sure we overwrite the record

Updated to 5.3.1.Final

    • -1
    • +1
    ./arjuna/recovery/ExpiredEntryMonitor.java
    • -1
    • +1
    ./arjuna/tools/log/EditableAtomicAction.java
  1. … 566 more files in changeset.