[JBoss JIRA] (WFLY-10968) Backup doesn't activate after shared store is reconnected
by Emmanuel Hugonnet (Jira)
[ https://issues.jboss.org/browse/WFLY-10968?page=com.atlassian.jira.plugin... ]
Emmanuel Hugonnet commented on WFLY-10968:
------------------------------------------
[~jamezp]this is part of current Artemis master which is going to be Artemis 2.10.0. Thus it is not curretnly fixed in WildFly without a component upgrade.
> Backup doesn't activate after shared store is reconnected
> ---------------------------------------------------------
>
> Key: WFLY-10968
> URL: https://issues.jboss.org/browse/WFLY-10968
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Environment: NFS configuration
> {noformat}
> messaging-10.jbm.lab.bos.redhat.com:/hornetq on /mnt/hornetq/client type nfs4 (rw,nosuid,nodev,relatime,sync,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,acregmin=0,acregmax=0,acdirmin=0,acdirmax=0,soft,noac,nosharecache,proto=tcp,timeo=50,retrans=5,sec=sys,clientaddr=10.16.100.40,lookupcache=none,local_lock=none,addr=10.16.100.24)
> {noformat}
> Java version
> {noformat}
> java version "1.8.0_151"
> Java(TM) SE Runtime Environment (build 1.8.0_151-b12)
> Java HotSpot(TM) 64-Bit Server VM (build 25.151-b12, mixed mode
> {noformat}
> Reporter: Tomas Hofman
> Assignee: Tomas Hofman
> Priority: Critical
> Labels: downstream_dependency
>
> *Scenario*
> # Start live backup server pair in dedicated topology with shared store HA, with journal located on NFS
> # NFS mounted on backup server fails
> # Reconnect NFS on backup server
> # Try to shut down live EAP server
> # Backup doesn't activate
> *What happens*
> Backup is waiting for live to fail by checking its file lock. In case the connection to shared storage fails, backup logs following error.
> {noformat}
> 05:50:57,896 ERROR [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=836c9b1e-f067-11e7-8763-001b21862475) AMQ224000: Failure in initialisation: java.io.IOException: Input/output error
> at sun.nio.ch.FileDispatcherImpl.lock0(Native Method) [rt.jar:1.8.0_151]
> at sun.nio.ch.FileDispatcherImpl.lock(FileDispatcherImpl.java:90) [rt.jar:1.8.0_151]
> at sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:1115) [rt.jar:1.8.0_151]
> at org.apache.activemq.artemis.core.server.impl.FileLockNodeManager.tryLock(FileLockNodeManager.java:299) [artemis-server-1.5.5.008-redhat-1.jar:1.5.5.008-redhat-1]
> at org.apache.activemq.artemis.core.server.impl.FileLockNodeManager.lock(FileLockNodeManager.java:316) [artemis-server-1.5.5.008-redhat-1.jar:1.5.5.008-redhat-1]
> at org.apache.activemq.artemis.core.server.impl.FileLockNodeManager.awaitLiveNode(FileLockNodeManager.java:127) [artemis-server-1.5.5.008-redhat-1.jar:1.5.5.008-redhat-1]
> at org.apache.activemq.artemis.core.server.impl.SharedStoreBackupActivation.run(SharedStoreBackupActivation.java:77) [artemis-server-1.5.5.008-redhat-1.jar:1.5.5.008-redhat-1]
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$ActivationThread.run(ActiveMQServerImpl.java:2496) [artemis-server-1.5.5.008-redhat-1.jar:1.5.5.008-redhat-1]
> {noformat}
> Exception is caught in {{SharedStoreBackupActivation.run}}, and causes termination of backup activation process.
> In case the NFS is reconnected later, backup server doesn't continue in activation process and it doesn't wait for live to fail. In case the live fails, backup doesn't activate, even though it has a connection to shared storage.
> Backup should retry checking live lock even in case the storage is unavailable. It should log warning/error messages that storage is unavailable, but it should not terminate the activation process. This would allow backup to continue its duties when the storage is reconnected.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (WFLY-12099) Cannot change transaction log store type via CLI
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-12099?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-12099:
---------------------------------
Labels: (was: closed)
> Cannot change transaction log store type via CLI
> ------------------------------------------------
>
> Key: WFLY-12099
> URL: https://issues.jboss.org/browse/WFLY-12099
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 17.0.0.Alpha1
> Reporter: Kabir Khan
> Assignee: Ondrej Chaloupka
> Priority: Critical
>
> For the OpenShift image work we need to be able to handle configuration of datasources. There is an effort underway to replace the current template marker replacement done in standalone.xml with CLI commands.
> While this works for the datasource subsystem itself, the OpenShift image scripts also touch other subsystems. For example if it is configured to use the Tx subsystem JDBC log store, we need to change the value of the /subsystem=transactions/log-store=log-store's 'type' attribute and to set the values of jdbc-action-store-table-prefix, jdbc-communication-store-table-prefix and jdbc-state-store-table-prefix and jdbc-store-datasource attributes on the subsystem itself.
> The equivalent in the existing xml marker replacement is to inject the following xml into the subsystem (the 'os77c791d37250' is calculated by the OpenShift launch scripts):
> {code}
> <jdbc-store datasource-jndi-name="java:jboss/datasources/testtx_postgresqlObjectStore">
> <action table-prefix="os77c791d37250"/>
> <communication table-prefix="os77c791d37250"/>
> <state table-prefix="os77c791d37250"/>
> </jdbc-store>
> {code}
> However, this is not possible to do via CLI. Starting the server without a jdbc-store, you end up with the following
> {code}
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store:read-resource
> {
> "outcome" => "success",
> "result" => {
> "type" => "default",
> "transactions" => undefined
> }
> }
> {code}
> If you try to write the 'type' attribute it gives the error than it is read-only
> {code}
> [standalone@embedded /] /subsystem=transactions/log-store=log-store:write-attribute(name=type, value=jdbc)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0048: Attribute type is not writable",
> "rolled-back" => true
> }
> {code}
> If you try to delete the resource and add it again, it gives another error:
> {code}
> [standalone@embedded /] /subsystem=transactions/log-store=log-store:remove
> {
> "outcome" => "success",
> "result" => undefined
> }
> [standalone@embedded /] /subsystem=transactions/log-store=log-store:add(type=jdbc)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0212: Duplicate resource [
> (\"subsystem\" => \"transactions\"),
> (\"log-store\" => \"log-store\")
> ]",
> "rolled-back" => true
> }
> {code}
> Despite the change looking like it has taken effect:
> {code}
> [standalone@embedded /] /subsystem=transactions/log-store=log-store:read-resource
> {
> "outcome" => "success",
> "result" => {
> "type" => "jdbc",
> "transactions" => undefined
> }
> }
> {code}
> However, it is not persisted in xml, so restarting the server it says the type is 'default' again
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (DROOLS-4245) [DMN Designer] Documentation - Enhance presentation
by Brian Dellascio (Jira)
[ https://issues.jboss.org/browse/DROOLS-4245?page=com.atlassian.jira.plugi... ]
Brian Dellascio edited comment on DROOLS-4245 at 7/11/19 6:10 PM:
------------------------------------------------------------------
[~uxdlc], [~karreiro] I've posted a Marvel prototype (section below the description) that mainly focused on the font and table styling. To see the font sizes, colors, line thicknesses, etc, just click on the "handoff" button in the bottom left of the screen. Once in that mode, you can hover on and select various elements to see the specs on them. It should be enough information to get you started. I'm on PTO starting tomorrow through next week, but can review progress upon my return. Thanks!
was (Author: bdellasc):
[~uxdlc][~karreiro] I've posted a Marvel prototype (section below the description) that mainly focused on the font and table styling. To see the font sizes, colors, line thicknesses, etc, just click on the "handoff" button in the bottom left of the screen. Once in that mode, you can hover on and select various elements to see the specs on them. It should be enough information to get you started. I'm on PTO starting tomorrow through next week, but can review progress upon my return. Thanks!
> [DMN Designer] Documentation - Enhance presentation
> ---------------------------------------------------
>
> Key: DROOLS-4245
> URL: https://issues.jboss.org/browse/DROOLS-4245
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Brian Dellascio
> Priority: Major
> Labels: UX, UXTeam, VisualDesign, drools-tools
> Attachments: doc.pdf, new_doc.pdf
>
>
> Enhance styles and presentation of the Documentation output.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (DROOLS-4245) [DMN Designer] Documentation - Enhance presentation
by Brian Dellascio (Jira)
[ https://issues.jboss.org/browse/DROOLS-4245?page=com.atlassian.jira.plugi... ]
Brian Dellascio edited comment on DROOLS-4245 at 7/11/19 6:10 PM:
------------------------------------------------------------------
[~uxdlc][~karreiro] I've posted a Marvel prototype (section below the description) that mainly focused on the font and table styling. To see the font sizes, colors, line thicknesses, etc, just click on the "handoff" button in the bottom left of the screen. Once in that mode, you can hover on and select various elements to see the specs on them. It should be enough information to get you started. I'm on PTO starting tomorrow through next week, but can review progress upon my return. Thanks!
was (Author: bdellasc):
I've posted a Marvel prototype (section below the description) that mainly focused on the font and table styling. To see the font sizes, colors, line thicknesses, etc, just click on the "handoff" button in the bottom left of the screen. Once in that mode, you can hover on and select various elements to see the specs on them. It should be enough information to get you started. I'm on PTO starting tomorrow through next week, but can review progress upon my return. Thanks!
> [DMN Designer] Documentation - Enhance presentation
> ---------------------------------------------------
>
> Key: DROOLS-4245
> URL: https://issues.jboss.org/browse/DROOLS-4245
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Brian Dellascio
> Priority: Major
> Labels: UX, UXTeam, VisualDesign, drools-tools
> Attachments: doc.pdf, new_doc.pdf
>
>
> Enhance styles and presentation of the Documentation output.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (DROOLS-4245) [DMN Designer] Documentation - Enhance presentation
by Brian Dellascio (Jira)
[ https://issues.jboss.org/browse/DROOLS-4245?page=com.atlassian.jira.plugi... ]
Brian Dellascio commented on DROOLS-4245:
-----------------------------------------
I've posted a Marvel prototype (section below the description) that mainly focused on the font and table styling. To see the font sizes, colors, line thicknesses, etc, just click on the "handoff" button in the bottom left of the screen. Once in that mode, you can hover on and select various elements to see the specs on them. It should be enough information to get you started. I'm on PTO starting tomorrow through next week, but can review progress upon my return. Thanks!
> [DMN Designer] Documentation - Enhance presentation
> ---------------------------------------------------
>
> Key: DROOLS-4245
> URL: https://issues.jboss.org/browse/DROOLS-4245
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Brian Dellascio
> Priority: Major
> Labels: UX, UXTeam, VisualDesign, drools-tools
> Attachments: doc.pdf, new_doc.pdf
>
>
> Enhance styles and presentation of the Documentation output.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years