August 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1723) OperationRequestCompleter ignores CommandArgument#canAppearNext in choosing ValueCompleter when there's more then one indexed arguments

by Bartosz Spyrko-Śmietanko (JIRA)

Bartosz Spyrko-Śmietanko created WFCORE-1723: ------------------------------------------------ Summary: OperationRequestCompleter ignores CommandArgument#canAppearNext in choosing ValueCompleter when there's more then one indexed arguments Key: WFCORE-1723 URL: https://issues.jboss.org/browse/WFCORE-1723 Project: WildFly Core Issue Type: Bug Components: CLI Affects Versions: 3.0.0.Alpha5 Reporter: Bartosz Spyrko-Śmietanko Assignee: Bartosz Spyrko-Śmietanko If there are two or more indexed CommandArguments that can be used to complete user entry at the same index, the first one will always be chosen - even if it clashes with previous arguments. For example: {{patch rollback ..<TAB>}} produces a list of directories - this is because PatchHandler registers multiple CommandArguments with index 1 and in this case a completer for patch apply is the first one matched. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6970) JMS Queue creation is wrong

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6970?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-6970: ---------------------------------------- Why do you say it's a docs issue? The first command is a CLI high level command and should work. What happens when you use it? > JMS Queue creation is wrong > ---------------------------- > > Key: WFLY-6970 > URL: https://issues.jboss.org/browse/WFLY-6970 > Project: WildFly > Issue Type: Bug > Components: CLI, Documentation, JMS > Affects Versions: 10.0.0.Final > Environment: https://docs.jboss.org/author/display/WFLY10/Messaging+configuration > Reporter: Rajitha Gunawardhane > Priority: Critical > Labels: JMS > > related link: https://docs.jboss.org/author/display/WFLY10/Messaging+configuration > jms-queue add --queue-address=myQueue --entries=queues/myQueue > above command is not working > Following one is working > /subsystem=messaging-activemq/server=default/jms-queue=TestQ/:add(entries=["java:/jboss/exported/jms/queue/TestQ"]) > http://middlewaremagic.com/jboss/?p=2739 has a better explanation for Wildfly 10.0.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6970) JMS Queue creation is wrong

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6970?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-6970: ----------------------------------- Component/s: CLI JMS > JMS Queue creation is wrong > ---------------------------- > > Key: WFLY-6970 > URL: https://issues.jboss.org/browse/WFLY-6970 > Project: WildFly > Issue Type: Bug > Components: CLI, Documentation, JMS > Affects Versions: 10.0.0.Final > Environment: https://docs.jboss.org/author/display/WFLY10/Messaging+configuration > Reporter: Rajitha Gunawardhane > Priority: Critical > Labels: JMS > > related link: https://docs.jboss.org/author/display/WFLY10/Messaging+configuration > jms-queue add --queue-address=myQueue --entries=queues/myQueue > above command is not working > Following one is working > /subsystem=messaging-activemq/server=default/jms-queue=TestQ/:add(entries=["java:/jboss/exported/jms/queue/TestQ"]) > http://middlewaremagic.com/jboss/?p=2739 has a better explanation for Wildfly 10.0.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5542) Look into using apache's upstream JSTL

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5542?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-5542: ----------------------------------- about 1) from reading the BZ, the fixes doesn't apply to upstream aka 1.1 version and as such shouldn't be there. > Look into using apache's upstream JSTL > -------------------------------------- > > Key: WFLY-5542 > URL: https://issues.jboss.org/browse/WFLY-5542 > Project: WildFly > Issue Type: Task > Components: EE, Web (Undertow) > Affects Versions: 10.0.0.CR2 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > We are now using forked combination of apache & java.net's version of JSTL. > We should look into using upstream version if possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-573) Programatic authentication

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-573?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-573. ---------------------------------- Resolution: Migrated to another ITS https://github.com/wildfly-security/elytron-web/issues/27 > Programatic authentication > -------------------------- > > Key: ELY-573 > URL: https://issues.jboss.org/browse/ELY-573 > Project: WildFly Elytron > Issue Type: Enhancement > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta9 > > > This is critical as it risks changing defined APIs and SPIs but we need to cover programatic authentication. > It is however possible this is handled within the app server integration and not within our framework but we have two predominant cases: - > - Servlet calls authenticate which means our mechanisms need to be triggered to challenge the client. > - Servlet calls login with a username and password. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-573) Programatic authentication

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-573?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reopened ELY-573: ---------------------------------- > Programatic authentication > -------------------------- > > Key: ELY-573 > URL: https://issues.jboss.org/browse/ELY-573 > Project: WildFly Elytron > Issue Type: Enhancement > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta9 > > > This is critical as it risks changing defined APIs and SPIs but we need to cover programatic authentication. > It is however possible this is handled within the app server integration and not within our framework but we have two predominant cases: - > - Servlet calls authenticate which means our mechanisms need to be triggered to challenge the client. > - Servlet calls login with a username and password. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-573) Programatic authentication

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-573?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-573. ---------------------------------- Resolution: Done Programatic authentication for HTTP is handled within the Elytron Web project. > Programatic authentication > -------------------------- > > Key: ELY-573 > URL: https://issues.jboss.org/browse/ELY-573 > Project: WildFly Elytron > Issue Type: Enhancement > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta9 > > > This is critical as it risks changing defined APIs and SPIs but we need to cover programatic authentication. > It is however possible this is handled within the app server integration and not within our framework but we have two predominant cases: - > - Servlet calls authenticate which means our mechanisms need to be triggered to challenge the client. > - Servlet calls login with a username and password. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1722) Tests for ignore-unused-configuration in conjunction with --backup

by Martin Simka (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1722?page=com.atlassian.jira.plugi... ] Martin Simka updated WFCORE-1722: --------------------------------- Summary: Tests for ignore-unused-configuration in conjunction with --backup (was: Tests for ignore-unused-configuration in conjuction with --backup) > Tests for ignore-unused-configuration in conjunction with --backup > ------------------------------------------------------------------ > > Key: WFCORE-1722 > URL: https://issues.jboss.org/browse/WFCORE-1722 > Project: WildFly Core > Issue Type: Enhancement > Components: Test Suite > Reporter: Martin Simka > Assignee: Martin Simka > > Add new tests that check that ignore-unused-resources works as expected in combination with --backup: > * check that if ignore-unused-resources is undefined and --backup not set, then the behavior is as if the attribute had a value of 'true' > * check that if ignore-unused-resources is undefined and --backup is set, then the behavior is as if the attribute had a value of 'false' > * no need to check that if ignore-unused-resources is true and --backup not set, this is already covered by other tests > * check that if ignore-unused-resources is true and --backup is set, slave does not have full domain config > * check that if ignore-unused-resources is false and --backup not set, then the slave has full domain config > * check that if ignore-unused-resources is false and --backup is set, then the slave has full domain config -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1722) Tests for ignore-unused-configuration in conjuction with --backup

by Martin Simka (JIRA)

Martin Simka created WFCORE-1722: ------------------------------------ Summary: Tests for ignore-unused-configuration in conjuction with --backup Key: WFCORE-1722 URL: https://issues.jboss.org/browse/WFCORE-1722 Project: WildFly Core Issue Type: Enhancement Components: Test Suite Reporter: Martin Simka Assignee: Martin Simka Add new tests that check that ignore-unused-resources works as expected in combination with --backup: * check that if ignore-unused-resources is undefined and --backup not set, then the behavior is as if the attribute had a value of 'true' * check that if ignore-unused-resources is undefined and --backup is set, then the behavior is as if the attribute had a value of 'false' * no need to check that if ignore-unused-resources is true and --backup not set, this is already covered by other tests * check that if ignore-unused-resources is true and --backup is set, slave does not have full domain config * check that if ignore-unused-resources is false and --backup not set, then the slave has full domain config * check that if ignore-unused-resources is false and --backup is set, then the slave has full domain config -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6971) MDB cannot be deployed after migration due to "DuplicateServiceException: Service jboss.infinispan.ejb."mdb-1.0-SNAPSHOT.jar".config is already registered"

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/WFLY-6971?page=com.atlassian.jira.plugin.... ] Panagiotis Sotiropoulos updated WFLY-6971: ------------------------------------------ Git Pull Request: (was: https://github.com/jbossas/jboss-eap7/pull/695, https://github.com/jbossas/jboss-eap7/pull/694) > MDB cannot be deployed after migration due to "DuplicateServiceException: Service jboss.infinispan.ejb."mdb-1.0-SNAPSHOT.jar".config is already registered" > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-6971 > URL: https://issues.jboss.org/browse/WFLY-6971 > Project: WildFly > Issue Type: Bug > Components: EJB, JMS > Affects Versions: 10.1.0.CR1 > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > Priority: Critical > Attachments: mdb-1.0-SNAPSHOT.jar, standalone-full-ha.xml_eap6 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > If EAP 7 with (manually) migrated configuration from EAP 6.4.7.CP server is started then MDB deployment fails with: > {code} > 14:17:09,432 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."mdb-1.0-SNAPSHOT.jar".cache-dependencies-installer: org.jboss.msc.service.StartException in service jboss.deployment.unit."mdb-1.0-SNAPSHOT.jar".cache-dependencies-installer: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_71] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_71] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_71] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.infinispan.ejb."mdb-1.0-SNAPSHOT.jar".config is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1] > at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1] > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1] > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1] > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1] > at org.jboss.as.ejb3.cache.distributable.DistributableCacheFactoryBuilderService.installDeploymentUnitDependencies(DistributableCacheFactoryBuilderService.java:93) > at org.jboss.as.ejb3.deployment.processors.CacheDependenciesProcessor$1.start(CacheDependenciesProcessor.java:50) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1] > ... 3 more > {code} > Problem seems to be configuration of caches in ejb subsystem which looks like: > {code} > <subsystem xmlns="urn:jboss:domain:ejb3:4.0"> > ... > <caches> > <cache name="simple" aliases="NoPassivationCache"/> > <cache name="passivating" passivation-store-ref="file" aliases="SimpleStatefulCache"/> > <cache name="clustered" passivation-store-ref="infinispan" aliases="StatefulTreeCache"/> > </caches> > ... > </subsystem> > {code} > If any of lines: > {code} > <cache name="passivating" passivation-store-ref="file" aliases="SimpleStatefulCache"/> > <cache name="clustered" passivation-store-ref="infinispan" > {code} > is removed or I take default configuration from EAP 7: > {code} > <caches> > <cache name="simple"/> > <cache name="distributable" passivation-store-ref="infinispan" aliases="passivating clustered"/> > </caches> > {code} > then MDB is deployed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 August 2016