October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-410) Implement custom Stack resource for JGroups to maintain protocol order

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-410?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-410: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Implement custom Stack resource for JGroups to maintain protocol order > ----------------------------------------------------------------------- > > Key: WFLY-410 > URL: https://issues.jboss.org/browse/WFLY-410 > Project: WildFly > Issue Type: Task > Components: Clustering, Domain Management > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Priority: Minor > Fix For: 8.0.0.CR1 > > > A JGroups stack is a transport together with an ordered list of protocols. The transport and the protocols are maintained as child resources. There is no direct way to maintain the order of a set of protocol child resources, so we need to implement a custom resource which does this. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-416) Complete <xs:documentation> for all configuration elements/attributes in Infinispan subsystem's XSD

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-416?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-416: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Complete <xs:documentation> for all configuration elements/attributes in Infinispan subsystem's XSD > --------------------------------------------------------------------------------------------------- > > Key: WFLY-416 > URL: https://issues.jboss.org/browse/WFLY-416 > Project: WildFly > Issue Type: Task > Components: Clustering > Reporter: Martin Gencur > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > Infinispan subsystem's XSD still contains a lot of elements/attributes which do NOT have their description: https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/... > It would be very useful for users to know what each element is supposed to do. > This document can help out: https://docspace.corp.redhat.com/docs/DOC-69249 -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-441) If possible, eliminate the NonTxEmCloser by closing the EM immediately after each EM invocation

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-441?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-441: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > If possible, eliminate the NonTxEmCloser by closing the EM immediately after each EM invocation > ----------------------------------------------------------------------------------------------- > > Key: WFLY-441 > URL: https://issues.jboss.org/browse/WFLY-441 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Priority: Minor > Fix For: 8.0.0.CR1 > > > For Queries, handoff the EntityManager to a Query object wrapper and have the Query object finalizer close the EntityManager. > Make sure that we respect JPA 2.0 section 3.8.6 (detach objects returned from Query object). > 1. Methods that return a Query, will hand off the EM to the Query object wrapper. > 2. Other methods will close the EM at the end of the EM method invocation. > When making this change, make sure that performance doesn't degrade. The cost of this change, will be that each (transaction scoped non-tx) EM invocation will create a new persistence context, but we can eliminate the NonTxEmCloser which has its own overhead. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-436) Inline JGroups subsystem references to threads subsystem.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-436?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-436: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Inline JGroups subsystem references to threads subsystem. > --------------------------------------------------------- > > Key: WFLY-436 > URL: https://issues.jboss.org/browse/WFLY-436 > Project: WildFly > Issue Type: Sub-task > Components: Clustering > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > Currently, the JGroups subsystem defers to the threads subsystem to define thread pools and thread factories. Apparently, this is now frowned upon. Instead, the executors for the default pool, OOB pool, and timer pool should be defined inline. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-434) Domain Management - Support for database connection pool in non AS process.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-434?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-434: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Domain Management - Support for database connection pool in non AS process. > --------------------------------------------------------------------------- > > Key: WFLY-434 > URL: https://issues.jboss.org/browse/WFLY-434 > Project: WildFly > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Brian Stansberry > Fix For: 8.0.0.CR1 > > > We need to support authentication for users stored in database, the domain management is in a non-AS process so we also need a pool of database connections. > These connections will be used to read only from the database, other than the isolation offered by the driver we should not require any advanced transaction support. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-435) Validate servlet run as identity propagation

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-435?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-435: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Validate servlet run as identity propagation > -------------------------------------------- > > Key: WFLY-435 > URL: https://issues.jboss.org/browse/WFLY-435 > Project: WildFly > Issue Type: Task > Components: EJB, Security, Web (JBoss Web) > Reporter: Marcus Moyses > Assignee: Peter Skopek > Priority: Minor > Fix For: 8.0.0.CR1 > > > Need to validate if the run as identity configured in jboss-web.xml for a servlet is propagated to ejb invocations. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-418) TS: Move resources to source packages.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-418?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-418: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > TS: Move resources to source packages. > -------------------------------------- > > Key: WFLY-418 > URL: https://issues.jboss.org/browse/WFLY-418 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > Priority: Minor > Fix For: 8.0.0.CR1 > > -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-458) ServerInventory#reconnectServer should take auto-start into account

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-458?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-458: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > ServerInventory#reconnectServer should take auto-start into account > ------------------------------------------------------------------- > > Key: WFLY-458 > URL: https://issues.jboss.org/browse/WFLY-458 > Project: WildFly > Issue Type: Task > Components: Domain Management > Reporter: Emanuel Muckenhuber > Fix For: 8.0.0.CR1 > > > When reconnecting to stopped (but not removed) servers, the ServerInventory should take the auto-start property into account. Otherwise the process will just get removed, however started with the next :reload of the HC. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-446) Add quickstarts info to localhost:8080

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-446?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-446: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Add quickstarts info to localhost:8080 > -------------------------------------- > > Key: WFLY-446 > URL: https://issues.jboss.org/browse/WFLY-446 > Project: WildFly > Issue Type: Task > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Minor > Fix For: 8.0.0.CR1 > > > Add another static page, quickstarts.html, that lists the quickstarts available and how to get them. Add a link from the main page. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-457) Replace mod_cluster proxy-list attribute with list of outbound socket bindings

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-457?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-457: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Replace mod_cluster proxy-list attribute with list of outbound socket bindings > ------------------------------------------------------------------------------ > > Key: WFLY-457 > URL: https://issues.jboss.org/browse/WFLY-457 > Project: WildFly > Issue Type: Task > Components: Clustering > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Fix For: 8.0.0.CR1 > > > Currently, the mod_cluster subsystem defines proxies using a comma separated string of address:port. This attribute needs to be deprecated in favor of an attribute, call it "proxies" that defines an xs:list of outbound socket binding names. -- 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

12 years, 9 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 October 2013