September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4428) Port DROOLS-4188 to Kogito

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-4428?page=com.atlassian.jira.plugi... ] Luca Molteni updated DROOLS-4428: --------------------------------- Sprint: 2019 Week 35-37 > Port DROOLS-4188 to Kogito > -------------------------- > > Key: DROOLS-4428 > URL: https://issues.jboss.org/browse/DROOLS-4428 > Project: Drools > Issue Type: Task > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4429) Port 4375 to Kogito

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-4429?page=com.atlassian.jira.plugi... ] Luca Molteni updated DROOLS-4429: --------------------------------- Sprint: 2019 Week 35-37 > Port 4375 to Kogito > ------------------- > > Key: DROOLS-4429 > URL: https://issues.jboss.org/browse/DROOLS-4429 > Project: Drools > Issue Type: Task > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4497) Failed to create new column inside Guided Decision Table

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-4497?page=com.atlassian.jira.plugi... ] Toni Rikkola commented on DROOLS-4497: -------------------------------------- I could use the steps you did when the column was created. What field and so on. > Failed to create new column inside Guided Decision Table > -------------------------------------------------------- > > Key: DROOLS-4497 > URL: https://issues.jboss.org/browse/DROOLS-4497 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Environment: jbpm-server-distribution-7.26.0.Final-dist > Reporter: Gabriele Cardosi > Assignee: Toni Rikkola > Priority: Major > Attachments: Person.java, PersonGDT.gdst > > > # Created "Person" data object with three field [^Person.java] . > # Created "PersonGDT" guided decision table with wizard (hit policy "none", "Limited entry" type). [^PersonGDT.gdst] > # Trying to insert new column: ""Unexpected error" when click "Finish" button. > # Can not proceed further. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBEE-229) Release JBoss / Jakrta JACC 2.0.0.CR3

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/JBEE-229?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved JBEE-229. ----------------------------------- Resolution: Done > Release JBoss / Jakrta JACC 2.0.0.CR3 > ------------------------------------- > > Key: JBEE-229 > URL: https://issues.jboss.org/browse/JBEE-229 > Project: JBoss Enterprise Spec APIs > Issue Type: Task > Components: jboss-jacc-api > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: jboss-jakarta-jacc-api_spec-2.0.0.CR3 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4497) Failed to create new column inside Guided Decision Table

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-4497?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-4497: --------------------------------- Tester: Jozef Marko > Failed to create new column inside Guided Decision Table > -------------------------------------------------------- > > Key: DROOLS-4497 > URL: https://issues.jboss.org/browse/DROOLS-4497 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Environment: jbpm-server-distribution-7.26.0.Final-dist > Reporter: Gabriele Cardosi > Assignee: Toni Rikkola > Priority: Major > Attachments: Person.java, PersonGDT.gdst > > > # Created "Person" data object with three field [^Person.java] . > # Created "PersonGDT" guided decision table with wizard (hit policy "none", "Limited entry" type). [^PersonGDT.gdst] > # Trying to insert new column: ""Unexpected error" when click "Finish" button. > # Can not proceed further. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4497) Failed to create new column inside Guided Decision Table

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-4497?page=com.atlassian.jira.plugi... ] Toni Rikkola reassigned DROOLS-4497: ------------------------------------ Assignee: Toni Rikkola (was: Michael Anstis) > Failed to create new column inside Guided Decision Table > -------------------------------------------------------- > > Key: DROOLS-4497 > URL: https://issues.jboss.org/browse/DROOLS-4497 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Environment: jbpm-server-distribution-7.26.0.Final-dist > Reporter: Gabriele Cardosi > Assignee: Toni Rikkola > Priority: Major > Attachments: Person.java, PersonGDT.gdst > > > # Created "Person" data object with three field [^Person.java] . > # Created "PersonGDT" guided decision table with wizard (hit policy "none", "Limited entry" type). [^PersonGDT.gdst] > # Trying to insert new column: ""Unexpected error" when click "Finish" button. > # Can not proceed further. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

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

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2360?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2360: -------------------------------- Hi [~dklosek] Daniel, thanks for the PR! I applied it and released 3.6.19.Final to maven. Cheers, > 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: 3.6.18, 4.1.1 > Environment: JGroups-4.1.1-Final > Red Hat 4.4.7-23 > JDK 1.8.0_202 > Reporter: Daniel Klosinski > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.2 > > 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} > Running such loop I am getting dead look after a few loop iterations. In the attached logs program hanged after 3 iterations > 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 which handles RELEASE_LOCK_OK from the coordinator and this is why we have a race condition here. Here is a sequence which leads to deadlock: > 1. Create client lock (lock_id=2) > 2. Send GRANT_LOCK (lock_id=2) to coordinator > 3. Receive LOCK_GRANTED (lock_id=2) from coordinator > 4. Send RELEASE_LOCK (lock_id=2) to coordinator > 5. Call look() method in the same thread (new client lock won't be created as there is an existing entry in the client lock table for this owner) > 6. Receive RELEASE_LOCK_OK and delete client lock from client lock table. > 7. Send GRANT_LOCK (lock_id=2) to coordinator > 8. Receive LOCK_GRANTED (lock_id=2) from coordinator > 9. No entry in the client lock table. It's not possible to get the thread which needs to be notified. > I am attaching a simple program which can be used to reproduce and generated logs. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2376) Backport of JFRP-2364 to the 3.6 branch

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2376?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2376. ---------------------------- Resolution: Done > Backport of JFRP-2364 to the 3.6 branch > --------------------------------------- > > Key: JGRP-2376 > URL: https://issues.jboss.org/browse/JGRP-2376 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 3.6.19 > > > Backport of [1] to the 3.6 branch > [1] https://issues.jboss.org/browse/JGRP-2364 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4497) Failed to create new column inside Guided Decision Table

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4497?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-4497: ------------------------------------- Description: # Created "Person" data object with three field [^Person.java] . # Created "PersonGDT" guided decision table with wizard (hit policy "none", "Limited entry" type). [^PersonGDT.gdst] # Trying to insert new column: ""Unexpected error" when click "Finish" button. # Can not proceed further. was:Created "Person" data object with three fiel. Created "PersonGDT" guided decision table with wizard (hit policy "none", "Limited entry" type). Trying to insert new column: ""Unexpected error" when click "Finish" button. Can not proceed further. > Failed to create new column inside Guided Decision Table > -------------------------------------------------------- > > Key: DROOLS-4497 > URL: https://issues.jboss.org/browse/DROOLS-4497 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Environment: jbpm-server-distribution-7.26.0.Final-dist > Reporter: Gabriele Cardosi > Assignee: Michael Anstis > Priority: Major > Attachments: Person.java, PersonGDT.gdst > > > # Created "Person" data object with three field [^Person.java] . > # Created "PersonGDT" guided decision table with wizard (hit policy "none", "Limited entry" type). [^PersonGDT.gdst] > # Trying to insert new column: ""Unexpected error" when click "Finish" button. > # Can not proceed further. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4497) Failed to create new column inside Guided Decision Table

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4497?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-4497: ------------------------------------- Attachment: PersonGDT.gdst > Failed to create new column inside Guided Decision Table > -------------------------------------------------------- > > Key: DROOLS-4497 > URL: https://issues.jboss.org/browse/DROOLS-4497 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Environment: jbpm-server-distribution-7.26.0.Final-dist > Reporter: Gabriele Cardosi > Assignee: Michael Anstis > Priority: Major > Attachments: Person.java, PersonGDT.gdst > > > Created "Person" data object with three fiel. Created "PersonGDT" guided decision table with wizard (hit policy "none", "Limited entry" type). Trying to insert new column: ""Unexpected error" when click "Finish" button. Can not proceed further. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 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 September 2019