November 2017 - jboss-jira - Jboss List Archives

[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)

8 years

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)

8 years

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)

8 years

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)

8 years

1
0
0 / 0

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

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-457?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-457: -------------------------------- [~dlofthouse] By specification SAML SaslServer should wait and receive HTTP call from IdP - it looks like it needs to be integrated with undertow somehow... Do we have some plan how to handle similar things already? Or should I postpone this until F2F too? The SaslServer should work by following way: * sasl server receive initial-response (domain name of IdP) * sasl server sends authentication-request * sasl server receive "=" * *! sasl server waits for authentication statement from IdP over HTTP !* * when received, sasl server sends completion message to client > 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)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3436) Server path capabilities should be registered as possible capabilities of ServerRootResourceDefinition

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFCORE-3436: ----------------------------------------- Summary: Server path capabilities should be registered as possible capabilities of ServerRootResourceDefinition Key: WFCORE-3436 URL: https://issues.jboss.org/browse/WFCORE-3436 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet The paths defined in server and hc environment are not deined from a resource. They should be possible capabilities from the ServerRootResourceDefinition and HostResourceDefinition -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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: -------------------------------- Have you tried this with the config I attached (test.xml)? And please use the latest 4.0.8 to test; this is what I used and I never hit a problem. Your log shows the member waited for 30s which is impossible as {{GMS.timeout}} is 3s in the config you attached! So either you used the wrong config, or attached the wrong config! > 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)

8 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2238) KUBE_PING should read old env variables and should warn

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2238?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2238: --------------------------- Fix Version/s: 4.0.9 > KUBE_PING should read old env variables and should warn > ------------------------------------------------------- > > Key: JGRP-2238 > URL: https://issues.jboss.org/browse/JGRP-2238 > Project: JGroups > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 4.0.9 > > > While I was upgrading Infinispan cluster on docker, I realised I was using old environment properties. These were neither read nor was any WARN messages being reported. > The code should read the current properties and if not present should try to read the old ones and assign them. Then, we should check if both new and old properties are in use and we should also check if only old ones in use. Both scenarios should warn the user. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-9580) Drop ASYNC variant of the clustering testsuite

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9580?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned WFLY-9580: ------------------------------------ Assignee: Radoslav Husar (was: Jason Greene) > Drop ASYNC variant of the clustering testsuite > ---------------------------------------------- > > Key: WFLY-9580 > URL: https://issues.jboss.org/browse/WFLY-9580 > Project: WildFly > Issue Type: Task > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Cuts the time in half when running {{-DextendedTests}}. This can be dropped since we are moving to Infinispan 9.x,. see http://infinispan.org/docs/9.0.x/upgrading/upgrading.html#removed_async_t... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-9580) Drop ASYNC variant of the clustering testsuite

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9580?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9580: --------------------------------- Component/s: Clustering Test Suite > Drop ASYNC variant of the clustering testsuite > ---------------------------------------------- > > Key: WFLY-9580 > URL: https://issues.jboss.org/browse/WFLY-9580 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Cuts the time in half when running {{-DextendedTests}}. This can be dropped since we are moving to Infinispan 9.x,. see http://infinispan.org/docs/9.0.x/upgrading/upgrading.html#removed_async_t... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2017