February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9407) Upgrade Artemis 2.4.0

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-9407?page=com.atlassian.jira.plugin.... ] Ivo Studensky updated WFLY-9407: -------------------------------- Labels: downstream_dependency (was: ) > Upgrade Artemis 2.4.0 > --------------------- > > Key: WFLY-9407 > URL: https://issues.jboss.org/browse/WFLY-9407 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Labels: downstream_dependency > Fix For: 12.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AG-52) Fix typo in ResultSetWrapper.setFetchSize()

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-52?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-52. ----------------------------- Resolution: Done > Fix typo in ResultSetWrapper.setFetchSize() > ------------------------------------------- > > Key: AG-52 > URL: https://issues.jboss.org/browse/AG-52 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 0.3 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.4 > > > Currently calls setFetchDirection() on the wrapped ResultSet -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AG-51) Don't wrap null Statement / ResultSet

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-51?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-51. ----------------------------- Resolution: Done > Don't wrap null Statement / ResultSet > ------------------------------------- > > Key: AG-51 > URL: https://issues.jboss.org/browse/AG-51 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 0.3 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.4 > > > Do not create and return a wrapper for null Statement / ResultSet -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AG-52) Fix typo in ResultSetWrapper.setFetchSize()

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-52?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro updated AG-52: ---------------------------- Summary: Fix typo in ResultSetWrapper.setFetchSize() (was: Fix typo in ResultSetWrapper.setFetchsize()) > Fix typo in ResultSetWrapper.setFetchSize() > ------------------------------------------- > > Key: AG-52 > URL: https://issues.jboss.org/browse/AG-52 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 0.3 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.4 > > > Currently calls setFetchDirection() on the wrapped ResultSet -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AG-52) Fix typo in ResultSetWrapper.setFetchsize()

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-52?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro updated AG-52: ---------------------------- Summary: Fix typo in ResultSetWrapper.setFetchsize() (was: Fix typo in WrappedResultSet.setFetchsize()) > Fix typo in ResultSetWrapper.setFetchsize() > ------------------------------------------- > > Key: AG-52 > URL: https://issues.jboss.org/browse/AG-52 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 0.3 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.4 > > > Currently calls setFetchDirection() on the wrapped ResultSet -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AG-52) Fix typo in WrappedResultSet.setFetchsize()

by Luis Barreiro (JIRA)

Luis Barreiro created AG-52: ------------------------------- Summary: Fix typo in WrappedResultSet.setFetchsize() Key: AG-52 URL: https://issues.jboss.org/browse/AG-52 Project: Agroal Issue Type: Bug Components: pool Affects Versions: 0.3 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 0.4 Currently calls setFetchDirection() on the wrapped ResultSet -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AG-51) Don't wrap null Statement / ResultSet

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-51?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro updated AG-51: ---------------------------- Summary: Don't wrap null Statement / ResultSet (was: Do't wrap null Statement / ResultSet) > Don't wrap null Statement / ResultSet > ------------------------------------- > > Key: AG-51 > URL: https://issues.jboss.org/browse/AG-51 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 0.3 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.4 > > > Do not create and return a wrapper for null Statement / ResultSet -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2245) JGroup JDBC_PING is not clearing the crashed members

by Sibin Karnavar (JIRA)

[ https://issues.jboss.org/browse/JGRP-2245?page=com.atlassian.jira.plugin.... ] Sibin Karnavar commented on JGRP-2245: -------------------------------------- Do you know When you are planning to publish 4.0.10 Final? > JGroup JDBC_PING is not clearing the crashed members > ---------------------------------------------------- > > Key: JGRP-2245 > URL: https://issues.jboss.org/browse/JGRP-2245 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.8 > Reporter: Sibin Karnavar > Assignee: Bela Ban > Fix For: 4.0.10 > > > 1) In AWS cloud environments, IP address will be different when a node crashes and when a new cluster node gets recreated. > 2) In this situation, JGroup is not clearing logical_addr_cache and it gets confused, when we restart the cluster nodes. > 3)logical_addr_cache_max_size and the eviction did not work because, the cache is again getting updated from the ping and it never getting marked as removable. > I think the issue is > handleView method is always re writing the entire cache on view change to the db. So even if we clear the table with the help of above mentioned flags (remove_all_data_on_view_change && remove_old_coords_on_view_change) , its getting re written to the table. > {code:java} > // remove all files which are not from the current members > protected void handleView(View new_view, View old_view, boolean coord_changed) { > if(is_coord) { > if(coord_changed) { > if(remove_all_data_on_view_change) > removeAll(cluster_name); > else if(remove_old_coords_on_view_change) { > Address old_coord=old_view != null? old_view.getCreator() : null; > if(old_coord != null) > remove(cluster_name, old_coord); > } > } > if(coord_changed || View.diff(old_view, new_view)[1].length > 0) { > writeAll(); > if(remove_all_data_on_view_change || remove_old_coords_on_view_change) > startInfoWriter(); > } > } > else if(coord_changed) // I'm no longer the coordinator > remove(cluster_name, local_addr); > } > {code} > 4) Because of the crashed members (non existing ip address), we are getting lot of socket timeouts > sendToMembers of TP is trying to send messages to old crashed members and writing error logs while startup. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2245) JGroup JDBC_PING is not clearing the crashed members

by Sibin Karnavar (JIRA)

[ https://issues.jboss.org/browse/JGRP-2245?page=com.atlassian.jira.plugin.... ] Sibin Karnavar commented on JGRP-2245: -------------------------------------- I have tested it in AWS. Looks good when instances gets terminated. I am not able able to now see the TQ bundler timeout errors. Thanks for fixing it. > JGroup JDBC_PING is not clearing the crashed members > ---------------------------------------------------- > > Key: JGRP-2245 > URL: https://issues.jboss.org/browse/JGRP-2245 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.8 > Reporter: Sibin Karnavar > Assignee: Bela Ban > Fix For: 4.0.10 > > > 1) In AWS cloud environments, IP address will be different when a node crashes and when a new cluster node gets recreated. > 2) In this situation, JGroup is not clearing logical_addr_cache and it gets confused, when we restart the cluster nodes. > 3)logical_addr_cache_max_size and the eviction did not work because, the cache is again getting updated from the ping and it never getting marked as removable. > I think the issue is > handleView method is always re writing the entire cache on view change to the db. So even if we clear the table with the help of above mentioned flags (remove_all_data_on_view_change && remove_old_coords_on_view_change) , its getting re written to the table. > {code:java} > // remove all files which are not from the current members > protected void handleView(View new_view, View old_view, boolean coord_changed) { > if(is_coord) { > if(coord_changed) { > if(remove_all_data_on_view_change) > removeAll(cluster_name); > else if(remove_old_coords_on_view_change) { > Address old_coord=old_view != null? old_view.getCreator() : null; > if(old_coord != null) > remove(cluster_name, old_coord); > } > } > if(coord_changed || View.diff(old_view, new_view)[1].length > 0) { > writeAll(); > if(remove_all_data_on_view_change || remove_old_coords_on_view_change) > startInfoWriter(); > } > } > else if(coord_changed) // I'm no longer the coordinator > remove(cluster_name, local_addr); > } > {code} > 4) Because of the crashed members (non existing ip address), we are getting lot of socket timeouts > sendToMembers of TP is trying to send messages to old crashed members and writing error logs while startup. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AG-51) Do't wrap null Statement / ResultSet

by Luis Barreiro (JIRA)

Luis Barreiro created AG-51: ------------------------------- Summary: Do't wrap null Statement / ResultSet Key: AG-51 URL: https://issues.jboss.org/browse/AG-51 Project: Agroal Issue Type: Bug Components: pool Affects Versions: 0.3 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 0.4 Do not create and return a wrapper for null Statement / ResultSet -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2018