November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2397) MPING: issue with MulticastSocket creation

by Bela Ban (Jira)

Bela Ban created JGRP-2397: ------------------------------ Summary: MPING: issue with MulticastSocket creation Key: JGRP-2397 URL: https://issues.jboss.org/browse/JGRP-2397 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 4.1.8 ------------------------------------------------------------------- 1185 [ERROR] MPING: JGRP000200: failed sending discovery request java.io.IOException: Can't assign requested address at java.net.PlainDatagramSocketImpl.send(Native Method) ~[?:?] at java.net.DatagramSocket.send(DatagramSocket.java:695) ~[?:?] at org.jgroups.protocols.MPING.sendMcastDiscoveryRequest(MPING.java:293) [classes/:?] at org.jgroups.protocols.PING.sendDiscoveryRequest(PING.java:64) [classes/:?] at org.jgroups.protocols.PING.findMembers(PING.java:32) [classes/:?] at org.jgroups.protocols.Discovery.invokeFindMembers(Discovery.java:217) [classes/:?] at org.jgroups.protocols.Discovery.findMembers(Discovery.java:244) [classes/:?] at org.jgroups.protocols.Discovery.down(Discovery.java:383) [classes/:?] at org.jgroups.protocols.MERGE3.down(MERGE3.java:278) [classes/:?] at org.jgroups.protocols.FD_ALL.down(FD_ALL.java:235) [classes/:?] at org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:102) [classes/:?] at org.jgroups.protocols.BARRIER.down(BARRIER.java:136) [classes/:?] at org.jgroups.protocols.pbcast.NAKACK2.down(NAKACK2.java:555) [classes/:?] at org.jgroups.protocols.UNICAST3.down(UNICAST3.java:595) [classes/:?] at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:349) [classes/:?] at org.jgroups.protocols.pbcast.ClientGmsImpl.joinInternal(ClientGmsImpl.java:72) [classes/:?] at org.jgroups.protocols.pbcast.ClientGmsImpl.join(ClientGmsImpl.java:41) [classes/:?] at org.jgroups.protocols.pbcast.GMS.down(GMS.java:1054) [classes/:?] at org.jgroups.protocols.FlowControl.down(FlowControl.java:295) [classes/:?] at org.jgroups.protocols.FlowControl.down(FlowControl.java:295) [classes/:?] at org.jgroups.protocols.FRAG2.down(FRAG2.java:141) [classes/:?] at org.jgroups.protocols.pbcast.STATE_TRANSFER.down(STATE_TRANSFER.java:207) [classes/:?] at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:928) [classes/:?] at org.jgroups.JChannel.down(JChannel.java:627) [classes/:?] at org.jgroups.JChannel._connect(JChannel.java:855) [classes/:?] at org.jgroups.JChannel.connect(JChannel.java:352) [classes/:?] at org.jgroups.JChannel.connect(JChannel.java:343) [classes/:?] at org.jgroups.demos.Draw.go(Draw.java:193) [classes/:?] at org.jgroups.demos.Draw.main(Draw.java:156) [classes/:?] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2396) increasing networkdata, cpu and heap

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2396?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2396: -------------------------------- When the system is idle and you have a high CPU, then take a stack trace and attach it here. What I meant is that almost all CPU consumed by JGroups will be either on reception or sending of messages. This is normal. > increasing networkdata, cpu and heap > ------------------------------------ > > Key: JGRP-2396 > URL: https://issues.jboss.org/browse/JGRP-2396 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.19 > Reporter: Rob van der Boom > Assignee: Bela Ban > Priority: Major > Attachments: Schermafbeelding 2019-11-08 om 15.43.04.png, Schermafbeelding 2019-11-08 om 15.44.52.png, Schermafbeelding 2019-11-08 om 16.00.48.png, standalone-ha.xml > > > hey, > we have an keycloak (sso) setup, version 7.0.1 running in kubernetes - aws. > Its build on wildfly 17, infinispan 9.4 and jgroups 4.0.19. > We have 3 pods running in standalone-ha with cache setup on distribution (all 3 nodes - so equivalent to replication) > ISSUE: > We see a slowly growing of networkstatistics, heap and cpu, while the number of sessions in keycloak (cached) remain almost stable. > The cpu growth is caused by the TQbundler process, which explaines the networkdata growth. It looks like this is causing also a memory leakage.. > every 5 days we have to restart the pods and then every resets to a very low level including the heap. this while all sessions are still valid and cached. > The only issue i could find maybe related to this is: > https://issues.jboss.org/browse/JGRP-2382?jql=project%20%3D%20JGRP%20AND%... > Could this be the same issue and does it also cause increasing network and cpu (since that is why we have to restart, the heap has much space left !). > And if so how does this issue continue since for us its a major issue. > We als had this issue already in keycloak 5 (wildfly 15), thats why we upgraded to the latest available version. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12574) Documentation for SSH authentication for Git persistence

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12574?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12574: ------------------------------------ Labels: (was: EAP-CD19) > Documentation for SSH authentication for Git persistence > -------------------------------------------------------- > > Key: WFLY-12574 > URL: https://issues.jboss.org/browse/WFLY-12574 > Project: WildFly > Issue Type: Feature Request > Components: Management, Security > Reporter: Ashley Abdel-Sayed > Assignee: Ashley Abdel-Sayed > Priority: Major > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-1900) Add version 1.5 of the Elytron client schema

by Ashley Abdel-Sayed (Jira)

[ https://issues.jboss.org/browse/ELY-1900?page=com.atlassian.jira.plugin.s... ] Ashley Abdel-Sayed updated ELY-1900: ------------------------------------ Fix Version/s: 1.11.0.CR2 (was: 1.10.0.CR1) (was: 2.0.0.Alpha5) > Add version 1.5 of the Elytron client schema > -------------------------------------------- > > Key: ELY-1900 > URL: https://issues.jboss.org/browse/ELY-1900 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Ashley Abdel-Sayed > Assignee: Farah Juma > Priority: Major > Fix For: 1.11.0.CR2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-1900) Add version 1.5 of the Elytron client schema

by Ashley Abdel-Sayed (Jira)

[ https://issues.jboss.org/browse/ELY-1900?page=com.atlassian.jira.plugin.s... ] Ashley Abdel-Sayed reassigned ELY-1900: --------------------------------------- Assignee: Ashley Abdel-Sayed (was: Farah Juma) > Add version 1.5 of the Elytron client schema > -------------------------------------------- > > Key: ELY-1900 > URL: https://issues.jboss.org/browse/ELY-1900 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Ashley Abdel-Sayed > Assignee: Ashley Abdel-Sayed > Priority: Major > Fix For: 1.11.0.CR2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-1900) Add version 1.5 of the Elytron client schema

by Ashley Abdel-Sayed (Jira)

Ashley Abdel-Sayed created ELY-1900: --------------------------------------- Summary: Add version 1.5 of the Elytron client schema Key: ELY-1900 URL: https://issues.jboss.org/browse/ELY-1900 Project: WildFly Elytron Issue Type: Task Components: Authentication Client Reporter: Ashley Abdel-Sayed Assignee: Farah Juma Fix For: 1.10.0.CR1, 2.0.0.Alpha5 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-1900) Add version 1.5 of the Elytron client schema

by Ashley Abdel-Sayed (Jira)

[ https://issues.jboss.org/browse/ELY-1900?page=com.atlassian.jira.plugin.s... ] Ashley Abdel-Sayed updated ELY-1900: ------------------------------------ Git Pull Request: (was: https://github.com/wildfly-security/wildfly-elytron/pull/1269) > Add version 1.5 of the Elytron client schema > -------------------------------------------- > > Key: ELY-1900 > URL: https://issues.jboss.org/browse/ELY-1900 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Ashley Abdel-Sayed > Assignee: Farah Juma > Priority: Major > Fix For: 1.10.0.CR1, 2.0.0.Alpha5 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12722) Upgrade Infinispan to 10.0.0.Final

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12722?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-12722: -------------------------------- Issue Type: Component Upgrade (was: Feature Request) > Upgrade Infinispan to 10.0.0.Final > ---------------------------------- > > Key: WFLY-12722 > URL: https://issues.jboss.org/browse/WFLY-12722 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 18.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > https://issues.jboss.org/projects/ISPN/versions/12332894 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4745) Fix logging test suite to work in all environments

by James Perkins (Jira)

James Perkins created WFCORE-4745: ------------------------------------- Summary: Fix logging test suite to work in all environments Key: WFCORE-4745 URL: https://issues.jboss.org/browse/WFCORE-4745 Project: WildFly Core Issue Type: Bug Components: Logging, Test Suite Reporter: James Perkins Assignee: James Perkins In some cases, seems to happen in CI, the modules created in the logging subsystem tests fail to load. There are a couple issues with the test environment. # There are some invalid version properties used in the {{module.xml}} files # The {{maven.repo.local}} system property needs to be set in the surefire system properties. The combinations of these fixes seems to fix the test suite issues seen only on an internal CI box for some reason. Either way this should be corrected as it is invalid and could fail in other environments as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4746) Fix logging test suite to work in all environments

by James Perkins (Jira)

James Perkins created WFCORE-4746: ------------------------------------- Summary: Fix logging test suite to work in all environments Key: WFCORE-4746 URL: https://issues.jboss.org/browse/WFCORE-4746 Project: WildFly Core Issue Type: Bug Components: Logging, Test Suite Reporter: James Perkins Assignee: James Perkins In some cases, seems to happen in CI, the modules created in the logging subsystem tests fail to load. There are a couple issues with the test environment. # There are some invalid version properties used in the {{module.xml}} files # The {{maven.repo.local}} system property needs to be set in the surefire system properties. The combinations of these fixes seems to fix the test suite issues seen only on an internal CI box for some reason. Either way this should be corrected as it is invalid and could fail in other environments as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 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 November 2019