December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3455) Reduce unnecessary lambda usage

by David Lloyd (JIRA)

David Lloyd created WFCORE-3455: ----------------------------------- Summary: Reduce unnecessary lambda usage Key: WFCORE-3455 URL: https://issues.jboss.org/browse/WFCORE-3455 Project: WildFly Core Issue Type: Task Reporter: David Lloyd Assignee: David Lloyd Fix For: 4.0.0.Alpha5 Lambdas chew up a lot of resources and we use a lot of them. Eliminate whenever possible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1461) Java 9: Eliminate reflection warning from security manager

by David Lloyd (JIRA)

David Lloyd created ELY-1461: -------------------------------- Summary: Java 9: Eliminate reflection warning from security manager Key: ELY-1461 URL: https://issues.jboss.org/browse/ELY-1461 Project: WildFly Elytron Issue Type: Task Components: Security Manager Reporter: David Lloyd Assignee: David Lloyd Java 9 does not take kindly to our invasive reflection into AccessControlContext; also, if the implementation happens to not have the same fields, we fail to start the entire application server. Our enhanced debug output is nice but for now this should be changed to be Java 9-safe. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9598) Clustering Testsuite 2.0: CLI, no ant, no XSLT, 3-node DIST testing

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9598?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9598: --------------------------------- Description: Goals * simplify test development * make the testsuite manageable again * lower execution time Steps to take * move the testsuite away from using XSLT and just rely on the CLI scripts * provide utility for configuring servers using CLI was: Goals * simplify test development * make the testsuite manageable again Steps to take * move the testsuite away from using XSLT and just rely on the CLI scripts * provide utility for configuring servers using CLI > Clustering Testsuite 2.0: CLI, no ant, no XSLT, 3-node DIST testing > ------------------------------------------------------------------- > > Key: WFLY-9598 > URL: https://issues.jboss.org/browse/WFLY-9598 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 12.0.0.Alpha1 > > > Goals > * simplify test development > * make the testsuite manageable again > * lower execution time > Steps to take > * move the testsuite away from using XSLT and just rely on the CLI scripts > * provide utility for configuring servers using CLI -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9598) Clustering Testsuite 2.0: CLI, no ant, no XSLT, 3-node DIST testing

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9598?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9598: --------------------------------- Description: Goals * simplify test development * make the testsuite manageable again Steps to take * move the testsuite away from using XSLT and just rely on the CLI scripts * provide utility for configuring servers using CLI was:For starters, move the testsuite away from using XSLT and just rely on the CLI scripts. > Clustering Testsuite 2.0: CLI, no ant, no XSLT, 3-node DIST testing > ------------------------------------------------------------------- > > Key: WFLY-9598 > URL: https://issues.jboss.org/browse/WFLY-9598 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 12.0.0.Alpha1 > > > Goals > * simplify test development > * make the testsuite manageable again > Steps to take > * move the testsuite away from using XSLT and just rely on the CLI scripts > * provide utility for configuring servers using CLI -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-728) The map backing SimpleMapBackedSecurityRealm should be an identity map not a password map.

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-728?page=com.atlassian.jira.plugin.sy... ] Jan Kalina updated ELY-728: --------------------------- Fix Version/s: 1.2.0.Beta11 (was: 1.2.0.Beta12) > The map backing SimpleMapBackedSecurityRealm should be an identity map not a password map. > ------------------------------------------------------------------------------------------ > > Key: ELY-728 > URL: https://issues.jboss.org/browse/ELY-728 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI, Realms > Affects Versions: 1.2.0.Beta10 > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Priority: Critical > Fix For: 1.2.0.Beta11 > > > This realm is useful in cases where we need an identity to exist where the mechanism has performed validation without requiring access to credentials. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2149) Row and column can be added to read only table

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2149?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2149: ----------------------------------- Sprint: 2017 Week 49-50 > Row and column can be added to read only table > ---------------------------------------------- > > Key: DROOLS-2149 > URL: https://issues.jboss.org/browse/DROOLS-2149 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.4.1.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Fix For: 7.6.0.Final > > > The options for adding row or column into guided decision table are not disabled correctly in special case. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9611) Support messaging export/import-journal for JDBC persistent store

by Erich Duda (JIRA)

Erich Duda created WFLY-9611: -------------------------------- Summary: Support messaging export/import-journal for JDBC persistent store Key: WFLY-9611 URL: https://issues.jboss.org/browse/WFLY-9611 Project: WildFly Issue Type: Feature Request Components: JMS Affects Versions: 11.0.0.Final Reporter: Erich Duda Assignee: Jeff Mesnil Priority: Critical In management model of Wildfly there are operations called import/export-journal which import/export messaging data from/to XML format. These operations are supported only for file based journal and they are not supported for JDBC based journal. This feature is important for migration between persistence solutions and between versions of messaging brokers which use incompatible formats for storing messaging data. XML exported from file based journal has to be able to import to JDBC based journal and vice versa. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9612) Support messaging export/import-journal for JDBC persistent store

by Erich Duda (JIRA)

Erich Duda created WFLY-9612: -------------------------------- Summary: Support messaging export/import-journal for JDBC persistent store Key: WFLY-9612 URL: https://issues.jboss.org/browse/WFLY-9612 Project: WildFly Issue Type: Feature Request Components: JMS Affects Versions: 11.0.0.Final Reporter: Erich Duda Assignee: Jeff Mesnil Priority: Critical In management model of Wildfly there are operations called import/export-journal which import/export messaging data from/to XML format. These operations are supported only for file based journal and they are not supported for JDBC based journal. This feature is important for migration between persistence solutions and between versions of messaging brokers which use incompatible formats for storing messaging data. XML exported from file based journal has to be able to import to JDBC based journal and vice versa. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2175) [Guided Decision Table Graph] Refresh after removal of table

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2175?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3486 to DROOLS-2175: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2175 (was: GUVNOR-3486) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) Affects Version/s: 7.3.0.Final (was: 7.3.0.Final) Fix Version/s: (was: 7.5.0.Final) > [Guided Decision Table Graph] Refresh after removal of table > ------------------------------------------------------------ > > Key: DROOLS-2175 > URL: https://issues.jboss.org/browse/DROOLS-2175 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.3.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Minor > > There are two problem after removal one of linked tables. For more details see Steps to Reproduce. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2174) Deadlock between AbstractWorkingMemory and DefaultAgenda

by Umang Sharma (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2174?page=com.atlassian.jira.plugi... ] Umang Sharma commented on DROOLS-2174: -------------------------------------- This is right from one of our production servers. I don't have a shareable reproducer for this as of now. Would require some work for get to that. Would try and provide it in few days time. For now, I would request you to investigate it from the perspective of the cloned bug. Because the stack traces are exactly same. Also if some workarounds can be suggested that would be great. Another point is that we already have an application level lock in place to ensure that no sessions are created while some rules are getting added/modified. Si is there a way we can bypass the Drools internal locking mechanism? Also I would also like to know any best practices while using stateful sessions. > Deadlock between AbstractWorkingMemory and DefaultAgenda > -------------------------------------------------------- > > Key: DROOLS-2174 > URL: https://issues.jboss.org/browse/DROOLS-2174 > Project: Drools > Issue Type: Bug > Affects Versions: 5.5.0.Final > Reporter: Umang Sharma > Assignee: Mario Fusco > Fix For: 6.0.0.CR2 > > > I am getting a similar deadlock as the one in the cloned issue. We are using following dependencies: > <dependency> > <groupId>org.drools</groupId> > <artifactId>drools-templates</artifactId> > <version>$ > {runtime.version}</version> > </dependency> > <dependency> > <groupId>org.kie</groupId> > <artifactId>kie-api</artifactId> > <version>${runtime.version} > </version> > </dependency> > <dependency> > <groupId>org.drools</groupId> > <artifactId>drools-core</artifactId> > <version>$ > {runtime.version}</version> > </dependency> > <dependency> > <groupId>org.drools</groupId> > <artifactId>drools-compiler</artifactId> > <version>${runtime.version} > </version> > </dependency> > runtime.version = 6.5.0-Final > I have around 50 off threads stuck in a deadlock. 49 of them are having following stack trace: > "THREAD-4" #124 prio=5 os_prio=0 tid=0x00000000015fc800 nid=0x3a5d waiting on condition [0x00007fc773e7b000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > parking to wait for <0x000000074d189818> (a java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:967) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1283) > at java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.lock(ReentrantReadWriteLock.java:727) > at org.drools.core.impl.KnowledgeBaseImpl.readLock(KnowledgeBaseImpl.java:703) > at org.drools.core.impl.KnowledgeBaseImpl.newStatefulSession(KnowledgeBaseImpl.java:1434) > at org.drools.core.impl.KnowledgeBaseImpl.newStatefulSession(KnowledgeBaseImpl.java:1422) > at org.drools.core.impl.KnowledgeBaseImpl.newStatefulKnowledgeSession(KnowledgeBaseImpl.java:308) > at org.drools.core.impl.KnowledgeBaseImpl.newKieSession(KnowledgeBaseImpl.java:385) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:693) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:629) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:611) > And one of them is stuck in the following stack trace: > "THREAD-4" #124 prio=5 os_prio=0 tid=0x00000000015fc800 nid=0x3a5d waiting on condition [0x00007fc773e7b000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > parking to wait for <0x000000074d189818> (a java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:967) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1283) > at java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.lock(ReentrantReadWriteLock.java:727) > at org.drools.core.impl.KnowledgeBaseImpl.readLock(KnowledgeBaseImpl.java:703) > at org.drools.core.impl.KnowledgeBaseImpl.newStatefulSession(KnowledgeBaseImpl.java:1434) > at org.drools.core.impl.KnowledgeBaseImpl.newStatefulSession(KnowledgeBaseImpl.java:1422) > at org.drools.core.impl.KnowledgeBaseImpl.newStatefulKnowledgeSession(KnowledgeBaseImpl.java:308) > at org.drools.core.impl.KnowledgeBaseImpl.newKieSession(KnowledgeBaseImpl.java:385) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:693) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:629) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:611) > Please help us out in fixing this. Its a production system serving millions of users. > PS: This is was reproduced under a medium load where we create 50 stateful sessions in parallel and also some rule were also getting added in the KieContainer at the same time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 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 December 2017