November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-493) Central CI Resource Availability

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-493?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-493: ------------------------------------ Cleaned up Openstack resources. Current resource availability: !screenshot-1.png|thumbnail! > Central CI Resource Availability > -------------------------------- > > Key: SWSQE-493 > URL: https://issues.jboss.org/browse/SWSQE-493 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Major > Attachments: screenshot-1.png > > > Clean up unused instances. > Currently OSOOS clusters are built with instance flavor: > m1.large: 8Gb, 4 Cores, 40G storage -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-498) Create new cluster/s from free baremetal hosts

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-498?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-498. --------------------------------- Resolution: Done created b06 cluster: b06 master, b11 node > Create new cluster/s from free baremetal hosts > ---------------------------------------------- > > Key: SWSQE-498 > URL: https://issues.jboss.org/browse/SWSQE-498 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3098) UX: Add support for map and list

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3098?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-3098: --------------------------------------- [~manstis] Hi, I think we can expose to the user directly and only `Collection` and `Map`. * `Collection` is iterable and it should be enough to cover all the flavors (`List`, `Set`, `Queue` etc) for the user because I don't think it will be supported index based condition (for instance "I expect element of index 2 of the List has this value") * `Map` should be enough to cover all key-value structures I would like to hide all the rest of complexity in the backend > UX: Add support for map and list > -------------------------------- > > Key: DROOLS-3098 > URL: https://issues.jboss.org/browse/DROOLS-3098 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to be able to use Data Objects that contain Lists and Maps -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-494) Install Python Module 'requests' on Jenkins E2E Agent

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-494?page=com.atlassian.jira.plugin.... ] Matt Mahoney reassigned SWSQE-494: ---------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Install Python Module 'requests' on Jenkins E2E Agent > ----------------------------------------------------- > > Key: SWSQE-494 > URL: https://issues.jboss.org/browse/SWSQE-494 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4207) Add capabilities in the Thread subsystem resource definitions

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFCORE-4207?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet commented on WFCORE-4207: ------------------------------------------- As far as I could see the problem is not present because, like you wrote: it would have led to a duplicate ServiceName problem. > Add capabilities in the Thread subsystem resource definitions > ------------------------------------------------------------- > > Key: WFCORE-4207 > URL: https://issues.jboss.org/browse/WFCORE-4207 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Affects Versions: 7.0.0.Alpha5 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Priority: Major > > The deprecated thread subsystem resource definitions are used in several subsystems. Adding support for capabilities should help them get the model validation easier. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4223) IllegalArgumentException when add a server-ssl-sni-context with no host-context-map

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFCORE-4223?page=com.atlassian.jira.plugi... ] Farah Juma reassigned WFCORE-4223: ---------------------------------- Assignee: Martin Mazanek (was: Darran Lofthouse) > IllegalArgumentException when add a server-ssl-sni-context with no host-context-map > ----------------------------------------------------------------------------------- > > Key: WFCORE-4223 > URL: https://issues.jboss.org/browse/WFCORE-4223 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Claudio Miranda > Assignee: Martin Mazanek > Priority: Minor > > "add" operation for /subsystem=elytron/server-ssl-sni-context doesn't require "host-context-map" attribute, however add a server-ssl-sni-context without this attribute results in an IllegalArgumentException. Set the "host-context-map" and the "add" operation works. > {code} > [standalone@localhost:9990 /] /subsystem=elytron/server-ssl-sni-context=sn3:add(default-ssl-context=wssl_ctx) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException", > "rolled-back" => true, > "response-headers" => {"process-state" => "reload-required"} > } > {code} > {code} > 11:29:09,803 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("server-ssl-sni-context" => "sn3") > ]): 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) > {code} > {code} > /subsystem=elytron/server-ssl-sni-context=sn1:read-operation-description(name=add) > { > "outcome" => "success", > "result" => { > "operation-name" => "add", > "description" => "Adds a SNI context", > "request-properties" => { > "default-ssl-context" => { > "type" => STRING, > "description" => "The context to use if no SNI information is present, or if it does not match any mappings", > "expressions-allowed" => false, > "required" => true, > "nillable" => false, > "capability-reference" => "org.wildfly.security.ssl-context", > "min-length" => 1L, > "max-length" => 2147483647L > }, > "host-context-map" => { > "type" => OBJECT, > "description" => "A mapping between a server name and an SSContext", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "capability-reference" => "org.wildfly.security.ssl-context", > "value-type" => STRING > } > }, > "reply-properties" => {}, > "read-only" => false, > "restart-required" => "resource-services", > "runtime-only" => false > }, > "response-headers" => {"process-state" => "reload-required"} > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3098) UX: Add support for map and list

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3098?page=com.atlassian.jira.plugi... ] Michael Anstis edited comment on DROOLS-3098 at 11/14/18 10:09 AM: ------------------------------------------------------------------- [~danielezonca] Hi, I was chatting to [~uxdlc] about this JIRA (helping her understand your requirements). Could you please advise what explicit types of {{Collection}} you want the UI to handle? e.g. {{List}}, {{Set}}, {{Map}}, {{Queue}}?, {{Stack}}? etc was (Author: manstis): [~danielezonca] Hi, I was chatting to [~uxdlc] about this JIRA (helping her understand your requirements). Could you please advise what explicit types of {{Collection}} you want the UI to handle? e.g. {{List}}, {{Set}}, {{Map}}, {{Queue?}?, {{Stack}}? etc > UX: Add support for map and list > -------------------------------- > > Key: DROOLS-3098 > URL: https://issues.jboss.org/browse/DROOLS-3098 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to be able to use Data Objects that contain Lists and Maps -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3098) UX: Add support for map and list

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3098?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3098: ---------------------------------------- [~danielezonca] Hi, I was chatting to [~uxdlc] about this JIRA (helping her understand your requirements). Could you please advise what explicit types of {{Collection}} you want the UI to handle? e.g. {{List}}, {{Set}}, {{Map}}, {{Queue?}?, {{Stack}}? etc > UX: Add support for map and list > -------------------------------- > > Key: DROOLS-3098 > URL: https://issues.jboss.org/browse/DROOLS-3098 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to be able to use Data Objects that contain Lists and Maps -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11343) Lock is not released when JTS is enabled and a timer is cancelled inside a transaction

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFLY-11343?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFLY-11343: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1648762 Bugzilla Update: Perform > Lock is not released when JTS is enabled and a timer is cancelled inside a transaction > -------------------------------------------------------------------------------------- > > Key: WFLY-11343 > URL: https://issues.jboss.org/browse/WFLY-11343 > Project: WildFly > Issue Type: Bug > Components: EJB > Environment: EAP 6.4.18 > Reporter: Shaun Appleton > Priority: Major > > Description of problem: > Lock is held by EJB timer (TimerServiceImpl) and in case JTS transaction is cancelled the lock won't be released correctly . This code is the problem: > https://github.com/wildfly/wildfly/blob/78dee79dd0f49c6cbd2b8db5d8640980f... > Basically it holds the timer lock until the transaction completes, and then attempts to release it in afterCompletion. The problem is that when JTS is enabled afterCompletion will be called by a seperate thread, which can't call unlock as it is not the owner. > A simple fix could be to just change the lock to a semaphore, so that the other thread can release it. > Version-Release number of selected component (if applicable): > How reproducible: > Always > Steps to Reproduce: > 1. Start a JTA/JTS tx and call an EJB timer inside it > 2. Make the transaction timeout > 3. Capture a thread dump and see a thread like below (0a0818b80 is locked object) > --------------------------------------------------------------------------------------------------------- > "Incoming-2,RouterPoliciesClusterGroup,svc-3-comecimpolicy-59228 (, payload=52 bytes)" #661 prio=5 os_prio=0 tid=0x00007f5214c2d000 nid=0x1e67 waiting on condition [0x00007f520ac97000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a0818b80> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Locked ownable synchronizers: > - <0x00000000ea1f4c48> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) > --------------------------------------------------------------------------------------------------------- > Actual results: > Lock being held forever > Expected results: > Lock getting released -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11351) Add resource address and attribute name to metric tags

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFLY-11351?page=com.atlassian.jira.plugin... ] Jeff Mesnil reassigned WFLY-11351: ---------------------------------- Assignee: Jeff Mesnil (was: Jason Greene) > Add resource address and attribute name to metric tags > ------------------------------------------------------ > > Key: WFLY-11351 > URL: https://issues.jboss.org/browse/WFLY-11351 > Project: WildFly > Issue Type: Enhancement > Components: MP Metrics > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > Fix For: 15.0.0.CR1 > > > WildFly metrics are exposed as Microprofile Metrics with unique names composed of the resource address and the attribute name. > This can lead to very long unhelpful names. For example, the request-count metric on the /deployment=example.war/subsystem=undertow/servlet=org.example.MyServlet resource is named is registered as `deployment/example.war/subsystem/undertow/servlet/org.example.MyServlet/request-count`. > When the metric is exported to Prometheus format, it becomes `deployment_example_war_subsystem_undertow_servlet_org_example_my_servlet_request_count` which is a mouthful. > In order to simply query and aggregation of metrics, the resource address and the attribute name will be stored in the metric tags. > E.g. for the metric above, its tags will be: > * subsystem="undertow" > * deployment="example.war" > * servlet="org.example.MyServlet" > * attribute="request-count" > This makes it much simple for example to aggregate all metrics from a given deployment by looking at metrics with the tag deployment="example.war". > Note hower that the tags does not preserve the order of the resource address' elements. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 November 2018