January 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2333) Blacktie subsystem build fails, because of missing org.jacorb module

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2333?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2333: -------------------------------- Summary: Blacktie subsystem build fails, because of missing org.jacorb module (was: BlacTie subsystem build fails, because of missing org.jacorb module) > Blacktie subsystem build fails, because of missing org.jacorb module > -------------------------------------------------------------------- > > Key: JBTM-2333 > URL: https://issues.jboss.org/browse/JBTM-2333 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration, BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.5 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/731/ > {code} > [ERROR] Failed to execute goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build (feature-pack-build) on project wildfly-blacktie-feature-pack: Execution feature-pack-build of goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: Some errors were encountered creating the feature pack > [ERROR] Missing module ModuleIdentifier{name='org.jacorb', slot='main'}. Module was required by [ModuleIdentifier{name='org.wildfly.extension.blacktie', slot='main'}] > [ERROR] -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2302?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2302: ----------------------------------------------- Hayk Hovsepyan <hhovsepy(a)redhat.com> changed the Status of [bug 1170567|https://bugzilla.redhat.com/show_bug.cgi?id=1170567] from ON_QA to VERIFIED > Tooling can create two mbeans for a CMR record > ---------------------------------------------- > > Key: JBTM-2302 > URL: https://issues.jboss.org/browse/JBTM-2302 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Environment: JDK8 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.25, 5.0.4 > > > The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because: > - the record is moved between the locations so there should only ever be one bean representation of it; > - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model > The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid. > The fix is to do the bean remove before adding new beans for new records. > It is unclear why the bug only happens on JDK8. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2333) BlacTie subsystem build fails, because of missing org.jacorb module

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2333?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2333: --------------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana-windows200... > BlacTie subsystem build fails, because of missing org.jacorb module > ------------------------------------------------------------------- > > Key: JBTM-2333 > URL: https://issues.jboss.org/browse/JBTM-2333 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration, BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.5 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/731/ > {code} > [ERROR] Failed to execute goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build (feature-pack-build) on project wildfly-blacktie-feature-pack: Execution feature-pack-build of goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: Some errors were encountered creating the feature pack > [ERROR] Missing module ModuleIdentifier{name='org.jacorb', slot='main'}. Module was required by [ModuleIdentifier{name='org.wildfly.extension.blacktie', slot='main'}] > [ERROR] -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2333) BlacTie subsystem build fails, because of missing org.jacorb module

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2333: ------------------------------------- Summary: BlacTie subsystem build fails, because of missing org.jacorb module Key: JBTM-2333 URL: https://issues.jboss.org/browse/JBTM-2333 Project: JBoss Transaction Manager Issue Type: Bug Components: Application Server Integration, BlackTie Reporter: Gytis Trikleris Assignee: Amos Feng Priority: Minor Fix For: 5.0.5 http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/731/ {code} [ERROR] Failed to execute goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build (feature-pack-build) on project wildfly-blacktie-feature-pack: Execution feature-pack-build of goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: Some errors were encountered creating the feature pack [ERROR] Missing module ModuleIdentifier{name='org.jacorb', slot='main'}. Module was required by [ModuleIdentifier{name='org.wildfly.extension.blacktie', slot='main'}] [ERROR] -> [Help 1] {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2302?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2302: ----------------------------------------------- Vaclav Tunka <vtunka(a)redhat.com> changed the Status of [bug 1170567|https://bugzilla.redhat.com/show_bug.cgi?id=1170567] from MODIFIED to ON_QA > Tooling can create two mbeans for a CMR record > ---------------------------------------------- > > Key: JBTM-2302 > URL: https://issues.jboss.org/browse/JBTM-2302 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Environment: JDK8 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.25, 5.0.4 > > > The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because: > - the record is moved between the locations so there should only ever be one bean representation of it; > - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model > The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid. > The fix is to do the bean remove before adding new beans for new records. > It is unclear why the bug only happens on JDK8. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 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 RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2326?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2326: ----------------------------------------------- Harald Pehl <hpehl(a)redhat.com> changed the Status of [bug 1178798|https://bugzilla.redhat.com/show_bug.cgi?id=1178798] from ASSIGNED to POST > 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 > Assignee: Tom Jenkinson > > 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 (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2332) resolve_initial_references on JDK ORB

by Mark Little (JIRA)

Mark Little created JBTM-2332: --------------------------------- Summary: resolve_initial_references on JDK ORB Key: JBTM-2332 URL: https://issues.jboss.org/browse/JBTM-2332 Project: JBoss Transaction Manager Issue Type: Feature Request Components: JTS Affects Versions: 5.0.4 Reporter: Mark Little Assignee: Michael Musgrove Check how the JDK ORB uses resolve_initial_references and that it is tied into the ORB Portability layer. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2296) Provide better way of distributing IOR to users

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2296?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2296: ----------------------------------- Another thought: CORBA already specifies how key services should be resolved using resolve_initial_references. Some ORBs may use a Name Server for this, others may statically add it via config data. Check the ORB Portability layer for these options. If we are going to stay within CORBA land then it should be done via resolve_initial_references, which may be the same as CosServices.cfg for JacORB but it could be something different for the JDK ORB. > Provide better way of distributing IOR to users > ----------------------------------------------- > > Key: JBTM-2296 > URL: https://issues.jboss.org/browse/JBTM-2296 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.0.5 > > > Original JIRA shows I used github. Maybe that's fine. Maybe not. Consider other options (too, or instead). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2323) Resume dualstack testing on the NCL CI cluster

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2323?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-2323. ------------------------------------ Resolution: Done I have configured the job on the NCL cluser: http://172.17.130.4:8080/job/narayana-dualstack/ > Resume dualstack testing on the NCL CI cluster > ---------------------------------------------- > > Key: JBTM-2323 > URL: https://issues.jboss.org/browse/JBTM-2323 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > The new CI nodes are not configured for IPv6. As this is a bit specialised it would make sense to keep this job back on the Newcastle cluster. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2296) Provide better way of distributing IOR to users

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2296?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2296: ------------------------------------- I was actually chatting to Gytis about this this morning on IRC. Allowing clients to resolve the transaction manager via an ORBInitialHost:ORBInitialPort combo seems easier than asking clients to retrieve the IOR from a shared location. He is looking at sharing on the forum a prototype docker setup that: 1. Spins up the JacORB naming service on a known port first 2. Config Narayana to connect to the name service to register the IOR Then a remote client just need the IP address of the docker VM plus this known port in order to connect to the transaction manager, rather than access to the CosServices.cfg. The other option we considered is to use a configurable name for the CosServices.cfg based on the node name so that we can have a variable number of them: https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/orbportability/... That would require sharing those files in a manner similar to our current POC. > Provide better way of distributing IOR to users > ----------------------------------------------- > > Key: JBTM-2296 > URL: https://issues.jboss.org/browse/JBTM-2296 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.0.5 > > > Original JIRA shows I used github. Maybe that's fine. Maybe not. Consider other options (too, or instead). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 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 January 2015