[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)
7 months
[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)
7 months
[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)
1 year
[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, 8 months
[JBoss JIRA] (REMJMX-166) IllegalThreadStateException after idle jmx connection
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/REMJMX-166?page=com.atlassian.jira.plugi... ]
Darran Lofthouse updated REMJMX-166:
------------------------------------
Workaround Description:
Two workarounds are available: -
# Close the connection and recreate if it would be left idle for 60 seconds or more.
# Pass in an Executor within the configuration map using the key 'java.util.concurrent.Executor' this will then be used instead of the Remoting JMX thread management.
Workaround: Workaround Exists
> IllegalThreadStateException after idle jmx connection
> -----------------------------------------------------
>
> Key: REMJMX-166
> URL: https://issues.redhat.com/browse/REMJMX-166
> Project: Remoting JMX
> Issue Type: Bug
> Components: Connection
> Affects Versions: 3.0.2.Final, 3.0.3.Final
> Environment: org.jboss.remotingjmx:remoting-jmx:3.0.3.Final + java8
> Reporter: Märt Bakhoff
> Assignee: Brad Maxwell
> Priority: Blocker
> Attachments: REMJMX-160.jar, REMJMX-166.jar
>
>
> Start wildfly-17.0.1/bin/standalone.sh, then run this code snippet:
> {noformat}
> JMXServiceURL url = new JMXServiceURL("service:jmx:remote+http://127.0.0.1:9990");
> try (JMXConnector connector = new RemotingConnectorProvider().newJMXConnector(url, Collections.emptyMap())) {
> connector.connect();
> MBeanServerConnection beanServer = connector.getMBeanServerConnection();
> RuntimeMXBean bean = ManagementFactory.newPlatformMXBeanProxy(beanServer, ManagementFactory.RUNTIME_MXBEAN_NAME, RuntimeMXBean.class);
> Thread.sleep(70_000);
> System.out.println("uptime: " + bean.getUptime());
> }
> {noformat}
> The following exception is always thrown:
> {noformat}
> Exception in thread "XNIO-1 task-12" java.lang.IllegalThreadStateException
> at java.lang.ThreadGroup.addUnstarted(ThreadGroup.java:867)
> at java.lang.Thread.init(Thread.java:405)
> at java.lang.Thread.init(Thread.java:349)
> at java.lang.Thread.<init>(Thread.java:599)
> at org.jboss.remotingjmx.protocol.v2.ClientExecutorManager$1.newThread(ClientExecutorManager.java:56)
> at java.util.concurrent.ThreadPoolExecutor$Worker.<init>(ThreadPoolExecutor.java:619)
> at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:932)
> at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1378)
> at org.jboss.remotingjmx.protocol.v2.ClientExecutorManager.execute(ClientExecutorManager.java:64)
> at org.jboss.remotingjmx.protocol.v2.ClientCommon$MessageReceiver.handleMessage(ClientCommon.java:118)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> The cause is in org.jboss.remotingjmx.protocol.v2.ClientExecutorManager.<init>. It creates a thread pool with Executors.newCachedThreadPool that has the default keepAliveTime of 60s.
> The thread factory is using a daemon thread group REMOTING_JMX that will self-destruct when the cached thread is terminated.
> The same code works when using older org.jboss.remotingjmx:remoting-jmx:3.0.1.Final. The regression is likely caused by commit https://github.com/jbossas/remoting-jmx/commit/2d6ae6c26da43304b752fc48f1...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5114) Openshift 4.3 Drools 7.34.0-SNAPSHOT
by Massimiliano Dessi (Jira)
Massimiliano Dessi created DROOLS-5114:
------------------------------------------
Summary: Openshift 4.3 Drools 7.34.0-SNAPSHOT
Key: DROOLS-5114
URL: https://issues.redhat.com/browse/DROOLS-5114
Project: Drools
Issue Type: Bug
Reporter: Massimiliano Dessi
Assignee: Massimiliano Dessi
Dockerfile use java-1.8.0-openjdk-headless the project is build using open jdk 1.8 but at the pod startup the following stacktrace is printed in the log and prevent the pod to start correctly
java.lang.UnsupportedClassVersionError: org/drools/cep/Rule_StockAverage302521058AccumulateExpression0Invoker has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:757)
at org.drools.core.rule.JavaDialectRuntimeData$PackageClassLoader.internalDefineClass(JavaDialectRuntimeData.java:617)
at org.drools.core.rule.JavaDialectRuntimeData$PackageClassLoader.fastFindClass(JavaDialectRuntimeData.java:588)
at org.drools.core.rule.JavaDialectRuntimeData$PackageClassLoader.loadClass(JavaDialectRuntimeData.java:565)
at java.lang.ClassLoader.loadClass(ClassLoader.java:352)
at org.drools.core.rule.JavaDialectRuntimeData.wire(JavaDialectRuntimeData.java:459)
at org.drools.core.rule.JavaDialectRuntimeData.wire(JavaDialectRuntimeData.java:450)
at org.drools.core.rule.JavaDialectRuntimeData.wireAll(JavaDialectRuntimeData.java:280)
at org.drools.core.rule.JavaDialectRuntimeData.onBeforeExecute(JavaDialectRuntimeData.java:252)
at org.drools.core.rule.DialectRuntimeRegistry.onBeforeExecute(DialectRuntimeRegistry.java:137)
at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.reloadAll(KnowledgeBuilderImpl.java:1448)
at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.wireAllRules(KnowledgeBuilderImpl.java:927)
at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.buildRules(KnowledgeBuilderImpl.java:2504)
at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.buildPackages(KnowledgeBuilderImpl.java:2428)
at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:106)
at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:98)
at org.drools.compiler.kie.builder.impl.AbstractKieProject.buildKnowledgePackages(AbstractKieProject.java:261)
at org.drools.compiler.kie.builder.impl.AbstractKieModule.buildKnowledgePackages(AbstractKieModule.java:195)
at org.drools.compiler.kie.builder.impl.AbstractKieModule.createKieBase(AbstractKieModule.java:209)
at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(KieContainerImpl.java:407)
at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:375)
at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBaseFromKieSessionModel(KieContainerImpl.java:560)
at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:536)
at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:459)
at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:442)
at org.kie.hacep.consumer.DroolsConsumerHandler.createAndInitializeSessionContextWithoutSnapshot(DroolsConsumerHandler.java:89)
at org.kie.hacep.consumer.DroolsConsumerHandler.initializeKieSessionContext(DroolsConsumerHandler.java:69)
at org.kie.hacep.consumer.DroolsConsumerHandler.<init>(DroolsConsumerHandler.java:57)
at org.kie.hacep.core.infra.consumer.ConsumerController.<init>(ConsumerController.java:33)
at org.kie.hacep.core.Bootstrap.startConsumers(Bootstrap.java:102)
at org.kie.hacep.core.Bootstrap.startEngine(Bootstrap.java:47)
at org.kie.hacep.endpoint.bootstrap.BootstrapListener.initServices(BootstrapListener.java:37)
at org.kie.hacep.endpoint.bootstrap.BootstrapListener.contextInitialized(BootstrapListener.java:33)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4683)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5146)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5114) Hacep on Openshift 4.3 with Drools 7.34.0-SNAPSHOT error on startup
by Massimiliano Dessi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5114?page=com.atlassian.jira.plug... ]
Massimiliano Dessi updated DROOLS-5114:
---------------------------------------
Summary: Hacep on Openshift 4.3 with Drools 7.34.0-SNAPSHOT error on startup (was: Openshift 4.3 Drools 7.34.0-SNAPSHOT)
> Hacep on Openshift 4.3 with Drools 7.34.0-SNAPSHOT error on startup
> -------------------------------------------------------------------
>
> Key: DROOLS-5114
> URL: https://issues.redhat.com/browse/DROOLS-5114
> Project: Drools
> Issue Type: Bug
> Reporter: Massimiliano Dessi
> Assignee: Massimiliano Dessi
> Priority: Major
>
> Dockerfile use java-1.8.0-openjdk-headless the project is build using open jdk 1.8 but at the pod startup the following stacktrace is printed in the log and prevent the pod to start correctly
> java.lang.UnsupportedClassVersionError: org/drools/cep/Rule_StockAverage302521058AccumulateExpression0Invoker has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:757)
> at org.drools.core.rule.JavaDialectRuntimeData$PackageClassLoader.internalDefineClass(JavaDialectRuntimeData.java:617)
> at org.drools.core.rule.JavaDialectRuntimeData$PackageClassLoader.fastFindClass(JavaDialectRuntimeData.java:588)
> at org.drools.core.rule.JavaDialectRuntimeData$PackageClassLoader.loadClass(JavaDialectRuntimeData.java:565)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:352)
> at org.drools.core.rule.JavaDialectRuntimeData.wire(JavaDialectRuntimeData.java:459)
> at org.drools.core.rule.JavaDialectRuntimeData.wire(JavaDialectRuntimeData.java:450)
> at org.drools.core.rule.JavaDialectRuntimeData.wireAll(JavaDialectRuntimeData.java:280)
> at org.drools.core.rule.JavaDialectRuntimeData.onBeforeExecute(JavaDialectRuntimeData.java:252)
> at org.drools.core.rule.DialectRuntimeRegistry.onBeforeExecute(DialectRuntimeRegistry.java:137)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.reloadAll(KnowledgeBuilderImpl.java:1448)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.wireAllRules(KnowledgeBuilderImpl.java:927)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.buildRules(KnowledgeBuilderImpl.java:2504)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.buildPackages(KnowledgeBuilderImpl.java:2428)
> at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:106)
> at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:98)
> at org.drools.compiler.kie.builder.impl.AbstractKieProject.buildKnowledgePackages(AbstractKieProject.java:261)
> at org.drools.compiler.kie.builder.impl.AbstractKieModule.buildKnowledgePackages(AbstractKieModule.java:195)
> at org.drools.compiler.kie.builder.impl.AbstractKieModule.createKieBase(AbstractKieModule.java:209)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(KieContainerImpl.java:407)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:375)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBaseFromKieSessionModel(KieContainerImpl.java:560)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:536)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:459)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:442)
> at org.kie.hacep.consumer.DroolsConsumerHandler.createAndInitializeSessionContextWithoutSnapshot(DroolsConsumerHandler.java:89)
> at org.kie.hacep.consumer.DroolsConsumerHandler.initializeKieSessionContext(DroolsConsumerHandler.java:69)
> at org.kie.hacep.consumer.DroolsConsumerHandler.<init>(DroolsConsumerHandler.java:57)
> at org.kie.hacep.core.infra.consumer.ConsumerController.<init>(ConsumerController.java:33)
> at org.kie.hacep.core.Bootstrap.startConsumers(Bootstrap.java:102)
> at org.kie.hacep.core.Bootstrap.startEngine(Bootstrap.java:47)
> at org.kie.hacep.endpoint.bootstrap.BootstrapListener.initServices(BootstrapListener.java:37)
> at org.kie.hacep.endpoint.bootstrap.BootstrapListener.contextInitialized(BootstrapListener.java:33)
> at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4683)
> at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5146)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
