August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4262) Test and move infrastructure and code to Openshift 4

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4262?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4262: --------------------------------------- Attachment: Istantanea_2019-08-08_12-45-18.png > Test and move infrastructure and code to Openshift 4 > ---------------------------------------------------- > > Key: DROOLS-4262 > URL: https://issues.jboss.org/browse/DROOLS-4262 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > Labels: HADrools > Attachments: Istantanea_2019-08-08_12-48-58.png > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4262) Test and move infrastructure and code to Openshift 4

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4262?page=com.atlassian.jira.plugi... ] Massimiliano Dessi commented on DROOLS-4262: -------------------------------------------- !Istantanea_2019-08-08_12-48-58.png|thumbnail! > Test and move infrastructure and code to Openshift 4 > ---------------------------------------------------- > > Key: DROOLS-4262 > URL: https://issues.jboss.org/browse/DROOLS-4262 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > Labels: HADrools > Attachments: Istantanea_2019-08-08_12-48-58.png > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4262) Test and move infrastructure and code to Openshift 4

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4262?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4262: --------------------------------------- Attachment: (was: Istantanea_2019-08-08_12-45-18.png) > Test and move infrastructure and code to Openshift 4 > ---------------------------------------------------- > > Key: DROOLS-4262 > URL: https://issues.jboss.org/browse/DROOLS-4262 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > Labels: HADrools > Attachments: Istantanea_2019-08-08_12-48-58.png > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4262) Test and move infrastructure and code to Openshift 4

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4262?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4262: --------------------------------------- Attachment: Istantanea_2019-08-08_12-48-58.png > Test and move infrastructure and code to Openshift 4 > ---------------------------------------------------- > > Key: DROOLS-4262 > URL: https://issues.jboss.org/browse/DROOLS-4262 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > Labels: HADrools > Attachments: Istantanea_2019-08-08_12-48-58.png > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4592) WildFly Core doesn't compile on Open JDK 14 anymore

by Richard Opalka (Jira)

[ https://issues.jboss.org/browse/WFCORE-4592?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFCORE-4592: ----------------------------------- Priority: Major (was: Blocker) > WildFly Core doesn't compile on Open JDK 14 anymore > --------------------------------------------------- > > Key: WFCORE-4592 > URL: https://issues.jboss.org/browse/WFCORE-4592 > Project: WildFly Core > Issue Type: Task > Components: Security > Environment: Since Open JDK 14 EA build 8 including > Reporter: Richard Opalka > Assignee: Darran Lofthouse > Priority: Major > Fix For: 10.0.0.Beta4 > > > [INFO] ------------------------------------------------------------- > [ERROR] COMPILATION ERROR : > [INFO] ------------------------------------------------------------- > [ERROR] /home/opalka/git/redhat/wildfly-core/domain-management/src/main/java/org/jboss/as/domain/management/security/JaasCallbackHandler.java:[224,51] cannot access java.security.acl.Group > class file for java.security.acl.Group not found > [INFO] 1 error > [INFO] ------------------------------------------------------------- -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4414) Scenario Simulation model versions are incompatible

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4414?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4414: -------------------------------- Description: There is an incompatibility between Scenario Simulation 1.5 and 1.6 versions. The incompatibility can be spotted for example: - Create project on the RHPAM product 7.4.0, there is Scenario Simulation model version 1.5 - Import such project into business central 7.25.0-SNAPSHOT, There is Scenario Simulation model version 1.6 - Try to open the *test-salary.scesim* file - The error user will see is attached h2. Acceptance Test Import attached projects into business-central and open all *scesim* files was: There is an incompatibility between Scenario Simulation 1.5 and 1.6 versions. The incompatibility can be spotted for example: - Create project on the RHPAM product 7.4.0, there is Scenario Simulation model version 1.5 - Import such project into business central 7.25.0-SNAPSHOT, There is Scenario Simulation model version 1.6 - Try to open the *test-salary.scesim* file - The error user will see is attached > Scenario Simulation model versions are incompatible > --------------------------------------------------- > > Key: DROOLS-4414 > URL: https://issues.jboss.org/browse/DROOLS-4414 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.25.0.Final > Reporter: Jozef Marko > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > Attachments: Screenshot from 2019-08-06 11-42-52.png, dmn-scenario-7.4.cr2.zip, dmn7514092237000103858.zip > > > There is an incompatibility between Scenario Simulation 1.5 and 1.6 versions. > The incompatibility can be spotted for example: > - Create project on the RHPAM product 7.4.0, there is Scenario Simulation model version 1.5 > - Import such project into business central 7.25.0-SNAPSHOT, There is Scenario Simulation model version 1.6 > - Try to open the *test-salary.scesim* file > - The error user will see is attached > h2. Acceptance Test > Import attached projects into business-central and open all *scesim* files -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4414) Scenario Simulation model versions are incompatible

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4414?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4414: -------------------------------- Attachment: dmn7514092237000103858.zip > Scenario Simulation model versions are incompatible > --------------------------------------------------- > > Key: DROOLS-4414 > URL: https://issues.jboss.org/browse/DROOLS-4414 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.25.0.Final > Reporter: Jozef Marko > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > Attachments: Screenshot from 2019-08-06 11-42-52.png, dmn-scenario-7.4.cr2.zip, dmn7514092237000103858.zip > > > There is an incompatibility between Scenario Simulation 1.5 and 1.6 versions. > The incompatibility can be spotted for example: > - Create project on the RHPAM product 7.4.0, there is Scenario Simulation model version 1.5 > - Import such project into business central 7.25.0-SNAPSHOT, There is Scenario Simulation model version 1.6 > - Try to open the *test-salary.scesim* file > - The error user will see is attached -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12283) Upgrade IronJacamar from 1.4.16.Final to 1.4.17.Final

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/WFLY-12283?page=com.atlassian.jira.plugin... ] Martin Stefanko reassigned WFLY-12283: -------------------------------------- Assignee: Martin Stefanko (was: Stefano Maestri) > Upgrade IronJacamar from 1.4.16.Final to 1.4.17.Final > ----------------------------------------------------- > > Key: WFLY-12283 > URL: https://issues.jboss.org/browse/WFLY-12283 > Project: WildFly > Issue Type: Component Upgrade > Components: JCA > Affects Versions: 17.0.1.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12329) ManagedScheduledExecutorService should be only available after server is ready

by nimo stephan (Jira)

[ https://issues.jboss.org/browse/WFLY-12329?page=com.atlassian.jira.plugin... ] nimo stephan commented on WFLY-12329: ------------------------------------- [~emmartins] to reproduce the issue at startup, put only the following class into a common war and start the server while watching the wildfly log at startup and you will see the stacktrace above: {code:java} @Startup @Singleton public class TaskScheduler { @Resource ManagedScheduledExecutorService executorService; // This will start the executorService automatically @PostConstruct public void init() { executorService.scheduleAtFixedRate(this::task, 0, 5, TimeUnit.SECONDS); } public void task() { System.out.println("long running task:" + LocalTime.now()); } } {code} > ManagedScheduledExecutorService should be only available after server is ready > ------------------------------------------------------------------------------ > > Key: WFLY-12329 > URL: https://issues.jboss.org/browse/WFLY-12329 > Project: WildFly > Issue Type: Bug > Components: Concurrency Utilities > Affects Versions: 17.0.1.Final > Reporter: nimo stephan > Assignee: Eduardo Martins > Priority: Major > > I use a *ManagedScheduledExecutorService* to execute tasks periodically: > {code:java} > @Startup > @Singleton > public class TaskScheduler { > @Resource > ManagedScheduledExecutorService executorService; > @PostConstruct > public void init() { > executorService.scheduleAtFixedRate(this::task, 0, 5, TimeUnit.SECONDS); > } > public void task() { > System.out.println("long running task:" + LocalTime.now()); > } > } > {code} > Wildfly throws a few exceptions as long as server is not fully initiated and in "suspend"-mode: > {code:java} > 12:44:12,715 ERROR [org.jboss.as.ee] (EE-ManagedScheduledExecutorService-default-Thread-3) WFLYEE0110: Failed to run scheduled task: java.lang.IllegalStateException: WFLYEE0111: Cannot run scheduled task my.Task$$Lambda$1041/0x000000080240a040@5ee966ec as container is suspended > at org.jboss.as.ee@17.0.1.Final//org.jboss.as.ee.concurrent.ControlPointUtils$ControlledScheduledRunnable.run(ControlPointUtils.java:164) > at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) > at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383) > at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:835) > at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) > {code} > I use _ManagedScheduledExecutorService_ instead of _ScheduledExecutorService_ in JEE because, *ManagedScheduledExecutorService* should be managed by JEE. Hence, the server should also manage and guarantee not to fire the executorService until the server is ready (and EJBs are available). -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7297) It is not possible to explode and browse deployments within deployment

by Harald Pehl (Jira)

[ https://issues.jboss.org/browse/WFLY-7297?page=com.atlassian.jira.plugin.... ] Harald Pehl commented on WFLY-7297: ----------------------------------- I think to explode a sub-deployments, we need to implement a custom feature. > It is not possible to explode and browse deployments within deployment > ---------------------------------------------------------------------- > > Key: WFLY-7297 > URL: https://issues.jboss.org/browse/WFLY-7297 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 11.0.0.Alpha1 > Reporter: Jan Štefl > Assignee: Harald Pehl > Priority: Major > Attachments: jboss-kitchensink-ear.ear > > > It is possible to explode and browse content of top level deployment but there is no possibility for such operation with deployment. > Attaching test deployent for experiments. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 August 2019