September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2973) Revisit the XML and XStream format and setup for Scenario Simulation

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2973?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-2973: --------------------------------- Story Points: 1 > Revisit the XML and XStream format and setup for Scenario Simulation > -------------------------------------------------------------------- > > Key: DROOLS-2973 > URL: https://issues.jboss.org/browse/DROOLS-2973 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Toni Rikkola > Assignee: Toni Rikkola > > Things to check: > * Use aliases instead of full fqcn names > * Include a version number for the XML -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2973) Revisit the XML and XStream format and setup for Scenario Simulation

by Toni Rikkola (JIRA)

Toni Rikkola created DROOLS-2973: ------------------------------------ Summary: Revisit the XML and XStream format and setup for Scenario Simulation Key: DROOLS-2973 URL: https://issues.jboss.org/browse/DROOLS-2973 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing Reporter: Toni Rikkola Assignee: Toni Rikkola Things to check: * Use aliases instead of full fqcn names * Include a version number for the XML -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2972) Scorecards tests from drools-scorecards are failing randomly

by Tibor Zimányi (JIRA)

Tibor Zimányi created DROOLS-2972: ------------------------------------- Summary: Scorecards tests from drools-scorecards are failing randomly Key: DROOLS-2972 URL: https://issues.jboss.org/browse/DROOLS-2972 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.11.0.Final Reporter: Tibor Zimányi Assignee: Tibor Zimányi Scorecards tests are failing randomly on Jenkins with following stacktrace [1]. [1] https://gist.github.com/baldimir/420bb0d3ca3ce15562a49132a4ad1661 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2919) [DMN Designer] Data-types: Clean-up

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2919?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2919: -------------------------------- Description: During review of the PRs adding support to the different grids, both [~jomarko] and [~karreiro] found some re-occurring issues that need addressing. Rather than fix at the point of discovery, i.e. when my colleagues review the PR, I prefer to circle back and fix all together once the queue of pending PRs are merged. Current action items: * (/) https://github.com/kiegroup/kie-wb-common/pull/2055#discussion_r212084447 * (/) https://github.com/kiegroup/kie-wb-common/pull/2041#discussion_r212250221 * (/) https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... and https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... - check for other occurrences too. If we pass a parameter as to whether to update "Stunner" title or not we can remove these methods accessing the super implementation. * (/) Review whether _legacy_ {{BaseExpressionGrid.HeaderTextAreaFactory}} related methods are required when all grids support "in place" editing of name and data-type. Removing if possible. h2. Acceptance test Data type can be changed for - All supported node types - All supported expression types was: During review of the PRs adding support to the different grids, both [~jomarko] and [~karreiro] found some re-occurring issues that need addressing. Rather than fix at the point of discovery, i.e. when my colleagues review the PR, I prefer to circle back and fix all together once the queue of pending PRs are merged. Current action items: * (/) https://github.com/kiegroup/kie-wb-common/pull/2055#discussion_r212084447 * (/) https://github.com/kiegroup/kie-wb-common/pull/2041#discussion_r212250221 * (/) https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... and https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... - check for other occurrences too. If we pass a parameter as to whether to update "Stunner" title or not we can remove these methods accessing the super implementation. * (/) Review whether _legacy_ {{BaseExpressionGrid.HeaderTextAreaFactory}} related methods are required when all grids support "in place" editing of name and data-type. Removing if possible. h2. Acceptance test Data type can be changed for - All node supported node types - All supported expression types > [DMN Designer] Data-types: Clean-up > ----------------------------------- > > Key: DROOLS-2919 > URL: https://issues.jboss.org/browse/DROOLS-2919 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Labels: drools-tools > > During review of the PRs adding support to the different grids, both [~jomarko] and [~karreiro] found some re-occurring issues that need addressing. Rather than fix at the point of discovery, i.e. when my colleagues review the PR, I prefer to circle back and fix all together once the queue of pending PRs are merged. > Current action items: > * (/) https://github.com/kiegroup/kie-wb-common/pull/2055#discussion_r212084447 > * (/) https://github.com/kiegroup/kie-wb-common/pull/2041#discussion_r212250221 > * (/) https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... and https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... - check for other occurrences too. If we pass a parameter as to whether to update "Stunner" title or not we can remove these methods accessing the super implementation. > * (/) Review whether _legacy_ {{BaseExpressionGrid.HeaderTextAreaFactory}} related methods are required when all grids support "in place" editing of name and data-type. Removing if possible. > h2. Acceptance test > Data type can be changed for > - All supported node types > - All supported expression types -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2919) [DMN Designer] Data-types: Clean-up

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2919?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2919: -------------------------------- Description: During review of the PRs adding support to the different grids, both [~jomarko] and [~karreiro] found some re-occurring issues that need addressing. Rather than fix at the point of discovery, i.e. when my colleagues review the PR, I prefer to circle back and fix all together once the queue of pending PRs are merged. Current action items: * (/) https://github.com/kiegroup/kie-wb-common/pull/2055#discussion_r212084447 * (/) https://github.com/kiegroup/kie-wb-common/pull/2041#discussion_r212250221 * (/) https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... and https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... - check for other occurrences too. If we pass a parameter as to whether to update "Stunner" title or not we can remove these methods accessing the super implementation. * (/) Review whether _legacy_ {{BaseExpressionGrid.HeaderTextAreaFactory}} related methods are required when all grids support "in place" editing of name and data-type. Removing if possible. h2. Acceptance test Data type can be changed for - All node supported node types - All supported expression types was: During review of the PRs adding support to the different grids, both [~jomarko] and [~karreiro] found some re-occurring issues that need addressing. Rather than fix at the point of discovery, i.e. when my colleagues review the PR, I prefer to circle back and fix all together once the queue of pending PRs are merged. Current action items: * (/) https://github.com/kiegroup/kie-wb-common/pull/2055#discussion_r212084447 * (/) https://github.com/kiegroup/kie-wb-common/pull/2041#discussion_r212250221 * (/) https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... and https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... - check for other occurrences too. If we pass a parameter as to whether to update "Stunner" title or not we can remove these methods accessing the super implementation. * (/) Review whether _legacy_ {{BaseExpressionGrid.HeaderTextAreaFactory}} related methods are required when all grids support "in place" editing of name and data-type. Removing if possible. > [DMN Designer] Data-types: Clean-up > ----------------------------------- > > Key: DROOLS-2919 > URL: https://issues.jboss.org/browse/DROOLS-2919 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Labels: drools-tools > > During review of the PRs adding support to the different grids, both [~jomarko] and [~karreiro] found some re-occurring issues that need addressing. Rather than fix at the point of discovery, i.e. when my colleagues review the PR, I prefer to circle back and fix all together once the queue of pending PRs are merged. > Current action items: > * (/) https://github.com/kiegroup/kie-wb-common/pull/2055#discussion_r212084447 > * (/) https://github.com/kiegroup/kie-wb-common/pull/2041#discussion_r212250221 > * (/) https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... and https://github.com/kiegroup/kie-wb-common/pull/2075/files#diff-5192d74da9... - check for other occurrences too. If we pass a parameter as to whether to update "Stunner" title or not we can remove these methods accessing the super implementation. > * (/) Review whether _legacy_ {{BaseExpressionGrid.HeaderTextAreaFactory}} related methods are required when all grids support "in place" editing of name and data-type. Removing if possible. > h2. Acceptance test > Data type can be changed for > - All node supported node types > - All supported expression types -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1108) Wildfly 9.0.1 Final fails next day with WFLYDS0032: Failed to list files in directory

by Fengxu Guo (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1108?page=com.atlassian.jira.plugi... ] Fengxu Guo commented on WFCORE-1108: ------------------------------------ Hi team, Did you fix this bug? I met this issue , if you have any update please let me know . thanks > Wildfly 9.0.1 Final fails next day with WFLYDS0032: Failed to list files in directory > ---------------------------------------------------------------------------------------- > > Key: WFCORE-1108 > URL: https://issues.jboss.org/browse/WFCORE-1108 > Project: WildFly Core > Issue Type: Bug > Environment: Wildfly 9.0.1 Final > Reporter: George Leon > Assignee: ehsavoie Hugonnet > > Hi all, > First Wildlfly is the best Bravo from Greece . > > > We have wildfly 9.0.1 Final installed as root and all folders are owner root > we deployed our web app (war) via the Web UI administration everything works for several hours the next day we come to work and Wildlfly fails with error below any help is very welcome > > ls /opt/wildfly-9.0.1.Final/standalone/deployments > drwxr-xr-x. 3 root root 4096 Sep 16 14:24 configuration > drwxr-xr-x. 8 root root 4096 Sep 10 11:20 data > drwxr-xr-x. 2 root root 23 Jul 23 21:01 deployments > drwxr-xr-x. 3 root root 16 Jul 23 21:01 lib > drwxr-xr-x. 2 root root 4096 Sep 18 00:00 log > drwxr-xr-x. 7 root root 94 Sep 16 14:24 tmp > > > 2015-09-18 10:02:41,735 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0012: Scan of /opt/wildfly-9.0.1.Final/standalone/deployments threw Exception: java.lang.RuntimeException: WFLYDS0032: Failed to list files in directory /opt/wildfly-9.0.1.Final/standalone/deployments. Check that the contents of the directory are readable. > at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.listDirectoryChildren(FileSystemDeploymentService.java:1170) > at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.scanDirectory(FileSystemDeploymentService.java:664) > at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.scan(FileSystemDeploymentService.java:474) > at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.scan(FileSystemDeploymentService.java:393) > at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$DeploymentScanRunnable.run(FileSystemDeploymentService.java:161) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > > > Thanks -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10964) JPA statistics do not show in the management console

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-10964?page=com.atlassian.jira.plugin... ] Scott Marlow closed WFLY-10964. ------------------------------- > JPA statistics do not show in the management console > ---------------------------------------------------- > > Key: WFLY-10964 > URL: https://issues.jboss.org/browse/WFLY-10964 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 14.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 15.0.0.Alpha1 > > > Currently, the following "Unknown entity" error shows up in the server console: > {code} > 2018-09-04 12:01:32,740 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "JpaStatisticsTestCase.jar" (runtime-name : "JpaStatisticsTestCase.jar") > 2018-09-04 12:01:32,810 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("read-attribute") failed - address: ([ > ("deployment" => "JpaStatisticsTestCase.jar"), > ("subsystem" => "jpa"), > ("hibernate-persistence-unit" => "JpaStatisticsTestCase.jar#mypc"), > ("entity" => "org.jboss.as.test.integration.jpa.secondlevelcache.Company") > ]): org.hibernate.MappingException: Unknown entity: entity-update-count > at org.hibernate.metamodel.internal.MetamodelImpl.entityPersister(MetamodelImpl.java:670) > at org.hibernate.stat.internal.StatisticsImpl.lambda$getEntityStatistics$0(StatisticsImpl.java:215) > at java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1660) > at org.hibernate.stat.internal.StatisticsImpl.getEntityStatistics(StatisticsImpl.java:213) > at org.hibernate.stat.internal.StatisticsImpl.getEntityStatistics(StatisticsImpl.java:32) > at org.jboss.as.jpa.hibernate5.management.HibernateEntityStatistics.getStatistics(HibernateEntityStatistics.java:86) > at org.jboss.as.jpa.hibernate5.management.HibernateEntityStatistics.access$000(HibernateEntityStatistics.java:37) > at org.jboss.as.jpa.hibernate5.management.HibernateEntityStatistics$5.invoke(HibernateEntityStatistics.java:126) > at org.jboss.as.jpa.hibernate5.management.HibernateAbstractStatistics.getValue(HibernateAbstractStatistics.java:99) > at org.jboss.as.jpa.management.ManagementResourceDefinition$1.handle(ManagementResourceDefinition.java:130) > at org.jboss.as.jpa.management.ManagementResourceDefinition$AbstractMetricsHandler.executeRuntimeStep(ManagementResourceDefinition.java:268) > at org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:59) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1411) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:265) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:231) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:289) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:246) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {code} > Fix this bug and add test to testsuite for this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-330) Pipeline Support For Productized Kiali

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-330?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-330. ------------------------------------------- Resolution: Done Kiali is ready to be installed when it is back to the operator. It depends on https://github.com/Maistra/istio-operator/pull/2 and https://github.com/Maistra/openshift-ansible/pull/6 > Pipeline Support For Productized Kiali > -------------------------------------- > > Key: SWSQE-330 > URL: https://issues.jboss.org/browse/SWSQE-330 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > > Add Support for Productized Kiali -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-330) Pipeline Support For Productized Kiali

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-330?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-330: ------------------------------------------ Team: (was: Infrastructure) > Pipeline Support For Productized Kiali > -------------------------------------- > > Key: SWSQE-330 > URL: https://issues.jboss.org/browse/SWSQE-330 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > > Add Support for Productized Kiali -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-331) Support Produtized Builds

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-331?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-331: ------------------------------------------ Description: Create a CR > Support Produtized Builds > ------------------------- > > Key: SWSQE-331 > URL: https://issues.jboss.org/browse/SWSQE-331 > Project: Kiali QE > Issue Type: Story > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > > Create a CR -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 September 2018