November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3333) Executable model throws "code too large" error when processing large DRL file

by Tibor Zimányi (Jira)

Tibor Zimányi created DROOLS-3333: ------------------------------------- Summary: Executable model throws "code too large" error when processing large DRL file Key: DROOLS-3333 URL: https://issues.jboss.org/browse/DROOLS-3333 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.14.0.Final Reporter: Tibor Zimányi Assignee: Mario Fusco When handling larger DRL files, executable model fails with this stacktrace: [1]. PR with a reproducer can be found here [2]. [1] https://gist.github.com/baldimir/6f84ef33052e4bf7df7c2ec8603ded67 [2] https://github.com/kiegroup/drools/pull/2157 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3332) Executable model throws "code too large" error when processing large DRL file

by Tibor Zimányi (Jira)

Tibor Zimányi created DROOLS-3332: ------------------------------------- Summary: Executable model throws "code too large" error when processing large DRL file Key: DROOLS-3332 URL: https://issues.jboss.org/browse/DROOLS-3332 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.14.0.Final Reporter: Tibor Zimányi Assignee: Mario Fusco When handling larger DRL files, executable model fails with this stacktrace: [1]. I will create a PR with reproducer for this. [1] https://gist.github.com/baldimir/6f84ef33052e4bf7df7c2ec8603ded67 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-519) Adjust workloads to KIALI-1803

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-519?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-519. ---------------------------------- Resolution: Done https://github.com/Kiali-QE/kiali-qe-python/pull/104 > Adjust workloads to KIALI-1803 > ------------------------------ > > Key: SWSQE-519 > URL: https://issues.jboss.org/browse/SWSQE-519 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-519) Adjust workloads to KIALI-1803

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-519: ------------------------------------ Summary: Adjust workloads to KIALI-1803 Key: SWSQE-519 URL: https://issues.jboss.org/browse/SWSQE-519 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9879) ActiveMQ resource adapter properties doesn't work

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-9879?page=com.atlassian.jira.plugin.... ] Miroslav Novak commented on WFLY-9879: -------------------------------------- [~barhiz33] Do you still see this issue with latest Widflly and ActiveMQ? > ActiveMQ resource adapter properties doesn't work > ------------------------------------------------- > > Key: WFLY-9879 > URL: https://issues.jboss.org/browse/WFLY-9879 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 11.0.0.Final > Reporter: baruch hiz > Assignee: Jeff Mesnil > Priority: Major > > Using activemq5.15.3 rar when configuring MDB, the redelivery policy doesn't work -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3258) [DMN Designer] Import DMN file (initial R&D)

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3258?page=com.atlassian.jira.plugi... ] Guilherme Carreiro commented on DROOLS-3258: -------------------------------------------- [~manstis] This JIRA refers to the initial effort for implementing the import feature. This is not related to where the DMN file lives (inside of Workbench or not). I've renamed the JIRA to clarify things. > [DMN Designer] Import DMN file (initial R&D) > -------------------------------------------- > > Key: DROOLS-3258 > URL: https://issues.jboss.org/browse/DROOLS-3258 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > This is a R&D task. > Check DMN spec, the current code, break the initial tasks, convert this JIRA to a EPIC and update its description for the import feature. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3258) [DMN Designer] Import DMN file (initial R&D)

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3258?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3258: --------------------------------------- Summary: [DMN Designer] Import DMN file (initial R&D) (was: [DMN Designer] Import external DMN file (initial R&D)) > [DMN Designer] Import DMN file (initial R&D) > -------------------------------------------- > > Key: DROOLS-3258 > URL: https://issues.jboss.org/browse/DROOLS-3258 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > This is a R&D task. > Check DMN spec, the current code, break the initial tasks, convert this JIRA to a EPIC and update its description for the import feature. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9595) Incorrect Journal filesize calculation where specified size is lest that the block size when using AIO

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-9595?page=com.atlassian.jira.plugin.... ] Miroslav Novak commented on WFLY-9595: -------------------------------------- Issue is still valid in Wildfly14/Artemis 2.6.3. > Incorrect Journal filesize calculation where specified size is lest that the block size when using AIO > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-9595 > URL: https://issues.jboss.org/browse/WFLY-9595 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 11.0.0.Final, 14.0.0.Final > Reporter: Darran Lofthouse > Assignee: Jeff Mesnil > Priority: Major > > This issue was discovered as a side effect of: - > https://github.com/wildfly/wildfly/commit/df9e16241207ebc412ddd16c790c4b7... > This change updated the size to be 1024 for the tests as a large file was not necessary. For continuous integration the agents have a blocksize of 512 so as the configured size is a multiple of the blocksize this was fine. > However running the test 'org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase' on a machine with a blocksize of 4096 this test would fail as the servers would fail to boot. > After some debugging it became aparant this was the underlying error: - > {noformat} > {"jboss.messaging-activemq.default.jms.manager" => "java.lang.IllegalArgumentException: File size cannot be less than 1024 bytes > Caused by: java.lang.IllegalArgumentException: File size cannot be less than 1024 bytes"} > {noformat} > After further debugging I have tracked it down to this class 'org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager' - I can confirm the configured value does make it to this class but it is the following block of code which then looses the value: - > {code:java} > int fileSize = config.getJournalFileSize(); > // we need to correct the file size if its not a multiple of the alignement > int modulus = fileSize % journalFF.getAlignment(); > if (modulus != 0) { > int difference = modulus; > int low = config.getJournalFileSize() - difference; > int high = low + journalFF.getAlignment(); > fileSize = difference < journalFF.getAlignment() / 2 ? low : high; > ActiveMQServerLogger.LOGGER.invalidJournalFileSize(config.getJournalFileSize(), fileSize, journalFF.getAlignment()); > } > Journal localMessage = new JournalImpl(ioExecutors, fileSize, config.getJournalMinFiles(), config.getJournalPoolFiles(), config.getJournalCompactMinFiles(), config.getJournalCompactPercentage(), journalFF, "activemq-data", "amq", journalFF.getMaxIO(), 0); > {code} > The file size comes in as 1024, the default is AIO so getAlignment returns the blocksize which in this case is 4096. So modulus and subsequently difference become 1024. > The file size and difference are both 1024 so low becomes 0, high becomes 4096. Due to the difference being less than half the block size low is selected and the file size is set to 0. > To select a correct filesize it looks like if low is less than the alignment always select high should be an option. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9595) Incorrect Journal filesize calculation where specified size is lest that the block size when using AIO

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-9595?page=com.atlassian.jira.plugin.... ] Miroslav Novak updated WFLY-9595: --------------------------------- Affects Version/s: 14.0.0.Final > Incorrect Journal filesize calculation where specified size is lest that the block size when using AIO > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-9595 > URL: https://issues.jboss.org/browse/WFLY-9595 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 11.0.0.Final, 14.0.0.Final > Reporter: Darran Lofthouse > Assignee: Jeff Mesnil > Priority: Major > > This issue was discovered as a side effect of: - > https://github.com/wildfly/wildfly/commit/df9e16241207ebc412ddd16c790c4b7... > This change updated the size to be 1024 for the tests as a large file was not necessary. For continuous integration the agents have a blocksize of 512 so as the configured size is a multiple of the blocksize this was fine. > However running the test 'org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase' on a machine with a blocksize of 4096 this test would fail as the servers would fail to boot. > After some debugging it became aparant this was the underlying error: - > {noformat} > {"jboss.messaging-activemq.default.jms.manager" => "java.lang.IllegalArgumentException: File size cannot be less than 1024 bytes > Caused by: java.lang.IllegalArgumentException: File size cannot be less than 1024 bytes"} > {noformat} > After further debugging I have tracked it down to this class 'org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager' - I can confirm the configured value does make it to this class but it is the following block of code which then looses the value: - > {code:java} > int fileSize = config.getJournalFileSize(); > // we need to correct the file size if its not a multiple of the alignement > int modulus = fileSize % journalFF.getAlignment(); > if (modulus != 0) { > int difference = modulus; > int low = config.getJournalFileSize() - difference; > int high = low + journalFF.getAlignment(); > fileSize = difference < journalFF.getAlignment() / 2 ? low : high; > ActiveMQServerLogger.LOGGER.invalidJournalFileSize(config.getJournalFileSize(), fileSize, journalFF.getAlignment()); > } > Journal localMessage = new JournalImpl(ioExecutors, fileSize, config.getJournalMinFiles(), config.getJournalPoolFiles(), config.getJournalCompactMinFiles(), config.getJournalCompactPercentage(), journalFF, "activemq-data", "amq", journalFF.getMaxIO(), 0); > {code} > The file size comes in as 1024, the default is AIO so getAlignment returns the blocksize which in this case is 4096. So modulus and subsequently difference become 1024. > The file size and difference are both 1024 so low becomes 0, high becomes 4096. Due to the difference being less than half the block size low is selected and the file size is set to 0. > To select a correct filesize it looks like if low is less than the alignment always select high should be an option. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3193) UX to support selection of multiple data/domain object instances

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3193?page=com.atlassian.jira.plugi... ] Klara Kufova commented on DROOLS-3193: -------------------------------------- [~uxdlc], the list looks good to me; I would create the four issues as listed. [~danielezonca], WDYT? > UX to support selection of multiple data/domain object instances > ---------------------------------------------------------------- > > Key: DROOLS-3193 > URL: https://issues.jboss.org/browse/DROOLS-3193 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. scenario with more than one instance of “Person”...), so that I can create a test scenario. -- This message was sent by Atlassian Jira (v7.12.1#712002)

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