March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3120) Upgrade JSF based on Mojarra 2.2.6 Final

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-3120?page=com.atlassian.jira.plugin.... ] Farah Juma updated WFLY-3120: ----------------------------- Description: Upgrade JSF based on Mojarra 2.2.6 Final. Also incorporate the patch for WFLY-2594/[JAVASERVERFACES-3189|https://java.net/jira/browse/JAVASERVERFA... for WildFly 8.0.1.Final. (was: Incorporate the patch for WFLY-2594/[JAVASERVERFACES-3189|https://java.net/jira/browse/JAVASERVERFA... for WildFly 8.0.1.Final.) > Upgrade JSF based on Mojarra 2.2.6 Final > ---------------------------------------- > > Key: WFLY-3120 > URL: https://issues.jboss.org/browse/WFLY-3120 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JSF > Affects Versions: 8.0.0.Final > Reporter: Farah Juma > Assignee: Farah Juma > > Upgrade JSF based on Mojarra 2.2.6 Final. Also incorporate the patch for WFLY-2594/[JAVASERVERFACES-3189|https://java.net/jira/browse/JAVASERVERFA... for WildFly 8.0.1.Final. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3120) Upgrade jsf-impl to 2.2.5-jbossorg-4

by Farah Juma (JIRA)

Farah Juma created WFLY-3120: -------------------------------- Summary: Upgrade jsf-impl to 2.2.5-jbossorg-4 Key: WFLY-3120 URL: https://issues.jboss.org/browse/WFLY-3120 Project: WildFly Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: JSF Affects Versions: 8.0.0.Final Reporter: Farah Juma Assignee: Farah Juma Incorporate the patch for WFLY-2594/[JAVASERVERFACES-3189|https://java.net/jira/browse/JAVASERVERFA... for WildFly 8.0.1.Final. -- 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, 10 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 commented on JGRP-1750: -------------------------------- Perhaps it would be simpler to create a new interface {{ExtendedAddress}} and an impl {{ExtendedUUID}} which contains the UUID and additional data, e.g. {{site_id}}, {{rack_id}} and {{machine_id}} for {{TopologyUUID}}, or a string for {{PayloadUUID}} etc... The {{AddressGenerator}} would wrap the base address in an {{ExtendedUUID}} and data could then be added to that address, e.g. via puts and gets (conceptual hashmap). This would also allow us to get rid of a number of classes... > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1759) BecomeServerTest.testSendingOfMsgsOnUnconnectedChannel deadlocks

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1759?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1759: -------------------------------- I haven't been able to reproduce such a hang, *not a single time* ! Is this specific to 3.2.x ? > BecomeServerTest.testSendingOfMsgsOnUnconnectedChannel deadlocks > ---------------------------------------------------------------- > > Key: JGRP-1759 > URL: https://issues.jboss.org/browse/JGRP-1759 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.5 > Environment: Windows 2008, x86_64 > Reporter: Richard Achmatowicz > Assignee: Bela Ban > Priority: Minor > Fix For: 3.5 > > > Running the Byteman tests in the QA lab, this test deadlocks in a repeatable fashion and causes the testsuite to hang. > The test makes use of the Byteman rendezvous built-in function to suspend (and reorder) thread execution. It appears that with threads re-ordered, certain parts of JGroups block in such a way that no progress is made and the test deadlocks. > . -- 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, 10 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 commented on JGRP-1750: -------------------------------- Would you want to set an {{AddressGenerator}} both for (1) nodes in the local cluster and the bridge cluster, or (2) only for nodes of the bridge cluster ? The latter case is simple: we could allow to set an {{AddressGenerator}} in Relayer, and use it to generate an address which would then we wrapped with a SiteUUID. The former case is more generic: in essence, this would allow for multiple {{AddressGenerator}}s to build an address. So is your use case (1) or (2) ? > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3042) There should be a warning logged if the default value of node identifier has not been changed.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3042?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3042: ----------------------------------------------- Ondrej Chaloupka <ochaloup(a)redhat.com> changed the Status of [bug 1072312|https://bugzilla.redhat.com/show_bug.cgi?id=1072312] from ON_QA to VERIFIED > There should be a warning logged if the default value of node identifier has not been changed. > ------------------------------------------------------------------------------------------------ > > Key: WFLY-3042 > URL: https://issues.jboss.org/browse/WFLY-3042 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transactions > Affects Versions: 8.0.0.Final > Environment: JBoss EAP 6.x > Reporter: Tom Ross > Assignee: Gytis Trikleris > > JBoss EAP instance is using the value of node identifier to identify XA transactions that belong to it. By default this value is set to 1. Now days in most environments there will be multiple JBoss instances sharing XA resources there for it is necessary to set the value of node identifier to a unique value for each instance. This is something that most end users fail to perform. Therefor it would be helpful if a warning message was logged at startup telling the user to do it. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2648) Review/move the per-logging deployment tests

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2648?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-2648: ------------------------------------- Excellent, thanks Petr! Just ping me if you have any questions. I have some vague memories of the issues :) > Review/move the per-logging deployment tests > -------------------------------------------- > > Key: WFLY-2648 > URL: https://issues.jboss.org/browse/WFLY-2648 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Test Suite > Reporter: James Perkins > Assignee: Petr Kremensky > Priority: Minor > > The {{org.jboss.as.logging.per-deployment}} property has been deprecated. There are two tests {{LoggingPerDeployFalseTestCase}} and {{LoggingPreferencesPerDeployFalseTestCase}} that use this property. They need to be copied and/or moved to the manualmode tests and modified to use the new attribute. > Also these tests appear not to work correctly. Breaking the system property during the patch, the tests still seemed to pass. They need to be reviewed and tested when working on this issue. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2415) Add configuration option to enable/disable Infinispan statistics

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2415?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2415: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1025023|https://bugzilla.redhat.com/show_bug.cgi?id=1025023] from POST to MODIFIED > Add configuration option to enable/disable Infinispan statistics > ---------------------------------------------------------------- > > Key: WFLY-2415 > URL: https://issues.jboss.org/browse/WFLY-2415 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Scott Marlow > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > When the Infinispan MBean is enabled, Infinispan statistics are enabled by default. Could we allow Infinispan statistics to be enabled/disabled via a WF configuration setting? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3106) Infinispan cache statistics cannot be enabled/disabled independently of the cache manager statistics

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3106?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3106: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1025023|https://bugzilla.redhat.com/show_bug.cgi?id=1025023] from POST to MODIFIED > Infinispan cache statistics cannot be enabled/disabled independently of the cache manager statistics > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-3106 > URL: https://issues.jboss.org/browse/WFLY-3106 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Final > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Fix For: 8.0.1.Final > > > The Infinispan subsystem allows enabling and disabling the collection of statistics for cache managers and caches via the "statistics-enabled" management API attribute. > It is possible to set statistics-enabled attributes independently for cache managers and caches in the management API, but when checking the Infinispan MBeans, we see that statistics are either enabled for cache managers and their caches, or disabled for cache managers and caches. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-805) Overload SecurityVaultFactory.get() to be able to specify the classloader

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/SECURITY-805?page=com.atlassian.jira.plug... ] Kabir Khan updated SECURITY-805: -------------------------------- Attachment: SECURITY-805-2.diff > Overload SecurityVaultFactory.get() to be able to specify the classloader > ------------------------------------------------------------------------- > > Key: SECURITY-805 > URL: https://issues.jboss.org/browse/SECURITY-805 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Kabir Khan > Assignee: Kabir Khan > Attachments: SECURITY-805-2.diff, SECURITY-805.diff > > > To work better with modular class loading in WF -- 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, 10 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