August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-457) Optimization: make threads return immediately if NAKACK has another active thread for the same sender

by Bela Ban (JIRA)

Optimization: make threads return immediately if NAKACK has another active thread for the same sender ----------------------------------------------------------------------------------------------------- Key: JGRP-457 URL: http://jira.jboss.com/jira/browse/JGRP-457 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.5 In NAKACK, when a thread places a message for sender S into the NakReceiverWindow NRW, it subsequently acquires a lock on NRW (lock by sender) and removes as many messages as possible and passes them up. If many threads do this at the same time, all threads but one are blocked, and - when finally unblocked - usually return. This causes context switches and possibly cache flushing, so a better way would be to have the threads check whether another thread is already removing messages using a CAS operation *before* acquiring the lock. The effect should be that no threads will wait on the lock unnecessarily, and thus fewer context switches, and more threads available to the pool. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 day, 2 hours

2
3
0 / 0

[JBoss JIRA] (ELY-776) Eliminate reference to "slot" from module configurations

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-776?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-776: ------------------------------------ Assignee: Darran Lofthouse > Eliminate reference to "slot" from module configurations > -------------------------------------------------------- > > Key: ELY-776 > URL: https://issues.jboss.org/browse/ELY-776 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: David Lloyd > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta15 > > > The final version of our client XSD should accept a name for modules but no slot. Instead, either the new name-only APIs should be used or a ModuleIdentifier created via that class's "fromString" method. Module slots are deprecated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

3 weeks, 5 days

2
1
0 / 0

[JBoss JIRA] (JBRULES-3445) DSL expander expands lines in /* */comment block

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3445: ------------------------------------ Summary: DSL expander expands lines in /* */comment block Key: JBRULES-3445 URL: https://issues.jboss.org/browse/JBRULES-3445 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco When you comment some code in dslr file, the expander still tries to expand it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

5 months, 3 weeks

3
10
0 / 0

[JBoss JIRA] (SWSQE-401) Kiali Client Needs To Support SSL

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-401?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo commented on SWSQE-401: ----------------------------------------------- FIxed with Existing code {code:python} import ssl context = ssl._create_unverified_context() client = KialiClient(host='kiali-istio-system.openshift.jonqe.lab.eng.bos.redhat.com', scheme='https', port=443, context=context) client.status() {u'status': {u'Kiali state': u'running', u'Kiali core version': u'v0.7.0-SNAPSHOT', u'Kiali core commit hash': u'816129afd83b9fdbc07ba2361a63d321d5adea55', u'Kiali console version': u'0.7.0-SNAPSHOT.2073-local-543db3ee21cb717df588ab3c7fabd72a5c22ca1f'}, u'externalServices': [{u'version': u'1.0.0', u'name': u'Istio'}, {u'version': u'2.3.1', u'name': u'Prometheus'}, {u'version': u'v1.10.0+b81c8f8', u'name': u'Kubernetes'}], u'warningMessages': []} {code} > Kiali Client Needs To Support SSL > --------------------------------- > > Key: SWSQE-401 > URL: https://issues.jboss.org/browse/SWSQE-401 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > > Issue is as follows: > KialiClient(scheme='https', host=config.get('kiali_hostname'), > username=config.get('kiali_username'), password=config.get('kiali_password')) > > raise URLError(err) > E URLError: <urlopen error [SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:579)> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-402) Release Kiali Python 0.4.6 to support Certificates and update the documentation

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-402?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-402. ------------------------------------------- Resolution: Done > Release Kiali Python 0.4.6 to support Certificates and update the documentation > ------------------------------------------------------------------------------- > > Key: SWSQE-402 > URL: https://issues.jboss.org/browse/SWSQE-402 > Project: Kiali QE > Issue Type: QE Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > Kiali Python Client needs to be updated in order to support SSL -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-402) Release Kiali Python 0.4.6 to support Certificates and update the documentation

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-402?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-402: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Release Kiali Python 0.4.6 to support Certificates and update the documentation > ------------------------------------------------------------------------------- > > Key: SWSQE-402 > URL: https://issues.jboss.org/browse/SWSQE-402 > Project: Kiali QE > Issue Type: QE Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > Kiali Python Client needs to be updated in order to support SSL -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-402) Release Kiali Python 0.4.6 to support Certificates and update the documentation

by Guilherme Baufaker Rêgo (JIRA)

Guilherme Baufaker Rêgo created SWSQE-402: --------------------------------------------- Summary: Release Kiali Python 0.4.6 to support Certificates and update the documentation Key: SWSQE-402 URL: https://issues.jboss.org/browse/SWSQE-402 Project: Kiali QE Issue Type: QE Task Reporter: Guilherme Baufaker Rêgo Assignee: Michael Foley Kiali Python Client needs to be updated in order to support SSL -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2951) Unable to debug drools file with eclipse

by raghu thota (JIRA)

raghu thota created DROOLS-2951: ----------------------------------- Summary: Unable to debug drools file with eclipse Key: DROOLS-2951 URL: https://issues.jboss.org/browse/DROOLS-2951 Project: Drools Issue Type: Feature Request Reporter: raghu thota Assignee: Mario Fusco I am trying to debug a .drl file using Eclipse mars (version Mars.2 Release (4.5.2)) and drools version 5.5.0.FINAL. I have added drools runtime. After running the Junit test as "Debug as Drools Junit test" , I got the following error. An internal error occurred during: "Launching DroolsDummyTest.testHelloWorldRule (1)". org.drools.eclipse.launching.DroolsVMDebugger.renderProcessLabel([Ljava/lang/String;)Ljava/lang/String; This is the problem with incompatibility of drools and eclipse. I am able to debug other drools (version 5.5.0.FINAL) applications using Eclipse Helios. But, My current project is written in Java 7 which is not supported by Helios. I am referring the link : http://docs.jboss.org/drools/release/5.5.0.Final/drools-expert-docs/html/... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2876) Data Type list icons - visual design

by Guilherme Carreiro (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2876?page=com.atlassian.jira.plugi... ] Guilherme Carreiro commented on DROOLS-2876: -------------------------------------------- [~mstevens1] I'm able to apply the icons above with CSS :-) > Data Type list icons - visual design > ------------------------------------ > > Key: DROOLS-2876 > URL: https://issues.jboss.org/browse/DROOLS-2876 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Brian Dellascio > Labels: UX, UXTeam, VisualDesign, drools-tools > Attachments: Screen Shot 2018-08-10 at 9.22.23 AM.png > > > DMN Data Types dialog uses the following PF pattern: https://www.patternfly.org/pattern-library/content-views/tree-list-view/. As such it includes a list. We need list icons for two types of list items: > - Simple custom Data Types (basically means not nested date types) > - Structured custom Data Types (basically means nested data types) > Design documented in detail at: https://issues.jboss.org/browse/DROOLS-2787 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2950) [DMN Editor] Custom data-types - ItemDefinitionRecordEngine - The QName instance should lookup the real prefix from the URI

by Guilherme Carreiro (JIRA)

Guilherme Carreiro created DROOLS-2950: ------------------------------------------ Summary: [DMN Editor] Custom data-types - ItemDefinitionRecordEngine - The QName instance should lookup the real prefix from the URI Key: DROOLS-2950 URL: https://issues.jboss.org/browse/DROOLS-2950 Project: Drools Issue Type: Bug Components: DMN Editor Reporter: Guilherme Carreiro Assignee: Guilherme Carreiro -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2018