August 2018 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3049) Setting properties via arjPropertyManager should affect all related config bean instances

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-3049?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-3049: -------------------------------- Forum Reference: https://developer.jboss.org/message/984739?et=watches.email.thread#984739 > Setting properties via arjPropertyManager should affect all related config bean instances > ----------------------------------------------------------------------------------------- > > Key: JBTM-3049 > URL: https://issues.jboss.org/browse/JBTM-3049 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > Narayana configuration is performed through named configuration beans. For example the ObjectStoreEnvironmentBean has three instances for configuring different store types: > * the action store (default) > * the stateStore (with the name "stateStore") > * the communicationsStore (with the name "communicationsStore") > Each of the stores have their own getters and setters. > We also have the arjPropertyManager API which returns the default configuration beans: > {code} > public static CoreEnvironmentBean getCoreEnvironmentBean(); > public static CoordinatorEnvironmentBean getCoordinatorEnvironmentBean(); > public static ObjectStoreEnvironmentBean getObjectStoreEnvironmentBean(); > {code} > For example the getObjectStoreEnvironmentBean() call returns the config for the action store. > Historically (ie before we moved to using configuration beans) the user could set all config properties via the single instance of arjPropertyManager. For example, if the user wanted to disable file system sync'ing for the object store he would obtain an arjuna PropertyManager with which he could set a single property called OBJECTSTORE_SYNC and the setting would be applied to all writes to the object store. However, with the new/current config mechanism he would need to call the setter on each known instance of the ObjectStoreEnvironmentBean: > {code} > BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, "communicationStore").setObjectStoreSync(false); > BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, "stateStore").setObjectStoreSync(false); > BeanPopulator.getDefaultInstance(ObjectStoreEnvironmentBean.class).setObjectStoreSync(false); > {code} > This JIRA is to return to the original behaviour where calling the setters of the beans returned from arjPropertyManager should be applied to all named instances of the returned bean. > The semantics of calling the getters needs be discussed and defined. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3053) Narayana log should be enhanced for information what are nodes the node name orphan filter takes care of

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-3053?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1363 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Narayana log should be enhanced for information what are nodes the node name orphan filter takes care of > -------------------------------------------------------------------------------------------------------- > > Key: JBTM-3053 > URL: https://issues.jboss.org/browse/JBTM-3053 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > Based on my investigation of logs at WFWIP-118 I found out I'm not able to (easily) find what are node names that the recovery considers to be responsible for. > The orphan filter {{NodeNameXAResourceOrphanFilter}} checks the node name sealed in the {{Xid}} to be part of the list {{_xaRecoveryNodes}} > https://github.com/jbosstm/narayana/blob/5.9.0.Final/ArjunaJTA/jta/classe... > But what is the content of the list is not recorded in the log anywhere. I think setting up the environmental bean with this information should be logged at debug level to be possible to find it > https://github.com/jbosstm/narayana/blob/5.9.0.Final/ArjunaJTA/jta/classe... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3053) Narayana log should be enhanced for information what are nodes the node name orphan filter takes care of

by Ondra Chaloupka (JIRA)

Ondra Chaloupka created JBTM-3053: ------------------------------------- Summary: Narayana log should be enhanced for information what are nodes the node name orphan filter takes care of Key: JBTM-3053 URL: https://issues.jboss.org/browse/JBTM-3053 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Transaction Core Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka Priority: Minor Based on my investigation of logs at WFWIP-118 I found out I'm not able to (easily) find what are node names that the recovery considers to be responsible for. The orphan filter {{NodeNameXAResourceOrphanFilter}} checks the node name sealed in the {{Xid}} to be part of the list {{_xaRecoveryNodes}} https://github.com/jbosstm/narayana/blob/5.9.0.Final/ArjunaJTA/jta/classe... But what is the content of the list is not recorded in the log anywhere. I think setting up the environmental bean with this information should be logged at debug level to be possible to find it https://github.com/jbosstm/narayana/blob/5.9.0.Final/ArjunaJTA/jta/classe... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3049) Setting properties via arjPropertyManager should affect all related config bean instances

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3049?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3049: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1362 > Setting properties via arjPropertyManager should affect all related config bean instances > ----------------------------------------------------------------------------------------- > > Key: JBTM-3049 > URL: https://issues.jboss.org/browse/JBTM-3049 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > Narayana configuration is performed through named configuration beans. For example the ObjectStoreEnvironmentBean has three instances for configuring different store types: > * the action store (default) > * the stateStore (with the name "stateStore") > * the communicationsStore (with the name "communicationsStore") > Each of the stores have their own getters and setters. > We also have the arjPropertyManager API which returns the default configuration beans: > {code} > public static CoreEnvironmentBean getCoreEnvironmentBean(); > public static CoordinatorEnvironmentBean getCoordinatorEnvironmentBean(); > public static ObjectStoreEnvironmentBean getObjectStoreEnvironmentBean(); > {code} > For example the getObjectStoreEnvironmentBean() call returns the config for the action store. > Historically (ie before we moved to using configuration beans) the user could set all config properties via the single instance of arjPropertyManager. For example, if the user wanted to disable file system sync'ing for the object store he would obtain an arjuna PropertyManager with which he could set a single property called OBJECTSTORE_SYNC and the setting would be applied to all writes to the object store. However, with the new/current config mechanism he would need to call the setter on each known instance of the ObjectStoreEnvironmentBean: > {code} > BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, "communicationStore").setObjectStoreSync(false); > BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, "stateStore").setObjectStoreSync(false); > BeanPopulator.getDefaultInstance(ObjectStoreEnvironmentBean.class).setObjectStoreSync(false); > {code} > This JIRA is to return to the original behaviour where calling the setters of the beans returned from arjPropertyManager should be applied to all named instances of the returned bean. > The semantics of calling the getters needs be discussed and defined. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3010) Move the tomcat-jta module out of the narayana repo

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-3010?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-3010. ------------------------------- Resolution: Duplicate Issue Seems to be a duplicate of JBTM-3030 > Move the tomcat-jta module out of the narayana repo > --------------------------------------------------- > > Key: JBTM-3010 > URL: https://issues.jboss.org/browse/JBTM-3010 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Tomcat > Reporter: Amos Feng > Assignee: Tom Jenkinson > Priority: Minor > > We tend to prefer the integration code for specific application servers be kept outside of the main Narayana transaction manager repository as it tends to iterate under different release cycle also. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3010) Move the tomcat-jta module out of the narayana repo

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-3010?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-3010: -------------------------------- Fix Version/s: (was: 5.next) > Move the tomcat-jta module out of the narayana repo > --------------------------------------------------- > > Key: JBTM-3010 > URL: https://issues.jboss.org/browse/JBTM-3010 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Tomcat > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > > We tend to prefer the integration code for specific application servers be kept outside of the main Narayana transaction manager repository as it tends to iterate under different release cycle also. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3010) Move the tomcat-jta module out of the narayana repo

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-3010?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reopened JBTM-3010: --------------------------------- > Move the tomcat-jta module out of the narayana repo > --------------------------------------------------- > > Key: JBTM-3010 > URL: https://issues.jboss.org/browse/JBTM-3010 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Tomcat > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > > We tend to prefer the integration code for specific application servers be kept outside of the main Narayana transaction manager repository as it tends to iterate under different release cycle also. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3010) Move the tomcat-jta module out of the narayana repo

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-3010?page=com.atlassian.jira.plugin.... ] Work on JBTM-3010 started by Tom Jenkinson. ------------------------------------------- > Move the tomcat-jta module out of the narayana repo > --------------------------------------------------- > > Key: JBTM-3010 > URL: https://issues.jboss.org/browse/JBTM-3010 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Tomcat > Reporter: Amos Feng > Assignee: Tom Jenkinson > Priority: Minor > > We tend to prefer the integration code for specific application servers be kept outside of the main Narayana transaction manager repository as it tends to iterate under different release cycle also. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3050) CMRIntegrationTest consistently fails on CI

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-3050?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-3050: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > CMRIntegrationTest consistently fails on CI > ------------------------------------------- > > Key: JBTM-3050 > URL: https://issues.jboss.org/browse/JBTM-3050 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Ondra Chaloupka > Priority: Blocker > Fix For: 5.next > > > Test com.hp.mwtests.ts.jta.commitmarkable.integration.CMRIntegrationTest is failing on our CI cluster, for example: > http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/PROFILE=MAIN,jdk=... > fails with the output: > {quote} > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.962 sec <<< FAILURE! - in com.hp.mwtests.ts.jta.commitmarkable.integration.CMRIntegrationTest > com.hp.mwtests.ts.jta.commitmarkable.integration.CMRIntegrationTest Time elapsed: 4.962 sec <<< ERROR! > java.lang.RuntimeException: org.jboss.as.arquillian.container.ManagementClient$UnSuccessfulOperationException: "WFLYCTL0216: Management resource '[(\"deployment\" => \"test.war\")]' not found" > Caused by: org.jboss.as.arquillian.container.ManagementClient$UnSuccessfulOperationException: "WFLYCTL0216: Management resource '[(\"deployment\" => \"test.war\")]' not found" > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2992) Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2992?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2992: --------------------------------- The tomcat 9.0.10 could work with the JDK9 > Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar > ------------------------------------------------------------------------------ > > Key: JBTM-2992 > URL: https://issues.jboss.org/browse/JBTM-2992 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.7.2.Final > Environment: Java 9 > Reporter: Michal Karm Babacek > Assignee: Amos Feng > Priority: Minor > > {code} > [ERROR] Failed to execute goal on project tomcat-jta: > Could not resolve dependencies for project > org.jboss.narayana.tomcat:tomcat-jta:jar:5.7.2.Final-SNAPSHOT: > Could not find artifact > com.sun:tools:jar:1.6 at specified path /file-not-found/tools.jar -> [Help 1] > [ERROR] > {code} > See: StackOverflow and [~ogondza]'s comments -> [link|https://stackoverflow.com/questions/35240134/declare-maven-dependenc...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 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 August 2018