May 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2076) Add security manager's permission checking in com.arjuna.webservices11.ServiceRegistry#getRegistry

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2076?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2076: ----------------------------------------------- Gytis Trikleris <gtrikler(a)redhat.com> changed the Status of [bug 1054888|https://bugzilla.redhat.com/show_bug.cgi?id=1054888] from NEW to MODIFIED > Add security manager's permission checking in com.arjuna.webservices11.ServiceRegistry#getRegistry > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2076 > URL: https://issues.jboss.org/browse/JBTM-2076 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 4.17.19, 5.0.2 > > > Permissions checking in public static methods is needed for Common Criteria certification. > Add something similar to this at the beginning of the method: > {code} > public static ServiceRegistry getRegistry() > { > SecurityManager sm = System.getSecurityManager(); > if (sm != null) { > sm.checkPermission(new RuntimePermission(ServiceRegistry.class.getName() + ".getRegistry")); > } > return REGISTRY ; > } > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2165) CMR synchronisations should be interposed

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2165: -------------------------------------- Summary: CMR synchronisations should be interposed Key: JBTM-2165 URL: https://issues.jboss.org/browse/JBTM-2165 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Affects Versions: 5.0.1, 4.17.19 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 4.17.20, 5.0.2 A CMR resource registers a synchronization to perform deferred cleanup of xids. Since it is possible for another synchronization to enlist a CMR resource the CMR synch must be ordered after non interposed synchronizations. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2165) CMR synchronisations should be interposed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2165?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBTM-2165: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1095413 > CMR synchronisations should be interposed > ----------------------------------------- > > Key: JBTM-2165 > URL: https://issues.jboss.org/browse/JBTM-2165 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.19, 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.20, 5.0.2 > > > A CMR resource registers a synchronization to perform deferred cleanup of xids. Since it is possible for another synchronization to enlist a CMR resource the CMR synch must be ordered after non interposed synchronizations. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2124) Add orphan detection for JTS interposition mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2124?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2124: ----------------------------------------------- Ondrej Chaloupka <ochaloup(a)redhat.com> changed the Status of [bug 1064170|https://bugzilla.redhat.com/show_bug.cgi?id=1064170] from NEW to CLOSED > Add orphan detection for JTS interposition mode > ----------------------------------------------- > > Key: JBTM-2124 > URL: https://issues.jboss.org/browse/JBTM-2124 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.17 > Reporter: Ondřej Chaloupka > Assignee: Tom Jenkinson > > Currently orphan detection is supported for JTA, not for JTS. Please, add the suport for JTS as well. > The following scenario for JTS causes that the orphan is left in the transaction log store and the prepared resource could held the lock till the time that it's timeouted on the side of the database/jms. > The program flow is following (test run on EAP 6) > enlisting jms xaresource to transaction > sending msg to queue > enlisting xa test resource > preparing jms xaresource > preparing xa test resource > crash JVM at the end of the test XAResource.prepare() > restart app server and recovery is run > During recovery the jms resource is processed correctly because TM found some info in its jts logs. But such info was not saved for test xa resource. The test xa is not rollback. > More info and discussion could be found at: https://bugzilla.redhat.com/show_bug.cgi?id=1064170 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2110) Investigate support for IBM ORB

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2110?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2110: ---------------------------------------- PR (http://172.17.131.2/view/Narayana+BlackTie-pulls/job/btny-pulls-narayana/...) adds support without recovery > Investigate support for IBM ORB > ------------------------------- > > Key: JBTM-2110 > URL: https://issues.jboss.org/browse/JBTM-2110 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.2 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2164) CI app server rebase not working on Mac in narayana.sh

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2164?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2164: ------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana/505/ http://172.17.131.2/view/Narayana+BlackTie/job/narayana/506/ http://172.17.131.2/view/Narayana+BlackTie/job/narayana/507/ > CI app server rebase not working on Mac in narayana.sh > ------------------------------------------------------ > > Key: JBTM-2164 > URL: https://issues.jboss.org/browse/JBTM-2164 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Build System > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Critical > > Seems to be occurring since the app server updated to 8.1.0.Final-SNAPSHOT. It could be an issue with the grep/sed for the app server version. > {quote} > Building AS > First time checkout of AS7 > Cloning into jboss-as... > From https://github.com/wildfly/wildfly > * [new branch] 7.1 -> upstream/7.1 > * [new branch] 7.1-ignore -> upstream/7.1-ignore > * [new branch] master -> upstream/master > * [new branch] master-ignore -> upstream/master-ignore > * [new tag] 7.1.2-prerelease -> 7.1.2-prerelease > * [new tag] 7.1.2.Final -> 7.1.2.Final > * [new tag] 7.1.3.Beta1 -> 7.1.3.Beta1 > * [new tag] 7.2.0.Final -> 7.2.0.Final > * [new tag] 7.2.0.Final-prerelease1 -> 7.2.0.Final-prerelease1 > * [new tag] 8.0.0.Alpha1 -> 8.0.0.Alpha1 > * [new tag] 8.0.0.Alpha2 -> 8.0.0.Alpha2 > * [new tag] 8.0.0.Alpha3 -> 8.0.0.Alpha3 > * [new tag] 8.0.0.Alpha4 -> 8.0.0.Alpha4 > * [new tag] 8.0.0.Beta1 -> 8.0.0.Beta1 > * [new tag] 8.0.0.CR1 -> 8.0.0.CR1 > * [new tag] 8.0.0.Final -> 8.0.0.Final > * [new tag] 8.1.0.CR1 -> 8.1.0.CR1 > This is the JBoss-AS commit > 4e5271d07ace06e19745b933f9141f718bdce1b5 > From https://github.com/wildfly/wildfly > * branch master -> FETCH_HEAD > Current branch 5_BRANCH is up to date. > AS version is <version>8.1.0.Final-SNAPSHOT</version> > Need to upgrade the jboss-as.version in the narayana pom.xml to > Build step 'Execute shell' marked build as failure > Archiving artifacts > Sending e-mails to: ***** > Finished: FAILURE > {quote} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2164) CI app server rebase not working on Mac in narayana.sh

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2164: ----------------------------------- Summary: CI app server rebase not working on Mac in narayana.sh Key: JBTM-2164 URL: https://issues.jboss.org/browse/JBTM-2164 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: BlackTie, Build System Reporter: Tom Jenkinson Assignee: Amos Feng Priority: Critical Seems to be occurring since the app server updated to 8.1.0.Final-SNAPSHOT. It could be an issue with the grep/sed for the app server version. {quote} Building AS First time checkout of AS7 Cloning into jboss-as... >From https://github.com/wildfly/wildfly * [new branch] 7.1 -> upstream/7.1 * [new branch] 7.1-ignore -> upstream/7.1-ignore * [new branch] master -> upstream/master * [new branch] master-ignore -> upstream/master-ignore * [new tag] 7.1.2-prerelease -> 7.1.2-prerelease * [new tag] 7.1.2.Final -> 7.1.2.Final * [new tag] 7.1.3.Beta1 -> 7.1.3.Beta1 * [new tag] 7.2.0.Final -> 7.2.0.Final * [new tag] 7.2.0.Final-prerelease1 -> 7.2.0.Final-prerelease1 * [new tag] 8.0.0.Alpha1 -> 8.0.0.Alpha1 * [new tag] 8.0.0.Alpha2 -> 8.0.0.Alpha2 * [new tag] 8.0.0.Alpha3 -> 8.0.0.Alpha3 * [new tag] 8.0.0.Alpha4 -> 8.0.0.Alpha4 * [new tag] 8.0.0.Beta1 -> 8.0.0.Beta1 * [new tag] 8.0.0.CR1 -> 8.0.0.CR1 * [new tag] 8.0.0.Final -> 8.0.0.Final * [new tag] 8.1.0.CR1 -> 8.1.0.CR1 This is the JBoss-AS commit 4e5271d07ace06e19745b933f9141f718bdce1b5 >From https://github.com/wildfly/wildfly * branch master -> FETCH_HEAD Current branch 5_BRANCH is up to date. AS version is <version>8.1.0.Final-SNAPSHOT</version> Need to upgrade the jboss-as.version in the narayana pom.xml to Build step 'Execute shell' marked build as failure Archiving artifacts Sending e-mails to: ***** Finished: FAILURE {quote} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2159) It is possible for the CommitMarkableResource recovery manager to attempt to activate an AtomicAction while it is being committed which can cause filenotfoundstacktrace and NullPointerException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2159?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBTM-2159: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1089251 > It is possible for the CommitMarkableResource recovery manager to attempt to activate an AtomicAction while it is being committed which can cause filenotfoundstacktrace and NullPointerException > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2159 > URL: https://issues.jboss.org/browse/JBTM-2159 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > Basically: > 1. App thread creates AA > 2. AA UID is seen in phase1 recovery thread by CommitMarkableResourceRecoveryModule > 3. App thread commits AA > 4. App thread deletes AA UID > 5. Recovery thread tries to activate AA with UID in CommitMarkableResourceRecoveryModule but it gets exceptions as shown here: > 12:23:07 [0m[33m12:23:07,915 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Could not query objectstore: : java.io.IOException: java.lang.NullPointerException > 12:23:07 at com.arjuna.ats.arjuna.StateManager.unpackHeader(StateManager.java:732) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 12:23:07 at com.arjuna.ats.internal.jta.recovery.arjunacore.RecoverConnectableAtomicAction.<init>(RecoverConnectableAtomicAction.java:52) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 12:23:07 at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.periodicWorkFirstPass(CommitMarkableResourceRecordRecoveryModule.java:379) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 12:23:07 at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:743) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 12:23:07 at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 12:23:07 Caused by: java.lang.NullPointerException > 12:23:07 at com.arjuna.ats.arjuna.StateManager.unpackHeader(StateManager.java:697) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 12:23:07 ... 4 more > 12:23:07 > 15:16:36 [0m[33m15:16:36,247 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Could not query objectstore: : com.arjuna.ats.arjuna.exceptions.ObjectStoreException: ShadowingStore::read_state error: java.io.FileNotFoundException: /tmp/activemq-soak/ibm-mq-testsuite/src/test/config/activemq/install/target/jboss-eap/standalone/data/tx-object-store/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/0_ffff0a106418_-2b02421b_534ffd61_4c1764 (No such file or directory) > 15:16:36 at com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore.read_state(ShadowingStore.java:412) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 15:16:36 at com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.read_committed(FileSystemStore.java:98) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 15:16:36 at com.arjuna.ats.internal.jta.recovery.arjunacore.RecoverConnectableAtomicAction.<init>(RecoverConnectableAtomicAction.java:48) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 15:16:36 at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.periodicWorkFirstPass(CommitMarkableResourceRecordRecoveryModule.java:379) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 15:16:36 at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:743) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 15:16:36 at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 15:16:36 Caused by: java.io.FileNotFoundException: /tmp/activemq-soak/ibm-mq-testsuite/src/test/config/activemq/install/target/jboss-eap/standalone/data/tx-object-store/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/0_ffff0a106418_-2b02421b_534ffd61_4c1764 (No such file or directory) > 15:16:36 at java.io.FileInputStream.open(Native Method) [rt.jar:1.7.0_51] > 15:16:36 at java.io.FileInputStream.<init>(FileInputStream.java:146) [rt.jar:1.7.0_51] > 15:16:36 at com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore.read_state(ShadowingStore.java:406) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 15:16:36 ... 5 more > 15:16:36 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2101) Blacktie integration CSTest hang

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2101?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2101: ---------------------------- Priority: Major (was: Minor) > Blacktie integration CSTest hang > -------------------------------- > > Key: JBTM-2101 > URL: https://issues.jboss.org/browse/JBTM-2101 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/427/PROFILE=BLACK... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2101) Blacktie integration CSTest hang

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2101?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2101: --------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana/504/PROFILE=BLACK... > Blacktie integration CSTest hang > -------------------------------- > > Key: JBTM-2101 > URL: https://issues.jboss.org/browse/JBTM-2101 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/427/PROFILE=BLACK... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 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 May 2014