March 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2480) Investigate Infinispan test XML files do not validate against XSD yet are parsed ok

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2480?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2480: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Investigate Infinispan test XML files do not validate against XSD yet are parsed ok > ----------------------------------------------------------------------------------- > > Key: WFLY-2480 > URL: https://issues.jboss.org/browse/WFLY-2480 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.0.0.CR1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 9.0.0.CR1 > > > So one or the other should to change. > cvc-complex-type.2.4.a: Invalid content was found starting with element 'store'. One of '{"urn:jboss:domain:infinispan:2.0":backups, "urn:jboss:domain:infinispan:2.0":backup-for}' is expected. > cvc-complex-type.2.4.a: Invalid content was found starting with element 'mixed-keyed-jdbc-store'. One of '{"urn:jboss:domain:infinispan:2.0":backups, "urn:jboss:domain:infinispan:2.0":backup-for}' is expected. > cvc-complex-type.2.4.d: Invalid content was found starting with element 'binary-keyed-table'. No child element is expected at this point. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2456) Using add-user.bat for initial admin user results in "JBAS015234: No mgmt-groups.properties files found"

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2456?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2456: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Using add-user.bat for initial admin user results in "JBAS015234: No mgmt-groups.properties files found" > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-2456 > URL: https://issues.jboss.org/browse/WFLY-2456 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 8.0.0.Beta1 > Environment: Windows 7, 32-bit, jdk1.7.0_45 > Reporter: John Lusk > Assignee: Darran Lofthouse > Fix For: 9.0.0.CR1 > > > Just getting started w/Wildfly after a long absence from Java. Fresh download, trying to hit admin console, got instructed to use add-user to add an admin user. > c:\usr\local\wildfly-8.0.0.Beta1\bin>.\add-user.bat > What type of user do you wish to add? > a) Management User (mgmt-users.properties) > b) Application User (application-users.properties) > (a): a > * Error * > JBAS015234: No mgmt-groups.properties files found. > Press any key to continue . . . > c:\usr\local\wildfly-8.0.0.Beta1\bin>echo %JBOSS_HOME% > C:\usr\local\wildfly-8.0.0.Beta1 > c:\usr\local\wildfly-8.0.0.Beta1\bin>echo %JAVA_HOME% > C:\java\jdk1.7.0_45 > c:\usr\local\wildfly-8.0.0.Beta1\bin>echo %M2_HOME% > C:\usr\local\Maven\3.1.1 > c:\usr\local\wildfly-8.0.0.Beta1\bin>mvn -version > Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 11:22:2 > 2-0400) > Maven home: C:\usr\local\Maven\3.1.1 > Java version: 1.7.0_45, vendor: Oracle Corporation > Java home: C:\java\jdk1.7.0_45\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "x86", family: "windows" > c:\usr\local\wildfly-8.0.0.Beta1\bin> -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2504) add lazy xpc inheritance to handle legacy case, remote client with UserTransaction fails on 2nd SFSB invocation when using extended persistence context

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2504?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2504: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > add lazy xpc inheritance to handle legacy case, remote client with UserTransaction fails on 2nd SFSB invocation when using extended persistence context > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2504 > URL: https://issues.jboss.org/browse/WFLY-2504 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 9.0.0.CR1 > > > AS5 allowed a remote client to instantiate a set of stateful session beans (e.g. SFSB1 + SFSB2) and then call the remote stateful session beans (SFSB1+SFSB2) in a started user transaction (UT1). Each of the stateful beans reference the same extended persistence context by name. In AS5, both stateful beans will share the same extended persistence unit context but on AS7/WF8, each bean has its own extended persistence unit context. Having both XPCS involved in the same user transaction, causes an (EJBException: JBAS011437: Found extended persistence context in SFSB invocation call stack but that cannot be used because the transaction already has a transactional context associated with it...) error to be thrown. > On AS7/WF8, Allow the separate (remote) stateful beans to share the same persistence context. > One approach might be to defer creation of the extended persistence context until the first invocation (need to verify that this is the right approach). > Currently, we support shallow + deep extended persistence context inheritance. This will be a "lazy" variation of the deep XPC inheritance. > Some of the AS5 code is pasted below for easy reference. > {code} > public class ExtendedPersistenceContextPropagationInterceptor implements Interceptor > { > private static final Logger log = Logger.getLogger(ExtendedPersistenceContextPropagationInterceptor.class); > public String getName() > { > return this.getClass().getName(); > } > public Object invoke(Invocation invocation) throws Throwable > { > log.debug("++++ LongLivedSessionPropagationInterceptor"); > StatefulContainerInvocation ejb = (StatefulContainerInvocation) invocation; > StatefulBeanContext ctx = (StatefulBeanContext) ejb.getBeanContext(); > Map<String, EntityManager> extendedPCs = ctx.getExtendedPersistenceContexts(); > if (extendedPCs == null || extendedPCs.size() == 0) > { > return invocation.invokeNext(); > } > TransactionManager tm = TxUtil.getTransactionManager(); > if (tm.getTransaction() != null) > { > for (String kernelname : extendedPCs.keySet()) > { > EntityManager manager = extendedPCs.get(kernelname); > ManagedEntityManagerFactory factory = ManagedEntityManagerFactoryHelper.getManagedEntityManagerFactory(kernelname); > factory.registerExtendedWithTransaction(manager); > } > } > return invocation.invokeNext(); > } > } > {code} > {code} > public class EJB3XPCResolver implements XPCResolver > { > private static final Logger log = Logger.getLogger(EJB3XPCResolver.class); > /** > * Query the current stateful bean contexts for the specified XPC. > */ > public EntityManager getExtendedPersistenceContext(String kernelName) > { > StatefulBeanContext beanContext = StatefulBeanContext.currentBean.get(); > if (beanContext != null) > { > EntityManager em = null; > em = beanContext.getExtendedPersistenceContext(kernelName); > if (em != null) { > log.info("current SFSB has XPC with scoped pu name=" + kernelName + " on SFSB bean=" + beanContext.getContainer().getIdentifier() + beanContext.getId()); > return em; > } > /** > * Look for XPC in current bean set. > */ > log.info("looking for existing XPC with scoped pu name=" + kernelName); > List <StatefulBeanContext> beanContexts = StatefulBeanContext.currentBean.getList(); > for( StatefulBeanContext bc : beanContexts) > { > em = bc.getExtendedPersistenceContext(kernelName); > if (em != null) { > log.info("found existing XPC with scoped pu name=" + kernelName + " on SFSB bean=" + bc.getContainer().getIdentifier() + bc.getId()); > // Propagate created XPC as required (7.6.2.1 Inheritance of Extended Persistence Context > beanContext.addExtendedPersistenceContext(kernelName, em); > return em; > } > log.info("XPC not found yet, scoped pu name=" + kernelName + " not in SFSB bean=" + bc.getContainer().getIdentifier() + bc.getId()); > } > } > log.info("XPC not found scoped, search done, pu name=" + kernelName); > return null; > } > @Override > public EntityManager createExtendedPersistenceContext(String kernelName) > { > StatefulBeanContext beanContext = StatefulBeanContext.currentBean.get(); > if (beanContext != null) > { > EntityManager em = null; > ManagedEntityManagerFactory factory= > ((PersistenceUnitDeployment) PersistenceUnitRegistry.getPersistenceUnit(kernelName)).getManagedFactory(); > if (factory != null) > { > em = factory.createEntityManager(); > if (em != null) > { > beanContext.addExtendedPersistenceContext(factory.getKernelName(), em); > log.info("created new XPC with scoped pu name=" + kernelName + " on SFSB bean=" + beanContext.getContainer().getIdentifier() + beanContext.getId()); > /** > * TODO: Propagate created XPC as required (7.6.2.1 Inheritance of Extended Persistence Context > * > */ > // List <StatefulBeanContext> beanContexts = StatefulBeanContext.currentBean.getList(); > // for( StatefulBeanContext bc : beanContexts) > // { > // bc.addExtendedPersistenceContext(kernelName, em); > // } > } > } > return em; > } > return null; > } > } > {code} > {code} > public class ManagedEntityManagerFactoryHelper > { > public static ManagedEntityManagerFactory getManagedEntityManagerFactory(String kernelName) > { > PersistenceUnitDeployment pu = (PersistenceUnitDeployment) PersistenceUnitRegistry.getPersistenceUnit(kernelName); > if(pu != null) > return pu.getManagedFactory(); > return null; > } > } > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2552) Undertow AuthenticationMechanism Configuration Overrides

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2552?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2552: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Undertow AuthenticationMechanism Configuration Overrides > -------------------------------------------------------- > > Key: WFLY-2552 > URL: https://issues.jboss.org/browse/WFLY-2552 > Project: WildFly > Issue Type: Task > Components: Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: web_security > Fix For: 9.0.0.CR1 > > > General article covering the security configuration for Undertow / WildFly: - > https://community.jboss.org/wiki/UndertowSecurityConfiguration -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2553) Enable SPNEGO Authentication

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2553?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2553: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Enable SPNEGO Authentication > ---------------------------- > > Key: WFLY-2553 > URL: https://issues.jboss.org/browse/WFLY-2553 > Project: WildFly > Issue Type: Sub-task > Components: Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: web_security > Fix For: 9.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2567) Custom authentication mechanism definition - Subsystem Level

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2567?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2567: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Custom authentication mechanism definition - Subsystem Level > ------------------------------------------------------------ > > Key: WFLY-2567 > URL: https://issues.jboss.org/browse/WFLY-2567 > Project: WildFly > Issue Type: Sub-task > Components: Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: web_security > Fix For: 9.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2652) Add/remove load metric operations should not require service restart

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2652?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2652: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Add/remove load metric operations should not require service restart > -------------------------------------------------------------------- > > Key: WFLY-2652 > URL: https://issues.jboss.org/browse/WFLY-2652 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 8.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Fix For: 9.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2824) Remove https://issues.apache.org/jira/browse/DIRAPI-125 workaround

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2824?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2824: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Remove https://issues.apache.org/jira/browse/DIRAPI-125 workaround > ------------------------------------------------------------------- > > Key: WFLY-2824 > URL: https://issues.jboss.org/browse/WFLY-2824 > Project: WildFly > Issue Type: Task > Components: Test Suite > Affects Versions: 8.0.0.CR1 > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Fix For: 9.0.0.CR1 > > > As a workaround for an Apache DS bug (https://issues.apache.org/jira/browse/DIRAPI-125) we forked their LdapUrl class in the testsuite/integration/basic module. This JIRA is a reminder to check if the upstream bug is fixed and the fix is in the release WF uses; if so remove the workaround. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2807) Messaging subsystem runtime-queue resource is not registered as "runtime-only"

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2807?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2807: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Messaging subsystem runtime-queue resource is not registered as "runtime-only" > ------------------------------------------------------------------------------ > > Key: WFLY-2807 > URL: https://issues.jboss.org/browse/WFLY-2807 > Project: WildFly > Issue Type: Bug > Components: Domain Management, JMS > Affects Versions: 8.0.0.CR1 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 9.0.0.CR1 > > > The runtime-queue resource only exists at runtime but isn't registered as such. I noticed this as ManagementClient does a recursive read-resource of the entire tree, but with include-runtime=false, but a CI run showed a failure reading one of these resources anyway: > ``` > 21:01:01,754 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) JBAS014613: Operation ("read-attribute") failed - address: ([ > ("subsystem" => "messaging"), > ("hornetq-server" => "default"), > ("runtime-queue" => "jms.tempqueue.661a6b15-7863-4d6c-b4b1-f8d62d294ea5") > ]) - failure description: "JBAS011676: No resource exists at address [ > (\"subsystem\" => \"messaging\"), > (\"hornetq-server\" => \"default\"), > (\"runtime-queue\" => \"jms.tempqueue.661a6b15-7863-4d6c-b4b1-f8d62d294ea5\") > ]" > ``` > Doing read-resource with these is a bit problematic in any case, since a bunch of read-attribute calls get executed as steps (that's what the above was) but the resource can disappear in the middle. But that's a separate problem. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2667) Support application-level batch configuration

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2667?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2667: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Support application-level batch configuration > --------------------------------------------- > > Key: WFLY-2667 > URL: https://issues.jboss.org/browse/WFLY-2667 > Project: WildFly > Issue Type: Feature Request > Components: Batch > Affects Versions: 8.0.0.Beta1 > Reporter: Cheng Fang > Assignee: James Perkins > Fix For: 9.0.0.CR1 > > > Applications should be able to override certain batch configuration in WildFly batch subsystem with application deployment descriptors. In particular, applications may want to specify their own datasource jndi-name for batch job repository. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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 March 2015