October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-264) Add support for use1PcForAutoCommitTransactions

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-264?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-264: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Add support for use1PcForAutoCommitTransactions > ----------------------------------------------- > > Key: WFLY-264 > URL: https://issues.jboss.org/browse/WFLY-264 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Priority: Minor > Fix For: 8.0.0.CR1 > > > Since clustered web sessions/SFSBs won't ever incur inter-node concurrent access, we can tolerate a 1PC commit optimization - which will reduce the number of RPCs involved in replication/distribution. This should result it a significant performance gains for REPL_SYNC and DIST_SYNC 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-261) Add way to properly parse JNDI urls in AS codebase

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-261?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-261: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Add way to properly parse JNDI urls in AS codebase > -------------------------------------------------- > > Key: WFLY-261 > URL: https://issues.jboss.org/browse/WFLY-261 > Project: WildFly > Issue Type: Feature Request > Components: Naming > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 8.0.0.CR1 > > > This is a followup of AS7-2138. Original code, in case no URL context threw NamingException. The AS7-2138 introduced a fallback to NamingContext in case AS7 does not provide custom hack for url( like EJB ). However the fallback did not fail with NamingException in case it did not locate Context. This essentially made it go knee deep into AS7 service lookups, which hides real cause of failure. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-262) Update the DC's IgnoredTransformationRegistry when changes are made to a slave's <ignored-resources>

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-262?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-262: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Update the DC's IgnoredTransformationRegistry when changes are made to a slave's <ignored-resources> > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-262 > URL: https://issues.jboss.org/browse/WFLY-262 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-259) Auto ignore domain resources on a slave HC which do not affect its servers

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-259?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-259: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Auto ignore domain resources on a slave HC which do not affect its servers > -------------------------------------------------------------------------- > > Key: WFLY-259 > URL: https://issues.jboss.org/browse/WFLY-259 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.CR1 > > > Currently to avoid receiving resources and ops for parts of the domain model which do not work on an older slave we use <ignored-resources> in the slave host.xml to ignore them. > Instead we should only pull in parts of the domain model that is actually required on the slave for its servers to start. Once started we need to be able to update the slave with domain information as the config changes > The main things which can change affecting the data required are: > 1) A domain's server-group, where the profile (and thus extensions) and the socket-binding group can be changed. > 2) A host's server-config, where the server-group and the socket-binding-group override might be changed. > For 1) we can piggy-back missing data to the slave. > For 2) the slave needs to connect back to the DC, attempt to get the DC lock and pull down the required data. If the lock cannot be obtained, the operation should fail fast. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-263) JASPI Support for Web Services

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-263?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-263: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > JASPI Support for Web Services > ------------------------------ > > Key: WFLY-263 > URL: https://issues.jboss.org/browse/WFLY-263 > Project: WildFly > Issue Type: Feature Request > Components: Security, Web Services > Reporter: Anil Saldhana > Assignee: Jim Ma > Fix For: 8.0.0.CR1 > > > Take care of the JASPI requirements for SOAP layer. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-258) mod_cluster schema 1.2

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-258?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-258: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > mod_cluster schema 1.2 > ---------------------- > > Key: WFLY-258 > URL: https://issues.jboss.org/browse/WFLY-258 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.CR1 > > > Changes to the schema > * simplified names and sync in line with scheme recommendations > * remove redundant <mod-cluster-config .. /> for good, everything should be element of the subsystem > * fix load factor enum: no pool metric supported > * make load-balancers configurable via socket-outbuound-group mechanism > * add missing load-balancer properties to <proxies/> -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-260) Error

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-260?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-260: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Error > ----- > > Key: WFLY-260 > URL: https://issues.jboss.org/browse/WFLY-260 > Project: WildFly > Issue Type: Feature Request > Components: Class Loading > Reporter: Pablo Ochoa > Assignee: David Lloyd > Fix For: 8.0.0.CR1 > > > Buenos Días, > Tengo problema con la version 7.1.1 de Jboss por defecto viene creado un Selector y yo intento crea uno nuevo para el manejo de mi classes me arroja el siguiente error > Preferred repository selector not installed because one has already exists. No problem, using existing selector... > Estado investigando de verdad no conseguido algo para poder solventar este problema el la ultima version de Jboss 6 no ocurre este mismo problema agradezco toda la colaboración que me puedan brindar > Te anexo el codigo que utilizo > import java.util.*; > import javax.naming.*; > import org.apache.log4j.Hierarchy; > import org.apache.log4j.Level; > import org.apache.log4j.spi.*; > public class Log4jContextJNDISelector > implements RepositorySelector > { > public Log4jContextJNDISelector(){ > defaultHierarchy = new Hierarchy(new RootLogger(Level.DEBUG)); > } > public LoggerRepository getLoggerRepository() > { > String loggingContextName = null; > try > { > Context ctx = new InitialContext(); > loggingContextName = (String)ctx.lookup("java:comp/env/log4j/logging-context"); > } > catch(NamingException ne) { } > if(loggingContextName == null) > return defaultHierarchy; > Hierarchy hierarchy = (Hierarchy)hierMap.get(loggingContextName); > if(hierarchy == null) > { > hierarchy = new Hierarchy(new RootLogger(Level.DEBUG)); > hierMap.put(loggingContextName, hierarchy); > } > return hierarchy; > } > Archivo web.xml esta configuración > <context-param> > <param-name>log4j-selector</param-name> > <param-value>ve.com.prueba.gdis.cia.config.logging.Log4jContextJNDISelector</param-value> > <description> Selector de repositorios basado en JNDI desde donde se > configurar el repositorio de logs para esta aplicación > </description> > </context-param> -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-283) EJB timers in cluster and failover support

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-283?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-283: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > EJB timers in cluster and failover support > ------------------------------------------ > > Key: WFLY-283 > URL: https://issues.jboss.org/browse/WFLY-283 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, EJB > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > Support for clustered EJB timer service providing failover. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-277) TS: Integrate JUnitDiff

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-277?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-277: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > TS: Integrate JUnitDiff > ----------------------- > > Key: WFLY-277 > URL: https://issues.jboss.org/browse/WFLY-277 > Project: WildFly > Issue Type: Feature Request > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > Priority: Minor > Fix For: 8.0.0.CR1 > > Original Estimate: 3 weeks > Remaining Estimate: 3 weeks > > Running with > {code} > -DjunitDiff='<path1>:<path2>:<path3>' > {code} > would create a comparison to given testsuite result sets (JUnit .xml and txt files). -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-279) Add deployment-scanner for singleton deployments

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-279?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-279: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Add deployment-scanner for singleton deployments > ------------------------------------------------ > > Key: WFLY-279 > URL: https://issues.jboss.org/browse/WFLY-279 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > To simplify the use of singleton deployments in standalone mode, it would be nice to have a mechanism analogous to the hasingleton-deploy directory in AS6 and earlier. To do this, we can enhance the existing deployment-scanner to accept an additional policy attribute. Something like: > <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1"> > <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" policy="standard"/> > <deployment-scanner path="singleton-deployments" relative-to="jboss.server.base.dir" scan-interval="5000" policy="singleton"/> > </subsystem> -- 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

11 years, 3 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 October 2013