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

5 months, 3 weeks

2
3
0 / 0

[JBoss JIRA] (WFLY-10796) Warning about JSF version 'NONE' is shown in logs

by Jan Kašík (JIRA)

[ https://issues.jboss.org/browse/WFLY-10796?page=com.atlassian.jira.plugin... ] Jan Kašík updated WFLY-10796: ----------------------------- Description: Following warning is shown in log upon server start: {code} 2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead. {code} Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present. From my point of view, it seems like I am trying set slot 'NONE' to be the default. But nothing like that is happening. was: Following warning is shown in log upon server start: {code} 2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead. {code} Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present. > Warning about JSF version 'NONE' is shown in logs > -------------------------------------------------- > > Key: WFLY-10796 > URL: https://issues.jboss.org/browse/WFLY-10796 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 14.0.0.Beta2 > Reporter: Jan Kašík > Assignee: Dmitrii Tikhomirov > > Following warning is shown in log upon server start: > {code} > 2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead. > {code} > Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present. From my point of view, it seems like I am trying set slot 'NONE' to be the default. But nothing like that is happening. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 months, 2 weeks

2
1
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)

6 months, 2 weeks

2
1
0 / 0

[JBoss JIRA] (DROOLS-4849) SudokuExample cannot solve hard samples any more in Drools 7

by Didier Loiseau (Jira)

Didier Loiseau created DROOLS-4849: -------------------------------------- Summary: SudokuExample cannot solve hard samples any more in Drools 7 Key: DROOLS-4849 URL: https://issues.redhat.com/browse/DROOLS-4849 Project: Drools Issue Type: Bug Affects Versions: 7.30.0.Final Reporter: Didier Loiseau Assignee: Mario Fusco It appears {{SudokuExample}} is capable to resolve the Simple and Medium samples, but none of the Hard ones. They resolve a few cells but end with {quote} Sorry - can't solve this grid. {quote} in the console. With explain = true, I can see that the "single" and "hidden single" rules fire (not always both, depends on the puzzle), but clearly when it stops, at least the latter should still fire for some cells. There is also a small bug in the code, which is that the {{unsolvable}} flag is not reset during setup, so when you get the above error you also get it for any other example you solve afterwards. I have checked with Drools 6.5.0.Final (checked out the examples from GitHub) and the solver works fine. The Sudoku example appears to be mostly the same though. I am running the examples with Java 8 from IntelliJ or command line, if that matters. I tested this on 2 different machines. It is a bit unfortunate because it is the first example in the GUI. Full console output for sample Hard 1: {code} 12:14:28.256 [main] INFO o.d.c.k.b.impl.ClasspathKieProject.notifyKieModuleFound:133 - Found kmodule: file:/C:/Users/Public/Documents/projects/drools/drools-examples/target/classes/META-INF/kmodule.xml 12:14:30.424 [main] WARN o.d.c.k.b.impl.ClasspathKieProject.getPomPropertiesFromFileSystem:322 - Unable to find pom.properties in /C:/Users/Public/Documents/projects/drools/drools-examples/target/classes 12:14:30.475 [main] INFO o.d.c.k.b.impl.ClasspathKieProject.generatePomPropertiesFromPom:354 - Recursed up folders, found and used pom.xml C:\Users\Public\Documents\projects\drools\drools-examples\pom.xml 12:14:42.619 [AWT-EventQueue-0] WARN o.d.c.k.builder.impl.KieBuilderImpl.packageNameForFile:394 - File 'org/drools/games/wumpus/server/paintCave.drl' is in folder 'org/drools/games/wumpus/server' but declares package 'org.drools.games.wumpus.server.view'. It is advised to have a correspondance between package and folder names. 12:14:42.632 [AWT-EventQueue-0] WARN o.d.c.k.builder.impl.KieBuilderImpl.packageNameForFile:394 - File 'org/drools/games/wumpus/server/paintSensor.drl' is in folder 'org/drools/games/wumpus/server' but declares package 'org.drools.games.wumpus.server.view'. It is advised to have a correspondance between package and folder names. 12:14:42.687 [AWT-EventQueue-0] WARN o.d.c.k.builder.impl.KieBuilderImpl.packageNameForFile:394 - File 'org/drools/games/wumpus/server/ui.drl' is in folder 'org/drools/games/wumpus/server' but declares package 'org.drools.games.wumpus.server.view'. It is advised to have a correspondance between package and folder names. Validation complete. Col: 0 Col: 1 Col: 2 Col: 3 Col: 4 Col: 5 Col: 6 Col: 7 Col: 8 Row 0: 2 4 7 9 2 4 6 4 67 9 23 6 9 --- 5 --- --- 1 --- 3 67 9 --- 8 --- 4 67 Row 1: 12 7 9 --- 8 --- 1 67 9 23 6 9 --- 4 --- 23 6 1 3 67 9 3 67 9 --- 5 --- Row 2: 1 4 9 1 456 --- 3 --- 6 89 --- 7 --- 6 8 --- 2 --- 4 6 9 1 4 6 Row 3: 1234 1234 1 4 1 5 8 --- 6 --- 5 78 5 7 45 7 --- 9 --- Row 4: --- 6 --- --- 7 --- --- 5 --- --- 4 --- --- 2 --- --- 9 --- --- 8 --- --- 1 --- --- 3 --- Row 5: --- 8 --- 12 4 1 4 9 1 5 --- 3 --- 5 7 567 4567 2 4 67 Row 6: 1 3 7 1 3 6 --- 2 --- 3 56 --- 8 --- 3 56 --- 4 --- 3 567 9 1 67 Row 7: --- 5 --- 1 34 6 1 4 678 3 6 --- 9 --- 34 6 1 3 67 --- 2 --- 1 678 Row 8: 34 --- 9 --- 4 6 8 --- 7 --- --- 1 --- 23456 3 56 3 56 6 8 Sorry - can't solve this grid. {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 months, 2 weeks

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

11 months, 2 weeks

3
10
0 / 0

[JBoss JIRA] (WFLY-12461) Can't use smallrye-health without weld extension

by Florian Sailer (Jira)

Florian Sailer created WFLY-12461: ------------------------------------- Summary: Can't use smallrye-health without weld extension Key: WFLY-12461 URL: https://issues.jboss.org/browse/WFLY-12461 Project: WildFly Issue Type: Bug Components: MP Health Affects Versions: 17.0.1.Final Reporter: Florian Sailer Assignee: Jeff Mesnil Since this commit in the smallrye implementation it was possible to use smallrye without CDI. https://github.com/smallrye/smallrye-health/commit/a6a7812877d74d2c3f5b29... I'm trying to migrate from Wildfly 15.0.1-Final to 17.0.1-Final, where the smallrye-health extension unfortunately needs weld to startup. It's not possbible for me to activate weld on my sever, because there are some problems using the org.apache.cxf.jaxrs framework with weld. I am getting the following exception while starting: 14:16:04,960 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=microprofile-health-smallrye' are not available: org.wildfly.weld; There are no known registration points which can provide this capability. -- This message was sent by Atlassian Jira (v7.13.5#713005)

12 months

3
2
0 / 0

[JBoss JIRA] (DROOLS-3944) DMN Editor: Data type usability study

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3944?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3944: -------------------------------------- Sprint: 2019 Week 23-25 > DMN Editor: Data type usability study > ------------------------------------- > > Key: DROOLS-3944 > URL: https://issues.jboss.org/browse/DROOLS-3944 > Project: Drools > Issue Type: Task > Components: DMN Editor > Environment: Version 7.4 > Reporter: Elizabeth Clayton > Assignee: Sarahjane Clark > Priority: Major > Labels: UX, UXTeam, Usability, drools-tools > > Lightweight usability study to test the ease of use in viewing, creating, editing and deleting data types, particularly structured data types. > GOALS: Access the Data Type editor in terms of productivity and usability. > * Ease of use when creating a complex type (concern: minimizing the mouse usage.) > * Ease of use when saving a basic data type (e.g. age: number) > * Discoverability of actions in the kebab menu, especially, insert nested, delete. > * Ease of use/accuracy: Type-ahead of the data type selector. -- This message was sent by Atlassian Jira (v7.12.1#712002)

1 year, 7 months

2
1
0 / 0

[Red Hat JIRA] (WFCORE-5294) Upgrade Jandex to 2.2.3.Final

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5294?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-5294: ------------------------------------- Description: https://github.com/wildfly/jandex/compare/2.1.4...2.2.3.Final With this release I no longer see the WFCORE-5295 problem. was: https://github.com/wildfly/jandex/compare/2.1.4...2.2.3.Final With this release I no longer see the WFLY-14044 problem. > Upgrade Jandex to 2.2.3.Final > ----------------------------- > > Key: WFCORE-5294 > URL: https://issues.redhat.com/browse/WFCORE-5294 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > https://github.com/wildfly/jandex/compare/2.1.4...2.2.3.Final > With this release I no longer see the WFCORE-5295 problem. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5295) Indexing org.postgresq.jdbc.PgConnection$1 fails

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5295?page=com.atlassian.jira.plug... ] Brian Stansberry moved WFLY-14044 to WFCORE-5295: ------------------------------------------------- Key: WFCORE-5295 (was: WFLY-14044) Affects Version/s: 14.0.1.Final (was: 18.0.0.Final) Project: WildFly Core (was: WildFly) > Indexing org.postgresq.jdbc.PgConnection$1 fails > ------------------------------------------------ > > Key: WFCORE-5295 > URL: https://issues.redhat.com/browse/WFCORE-5295 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 14.0.1.Final > Reporter: Tobias Stadler > Assignee: Brian Stansberry > Priority: Major > > If I package postgresql-42.2.18.jar in a war, jandex fails to index it: > {code:java} > 09:15:26,059 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0003: Could not index class org/postgresql/jdbc/PgConnection$1.class at /content/foo.war/WEB-INF/lib/postgresql-42.2.18.jar: java.lang.IllegalStateException: Required class information is missing09:15:26,059 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0003: Could not index class org/postgresql/jdbc/PgConnection$1.class at /content/foo.war/WEB-INF/lib/postgresql-42.2.18.jar: java.lang.IllegalStateException: Required class information is missing at org.jboss.jandex.Indexer.rebuildNestedType(Indexer.java:926) at org.jboss.jandex.Indexer.resolveTypePath(Indexer.java:786) at org.jboss.jandex.Indexer.resolveTypeAnnotation(Indexer.java:705) at org.jboss.jandex.Indexer.resolveTypeAnnotations(Indexer.java:613) at org.jboss.jandex.Indexer.index(Indexer.java:1602) at org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:99) at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363) at java.lang.Thread.run(Thread.java:748){code} -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-14044) Indexing org.postgresq.jdbc.PgConnection$1 fails

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14044?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-14044: ----------------------------------------- I'm going to move this to WFCORE as that's where the relevant code is. > Indexing org.postgresq.jdbc.PgConnection$1 fails > ------------------------------------------------ > > Key: WFLY-14044 > URL: https://issues.redhat.com/browse/WFLY-14044 > Project: WildFly > Issue Type: Bug > Affects Versions: 18.0.0.Final > Reporter: Tobias Stadler > Assignee: Brian Stansberry > Priority: Major > > If I package postgresql-42.2.18.jar in a war, jandex fails to index it: > {code:java} > 09:15:26,059 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0003: Could not index class org/postgresql/jdbc/PgConnection$1.class at /content/foo.war/WEB-INF/lib/postgresql-42.2.18.jar: java.lang.IllegalStateException: Required class information is missing09:15:26,059 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0003: Could not index class org/postgresql/jdbc/PgConnection$1.class at /content/foo.war/WEB-INF/lib/postgresql-42.2.18.jar: java.lang.IllegalStateException: Required class information is missing at org.jboss.jandex.Indexer.rebuildNestedType(Indexer.java:926) at org.jboss.jandex.Indexer.resolveTypePath(Indexer.java:786) at org.jboss.jandex.Indexer.resolveTypeAnnotation(Indexer.java:705) at org.jboss.jandex.Indexer.resolveTypeAnnotations(Indexer.java:613) at org.jboss.jandex.Indexer.index(Indexer.java:1602) at org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:99) at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363) at java.lang.Thread.run(Thread.java:748){code} -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

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