WebSphere Application Server & Liberty

 View Only

 WebSphere Thread Hang After Upgrading to Windows 11

Zeeshan Naqvi's profile image
Zeeshan Naqvi posted Tue June 17, 2025 04:52 AM

Hi IBM Community,

We recently upgraded our development machine from Windows 10 to Windows 11, and since then, we’ve started encountering thread hang warnings in WebSphere Application Server during application startup. This issue did not exist on Windows 10 under the same setup.

Issue Details

  • Server: WebSphere Application Server (Traditional)

  • App: Legacy monolith EAR application (banking domain)

  • JVM: IBM JDK

  • Database: PostgreSQL 16.1

  • OS (Post-upgrade): Windows 11 Pro

  • Problem: During deployment/startup of the auth.war module in our EAR, we are consistently seeing this thread hang warning:

WSVR0605W: Thread "server.startup : 1" has been active for 741331 milliseconds and may be hung.

The thread trace points to our CharacteristicLocator.loadZoneConfigs() method, specifically where SortedSet<Characteristic> chartcs = new TreeSet<>(); is populated. This method internally relies on a custom compareTo() implementation.

Symptoms Observed

  • Startup gets stuck during zone config processing

  • Logs show activity halting around creation of TreeSet<Characteristic>

  • No changes were made in application code or server configs — only OS was upgraded

Troubleshooting Done

  • Reviewed compareTo() logic for nulls, exceptions, infinite loops

  • Added verbose logging in the flow (go(), process(), and compareTo())

  • Verified same codebase works fine on other machines still running Windows 10

  • No JVM exceptions, GC issues, or DB connection problems in the logs

  • PostgreSQL and JDBC driver versions are the same pre- and post-upgrade

  • Upgraded websphere components to latest versions: IBM HTTP Server for WebSphere Application Server 9.0.5.20, 
    IBM HTTP Server for WebSphere Application Server 9.0.5.20

Main Ask

Has anyone encountered WebSphere thread hangs or unexpected behavior after upgrading to Windows 11?

  • Are there known compatibility issues between WebSphere and Windows 11?

  • Could any changes in file system, thread scheduling, or JVM behavior on Windows 11 affect this?

  • Are there any specific WebSphere hotfixes or settings we should check for Windows 11 environments

Happy to share more logs or class definitions if needed. Appreciate any guidance from those who've faced similar issues or have insight into how Windows 11 might be affecting the WebSphere runtime

Related Content