January 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-223) Check WL-to-JBossTS interoperability (via JTS).

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/JBTM-223?page=com.atlassian.jira.plugin.s... ] Johnathon Lee updated JBTM-223: ------------------------------- > Check WL-to-JBossTS interoperability (via JTS). > ----------------------------------------------- > > Key: JBTM-223 > URL: https://issues.jboss.org/browse/JBTM-223 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Mark Little > Assignee: Michael Musgrove > Fix For: 6.later > > > Extensible header structure corba call > key value slot ids > slot for transaction context is not in the well known slot > tx context was not defined so we used the market leader at the time -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2593) Suggest making this read_state INFO not WARN

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2593?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2593: ----------------------------------- Thanks Tom. > Suggest making this read_state INFO not WARN > -------------------------------------------- > > Key: JBTM-2593 > URL: https://issues.jboss.org/browse/JBTM-2593 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Mark Little > Priority: Minor > Fix For: 5.2.12.Final > > > I'm not sure why it was added or why it's a warning. Maybe should be info or debug? > read_state operation, ShadowingStore_6 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2603) Http request fails with internal server error in EnabledContextPropagationTests

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2603: ------------------------------------- Summary: Http request fails with internal server error in EnabledContextPropagationTests Key: JBTM-2603 URL: https://issues.jboss.org/browse/JBTM-2603 Project: JBoss Transaction Manager Issue Type: Bug Components: TxBridge Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Minor Fix For: 5.next {code} testNoTransactionWithDisabledJTAOverWSATFeature(org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests) Time elapsed: 76.255 sec <<< ERROR! org.apache.http.client.HttpResponseException: Internal Server Error at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:68) at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:54) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1070) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1044) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1035) at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.makeRequest(EnabledContextPropagationTests.java:377) at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.testNoTransactionWithDisabledJTAOverWSATFeature(EnabledContextPropagationTests.java:256) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2599) Update activemq-artemis to 1.1.0.wildfly-010

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2599?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2599: ------------------------------------- No problem and thanks to [~lbarreiro] for the contribution. > Update activemq-artemis to 1.1.0.wildfly-010 > -------------------------------------------- > > Key: JBTM-2599 > URL: https://issues.jboss.org/browse/JBTM-2599 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: Application Server Integration > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Blocker > Fix For: 5.2.12.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2599) Update activemq-artemis to 1.1.0.wildfly-010

by Ståle Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBTM-2599?page=com.atlassian.jira.plugin.... ] Ståle Pedersen commented on JBTM-2599: -------------------------------------- thanks a lot [~tomjenkinson]! - really nice to get this into wf10. > Update activemq-artemis to 1.1.0.wildfly-010 > -------------------------------------------- > > Key: JBTM-2599 > URL: https://issues.jboss.org/browse/JBTM-2599 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: Application Server Integration > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Blocker > Fix For: 5.2.12.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2115) Not all classes are under code coverage

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2115?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2115: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > Not all classes are under code coverage > --------------------------------------- > > Key: JBTM-2115 > URL: https://issues.jboss.org/browse/JBTM-2115 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.0.1 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.next > > > The following poms contain skipped classes for code coverage: > ArjunaCore/arjuna/pom.xml > ArjunaJTA/jdbc/pom.xml > ArjunaJTA/jta/pom.xml > ArjunaJTA/spi/pom.xml > XTS/localjunit/pom.xml > We should aim to test everything -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2234) out of memory when logging more messages than heap size (surefire issue)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2234?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2234: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > out of memory when logging more messages than heap size (surefire issue) > ------------------------------------------------------------------------ > > Key: JBTM-2234 > URL: https://issues.jboss.org/browse/JBTM-2234 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.0.2 > Environment: JTS testing > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > Running com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 on JacORB with about 500000 transactions results in an OOM error because surefire keeps in logs in memory until the test has finished. > In this particular test jacorb logs messages at INFO level for each transaction resulting in excessive memory requirements. We can't make the heap too large because the default JVM is 32 bit. However, we could fix it by reducing the jacorb log level to WARN. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-855) Create an example showing integration with Spring

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-855: ------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > Create an example showing integration with Spring > ------------------------------------------------- > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The main thing is to show the config but we need to provide an example that shows how to ensure the XAResources are available for recovery -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1804: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > JTS remote tests not run and no code coverage > --------------------------------------------- > > Key: JBTM-1804 > URL: https://issues.jboss.org/browse/JBTM-1804 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS, Testing > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Amos Feng > Fix For: 5.next > > > The tests in .remote. package for JTS are not run by default. We should consider adding a build option so that they are run (will require some mods to the tests since many of them are client/server based - see associated Readme.txt files); don't run them by default since they will add delay to a normal build. > It would then be beneficial to have them instrumented by emma to get code coverage. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2498) Incomplete BlackTie quickstart documentation

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2498?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2498: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > Incomplete BlackTie quickstart documentation > -------------------------------------------- > > Key: JBTM-2498 > URL: https://issues.jboss.org/browse/JBTM-2498 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Demonstrator, Documentation > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The BlackTie README.md quickstart files are out of date with respect to running against the latest wildfly. > Ideally, the quickstarts should be standalone (and automatable - run.sh nearly works but not quite) so we need better instructions on how to configure, start and deploy to wildfly. > My ideal quickstart is one from which I can cut lines and paste into a terminal in order to get it working. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 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 January 2016