Merge pull request #18187 from Sreekala-Gopakumar/41RelNote

Update 0.41.0 release note

doc/release-notes/0.41/0.41.md

@@ -68,6 +68,30 @@ The following table covers notable changes in v0.41.0. Further information about
 <td valign="top">In the earlier releases, if the <tt>-Xshareclasses:readonly</tt> option and the JITServer AOT cache feature were both enabled at the same time at a JITServer client, the client could not use the JITServer AOT cache because the cache for storing data that the JITServer AOT cache needed was read-only.
 Now, with the change in behavior of the <tt>-Xshareclasses:readonly</tt> option, the shared class cache startup creates a temporary new (writable) top layer that the JITServer AOT cache can use to store data that it needs to function.</td>
 </tr>
+<tr>
+<td valign="top"><a href="https://github.com/eclipse-openj9/openj9/issues/17215">#17215</a></td>
+<td valign="top">New <tt>-XX:[+|-]EnableDynamicAgentLoading</tt> option is added to enable or disable the dynamic loading of agents into a running VM.</tt></td>
+<td valign="top">All versions</td>
+<td valign="top">With the Attach API, your application can load an agent dynamically into a running VM to run tasks. You can disable the dynamic loading of the agents into a VM after startup with the <tt>-XX:-EnableDynamicAgentLoading</tt> option to prevent the misuse of the Attach API to dynamically load an agent without the approval of the application owner.<br>For Java 21 and later, warnings are issued when the agents are loaded dynamically without specifying the <tt>-XX:+EnableDynamicAgentLoading</tt> option and the same agents were not loaded before.</td>
+</tr>
+<tr>
+<td valign="top"><a href="https://github.com/eclipse-openj9/openj9/issues/17643">#17643</a></td>
+<td valign="top">New <tt>-XX:ContinuationCache</tt> option is added to tune the continuation tier 1 and 2 cache size.</tt></td>
+<td valign="top">OpenJDK 21 and later</td>
+<td valign="top">New continuations can reuse the cached structure instead of allocating new memory for it. The continuation cache is implemented in two tiers, tier 1 and tier 2. You can set the maximum size for the two tiers with the <tt>-XX:ContinuationCache</tt> option. If an application uses more than 10000 virtual threads, setting a larger cache size might improve performance.</td>
+</tr>
+<tr>
+<td valign="top"><a href="https://github.com/ibmruntimes/openj9-openjdk-jdk17/pull/265">#265</a></td>
+<td valign="top">New <tt>-XX:[+|-]UseZlibNX</tt> option is added to control the loading of the <tt>zlibnx</tt> library in the <tt>LIBPATH</tt> environment variable.</td>
+<td valign="top">All versions (AIX&reg;)</td>
+<td valign="top">The AIX system adds the <tt>zlibNX</tt> library location, if available, to the <tt>LIBPATH</tt> variable by default. But, having the <tt>zlibNX</tt> library directory location in the <tt>LIBPATH</tt> variable might cause some issues. You can disable adding of the <tt>zlibNX</tt> library location to that variable with the <tt>-XX:-UseZlibNX</tt> option.</td>
+</tr>
+<tr>
+<td valign="top"><a href="https://github.com/eclipse-openj9/openj9/issues/13686">#13686</a></td>
+<td valign="top">OpenSSL 3.x is now supported on all operating systems.</td>
+<td valign="top">All versions</td>
+<td valign="top">In the earlier releases, OpenSSL 3.x was supported only on Linux. Now, OpenSSL 3.x is supported on all operating systems.</td>
+</tr>
 
 </tbody>
 </table>