January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2233) DMN: time(date("2017-08-10")) should return 00:00:00z time

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2233?page=com.atlassian.jira.plugi... ] Tibor Zimányi commented on DROOLS-2233: --------------------------------------- Solved as part of this PR: https://github.com/kiegroup/drools/pull/1688 > DMN: time(date("2017-08-10")) should return 00:00:00z time > ---------------------------------------------------------- > > Key: DROOLS-2233 > URL: https://issues.jboss.org/browse/DROOLS-2233 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.5.0.Final > Reporter: Tibor Zimányi > Assignee: Tibor Zimányi > > According to the specification in section "10.3.2.3.5 date": > "Where necessary, including the valuedt function (see 10.3.2.x.6), a date value is considered to be equivalent to a date time value in which the time of day is UTC midnight (00:00:00)." > Currently the case time(date("2017-08-10")) returns null, because the evaluation ends with DateTimeException, because internally we represent dates as LocalDate class, which doesn't have time part. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8416) Create BroadcastEndpoint implementation using WF clustering API

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-8416?page=com.atlassian.jira.plugin.... ] Paul Ferraro closed WFLY-8416. ------------------------------ Resolution: Duplicate Issue Duplicate of WFLY-9271. > Create BroadcastEndpoint implementation using WF clustering API > --------------------------------------------------------------- > > Key: WFLY-8416 > URL: https://issues.jboss.org/browse/WFLY-8416 > Project: WildFly > Issue Type: Task > Components: Clustering, JMS > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 12.0.0.Alpha1 > > > The upgrade to JGroups 4.0 will break the JGroups BroadcastEndpoint implementation in ActiveMQ Artemis (which uses JGroups 3.x). JGroups is only used to broadcast/receive a byte[] to the cluster. This can be easily implemented using the WildFly clustering API. Such an implementation will simplify the transition to JGroups 4.0 and future-proof WildFly from any new API breakage as well as abstract away concepts like fork channels, etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9484) Upgrade netty-xnio-transport to 0.1.4.Final

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-9484?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-9484: ------------------------------ Summary: Upgrade netty-xnio-transport to 0.1.4.Final (was: Upgrade netty-xnio-transport to 0.1.3.Final) > Upgrade netty-xnio-transport to 0.1.4.Final > ------------------------------------------- > > Key: WFLY-9484 > URL: https://issues.jboss.org/browse/WFLY-9484 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 12.0.0.Alpha1 > > > netty-xnio-transport must be updated to the version of XNIO and netty used in WildFly with Artemis 2.x releases -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9483) Upgrade Netty to 4.1.19.Final

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-9483?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-9483: ------------------------------ Description: https://github.com/netty/netty/compare/netty-4.1.9.Final...netty-4.1.19.F... (was: https://github.com/netty/netty/compare/netty-4.1.9.Final...netty-4.1.16.F...) > Upgrade Netty to 4.1.19.Final > ----------------------------- > > Key: WFLY-9483 > URL: https://issues.jboss.org/browse/WFLY-9483 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 12.0.0.Alpha1 > > > https://github.com/netty/netty/compare/netty-4.1.9.Final...netty-4.1.19.F... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9483) Upgrade Netty to 4.1.19.Final

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-9483?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-9483: ------------------------------ Summary: Upgrade Netty to 4.1.19.Final (was: Upgrade Netty to 4.1.16.Final) > Upgrade Netty to 4.1.19.Final > ----------------------------- > > Key: WFLY-9483 > URL: https://issues.jboss.org/browse/WFLY-9483 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 12.0.0.Alpha1 > > > https://github.com/netty/netty/compare/netty-4.1.9.Final...netty-4.1.16.F... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2239) Property reactivity mask is not correctly calculated for nodes having a TimerNode as sink

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2239: ----------------------------------- Summary: Property reactivity mask is not correctly calculated for nodes having a TimerNode as sink Key: DROOLS-2239 URL: https://issues.jboss.org/browse/DROOLS-2239 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9610) Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution

by Serg Pol (JIRA)

[ https://issues.jboss.org/browse/WFLY-9610?page=com.atlassian.jira.plugin.... ] Serg Pol commented on WFLY-9610: -------------------------------- thanks. do You know occasionally why status STOPPING was not saved in DB till free available Thread? Will You publicise changes in java Class for fix? > Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9610 > URL: https://issues.jboss.org/browse/WFLY-9610 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 9.0.1.Final > Environment: Cluster, standalone-full-ha > Reporter: Serg Pol > Assignee: Cheng Fang > > Start of a BatchJob is called and record/entry is absent sometimes in DB table "step_execution" as well as Endtime and Exitstatus in the table job_execution (there is just info about start of BatchJob). > There are no any error nessages. > BatchJob is not started in this case according Log. > Any idea? Thanks -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2238) Property reactivity mask is not correctly calculated for nodes having a TimerNode as sink

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2238?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2238. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/dbfdf7cfcc3c2e59c7c9ffd08f06616... > Property reactivity mask is not correctly calculated for nodes having a TimerNode as sink > ----------------------------------------------------------------------------------------- > > Key: DROOLS-2238 > URL: https://issues.jboss.org/browse/DROOLS-2238 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2238) Property reactivity mask is not correctly calculated for nodes having a TimerNode as sink

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2238: ----------------------------------- Summary: Property reactivity mask is not correctly calculated for nodes having a TimerNode as sink Key: DROOLS-2238 URL: https://issues.jboss.org/browse/DROOLS-2238 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2237) Turn on CheckStyle for dmn editor

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2237: ----------------------------------- Summary: Turn on CheckStyle for dmn editor Key: DROOLS-2237 URL: https://issues.jboss.org/browse/DROOLS-2237 Project: Drools Issue Type: Task Components: DMN Editor Affects Versions: 7.6.0.Final Reporter: Jozef Marko Assignee: Jozef Marko Turn of the CheckStyle control of imports and licences for the dmn editor. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 January 2018