[JBoss JIRA] (WFCORE-3712) Provided mechanism to disable configuration file backup
by Yeray Borges Santana (Jira)
[ https://issues.redhat.com/browse/WFCORE-3712?page=com.atlassian.jira.plug... ]
Yeray Borges Santana resolved WFCORE-3712.
------------------------------------------
Resolution: Duplicate Issue
Duplicated issue: see WFCORE-4135
> Provided mechanism to disable configuration file backup
> -------------------------------------------------------
>
> Key: WFCORE-3712
> URL: https://issues.redhat.com/browse/WFCORE-3712
> Project: WildFly Core
> Issue Type: Enhancement
> Reporter: Ken Wills
> Priority: Major
>
> For certain use cases, e.g. cloud with non-writable storage, the automatic persistence backup of configuration files (standalone.xml etc) is not needed or desired.
> It would be nice to have a mechanism to disable this.
> Example:
> {quote}
> 17:42:13,104 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: java.lang.IllegalStateException: WFLYCTL0056: Could not rename /opt/datagrid/standalone/configuration/standalone_xml_history/current to /opt/datagrid/standalone/configuration/standalone_xml_history/20180326-174213103
> at org.jboss.as.controller.persistence.ConfigurationFile.createHistoryDirectory(ConfigurationFile.java:638) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1]
> at org.jboss.as.controller.persistence.ConfigurationFile.successfulBoot(ConfigurationFile.java:470) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1]
> at org.jboss.as.controller.persistence.BackupXmlConfigurationPersister.successfulBoot(BackupXmlConfigurationPersister.java:94) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1]
> at org.jboss.as.controller.AbstractControllerService.finishBoot(AbstractControllerService.java:451) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1]
> at org.jboss.as.server.ServerService.boot(ServerService.java:373) [wildfly-server-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:301) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_161]
> 17:42:13,106 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {quote}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5067) Bound property check mark
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5067?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5067:
--------------------------------
Summary: Bound property check mark (was: Bound property indicator)
> Bound property check mark
> -------------------------
>
> Key: DROOLS-5067
> URL: https://issues.redhat.com/browse/DROOLS-5067
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Trivial
> Labels: drools-tools
>
> In Test Scenario we have a feature for highlighting a property during binding to a fact property. However we do not highlight the already bound fact property.
> In other words, if a column is bound to some fact property, there should be check mark in test tools panel next to the given fact property.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5067) Bound property indicator
by Jozef Marko (Jira)
Jozef Marko created DROOLS-5067:
-----------------------------------
Summary: Bound property indicator
Key: DROOLS-5067
URL: https://issues.redhat.com/browse/DROOLS-5067
Project: Drools
Issue Type: Enhancement
Components: Scenario Simulation and Testing
Reporter: Jozef Marko
Assignee: Jozef Marko
In Test Scenario we have a feature for highlighting a property during binding to a fact property. However we do not highlight the already bound fact property.
In other words, if a column is bound to some fact property, there should be check mark in test tools panel next to the given fact property.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5067) Bound property indicator
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5067?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5067:
--------------------------------
Priority: Trivial (was: Major)
> Bound property indicator
> ------------------------
>
> Key: DROOLS-5067
> URL: https://issues.redhat.com/browse/DROOLS-5067
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Trivial
> Labels: drools-tools
>
> In Test Scenario we have a feature for highlighting a property during binding to a fact property. However we do not highlight the already bound fact property.
> In other words, if a column is bound to some fact property, there should be check mark in test tools panel next to the given fact property.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFCORE-3937) Error when running configured wildfly
by Yeray Borges Santana (Jira)
[ https://issues.redhat.com/browse/WFCORE-3937?page=com.atlassian.jira.plug... ]
Yeray Borges Santana commented on WFCORE-3937:
----------------------------------------------
This is also hitting the wildfly-s2i cloud image when drivers are configured at S2I phase; the standalone_xml_history is being created at S2I phase and it ends up in a different overlay filesystem mounted by Docker in the final image, thanks [~jdenise] for pointing me out to the Overlays Filesystem concept.
Files.move is unable to move directories if they are in different partitions (overlay filesystem mounted in the docker image)
> Error when running configured wildfly
> -------------------------------------
>
> Key: WFCORE-3937
> URL: https://issues.redhat.com/browse/WFCORE-3937
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 5.0.0.Final
> Reporter: Stephen Buergler
> Assignee: Jeff Mesnil
> Priority: Minor
> Attachments: Dockerfile
>
>
> 08:32:20,676 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0056: Could not rename /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current to /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/20180619-083220673: java.nio.file.DirectoryNotEmptyException: /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current
> ...
> 08:50:08,531 WARN [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0414: Could not create a timestamped backup of current history dir /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current, so it may still include versions from the previous boot.
> To reproduce:
> docker build -t testing .
> docker run --rm -it testing
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months