March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1775) Relay2Test.testQueueingAndForwarding fails randomly

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1775?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1775. ---------------------------- Resolution: Won't Fix I'm afraid I won't fix this in 3.5 as that test doesn't exist anymore. > Relay2Test.testQueueingAndForwarding fails randomly > --------------------------------------------------- > > Key: JGRP-1775 > URL: https://issues.jboss.org/browse/JGRP-1775 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.3.5 > Reporter: Risto Oikarinen > Assignee: Bela Ban > Priority: Minor > Fix For: 3.5 > > Attachments: relay2test_fails_randomly_log.txt > > > Relay2Test.testQueueingAndForwarding seems to be failing randomly. I was able to reproduce this with the following test: > {code:java} > public void testQueueInLoop() throws Exception { > for ( int i = 0; i < 1000; ++i) { > testQueueingAndForwarding(); > destroy(); > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1750) RELAY2 : Address formats are not relayed.

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1750?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1750. ---------------------------- Resolution: Done [~ammous] Let me know if this works now, and reopen if it doesn't. > RELAY2 : Address formats are not relayed. > ----------------------------------------- > > Key: JGRP-1750 > URL: https://issues.jboss.org/browse/JGRP-1750 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 3.4.1 > Reporter: Karim AMMOUS > Assignee: Bela Ban > Fix For: 3.5 > > > When defining a relay channel, we haven't the ability to set an AddressGenrator. Indeed, the Relayer uses its own AddressGenerator providing addresses of type SiteUUID. > This is particularly embarrassing in the following case: when we define a customized address format (like CanBeSiteMasterTopology or TopologyUUID) for members of two Sites A and B, address format is lost by crossing relay. Address type of messages sent by A to B are seen as SiteUUID at B side. > Suggestions: > - Making address format "relayable" ? > - Using the same (or an extended format) AddressGenerator of site Channel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2713) ViewExpiredException in Chrome on WildFly 8.0.0.CR1

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-2713?page=com.atlassian.jira.plugin.... ] Farah Juma commented on WFLY-2713: ---------------------------------- [~ppitonak] Are you still able to reproduce this? I just tried with the latest WildFly 8.0.1.Final-SNAPSHOT version (i.e., rev 84638b1a4f4705875dfaaf72cd6decd9342394fc) and with Chrome 33.0.1750.152 but wasn't able to reproduce this issue. > ViewExpiredException in Chrome on WildFly 8.0.0.CR1 > --------------------------------------------------- > > Key: WFLY-2713 > URL: https://issues.jboss.org/browse/WFLY-2713 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JSF > Affects Versions: 8.0.0.CR1 > Environment: WildFly 8.0.0.CR1 > Chrome 31.0.1650.63 @ Fedora 20 x86_64 > Reporter: Pavol Pitonak > Assignee: Farah Juma > Attachments: reproducer.zip > > > # unzip attached reproducer > # mvn clean package > # deploy reproducer.war to WildFly > # open http://localhost:8080/reproducer/ > # type something to the input > result: > * in Chrome, a popup with error is displayed > * server console contains stack trace: > {code} > 17:10:54,852 SEVERE [javax.enterprise.resource.webcontainer.jsf.context] (default task-7) javax.faces.application.ViewExpiredException: viewId:/index.xhtml - View /index.xhtml could not be restored. > {code} > * works fine in Firefox 26 > * works fine in WildFly 8.0.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3150) component upgrade to Hibernate next ORM 4.3.x release

by Scott Marlow (JIRA)

Scott Marlow created WFLY-3150: ---------------------------------- Summary: component upgrade to Hibernate next ORM 4.3.x release Key: WFLY-3150 URL: https://issues.jboss.org/browse/WFLY-3150 Project: WildFly Issue Type: Task Security Level: Public (Everyone can see) Components: JPA / Hibernate Affects Versions: 8.0.0.Final Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 8.0.1.Final Need the https://hibernate.atlassian.net/browse/HHH-9073 change. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-810) Lifetime configuration option for Kerberos LoginModule

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-810?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-810: -------------------------------------- Component/s: Negotiation > Lifetime configuration option for Kerberos LoginModule > ------------------------------------------------------ > > Key: SECURITY-810 > URL: https://issues.jboss.org/browse/SECURITY-810 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Jesper Pedersen > Assignee: Darran Lofthouse > > Add a configuration option to the Kerberos LoginModule that allows to control the lifetime -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-810) Lifetime configuration option for Kerberos LoginModule

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-810?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-810: -------------------------------------- Fix Version/s: Negotiation_2_3_0_CR1 > Lifetime configuration option for Kerberos LoginModule > ------------------------------------------------------ > > Key: SECURITY-810 > URL: https://issues.jboss.org/browse/SECURITY-810 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Jesper Pedersen > Assignee: Darran Lofthouse > Fix For: Negotiation_2_3_0_CR1 > > > Add a configuration option to the Kerberos LoginModule that allows to control the lifetime -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3077) Convert command line IPv6 URL literals to address literals

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3077?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3077: ----------------------------------------------- Rostislav Svoboda <rsvoboda(a)redhat.com> changed the Status of [bug 1064771|https://bugzilla.redhat.com/show_bug.cgi?id=1064771] from ASSIGNED to VERIFIED > Convert command line IPv6 URL literals to address literals > ---------------------------------------------------------- > > Key: WFLY-3077 > URL: https://issues.jboss.org/browse/WFLY-3077 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 8.0.1.Final > > > When people provide URL-style values like [::1] for command line args like -b, convert them to address values (i.e. strip the enclosing brackets.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-810) Lifetime configuration option for Kerberos LoginModule

by Jesper Pedersen (JIRA)

Jesper Pedersen created SECURITY-810: ---------------------------------------- Summary: Lifetime configuration option for Kerberos LoginModule Key: SECURITY-810 URL: https://issues.jboss.org/browse/SECURITY-810 Project: PicketBox Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Jesper Pedersen Assignee: Darran Lofthouse Add a configuration option to the Kerberos LoginModule that allows to control the lifetime -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2214) Allow additional environment properties to be set for outbound LDAP connections used by security realms.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2214?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2214: ----------------------------------------------- Darran Lofthouse <darran.lofthouse(a)redhat.com> changed the Status of [bug 1015303|https://bugzilla.redhat.com/show_bug.cgi?id=1015303] from ASSIGNED to POST > Allow additional environment properties to be set for outbound LDAP connections used by security realms. > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-2214 > URL: https://issues.jboss.org/browse/WFLY-2214 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Alpha4 > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > LDAP security realm needs to have configurable timeouts. > The default LDAP connection timeout appears to be 2 minutes. If the ldap server is down, it could take 2 minutes for the connection to timeout. This can cause unneeded delay if you have configured multiple ldap servers for failover / redundancy. > The following hack appears to work: > +++ domain-management/src/main/java/org/jboss/as/domain/management/connections/ldap/LdapConnectionManagerService.java > @@ -132,6 +132,7 @@ public class LdapConnectionManagerService implements Service<LdapConnectionManag > result.put(Context.INITIAL_CONTEXT_FACTORY,initialContextFactory); > String url = config.require(URL).asString(); > result.put(Context.PROVIDER_URL,url); > + result.put("com.sun.jndi.ldap.connect.timeout", "500"); > return result; > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-315) Avoid running out of threads when connecting to the DC from a slave to pull down missing data

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-315?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on WFLY-315: ---------------------------------- Ideally, dependency-oriented tasks would be asynchronous/callback-based. I have a simple DependencyTask class in jboss-threads that might be interesting for certain trivial cases (probably not for this case though). The idea is to avoid submitting tasks that you know will block, instead favoring tasks that will proceed and that will resolve future tasks' blocks before they are executed. > Avoid running out of threads when connecting to the DC from a slave to pull down missing data > --------------------------------------------------------------------------------------------- > > Key: WFLY-315 > URL: https://issues.jboss.org/browse/WFLY-315 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Kabir Khan > Assignee: Emanuel Muckenhuber > Priority: Blocker > Fix For: 9.0.0.CR1 > > > For WFLY-259 when a slave connects to the DC to pull down missing data, it does this by either getting a lock for the DC, or by joining the permit of the existing DC lock if the request to update a slave's server-config was executed as part of a composite obtaining a lock on the DC. > The way it works at present there is a thread per slave which is blocked until the transaction completes. The DC threads are a finite resource, so a large number of slaves trying to pull down dats will cause deadlock -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 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 March 2014