[JBoss JIRA] (JGRP-2481) Use IdentityHashmap in Util.TYPES and ClassConfigurator
by Bela Ban (Jira)
Bela Ban created JGRP-2481:
------------------------------
Summary: Use IdentityHashmap in Util.TYPES and ClassConfigurator
Key: JGRP-2481
URL: https://issues.redhat.com/browse/JGRP-2481
Project: JGroups
Issue Type: Enhancement
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 5.0.0.Beta2
When we have lookup hashmaps, populated at startup, and not changed afterwards, we can use IdentityHashmaps, as a {{get()}} is constant.
For keys with a contiguous range (e.g. {{[1 .. 20]}}), we might even use a simple array of keys and values, e.g. {{[K1,V1,K2,V2, ... Kn,Vn}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (JGRP-2480) ObjectMessage: better marshalling
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2480?page=com.atlassian.jira.plugin... ]
Bela Ban resolved JGRP-2480.
----------------------------
Resolution: Done
> ObjectMessage: better marshalling
> ---------------------------------
>
> Key: JGRP-2480
> URL: https://issues.redhat.com/browse/JGRP-2480
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 5.0.0.Beta2
>
>
> Currently, {{ObjectMessage}} accepts only objects of type {{SizeStreamable}} and wraps everything else into {{ObjectWrapper}} instances.
> This means that primitive types (e.g. "{{7}}" or "{{hello world}}") will be wrapped, too. The disadvantage of {{ObjectWrapper}} is that it performs _eager marshalling_, creating an unwanted byte[] array before the message is actually marshalled. On the receiver side, another byte[] array will be created before the actual unmarshalling starts.
> Solution: accept primitive types (e.g. {{int}}, {{Integer}}, {{String}}, {{AsciiString}}, {{byte[]}} etc) directly, without wrapping them into an {{ObjectWrapper}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (DROOLS-5400) Executable model build fails with SerialVersionUID and key annotations
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5400?page=com.atlassian.jira.plug... ]
Mario Fusco updated DROOLS-5400:
--------------------------------
Sprint: 2020 Week 22-24 (from May 25)
> Executable model build fails with SerialVersionUID and key annotations
> ----------------------------------------------------------------------
>
> Key: DROOLS-5400
> URL: https://issues.redhat.com/browse/DROOLS-5400
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.38.0.Final
> Reporter: Matteo Casalino
> Assignee: Mario Fusco
> Priority: Minor
> Attachments: serial-version-uid-exec-model.zip
>
>
> Executable model compilation fails on declared types with both _@SerialVersionUID_ and _@key_ annotations.
> Example of DRL that fails to compile:
> {noformat}
> declare ServiceInformation
> @serialVersionUID( 0 )
> code: String @key
> end
> rule "create new ServiceInformation"
> when
> then
> insert( new ServiceInformation("123456") );
> end
> {noformat}
> Error:
> {noformat}
> Error Messages:
> Message [id=1, kieBase=binding-field-indexed-with-square-brackets, level=ERROR, path=null, line=56, column=0
> text=Duplicate method ServiceInformation(String) in type ServiceInformation]
> Message [id=2, kieBase=binding-field-indexed-with-square-brackets, level=ERROR, path=null, line=61, column=0
> text=Duplicate method ServiceInformation(String) in type ServiceInformation]
> {noformat}
> The example works fine when compiling without executable model.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (DROOLS-5401) Suppress RuntimeException in ExecModelLambdaPostProcessor
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5401?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi updated DROOLS-5401:
--------------------------------------
Description:
When we hit an issue in ExecModelLambdaPostProcessor, we want to silently fall back to non-externalized lambda (don't want to break a build). Currently ExecModelLambdaPostProcessor throws RuntimeException only in unusual cases but still it's better to log and return rather than throwing RuntimeException.
Btw, we can detect non-externalized lambda with option "drools.check.nonExternalisedLambda" (DROOLS-5346).
was:
When we hit an issue in ExecModelLambdaPostProcessor, we want to silently fall back to non-externalized lambda. Currently ExecModelLambdaPostProcessor throws RuntimeException only in unusual cases but still it's better to log and return rather than throwing RuntimeException.
Btw, we can detect non-externalized lambda with option "drools.check.nonExternalisedLambda" (DROOLS-5346).
> Suppress RuntimeException in ExecModelLambdaPostProcessor
> ---------------------------------------------------------
>
> Key: DROOLS-5401
> URL: https://issues.redhat.com/browse/DROOLS-5401
> Project: Drools
> Issue Type: Enhancement
> Components: executable model
> Affects Versions: 7.38.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Minor
>
> When we hit an issue in ExecModelLambdaPostProcessor, we want to silently fall back to non-externalized lambda (don't want to break a build). Currently ExecModelLambdaPostProcessor throws RuntimeException only in unusual cases but still it's better to log and return rather than throwing RuntimeException.
> Btw, we can detect non-externalized lambda with option "drools.check.nonExternalisedLambda" (DROOLS-5346).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (DROOLS-3746) JavaScript run error when edit Guided Decision Tables on latest chrome
by Sergey Manukyan (Jira)
[ https://issues.redhat.com/browse/DROOLS-3746?page=com.atlassian.jira.plug... ]
Sergey Manukyan edited comment on DROOLS-3746 at 6/3/20 12:13 AM:
------------------------------------------------------------------
Had same issue, appeared next day suddenly, was using OSX, OpenJDK 1.8, the Decision Manager 7.7. on EAP 7.2 . Same issue on Chrome 83 & Firefox 68
{quote}
15:03:03,651 ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-41) Error from user: dmAdmin Error ID: -79860134 Location: LibraryPerspective|$ProjectScreen,GuidedDecisionTableEditor?path_uri=default://master@MySpace/AAAPricing/src/main/resources/com/myspace/aaapricing/Pricing%2520Table.gdst&file_name=Pricing%20Table.gdst&has_version_support=true Exception: Uncaught exception: Uncaught TypeError: Cannot read property 'createElement' of undefined (http://localhost:8080/decision-central/verifier/dtableVerifier/3EA3E9D35E...)
{quote}
The workaround with {{-Dorg.kie.verification.disable-dtable-realtime-verification=true}}
helped
was (Author: smanukya):
Had same issue, appeared next day suddenly, was using OSX, OpenJDK 1.8, the Decision Manager 7.7. on EAP 7.2
{quote}
15:03:03,651 ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-41) Error from user: dmAdmin Error ID: -79860134 Location: LibraryPerspective|$ProjectScreen,GuidedDecisionTableEditor?path_uri=default://master@MySpace/AAAPricing/src/main/resources/com/myspace/aaapricing/Pricing%2520Table.gdst&file_name=Pricing%20Table.gdst&has_version_support=true Exception: Uncaught exception: Uncaught TypeError: Cannot read property 'createElement' of undefined (http://localhost:8080/decision-central/verifier/dtableVerifier/3EA3E9D35E...)
{quote}
The workaround with {{-Dorg.kie.verification.disable-dtable-realtime-verification=true}}
helped
> JavaScript run error when edit Guided Decision Tables on latest chrome
> ----------------------------------------------------------------------
>
> Key: DROOLS-3746
> URL: https://issues.redhat.com/browse/DROOLS-3746
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 7.18.0.Final
> Reporter: xiaodong zhang
> Assignee: Toni Rikkola
> Priority: Blocker
>
> When updated to the latest chrome (72.0.3626.121), When I do edit using Guided Decision Tables, an error will throw.
> The error detail is :
> | Uncaught exception: Uncaught TypeError: Cannot read property 'createElement' of undefined (http://127.0.0.1:8080/kie-drools-wb/verifier/dtableVerifier/C1C6DDEF649DA...)
> My version is 7.14.0.Final and I also tried the latest 7.18.0.Final but no lucky. It's happend on both windows and Mac client when using the latest chrome or safari.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (DROOLS-3746) JavaScript run error when edit Guided Decision Tables on latest chrome
by Sergey Manukyan (Jira)
[ https://issues.redhat.com/browse/DROOLS-3746?page=com.atlassian.jira.plug... ]
Sergey Manukyan edited comment on DROOLS-3746 at 6/3/20 12:07 AM:
------------------------------------------------------------------
Had same issue, appeared next day suddenly, was using OSX, OpenJDK 1.8, the Decision Manager 7.7. on EAP 7.2
{quote}
15:03:03,651 ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-41) Error from user: dmAdmin Error ID: -79860134 Location: LibraryPerspective|$ProjectScreen,GuidedDecisionTableEditor?path_uri=default://master@MySpace/AAAPricing/src/main/resources/com/myspace/aaapricing/Pricing%2520Table.gdst&file_name=Pricing%20Table.gdst&has_version_support=true Exception: Uncaught exception: Uncaught TypeError: Cannot read property 'createElement' of undefined (http://localhost:8080/decision-central/verifier/dtableVerifier/3EA3E9D35E...)
{quote}
The workaround with {{-Dorg.kie.verification.disable-dtable-realtime-verification=true}}
helped
was (Author: smanukya):
Had same issue, appeared next day suddenly, was using OSX, OpenJDK 1.8, the Decision Manager 7.7. on EAP 7.2
```15:03:03,651 ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-41) Error from user: dmAdmin Error ID: -79860134 Location: LibraryPerspective|$ProjectScreen,GuidedDecisionTableEditor?path_uri=default://master@MySpace/AAAPricing/src/main/resources/com/myspace/aaapricing/Pricing%2520Table.gdst&file_name=Pricing%20Table.gdst&has_version_support=true Exception: Uncaught exception: Uncaught TypeError: Cannot read property 'createElement' of undefined (http://localhost:8080/decision-central/verifier/dtableVerifier/3EA3E9D35E...
The workaround with ```-Dorg.kie.verification.disable-dtable-realtime-verification=true``` - helped
> JavaScript run error when edit Guided Decision Tables on latest chrome
> ----------------------------------------------------------------------
>
> Key: DROOLS-3746
> URL: https://issues.redhat.com/browse/DROOLS-3746
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 7.18.0.Final
> Reporter: xiaodong zhang
> Assignee: Toni Rikkola
> Priority: Blocker
>
> When updated to the latest chrome (72.0.3626.121), When I do edit using Guided Decision Tables, an error will throw.
> The error detail is :
> | Uncaught exception: Uncaught TypeError: Cannot read property 'createElement' of undefined (http://127.0.0.1:8080/kie-drools-wb/verifier/dtableVerifier/C1C6DDEF649DA...)
> My version is 7.14.0.Final and I also tried the latest 7.18.0.Final but no lucky. It's happend on both windows and Mac client when using the latest chrome or safari.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (DROOLS-3746) JavaScript run error when edit Guided Decision Tables on latest chrome
by Sergey Manukyan (Jira)
[ https://issues.redhat.com/browse/DROOLS-3746?page=com.atlassian.jira.plug... ]
Sergey Manukyan commented on DROOLS-3746:
-----------------------------------------
Had same issue, appeared next day suddenly, was using OSX, OpenJDK 1.8, the Decision Manager 7.7. on EAP 7.2
```15:03:03,651 ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-41) Error from user: dmAdmin Error ID: -79860134 Location: LibraryPerspective|$ProjectScreen,GuidedDecisionTableEditor?path_uri=default://master@MySpace/AAAPricing/src/main/resources/com/myspace/aaapricing/Pricing%2520Table.gdst&file_name=Pricing%20Table.gdst&has_version_support=true Exception: Uncaught exception: Uncaught TypeError: Cannot read property 'createElement' of undefined (http://localhost:8080/decision-central/verifier/dtableVerifier/3EA3E9D35E...
The workaround with ```-Dorg.kie.verification.disable-dtable-realtime-verification=true``` - helped
> JavaScript run error when edit Guided Decision Tables on latest chrome
> ----------------------------------------------------------------------
>
> Key: DROOLS-3746
> URL: https://issues.redhat.com/browse/DROOLS-3746
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 7.18.0.Final
> Reporter: xiaodong zhang
> Assignee: Toni Rikkola
> Priority: Blocker
>
> When updated to the latest chrome (72.0.3626.121), When I do edit using Guided Decision Tables, an error will throw.
> The error detail is :
> | Uncaught exception: Uncaught TypeError: Cannot read property 'createElement' of undefined (http://127.0.0.1:8080/kie-drools-wb/verifier/dtableVerifier/C1C6DDEF649DA...)
> My version is 7.14.0.Final and I also tried the latest 7.18.0.Final but no lucky. It's happend on both windows and Mac client when using the latest chrome or safari.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (DROOLS-5401) Suppress RuntimeException in ExecModelLambdaPostProcessor
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5401?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi updated DROOLS-5401:
--------------------------------------
Description:
When we hit an issue in ExecModelLambdaPostProcessor, we want to silently fall back to non-externalized lambda. Currently ExecModelLambdaPostProcessor throws RuntimeException only in unusual cases but still it's better to log and return rather than throwing RuntimeException.
Btw, we can detect non-externalized lambda with option "drools.check.nonExternalisedLambda" (DROOLS-5346).
was:
When we hit an issue in ExecModelLambdaPostProcessor, we want to silently fall back to non-externalized lambda. So it's better to log warn messages and return rather than RuntimeException.
Btw, we can detect non-externalized lambda with option "drools.check.nonExternalisedLambda" (DROOLS-5346).
> Suppress RuntimeException in ExecModelLambdaPostProcessor
> ---------------------------------------------------------
>
> Key: DROOLS-5401
> URL: https://issues.redhat.com/browse/DROOLS-5401
> Project: Drools
> Issue Type: Enhancement
> Components: executable model
> Affects Versions: 7.38.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Minor
>
> When we hit an issue in ExecModelLambdaPostProcessor, we want to silently fall back to non-externalized lambda. Currently ExecModelLambdaPostProcessor throws RuntimeException only in unusual cases but still it's better to log and return rather than throwing RuntimeException.
> Btw, we can detect non-externalized lambda with option "drools.check.nonExternalisedLambda" (DROOLS-5346).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (DROOLS-5401) Suppress RuntimeException in ExecModelLambdaPostProcessor
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5401?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi updated DROOLS-5401:
--------------------------------------
Description:
When we hit an issue in ExecModelLambdaPostProcessor, we want to silently fall back to non-externalized lambda. So it's better to log warn messages and return rather than RuntimeException.
Btw, we can detect non-externalized lambda with option "drools.check.nonExternalisedLambda" (DROOLS-5346).
was:When we hit an issue in ExecModelLambdaPostProcessor, we would silently fall back to non-externalized lambda. So we don't need to throw RuntimeException. Instead, we can detect non-externalized lambda with option "drools.check.nonExternalisedLambda" (DROOLS-5346).
> Suppress RuntimeException in ExecModelLambdaPostProcessor
> ---------------------------------------------------------
>
> Key: DROOLS-5401
> URL: https://issues.redhat.com/browse/DROOLS-5401
> Project: Drools
> Issue Type: Enhancement
> Components: executable model
> Affects Versions: 7.38.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Minor
>
> When we hit an issue in ExecModelLambdaPostProcessor, we want to silently fall back to non-externalized lambda. So it's better to log warn messages and return rather than RuntimeException.
> Btw, we can detect non-externalized lambda with option "drools.check.nonExternalisedLambda" (DROOLS-5346).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months