Hide Forgot
It seems that in case that of using hornetq for implementation of object store (configuration of transaction subsystem via <use-hornetq-store/> tag) the native library (AIO) is used automatically without necessity of user confirmation. For EAP 6.0.1 was decided that native library can't be used without explicit customer configuration request. Please check discussion on bug #900591. The NIO should be used until customer defined otherwise. The configuration option is missing in TM and after the adding it the EAP configuration should reflect fact that the default behaviour should be NIO.
The messaging subsystem defines element journal-type that defines the type of library which will be used. Possible values are ASYNCIO and NIO. <subsystem xmlns="urn:jboss:domain:messaging:1.2"> <hornetq-server> <journal-type>ASYNCIO</journal-type> ... For transaction subystem would be probably necessary to enhance schema. The transactions use element use-hornetq-store where would be fine to have possibility to define (as subelement or parameter) the type of libraries that will be used.
Jira here: https://issues.jboss.org/browse/JBTM-1480
Ivo Studensky <istudens> made a comment on jira JBTM-1480 New configuration attribute 'boolean asyncIO' has been added to the HornetqJournalEnvironmentBean. The default value is true to keep the origin behavior.
Ivo Studensky <istudens> made a comment on jira AS7-6768 The fix is available at https://github.com/istudens/jboss-as/tree/AS7-6768
Ivo Studensky <istudens> made a comment on jira JBTM-1480 Adding two another PRs for a small fix in the docs.
Ivo Studensky <istudens> made a comment on jira JBTM-1480 PRs have been merged.
Paul Robinson <paul.robinson> updated the status of jira JBTM-1480 to Closed
Moving this BZ to 6.2.0 as it changes the default behaviour of the server and introduces a new version of the schema of transaction subsystem. Because of these reasons it does not seem to belong to 6.1.1 release.
Verified for EAP 6.2.0.ER2