July 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1725) Update The Wildfly High Availability Guide

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-1725?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-1725: ------------------------------------ This looks great, though I think the undertow subsystem documentation belongs somewhere else. We only need to discuss relevant parts (e.g. mod_cluster connectors, clustered SSO, etc.) I think the next step is to create sub-tasks and start assigning owners. > Update The Wildfly High Availability Guide > ------------------------------------------- > > Key: WFLY-1725 > URL: https://issues.jboss.org/browse/WFLY-1725 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.0.0.Alpha3 > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Fix For: 8.0.0.Beta1 > > > The main source of clustering-related documentation for a Wildfly user is the High Availability Guide in the Wildfly 8 documentation on docs.jboss.org. > Update this document into a quality document which will aid the user's understanding of new features and configuration in Wildfly 8 clustering. -- 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] (DROOLS-193) KnowledgeBuilderResult does not always contain a Resource

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-193?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-193: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > KnowledgeBuilderResult does not always contain a Resource > --------------------------------------------------------- > > Key: DROOLS-193 > URL: https://issues.jboss.org/browse/DROOLS-193 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michael Anstis > Assignee: Mario Fusco > -- 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-1500) File attribute always replaces the file even if the values are equal

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1500?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1500: ----------------------------------------------- pkremens(a)redhat.com made a comment on [bug 973450|https://bugzilla.redhat.com/show_bug.cgi?id=973450] Verified on EAP 6.1.1 ER3, bootstrap logged are now not overwritten. > File attribute always replaces the file even if the values are equal > -------------------------------------------------------------------- > > Key: WFLY-1500 > URL: https://issues.jboss.org/browse/WFLY-1500 > Project: WildFly > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.0.Alpha2 > > > The value for the {{FILE}} attribute for file log handlers isn't properly checked when comparing bootstrap file value. With a file that is not appendable, the overwrite would overwrite bootstrapped logged data. -- 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-1500) File attribute always replaces the file even if the values are equal

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1500?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1500: ----------------------------------------------- pkremens(a)redhat.com changed the Status of [bug 973450|https://bugzilla.redhat.com/show_bug.cgi?id=973450] from ON_QA to VERIFIED > File attribute always replaces the file even if the values are equal > -------------------------------------------------------------------- > > Key: WFLY-1500 > URL: https://issues.jboss.org/browse/WFLY-1500 > Project: WildFly > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.0.Alpha2 > > > The value for the {{FILE}} attribute for file log handlers isn't properly checked when comparing bootstrap file value. With a file that is not appendable, the overwrite would overwrite bootstrapped logged data. -- 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-1668) Cache passwords from external source for LdapExtLoginModule doesn't work with {EXTC}

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1668?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1668: ----------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 982539|https://bugzilla.redhat.com/show_bug.cgi?id=982539] from POST to MODIFIED > Cache passwords from external source for LdapExtLoginModule doesn't work with {EXTC} > ------------------------------------------------------------------------------------ > > Key: WFLY-1668 > URL: https://issues.jboss.org/browse/WFLY-1668 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 8.0.0.Alpha2 > Reporter: Josef Cacek > Assignee: Peter Skopek > > Mechanism to obtain passwords from external sources for login modules works only with option {EXT} - non-cached. New feature to cache passwords with command option {EXTC[:timeout]} doesn't work. > Problem is propably in LdapExtLoginModule method createLdapInitContext, that doesn't deal with commands that starts with "{EXTC" -- 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-1731) Bad management of bind owner at the WritableServiceBasedNamingStore

by Eduardo Martins (JIRA)

Eduardo Martins created WFLY-1731: ------------------------------------- Summary: Bad management of bind owner at the WritableServiceBasedNamingStore Key: WFLY-1731 URL: https://issues.jboss.org/browse/WFLY-1731 Project: WildFly Issue Type: Feature Request Components: Naming Reporter: Eduardo Martins Assignee: Eduardo Martins Fix For: 8.0.0.Beta1 Each EE deployment maintains a set of service names wrt bindings it "owns", which should be removed when the deployment stops, and the management of these is not proper on unbind and rebind done at the naming store. -- 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-1730) Wrong TCCL during ValidatorFactory retrieval

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFLY-1730?page=com.atlassian.jira.plugin.... ] Eduardo Martins commented on WFLY-1730: --------------------------------------- this issue is valid, the ValidatorFactory may not provide the correct TCCL, so Context#list() or the management op jndi-view will fail > Wrong TCCL during ValidatorFactory retrieval > -------------------------------------------- > > Key: WFLY-1730 > URL: https://issues.jboss.org/browse/WFLY-1730 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.0.0.Alpha3 > Reporter: Jozef Hartinger > Assignee: Eduardo Martins > Fix For: 8.0.0.Beta1 > > > Here https://github.com/wildfly/wildfly/blob/master/ee/src/main/java/org/jboss... > the TCCL is set to the classloader of the ValidatorFactory. If the ValidatorFactory is LazyValidatorFactory which delegates to a client proxy obtained from Weld, this call fails with > {noformat} > Caused by: java.lang.IllegalStateException: JBAS016071: Singleton not set for ModuleClassLoader for Module "org.jboss.as.ee:main" from local module loader @76724357 (finder: local module finder @47a34181 (r$ > at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:75) [wildfly-weld-8.0.0.Alpha4-SNAPSHOT.jar:8.0.0.Alpha4-SNAPSHOT] > at org.jboss.weld.Container.instance(Container.java:54) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15] > at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:70) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15] > at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15] > at org.jboss.weld.proxies.ValidatorFactory$618047133$Proxy$_$$_WeldClientProxy.getValidator(Unknown Source) [weld-core-impl-2.0.2.Final.jar:] > at org.jboss.as.ee.beanvalidation.LazyValidatorFactory.getValidator(LazyValidatorFactory.java:83) > at org.jboss.as.ee.beanvalidation.ValidatorJndiInjectable.getInstanceSafely(ValidatorJndiInjectable.java:53) > at org.jboss.as.ee.beanvalidation.ValidatorJndiInjectable.getInstanceClassName(ValidatorJndiInjectable.java:61) > at org.jboss.as.naming.ServiceBasedNamingStore.list(ServiceBasedNamingStore.java:176) > at org.jboss.as.naming.NamingContext.list(NamingContext.java:323) > at org.jboss.as.naming.InitialContext.list(InitialContext.java:140) > at org.jboss.as.naming.NamingContext.list(NamingContext.java:339) > at javax.naming.InitialContext.list(InitialContext.java:455) [rt.jar:1.7.0_25] > at org.jboss.as.test.integration.web.injection.SimpleServlet.testAS7_5347(SimpleServlet.java:59) [classes:] > ... 29 more > {noformat} > My assumption is that setting the TCCL is not necessary here at all though I may be wrong. -- 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-1337) Support JMS 2.0 definition annotations

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-1337?page=com.atlassian.jira.plugin.... ] Jeff Mesnil reassigned WFLY-1337: --------------------------------- Assignee: Jeff Mesnil (was: Eduardo Martins) > Support JMS 2.0 definition annotations > -------------------------------------- > > Key: WFLY-1337 > URL: https://issues.jboss.org/browse/WFLY-1337 > Project: WildFly > Issue Type: Feature Request > Components: EE > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Beta1 > > > As described in EE7 spec (5.18.4 & 5.18.5), JMS managed resources can be defined using new annotations (and XML deployment element): > * @JMSConnectionFactoryDefinition > * @JMSDefinition -- 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-1730) Wrong TCCL during ValidatorFactory retrieval

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFLY-1730?page=com.atlassian.jira.plugin.... ] Eduardo Martins updated WFLY-1730: ---------------------------------- Assignee: Eduardo Martins > Wrong TCCL during ValidatorFactory retrieval > -------------------------------------------- > > Key: WFLY-1730 > URL: https://issues.jboss.org/browse/WFLY-1730 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.0.0.Alpha3 > Reporter: Jozef Hartinger > Assignee: Eduardo Martins > Fix For: 8.0.0.Beta1 > > > Here https://github.com/wildfly/wildfly/blob/master/ee/src/main/java/org/jboss... > the TCCL is set to the classloader of the ValidatorFactory. If the ValidatorFactory is LazyValidatorFactory which delegates to a client proxy obtained from Weld, this call fails with > {noformat} > Caused by: java.lang.IllegalStateException: JBAS016071: Singleton not set for ModuleClassLoader for Module "org.jboss.as.ee:main" from local module loader @76724357 (finder: local module finder @47a34181 (r$ > at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:75) [wildfly-weld-8.0.0.Alpha4-SNAPSHOT.jar:8.0.0.Alpha4-SNAPSHOT] > at org.jboss.weld.Container.instance(Container.java:54) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15] > at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:70) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15] > at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15] > at org.jboss.weld.proxies.ValidatorFactory$618047133$Proxy$_$$_WeldClientProxy.getValidator(Unknown Source) [weld-core-impl-2.0.2.Final.jar:] > at org.jboss.as.ee.beanvalidation.LazyValidatorFactory.getValidator(LazyValidatorFactory.java:83) > at org.jboss.as.ee.beanvalidation.ValidatorJndiInjectable.getInstanceSafely(ValidatorJndiInjectable.java:53) > at org.jboss.as.ee.beanvalidation.ValidatorJndiInjectable.getInstanceClassName(ValidatorJndiInjectable.java:61) > at org.jboss.as.naming.ServiceBasedNamingStore.list(ServiceBasedNamingStore.java:176) > at org.jboss.as.naming.NamingContext.list(NamingContext.java:323) > at org.jboss.as.naming.InitialContext.list(InitialContext.java:140) > at org.jboss.as.naming.NamingContext.list(NamingContext.java:339) > at javax.naming.InitialContext.list(InitialContext.java:455) [rt.jar:1.7.0_25] > at org.jboss.as.test.integration.web.injection.SimpleServlet.testAS7_5347(SimpleServlet.java:59) [classes:] > ... 29 more > {noformat} > My assumption is that setting the TCCL is not necessary here at all though I may be wrong. -- 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-476) Add support for implicit bean archives

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/WFLY-476?page=com.atlassian.jira.plugin.s... ] Jozef Hartinger commented on WFLY-476: -------------------------------------- This issue depends on https://github.com/wildfly/wildfly/pull/4817 also > Add support for implicit bean archives > -------------------------------------- > > Key: WFLY-476 > URL: https://issues.jboss.org/browse/WFLY-476 > Project: WildFly > Issue Type: Task > Components: CDI / Weld > Reporter: Jozef Hartinger > Assignee: Jozef Hartinger > Fix For: 8.0.0.Beta1 > > > There is a prototype at https://github.com/weld/as7-weld-subsystem/tree/global-enablement-prototype -- 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 July 2013