November 2018 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1107) Recovery Support in Compensation API

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-1107?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Ondra Chaloupka created pull request #11885 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.jboss.org/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Compensations > Reporter: Tom Jenkinson > Assignee: Ondra Chaloupka > Priority: Major > Fix For: 5.later > > > *Background* > Currently Compensations API cannot handle system failures. Transaction state is not persisted in any stage. Thus no handlers will be invoked in case of the system crash. > *Requirements* > # Make handlers persistable (CompensationHandler, ConfirmationHandler, TransactionLoggedHandler). > ## Require Serializable interface. > ## Create PersistableHandler interface (similar to PersistableParticipant in RTS integration). > # Make participant persistable (ParticipantImpl, LocalParticipant, RemoteParticipant). > ## Make transaction identifier persistable (converting it to String should work). > ## Implement PersistableParticipant in ParticipantImpl. > ## Investigate if PARTICIPANT_COUNTERS in ParticipatnImpl have to be updated. > # Make compensation scoped beans persistable. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3067) Build and run the narayana with JDK-11

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3067?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Tom Jenkinson created pull request #1381 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Build and run the narayana with JDK-11 > -------------------------------------- > > Key: JBTM-3067 > URL: https://issues.jboss.org/browse/JBTM-3067 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Critical > > The jdk-11 could be downloaded from https://jdk.java.net/11/ and the most important feature that impacts us is [JEP 320: Remove the Java EE and CORBA Modules|https://openjdk.java.net/jeps/320] > The CI job is http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana-jdk-11/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2993) start-swarm-lra-coordinator : failed: Process was not healthy even after 30 seconds

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-2993?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka closed JBTM-2993. --------------------------------- Release Notes Text: I'm closing this issue for following reasons * the lra tests were moved to tck suite of lra microprofile spec and no lra test exist anymore in the narayana * I expect that failure was happening because of the timeout for starting the lra coordinator which is a timing issue and could be changed by person building the lra coordinator differently for environment Please, re-open the issue if there is some defect in my reasoning. Resolution: Deferred > start-swarm-lra-coordinator : failed: Process was not healthy even after 30 seconds > ------------------------------------------------------------------------------------ > > Key: JBTM-2993 > URL: https://issues.jboss.org/browse/JBTM-2993 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.8.0.Final > Environment: Fedora 26, OpenJDK 8, Maven 3.5.2 > Reporter: Michal Karm Babacek > Assignee: Ondra Chaloupka > Priority: Major > > I had updated to the latest Narayana master and it broke the build for me on "LRA": See: [log|https://gist.github.com/Karm/2eae842cff57964af65a3341dfae873c] > My git head: 40999b11 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3078) JDBC transaction driver does not support MSSQL, the list should be enriched

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3078?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1380 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > JDBC transaction driver does not support MSSQL, the list should be enriched > --------------------------------------------------------------------------- > > Key: JBTM-3078 > URL: https://issues.jboss.org/browse/JBTM-3078 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Affects Versions: 5.9.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > The transactional jdbc driver does not support MSSQL driver. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3078) JDBC transaction driver does not support MSSQL, the list should be enriched

by Ondra Chaloupka (Jira)

Ondra Chaloupka created JBTM-3078: ------------------------------------- Summary: JDBC transaction driver does not support MSSQL, the list should be enriched Key: JBTM-3078 URL: https://issues.jboss.org/browse/JBTM-3078 Project: JBoss Transaction Manager Issue Type: Bug Components: Transactional Driver Affects Versions: 5.9.0.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka The transactional jdbc driver does not support MSSQL driver. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2471) Provide a mechanism to get stack dumps from the C++ binaries

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2471?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2471: -------------------------------- Priority: Minor (was: Major) > Provide a mechanism to get stack dumps from the C++ binaries > ------------------------------------------------------------ > > Key: JBTM-2471 > URL: https://issues.jboss.org/browse/JBTM-2471 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: BlackTie > Reporter: Tom Jenkinson > Priority: Minor > > Currently debugging BlackTie is problematic as we are reliant on logs to know what was happening on stack dumping the application server to guess what is being called. It would be useful to provide a method to do this. > Potentially an open socket to connect to could dump the stacks or understanding how to do this on Windows and Linux natively. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2326) Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2326?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2326: -------------------------------- Priority: Minor (was: Major) > Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2326 > URL: https://issues.jboss.org/browse/JBTM-2326 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, Tooling > Reporter: Tom Jenkinson > Priority: Minor > Fix For: 5.later > > > Although it is possible to see the list of current transactions in the CLI, for those branches that are available for recovery it can be useful to see the list that the recovery manager is considering. I have often looked in the debugger at this state: > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com... so it might be useful to others. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2010) Scalability Enhancements for BlackTie

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2010?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2010: -------------------------------- Priority: Minor (was: Major) > Scalability Enhancements for BlackTie > ------------------------------------- > > Key: JBTM-2010 > URL: https://issues.jboss.org/browse/JBTM-2010 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: BlackTie > Reporter: Tom Jenkinson > Priority: Minor > > At the moment we are using traditional IO techniques which means there is a single thread and connection per service on the C++ side and a single thread per server per service on the WildFly side. > For example: > 10 servers with 10 services = 10 threads on the client side, 100 threads on the wildfly side > We should look to use AIO on the Java side and apr pollset on the C++ side to reduce the number of threads. This will not reduce the physical number of connections but should allow the server to scale much higher. > 1. use AIO for StompConnect, > 2. add a configurably sized connection polling pool to BlackTie C++, > 3. use a common pool for servicedispatchers, so for example if 10 services with a size of 10 would normally mean 100 threads, we can say 10 services, size of 10, share 10 threads. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-887) Simple WS-AT recovery quickstart

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-887?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-887: ------------------------------- Priority: Optional (was: Major) > Simple WS-AT recovery quickstart > -------------------------------- > > Key: JBTM-887 > URL: https://issues.jboss.org/browse/JBTM-887 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Demonstrator, XTS > Reporter: Paul Robinson > Priority: Optional > > This quickstart shows what happens when a participant fails at various points in the protocol. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-886) Simple WS-BA recovery quickstart

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-886?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-886: ------------------------------- Priority: Optional (was: Major) > Simple WS-BA recovery quickstart > -------------------------------- > > Key: JBTM-886 > URL: https://issues.jboss.org/browse/JBTM-886 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Demonstrator, XTS > Reporter: Paul Robinson > Priority: Optional > > This quickstart will show what happens when a participant crashes at various key points in the protocol. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2018