13.0 Full release notes. Highlights: Management methods for an address' duplicate ID cache to check the cache's size and clear it Support for min/max expiry-delay Per-acceptor security domains Command-line Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names use jakarta insead of javax . This difference was introduced due to the move from Oracle's Bootstrap dependencies like logging handlers must be accessible by the log manager at boot time. Package the dependency in a jar and put it on the boot classpath before of log manager jar. This can be

release notes. Versions 18 Highlights: Management methods for an address' duplicate ID cache to check the cache's size and clear it Support for min/max expiry-delay Per-acceptor security domains Command-line Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names use jakarta insead of javax . This difference was introduced due to the move from Oracle's Bootstrap dependencies like logging handlers must be accessible by the log manager at boot time. Package the dependency in a jar and put it on the boot classpath before of log manager jar. This can be

13.0 Full release notes. Highlights: Management methods for an address' duplicate ID cache to check the cache's size and clear it Support for min/max expiry-delay Per-acceptor security domains Command-line Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names use jakarta insead of javax . This difference was introduced due to the move from Oracle's Bootstrap dependencies like logging handlers must be accessible by the log manager at boot time. Package the dependency in a jar and put it on the boot classpath before of log manager jar. This can be

13.0 Full release notes. Highlights: Management methods for an address' duplicate ID cache to check the cache's size and clear it Support for min/max expiry-delay Per-acceptor security domains Command-line Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names use jakarta insead of javax . This difference was introduced due to the move from Oracle's Bootstrap dependencies like logging handlers must be accessible by the log manager at boot time. Package the dependency in a jar and put it on the boot classpath before of log manager jar. This can be

release notes. Versions 15 Highlights: Management methods for an address' duplicate ID cache to check the cache's size and clear it Support for min/max expiry-delay Per-acceptor security domains Command-line Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names use jakarta insead of javax . This difference was introduced due to the move from Oracle's Bootstrap dependencies like logging handlers must be accessible by the log manager at boot time. Package the dependency in a jar and put it on the boot classpath before of log manager jar. This can be

13.0 Full release notes. Highlights: Management methods for an address' duplicate ID cache to check the cache's size and clear it Support for min/max expiry-delay Per-acceptor security domains Command-line Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names use jakarta insead of javax . This difference was introduced due to the move from Oracle's Bootstrap dependencies like logging handlers must be accessible by the log manager at boot time. Package the dependency in a jar and put it on the boot classpath before of log manager jar. This can be

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 9.3. OpenWire Destination Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 13.7. Setting The Destination Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 40.5. Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.0 Full release notes. Highlights: Management methods for an address' duplicate ID cache to check the cache's size and clear it Support for min/max expiry-delay Per-acceptor security domains Command-line Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names use jakarta insead of javax . This difference was introduced due to the move from Oracle's Bootstrap dependencies like logging handlers must be accessible by the log manager at boot time. Package the dependency in a jar and put it on the boot classpath before of log manager jar. This can be

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 9.3. OpenWire Destination Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 13.7. Setting The Destination Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 40.5. Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 9.3. OpenWire Destination Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 13.7. Setting The Destination Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 40.5. Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .