September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-958) Public Nightly Kiali - Fix Build/Deploy

by Matthew Mahoney (Jira)

Matthew Mahoney created SWSQE-958: ------------------------------------- Summary: Public Nightly Kiali - Fix Build/Deploy Key: SWSQE-958 URL: https://issues.jboss.org/browse/SWSQE-958 Project: Kiali QE Issue Type: QE Task Reporter: Matthew Mahoney Assignee: Matthew Mahoney Need to build kiali, and then bounce the Kiali pod -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4484) Support SSH authentication for Git persistence

by Ashley Abdel-Sayed (Jira)

[ https://issues.jboss.org/browse/WFCORE-4484?page=com.atlassian.jira.plugi... ] Ashley Abdel-Sayed reassigned WFCORE-4484: ------------------------------------------ Assignee: Ashley Abdel-Sayed > Support SSH authentication for Git persistence > ---------------------------------------------- > > Key: WFCORE-4484 > URL: https://issues.jboss.org/browse/WFCORE-4484 > Project: WildFly Core > Issue Type: Feature Request > Components: Management, Security > Reporter: Farah Juma > Assignee: Ashley Abdel-Sayed > Priority: Major > Labels: EAP-CD19 > Fix For: 11.0.0.Beta1 > > > Currently Elytron only supports authentication for HTTP(s) URLS so there is no way to connect to a SSH git server to pull/push configuration history -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1879) Support SSH authentication for Git persistence

by Ashley Abdel-Sayed (Jira)

[ https://issues.jboss.org/browse/ELY-1879?page=com.atlassian.jira.plugin.s... ] Ashley Abdel-Sayed reassigned ELY-1879: --------------------------------------- Assignee: Ashley Abdel-Sayed > Support SSH authentication for Git persistence > ---------------------------------------------- > > Key: ELY-1879 > URL: https://issues.jboss.org/browse/ELY-1879 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: Ashley Abdel-Sayed > Assignee: Ashley Abdel-Sayed > Priority: Major > Labels: EAP-CD19 > > Currently Elytron only supports authentication for HTTP(s) URLS so there is no way to connect to a SSH git server to pull/push configuration history -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1725) Remove 'org.wildfly.security.credential.source.OAuth2CredentialSource'

by Ashley Abdel-Sayed (Jira)

[ https://issues.jboss.org/browse/ELY-1725?page=com.atlassian.jira.plugin.s... ] Ashley Abdel-Sayed updated ELY-1725: ------------------------------------ Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/1335 (was: https://github.com/wildfly-security/wildfly-elytron/pull/1333) > Remove 'org.wildfly.security.credential.source.OAuth2CredentialSource' > ---------------------------------------------------------------------- > > Key: ELY-1725 > URL: https://issues.jboss.org/browse/ELY-1725 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Assignee: Ashley Abdel-Sayed > Priority: Blocker > Fix For: 2.0.0.Alpha5 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1878) Elytron Tool: Add new option to Credential Store command to utilize attribute "providersForPasswords".

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/ELY-1878?page=com.atlassian.jira.plugin.s... ] Ilia Vassilev updated ELY-1878: ------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.) > Elytron Tool: Add new option to Credential Store command to utilize attribute "providersForPasswords". > ------------------------------------------------------------------------------------------------------ > > Key: ELY-1878 > URL: https://issues.jboss.org/browse/ELY-1878 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Command-Line Tool > Affects Versions: 1.10.1.Final > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > > Add new option to Credential Store command to utilize attribute "providersForPasswords" > Elytron Tool new option > Long option (no arguments): --providers-for-passwords > Short option (no arguments): -w > Description: Use the specified Provider(s) algorithm implementation for passwords. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1878) Elytron Tool: Add new option to Credential Store command to utilize attribute "providersForPasswords".

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/ELY-1878?page=com.atlassian.jira.plugin.s... ] Ilia Vassilev updated ELY-1878: ------------------------------- Description: Add new option to Credential Store command to utilize attribute "providersForPasswords" Elytron Tool new option Long option (no arguments): --providers-for-passwords Short option (no arguments): -w Description: Use the specified Provider(s) algorithm implementation for passwords. was:Add new option to Credential Store command to utilize attribute "providersForPasswords" > Elytron Tool: Add new option to Credential Store command to utilize attribute "providersForPasswords". > ------------------------------------------------------------------------------------------------------ > > Key: ELY-1878 > URL: https://issues.jboss.org/browse/ELY-1878 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Command-Line Tool > Affects Versions: 1.10.1.Final > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > > Add new option to Credential Store command to utilize attribute "providersForPasswords" > Elytron Tool new option > Long option (no arguments): --providers-for-passwords > Short option (no arguments): -w > Description: Use the specified Provider(s) algorithm implementation for passwords. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12577) Upgrade WildFly Core to 10.0.0.CR1

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFLY-12577?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFLY-12577: ------------------------------- Summary: Upgrade WildFly Core to 10.0.0.CR1 (was: Upgrade WildFly Core to 10.0.0.Final) > Upgrade WildFly Core to 10.0.0.CR1 > ---------------------------------- > > Key: WFLY-12577 > URL: https://issues.jboss.org/browse/WFLY-12577 > Project: WildFly > Issue Type: Component Upgrade > Components: Server > Reporter: Brian Stansberry > Assignee: Jeff Mesnil > Priority: Blocker > Fix For: 18.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2382) JGroups version 4.0.13.Final.jar is causing memory leaks

by Rashmi Acharya (Jira)

[ https://issues.jboss.org/browse/JGRP-2382?page=com.atlassian.jira.plugin.... ] Rashmi Acharya commented on JGRP-2382: -------------------------------------- Hi Bella, For now we made further changes on the property and saw Cluster Load distribution is working fine. Support is going to share the new changes to customer and wait until tomorrow to see whether it is solving the memory leak. Here are the changes we made further: 1: Removing use_mcast_xmit="false" from NACACK2 protocol 2:Removed UNICAST3 sine heap memory growth was due to these messages.. This is actually not required for Workflow load distribution 3: Added FD_ALL parameter 4: Removed BARRIER New Change: <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:org:jgroups" xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/jgroups.xsd"> <TCP bind_port="&MULTICAST_NODE_PORT1;" /> <TCPPING async_discovery="true" initial_hosts="&CLUSTER_INITIAL_HOSTS;" port_range="0" send_cache_on_join="true" /> <MERGE3 min_interval="3000" max_interval="5000"/><FD_ALL timeout="20000" interval="15000" /> <FD_SOCK/> <FD timeout="5000" max_tries="48" /> <VERIFY_SUSPECT timeout="1500" /> <pbcast.NAKACK2 discard_delivered_msgs="true"/> <pbcast.STABLE desired_avg_gossip="20000" max_bytes="0" stability_delay="1000" /> <pbcast.GMS print_local_addr="true" join_timeout="15000"/></config> We need to understand 1: why we saw issues with load distribution when we had use_mcast_xmit in NACACK2. 2 What is the equivalent parameter for NACACK retransmit_timeout="5000" in NACACK2 3: What is the use of FD_ALL parameter 4: Why UNICAST3 objects were lying on memory and is there any way it can be GCed with timeout settings ? > JGroups version 4.0.13.Final.jar is causing memory leaks > -------------------------------------------------------- > > Key: JGRP-2382 > URL: https://issues.jboss.org/browse/JGRP-2382 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 4.0.13 > Environment: AIX machine 7.1 with JDK 1.8 > Reporter: Rashmi Acharya > Assignee: Bela Ban > Priority: Major > Attachments: dumps_TEST_node1_20190918_after_3_hours.zip, dumps_TEST_node1_20190918_right_after_restart.zip, dumps_TEST_node2_20190918_after_3_hours.zip, dumps_TEST_node2_20190918_right_after_restart.zip > > > We are observing a constant memory growth and leak with JGroup version 4.0.13 .. > One of our customer is having two node cluster environment and in one node we are observing org.Group.Messages which contain org.groups.Header and org.groups.Stack.ipAddress objects.. these are not getting cleared from memory.. > We dont see any exception related to Jgroups from logs and but it is causing a gradual emory growth and OOM. > Here is the Jgroups cluster configuration we have: > dynamic.cluster.property_string > <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:org:jgroups" xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/jgroups.xsd"> > <TCP bind_addr="&HOST_ADDR;" bind_port="&MULTICAST_NODE_PORT2;"/> > <TCPPING async_discovery="true" initial_hosts="&CLUSTER_INITIAL_HOSTS;" port_range="0" send_cache_on_join="true"/> > <MERGE3 min_interval="3000" max_interval="5000" /> > <FD_ALL timeout="20000" interval="15000"/> > <FD_SOCK/> > <FD timeout="5000" max_tries="48" /> > <VERIFY_SUSPECT timeout="1500"/> > <BARRIER/> > <pbcast.NAKACK2 use_mcast_xmit="false" discard_delivered_msgs="true"/> > <UNICAST3/> > <pbcast.STABLE desired_avg_gossip="20000" max_bytes="0" stability_delay="1000"/> > <pbcast.GMS print_local_addr="true" join_timeout="15000" /> > </config> > ================================= > dynamic.cluster.distribution_property_string > <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:org:jgroups" xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/jgroups.xsd"> > <TCP bind_port="&MULTICAST_NODE_PORT1;" /> > <TCPPING async_discovery="true" initial_hosts="&CLUSTER_INITIAL_HOSTS;" port_range="0" send_cache_on_join="true"/> > <MERGE3 min_interval="3000" max_interval="5000"/> > <FD_SOCK/> > <FD timeout="5000" max_tries="48"/> > <VERIFY_SUSPECT timeout="1500"/> > <BARRIER/> > <pbcast.NAKACK2 use_mcast_xmit="false" discard_delivered_msgs="true"/> > <UNICAST3/> > <pbcast.STABLE desired_avg_gossip="20000" max_bytes="0" stability_delay="1000" /> > <pbcast.GMS print_local_addr="true" join_timeout="5000"/> > </config> > ================================ > dynamic.cluster.lock.protocolStack > <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:org:jgroups" xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/jgroups.xsd"> > <TCP bind_addr="&HOST_ADDR;" bind_port="&MULTICAST_NODE_PORT3;"/> > <TCPPING async_discovery="true" initial_hosts="&CLUSTER_INITIAL_HOSTS;" port_range="0" send_cache_on_join="true"/> > <MERGE3 min_interval="3000" max_interval="5000"/> > <FD_ALL timeout="20000" interval="5000"/> > <FD timeout="5000" max_tries="48"/> > <VERIFY_SUSPECT timeout="1500"/> > <BARRIER/> > <pbcast.NAKACK2 use_mcast_xmit="false" discard_delivered_msgs="true"/> > <UNICAST3 /> <pbcast.STABLE desired_avg_gossip="20000" /> > <pbcast.GMS print_local_addr="true" join_timeout="5000"/> > <FRAG2 frag_size="8096"/> > <CENTRAL_LOCK2/> > </config> -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4555) Importing DMN model causes NullPointerException

by Jonas Tamimi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4555?page=com.atlassian.jira.plugi... ] Jonas Tamimi updated DROOLS-4555: --------------------------------- Description: Hi, this is my first issue, so I hope I did everything right. We have been using version 7.21.0.Final of Drools for the last few months. A few weeks ago we switched to the latest version and could not import a few of our decision models (.dmn) anymore. According to our own research the bug seems to be present since 7.22.0.t042 and is still present in the latest snapshot. This is the relevant logging output: [https://gist.github.com/oas/ec0f70585411d8c3f0266b7d2fd02ebc|https://gist...] I tried to narrow down the exception and it seems to be in the method {{checkVariableName}} of {{org.kie.dmn.feel.parser.feel11.FEELParser}}. {{errorChecker.hasErrors()}} is false, but it is not catched by the if statement in line 111. Because of this, {{errorChecker.getErrors()}} returns null instead of a {{List<FEELEvent>}}. The method {{checkVariableName}} in {{org.kie.dmn.core.compiler.DMNCompilerHelper}}, assumes that a list will be returned and calls {{isEmpty()}}. This throws the {{NullPointerException}}. was: Hi, this is my first issue, so I hope I did everything right. We have been using version 7.21.0.Final of Drools for the last few months. A few weeks ago we switched to the latest version and could not import a few of our decision models (.dmn) anymore. According to our own research the bug seems to be present since 7.22.0.t042 and is still present in the latest snapshot. This is the relevant logging output: [https://gist.github.com/oas/ec0f70585411d8c3f0266b7d2fd02ebc|https://gist...] I tried to narrow down the exception and it seems to be in the method {{checkVariableName}} of {{org.kie.dmn.feel.parser.feel11.FEELParser}}. {{errorChecker.hasErrors()}} is false, but it is not catched by the if statement in line 111. Because of this, {{errorChecker.getErrors()}} returns null instead of a {{List<FEELEvent>}}. The method {{checkVariableName }}in {{org.kie.dmn.core.compiler.DMNCompilerHelper}}, assumes that a list will be returned and calls {{isEmpty()}}. This throws the {{NullPointerException}}. > Importing DMN model causes NullPointerException > ----------------------------------------------- > > Key: DROOLS-4555 > URL: https://issues.jboss.org/browse/DROOLS-4555 > Project: Drools > Issue Type: Bug > Reporter: Jonas Tamimi > Assignee: Mario Fusco > Priority: Major > > Hi, > this is my first issue, so I hope I did everything right. We have been using version 7.21.0.Final of Drools for the last few months. A few weeks ago we switched to the latest version and could not import a few of our decision models (.dmn) anymore. According to our own research the bug seems to be present since 7.22.0.t042 and is still present in the latest snapshot. > This is the relevant logging output: [https://gist.github.com/oas/ec0f70585411d8c3f0266b7d2fd02ebc|https://gist...] > I tried to narrow down the exception and it seems to be in the method {{checkVariableName}} of {{org.kie.dmn.feel.parser.feel11.FEELParser}}. {{errorChecker.hasErrors()}} is false, but it is not catched by the if statement in line 111. Because of this, {{errorChecker.getErrors()}} returns null instead of a {{List<FEELEvent>}}. > The method {{checkVariableName}} in {{org.kie.dmn.core.compiler.DMNCompilerHelper}}, assumes that a list will be returned and calls {{isEmpty()}}. This throws the {{NullPointerException}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4555) Importing DMN model causes NullPointerException

by Jonas Tamimi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4555?page=com.atlassian.jira.plugi... ] Jonas Tamimi updated DROOLS-4555: --------------------------------- Description: Hi, this is my first issue, so I hope I did everything right. We have been using version 7.21.0.Final of Drools for the last few months. A few weeks ago we switched to the latest version and could not import a few of our decision models (.dmn) anymore. According to our own research the bug seems to be present since 7.22.0.t042 and is still present in the latest snapshot. This is the relevant logging output: [https://gist.github.com/oas/ec0f70585411d8c3f0266b7d2fd02ebc|https://gist...] I tried to narrow down the exception and it seems to be in the method {{checkVariableName}} of {{org.kie.dmn.feel.parser.feel11.FEELParser}}. {{errorChecker.hasErrors()}} is false, but it is not catched by the if statement in line 111. Because of this, {{errorChecker.getErrors()}} returns null instead of a {{List<FEELEvent>}}. The method {{checkVariableName }}in {{org.kie.dmn.core.compiler.DMNCompilerHelper}}, assumes that a list will be returned and calls {{isEmpty()}}. This throws the {{NullPointerException}}. was: Hi, this is my first issue, so I hope I did everything right. We have been using version 7.21.0.Final of Drools for the last few months. A few weeks ago we switched to the latest version and could not import a few of our decision models (.dmn) anymore. According to our own research the bug seems to be present since 7.22.0.t042 and is still present in the latest snapshot. This is the relevant logging output: [https://gist.github.com/oas/ec0f70585411d8c3f0266b7d2fd02ebc|https://gist...] I tried to narrow down the exception and it seems to be in the method {{checkVariableName}} of {{org.kie.dmn.feel.parser.feel11.FEELParser}}. {{errorChecker.hasErrors()}} is false, but it is not catched by the if statement in line 111. Because of this, {{errorChecker.getErrors()}} returns null instead of a {{List<FEELEvent>}}. The method checkVariableName in {{org.kie.dmn.core.compiler.DMNCompilerHelper}}, assumes that a list will be returned and calls {{isEmpty()}}. This throws the {{NullPointerException}}. > Importing DMN model causes NullPointerException > ----------------------------------------------- > > Key: DROOLS-4555 > URL: https://issues.jboss.org/browse/DROOLS-4555 > Project: Drools > Issue Type: Bug > Reporter: Jonas Tamimi > Assignee: Mario Fusco > Priority: Major > > Hi, > this is my first issue, so I hope I did everything right. We have been using version 7.21.0.Final of Drools for the last few months. A few weeks ago we switched to the latest version and could not import a few of our decision models (.dmn) anymore. According to our own research the bug seems to be present since 7.22.0.t042 and is still present in the latest snapshot. > This is the relevant logging output: [https://gist.github.com/oas/ec0f70585411d8c3f0266b7d2fd02ebc|https://gist...] > I tried to narrow down the exception and it seems to be in the method {{checkVariableName}} of {{org.kie.dmn.feel.parser.feel11.FEELParser}}. {{errorChecker.hasErrors()}} is false, but it is not catched by the if statement in line 111. Because of this, {{errorChecker.getErrors()}} returns null instead of a {{List<FEELEvent>}}. > The method {{checkVariableName }}in {{org.kie.dmn.core.compiler.DMNCompilerHelper}}, assumes that a list will be returned and calls {{isEmpty()}}. This throws the {{NullPointerException}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2019