November 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2155) table editor should use full canvas area available

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2155?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2155: -------------------------------- Labels: UX (was: ) > table editor should use full canvas area available > -------------------------------------------------- > > Key: DROOLS-2155 > URL: https://issues.jboss.org/browse/DROOLS-2155 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Michael Anstis > Priority: Minor > Labels: UX > > DMN table editor should use the full canvas width that is available (minus panels, toolbars, etc.) It should not appear as a smaller fixed size area, with scrollbars, within the canvas. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9581) Refactor DoctypeDeclTestCase slightly to make it more similar to other tests that execute management operations and reload the server

by Farah Juma (JIRA)

Farah Juma created WFLY-9581: -------------------------------- Summary: Refactor DoctypeDeclTestCase slightly to make it more similar to other tests that execute management operations and reload the server Key: WFLY-9581 URL: https://issues.jboss.org/browse/WFLY-9581 Project: WildFly Issue Type: Task Reporter: Farah Juma Assignee: Farah Juma It's still unclear why {{DoctypeDeclTestCase}} fails intermittently on Windows CI with the following exception: {code} 18:51:38,995 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0268: Failed to rename temp file C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml.tmp to C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0268: Failed to rename temp file C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml.tmp to C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml at org.jboss.as.controller.persistence.FilePersistenceUtils.moveTempFileToMain(FilePersistenceUtils.java:88) at org.jboss.as.controller.persistence.ConfigurationFile.commitTempFile(ConfigurationFile.java:570) at org.jboss.as.controller.persistence.ConfigurationFilePersistenceResource.doCommit(ConfigurationFilePersistenceResource.java:70) at org.jboss.as.controller.persistence.AbstractFilePersistenceResource.commit(AbstractFilePersistenceResource.java:58) at org.jboss.as.controller.ModelControllerImpl$3.commit(ModelControllerImpl.java:727) at org.jboss.as.controller.AbstractOperationContext.executeDoneStage(AbstractOperationContext.java:838) at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:752) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450) at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1402) at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:420) at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:245) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229) at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:245) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:217) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:137) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:161) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244) 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:157) 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 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) Caused by: java.nio.file.FileSystemException: C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml: The process cannot access the file because it is being used by another process. at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102) at sun.nio.fs.WindowsFileCopy.move(WindowsFileCopy.java:376) at sun.nio.fs.WindowsFileSystemProvider.move(WindowsFileSystemProvider.java:287) at java.nio.file.Files.move(Files.java:1395) at org.jboss.as.controller.persistence.FilePersistenceUtils.moveTempFileToMain(FilePersistenceUtils.java:86) ... 28 more {code} Attempt to refactor this test slightly to make it more similar to other tests that execute management operations and reload the server to see if this has an impact on Windows CI. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2156) DMN decision table names should be presented as titles in editor screen.

by Liz Clayton (JIRA)

Liz Clayton created DROOLS-2156: ----------------------------------- Summary: DMN decision table names should be presented as titles in editor screen. Key: DROOLS-2156 URL: https://issues.jboss.org/browse/DROOLS-2156 Project: Drools Issue Type: Enhancement Components: DMN Editor Reporter: Liz Clayton Assignee: Michael Anstis To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2155) table editor should use full canvas area available

by Liz Clayton (JIRA)

Liz Clayton created DROOLS-2155: ----------------------------------- Summary: table editor should use full canvas area available Key: DROOLS-2155 URL: https://issues.jboss.org/browse/DROOLS-2155 Project: Drools Issue Type: Bug Components: DMN Editor Reporter: Liz Clayton Assignee: Michael Anstis Priority: Minor DMN table editor should use the full canvas width that is available (minus panels, toolbars, etc.) It should not appear as a smaller fixed size area, with scrollbars, within the canvas. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-29) Add support for module version strings

by David Lloyd (JIRA)

David Lloyd created WFBUILD-29: ---------------------------------- Summary: Add support for module version strings Key: WFBUILD-29 URL: https://issues.jboss.org/browse/WFBUILD-29 Project: WildFly Build Tools Issue Type: Enhancement Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.2.3.Final JBoss Modules supports version strings now. Allow version numbers to derive from artifacts or be hard-coded in the source {{module.xml}}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-28) Use a proper DOM instead of string replacement to provision servers

by David Lloyd (JIRA)

David Lloyd created WFBUILD-28: ---------------------------------- Summary: Use a proper DOM instead of string replacement to provision servers Key: WFBUILD-28 URL: https://issues.jboss.org/browse/WFBUILD-28 Project: WildFly Build Tools Issue Type: Enhancement Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.2.3.Final Using string replacement is incredibly brittle and prevents enhancements. Use a DOM instead, and manipulate the XML in place. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2154) Design navigation between the DRG and DRD's

by Liz Clayton (JIRA)

Liz Clayton created DROOLS-2154: ----------------------------------- Summary: Design navigation between the DRG and DRD's Key: DROOLS-2154 URL: https://issues.jboss.org/browse/DROOLS-2154 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Liz Clayton Assignee: Liz Clayton *Use case description: * As a business user (Citizen Developer…), I want to navigate between the DRG and the DRDs, and the content of each node, to model business decision logic. *Verification Conditions* * The user of this feature is able to understand that the the DRDs are subsets of the whole DRG model/file. * The user of this feature can seamlessly navigate between the diagrams and the content of the nodes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3434) ERROR in logs while using vault in system properties

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3434?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3434: ------------------------------------------ +1 to changing the message to DEBUG level. Logging that at all is a quite minor aid. If people are using vault expressions with no vault configured, I doubt it would be difficult for them to figure out the problem. > ERROR in logs while using vault in system properties > ---------------------------------------------------- > > Key: WFCORE-3434 > URL: https://issues.jboss.org/browse/WFCORE-3434 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 4.0.0.Alpha3 > Environment: JBoss EAP 7.1 Beta > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > > Getting below ERROR message in server.log when *Picketbox Vault expressions* used in *system properties*.: > {code:java} > ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0230: Vault is not initialized; resolution of vault expressions is not possible > {code} > Below expressions are resolving fine but due to race condition this ERROR message got printed in the logs. > {code:java} > <system-properties> > <property name="javax.net.ssl.trustStore" value="/home/jboss-eap-7.1/vault/vault.keystore"/> > <property name="javax.net.ssl.trustStorePassword" value="${VAULT::datasource::password::1}"/> > </system-properties> > <vault> > <vault-option name="KEYSTORE_URL" value="/home/jboss-eap-7.1/vault/vault.keystore"/> > <vault-option name="KEYSTORE_PASSWORD" value="MASK-2GAtdnlXL8H"/> > <vault-option name="KEYSTORE_ALIAS" value="vault"/> > <vault-option name="SALT" value="12345678"/> > <vault-option name="ITERATION_COUNT" value="44"/> > <vault-option name="ENC_FILE_DIR" value="/home/jboss-eap-7.1/vault/"/> > </vault> > {code} > Expression is actually resolving to the correct value and that can be check using below CLI command : > {code:java} > /core-service=platform-mbean/type=runtime:read-attribute(name=system-properties). > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-457) SASL SAML Authentication Mechanism

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-457?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-457: -------------------------------------- You could always get an analysis document started with the bits you do know, the bits we don't know should then be clearer for us to work out how to fill in the blanks. > SASL SAML Authentication Mechanism > ---------------------------------- > > Key: ELY-457 > URL: https://issues.jboss.org/browse/ELY-457 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SASL > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Fix For: 2.0.0.Alpha1 > > > https://tools.ietf.org/html/rfc6595 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2237) The single node in the cluster not become a coordinator after coordinator leave.

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2237?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2237: -------------------------------- So if we look at the view changes, the following happens: {{654}} is the first member, then {{11729}} joins. Next, {{654}} (the coord) leaves. Then, {{28153}} joins, but becomes singleton as it doesn't get a discovery response from {{11729}}. This could be because of a misconfig; again. I tried my {{test.xml}} with {{master}} at least 30 times, and it always worked, and views were created correctly. > The single node in the cluster not become a coordinator after coordinator leave. > -------------------------------------------------------------------------------- > > Key: JGRP-2237 > URL: https://issues.jboss.org/browse/JGRP-2237 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.2, 4.0.8 > Reporter: kfir avraham > Assignee: Bela Ban > Priority: Minor > Attachments: test.xml > > > I got cluster with 2 members, sometimes when the first node (coordinator) leave the cluster the second one is not become a coordinator. > When the first one is rejoin, he could not determine coordinator and select new one from the nodes list. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2017