February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1507) JwtValidator issuer and audience check ignoring does not work

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1507?page=com.atlassian.jira.plugin.s... ] Jan Kalina commented on ELY-1507: --------------------------------- Please provide some issue description - for example reference to RFC part, which is violated. > JwtValidator issuer and audience check ignoring does not work > ------------------------------------------------------------- > > Key: ELY-1507 > URL: https://issues.jboss.org/browse/ELY-1507 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Reporter: Martin Mazanek > Assignee: Martin Mazanek > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3581) Graceful shutdown via sigterm cannot be resumed

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3581?page=com.atlassian.jira.plugi... ] David Lloyd commented on WFCORE-3581: ------------------------------------- The problem is that you cannot react twice. So if a SIGTERM is received and we supported resume, and the user chooses to resume the server, now the server is in a perpetual state of having exited; further SIGTERM will be ignored by the JVM, and process-exit processing will never start again. It would become difficult to kill the server. SIGTERM cannot be treated the same as the CLI operation due to this basic limitation of the JVM. > Graceful shutdown via sigterm cannot be resumed > ----------------------------------------------- > > Key: WFCORE-3581 > URL: https://issues.jboss.org/browse/WFCORE-3581 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Jan Stourac > Assignee: Brian Stansberry > Attachments: long-running-servlet.war > > > When server is sent SIGTERM signal to perform graceful shutdown just at the moment it is crunching a long-time running request, it cannot be resumed anymore with the :resume() CLI operation. > See server output (NOTE: NPE in server log is probably caused by this WFCORE-3572.): > {code} > 17:47:30,141 INFO [org.jboss.qa.management.web.resources.HeavyProcessingServlet] (default task-1) Started request processing > 17:47:34,367 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0211: Suspending server with 10000 ms timeout. > 17:47:34,368 INFO [org.jboss.as.ejb3] (Thread-2) WFLYEJB0493: EJB subsystem suspension complete > 17:47:36,022 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0212: Resuming server > 17:47:36,023 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested via an OS signal > 17:47:36,034 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 70) WFLYUT0022: Unregistered web context: '/long-running-servlet' from server 'default-server' > 17:47:36,050 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] > 17:47:36,055 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0019: Host default-host stopping > 17:47:36,058 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0019: Stopped Driver service with driver-name = h2 > 17:47:36,067 ERROR [org.jboss.threads.errors] (management task-1) Thread Thread[management task-1,5,main] threw an uncaught exception: java.lang.NullPointerException > at org.jboss.as.server.mgmt.ManagementWorkerService.stopDone(ManagementWorkerService.java:72) > at org.xnio.XnioWorker$1.run(XnioWorker.java:138) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor.completeTermination(EnhancedQueueExecutor.java:1755) > at org.jboss.threads.EnhancedQueueExecutor.tryDeallocateThread(EnhancedQueueExecutor.java:1578) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1393) > at java.lang.Thread.run(Thread.java:748) > 17:47:36,070 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 69) WFLYCLINF0003: Stopped client-mappings cache from ejb container > 17:47:36,086 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0008: Undertow HTTPS listener https suspending > 17:47:36,086 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0008: Undertow HTTP listener default suspending > 17:47:36,086 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0007: Undertow HTTPS listener https stopped, was bound to 127.0.0.1:8443 > 17:47:36,086 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080 > 17:47:36,087 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment long-running-servlet.war (runtime-name: long-running-servlet.war) in 61ms > 17:47:36,089 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0004: Undertow 1.4.22.Final stopping > {code} > This is server output in case that graceful shutdown is called via :shutdown(timeout=<time>) CLI operation: > {code} > 17:46:34,064 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 62) WFLYCLINF0002: Started client-mappings cache from ejb container > 17:46:34,184 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0021: Registered web context: '/long-running-servlet' for server 'default-server' > 17:46:34,194 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "long-running-servlet.war" (runtime-name : "long-running-servlet.war") > 17:46:34,249 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server > 17:46:34,251 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 17:46:34,251 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 17:46:34,251 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 12.0.0.Alpha1-SNAPSHOT (WildFly Core 4.0.0.Beta1-SNAPSHOT) started in 2915ms - Started 396 of 607 services (333 services are lazy, passive or on-demand) > 17:46:36,122 INFO [org.jboss.qa.management.web.resources.HeavyProcessingServlet] (default task-1) Started request processing > 17:46:39,998 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0211: Suspending server with 10000 ms timeout. > 17:46:40,000 INFO [org.jboss.as.ejb3] (management-handler-thread - 1) WFLYEJB0493: EJB subsystem suspension complete > 17:46:42,197 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0212: Resuming server > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2311) Drools Engine not able to load rules in spring-Boot project

by Chandresh Mishra (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2311?page=com.atlassian.jira.plugi... ] Chandresh Mishra reopened DROOLS-2311: -------------------------------------- > Drools Engine not able to load rules in spring-Boot project > ----------------------------------------------------------- > > Key: DROOLS-2311 > URL: https://issues.jboss.org/browse/DROOLS-2311 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.5.0.Final > Reporter: Chandresh Mishra > Assignee: Mario Fusco > Attachments: Drools-Issue.rar > > > am using the Drools 7.5.0-final in the spring Boot project. > I am working on a multi-module Gradle project. Rules and kmodule.xml is present in the sub-module project. This module is packaged as a Jar inside a fat spring boot Jar file. > I am building the container from the classpath. > KieContainer kContainer = kieService.newKieClasspathContainer(); > on server start-up (java -jar) it loads the Kmodule.xml and prints all the kbase and sessionName. > But when I fire rules it returns zero rules fired. > It works fine when I run as spring boot app from Eclipse. Please help. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2311) Drools Engine not able to load rules in spring-Boot project

by Chandresh Mishra (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2311?page=com.atlassian.jira.plugi... ] Chandresh Mishra updated DROOLS-2311: ------------------------------------- Attachment: Drools-Issue.rar > Drools Engine not able to load rules in spring-Boot project > ----------------------------------------------------------- > > Key: DROOLS-2311 > URL: https://issues.jboss.org/browse/DROOLS-2311 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.5.0.Final > Reporter: Chandresh Mishra > Assignee: Mario Fusco > Attachments: Drools-Issue.rar > > > am using the Drools 7.5.0-final in the spring Boot project. > I am working on a multi-module Gradle project. Rules and kmodule.xml is present in the sub-module project. This module is packaged as a Jar inside a fat spring boot Jar file. > I am building the container from the classpath. > KieContainer kContainer = kieService.newKieClasspathContainer(); > on server start-up (java -jar) it loads the Kmodule.xml and prints all the kbase and sessionName. > But when I fire rules it returns zero rules fired. > It works fine when I run as spring boot app from Eclipse. Please help. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2311) Drools Engine not able to load rules in spring-Boot project

by Chandresh Mishra (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2311?page=com.atlassian.jira.plugi... ] Chandresh Mishra commented on DROOLS-2311: ------------------------------------------ [~mfusco] No, I am not using the spring-boot-devtools. I am attaching the reproducer. Code attached is a Gradle project with 3 subprojects: A. application - spring boot project B. application-rule - DRL files and kmodule.xml C. application-service-data- calling rules engine. D. Drools-Issue- root project Steps to reproduce: 1. run "gradle clean build" inside "Drools-Issue" folder. 2. run "java -jar application-0.0.1-SNAPSHOT.jar" inside "Drools-Issue\application\build\libs" 3. Hit "http://localhost:8081//Rules/fireRules" Ideally, it should return "2" as a result but it will return "java.lang.RuntimeException: Unexpected global" > Drools Engine not able to load rules in spring-Boot project > ----------------------------------------------------------- > > Key: DROOLS-2311 > URL: https://issues.jboss.org/browse/DROOLS-2311 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.5.0.Final > Reporter: Chandresh Mishra > Assignee: Mario Fusco > Attachments: Drools-Issue.rar > > > am using the Drools 7.5.0-final in the spring Boot project. > I am working on a multi-module Gradle project. Rules and kmodule.xml is present in the sub-module project. This module is packaged as a Jar inside a fat spring boot Jar file. > I am building the container from the classpath. > KieContainer kContainer = kieService.newKieClasspathContainer(); > on server start-up (java -jar) it loads the Kmodule.xml and prints all the kbase and sessionName. > But when I fire rules it returns zero rules fired. > It works fine when I run as spring boot app from Eclipse. Please help. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1783) [Guided Decision Table] Focus is lost after renaming the GDT

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1783?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-1783: -------------------------------- Affects Version/s: 7.7.0.Final > [Guided Decision Table] Focus is lost after renaming the GDT > ------------------------------------------------------------ > > Key: DROOLS-1783 > URL: https://issues.jboss.org/browse/DROOLS-1783 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.2.0.Final, 7.7.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Trivial > Attachments: Screenshot from 2017-08-09 15-01-39.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3522) Module dependency order for a deployment is wrong

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3522?page=com.atlassian.jira.plugi... ] David Lloyd commented on WFCORE-3522: ------------------------------------- This issue is only partially (narrowly) addressed in the current PR. > Module dependency order for a deployment is wrong > ------------------------------------------------- > > Key: WFCORE-3522 > URL: https://issues.jboss.org/browse/WFCORE-3522 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 3.0.8.Final > Reporter: Ken Finnigan > Assignee: David Lloyd > Priority: Blocker > Fix For: 4.0.0.Beta1, 3.1.0.Final > > > Within WildFly Swarm we need the ability to override the `javax.ws.rs.client.ClientBuilder` service file for a deployment to provide custom handling for implementing Eclipse MicroProfile. > With a service file present in the deployment, the existing RESTEasy service file is always found first because the deployment module is added as a dependency after other non local dependencies. See https://github.com/wildfly/wildfly-core/blob/master/server/src/main/java/... > After discussing with [~dmlloyd] on IRC, he agreed this was a bug and a better solution was for the deployment's dependency to always be first if `isLocalLast()` is false, and instead remove any spec packages that might be present on the deployment path instead. > He explained the purpose of this ordering was to prevent a user deploying `javax.servlet.api` and breaking things, but it appears this can be achieved by alternative methods. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9771) SingletonPartitionTestCase.testSingletonService fails intermittently

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9771?page=com.atlassian.jira.plugin.... ] Paul Ferraro reassigned WFLY-9771: ---------------------------------- Assignee: Radoslav Husar (was: Paul Ferraro) > SingletonPartitionTestCase.testSingletonService fails intermittently > -------------------------------------------------------------------- > > Key: WFLY-9771 > URL: https://issues.jboss.org/browse/WFLY-9771 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Stuart Douglas > Assignee: Radoslav Husar > > e.g. https://ci.wildfly.org/viewLog.html?buildId=88100&buildTypeId=WF_PullRequ... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2311) Drools Engine not able to load rules in spring-Boot project

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2311?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2311. --------------------------------- Resolution: Duplicate Issue I'm assuming you're using spring-boot-devtools and if so this is a duplicate of https://issues.jboss.org/browse/DROOLS-1540 If this is not the case feel free to reopen this ticket, possibly providing a reproducer. > Drools Engine not able to load rules in spring-Boot project > ----------------------------------------------------------- > > Key: DROOLS-2311 > URL: https://issues.jboss.org/browse/DROOLS-2311 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.5.0.Final > Reporter: Chandresh Mishra > Assignee: Mario Fusco > > am using the Drools 7.5.0-final in the spring Boot project. > I am working on a multi-module Gradle project. Rules and kmodule.xml is present in the sub-module project. This module is packaged as a Jar inside a fat spring boot Jar file. > I am building the container from the classpath. > KieContainer kContainer = kieService.newKieClasspathContainer(); > on server start-up (java -jar) it loads the Kmodule.xml and prints all the kbase and sessionName. > But when I fire rules it returns zero rules fired. > It works fine when I run as spring boot app from Eclipse. Please help. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2311) Drools Engine not able to load rules in spring-Boot project

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2311?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-2311: -------------------------------- Sprint: 2018 Week 05-06 > Drools Engine not able to load rules in spring-Boot project > ----------------------------------------------------------- > > Key: DROOLS-2311 > URL: https://issues.jboss.org/browse/DROOLS-2311 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.5.0.Final > Reporter: Chandresh Mishra > Assignee: Mario Fusco > > am using the Drools 7.5.0-final in the spring Boot project. > I am working on a multi-module Gradle project. Rules and kmodule.xml is present in the sub-module project. This module is packaged as a Jar inside a fat spring boot Jar file. > I am building the container from the classpath. > KieContainer kContainer = kieService.newKieClasspathContainer(); > on server start-up (java -jar) it loads the Kmodule.xml and prints all the kbase and sessionName. > But when I fire rules it returns zero rules fired. > It works fine when I run as spring boot app from Eclipse. Please help. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 February 2018