October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9473) Custom NAKACK2 automatically enables use_mcast_xmit/use_mcast_xmit_req when using multicast-based transports

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9473?page=com.atlassian.jira.plugin.... ] Radoslav Husar moved JBEAP-13604 to WFLY-9473: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9473 (was: JBEAP-13604) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering (was: Clustering) Affects Version/s: 11.0.0.Final (was: 7.1.0.CR3) > Custom NAKACK2 automatically enables use_mcast_xmit/use_mcast_xmit_req when using multicast-based transports > ------------------------------------------------------------------------------------------------------------ > > Key: WFLY-9473 > URL: https://issues.jboss.org/browse/WFLY-9473 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Blocker > > Enabling use_mcast_xmit_req could actually cause an excess messages to be send within the cluster. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3380) Elytron client + keystore which retrieve credential from credential store works fine when using OracleJDK and OpenJDK but doesn't work using IBM JDK.

by Hynek Švábek (JIRA)

Hynek Švábek created WFCORE-3380: ------------------------------------ Summary: Elytron client + keystore which retrieve credential from credential store works fine when using OracleJDK and OpenJDK but doesn't work using IBM JDK. Key: WFCORE-3380 URL: https://issues.jboss.org/browse/WFCORE-3380 Project: WildFly Core Issue Type: Bug Components: Security Reporter: Hynek Švábek Assignee: Darran Lofthouse Priority: Critical Elytron client + keystore which retrieve credential from credential store works fine when using OracleJDK and OpenJDK. Problem occurs when we use IBM JDK, {code} ./jboss-cli.sh -c -Dwildfly.config.url=path/to/wfly-config.xml java.lang.ExceptionInInitializerError: org.wildfly.client.config.ConfigXMLParseException: ELY01139: Failed to create credential store at file:///home/hsvabek/securityworkspace/VERIFICATION/2017_10_23_PKCS12/reproducer/wfly-config.xml:5:9: ELY01139: Failed to create credential store at file:///home/hsvabek/securityworkspace/VERIFICATION/2017_10_23_PKCS12/reproducer/wfly-config.xml:5:9: ELY09514: Unable to initialize credential store: com.sun.crypto.provider.SealedObjectForKeyProtector {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9456) High non heap memory consumption

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9456?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-9456: ------------------------------------- Is there anyway you could test with the Oracle JDK to see if it has the same issue? Also the exact version of the JVM you're running may be helpful. Below is what I have. {code} [root@localhost ~]# dnf info java-1.8.0-openjdk Last metadata expiration check: 0:25:39 ago on Tue 24 Oct 2017 08:10:57 AM PDT. Installed Packages Name : java-1.8.0-openjdk Epoch : 1 Version : 1.8.0.144 Release : 7.b01.fc26 Arch : x86_64 Size : 495 k Source : java-1.8.0-openjdk-1.8.0.144-7.b01.fc26.src.rpm Repo : @System >From repo : updates Summary : OpenJDK Runtime Environment URL : http://openjdk.java.net/ License : ASL 1.1 and ASL 2.0 and GPL+ and GPLv2 and GPLv2 with exceptions and LGPL+ and LGPLv2 and MPLv1.0 and MPLv1.1 and Public Domain and W3C Description : The OpenJDK runtime environment. {code} > High non heap memory consumption > -------------------------------- > > Key: WFLY-9456 > URL: https://issues.jboss.org/browse/WFLY-9456 > Project: WildFly > Issue Type: Bug > Components: Class Loading > Affects Versions: 11.0.0.CR1, 11.0.0.Final > Environment: CentOS 7 on Google compute engine VM > openjdk version "1.8.0_144" > OpenJDK Runtime Environment (build 1.8.0_144-b01) > OpenJDK 64-Bit Server VM (build 25.144-b01, mixed mode) > Reporter: Klaus Erber > Assignee: David Lloyd > Attachments: wf10-nmt.txt, wf11-nmt.txt > > > After a clean install of WF11CR1 without any configuration changes and startup with standalone.sh we see a high memory usage on the system side (about 800 MB). > Wenn we do the same with WF10Final we see a memory usage of about 210 MB. > Her are the output auf ps aux: > wf11 > ke4 1652 14.0 22.1 2863404 *801620* pts/3 Sl+ 14:01 0:07 java -D[Standalone] -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m > wf10 > ke4 1836 42.1 5.7 2687744 *209204* pts/2 Sl+ 14:02 0:06 java -D[Standalone] -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m > The result is, that we can only start 3 instances of wildfly 11 on a 3.75 GB VM. The 4th instance crashes the system. In our real scenario (Wildfly instances in docker containers hosting the REST interface for our application) we see about 1 GB memory consumption per backend node. > The heap and other memory pools not seems to be the reason for this behaviour - see the attached native memory tracking results. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2228) ASYM_ENCRYPT: test with encrypt_entire_msg=true

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2228?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2228: --------------------------- Fix Version/s: 4.0.9 (was: 4.0.8) Moved to next version - will be closed if I cannot reproduce this. > ASYM_ENCRYPT: test with encrypt_entire_msg=true > ----------------------------------------------- > > Key: JGRP-2228 > URL: https://issues.jboss.org/browse/JGRP-2228 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0.9 > > Attachments: asym-encrypt.xml > > > * Start a few nodes with {{ASYM_ENCRYPT}} and {{encrypt_entire_msg}} set to {{true}} > * Kill and restart a member > * Apparently, restarting is not possible, as the new member won't be able to join the cluster > -> Verify this is true and - if yes - fix it -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2228) ASYM_ENCRYPT: test with encrypt_entire_msg=true

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2228?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2228: -------------------------------- With the attached {{asym-encrypt.xml}} and 4 nodes, members were able to leave and rejoin the cluster without problems. I also checked coordinators leaving and rejoining. The tests included both graceful- and crash-leaves. > ASYM_ENCRYPT: test with encrypt_entire_msg=true > ----------------------------------------------- > > Key: JGRP-2228 > URL: https://issues.jboss.org/browse/JGRP-2228 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0.8 > > Attachments: asym-encrypt.xml > > > * Start a few nodes with {{ASYM_ENCRYPT}} and {{encrypt_entire_msg}} set to {{true}} > * Kill and restart a member > * Apparently, restarting is not possible, as the new member won't be able to join the cluster > -> Verify this is true and - if yes - fix it -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2228) ASYM_ENCRYPT: test with encrypt_entire_msg=true

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2228?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2228: --------------------------- Attachment: asym-encrypt.xml > ASYM_ENCRYPT: test with encrypt_entire_msg=true > ----------------------------------------------- > > Key: JGRP-2228 > URL: https://issues.jboss.org/browse/JGRP-2228 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0.8 > > Attachments: asym-encrypt.xml > > > * Start a few nodes with {{ASYM_ENCRYPT}} and {{encrypt_entire_msg}} set to {{true}} > * Kill and restart a member > * Apparently, restarting is not possible, as the new member won't be able to join the cluster > -> Verify this is true and - if yes - fix it -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9472) Updated digest-auth test for JBEAP-13298 - reusing nonces

by Jan Stourac (JIRA)

[ https://issues.jboss.org/browse/WFLY-9472?page=com.atlassian.jira.plugin.... ] Jan Stourac reassigned WFLY-9472: --------------------------------- Assignee: Jan Stourac (was: Tomaz Cerar) > Updated digest-auth test for JBEAP-13298 - reusing nonces > --------------------------------------------------------- > > Key: WFLY-9472 > URL: https://issues.jboss.org/browse/WFLY-9472 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Jan Stourac > Assignee: Jan Stourac > Priority: Critical > > Update existing digest-auth tests in testsuite to cover issue described in JBEAP-13298. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9472) Updated digest-auth test for JBEAP-13298 - reusing nonces

by Jan Stourac (JIRA)

[ https://issues.jboss.org/browse/WFLY-9472?page=com.atlassian.jira.plugin.... ] Jan Stourac moved JBEAP-13602 to WFLY-9472: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9472 (was: JBEAP-13602) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) Affects Version/s: (was: 7.1.0.CR3) > Updated digest-auth test for JBEAP-13298 - reusing nonces > --------------------------------------------------------- > > Key: WFLY-9472 > URL: https://issues.jboss.org/browse/WFLY-9472 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Jan Stourac > Assignee: Tomaz Cerar > Priority: Critical > > Update existing digest-auth tests in testsuite to cover issue described in JBEAP-13298. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9471) ClassNotFoundException when loading Artemis transformer class.

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-9471: --------------------------------- Summary: ClassNotFoundException when loading Artemis transformer class. Key: WFLY-9471 URL: https://issues.jboss.org/browse/WFLY-9471 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 11.0.0.Final Reporter: Jeff Mesnil Assignee: Jeff Mesnil The org.apache.activemq.artemis module has an optional dependency on a org.apache.activemq.artemis.addons that is meant to define classes that needs to be instantiated by Artemis (e.g. divert's transformers, server interceptors, etc.). However the code that is instantiating classes from Artemis has been moved from the org.apache.activemq.artemis to the org.apache.activemq.artemis.journal module in WFLY-5522. The optional dependency to org.apache.activemq.artemis.addons should set export to true so that its classes can be loaded by the org.apache.activemq.artemis.journal module. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2227) Use of AUTH does not result in a SecurityException, but instead nodes create separate clusters with the same name

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2227?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2227. ---------------------------- Resolution: Done > Use of AUTH does not result in a SecurityException, but instead nodes create separate clusters with the same name > ----------------------------------------------------------------------------------------------------------------- > > Key: JGRP-2227 > URL: https://issues.jboss.org/browse/JGRP-2227 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.6 > Reporter: Robert Cernak > Assignee: Bela Ban > Fix For: 4.0.8 > > > I implemented method org.jgroups.auth.AuthToken#authenticate(AuthToken token, Message msg) in my class and its body contained only one line: return false; > In this way authentication should be false and I should get SecurityException. > When I started joining of nodes together to form a cluster, instead of getting SecurityException, nodes formed 2 different clusters with the same name. > I am sure method was evaluated, since I tried to run it also with breakpoint, which was triggered during joining process. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 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 October 2017