[JBoss JIRA] (WFLY-13386) Hung process instances and associated server.log WARN "Failed to reinstate timer 'kie-server.kie-server.EJBTimerScheduler' "
by Enrique González Martínez (Jira)
[ https://issues.redhat.com/browse/WFLY-13386?page=com.atlassian.jira.plugi... ]
Enrique González Martínez updated WFLY-13386:
---------------------------------------------
Issue Type: Bug (was: Enhancement)
> Hung process instances and associated server.log WARN "Failed to reinstate timer 'kie-server.kie-server.EJBTimerScheduler' "
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-13386
> URL: https://issues.redhat.com/browse/WFLY-13386
> Project: WildFly
> Issue Type: Bug
> Reporter: Enrique González Martínez
> Assignee: Brian Stansberry
> Priority: Major
>
> When a timer is reloaded for the first time in other node there are no listeners attached to it causing this problem (only in cluster environments with db timers)
> {code}
> 2020-04-15 16:43:57,733 WARN [org.jboss.as.ejb3.timer] (Timer-1) WFLYEJB0161: Failed to reinstate timer 'kie-server.kie-server.EJBTimerScheduler' (id=33170e5f-3b34-4503-8796-9b5e6871c074) from its persistent state: java.lang.NullPointerException
> at org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence$RefreshTask.run(DatabaseTimerPersistence.java:851)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (WFLY-13386) Hung process instances and associated server.log WARN "Failed to reinstate timer 'kie-server.kie-server.EJBTimerScheduler' "
by Enrique González Martínez (Jira)
Enrique González Martínez created WFLY-13386:
------------------------------------------------
Summary: Hung process instances and associated server.log WARN "Failed to reinstate timer 'kie-server.kie-server.EJBTimerScheduler' "
Key: WFLY-13386
URL: https://issues.redhat.com/browse/WFLY-13386
Project: WildFly
Issue Type: Enhancement
Reporter: Enrique González Martínez
Assignee: Brian Stansberry
When a timer is reloaded for the first time in other node there are no listeners attached to it causing this problem (only in cluster environments with db timers)
{code}
2020-04-15 16:43:57,733 WARN [org.jboss.as.ejb3.timer] (Timer-1) WFLYEJB0161: Failed to reinstate timer 'kie-server.kie-server.EJBTimerScheduler' (id=33170e5f-3b34-4503-8796-9b5e6871c074) from its persistent state: java.lang.NullPointerException
at org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence$RefreshTask.run(DatabaseTimerPersistence.java:851)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (WFLY-13385) Introduce ability to increase the timeout for the test which utilize CLI wrapper from shared testsuite module
by Ondrej Chaloupka (Jira)
Ondrej Chaloupka created WFLY-13385:
---------------------------------------
Summary: Introduce ability to increase the timeout for the test which utilize CLI wrapper from shared testsuite module
Key: WFLY-13385
URL: https://issues.redhat.com/browse/WFLY-13385
Project: WildFly
Issue Type: Enhancement
Components: Test Suite
Affects Versions: 19.0.0.Final
Reporter: Ondrej Chaloupka
Assignee: Ondrej Chaloupka
In Narayana CI we experience time to time a trouble of timeouting CLI operations which happens after {{reload}} is executed and just after that is run another CLI command.
We experience this with tests which use the {{CLIWrapper}} from the {{wildfly-core}} shared testsuite module (https://github.com/wildfly/wildfly-core/blob/12.0.0.Beta1/testsuite/share...)
For example test {{org.jboss.as.test.integration.management.cli.DataSourceTestCase}} (https://github.com/wildfly/wildfly/blob/19.0.0.Final/testsuite/integratio...) executes a change and then immediatelly runs {{reload}}, or other test cases which run {{reload}} and immediatelly runs some query.
When our CI is uder load then it's not capable to reload app server (or introduce changes of e.g. adding datasource to the model) in 5 seconds (which is the default {{--timeout}} for {{jboss-cli}} and fails.
{code}
testDataSource(org.jboss.as.test.integration.management.cli.DataSourceTestCase) Time elapsed: 6.102 s <<< FAILURE!
java.lang.AssertionError:
Failed to execute line 'reload'
org.jboss.as.cli.CommandLineException: java.util.concurrent.ExecutionException: org.jboss.as.cli.CommandLineException: Failed to establish connection in 6020ms
at org.jboss.as.cli.impl.CommandContextImpl.execute(CommandContextImpl.java:932)
at org.jboss.as.cli.impl.CommandContextImpl.handleLegacyCommand(CommandContextImpl.java:1902)
at org.jboss.as.cli.impl.CommandContextImpl.handle(CommandContextImpl.java:869)
at org.jboss.as.test.integration.management.util.CLIWrapper.sendLine(CLIWrapper.java:218)
at org.jboss.as.test.integration.management.util.CLIWrapper.sendLine(CLIWrapper.java:244)
at org.jboss.as.test.integration.management.cli.DataSourceTestCase.testRemoveDataSource(DataSourceTestCase.java:160)
at org.jboss.as.test.integration.management.cli.DataSourceTestCase.testDataSource(DataSourceTestCase.java:82)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
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.invokeMethod(Arquillian.java:325)
at org.jboss.arquillian.junit.MethodInvoker$1.invoke(MethodInvoker.java:18)
at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:57)
at sun.reflect.GeneratedMethodAccessor53.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:62)
at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:50)
at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:128)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:118)
at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:83)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:69)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:116)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:139)
at org.jboss.arquillian.junit.MethodInvoker.invoke(MethodInvoker.java:15)
at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:332)
at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:204)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:350)
at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54)
at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:215)
at org.jboss.arquillian.junit.Arquillian$7$1.invoke(Arquillian.java:279)
at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:88)
at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:66)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:128)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:114)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:83)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:69)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:116)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.fireCustomLifecycle(EventTestRunnerAdaptor.java:159)
at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:273)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:166)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:350)
at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54)
at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:177)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:115)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
Caused by: java.util.concurrent.ExecutionException: org.jboss.as.cli.CommandLineException: Failed to establish connection in 6020ms
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at org.jboss.as.cli.impl.CommandExecutor.execute(CommandExecutor.java:713)
at org.jboss.as.cli.impl.CommandExecutor.execute(CommandExecutor.java:694)
at org.jboss.as.cli.impl.CommandContextImpl.lambda$handleLegacyCommand$4(CommandContextImpl.java:1903)
at org.jboss.as.cli.impl.CommandContextImpl.execute(CommandContextImpl.java:919)
... 125 more
Caused by: org.jboss.as.cli.CommandLineException: Failed to establish connection in 6020ms
at org.jboss.as.cli.handlers.ReloadHandler.ensureServerRebootComplete(ReloadHandler.java:332)
at org.jboss.as.cli.handlers.ReloadHandler.doHandle(ReloadHandler.java:231)
at org.jboss.as.cli.handlers.CommandHandlerWithHelp.handle(CommandHandlerWithHelp.java:89)
at org.jboss.as.cli.impl.CommandExecutor$2.lambda$build$0(CommandExecutor.java:685)
at org.jboss.as.cli.impl.CommandExecutor.lambda$execute$0(CommandExecutor.java:708)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (DROOLS-4084) Export to Excel for decision tables 7.5
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-4084?page=com.atlassian.jira.plug... ]
Jozef Marko closed DROOLS-4084.
-------------------------------
Resolution: Done
> Export to Excel for decision tables 7.5
> ---------------------------------------
>
> Key: DROOLS-4084
> URL: https://issues.redhat.com/browse/DROOLS-4084
> Project: Drools
> Issue Type: Epic
> Components: Guided Decision Table Editor
> Affects Versions: 7.23.0.Final
> Reporter: Jozef Marko
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> This is a community epic for the BAPL-1169. The epic was created according to the [definition of done|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4o...] that advices what needs to be agreed before each feature implementation.
> h1. Requirement
> - As a user of the feature I want to convert guided decision table by single click to xls (Excel) format.
> - The converted table should have the same format as is supported for importing into business central.
> - The converted table should visually differentiate column and row types (constraint vs. action, metadata vs. data)
> - The conversion should support Simple GDT column
> - The conversion should support Brl GDT column
> - The conversion should support Attribute and Metadata columns
> - The converted table can be opened on Windows and Linux
> - The converted table split lines
> - The converted table support multibyte characters
> - The conversion of GDT graph is possible
> - User is prompted to save changes before conversion
> - Converted table is not stored in kie project, just downloaded via browser
> h1. UX design
> - Placement of the conversion button
> - Text of the conversion button
> - Dialog for case we support save changes before conversion
> h1. Documentation
> - Replace picture of GDT editor where they become obsolete
> - Comprehensive doc is probably not needed
> h1. Acceptance test
> - Convert table that
> -- Has more that 100 lines
> -- Has one Metadata column
> -- Has one Attribute column
> -- Has three constraint columns( two over same fact )
> -- Has three action columns( two over same fact )
> -- Has not all cells filled in
> -- Operates over String, Number, Boolean fields
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (DROOLS-5219) [DMN Designer] Multiple output columns in decision table
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5219?page=com.atlassian.jira.plug... ]
Jozef Marko closed DROOLS-5219.
-------------------------------
Resolution: Duplicate
> [DMN Designer] Multiple output columns in decision table
> --------------------------------------------------------
>
> Key: DROOLS-5219
> URL: https://issues.redhat.com/browse/DROOLS-5219
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.36.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: multicolumn-decision-table.webm
>
>
> The issue is when user tries to create a decision table expression with multiple output columns.
> To achieve this user needs to invoke context menu with items 'Insert left / Insert right'. User has two options. He can invoke such menu from 'data' cell and 'header' cell.
> For data cells the feature works fine, however for header cells the operation fails and an error is shown. For more details see the video.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (WFLY-13267) Convert EJB3 subsystem transformers to use chained transformers
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFLY-13267?page=com.atlassian.jira.plugi... ]
Richard Achmatowicz commented on WFLY-13267:
--------------------------------------------
I have added transformer tests for EAP 7.0.0, 7.1.0 and 7.2.0 which are long overdue.
I also refactored the transformers to use chained transformers, so that in future, only transformers from current to the most recent version will be required.
> Convert EJB3 subsystem transformers to use chained transformers
> ---------------------------------------------------------------
>
> Key: WFLY-13267
> URL: https://issues.redhat.com/browse/WFLY-13267
> Project: WildFly
> Issue Type: Task
> Components: EJB
> Affects Versions: 19.0.0.Final
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Major
> Fix For: 20.0.0.Beta1
>
>
> The EJB3 subsystem defines its subsystem transformers in the class org.jboss.as.ejb3.subsystem.EJBTransformers.
> This class organizes transformers in 'the old way' (see https://docs.jboss.org/author/display/WFLY/Domain+Mode+Subsystem+Transfor...), so that there is a lot of code duplication.
> This issue will reorganize the transformers to use the chained transformer technique, where only the changes from the current version to the most recent legacy version need be specified.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months