July 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by WildFly

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-1339. ------------------------------- > Ensure that JTS can use the JDK ORB provided by WildFly > ------------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2444) jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2444?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2444. ------------------------------- > jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ > --------------------------------------------------------------------------------------------- > > Key: JBTM-2444 > URL: https://issues.jboss.org/browse/JBTM-2444 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.2.0 > > > {code} > Running org.jboss.narayana.quickstarts.jta.TestCase > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 18.563 sec <<< FAILURE! > Results : > Tests in error: > org.jboss.narayana.quickstarts.jta.TestCase: Cannot deploy: test.war > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 > {code} > The log file says: > {code} > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file /home/hudson/workspace/narayana-quickstarts/wildfly-10.0.0.Alpha4-SNAPSHOT/standalone/tmp/vfs/temp/temp174d29cf17a7dbea/content-a7b7e754b2627502/WEB-INF/test-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[23,1] > Message: Unexpected element '{urn:jboss:messaging-deployment:1.0}messaging-deployment'"}} > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42) > at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55) > at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77) > ... 96 more > {code} > Which leads me to believe it is likely due to the parsing in test-jms.xml. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2453) Release the narayana-osgi-jta bundle

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2453?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2453: -------------------------------- Priority: Major (was: Blocker) > Release the narayana-osgi-jta bundle > ------------------------------------ > > Key: JBTM-2453 > URL: https://issues.jboss.org/browse/JBTM-2453 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Amos Feng > Assignee: Tom Jenkinson > Fix For: 5.2.0 > > > for KARAF-3749, they are looking for the narayana osgi jta bundle. I think we have not released it to the maven repos and it could add to the release process. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2455) Re-enable generate of javadoc jar for narayana-full

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2455?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2455: -------------------------------- Description: It seems as part of JBTM-2395 it seems the generation of the uber javadoc jar was accidentally disabled. It should be re-enabled for the next release. Workaround was to mod the pom during the release. was: It seems as part of JBTM-2395 I the generation of the uber javadoc jar was disabled. It should be re-enabled for the next release. Workaround was to mod the pom during the release. > Re-enable generate of javadoc jar for narayana-full > --------------------------------------------------- > > Key: JBTM-2455 > URL: https://issues.jboss.org/browse/JBTM-2455 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > It seems as part of JBTM-2395 it seems the generation of the uber javadoc jar was accidentally disabled. It should be re-enabled for the next release. > Workaround was to mod the pom during the release. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2455) Re-enable generate of javadoc jar for narayana-full

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2455?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2455: ------------------------------------- https://github.com/jbosstm/narayana/pull/842/files#diff-a4d765d7e7369c1ba... > Re-enable generate of javadoc jar for narayana-full > --------------------------------------------------- > > Key: JBTM-2455 > URL: https://issues.jboss.org/browse/JBTM-2455 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > It seems as part of JBTM-2395 it seems the generation of the uber javadoc jar was accidentally disabled. It should be re-enabled for the next release. > Workaround was to mod the pom during the release. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2455) Re-enable generate of javadoc jar for narayana-full

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2455: ----------------------------------- Summary: Re-enable generate of javadoc jar for narayana-full Key: JBTM-2455 URL: https://issues.jboss.org/browse/JBTM-2455 Project: JBoss Transaction Manager Issue Type: Bug Components: Build System, Documentation Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next It seems as part of JBTM-2395 I the generation of the uber javadoc jar was disabled. It should be re-enabled for the next release. Workaround was to mod the pom during the release. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2308) New JTS record types are not showing up in the tooling

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2308: -------------------------------- Fix Version/s: (was: 5.1.0) > New JTS record types are not showing up in the tooling > ------------------------------------------------------ > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.27, 5.next > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I have marked the type to enhancement since JTS participants do show up in the tooling (using records that are in-lined with records of type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple). Note that the tooling implementation does not look at records of type CosTransactions/XAResourceRecord (the only potentially useful information for the user here is the Xid and I will leave that until someone asks for it). > What is missing is instrumentation for new types: > {code} > AssumedCompleteHeuristicTransaction > AssumedCompleteHeuristicServerTransaction > AssumedCompleteTransaction > AssumedCompleteServerTransaction > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2449: -------------------------------- Issue Type: Bug (was: Feature Request) > 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)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2444) jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2444?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2444: -------------------------------- Issue Type: Bug (was: Feature Request) > jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ > --------------------------------------------------------------------------------------------- > > Key: JBTM-2444 > URL: https://issues.jboss.org/browse/JBTM-2444 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.next > > > {code} > Running org.jboss.narayana.quickstarts.jta.TestCase > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 18.563 sec <<< FAILURE! > Results : > Tests in error: > org.jboss.narayana.quickstarts.jta.TestCase: Cannot deploy: test.war > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 > {code} > The log file says: > {code} > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file /home/hudson/workspace/narayana-quickstarts/wildfly-10.0.0.Alpha4-SNAPSHOT/standalone/tmp/vfs/temp/temp174d29cf17a7dbea/content-a7b7e754b2627502/WEB-INF/test-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[23,1] > Message: Unexpected element '{urn:jboss:messaging-deployment:1.0}messaging-deployment'"}} > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42) > at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55) > at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77) > ... 96 more > {code} > Which leads me to believe it is likely due to the parsing in test-jms.xml. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2451) BlackTie quickstarts failing to deploy to WildFly

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2451?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2451: -------------------------------- Issue Type: Bug (was: Feature Request) > BlackTie quickstarts failing to deploy to WildFly > ------------------------------------------------- > > Key: JBTM-2451 > URL: https://issues.jboss.org/browse/JBTM-2451 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > Needs investigation: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-quicksta... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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