After the Wildfly server installation, the following configuration changes need to be done to integrate with the FioranoMQ resource adapter:
If the Wildfly application server ships and loads the jms2.0 specification jar by default, then the same jar needs to be used by the MDB by adding a dependency to prevent issues with respect to loading of classes (scope).
For example, Wildfly version 26.1.1 ships and loads the jms jar from $WILDFLY_HOME/modules/system/layers/base/javax/jms/api/main/. So a dependency such as the below needs to be added under META-INF/MANIFEST.MF of MDB:Since FioranoMQ runtime uses facade-based logging framework 'slf4j', Wildfly server profile (which also contains logger configuration) needs to be edited to enable and configure FioranoMQ client runtime loggers.
For example, if Wildfly server's standalone profile is used and if the FioranoMQ runtime logger 'Fiorano.FMQ.Services.ClientRootLoggerServices.FMQClientLoggerServices' needs to be configured to level TRACE, then the following log snippet needs to be included in the standalone.xml (located by default under $WILDFLY_HOME/standalone/configuration) file under the logging subsystem tag <subsystem xmlns="urn:jboss:domain:logging: "In order not to deploy the Wildfly server's implicit logging into the deployment but to use an exclusive logging framework such as log4j2 in the deployment, the attribute 'logging-api-dependencies' needs to be disabled under the logging subsystem configuration tag "<subsystem xmlns="urn:jboss:domain:logging:" as mentioned below and the logger configurations need to be included (log4j2.properties/xml incase of log4j2 framework) in the deployment: