May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2810) Add "hasCapability" to CapabilityServiceSupport

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2810?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2810: ------------------------------------- Description: Let services do capability checks. Looking at the discussion of the basic design considerations around CapabilityServiceSupport at [1] I don't see anything that argues against this. [1] http://lists.jboss.org/pipermail/wildfly-dev/2015-June/004159.html was:Let services do capability checks. > Add "hasCapability" to CapabilityServiceSupport > ----------------------------------------------- > > Key: WFCORE-2810 > URL: https://issues.jboss.org/browse/WFCORE-2810 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 3.0.0.Beta22 > > > Let services do capability checks. > Looking at the discussion of the basic design considerations around CapabilityServiceSupport at [1] I don't see anything that argues against this. > [1] http://lists.jboss.org/pipermail/wildfly-dev/2015-June/004159.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8782) Reenable RemoteIdentityTestCase in AS TS with elytron profile

by Josef Cacek (JIRA)

Josef Cacek created WFLY-8782: --------------------------------- Summary: Reenable RemoteIdentityTestCase in AS TS with elytron profile Key: WFLY-8782 URL: https://issues.jboss.org/browse/WFLY-8782 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Josef Cacek The JBEAP-9744 is fixed, let's reenable regression tests. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8782) Reenable RemoteIdentityTestCase in AS TS with elytron profile

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-8782?page=com.atlassian.jira.plugin.... ] Josef Cacek reassigned WFLY-8782: --------------------------------- Assignee: Josef Cacek > Reenable RemoteIdentityTestCase in AS TS with elytron profile > ------------------------------------------------------------- > > Key: WFLY-8782 > URL: https://issues.jboss.org/browse/WFLY-8782 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > > The JBEAP-9744 is fixed, let's reenable regression tests. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2667) CLI returns always "0" if CLI is started with "cmd /c " on Windows

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2667?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-2667: ------------------------------------------------- Peter Mackay <pmackay(a)redhat.com> changed the Status of [bug 1444620|https://bugzilla.redhat.com/show_bug.cgi?id=1444620] from ON_QA to VERIFIED > CLI returns always "0" if CLI is started with "cmd /c " on Windows > ------------------------------------------------------------------ > > Key: WFCORE-2667 > URL: https://issues.jboss.org/browse/WFCORE-2667 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Scripts > Environment: Windows > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > Priority: Critical > Fix For: 3.0.0.Beta16 > > > *Description of problem:* > CLI returns always "0" if CLI is started with "cmd /c " on Windows > This issue is regression against EAP 7.0.0, but priority of this jira is not blocker, because this issue is corner case. > *Steps to Reproduce:* > # jboss-cli.bat --command=version_error > # echo Exit Code is %errorlevel% > # REM verify correct return value: 1 > # cmd /c jboss-cli.bat --command=version_error > # echo Exit Code is %errorlevel% > # REM return value is 0 in EAP 7.1.0.DR16. Correct return value should be 1 > *Actual results:* > {noformat} > C:\Users\Administrator\playground\7.1.0.DR16\jboss-eap-7.1\bin>jboss-cli.bat --command=version_error > Unexpected command 'version_error'. Type 'help --commands' for the list of supported commands. > C:\Users\Administrator\playground\7.1.0.DR16\jboss-eap-7.1\bin>echo Exit Code is %errorlevel% > Exit Code is 1 > C:\Users\Administrator\playground\7.1.0.DR16\jboss-eap-7.1\bin> > C:\Users\Administrator\playground\7.1.0.DR16\jboss-eap-7.1\bin>cmd /c jboss-cli.bat --command=version_error > Unexpected command 'version_error'. Type 'help --commands' for the list of supported commands. > C:\Users\Administrator\playground\7.1.0.DR16\jboss-eap-7.1\bin>echo Exit Code is %errorlevel% > Exit Code is 0 > C:\Users\Administrator\playground\7.1.0.DR16\jboss-eap-7.1\bin> > {noformat} > *Expected results:* > {noformat} > C:\Users\Administrator\playground\7.0.0\jboss-eap-7.0\bin>jboss-cli.bat --command=version_error > Unexpected command 'version_error'. Type 'help --commands' for the list of supported commands. > C:\Users\Administrator\playground\7.0.0\jboss-eap-7.0\bin>echo Exit Code is %errorlevel% > Exit Code is 1 > C:\Users\Administrator\playground\7.0.0\jboss-eap-7.0\bin> > C:\Users\Administrator\playground\7.0.0\jboss-eap-7.0\bin>cmd /c jboss-cli.bat --command=version_error > Unexpected command 'version_error'. Type 'help --commands' for the list of supported commands. > C:\Users\Administrator\playground\7.0.0\jboss-eap-7.0\bin>echo Exit Code is %errorlevel% > Exit Code is 1 > C:\Users\Administrator\playground\7.0.0\jboss-eap-7.0\bin> > {noformat} > *Additional info:* > We see this issue also if jboss-cli.bat script is called from groovy or java -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AG-23) Proper implementation of XAResourceWrapper

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-23?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-23. ----------------------------- Resolution: Done Product Name and Product Version come from MANIFEST.MF which means that those fields will be null when the class is not loaded from the JAR file. Should be OK though, as those fields are informative. > Proper implementation of XAResourceWrapper > ------------------------------------------ > > Key: AG-23 > URL: https://issues.jboss.org/browse/AG-23 > Project: Agroal > Issue Type: Task > Components: narayana > Affects Versions: 0.1 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2814) There is description of "case-sensitive" attribute inconsistency between model and XSD.

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2814?page=com.atlassian.jira.plugi... ] Ilia Vassilev moved ELY-1111 to WFCORE-2814: -------------------------------------------- Project: WildFly Core (was: WildFly Elytron) Key: WFCORE-2814 (was: ELY-1111) Component/s: Security (was: Credential Store) > There is description of "case-sensitive" attribute inconsistency between model and XSD. > --------------------------------------------------------------------------------------- > > Key: WFCORE-2814 > URL: https://issues.jboss.org/browse/WFCORE-2814 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Ilia Vassilev > > There is description of "case-sensitive" attribute inconsistency between model and XSD. > In XSD is missing default value. > Please add to XSD default value and unify description. > I suggest use description from model as right one: "Case sensitivity of the credential store. If case insensitive only lower case names are allowed for aliases.". > *MODEL* > {code} > "case-sensitive" => { > "type" => BOOLEAN, > "description" => "Case sensitivity of the credential store. If case insensitive only lower case names are allowed for aliases.", > "attribute-group" => "implementation", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "default" => false, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > {code} > *DMR* > {code} > <xs:attribute name="case-sensitive" type="xs:boolean" use="optional"> > <xs:annotation> > <xs:documentation> > Indicates that the credential store is case sensitive and should then allow for upper case in alias. > </xs:documentation> > </xs:annotation> > </xs:attribute> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6895) TimerService problem(duplicated resource)

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6895?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-6895: ---------------------------------------- The linked PR is for the 10.x branch and it looks fine for that, so assuming it still passes CI I'll merge it. There are no particular plans for another 10.x release though. For WF 11, WFCORE-1272 has fixed the problem. > TimerService problem(duplicated resource) > ----------------------------------------- > > Key: WFLY-6895 > URL: https://issues.jboss.org/browse/WFLY-6895 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Final > Environment: Two standalone instances connected into a cluster. > *Master WildFly* > {code} > standalone.bat -c standalone-full-ha.xml -Djboss.node.name=master > {code} > *Slave WildFly* > {code} > standalone.bat -c standalone-full-ha.xml -Djboss.node.name=slave -Djboss.socket.binding.port-offset=100 > {code} > Both instances has the same singleton policy defined in singleton-full-ha.xml: > {code} > <singleton-policy name="scada-singleton" cache-container="server"> > <simple-election-policy> > <name-preferences>master</name-preferences> > </simple-election-policy> > </singleton-policy> > {code} > Reporter: Artur Kowalczyk > Assignee: Tomasz Adamski > Fix For: 10.2.0.Final, 11.0.0.Beta1 > > > I found a problem with TimerService that occurs when your application is configured as a singleton deployment. > *Test Case* > # Start master node, the app is also started - OK > # Start slave node, the app is deployed but bot stared - OK > # Stop master node, the app is started on slave - OK > # Start master node, there is a preference for node name so the app will be started again on master and stopped in slave - OK > # Stop master node, the app should be started again on slave but an exception occur. - ERROR > {code} > 09:50:42,115 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.subunit."wildfly-ejb-in-ear.ear"."wildfly-ejb-in-ear-ejb.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."wildfly-ejb-in-ear.ear"."wildfly-ejb-in-ear-ejb.jar".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of subdeployment "wildfly-ejb-in-ear-ejb.jar" of deployment "wildfly-ejb-in-ear.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEJB0086: Failed to install management resources for TimerEJB > at org.jboss.as.ejb3.deployment.processors.EjbManagementDeploymentUnitProcessor.deploy(EjbManagementDeploymentUnitProcessor.java:82) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) > ... 5 more > Caused by: java.lang.IllegalStateException: WFLYCTL0075: Duplicate resource timer-service > at org.jboss.as.controller.registry.AbstractModelResource$DefaultResourceProvider.register(AbstractModelResource.java:290) > at org.jboss.as.controller.registry.AbstractModelResource.registerChild(AbstractModelResource.java:169) > at org.jboss.as.server.deployment.DeploymentResourceSupport.register(DeploymentResourceSupport.java:322) > at org.jboss.as.server.deployment.DeploymentResourceSupport.registerDeploymentSubResource(DeploymentResourceSupport.java:219) > at org.jboss.as.ejb3.deployment.processors.EjbManagementDeploymentUnitProcessor.installManagementResource(EjbManagementDeploymentUnitProcessor.java:119) > at org.jboss.as.ejb3.deployment.processors.EjbManagementDeploymentUnitProcessor.deploy(EjbManagementDeploymentUnitProcessor.java:79) > ... 6 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AG-23) Proper implementation of XAResourceWrapper

by Luis Barreiro (JIRA)

Luis Barreiro created AG-23: ------------------------------- Summary: Proper implementation of XAResourceWrapper Key: AG-23 URL: https://issues.jboss.org/browse/AG-23 Project: Agroal Issue Type: Task Components: narayana Affects Versions: 0.1 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 0.2 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AG-22) Deprecate interrupt protection and remove jboss-threads integration

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-22?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-22. ----------------------------- Resolution: Done > Deprecate interrupt protection and remove jboss-threads integration > ------------------------------------------------------------------- > > Key: AG-22 > URL: https://issues.jboss.org/browse/AG-22 > Project: Agroal > Issue Type: Task > Components: api, jboss-threads > Affects Versions: 0.1 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.2 > > > Interrupt protection has been removed from the requirements. > It means that AG-19 sould be reverted, and also InterruptProtection should be removed from the API -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6895) TimerService problem(duplicated resource)

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6895?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-6895: ----------------------------------- Fix Version/s: 10.2.0.Final 11.0.0.Beta1 > TimerService problem(duplicated resource) > ----------------------------------------- > > Key: WFLY-6895 > URL: https://issues.jboss.org/browse/WFLY-6895 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Final > Environment: Two standalone instances connected into a cluster. > *Master WildFly* > {code} > standalone.bat -c standalone-full-ha.xml -Djboss.node.name=master > {code} > *Slave WildFly* > {code} > standalone.bat -c standalone-full-ha.xml -Djboss.node.name=slave -Djboss.socket.binding.port-offset=100 > {code} > Both instances has the same singleton policy defined in singleton-full-ha.xml: > {code} > <singleton-policy name="scada-singleton" cache-container="server"> > <simple-election-policy> > <name-preferences>master</name-preferences> > </simple-election-policy> > </singleton-policy> > {code} > Reporter: Artur Kowalczyk > Assignee: Tomasz Adamski > Fix For: 10.2.0.Final, 11.0.0.Beta1 > > > I found a problem with TimerService that occurs when your application is configured as a singleton deployment. > *Test Case* > # Start master node, the app is also started - OK > # Start slave node, the app is deployed but bot stared - OK > # Stop master node, the app is started on slave - OK > # Start master node, there is a preference for node name so the app will be started again on master and stopped in slave - OK > # Stop master node, the app should be started again on slave but an exception occur. - ERROR > {code} > 09:50:42,115 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.subunit."wildfly-ejb-in-ear.ear"."wildfly-ejb-in-ear-ejb.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."wildfly-ejb-in-ear.ear"."wildfly-ejb-in-ear-ejb.jar".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of subdeployment "wildfly-ejb-in-ear-ejb.jar" of deployment "wildfly-ejb-in-ear.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEJB0086: Failed to install management resources for TimerEJB > at org.jboss.as.ejb3.deployment.processors.EjbManagementDeploymentUnitProcessor.deploy(EjbManagementDeploymentUnitProcessor.java:82) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) > ... 5 more > Caused by: java.lang.IllegalStateException: WFLYCTL0075: Duplicate resource timer-service > at org.jboss.as.controller.registry.AbstractModelResource$DefaultResourceProvider.register(AbstractModelResource.java:290) > at org.jboss.as.controller.registry.AbstractModelResource.registerChild(AbstractModelResource.java:169) > at org.jboss.as.server.deployment.DeploymentResourceSupport.register(DeploymentResourceSupport.java:322) > at org.jboss.as.server.deployment.DeploymentResourceSupport.registerDeploymentSubResource(DeploymentResourceSupport.java:219) > at org.jboss.as.ejb3.deployment.processors.EjbManagementDeploymentUnitProcessor.installManagementResource(EjbManagementDeploymentUnitProcessor.java:119) > at org.jboss.as.ejb3.deployment.processors.EjbManagementDeploymentUnitProcessor.deploy(EjbManagementDeploymentUnitProcessor.java:79) > ... 6 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 May 2017