lixa Activity
LIXA, LIbre XA, is a free and open source XA transaction manager
Brought to you by:
tiian
Activity for lixa
-
Christian Ferrari committed [033987] on Git
Intermediate commit for MySQL and MariaDB, still under debugging
-
Intermediate commit with MariaDB adaptations, but still not stable
-
Intermediate commit for issue #20, ok for MySQL, not ok for MariaDB
-
function lixa_my_retrieve_subtype() completed
-
test commit from ubuntu 16.04
-
intermediate commit
-
Changes for issues #24, #25, #26
-
Small changes related to issue #18, issue #22, and issue #23
-
Fix of issue #19
-
Fix of issue #16
-
lixa released /lixa/testing/lixa-1.9.5.tar.gz
-
Version 1.9.5 commit, only minor documentation refinement
-
You must pay attention to the following aspects: XTA has currently been tested only for MySQL/MariaDB, PostgreSQL, Oracle DB as documented here https://www.tiian.org/lixa/manuals/html/ch08.html#XTA_Technology_Matrix If you want to use DB2 and MQ with XTA, you should use the xta::NativeXaResource as in the below code snippet: xar = new xta::NativeXaResource( "OracleIC_stareg", "/opt/lixa/lib/switch_oracle_stareg.so", "ORACLE_XA+Acc=P/hr/hr+SesTm=30+LogDir=/tmp+" "threads=true+DbgFl=7+SqlNet=lixa_ora_db+"...
-
NeXgeN posted a comment on discussion Open Discussion
Hi we are trying to configure for XTA . Just hit the ./configure command.
-
Hi!What API are you using to develop your application: the TX Transaction Demarcation specification or XTA? Il venerdì 21 gennaio 2022, 04:37:12 CET, NeXgeN <shri2009@users.sourceforge.net> ha scritto: Hi Team We don't have requirement for using mysql . we are testing LIXA as XA transaction manager for DB2 , Postgres and IBM MQ for C++ application . But we cant move past the installation of LIXA 1.9.4 configure. we keep getting following error on our Linux RHEL 7.9 OS configure: error: XTA for C++...
-
Hi Team We don't have requirement for using mysql . we are testing LIXA as XA transaction manager for DB2 , Postgres and IBM MQ for C++ application . But we cant move past the installation of LIXA 1.9.4 configure. we keep getting following error on our Linux RHEL 7.9 OS configure: error: XTA for C++ requires --with-mysql and --with-postgresql Is it mandatory to install MYSQL for proceeding further ?
-
Typo documentation fix
-
Dummy commit to keep CodeQL alive
-
Dummy commit to keep CodeQL alive
-
Updated copyright years
-
GitHub committed [7e239d]
Update codeql-analysis.yml
-
Added documentation for XA functions call order with TX and XTA API
-
Fixed a bug in Makefile that crated a wrong tarball
-
-
Fix for docker containers lixa/xta-jdk*
-
Commit for release 1.9.4
-
-
-
Commit for release 1.9.3
-
Passed tests for Ubuntu 20.04, traditional state engine
-
Added info to use MySQL 8.0
-
Adding support for mariadb-java-client-2.5.3.jar
-
Fixing timing in case0035 to reproduce a specific behavior
-
CentOS 8 passed all tests!
-
Progressing with test case fixing
-
Merge branch 'master' of github.com:tiian/lixa
-
Fixing CodeQL automation
-
Added CodeQL security scanner configuration
-
Fixing CodeQL automation
-
Fixind security CodeQL security alerts
-
Fixing CodeQL automation
-
Fixing CodeQL automation
-
Fixind security CodeQL security alerts
-
Fixind security CodeQL security alerts
-
Added java pre-requisites
-
Removed a race condition in test case XTA Java/8.2/2.3
-
--enable-debug to catch the last messages of lixad in the event of crash
-
--enable-debug to catch the last messages of lixad in the event of crash
-
--enable-debug to catch the last messages of lixad in the event of crash
-
Found a test case that does not work with CentOS 8
-
Improving examples for MariaDB
-
Changes for MySQL/MariaDB
-
Some doc improvements
-
Fixed reference manual, put Java stack trace under standard LIXA tracing
-
Fix of https://github.com/tiian/lixa/issues/6
-
Developing test cases for xta_transaction_recover
-
Changed xta_transaction_recover to support https://github.com/tiian/lixa/issues/6
-
Protected lixad against a violation transition of the FSM
-
Added check in configure.ac to protect against missing MySQL/PostgreSQL when XTA for C++ is required
-
Marked as DEPRECATED internal function xta_transaction_safe_delete
-
Some patches necessary to build the Docker containers for Debian 10.3: lixa/xta-python2
-
Commit for release 1.9.2
-
-
-
Improved restart time for function lixa_state_log_read_file
-
Commit for release 1.9.1
-
Before starting log buffering optimization...
-
Fixed pre processor condition
-
Fixed pre processor condition
-
Improved restart time for function lixa_state_log_open_file
-
Disabled write specific flags for log read in warm restart (journal state engine)
-
Added LIXA_TRACE_STACK() to most functions, wherever it makes sense
-
Added LIXA_TRACE_STACK() macro
-
-
Release 1.9.0
-
Added 25th%, average and std dev to lixat benchmark statistics
-
Fixed manual tracing table in reference manual
-
Added Troubleshooting chapter in the Reference Manual
-
Added total time stat to lixat
-
Commit before removing old stats from lixat
-
New statistics for lixat
-
Added POLLNVAL handling in lixa_msg_receive
-
Fixed log file size allocation
-
Fixed a bug when the file magic number is corrupted
-
Added message LXD079W
-
POLLNVAL new handling
-
Parameter C for lixat
-
Writing Tuning chapter
-
Manual update
-
Copyright updated, tests passed, manual update in progress
-
Completed hard server crash test cases
-
Added further test cases
-
Added test cases ct_2_2
-
Started to develop hard crash tests for JOURNAL state engine
-
Passed all case tests with LIXA_STATE_ENGINE=JOURNAL
-
Introduced synchronous log flushing
-
Found a tricky situation in crash test
-
Entering release candidate phase
-
Fixed another bunch of case tests
-
Fixed a bunch of case tests for the new state engine
1 >
