February 2016 - jbossts-issues - Jboss List Archives

[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: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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: Tom Jenkinson > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2617: --------------------------------------- You're correct. Workflow seems to be safe to create/remove connection only on XAResource.recovery calls with TMSTARTRSCAN/TMENDRSCAN attributes. > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2624) Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2624?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2624: ------------------------------------- Lets create a forum topic to define the scope. But first try to get an inventory of the available operations and include that in your posting. > Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf > ----------------------------------------------------------------------------------- > > Key: JBTM-2624 > URL: https://issues.jboss.org/browse/JBTM-2624 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > > {quote} > We have several management ways in Karaf : > * mbeans (no need to rewrap them) > * shell commands > * a servlet for the felix web console (used by the community) > * a hawtio plugin (used by fuse) > The first two are the most important imho. > {quote} > the manual interventions that may be needed if the heuristic fails to rollback / commit the transactions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2624) Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2624?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2624: ------------------------------------- I think we should look to expose the same functionality as we have in the WildFly CLI. /cc [~mmusgrov] for an idea on where to get the list of functionality. We need at least probe: https://github.com/wildfly/wildfly/blob/0c68aa0ebef3682e9ded4b473e24463b3... But we likely need others too: https://github.com/wildfly/wildfly/blob/0c68aa0ebef3682e9ded4b473e24463b3... > Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf > ----------------------------------------------------------------------------------- > > Key: JBTM-2624 > URL: https://issues.jboss.org/browse/JBTM-2624 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > > {quote} > We have several management ways in Karaf : > * mbeans (no need to rewrap them) > * shell commands > * a servlet for the felix web console (used by the community) > * a hawtio plugin (used by fuse) > The first two are the most important imho. > {quote} > the manual interventions that may be needed if the heuristic fails to rollback / commit the transactions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2578) Make "junit-jdbc-ncl-testsuite" testsuite of Narayana/qa compatible with IPv6

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/JBTM-2578?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan reassigned JBTM-2578: ------------------------------------ Assignee: Daniel Simko (was: Hayk Hovsepyan) > Make "junit-jdbc-ncl-testsuite" testsuite of Narayana/qa compatible with IPv6 > ----------------------------------------------------------------------------- > > Key: JBTM-2578 > URL: https://issues.jboss.org/browse/JBTM-2578 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Hayk Hovsepyan > Assignee: Daniel Simko > > Currently JDBC tests from "junit-jdbc-ncl-testsuite" testsuite of narayana/qa tsts fail while running on pure IPv6 machine. > The reason is that it is designed to connect to databases via IPv4 protocol, and there are hostnames of DB's specified in project. > It needs to be modified to connect to databases via IPv6 addresses protocol and run tests on pure Ipv6 machine. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2624) Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf

by Amos Feng (JIRA)

Amos Feng created JBTM-2624: ------------------------------- Summary: Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf Key: JBTM-2624 URL: https://issues.jboss.org/browse/JBTM-2624 Project: JBoss Transaction Manager Issue Type: Feature Request Reporter: Amos Feng Assignee: Amos Feng Priority: Minor {quote} We have several management ways in Karaf : * mbeans (no need to rewrap them) * shell commands * a servlet for the felix web console (used by the community) * a hawtio plugin (used by fuse) The first two are the most important imho. {quote} the manual interventions that may be needed if the heuristic fails to rollback / commit the transactions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2617: ------------------------------------- I suppose it depends how the driver is implemented but if its not pooling and established a connection and shut it down everytime it would have an effect on the overall life span of the server. As XARecoveryModule is last in the list https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/narayana-jts-id... TMENDRSCAN will be called after transaction recovery IMO it should therefore be safe. > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2617: --------------------------------------- My initial plan was to do this in between recover(TMSTARTRSCAN) and recover(TMENDRSCAN). However, I wasn't sure that all other calls e.g. commit are only executed in that time frame. If they're not, connection wouldn't be active and the call would fail. I agree with the performance, however my thought was that since it's during the recovery time it's not an issue. > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2617: ------------------------------------- It looks like it would perform (really) badly. May I suggest you get hold of the connection in recover(TMSTARTRSCAN) and release it in recover(TMENDRSCAN) - happy to discuss on forum if its easier. > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2617: --------------------------------------- I've just pushed the fix for this. Instead of holding connection in the recovery helper forever, I've implemented XAResource interface for it. Recovery helper acts as a proxy for JMS XAResource during recovery. It then creates and closes connections when needed. https://github.com/gytis/narayana/commit/781869d9c46ca994efe31f8acc773c46... > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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 February 2016