February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2455) Fibers use ForkJoinPool by default

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2455?page=com.atlassian.jira.plugin... ] Bela Ban deleted JGRP-2455: --------------------------- > Fibers use ForkJoinPool by default > ---------------------------------- > > Key: JGRP-2455 > URL: https://issues.redhat.com/browse/JGRP-2455 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > > Fibers are currently created with {{Thread.builder().virtual().task(t).name(name).build()}} > This uses the ForkJoinPool. See if changing this to thread_pool help; this pool is configurable via XML. > Run perftest to see if handling messages and scheduling threads on the same pool cause a perf degradation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2455) Fibers use ForkJoinPool by default

by Bela Ban (Jira)

Bela Ban created JGRP-2455: ------------------------------ Summary: Fibers use ForkJoinPool by default Key: JGRP-2455 URL: https://issues.redhat.com/browse/JGRP-2455 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.0, 4.2.1 Fibers are currently created with {{Thread.builder().virtual().task(t).name(name).build()}} This uses the ForkJoinPool. See if changing this to thread_pool help; this pool is configurable via XML. Run perftest to see if handling messages and scheduling threads on the same pool cause a perf degradation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4963) [DMN Designer] Type designer does not show save/cancel when many constraints are presents and the inspector is open

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4963?page=com.atlassian.jira.plug... ] Elizabeth Clayton reassigned DROOLS-4963: ----------------------------------------- Assignee: Toni Rikkola (was: Guilherme Gomes) > [DMN Designer] Type designer does not show save/cancel when many constraints are presents and the inspector is open > ------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4963 > URL: https://issues.redhat.com/browse/DROOLS-4963 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.32.0.Final > Reporter: Edoardo Vacchi > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2020-01-22 16-16-29.png > > > hiding the inspector on the right-hand side uncovers the save/cancel buttons > !Screenshot from 2020-01-22 16-16-29.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5106) Local/Internal Maven Repos can not be accessed

by Alexandre Bakos (Jira)

[ https://issues.redhat.com/browse/DROOLS-5106?page=com.atlassian.jira.plug... ] Alexandre Bakos commented on DROOLS-5106: ----------------------------------------- thank you for the report, but we need a better description of the environment setup and steps to reproduce. > Local/Internal Maven Repos can not be accessed > ---------------------------------------------- > > Key: DROOLS-5106 > URL: https://issues.redhat.com/browse/DROOLS-5106 > Project: Drools > Issue Type: Bug > Components: Artifact Repository > Affects Versions: 7.33.0.Final > Reporter: Steve Davidson > Assignee: Alexandre Bakos > Priority: Major > Labels: Drools, drools-compiler, maven > > Attempting to use an internal Nexus Repository, unable to load Drools KIE Modules using Maven. This works with 7.29.Final. Changing to 7.33.Final fails with the following stack trace; > {code:java} > WARNING: Environment variable M2_HOME is not set > Feb 24, 2020 5:12:30 PM org.kie.server.services.impl.KieServerImpl createContainer > SEVERE: Error creating container 'JUnit Test: kie-server' for module 'com.j2eeguys.demo:KieIssueDemo:0.1.0-SNAPSHOT' > java.lang.RuntimeException: Cannot find KieModule: com.j2eeguys.demo:KieIssueDemo:0.1.0-SNAPSHOT > at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:186) > at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:176) > at org.kie.server.services.impl.KieServerImpl.createContainer(KieServerImpl.java:281) > at org.kie.server.remote.rest.common.resource.KieServerRestImpl.createContainer(KieServerRestImpl.java:157) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:140) > at org.jboss.resteasy.core.ResourceMethodInvoker.internalInvokeOnTarget(ResourceMethodInvoker.java:509) > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTargetAfterFilter(ResourceMethodInvoker.java:399) > at org.jboss.resteasy.core.ResourceMethodInvoker.lambda$invokeOnTarget$0(ResourceMethodInvoker.java:363) > at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:358) > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:365) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:337) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:310) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:443) > at org.jboss.resteasy.core.SynchronousDispatcher.lambda$invoke$4(SynchronousDispatcher.java:233) > at org.jboss.resteasy.core.SynchronousDispatcher.lambda$preprocess$0(SynchronousDispatcher.java:139) > at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:358) > at org.jboss.resteasy.core.SynchronousDispatcher.preprocess(SynchronousDispatcher.java:142) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:219) > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:227) > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at org.eclipse.jetty.servlet.ServletHolder$NotAsyncServlet.service(ServletHolder.java:1401) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:760) > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) > at org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:226) > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) > at org.kie.server.services.impl.security.web.CaptureHttpRequestFilter.doFilter(CaptureHttpRequestFilter.java:42) > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1596) > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:545) > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:501) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) > at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235) > at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1592) > at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233) > at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1296) > at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188) > at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:485) > at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1562) > at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186) > at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1211) > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:221) > at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) > at org.eclipse.jetty.server.Server.handle(Server.java:500) > at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:386) > at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:562) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:378) > at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:270) > at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) > at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117) > at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336) > at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313) > at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171) > at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129) > at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:388) > at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:806) > at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:938) > at java.base/java.lang.Thread.run(Thread.java:834) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-1006) JASPIC module's initialize() is called multiple times

by Ricardo Martin Camarero (Jira)

[ https://issues.redhat.com/browse/SECURITY-1006?page=com.atlassian.jira.pl... ] Ricardo Martin Camarero closed SECURITY-1006. --------------------------------------------- Resolution: Explained Security project is no longer active. > JASPIC module's initialize() is called multiple times > ----------------------------------------------------- > > Key: SECURITY-1006 > URL: https://issues.redhat.com/browse/SECURITY-1006 > Project: PicketBox > Issue Type: Bug > Components: PicketBox > Affects Versions: PicketBox_5_0_3.Beta1 > Reporter: Hisanobu Okuda > Assignee: Ricardo Martin Camarero > Priority: Major > Attachments: reproducer.tar.gz > > > JASPIC module's initialize() is called multiple times. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-1006) JASPIC module's initialize() is called multiple times

by Ricardo Martin Camarero (Jira)

[ https://issues.redhat.com/browse/SECURITY-1006?page=com.atlassian.jira.pl... ] Ricardo Martin Camarero commented on SECURITY-1006: --------------------------------------------------- [~hisanobu.okuda] Security issues are no longer managed here. It's a closed project. We'll manage the JBEAP/WFLY jiras instead. Closing this one. > JASPIC module's initialize() is called multiple times > ----------------------------------------------------- > > Key: SECURITY-1006 > URL: https://issues.redhat.com/browse/SECURITY-1006 > Project: PicketBox > Issue Type: Bug > Components: PicketBox > Affects Versions: PicketBox_5_0_3.Beta1 > Reporter: Hisanobu Okuda > Assignee: Ricardo Martin Camarero > Priority: Major > Attachments: reproducer.tar.gz > > > JASPIC module's initialize() is called multiple times. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4584) Scrolling during editing mode move cell in new position on the screen

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4584?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4584: ------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) (was: 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10)) > Scrolling during editing mode move cell in new position on the screen > --------------------------------------------------------------------- > > Key: DROOLS-4584 > URL: https://issues.redhat.com/browse/DROOLS-4584 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.28.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Major > Labels: CustomerFocus, drools-tools > Attachments: ScrollIssue.webm, image-2019-10-01-11-24-36-774.png > > > !image-2019-10-01-11-24-36-774.png|thumbnail! > Cell moves unexpectedly in editing mode > {color:red}*Failure*{color} > If you start edit any cell of a big grid and then scroll the input would move not in the right cell. > *Expected* > Input element moves with entire table -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4991) Minor changes on Collection Editor UI

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4991?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4991: ------------------------------- Sprint: (was: 2020 Week 07-09 (from Feb 10)) > Minor changes on Collection Editor UI > ------------------------------------- > > Key: DROOLS-4991 > URL: https://issues.redhat.com/browse/DROOLS-4991 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Attachments: AddItem.webm, parent toggle.webm, unwrapped.webm > > > - When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list. > - Consider renaming the action to "Add list value" or whatever most closely describes the action. > - Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, but the "Add new item" looks about right. > https://issues.redhat.com/secure/thumbnail/12464511/_thumb_12464511.png > - Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo. > Thanks! > Liz -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1076) Automate Codes: https://github.com/kiali/kiali/pull/2275/

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1076?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1076: --------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/254 > Automate Codes: https://github.com/kiali/kiali/pull/2275/ > --------------------------------------------------------- > > Key: SWSQE-1076 > URL: https://issues.redhat.com/browse/SWSQE-1076 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Also automate: > "No matching workload found for authorization policy selector in this namespace" > "This subset is already referenced in another route destination" > "Destination field is mandatory" > "Unable to verify the validity, cross-namespace validation is not supported for this field" -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1070) Automate AuthPolicy https://github.com/kiali/kiali/pull/2261

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1070?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1070: --------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/254 > Automate AuthPolicy https://github.com/kiali/kiali/pull/2261 > ------------------------------------------------------------ > > Key: SWSQE-1070 > URL: https://issues.redhat.com/browse/SWSQE-1070 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

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 February 2020