[JBoss JIRA] (WFLY-11550) Provide ability to suspend and resume the set of servers managed by a specific host controller
by Yeray Borges (Jira)
[ https://issues.jboss.org/browse/WFLY-11550?page=com.atlassian.jira.plugin... ]
Yeray Borges moved WFCORE-4264 to WFLY-11550:
---------------------------------------------
Project: WildFly (was: WildFly Core)
Key: WFLY-11550 (was: WFCORE-4264)
Component/s: Documentation
(was: CLI)
(was: Management)
> Provide ability to suspend and resume the set of servers managed by a specific host controller
> ----------------------------------------------------------------------------------------------
>
> Key: WFLY-11550
> URL: https://issues.jboss.org/browse/WFLY-11550
> Project: WildFly
> Issue Type: Feature Request
> Components: Documentation
> Reporter: Yeray Borges
> Assignee: Yeray Borges
> Priority: Major
>
> In WildFly 10 we introduced the server suspend/resume and graceful shutdown feature. This feature allows the server to complete the active requests normally, without accepting any new requests. A timeout value specifies how long the suspend or shutdown operation waits for active request to complete.
> However, there are no specific operations to suspend/resume and shutdown gracefully all servers managed by a specific host controller. These operations can be applied only at server-group or whole domain level. The goal of this issue is to facilitate these tasks to the administrators.
> Additionally, the timeout attribute for all of those lifecycle operations will be renamed to suspend-timeout to avoid the confusion of this value with timeout applied to the entire operation. The suspend-timeout attribute has a meaning only for the timeout applied to suspend the servers.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFCORE-1427) Provide ability to suspend and resume the set of servers managed by a specific host controller
by Yeray Borges (Jira)
[ https://issues.jboss.org/browse/WFCORE-1427?page=com.atlassian.jira.plugi... ]
Yeray Borges updated WFCORE-1427:
---------------------------------
Description:
In WildFly 10 we introduced the server suspend/resume and graceful shutdown feature. This feature allows the server to complete the active requests normally, without accepting any new requests. A timeout value specifies how long the suspend or shutdown operation waits for active request to complete.
However, there are no specific operations to suspend/resume and shutdown gracefully all servers managed by a specific host controller. These operations can be applied only at server-group or whole domain level. The goal of this issue is to facilitate these tasks to the administrators.
Additionally, the timeout attribute for all of those lifecycle operations will be renamed to suspend-timeout to avoid the confusion of this value with timeout applied to the entire operation. The suspend-timeout attribute has a meaning only for the timeout applied to suspend the servers.
was:
So instead of
{code}
:suspend(20)
:reload
{code}
It's just
{code}
:reload(20)
{code}
The high level 'reload' command in the CLI should take a --timeout param as well.
If doing the graceful suspend as part of server side ":reload" handling proves problematic (I haven't looked into it at all before filing this) then a simpler alternative is to only go with the --timeout param on the CLI reload command, and have the CLI implement the graceful behavior internally by first calling :suspend and then :reload. Web console could do the same thing.
> Provide ability to suspend and resume the set of servers managed by a specific host controller
> ----------------------------------------------------------------------------------------------
>
> Key: WFCORE-1427
> URL: https://issues.jboss.org/browse/WFCORE-1427
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI, Management
> Reporter: Brian Stansberry
> Assignee: Yeray Borges
> Priority: Major
>
> In WildFly 10 we introduced the server suspend/resume and graceful shutdown feature. This feature allows the server to complete the active requests normally, without accepting any new requests. A timeout value specifies how long the suspend or shutdown operation waits for active request to complete.
> However, there are no specific operations to suspend/resume and shutdown gracefully all servers managed by a specific host controller. These operations can be applied only at server-group or whole domain level. The goal of this issue is to facilitate these tasks to the administrators.
> Additionally, the timeout attribute for all of those lifecycle operations will be renamed to suspend-timeout to avoid the confusion of this value with timeout applied to the entire operation. The suspend-timeout attribute has a meaning only for the timeout applied to suspend the servers.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFCORE-4264) Provide ability to suspend and resume the set of servers managed by a specific host controller
by Yeray Borges (Jira)
Yeray Borges created WFCORE-4264:
------------------------------------
Summary: Provide ability to suspend and resume the set of servers managed by a specific host controller
Key: WFCORE-4264
URL: https://issues.jboss.org/browse/WFCORE-4264
Project: WildFly Core
Issue Type: Feature Request
Components: CLI, Management
Reporter: Yeray Borges
Assignee: Yeray Borges
In WildFly 10 we introduced the server suspend/resume and graceful shutdown feature. This feature allows the server to complete the active requests normally, without accepting any new requests. A timeout value specifies how long the suspend or shutdown operation waits for active request to complete.
However, there are no specific operations to suspend/resume and shutdown gracefully all servers managed by a specific host controller. These operations can be applied only at server-group or whole domain level. The goal of this issue is to facilitate these tasks to the administrators.
Additionally, the timeout attribute for all of those lifecycle operations will be renamed to suspend-timeout to avoid the confusion of this value with timeout applied to the entire operation. The suspend-timeout attribute has a meaning only for the timeout applied to suspend the servers.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-11372) Latest DB2 11.1 JDBC driver requires additional IBM JDK system dependency
by Lin Gao (Jira)
[ https://issues.jboss.org/browse/WFLY-11372?page=com.atlassian.jira.plugin... ]
Lin Gao reassigned WFLY-11372:
------------------------------
Assignee: Lin Gao (was: Stefano Maestri)
> Latest DB2 11.1 JDBC driver requires additional IBM JDK system dependency
> -------------------------------------------------------------------------
>
> Key: WFLY-11372
> URL: https://issues.jboss.org/browse/WFLY-11372
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading, JCA
> Affects Versions: 14.0.0.Final, 15.0.0.Beta1
> Environment: IBM DB2 11.1 JDBC driver (version 4.24.92)
> IBM JDK 8:
> {noformat}
> $ java -version
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 8.0.5.22 - pxa6480sr5fp22-20180919_01(SR5 FP22))
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20180915_397057 (JIT enabled, AOT enabled)
> OpenJ9 - 6c152c2
> OMR - 15647c3
> IBM - d734883)
> JCL - 20180821_01 based on Oracle jdk8u181-b12
> {noformat}
> Reporter: Martin Simka
> Assignee: Lin Gao
> Priority: Critical
>
> Running on IBM JDK 8 latest DB2 11.1 JDBC driver (version 4.24.92) fails to connect to database with error:
> {noformat}
> Caused by: java.lang.NoClassDefFoundError: com/ibm/dataaccess/ByteArrayUnmarshaller
> at com.ibm.db2.jcc.a.j.h(j.java:21)
> at com.ibm.db2.jcc.a.i.g(i.java:151)
> at com.ibm.db2.jcc.a.i.b(i.java:76)
> at com.ibm.db2.jcc.t4.y.q(y.java:1373)
> at com.ibm.db2.jcc.t4.z.c(z.java:4792)
> at com.ibm.db2.jcc.t4.z.b(z.java:4740)
> at com.ibm.db2.jcc.t4.z.a(z.java:4726)
> at com.ibm.db2.jcc.t4.z.l(z.java:547)
> at com.ibm.db2.jcc.t4.z.d(z.java:153)
> at com.ibm.db2.jcc.t4.b.k(b.java:1442)
> at com.ibm.db2.jcc.t4.b.b(b.java:1354)
> at com.ibm.db2.jcc.t4.b.a(b.java:6687)
> at com.ibm.db2.jcc.t4.b.b(b.java:888)
> ... 244 more
> {noformat}
> It doesn't matter whether driver is installed as module or deployed to deployments folder.
> DB2 11.1 driver versions
> || Driver version|| status ||
> | 4.21.29 | OK |
> | 4.22.29 | OK |
> | 4.23.42 | Fail |
> | 4.24.92 | Fail |
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-11504) Some hibernate tests fail with security on IBM Java 8: HHH000142
by Ondrej Kotek (Jira)
[ https://issues.jboss.org/browse/WFLY-11504?page=com.atlassian.jira.plugin... ]
Ondrej Kotek updated WFLY-11504:
--------------------------------
Environment: IBM Java 8, build 8.0.5.25 (was: IBM Java 8)
> Some hibernate tests fail with security on IBM Java 8: HHH000142
> ----------------------------------------------------------------
>
> Key: WFLY-11504
> URL: https://issues.jboss.org/browse/WFLY-11504
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate, Test Suite
> Affects Versions: 16.0.0.Beta1
> Environment: IBM Java 8, build 8.0.5.25
> Reporter: Ondrej Kotek
> Assignee: Scott Marlow
> Priority: Major
> Attachments: org.jboss.as.test.integration.jpa.hibernate.entitytest.EntityTestCase-output.txt
>
>
> Seven hibernate tests fail with security on IBM Java 8, for example:
> {noformat}
> org.hibernate.HibernateException: HHH000142: Bytecode enhancement failed: org.jboss.as.test.integration.jpa.hibernate.Employee
> {noformat}
> Affected test cases:
> * {{org.jboss.as.test.integration.jpa.hibernate.entitytest.EntityTestCase}}
> * {{org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverOnetoManyJoinColumnTest}}
> * {{org.jboss.as.test.integration.jpa.hibernate.envers.basicenverstest.BasicEnversTestCase}}
> * {{org.jboss.as.test.integration.jpa.hibernate.envers.basicselectiveenverstest.BasicSelectiveEnversTestCase}}
> * {{org.jboss.as.test.integration.jpa.hibernate.envers.implementvalidityauditstrategytest.ImplementValidityAuditStrategyTestCase}}
> * {{org.jboss.as.test.integration.jpa.hibernate.envers.validityauditstrategyoninheritancetest.ValidityAuditStrategyonInheritanceTestCase}}
> * {{org.jboss.as.test.integration.jpa.hibernate.sessionfactorytest.SessionFactoryTestCase}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-3465) [DMN Designer] ContextGrid and DecisionTableGrid selectFirstCell() regression
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3465?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3465:
-----------------------------------
Tester: Jozef Marko
Labels: drools-tools (was: )
> [DMN Designer] ContextGrid and DecisionTableGrid selectFirstCell() regression
> -----------------------------------------------------------------------------
>
> Key: DROOLS-3465
> URL: https://issues.jboss.org/browse/DROOLS-3465
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> (Programmatic) selection of the "first cell" in both the {{ContextGrid}} and {{DecisionTableGrid}} has regressed. Selection should ignore the "row number" column however changes adding explicit "Row number columns" for the foregoing grids that do not extend {{RowNumberColumn}} have caused the expected behaviour to break.
> h2. Acceptance criteria
> # Create new Decision
> # Set expression to either {{Context}} or {{DecisionTable}}
> # The whole row should not be selected, only one cell.
> # Check other expression types.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-3465) [DMN Designer] ContextGrid and DecisionTableGrid selectFirstCell() regression
by Michael Anstis (Jira)
Michael Anstis created DROOLS-3465:
--------------------------------------
Summary: [DMN Designer] ContextGrid and DecisionTableGrid selectFirstCell() regression
Key: DROOLS-3465
URL: https://issues.jboss.org/browse/DROOLS-3465
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.15.0.Final
Reporter: Michael Anstis
Assignee: Michael Anstis
(Programmatic) selection of the "first cell" in both the {{ContextGrid}} and {{DecisionTableGrid}} has regressed. Selection should ignore the "row number" column however changes adding explicit "Row number columns" for the foregoing grids that do not extend {{RowNumberColumn}} have caused the expected behaviour to break.
h2. Acceptance criteria
# Create new Decision
# Set expression to either {{Context}} or {{DecisionTable}}
# The whole row should not be selected, only one cell.
# Check other expression types.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-1781) Investigate possible replacement of findbugs-maven-plugin with spotbugs-maven-plugin
by Geoffrey De Smet (Jira)
[ https://issues.jboss.org/browse/DROOLS-1781?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet commented on DROOLS-1781:
------------------------------------------
[~rsynek] Seeing as most of the work is already done by MichaelB I think the sonarcloud future work shouldn't prevent MichaelB from wrapping this up in the present. So let's get this through.
That being said, I am big fan of the sonarcloud work.
> Investigate possible replacement of findbugs-maven-plugin with spotbugs-maven-plugin
> ------------------------------------------------------------------------------------
>
> Key: DROOLS-1781
> URL: https://issues.jboss.org/browse/DROOLS-1781
> Project: Drools
> Issue Type: Task
> Components: build
> Affects Versions: 7.4.1.Final
> Reporter: Petr Široký
> Assignee: Michael Biarnes Kiefer
> Priority: Major
> Labels: java9
>
> SpotBugs is a successor of FingBugs and as such uses different groupId + artifactId for maven plugin. It should also be compatible with Java 9 (at least in the latest versions). We need to investigate it the switch is painless and if so, do it. Otherwise we need to figure out what the blockers are and slowly start to fix them as FindBugs itself won't bet any more updates it seems and so won't be Java 9 compatible.
> *How to migrate*
> * Replace
> {code}
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>findbugs-maven-plugin</artifactId>
> {code}
> by
> {code}
> <groupId>com.github.spotbugs</groupId>
> <artifactId>spotbugs-maven-plugin</artifactId>
> {code}
> * Look for all "findbugs" and replace it by "spotbugs"
> ** Except for anything related to the findbugs annotations dependency that some dependencies drag in or exclude. Leave that one alone!
> ** For example, change findbugs-check -> spotbugs-check, ...
> * Merge this PR if it hasn't been merged already: https://github.com/kiegroup/optaplanner-wb/pull/320
> * Then you only need to adjust the following repo's: build-boostrap, drools, optaplanner and kie-wb-distributions.
> ** See https://github.com/search?q=org%3Akiegroup+findbugs-maven-plugin&type=Code
> ** Ignore contributed experiments, that repo is dead
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-1781) Investigate possible replacement of findbugs-maven-plugin with spotbugs-maven-plugin
by Radovan Synek (Jira)
[ https://issues.jboss.org/browse/DROOLS-1781?page=com.atlassian.jira.plugi... ]
Radovan Synek commented on DROOLS-1781:
---------------------------------------
With SonarCloud showing up in some repositories - and my plan is to integrate it to entire KIE group - findbugs/spotbugs becomes a redundant tool. The only benefit of keeping this plugin is to provide some level of checking to developers even before they open a PR.
> Investigate possible replacement of findbugs-maven-plugin with spotbugs-maven-plugin
> ------------------------------------------------------------------------------------
>
> Key: DROOLS-1781
> URL: https://issues.jboss.org/browse/DROOLS-1781
> Project: Drools
> Issue Type: Task
> Components: build
> Affects Versions: 7.4.1.Final
> Reporter: Petr Široký
> Assignee: Michael Biarnes Kiefer
> Priority: Major
> Labels: java9
>
> SpotBugs is a successor of FingBugs and as such uses different groupId + artifactId for maven plugin. It should also be compatible with Java 9 (at least in the latest versions). We need to investigate it the switch is painless and if so, do it. Otherwise we need to figure out what the blockers are and slowly start to fix them as FindBugs itself won't bet any more updates it seems and so won't be Java 9 compatible.
> *How to migrate*
> * Replace
> {code}
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>findbugs-maven-plugin</artifactId>
> {code}
> by
> {code}
> <groupId>com.github.spotbugs</groupId>
> <artifactId>spotbugs-maven-plugin</artifactId>
> {code}
> * Look for all "findbugs" and replace it by "spotbugs"
> ** Except for anything related to the findbugs annotations dependency that some dependencies drag in or exclude. Leave that one alone!
> ** For example, change findbugs-check -> spotbugs-check, ...
> * Merge this PR if it hasn't been merged already: https://github.com/kiegroup/optaplanner-wb/pull/320
> * Then you only need to adjust the following repo's: build-boostrap, drools, optaplanner and kie-wb-distributions.
> ** See https://github.com/search?q=org%3Akiegroup+findbugs-maven-plugin&type=Code
> ** Ignore contributed experiments, that repo is dead
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-3420) Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget
by Klara Kufova (Jira)
[ https://issues.jboss.org/browse/DROOLS-3420?page=com.atlassian.jira.plugi... ]
Klara Kufova updated DROOLS-3420:
---------------------------------
Description:
SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget".
Later, ask [~Rikkola] to move it on upper framework.
*ADDITIONAL IMPROVEMENTS:*
# When there are two {{.dmn}} files in the project, the second one is not in the list when creating a new test scenario asset. *The list must be refreshed to contain all available {{.dmn}} files.* The same problem occurs also with a single {{.dmn}} file in the project. Sometimes the list of available {{.dmn}} files is not refreshed and even though they are in the project, they are not displayed in the list.
# Change *Choose DMN asset* to *Choose a DMN asset*.
# The box for choosing a {{.dmn}} file is not wide enough. Make it either as wide as the boxes above (for the name of the asset and the package) or change it to a drop down (the same style as the package drop down).
# The value of a {{.dmn}} file should not be pre-filled once the box has been used. Clear the status so the box is always empty.
was:
SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget".
Later, ask [~Rikkola] to move it on upper framework.
*ADDITIONAL IMPROVEMENTS:*
# When there are two {{.dmn}} files in the project, the second one is not in the list when creating a new test scenario asset. The list must be refreshed to contain all available {{.dmn}} files.
# Change *Choose DMN asset* to *Choose a DMN asset*.
# The box for choosing a {{.dmn}} file is not wide enough. Make it either as wide as the boxes above (for the name of the asset and the package) or change it to a drop down (the same style as the package drop down).
# The value of a {{.dmn}} file should not be pre-filled once the box has been used. Clear the status so the box is always empty.
> Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget
> -------------------------------------------------------------------
>
> Key: DROOLS-3420
> URL: https://issues.jboss.org/browse/DROOLS-3420
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Minor
>
> SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget".
> Later, ask [~Rikkola] to move it on upper framework.
> *ADDITIONAL IMPROVEMENTS:*
> # When there are two {{.dmn}} files in the project, the second one is not in the list when creating a new test scenario asset. *The list must be refreshed to contain all available {{.dmn}} files.* The same problem occurs also with a single {{.dmn}} file in the project. Sometimes the list of available {{.dmn}} files is not refreshed and even though they are in the project, they are not displayed in the list.
> # Change *Choose DMN asset* to *Choose a DMN asset*.
> # The box for choosing a {{.dmn}} file is not wide enough. Make it either as wide as the boxes above (for the name of the asset and the package) or change it to a drop down (the same style as the package drop down).
> # The value of a {{.dmn}} file should not be pre-filled once the box has been used. Clear the status so the box is always empty.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months