June 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1749) Failure building Javadoc when JAVA_HOME is empty

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1749?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1749: ------------------------------------- Also, can confirm I get the same behaviour after installing sun jdk1.6.0_45, jdk7 build is still fine for me though. > Failure building Javadoc when JAVA_HOME is empty > ------------------------------------------------ > > Key: JBTM-1749 > URL: https://issues.jboss.org/browse/JBTM-1749 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Environment: Mac OSX > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M4 > > > To reproduce: > # export JAVA_HOME= > # /opt/apache-maven-3.0.5/bin/mvn clean install -DskipTests -f ./ArjunaJTA/narayana-jta/pom.xml > It also happens if you use the maven version in tools/maven (also version 3.0.5). > This doesn't fail: > # export JAVA_HOME= > # /opt/apache-maven-3.0.3/bin/mvn clean install -DskipTests -f ./ArjunaJTA/narayana-jta/pom.xml > Currently only seen this on a Mac. Would be good if a linux user could try to reproduce. > Maven 3.0.5 is the latest release. I've not found a known issue for this, but it is hard to search for. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1749) Failure building Javadoc when JAVA_HOME is empty

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1749?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-1749: --------------------------------------- Also failed for me with OpenJDK 1.6.0_27. > Failure building Javadoc when JAVA_HOME is empty > ------------------------------------------------ > > Key: JBTM-1749 > URL: https://issues.jboss.org/browse/JBTM-1749 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Environment: Mac OSX > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M4 > > > To reproduce: > # export JAVA_HOME= > # /opt/apache-maven-3.0.5/bin/mvn clean install -DskipTests -f ./ArjunaJTA/narayana-jta/pom.xml > It also happens if you use the maven version in tools/maven (also version 3.0.5). > This doesn't fail: > # export JAVA_HOME= > # /opt/apache-maven-3.0.3/bin/mvn clean install -DskipTests -f ./ArjunaJTA/narayana-jta/pom.xml > Currently only seen this on a Mac. Would be good if a linux user could try to reproduce. > Maven 3.0.5 is the latest release. I've not found a known issue for this, but it is hard to search for. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1747) CNFE when invoking a plain Web service with standalone-xts.xml config

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1747?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1747: ---------------------------------- Original Estimate: 2 days Remaining Estimate: 2 days > CNFE when invoking a plain Web service with standalone-xts.xml config > --------------------------------------------------------------------- > > Key: JBTM-1747 > URL: https://issues.jboss.org/browse/JBTM-1747 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > I've not had chance to reproduce this, but this is what I think I did: > 1. Start Wildfly with the standalone-xts.xml configuration > 2. Deploy a plain (non-XTS) web service to the server > 3. Invoke the web service from inside this server, ensuring that org.jboss.xts is not in the dependencies. Which it shouldn't be if you are just invoking a plain WS. > 4. Observe the CNFE on one of the TXBridge interceptors (I don't remember which). > I think the problem is that XTS is adding the handler chain for doing default context propagation to all web services, rather than just those that have the XTS dependency. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1728) Use a global environment variable in CI for version numbers of Narayana and WildFly

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1728?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1728: ---------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > Use a global environment variable in CI for version numbers of Narayana and WildFly > ----------------------------------------------------------------------------------- > > Key: JBTM-1728 > URL: https://issues.jboss.org/browse/JBTM-1728 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System, Testing > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > We have "8.0.0.Alpha2-SNAPSHOT" scattered over many jobs. This is a pain to change every time we have a new release of Wildfly. > We should use a global env variable instead. See the following for how to do it. Notice that I have already added one for Narayana. > http://172.17.131.2/configure > Call the variable WILDFLY_CURRENT_VERSION and set it to "8.0.0.Alpha2-SNAPSHOT". > Ask paul to update the sanity check job before this is done. This will blacklist the usage of hardcoded wildfly version numbers. It will make it a lot easier to find all the places it is used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1730) narayana-dualstack does not test TXF and ArjunaJTA/cdi

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1730?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1730: ---------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > narayana-dualstack does not test TXF and ArjunaJTA/cdi > ------------------------------------------------------ > > Key: JBTM-1730 > URL: https://issues.jboss.org/browse/JBTM-1730 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA, Testing, TXFramework > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Notice these lines of output: > {code} > The requested profile "arqIPv6" could not be activated because it does not exist. > {code} > in: > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-dualstack/108/con... > Maybe we could make narayana.sh fail if this problem occurs. Better than it failing silently as it does now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1678) JTA 1.2 @Transactional for compensations

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1678?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1678: ---------------------------------- Original Estimate: 2 weeks Remaining Estimate: 2 weeks > JTA 1.2 @Transactional for compensations > ---------------------------------------- > > Key: JBTM-1678 > URL: https://issues.jboss.org/browse/JBTM-1678 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Essentially offer comparable features for Compensations as those defined for JTA in the @Transactional section of the JTA spec. > We can re-use the code and tests from our JTA 1.2 implementation. It may be possible to extend those impls, otherwise it's a copy-and-paste. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1749) Failure building Javadoc when JAVA_HOME is empty

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-1749?page=com.atlassian.jira.plugin.... ] Ondřej Chaloupka commented on JBTM-1749: ---------------------------------------- Hi, I'm hitting the same problem probably. I work on fedora 16 and setting the JAVA_HOME does not help (for JDK 1.6). It helps to switch to 1.7. It does not matter of using maven 3.0.3 or 3.0.5 export JAVA_HOME=/opt/jdk1.6.0_43 mvn -version Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100) Maven home: /home/ochaloup/Programs/apache-maven-3.0.5 Java version: 1.6.0_43, vendor: Sun Microsystems Inc. > Failure building Javadoc when JAVA_HOME is empty > ------------------------------------------------ > > Key: JBTM-1749 > URL: https://issues.jboss.org/browse/JBTM-1749 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Environment: Mac OSX > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M4 > > > To reproduce: > # export JAVA_HOME= > # /opt/apache-maven-3.0.5/bin/mvn clean install -DskipTests -f ./ArjunaJTA/narayana-jta/pom.xml > It also happens if you use the maven version in tools/maven (also version 3.0.5). > This doesn't fail: > # export JAVA_HOME= > # /opt/apache-maven-3.0.3/bin/mvn clean install -DskipTests -f ./ArjunaJTA/narayana-jta/pom.xml > Currently only seen this on a Mac. Would be good if a linux user could try to reproduce. > Maven 3.0.5 is the latest release. I've not found a known issue for this, but it is hard to search for. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1479) Create a quickstart to show how to use IronJacamar and JBTM inside tomcat

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1479?page=com.atlassian.jira.plugin.... ] Work on JBTM-1479 started by Gytis Trikleris. > Create a quickstart to show how to use IronJacamar and JBTM inside tomcat > ------------------------------------------------------------------------- > > Key: JBTM-1479 > URL: https://issues.jboss.org/browse/JBTM-1479 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > Attachments: test-ds.xml, transaction.xml > > Original Estimate: 3 days > Time Spent: 1 week, 2 days, 1 hour, 20 minutes > Remaining Estimate: 0 minutes > > See JBTM-809 for the algorithm > You might want to put the startup in the context listener: > public class MyServletContextListener implements ServletContextListener { > public void contextInitialized(ServletContextEvent sce) { > // Initialize RecoveryManager > // Initialize TransactionManager > // Initialize IronJacamar > } > > @Override > public void contextDestroyed(ServletContextEvent sce) { > // Clean IronJacamar > // Clean TransactionManager > // Clean RecoveryManager > } > } > Quickstart application should connect to the database (say PostgreSQL), dummy XA resource and coordinate the transaction. The PostgreSQL data source needs to be accessed via IronJacamar. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1479) Create a quickstart to show how to use IronJacamar and JBTM inside tomcat

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1479?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1479: ---------------------------------- Status: Open (was: Pull Request Sent) > Create a quickstart to show how to use IronJacamar and JBTM inside tomcat > ------------------------------------------------------------------------- > > Key: JBTM-1479 > URL: https://issues.jboss.org/browse/JBTM-1479 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > Attachments: test-ds.xml, transaction.xml > > Original Estimate: 3 days > Time Spent: 1 week, 2 days, 1 hour, 20 minutes > Remaining Estimate: 0 minutes > > See JBTM-809 for the algorithm > You might want to put the startup in the context listener: > public class MyServletContextListener implements ServletContextListener { > public void contextInitialized(ServletContextEvent sce) { > // Initialize RecoveryManager > // Initialize TransactionManager > // Initialize IronJacamar > } > > @Override > public void contextDestroyed(ServletContextEvent sce) { > // Clean IronJacamar > // Clean TransactionManager > // Clean RecoveryManager > } > } > Quickstart application should connect to the database (say PostgreSQL), dummy XA resource and coordinate the transaction. The PostgreSQL data source needs to be accessed via IronJacamar. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1364) Migrate "REST-AT to JTA" bridge into REST-TX component

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1364?page=com.atlassian.jira.plugin.... ] Work on JBTM-1364 stopped by Gytis Trikleris. > Migrate "REST-AT to JTA" bridge into REST-TX component > ------------------------------------------------------ > > Key: JBTM-1364 > URL: https://issues.jboss.org/browse/JBTM-1364 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, REST, TxBridge > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Labels: assign > Fix For: 5.0.0.M4 > > Original Estimate: 1 week > Time Spent: 3 days > Remaining Estimate: 2 days > > The task is to the work Gytis did on his internship and migrate it into the REST-TX project. > Tasks: > 1. Review the current solution looking for: > 1.1 Major issues that prevent an initial release > 1.2 Test coverage > 2. Make any required changes > 3. Merge into the REST-TX project > 4. Migrate the quickstarts accross > 5. Create a blog post > 5.1 Consider what the end user will need to do to use this technology. We may want to wait until REST-AT and this Bridge are shipped with a Narayana build of AS7. Otherwise the steps to get this working could be rather lengthy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2013