November 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4013) The value of the bound attribute in socket-binding-group messaging is always false

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-4013?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-4013: ------------------------------ Fix Version/s: 9.0.0.Beta1 > The value of the bound attribute in socket-binding-group messaging is always false > ---------------------------------------------------------------------------------- > > Key: WFLY-4013 > URL: https://issues.jboss.org/browse/WFLY-4013 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: JBoss AS7 7.2.0.Final > Environment: JBoss EAP 6.3.1. > Reporter: Tom Ross > Assignee: Jeff Mesnil > Fix For: 9.0.0.Beta1 > > > The value of bound attribute in messaging socket group is always false. > {noformat} > /socket-binding-group=standard-sockets/socket-binding=messaging:read-resource(include-runtime=true, recursive=true) > { > "outcome" => "success", > "result" => { > "bound" => false, > "bound-address" => undefined, > "bound-port" => undefined, > "client-mappings" => undefined, > "fixed-port" => false, > "interface" => undefined, > "multicast-address" => undefined, > "multicast-port" => undefined, > "name" => "messaging", > "port" => 5445 > } > {noformat} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1898) FD_HOST many false suspect with Full GC

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1898?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-1898: ----------------------------------------------- Radim Vansa <rvansa(a)redhat.com> changed the Status of [bug 1159162|https://bugzilla.redhat.com/show_bug.cgi?id=1159162] from ON_QA to VERIFIED > FD_HOST many false suspect with Full GC > --------------------------------------- > > Key: JGRP-1898 > URL: https://issues.jboss.org/browse/JGRP-1898 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 3.5.1 > Reporter: Takayoshi Kimura > Assignee: Takayoshi Kimura > Fix For: 3.4.7, 3.5.2, 3.6.1 > > Attachments: FD_HOSTTest.java, test-fdhost.zip > > > Currently FD_HOST PingTask has 2 loops, ping loop and cheking timeout loop. > {code} > for (h: hosts) { ping_and_update_timestamp(host) } > current = System.currentTimeMillis(); > for (h: hosts) { compare current and (ping_timestmp + timeout) } > {code} > Testing with large number of hosts, after lengthy Full GC during the ping loop, FD_HOST checks timeout and it counts the Full GC time in, sometimes causes many false suspects. > For example, 1 min Full GC and 50 sec timeout, all hosts are suspected with current implementation. > To reduce the impact of the Full GC time, we can combine the 2 loops into 1 loop, ping and checking timeout each host, so the Full GC delay only affects to a single host and never affect to other hosts. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1898) FD_HOST many false suspect with Full GC

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/JGRP-1898?page=com.atlassian.jira.plugin.... ] Radim Vansa edited comment on JGRP-1898 at 11/27/14 9:46 AM: ------------------------------------------------------------- Attached unit test reproduces the issue (and verifies that it's fixed). was (Author: rvansa): This unit test reproduces the issue (and verifies that it's fixed). > FD_HOST many false suspect with Full GC > --------------------------------------- > > Key: JGRP-1898 > URL: https://issues.jboss.org/browse/JGRP-1898 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 3.5.1 > Reporter: Takayoshi Kimura > Assignee: Takayoshi Kimura > Fix For: 3.4.7, 3.5.2, 3.6.1 > > Attachments: FD_HOSTTest.java, test-fdhost.zip > > > Currently FD_HOST PingTask has 2 loops, ping loop and cheking timeout loop. > {code} > for (h: hosts) { ping_and_update_timestamp(host) } > current = System.currentTimeMillis(); > for (h: hosts) { compare current and (ping_timestmp + timeout) } > {code} > Testing with large number of hosts, after lengthy Full GC during the ping loop, FD_HOST checks timeout and it counts the Full GC time in, sometimes causes many false suspects. > For example, 1 min Full GC and 50 sec timeout, all hosts are suspected with current implementation. > To reduce the impact of the Full GC time, we can combine the 2 loops into 1 loop, ping and checking timeout each host, so the Full GC delay only affects to a single host and never affect to other hosts. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1898) FD_HOST many false suspect with Full GC

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/JGRP-1898?page=com.atlassian.jira.plugin.... ] Radim Vansa updated JGRP-1898: ------------------------------ Attachment: FD_HOSTTest.java This unit test reproduces the issue (and verifies that it's fixed). > FD_HOST many false suspect with Full GC > --------------------------------------- > > Key: JGRP-1898 > URL: https://issues.jboss.org/browse/JGRP-1898 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 3.5.1 > Reporter: Takayoshi Kimura > Assignee: Takayoshi Kimura > Fix For: 3.4.7, 3.5.2, 3.6.1 > > Attachments: FD_HOSTTest.java, test-fdhost.zip > > > Currently FD_HOST PingTask has 2 loops, ping loop and cheking timeout loop. > {code} > for (h: hosts) { ping_and_update_timestamp(host) } > current = System.currentTimeMillis(); > for (h: hosts) { compare current and (ping_timestmp + timeout) } > {code} > Testing with large number of hosts, after lengthy Full GC during the ping loop, FD_HOST checks timeout and it counts the Full GC time in, sometimes causes many false suspects. > For example, 1 min Full GC and 50 sec timeout, all hosts are suspected with current implementation. > To reduce the impact of the Full GC time, we can combine the 2 loops into 1 loop, ping and checking timeout each host, so the Full GC delay only affects to a single host and never affect to other hosts. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3548) JTA synchronization for a distributed transaction called with incorrect TCCL

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-3548?page=com.atlassian.jira.plugin.... ] Martin Kouba updated WFLY-3548: ------------------------------- Fix Version/s: 9.0.0.Beta1 > JTA synchronization for a distributed transaction called with incorrect TCCL > ---------------------------------------------------------------------------- > > Key: WFLY-3548 > URL: https://issues.jboss.org/browse/WFLY-3548 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 8.1.0.Final > Reporter: Martin Kouba > Assignee: Martin Kouba > Fix For: 9.0.0.Beta1 > > > It seems the RequestProcessor which is processing JTA synchronizations > does not have the right TCCL set. > As a result, during synchronization invocation: > * {{NameNotFoundException}} is thrown for a JNDI lookup of "java:comp/UserTransaction" > * if we try to acccess {{org.jboss.weld.Container}} by means of {{org.jboss.as.weld.services.ModuleGroupSingletonProvider.TCCLSingleton}}, we get ISE: "Singleton not set....This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment." -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3548) JTA synchronization for a distributed transaction called with incorrect TCCL

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-3548?page=com.atlassian.jira.plugin.... ] Martin Kouba commented on WFLY-3548: ------------------------------------ The {{NameNotFoundException}} is gone and the CDI TCK test is passing. Waiting for the verification of the second part of the issue (TCCL). > JTA synchronization for a distributed transaction called with incorrect TCCL > ---------------------------------------------------------------------------- > > Key: WFLY-3548 > URL: https://issues.jboss.org/browse/WFLY-3548 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 8.1.0.Final > Reporter: Martin Kouba > Assignee: Martin Kouba > > It seems the RequestProcessor which is processing JTA synchronizations > does not have the right TCCL set. > As a result, during synchronization invocation: > * {{NameNotFoundException}} is thrown for a JNDI lookup of "java:comp/UserTransaction" > * if we try to acccess {{org.jboss.weld.Container}} by means of {{org.jboss.as.weld.services.ModuleGroupSingletonProvider.TCCLSingleton}}, we get ISE: "Singleton not set....This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment." -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3688) datasources subsystem: datasource and xa-datasource properties do not support the use of multiple values for one property

by Tom Fonteyne (JIRA)

[ https://issues.jboss.org/browse/WFLY-3688?page=com.atlassian.jira.plugin.... ] Tom Fonteyne updated WFLY-3688: ------------------------------- Steps to Reproduce: I logged this as a bug due to the fact we certify with the Oracle JDBC driver. It could be argued this is an RFE. I can see two solutions. 1. Limited to datasource and xa-datasource: org.jboss.as.connector.subsystems.datasources.DsParser.java -> schema change so a list of values can be assigned to a single xa-property, in JCA support a call to setXXX(java.util.Properties) 2. a universal fix to the ModelNode class to allow java.util.Properties was: I logged this as a bug due to the fact we certify with the Oracle JDBC driver. It could be argued this is an RFE. I can see two solutions. 1. Limited to xa-datasource: org.jboss.as.connector.subsystems.datasources.DsParser.java -> schema change so a list of values can be assigned to a single xa-property, in JCA support a call to setXXX(java.util.Properties) 2. a universal fix to the ModelNode class to allow java.util.Properties > datasources subsystem: datasource and xa-datasource properties do not support the use of multiple values for one property > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-3688 > URL: https://issues.jboss.org/browse/WFLY-3688 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 8.1.0.Final > Reporter: Tom Fonteyne > Assignee: Stefano Maestri > > The oracle JDBC driver had a method: > setConnectionProperties(java.util.Properties value) > which is needed to set several connection properties for datasources. > Most (all?) of these connection properties do not have individual setters. > WildFly does not support setting a "Properties" value for "xa-datasource-property" -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3688) datasources subsystem: datasource and xa-datasource properties do not support the use of multiple values for one property

by Tom Fonteyne (JIRA)

[ https://issues.jboss.org/browse/WFLY-3688?page=com.atlassian.jira.plugin.... ] Tom Fonteyne updated WFLY-3688: ------------------------------- Description: The oracle JDBC driver had a method: setConnectionProperties(java.util.Properties value) which is needed to set several connection properties for datasources. Most (all?) of these connection properties do not have individual setters. WildFly does not support setting a "Properties" value for "datasource-property" was: The oracle JDBC driver had a method: setConnectionProperties(java.util.Properties value) which is needed to set several connection properties for datasources. Most (all?) of these connection properties do not have individual setters. WildFly does not support setting a "Properties" value for "xa-datasource-property" > datasources subsystem: datasource and xa-datasource properties do not support the use of multiple values for one property > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-3688 > URL: https://issues.jboss.org/browse/WFLY-3688 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 8.1.0.Final > Reporter: Tom Fonteyne > Assignee: Stefano Maestri > > The oracle JDBC driver had a method: > setConnectionProperties(java.util.Properties value) > which is needed to set several connection properties for datasources. > Most (all?) of these connection properties do not have individual setters. > WildFly does not support setting a "Properties" value for "datasource-property" -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3688) datasources subsystem: datasource and xa-datasource properties do not support the use of multiple values for one property

by Tom Fonteyne (JIRA)

[ https://issues.jboss.org/browse/WFLY-3688?page=com.atlassian.jira.plugin.... ] Tom Fonteyne updated WFLY-3688: ------------------------------- Summary: datasources subsystem: datasource and xa-datasource properties do not support the use of multiple values for one property (was: datasources subsystem: xa-datasource properties doe not support the use of multiple values for one property) > datasources subsystem: datasource and xa-datasource properties do not support the use of multiple values for one property > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-3688 > URL: https://issues.jboss.org/browse/WFLY-3688 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 8.1.0.Final > Reporter: Tom Fonteyne > Assignee: Stefano Maestri > > The oracle JDBC driver had a method: > setConnectionProperties(java.util.Properties value) > which is needed to set several connection properties for datasources. > Most (all?) of these connection properties do not have individual setters. > WildFly does not support setting a "Properties" value for "xa-datasource-property" -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3285) Domain directory properties only work on specific operating systems

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3285?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3285: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1091198|https://bugzilla.redhat.com/show_bug.cgi?id=1091198] from ON_QA to ASSIGNED > Domain directory properties only work on specific operating systems > ------------------------------------------------------------------- > > Key: WFLY-3285 > URL: https://issues.jboss.org/browse/WFLY-3285 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 8.1.0.CR1 > Reporter: Dennis Reed > Assignee: Tomaz Cerar > > domain.sh only parses -Djboss.domain.base.dir, -Djboss.domain.log.dir, and -Djboss.domain.config.dir (used to set -Dlogging.configuration and -Dorg.jboss.boot.log.file) on Linux, Solaris, and OS X. > It does not attempt to parse these (and therefore does not set the logging properties correctly) on any other OS, including AIX. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 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

2006

jboss-jira November 2014