June 2020 - jboss-jira - Jboss List Archives

[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)

6 years, 1 month

1
0
0 / 0

[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)

6 years, 1 month

1
0
0 / 0

[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)

6 years, 1 month

1
0
0 / 0

[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)

6 years, 1 month

1
0
0 / 0

[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: -------------------------------------- Priority: Minor (was: Major) > 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 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). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[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 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). (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.) > 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: Major > > 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). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5401) Suppress RuntimeException in ExecModelLambdaPostProcessor

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-5401: ----------------------------------------- Summary: 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 When we hit an issue in ExecModelLambdaPostProcessor, we would silently fall back to non-externalized lambda. So we don't need to throw RuntimeException. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10173) EjbInvocationStatisticsTestCase fails on Windows: wait-time=0

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-10173?page=com.atlassian.jira.plugi... ] Cheng Fang commented on WFLY-10173: ----------------------------------- This test has a success rate of 96.7% in recent WF CI jobs. So I'll think more of a reliable way of testing singleton wait time. > EjbInvocationStatisticsTestCase fails on Windows: wait-time=0 > ------------------------------------------------------------- > > Key: WFLY-10173 > URL: https://issues.redhat.com/browse/WFLY-10173 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 12.0.0.Final > Reporter: Jan Kalina > Assignee: Cheng Fang > Priority: Major > Fix For: 20.0.0.Final > > > Sometime, when running EjbInvocationStatisticsTestCase on Windows, assertion fails, as wait-time is 0 (verified it is 0 by adding debug message). > For me it fails allTests in most of cases, but when running test standalone, it fails only in 1 of 4 cases. > I suppose it is because of too short sleep in AbstractManagedBean. (in test is called 4 times, each invocation include 50ms sleep, so I consider probable the wait-time is 0 - need to use longer sleeps to fulfill the test) > {code} > [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.078 s <<< FAILURE! - in org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase > [ERROR] testSingletonWaitTime(org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase) Time elapsed: 0.438 s <<< FAILURE! > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase.validateWaitTimeStatistic(EjbInvocationStatisticsTestCase.java:179) > at org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase.testSingletonWaitTime(EjbInvocationStatisticsTestCase.java:148) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:564) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.jboss.arquillian.junit.Arquillian$8$1.invoke(Arquillian.java:379) > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1979) Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl package

by Brian Stansberry (Jira)

Brian Stansberry created ELY-1979: ------------------------------------- Summary: Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl package Key: ELY-1979 URL: https://issues.redhat.com/browse/ELY-1979 Project: WildFly Elytron Issue Type: Bug Components: SSL Affects Versions: 1.12.0.Final Reporter: Brian Stansberry JEPS 244, available in JDK 9 or later and in JDK 8 since the 251 release[1] has added new methods to some of the javax.net.ssl classes that elytron wraps in org.wildfly.security.ssl. But the elytron classes do not handle those new methods. I believe the relevant change is at [2] and updates the SSLEngine, SSLParameters and SSLSocket classes (plus various non-javax classes.) If Elytron were to require 251 or later to build perhaps this could be a simple matter of adding new methods to the wrappers and calling the delegate, under the expectation that at runtime the wrapper methods would not be invoked in a JVM < 251. Or the wrappers could use reflection and throw a UOE if the methods are not available. [1] https://www.oracle.com/technetwork/java/javase/8u251-relnotes-5972664.htm... [2] https://hg.openjdk.java.net/jdk8u/jdk8u41/jdk/rev/b26b096d4c89 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13551) Upgrade wildfly-naming-client to 1.0.13.Final

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13551?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13551: ------------------------------------ Description: Pick up https://issues.redhat.com/browse/WFNC-57 https://github.com/wildfly/wildfly-naming-client/compare/1.0.12.Final...1... was:Pick up https://issues.redhat.com/browse/WFNC-57 > Upgrade wildfly-naming-client to 1.0.13.Final > --------------------------------------------- > > Key: WFLY-13551 > URL: https://issues.redhat.com/browse/WFLY-13551 > Project: WildFly > Issue Type: Component Upgrade > Components: Naming > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 20.0.0.Final > > > Pick up https://issues.redhat.com/browse/WFNC-57 > https://github.com/wildfly/wildfly-naming-client/compare/1.0.12.Final...1... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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 June 2020