June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12031) Memory leak in wildfly transaction client

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFLY-12031?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka commented on WFLY-12031: ----------------------------------------- [~cfang] hi. Unfortunately I do not have a reproducer for this one. I did manual testing of the behaviour but I didn't automatize. I still have plan to start with some testsuite for WFTC (possibly as part of the WFTC-63) but I haven't started with that effort yet :-/ > Memory leak in wildfly transaction client > ----------------------------------------- > > Key: WFLY-12031 > URL: https://issues.jboss.org/browse/WFLY-12031 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 15.0.1.Final > Environment: wildfly-transaction-client-1.1.3.Final > wildfly.15.0.1.Final > Windows 10 > Reporter: Joachim Petrich > Assignee: Cheng Fang > Priority: Critical > > After a volume run of our system we recognized millions of entries in the openFilePaths Object of class FileSystemXAResourceRegistry. When enabling traces for org.wildfly.transaction it seems that for adding an entry a xid string is used > {code:java} > XAResourceRegistryFile(Xid xid) throws SystemException { > xaRecoveryPath.toFile().mkdir(); // create dir if non existent > final String xidString = SimpleXid.of(xid).toHexString('_'); > this.filePath = xaRecoveryPath.resolve(xidString); > openFilePaths.add(*xidString*); > {code} > and for removing the entire file path: > {code:java} > protected void removeResource(XAResource resource) throws XAException { > if (resources.remove(resource)) { > if (resources.isEmpty()) { > // delete file > try { > if (fileChannel != null) { > fileChannel.close(); > } > Files.delete(filePath); > // deleting using the filepath as key caused a memory leak, > // if xid string have been added, therefore build the xid string for removing > openFilePaths.remove(*filePath.toString()*); > {code} > We didn't find any code where this xid are cleaned up. > As workaround we additionally extract the xid String from the file path and remove the corresponding entry. > {code:java} > String xidString = filePath.toString().substring(filePath.toString().indexOf( > xaRecoveryPath.toString()) + xaRecoveryPath.toString().length() + 1); > openFilePaths.remove(xidString); > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12251) Add transitives to BOMs with dependencies

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12251?page=com.atlassian.jira.plugin... ] Eduardo Martins reassigned WFLY-12251: -------------------------------------- Assignee: Eduardo Martins (was: Brian Stansberry) > Add transitives to BOMs with dependencies > ----------------------------------------- > > Key: WFLY-12251 > URL: https://issues.jboss.org/browse/WFLY-12251 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > ... otherwise when users want to have a single dependency on the BOM they need to also import the BOM, to get the proper dependency management. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12251) Add transitives to BOMs with dependencies

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12251?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-12251: ----------------------------------- Component/s: Build System > Add transitives to BOMs with dependencies > ----------------------------------------- > > Key: WFLY-12251 > URL: https://issues.jboss.org/browse/WFLY-12251 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Reporter: Eduardo Martins > Assignee: Brian Stansberry > Priority: Major > > ... otherwise when users want to have a single dependency on the BOM they need to also import the BOM, to get the proper dependency management. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12251) Add transitives to BOMs with dependencies

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-12251: -------------------------------------- Summary: Add transitives to BOMs with dependencies Key: WFLY-12251 URL: https://issues.jboss.org/browse/WFLY-12251 Project: WildFly Issue Type: Enhancement Reporter: Eduardo Martins Assignee: Brian Stansberry ... otherwise when users want to have a single dependency on the BOM they need to also import the BOM, to get the proper dependency management. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4495) Upgrade wildfly-openssl from 1.0.6.Final to 1.0.7.Final

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4495?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4495: -------------------------------- Fix Version/s: 9.0.2.Final 10.0.0.Beta1 > Upgrade wildfly-openssl from 1.0.6.Final to 1.0.7.Final > ------------------------------------------------------- > > Key: WFCORE-4495 > URL: https://issues.jboss.org/browse/WFCORE-4495 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Affects Versions: 9.0.0.Final > Reporter: Ingo Weiss > Assignee: Flavia Rainone > Priority: Major > Fix For: 9.0.2.Final, 10.0.0.Beta1 > > > https://github.com/wildfly/wildfly-openssl/compare/1.0.6.Final...master -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12228) Upgrade microprofile-health to 2.0.1

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFLY-12228?page=com.atlassian.jira.plugin... ] Jeff Mesnil commented on WFLY-12228: ------------------------------------ Right, MP Health 2.0.1 is the version in MicroProfile 3.0 umbrella > Upgrade microprofile-health to 2.0.1 > ------------------------------------ > > Key: WFLY-12228 > URL: https://issues.jboss.org/browse/WFLY-12228 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2273) ASYM_ENCRYPT: deprecate encrypt_entire_message

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2273?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2273: -------------------------------- You're right, of course! I changed the initial comment, thanks for catching this! > ASYM_ENCRYPT: deprecate encrypt_entire_message > ---------------------------------------------- > > Key: JGRP-2273 > URL: https://issues.jboss.org/browse/JGRP-2273 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.0.12 > > > In {{ASYM_ENCRYPT}}, {{encrypt_entire_message}} encrypts not only the payload, but also metadata such as destination and sender's address, headers and flags. > The rationale was to prevent replay attacks. However, this is not an issue, as replayed messages will simply get dropped by the retransmission layer (e.g. NAKACK2 or UNICAST3). > If people still want this feature, they can write a protocol _above_ {{ASYM_ENCRYPT}}, which serializes the entire message into the payload of a new message, and this would be exactly the same as setting {{encrypt_entire_message}} to {{true}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2273) ASYM_ENCRYPT: deprecate encrypt_entire_message

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2273?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-2273 at 6/28/19 2:20 AM: --------------------------------------------------------- A new protocol {{SERIALIZE}} has been created and can be used instead of {{encrypt_entire_message}} as follows: {code:xml} ... <ASYM_ENCRYPT/> <SERIALIZE/> ... {code} An example is shown in {{EncryptTest.testCapturingOfMessageByNonMemberAndResending()}} was (Author: belaban): A new protocol {{SERIALIZE}} has been created and can be used instead of {{encrypt_entire_message}} as follows: {code:xml} ... <SERIALIZE/> <ASYM_ENCRYPT/> ... {code} An example is shown in {{EncryptTest.testCapturingOfMessageByNonMemberAndResending()}} > ASYM_ENCRYPT: deprecate encrypt_entire_message > ---------------------------------------------- > > Key: JGRP-2273 > URL: https://issues.jboss.org/browse/JGRP-2273 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.0.12 > > > In {{ASYM_ENCRYPT}}, {{encrypt_entire_message}} encrypts not only the payload, but also metadata such as destination and sender's address, headers and flags. > The rationale was to prevent replay attacks. However, this is not an issue, as replayed messages will simply get dropped by the retransmission layer (e.g. NAKACK2 or UNICAST3). > If people still want this feature, they can write a protocol _above_ {{ASYM_ENCRYPT}}, which serializes the entire message into the payload of a new message, and this would be exactly the same as setting {{encrypt_entire_message}} to {{true}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12236) Log spam in category org.apache.activemq.audit.base

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12236?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-12236: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/12386, https://github.com/wildfly/wildfly/pull/12395 (was: https://github.com/wildfly/wildfly/pull/12386) > Log spam in category org.apache.activemq.audit.base > --------------------------------------------------- > > Key: WFLY-12236 > URL: https://issues.jboss.org/browse/WFLY-12236 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 17.0.0.Final > Reporter: Brian Stansberry > Assignee: James Perkins > Priority: Blocker > Fix For: 18.0.0.Beta1 > > > Artemis is spamming the logs with what look like low-level messages, but recorded at INFO level: > {code} > 14:43:29,427 INFO [org.apache.activemq.audit.base] (Thread-40 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@39c78b17)) AMQ601265: User 4dd3d543-be6a-4a9a-b5d2-5cac9efe8f0f is creating a core consumer on target resource ServerSessionI mpl(jms-session=*N/A*) [with parameters: [175, jms.queue.DCS_DEV.processDcsIntegrationQueue, null, 0, false, true, null]] > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12250) Align jgroups stacks in example configurations with default ha configuration

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12250: ----------------------------------- Summary: Align jgroups stacks in example configurations with default ha configuration Key: WFLY-12250 URL: https://issues.jboss.org/browse/WFLY-12250 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 17.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian Jira (v7.12.1#712002)

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 June 2019