January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3571) Rename Test Scenario

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-3571: ------------------------------------- Summary: Rename Test Scenario Key: DROOLS-3571 URL: https://issues.jboss.org/browse/DROOLS-3571 Project: Drools Issue Type: Task Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Daniele Zonca Rename Test Scenario to Test Scenario (Legacy) and rename Test Scenario (Preview) to Test Scenario -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-577) Run UI tests against all supported browsers

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-577?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-577: ------------------------------------- [~mmahoney] could you please add a list of supported browsers to description? > Run UI tests against all supported browsers > ------------------------------------------- > > Key: SWSQE-577 > URL: https://issues.jboss.org/browse/SWSQE-577 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Michael Foley > Priority: Minor > > Currently we run automation against chrome. We need to run it against all supported browsers. > List of supported browsers: > TODO -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-577) Run UI tests against all supported browsers

by Filip Brychta (Jira)

Filip Brychta created SWSQE-577: ----------------------------------- Summary: Run UI tests against all supported browsers Key: SWSQE-577 URL: https://issues.jboss.org/browse/SWSQE-577 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Michael Foley Currently we run automation against chrome. We need to run it against all supported browsers. List of supported browsers: TODO -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-573) Central CI will be decommissioned by the end of Feb 2019

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-573?page=com.atlassian.jira.plugin.... ] Filip Brychta reassigned SWSQE-573: ----------------------------------- Summary: Central CI will be decommissioned by the end of Feb 2019 (was: Check PSI options) Description: CI-RHOS is proposed to be decommissioned by the end of Feb 2019 We need to migrate to PSI - https://docs.engineering.redhat.com/display/HTD/CI-RHOS+consolidation+wit... We should check our options there. was: There is a new initiative which looks promising - https://docs.engineering.redhat.com/display/HTD/CI-RHOS+consolidation+wit... We should check our options there. Priority: Major (was: Minor) Team: Infrastructure (was: Infrastructure) Assignee: Filip Brychta (was: Michael Foley) Sprint: Kiali Sprint #17 > Central CI will be decommissioned by the end of Feb 2019 > -------------------------------------------------------- > > Key: SWSQE-573 > URL: https://issues.jboss.org/browse/SWSQE-573 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > > CI-RHOS is proposed to be decommissioned by the end of Feb 2019 > We need to migrate to PSI - https://docs.engineering.redhat.com/display/HTD/CI-RHOS+consolidation+wit... > We should check our options there. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11565) WildFly Server Adds Transfer Encoding Chunk Header to the HttpResponse with status code 204

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-11565?page=com.atlassian.jira.plugin... ] Bartosz Baranowski commented on WFLY-11565: ------------------------------------------- [~dsahu030686] Sure, np. I will take a look shortly. > WildFly Server Adds Transfer Encoding Chunk Header to the HttpResponse with status code 204 > ------------------------------------------------------------------------------------------- > > Key: WFLY-11565 > URL: https://issues.jboss.org/browse/WFLY-11565 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.0.Final > Reporter: Deepak Sahu > Assignee: Bartosz Baranowski > Priority: Major > Attachments: API.war > > > I am using WildFly Server 9.0.0 Final, Javax ws, Jersey for developing Rest APIs. For all the responses whose httpStatus code is 204, the wildfly server adds Transfer encoding Chunked in the response header, which is not correct as per the Rest Standards. Because of this behavior some of the RestAPI clients hang, as they keep waiting for the response (which is not at all there). > To verify the issue, I tried the same with Springboot instead of deploying the war in WildFly and the Response Header was not added with Transfer Encoding Chuncked. > Let me know if some other information is required to fix this issue, if this is already fixed is there any patch for this issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11658) Automatic detection of file based KeyStore types community docs.

by Martin Mazanek (Jira)

[ https://issues.jboss.org/browse/WFLY-11658?page=com.atlassian.jira.plugin... ] Martin Mazanek moved WFCORE-4300 to WFLY-11658: ----------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-11658 (was: WFCORE-4300) > Automatic detection of file based KeyStore types community docs. > ---------------------------------------------------------------- > > Key: WFLY-11658 > URL: https://issues.jboss.org/browse/WFLY-11658 > Project: WildFly > Issue Type: Enhancement > Reporter: Martin Mazanek > Assignee: Martin Mazanek > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4300) Automatic detection of file based KeyStore types community docs.

by Martin Mazanek (Jira)

Martin Mazanek created WFCORE-4300: -------------------------------------- Summary: Automatic detection of file based KeyStore types community docs. Key: WFCORE-4300 URL: https://issues.jboss.org/browse/WFCORE-4300 Project: WildFly Core Issue Type: Enhancement Reporter: Martin Mazanek Assignee: Martin Mazanek -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11657) Value validator for 'host-context-map' attribute of 'server-ssl-sni-context' resource

by Jan Stourac (Jira)

Jan Stourac created WFLY-11657: ---------------------------------- Summary: Value validator for 'host-context-map' attribute of 'server-ssl-sni-context' resource Key: WFLY-11657 URL: https://issues.jboss.org/browse/WFLY-11657 Project: WildFly Issue Type: Bug Components: Security Affects Versions: 15.0.1.Final, 15.0.0.Final Reporter: Jan Stourac Assignee: Darran Lofthouse There is not validation for 'host-context-map' property values on key side. There is validation for the values that represents 'server-ssl-contexts', although, there is no validation for host matching part. E.g. writing attribute of this value is possible: {code} /subsystem=elytron/server-ssl-sni-context=serverSslSniCtx:write-attribute(name=host-context-map,value={"\\?.example.com"=validSslContext,"..example.com"="validSslContext", "\\*\\*.example.com"=validSslContext}) {code} {code} "\\?.example.com" "..example.com" "\\*\\*.example.com" {code} even though, these are invalid host name matchers IMHO. It would be nice to identify these and report those to user immediately during the configuration attempt. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4299) Creating SNI context requires 'host-context-map' attribute defined

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4299?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-4299: ---------------------------------------- Assignee: (was: Darran Lofthouse) > Creating SNI context requires 'host-context-map' attribute defined > ------------------------------------------------------------------ > > Key: WFCORE-4299 > URL: https://issues.jboss.org/browse/WFCORE-4299 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 7.0.0.Final > Reporter: Jan Stourac > Priority: Major > > When one want to create a server-ssl-sni-context, there are two attributes for such resource: > * default-ssl-context - this one is marked as required > * host-context-map - not marked as required > Still, when I try to create server-ssl-sni-context without specifying 'host-context-map', the operation fails with following (see repro steps for further info): > {code} > $ ./bin/jboss-cli.sh -c "/subsystem=elytron/server-ssl-sni-context=sniContext:add(default-ssl-context=newServerSSLContext)" > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException", > "rolled-back" => true > } > {code} > in server log there is following: > {code} > 09:08:08,228 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("server-ssl-sni-context" => "sniContext") > ]): java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:139) > at org.jboss.dmr.ModelNode.keys(ModelNode.java:1580) > at org.wildfly.extension.elytron.SSLDefinitions$7.getValueSupplier(SSLDefinitions.java:1046) > at org.wildfly.extension.elytron.TrivialAddHandler.performRuntime(TrivialAddHandler.java:68) > at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:159) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1411) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:289) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:255) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4299) Creating SNI context requires 'host-context-map' attribute defined

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4299?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved WFLY-11655 to WFCORE-4299: ------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4299 (was: WFLY-11655) Component/s: Security (was: Security) Affects Version/s: 7.0.0.Final (was: 15.0.0.Final) (was: 15.0.1.Final) > Creating SNI context requires 'host-context-map' attribute defined > ------------------------------------------------------------------ > > Key: WFCORE-4299 > URL: https://issues.jboss.org/browse/WFCORE-4299 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 7.0.0.Final > Reporter: Jan Stourac > Assignee: Darran Lofthouse > Priority: Major > > When one want to create a server-ssl-sni-context, there are two attributes for such resource: > * default-ssl-context - this one is marked as required > * host-context-map - not marked as required > Still, when I try to create server-ssl-sni-context without specifying 'host-context-map', the operation fails with following (see repro steps for further info): > {code} > $ ./bin/jboss-cli.sh -c "/subsystem=elytron/server-ssl-sni-context=sniContext:add(default-ssl-context=newServerSSLContext)" > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException", > "rolled-back" => true > } > {code} > in server log there is following: > {code} > 09:08:08,228 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("server-ssl-sni-context" => "sniContext") > ]): java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:139) > at org.jboss.dmr.ModelNode.keys(ModelNode.java:1580) > at org.wildfly.extension.elytron.SSLDefinitions$7.getValueSupplier(SSLDefinitions.java:1046) > at org.wildfly.extension.elytron.TrivialAddHandler.performRuntime(TrivialAddHandler.java:68) > at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:159) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1411) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:289) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:255) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 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 January 2019