runtime, that's everything from Windows desktops to IBM mainframes. Amazing performance. Our ground-breaking high performance journal provides persistent messaging performance at rates normally seen for non-persistent older files it changes to an old-config-bkp. folder within the instance dir. Similarly, if you had customised the old logging.properties file you may need to prepare analogous changes for the new log4j2 deleted. 3. Related startup script or profile cleanups are needed: a diff file demonstrating the changes needed since 2.26.0 is available here for *nix or here for Windows. 2.26.0 Full release notes

runtime, that's everything from Windows desktops to IBM mainframes. Amazing performance. Our ground-breaking high performance journal provides persistent messaging performance at rates normally seen for non- older files it changes to an old-config-bkp. folder within the instance dir. Similarly, if you had customised the old logging.properties file you may need to prepare analogous changes for the new log4j2 deleted. 3. Related startup script or profile cleanups are needed: a diff file demonstrating the changes needed since 2.26.0 is available here for *nix or here for Windows. 2.26.0 Full release notes

runtime, that's everything from Windows desktops to IBM mainframes. Amazing performance. Our ground-breaking high performance journal provides persistent messaging performance at rates normally seen for non- older files it changes to an old-config-bkp. folder within the instance dir. Similarly, if you had customised the old logging.properties file you may need to prepare analogous changes for the new log4j2 deleted. 3. Related startup script or profile cleanups are needed: a diff file demonstrating the changes needed since 2.26.0 is available here for *nix or here for Windows. 2.26.0 Full release notes

runtime, that's everything from Windows desktops to IBM mainframes. Amazing performance. Our ground-breaking high performance journal provides persistent messaging performance at rates normally seen for non- older files it changes to an old-config-bkp. folder within the instance dir. Similarly, if you had customised the old logging.properties file you may need to prepare analogous changes for the new log4j2 deleted. 3. Related startup script or profile cleanups are needed: a diff file demonstrating the changes needed since 2.26.0 is available here for *nix or here for Windows. 2.26.0 Full release notes

runtime, that's everything from Windows desktops to IBM mainframes. Amazing performance. Our ground-breaking high performance journal provides persistent messaging performance at rates normally seen for non- clients including core JMS clients and core connections between cluster nodes. Although this is a "breaking" change, not performing hostname verification is a security risk (e.g. due to man-in-the- middle javax.net.ssl.SSLContext was created for every connection. This would implicitly pick up any changes to the keystore and truststore for any new connection. However, this was grossly inefficient and

runtime, that's everything from Windows desktops to IBM mainframes. Amazing performance. Our ground-breaking high performance journal provides persistent messaging performance at rates normally seen for non- clients including core JMS clients and core connections between cluster nodes. Although this is a "breaking" change, not performing hostname verification is a security risk (e.g. due to man-in-the- middle javax.net.ssl.SSLContext was created for every connection. This would implicitly pick up any changes to the keystore and truststore for any new connection. However, this was grossly inefficient and

runtime, that's everything from Windows desktops to IBM mainframes. Amazing performance. Our ground-breaking high performance journal provides persistent messaging performance at rates normally seen for non- Paging can now be configured by message count. Upgrading from older versions 1. Due to XML schema changes to correct an inaccurate domain name 2 files will need to be updated: i. etc/bootstrap.xml ii xmlns="http://activemq.apache.org/schema"> 2. If you're using JDBC persistence then due to the changes in ARTEMIS- 3679 you'll need to update your database. The column HOLDER_EXPIRATION_TIME on the

runtime, that's everything from Windows desktops to IBM mainframes. Amazing performance. Our ground-breaking high performance journal provides persistent messaging performance at rates normally seen for non- Paging can now be configured by message count. Upgrading from older versions 1. Due to XML schema changes to correct an inaccurate domain name 2 files will need to be updated: i. etc/bootstrap.xml ii xmlns="http://activemq.apache.org/schema"> 2. If you're using JDBC persistence then due to the changes in ARTEMIS- 3679 you'll need to update your database. The column HOLDER_EXPIRATION_TIME on the

runtime, that's everything from Windows desktops to IBM mainframes. Amazing performance. Our ground-breaking high performance journal provides persistent messaging performance at rates normally seen for non- Paging can now be configured by message count. Upgrading from older versions Due to XML schema changes to correct an inaccurate domain name 2 files will need to be updated: 1. etc/bootstrap.xml 2 clients including core JMS clients and core connections between cluster nodes. Although this is a "breaking" change, not performing hostname verification is a security risk (e.g. due to man-in-the- Versions

runtime, that's everything from Windows desktops to IBM mainframes. Amazing performance. Our ground-breaking high performance journal provides persistent messaging performance at rates normally seen for non- clients including core JMS clients and core connections between cluster nodes. Although this is a "breaking" change, not performing hostname verification is a security risk (e.g. due to man-in-the- middle javax.net.ssl.SSLContext was created for every connection. This would implicitly pick up any changes to the keystore and truststore for any new connection. However, this was grossly inefficient and