July 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2440) Byteman tests fail when running with the IBM JVM

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2440?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2440: ----------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/jbosstm/narayana/pull/876, https://github.com/jbosstm/narayana/pull/882 (was: https://github.com/jbosstm/narayana/pull/876) > Byteman tests fail when running with the IBM JVM > ------------------------------------------------ > > Key: JBTM-2440 > URL: https://issues.jboss.org/browse/JBTM-2440 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Byteman instrumentation does not work with the IBM J9 JVM:- it fails with errors like the following: > {code} > *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009 > Exception in thread "Attachment 59984" Agent failed to start! > JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102 > {code} > I will implement a workaround by disabling byteman when testing with this JVM. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2440) Byteman tests fail when running with the IBM JVM

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2440?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2440: ---------------------------------------- The [IBM manual | http://download.boulder.ibm.com/ibmdl/pub/software/dw/jdk/docs/java8/lnx/...] says bq. The Attach API can be enabled by setting the com.ibm.tools.attach.enable system property to the value yes; I tried this but tests marked up with the @BMUnitRunner annotation still fail with the error JVMTI_ERROR_NOT_AVAILABLE I tried enabling it in the pom via: * systemPropertyVariables; * systemProperties; and * <argLine>-Dcom.ibm.tools.attach.enable=yes</argLine> none of which work. I am going to work around the issue using an ibm jdk profile that disables byteman tests. > Byteman tests fail when running with the IBM JVM > ------------------------------------------------ > > Key: JBTM-2440 > URL: https://issues.jboss.org/browse/JBTM-2440 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Byteman instrumentation does not work with the IBM J9 JVM:- it fails with errors like the following: > {code} > *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009 > Exception in thread "Attachment 59984" Agent failed to start! > JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102 > {code} > I will implement a workaround by disabling byteman when testing with this JVM. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2365) Create feature choice helper on narayana.io

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2365?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2365: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Create feature choice helper on narayana.io > ------------------------------------------- > > Key: JBTM-2365 > URL: https://issues.jboss.org/browse/JBTM-2365 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > It would be useful to have something on our homepage that lists all the different transports we use and what features are available when you select each of those transport. Mainly all features are available which allows us to list those too. > Ideally in the future it might replace our current landing page so we should try to include all details from that too where possible - so you could include an axis that said "commercial support available" STM = No, XTS = yes and so on. > Needs experimentation to see what will work best. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2343) Add a new Observer SPI for tracking transaction state association changes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2343?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2343: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1238926|https://bugzilla.redhat.com/show_bug.cgi?id=1238926] from NEW to MODIFIED > Add a new Observer SPI for tracking transaction state association changes > ------------------------------------------------------------------------- > > Key: JBTM-2343 > URL: https://issues.jboss.org/browse/JBTM-2343 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: SPI > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.1.0 > > > We need a new interface to enable users to track thread-to-transaction association changes. See related JBTM-2342 for details -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2449: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1235886|https://bugzilla.redhat.com/show_bug.cgi?id=1235886] from ASSIGNED to MODIFIED > SPI class ServerVMClientUserTransaction should be Serializable and Referenceable > -------------------------------------------------------------------------------- > > Key: JBTM-2449 > URL: https://issues.jboss.org/browse/JBTM-2449 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: SPI > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: > bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2449: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > SPI class ServerVMClientUserTransaction should be Serializable and Referenceable > -------------------------------------------------------------------------------- > > Key: JBTM-2449 > URL: https://issues.jboss.org/browse/JBTM-2449 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: SPI > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: > bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2449: ----------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/jbosstm/jboss-transaction-spi/pull/6, https://github.com/jbosstm/narayana/pull/881 > SPI class ServerVMClientUserTransaction should be Serializable and Referenceable > -------------------------------------------------------------------------------- > > Key: JBTM-2449 > URL: https://issues.jboss.org/browse/JBTM-2449 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: SPI > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: > bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2428) JTS client side transaction context seems not being propagated to EAP server

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2428?page=com.atlassian.jira.plugin.... ] Ondřej Chaloupka closed JBTM-2428. ---------------------------------- Resolution: Done Found this being trouble of configuration of the testcase. > JTS client side transaction context seems not being propagated to EAP server > ---------------------------------------------------------------------------- > > Key: JBTM-2428 > URL: https://issues.jboss.org/browse/JBTM-2428 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.1.1 > Reporter: Ondřej Chaloupka > Assignee: Ondřej Chaloupka > > It seems that transaction context is not propagated when JTS transaction is started on client. > This was working for EAP 6.4 where iiop corba implementation was used. The testing client is based on guide [1]. > The call from client to server via IIOP [4] works fine but when I'm trying to start transaction on client side and then expecting being propagated to server, server proclaims that there is no txn in the context. > This is how the orb is set up [2] > This is how the transaction is started [3] > This is how the remote call on ejb app server is done [4] > [1] https://developer.jboss.org/wiki/TransactionPropagationWithJBoss > [2] https://code.engineering.redhat.com/gerrit/gitweb?p=jbossqe-eap-tests-tra... > [3] https://code.engineering.redhat.com/gerrit/gitweb?p=jbossqe-eap-tests-tra... > [4] https://code.engineering.redhat.com/gerrit/gitweb?p=jbossqe-eap-tests-tra... > [5] [com.arjuna.ats.jts] (main) ARJUNA022251: The ORBManager is already associated with an ORB/OA. > FINE [javax.enterprise.resource.corba._DEFAULT_.rpc.protocol] (main) "IOP01600014: (BAD_INV_ORDER) Cannot access this attribute or method at this point": org.omg.CORBA.BAD_INV_ORDER: vmcid: OMG minor code: 14 completed: No > -- or -- > FINE [javax.enterprise.resource.corba._CORBA_.rpc.presentation] (main) "IOP00110227: (BAD_PARAM) ORBDynamicStubFactoryFactoryClass property had value com.sun.corba.se.impl.presentation.rmi.bcel.StubFactoryFactoryBCELImpl, which could not be loaded by the ORB ClassLoader": org.omg.CORBA.BAD_PARAM: vmcid: SUN minor code: 227 completed: No -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2449: ----------------------------------- Issue Type: Feature Request (was: Bug) > SPI class ServerVMClientUserTransaction should be Serializable and Referenceable > -------------------------------------------------------------------------------- > > Key: JBTM-2449 > URL: https://issues.jboss.org/browse/JBTM-2449 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: SPI > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: > bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBTM-2449: ------------------------------------------ Bugzilla Update: (was: Perform) > SPI class ServerVMClientUserTransaction should be Serializable and Referenceable > -------------------------------------------------------------------------------- > > Key: JBTM-2449 > URL: https://issues.jboss.org/browse/JBTM-2449 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: SPI > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: > bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 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 July 2015