July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1846) Release WildFly Elytron 1.10.0.CR3

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1846?page=com.atlassian.jira.plugin.s... ] Farah Juma resolved ELY-1846. ----------------------------- Resolution: Done > Release WildFly Elytron 1.10.0.CR3 > ---------------------------------- > > Key: ELY-1846 > URL: https://issues.jboss.org/browse/ELY-1846 > Project: WildFly Elytron > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.10.0.CR3 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4566) Upgrade WildFly Elytron to 1.10.0.CR3

by Farah Juma (Jira)

Farah Juma created WFCORE-4566: ---------------------------------- Summary: Upgrade WildFly Elytron to 1.10.0.CR3 Key: WFCORE-4566 URL: https://issues.jboss.org/browse/WFCORE-4566 Project: WildFly Core Issue Type: Component Upgrade Reporter: Farah Juma Assignee: Farah Juma Fix For: 10.0.0.Beta2 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4566) Upgrade WildFly Elytron to 1.10.0.CR3

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFCORE-4566?page=com.atlassian.jira.plugi... ] Farah Juma updated WFCORE-4566: ------------------------------- Component/s: Security > Upgrade WildFly Elytron to 1.10.0.CR3 > ------------------------------------- > > Key: WFCORE-4566 > URL: https://issues.jboss.org/browse/WFCORE-4566 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 10.0.0.Beta2 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2360) DeadLock while acqiring a distributed lock consecutively by the same thread in a loop

by Daniel Klosinski (Jira)

Daniel Klosinski created JGRP-2360: -------------------------------------- Summary: DeadLock while acqiring a distributed lock consecutively by the same thread in a loop Key: JGRP-2360 URL: https://issues.jboss.org/browse/JGRP-2360 Project: JGroups Issue Type: Bug Affects Versions: 4.1.1, 3.6.18 Environment: JGroups-4.1.1-Final Red Hat 4.4.7-23 JDK 1.8.0_202 Reporter: Daniel Klosinski Assignee: Bela Ban Attachments: DLTest.java, DistributedLockRepoducer.zip, log.log Deadlock intermittently happens when trying to acquire a distributed lock by the same VM, consecutively by the same thread in a loop. Here is a code snippet for which this issue can occur : {code} for(String s : list){ Lock lock=lock_service.getLock("test_lock_name"); lock.lock(); //perform bussines logic lock.unlock(); } {code} During the troubleshooting, I found out that lock_id is not being incremented for the new distributed lock. In the first two loop iterations everything was fine. At the third iteration lock_id didn't get increased: {code} 2019-07-15 16:03:32 TRACE CENTRAL_LOCK:163 - svc-2-sps-34594 --> svc-1-sps-4688: GRANT_LOCK[test_lock_name, lock_id=1, owner=svc-2-sps-34594::1] 2019-07-15 16:03:32 TRACE CENTRAL_LOCK:163 - svc-2-sps-34594 <-- svc-1-sps-4688: LOCK_GRANTED[test_lock_name, lock_id=1, owner=svc-2-sps-34594::1, sender=svc-1-sps-4688] 2019-07-15 16:03:32 TRACE CENTRAL_LOCK:163 - svc-2-sps-34594 --> svc-1-sps-4688: RELEASE_LOCK[test_lock_name, lock_id=1, owner=svc-2-sps-34594::1] 2019-07-15 16:03:32 TRACE CENTRAL_LOCK:163 - svc-2-sps-34594 <-- svc-1-sps-4688: RELEASE_LOCK_OK[test_lock_name, lock_id=1, owner=svc-2-sps-34594::1, sender=svc-1-sps-4688] 2019-07-15 16:03:32 TRACE CENTRAL_LOCK:163 - svc-2-sps-34594 --> svc-1-sps-4688: GRANT_LOCK[test_lock_name, lock_id=2, owner=svc-2-sps-34594::1] 2019-07-15 16:03:32 TRACE CENTRAL_LOCK:163 - svc-2-sps-34594 <-- svc-1-sps-4688: LOCK_GRANTED[test_lock_name, lock_id=2, owner=svc-2-sps-34594::1, sender=svc-1-sps-4688] 2019-07-15 16:03:32 TRACE CENTRAL_LOCK:163 - svc-2-sps-34594 --> svc-1-sps-4688: RELEASE_LOCK[test_lock_name, lock_id=2, owner=svc-2-sps-34594::1] 2019-07-15 16:03:32 TRACE CENTRAL_LOCK:163 - svc-2-sps-34594 <-- svc-1-sps-4688: RELEASE_LOCK_OK[test_lock_name, lock_id=2, owner=svc-2-sps-34594::1, sender=svc-1-sps-4688] 2019-07-15 16:03:32 TRACE CENTRAL_LOCK:163 - svc-2-sps-34594 --> svc-1-sps-4688: GRANT_LOCK[test_lock_name, lock_id=2, owner=svc-2-sps-34594::1] 2019-07-15 16:03:32 TRACE CENTRAL_LOCK:163 - svc-2-sps-34594 <-- svc-1-sps-4688: CREATE_LOCK[test_lock_name, owner=svc-2-sps-34594::1, sender=svc-1-sps-4688] 2019-07-15 16:03:32 TRACE CENTRAL_LOCK:163 - svc-2-sps-34594 <-- svc-1-sps-4688: LOCK_GRANTED[test_lock_name, lock_id=2, owner=svc-2-sps-34594::1, sender=svc-1-sps-4688] {code} I've added few extra loggers into Jgroups-4.1.1.Final code and I realized that the second client lock was not removed from the client lock table before the creation of 3rd client lock. The issue lays in below piece of code. Owner consists of address and threadID. If the same thread, on the same VM, creates distributed lock consecutively and if there is an existing entry in the client lock table for the same owner, the new lock won't be created. The old client lock will be used to acquire a new distributed lock : {code} protected synchronized ClientLock getLock(String name, Owner owner, boolean create_if_absent) { Map<Owner,ClientLock> owners=table.get(name); if(owners == null) { if(!create_if_absent) return null; owners=Util.createConcurrentMap(20); Map<Owner,ClientLock> existing=table.putIfAbsent(name,owners); if(existing != null) owners=existing; } ClientLock lock=owners.get(owner); if(lock == null) { if(!create_if_absent) return null; lock=createLock(name, owner); owners.put(owner, lock); } return lock; } {code} I believe that this issue was introduced by the fix for JGRP-2234 and it is caused by the race condition. The logic that deletes client lock from the client lock table is now executed when the client's VM receives RELEASE_LOCK_OK message from the coordinator. Previously this deletion was executed by the thread in which unlock() method was called. Now, it is executed by the separate thread wich handles RELEASE_LOCK_OK from the coordinator and this is why we have a care condition here. I am attaching a simple program which can be used to reproduce and generated logs. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12289) Content.xml not found trying to install from Eclipse marketplace

by Ariel Barboza (Jira)

Ariel Barboza created WFLY-12289: ------------------------------------ Summary: Content.xml not found trying to install from Eclipse marketplace Key: WFLY-12289 URL: https://issues.jboss.org/browse/WFLY-12289 Project: WildFly Issue Type: Bug Components: Server Environment: Eclipse Market place Reporter: Ariel Barboza Assignee: Brian Stansberry Attachments: ErrorLog.PNG, ErrorLog1.PNG When trying to install JBoss tools from eclipse marketplace, it finds the applications needed for installation, when installing, it fails with the following error: https://download.jboss.org/jbosstools/updates/webtools/oxygen/content.xml does not exist Attached are pictures of the errors -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ELY-816) Support for masked passwords in client XML config

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-816?page=com.atlassian.jira.plugin.sy... ] Farah Juma updated ELY-816: --------------------------- Issue Type: Feature Request (was: Task) > Support for masked passwords in client XML config > ------------------------------------------------- > > Key: ELY-816 > URL: https://issues.jboss.org/browse/ELY-816 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: David Lloyd > Assignee: Ashley Abdel-Sayed > Priority: Critical > Fix For: 1.10.0.CR3 > > > We need a way to support masked passwords in the auth configuration file, either as: > * A dedicated masked-password-type XML type > * Adding necessary fields to hashed-password-type > * Adding a modular crypt format > Needs to be supported anywhere passwords are allowed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ELY-1846) Release WildFly Elytron 1.10.0.CR3

by Farah Juma (Jira)

Farah Juma created ELY-1846: ------------------------------- Summary: Release WildFly Elytron 1.10.0.CR3 Key: ELY-1846 URL: https://issues.jboss.org/browse/ELY-1846 Project: WildFly Elytron Issue Type: Release Reporter: Farah Juma Assignee: Farah Juma Fix For: 1.10.0.CR3 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4315) [DMN Designer] Documentation - Download buttons UX

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4315?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4315: ------------------------------------------- Thanks [~karreiro]! This issue potentially also applies to the process designer. Given the target timeframe, should I assume that the short-term solution needs to be specific to the DMN editor? I don't think there's time for a change for process designer as well, correct [~roger.martinez][~tsurdilovic] [~stetson.robinson]? If so, [~karreiro] what's in our purview to change for the dmn editor - toolbar buttons, or just the buttons on the documentation tab? > [DMN Designer] Documentation - Download buttons UX > -------------------------------------------------- > > Key: DROOLS-4315 > URL: https://issues.jboss.org/browse/DROOLS-4315 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: component-1.png, component-2.png, component-3.png > > > h3. Context: > Today users can: > 1) Download the diagram picture by using this component: > !component-1.png|thumbnail! > 2) Download the DMN file by using this component: > !component-2.png|thumbnail! > 3) Print or Download the documentation as PDF by using the *Print* button (into the Documentation tab): > !component-3.png|thumbnail! > 4) Download the documentation as DOC by using the *Download .doc file* button (into the Documentation tab): > !component-3.png|thumbnail! > ---- > h3. Problem: > The "Download" concept is getting confusing for users. > As a user, I want to be able to: > - Download the documentation as a .PDF file > - Download the documentation as a .DOC file > - Print the documentation > ---- > h3. Notice: > This component can be removed (if UX considers that it's necessary): > !component-1.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ELY-867) Masked password support cryptography usage

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-867?page=com.atlassian.jira.plugin.sy... ] Farah Juma updated ELY-867: --------------------------- Fix Version/s: 1.10.0.CR3 > Masked password support cryptography usage > ------------------------------------------ > > Key: ELY-867 > URL: https://issues.jboss.org/browse/ELY-867 > Project: WildFly Elytron > Issue Type: Bug > Components: Passwords > Reporter: Zoran Regvart > Assignee: Ashley Abdel-Sayed > Priority: Major > Fix For: 1.10.0.CR3 > > > I encountered couple of issues with cryptography used for password masking: > * implementation of masked passwords drops initialization vector (IV) randomly generated by the {{javax.crypto.Cipher}} which makes unmasking (decryption) impossible. > * the implementation is using the same algorithm for key derivation and encryption, which is not possible as there is no encryption support in {{javax.crypto.Cipher}} for PKDBF2 family of algorithms, they are supported only in {{javax.crypto.SecretKeyFactory}} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12288) Re-add jboss public maven repos to BOMs and Quickstart's parents

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-12288: -------------------------------------- Summary: Re-add jboss public maven repos to BOMs and Quickstart's parents Key: WFLY-12288 URL: https://issues.jboss.org/browse/WFLY-12288 Project: WildFly Issue Type: Enhancement Components: Quickstarts Reporter: Eduardo Martins Assignee: Eduardo Martins The repositories are still needed, not all dependencies are available in Maven Central -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

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 July 2019