November 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4133) Hanging EJB threads because of a persistent timer and failed deployment

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4133?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4133: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1147948 > Hanging EJB threads because of a persistent timer and failed deployment > ------------------------------------------------------------------------ > > Key: WFLY-4133 > URL: https://issues.jboss.org/browse/WFLY-4133 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.0.Alpha1 > Reporter: Enrique González Martínez > Assignee: Enrique González Martínez > > When there is a time service with pending timeouts a bad redeploy can hang worker threads in the server. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4133) Hanging EJB threads because of a persistent timer and failed deployment

by Enrique González Martínez (JIRA)

Enrique González Martínez created WFLY-4133: ----------------------------------------------- Summary: Hanging EJB threads because of a persistent timer and failed deployment Key: WFLY-4133 URL: https://issues.jboss.org/browse/WFLY-4133 Project: WildFly Issue Type: Bug Affects Versions: 9.0.0.Alpha1 Reporter: Enrique González Martínez Assignee: Enrique González Martínez When there is a time service with pending timeouts a bad redeploy can hang worker threads in the server. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4129) The RemotingLoginModule should first check if there is already a RealmUser

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4129?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4129: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1168585|https://bugzilla.redhat.com/show_bug.cgi?id=1168585] from POST to MODIFIED > The RemotingLoginModule should first check if there is already a RealmUser > -------------------------------------------------------------------------- > > Key: WFLY-4129 > URL: https://issues.jboss.org/browse/WFLY-4129 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 9.0.0.Alpha1 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.Beta1 > > > The reason is because the realm may have actually already substituted in a different name for the user. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-656) The blessed repo's should not accept a git force push

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-656?page=com.atlassian.jira.plugin... ] Geoffrey De Smet commented on DROOLS-656: ----------------------------------------- Might not be possible on GitHub yet: http://stackoverflow.com/questions/13016119/how-to-set-the-receive-denyno... > The blessed repo's should not accept a git force push > ----------------------------------------------------- > > Key: DROOLS-656 > URL: https://issues.jboss.org/browse/DROOLS-656 > Project: Drools > Issue Type: Task > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > Priority: Critical > > If someone ever git forces pushes to a blessed repo all hell will break loose. > We can prevent git forces pushes, as explained here: > http://stackoverflow.com/questions/1754491/is-there-a-way-to-configure-gi... > Force pushing on blessed repo's is very bad, but force pushing on forks is very common. > Requirements: > - Enable this on 1 new dummy blessed repository > - Prove you cannot force push to > - Prove you can fork it and force push to your fork. > - Delete the dummy blessed repository > - If that works well, enable it on the real blessed repositories -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-260) Incorrect LoginModule name used for Kerberos with IBM JDK and incorrect case for useKeytab

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-260?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-260: ------------------------------------------------ Darran Lofthouse <darran.lofthouse(a)redhat.com> changed the Status of [bug 1161589|https://bugzilla.redhat.com/show_bug.cgi?id=1161589] from ASSIGNED to POST > Incorrect LoginModule name used for Kerberos with IBM JDK and incorrect case for useKeytab > ------------------------------------------------------------------------------------------ > > Key: WFCORE-260 > URL: https://issues.jboss.org/browse/WFCORE-260 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha14 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 2 months

1
0
0 / 0

[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)

11 years, 2 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)

11 years, 2 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)

11 years, 2 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)

11 years, 2 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)

11 years, 2 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 November 2014