May 2025 - wildfly-dev - Jboss List Archives

Possible component upgrades report - wildfly-elytron:1.x

by thofman＠redhat.com

10 months, 2 weeks

3
2
0 / 0

Possible component upgrades report - elytron-web:4.x

by thofman＠redhat.com

10 months, 3 weeks

1
0
0 / 0

Possible component upgrades report - wildfly-core:main

by thofman＠redhat.com

10 months, 3 weeks

1
0
0 / 0

Fwd: [WildFly] New requests from members for Copilot Business

by Brian Stansberry

I've gotten a few emails like the one below where a Github wildfly organization member has requested access to Copilot. Please be aware that Copilot is not free and there is no funding stream or billing setup behind the wildfly and wildfly-extras Github organizations to pay for it. (And personally I prefer it that way.) So this won't be happening. Best regards, Brian ---------- Forwarded message --------- From: GitHub <noreply(a)noreply.github.com> Date: Thu, May 15, 2025 at 12:10 PM Subject: [WildFly] New requests from members for Copilot Business To: Brian Stansberry <brian.stansberry(a)redhat.com> Cc: Member feature requested <member_feature_requested(a)noreply.github.com> [image: GitHub]You have 1 new request from members for Copilot Business. *Members of your WildFly organization want Copilot Business* 1 member of your *wildfly* organization has requested access to Copilot Business since you last reviewed requests from members. Learn more about Copilot Business <https://docs.github.com/copilot/overview-of-github-copilot/about-github-c...> Research has found GitHub Copilot helps *96%* of developers code faster, *88%* feel more productive, and *74%* feel more fulfilled at work. Review requests from members <https://github.com/organizations/wildfly/settings/member_feature_requests...> Sign in to GitHub <https://github.com/login>・ Notifications settings <https://github.com/organizations/wildfly/settings/member_feature_requests> You are receiving this email because members of your organization have requested access to specific GitHub features. GitHub, Inc. ・ Colin P Kelly Jr Street ・ San Francisco, CA 94107 — View it on GitHub <https://github.com/organizations/wildfly/settings/member_feature_requests> or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACJB2XCC4L6PXFJCBPADS3...> . You are receiving this email because you are subscribed to this thread. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email...> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer...> . -- Brian Stansberry Principal Architect, Red Hat JBoss EAP WildFly Project Lead He/Him/His

10 months, 3 weeks

1
0
0 / 0

WildFly 36.0.1.Final Released

by Kabir Khan

I am pleased to announce the release of WildFly 36.0.1.Final which is now available for download from https://www.wildfly.org/downloads/ For more information about the issues fixed in this release please see the release announcement <https://www.wildfly.org/news/2025/05/15/WildFly3601-Released/> . Please update to this release and in the meantime the team will continue our work towards WildFly 37. Enjoy! Kabir

10 months, 3 weeks

2
1
0 / 0

Possible component upgrades report - wildfly:main

by thofman＠redhat.com

10 months, 3 weeks

1
0
0 / 0

Possible component upgrades report - wildfly-elytron:1.x

by thofman＠redhat.com

10 months, 3 weeks

1
0
0 / 0

Possible component upgrades report - elytron-web:4.x

by thofman＠redhat.com

10 months, 4 weeks

1
0
0 / 0

Possible component upgrades report - wildfly-core:main

by thofman＠redhat.com

10 months, 4 weeks

1
0
0 / 0

Moving to JBoss Threads 3.9.x

by Brian Stansberry

Hi David, We've had some Zulip discussions over the last few months about getting WF up to date with JBoss Threads. I've been looking at it some and figured I'd start a thread, for general status discussions plus to ask a specific question. Overall I think there are three things to consider: 1) The AsyncFuture APIs. David added these back into threads 3.9 (thanks!) so I'll *assume* all is well. We need to test to verify of course. 2) Alignment verification. Other libs we integrate use JBoss Threads 3 minors before 3.9 so we'll need to verify the upgrade is ok. 3) The WildFly Core threads module. This is what I've been looking at. I plan to: a) change any resources that provide non-blocking pools to provide to EnhancedQueueExecutor. b) change any resources that provide blocking pools to provide the JBoss Threads 3 ManagedThreadPoolExecutor. c) For any resources or attributes that are unused in WildFly, particularly those that involve blocking behavior, deprecate the management API bits (if not already done) and deprecate the classes for removal. AFAICT we only have one use of blocking pools in WildFly, which leads to: The specific questions for Tomek and David: The JCA subsystem creates blocking bound queues for its work manager pools. EnhancedQueueExecutor is non-blocking. 1) Tomek, these should continue to be blocking pools, yes? From my naive POV, I figure if people are configuring these they have reasons for their settings and changing pool semantics could be problematic. But I could be wrong. 2) David, do you have any sense of the perf impact of moving from the JBoss Threads 2 QueueExecutor (with blocking == true) to the JBoss Threads 3 ManagedThreadPoolExecutor, which basically means moving to the Java SE ThreadPoolExecutor? Assuming the work manager pools remain as blocking pools, that switch of underlying pool impl would be the likely migration. Best regards, -- Brian Stansberry Principal Architect, Red Hat JBoss EAP WildFly Project Lead He/Him/His

11 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

wildfly-dev May 2025