February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12093) bug in tutorial "batch-processing" with column "End Time"

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-12093?page=com.atlassian.jira.plugi... ] Cheng Fang commented on WFLY-12093: ----------------------------------- end time should not change after a job execution is done. {{org.jboss.as.quickstarts.batch.controller.JobData#getEndTime}} should just return the value retrieved from batch job repository to reflect job execution history. > bug in tutorial "batch-processing" with column "End Time" > --------------------------------------------------------- > > Key: WFLY-12093 > URL: https://issues.redhat.com/browse/WFLY-12093 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Environment: batch-processing > Reporter: Святослав Кремлёв > Assignee: Parul Sharma > Priority: Major > Attachments: 2019-05-18 23_16_51-Batch Processing.png > > > in file > org/jboss/as/quickstarts/batch/controller/JobData.java > {code} > public Date getEndTime() { > endTime = new Date(); > return endTime.getTime() == 0 ? null : endTime; > } > {code} > its returns current time every time, not the job endTime -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4993) [DMN Designer] Code Completion - add keywords

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4993?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4993: ------------------------------------ Tester: Jozef Marko Story Points: 2 > [DMN Designer] Code Completion - add keywords > --------------------------------------------- > > Key: DROOLS-4993 > URL: https://issues.redhat.com/browse/DROOLS-4993 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Donato Marrazzo > Assignee: Guilherme Gomes > Priority: Major > Labels: dmn-designer > > Manage FEEL expression keywords: > * in > * or > * and > * between > * if ... then ... else ... > * for ... in ... return ... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5001) [DMN Designer] Data Types - Disable top-right search in the data types page

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-5001: --------------------------------------- Summary: [DMN Designer] Data Types - Disable top-right search in the data types page Key: DROOLS-5001 URL: https://issues.redhat.com/browse/DROOLS-5001 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Guilherme Gomes Assignee: Guilherme Gomes Attachments: icon.png Disable top-right search in the data types page, since it already has the search bar: !icon.png|width=800! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10715) TransactionSubsystemTestCase does not test for invalid XML in some cases

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/WFLY-10715?page=com.atlassian.jira.plugi... ] Thomas Jenkinson updated WFLY-10715: ------------------------------------ Issue Type: Task (was: Bug) > TransactionSubsystemTestCase does not test for invalid XML in some cases > ------------------------------------------------------------------------ > > Key: WFLY-10715 > URL: https://issues.redhat.com/browse/WFLY-10715 > Project: WildFly > Issue Type: Task > Components: Test Suite, Transactions > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Major > > 7.0.0+ introduces the following attributes not found in 6.4.0: [use-journal-store, statistics-enabled, journal-store-enable-async-io]. The test xml should be updated to include these and transformers added where missing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5000) Support getContext in Drools' executable model

by Luca Molteni (Jira)

Luca Molteni created DROOLS-5000: ------------------------------------ Summary: Support getContext in Drools' executable model Key: DROOLS-5000 URL: https://issues.redhat.com/browse/DROOLS-5000 Project: Drools Issue Type: Bug Components: executable model Reporter: Luca Molteni Assignee: Luca Molteni jBPM uses this utility method in Knowledge Helper package org.drools.bpmn2 import org.kie.api.runtime.process.ProcessContext rule "Auto-activate Hello1" ruleflow-group "Hello" when then System.out.println(drools); System.out.println(drools.getContext(ProcessContext.class)); System.out.println(drools.getContext(ProcessContext.class).getProcessInstance()); drools.getContext(ProcessContext.class).getProcessInstance().signalEvent("Hello1", null); end -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4999) Make jbpm to work with the executable model

by Mario Fusco (Jira)

Mario Fusco created DROOLS-4999: ----------------------------------- Summary: Make jbpm to work with the executable model Key: DROOLS-4999 URL: https://issues.redhat.com/browse/DROOLS-4999 Project: Drools Issue Type: Task Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3068) could fail more gracefully when wrong Java version used

by Katarina Hermanova (Jira)

[ https://issues.redhat.com/browse/WFLY-3068?page=com.atlassian.jira.plugin... ] Katarina Hermanova reassigned WFLY-3068: ---------------------------------------- Assignee: Katarina Hermanova > could fail more gracefully when wrong Java version used > ------------------------------------------------------- > > Key: WFLY-3068 > URL: https://issues.redhat.com/browse/WFLY-3068 > Project: WildFly > Issue Type: Bug > Components: Class Loading, Server > Affects Versions: 8.0.0.Final > Environment: Java version < 7 > Reporter: dpocock > Assignee: Katarina Hermanova > Priority: Minor > > If I try to start Wildfly with Java 6 (which is no longer support of course) it just fails with a stack: > 09:51:00,536 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final > 09:51:00,543 WARN [org.jboss.modules] (main) Failed to define class org.jboss.as.jmx.PluggableMBeanServerBuilder in Module "org.jboss.as.jmx:main" from local module loader @36b60b93 (finder: local module finder @69b1fbf4 ()): java.lang.UnsupportedClassVersionError: org/jboss/as/jmx/PluggableMBeanServerBuilder : Unsupported major.minor version 51.0 > at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.6.0_26] > at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) [rt.jar:1.6.0_26] > at java.lang.ClassLoader.defineClass(ClassLoader.java:615) [rt.jar:1.6.0_26] > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:345) [jboss-modules.jar:1.3.0.Final] > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:423) [jboss-modules.jar:1.3.0.Final] > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261) [jboss-modules.jar:1.3.0.Final] > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76) [jboss-modules.jar:1.3.0.Final] > at org.jboss.modules.Module.loadModuleClass(Module.java:548) [jboss-modules.jar:1.3.0.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:189) [jboss-modules.jar:1.3.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443) [jboss-modules.jar:1.3.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431) [jboss-modules.jar:1.3.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373) [jboss-modules.jar:1.3.0.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118) [jboss-modules.jar:1.3.0.Final] > at javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:423) [rt.jar:1.6.0_26] > at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:465) [rt.jar:1.6.0_26] > at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:511) [rt.jar:1.6.0_26] > at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:298) [rt.jar:1.6.0_26] > at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:213) [rt.jar:1.6.0_26] > at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:174) [rt.jar:1.6.0_26] > at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:302) [rt.jar:1.6.0_26] > at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:504) [rt.jar:1.6.0_26] > at org.jboss.modules.Main.main(Main.java:449) [jboss-modules.jar:1.3.0.Final] > Exception in thread "main" java.lang.UnsupportedClassVersionError: org/jboss/as/jmx/PluggableMBeanServerBuilder : Unsupported major.minor version 51.0 > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) > at java.lang.ClassLoader.defineClass(ClassLoader.java:615) > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:345) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:423) > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261) > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76) > at org.jboss.modules.Module.loadModuleClass(Module.java:548) > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:189) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118) > at javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:423) > at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:465) > at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:511) > at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:298) > at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:213) > at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:174) > at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:302) > at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:504) > at org.jboss.modules.Main.main(Main.java:449) > It would be more friendly if it checked the Java version in the main() function and stopped gracefully. The stack trace is not hard to understand but may not be obvious to everybody. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13050) config and metrics should be optional in observability layer

by Jean Francois Denise (Jira)

Jean Francois Denise created WFLY-13050: ------------------------------------------- Summary: config and metrics should be optional in observability layer Key: WFLY-13050 URL: https://issues.redhat.com/browse/WFLY-13050 Project: WildFly Issue Type: Enhancement Components: Build System Reporter: Jean Francois Denise Assignee: Jean Francois Denise With the introduction of microprofile, one could provision both cloud-server,microprofile and exclude any microprofile-* layer. config and metrics being not optional in observability, they can't be excluded from cloud-server although they can with other server (jaxrs, datasources). This could be solved by excluding observability along with metric/config but in this case health would be excluded too. So to offer enough flexibility (eg: exclude config but provision health) and an aligned experience across the server layers, config and metrics should be optional in observability. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13049) Upgrate netty to 4.1.45.Final

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13049?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet updated WFLY-13049: ------------------------------------- Summary: Upgrate netty to 4.1.45.Final (was: Update netty to 4.1.45.Final) > Upgrate netty to 4.1.45.Final > ----------------------------- > > Key: WFLY-13049 > URL: https://issues.redhat.com/browse/WFLY-13049 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering, JMS > Affects Versions: 19.0.0.Beta1 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13049) Upgrade netty to 4.1.45.Final

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13049?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet updated WFLY-13049: ------------------------------------- Summary: Upgrade netty to 4.1.45.Final (was: Upgrate netty to 4.1.45.Final) > Upgrade netty to 4.1.45.Final > ----------------------------- > > Key: WFLY-13049 > URL: https://issues.redhat.com/browse/WFLY-13049 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering, JMS > Affects Versions: 19.0.0.Beta1 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2020