We are using jboss-structure.xml to enforce classpath ordering which is a necessary legacy requirment of the application.
Here are the MDB annotations:
@MessageDriven(name = "EventLogConsumerMDB", activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Topic"),
@ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
@ActivationConfigProperty(propertyName = "destination", propertyValue = "topic/com.xst.dao.ctl.IEventLogEntry"),
@ActivationConfigProperty(propertyName = "messageSelector", propertyValue = "loggerCategory NOT LIKE 'com.store.dataloader.download_id=configurator::%' "
+ "AND loggerCategory NOT LIKE 'com.store.dataloader.download_id=dataload::%' "
+ "AND loggerCategory NOT LIKE 'com.sysadmin.data.failover%'"),
@ActivationConfigProperty(propertyName = "subscriptionDurability", propertyValue = "Durable"),
@ActivationConfigProperty(propertyName = "clientId", propertyValue = "EventLogConsumerMDB"),
@ActivationConfigProperty(propertyName = "subscriptionName", propertyValue = "StoreEventLogs") }, messageListenerInterface = MessageListener.class)
public class EventLogConsumerMDB implements MessageDrivenBean, MessageListener {}
@MessageDriven(name = "DataloadEventLogConsumerMDB", activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Topic"),
@ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
@ActivationConfigProperty(propertyName = "destination", propertyValue = "topic/com.xst.dao.ctl.IEventLogEntry"),
@ActivationConfigProperty(propertyName = "messageSelector", propertyValue = "loggerCategory LIKE 'com.store.dataloader.download_id=dataload::%'"),
@ActivationConfigProperty(propertyName = "subscriptionDurability", propertyValue = "Durable"),
@ActivationConfigProperty(propertyName = "clientId", propertyValue = "DataloadEventLogConsumerMDB"),
@ActivationConfigProperty(propertyName = "subscriptionName", propertyValue = "StoreDataloadEventLogs")}, messageListenerInterface = MessageListener.class)
public class DataloadEventLogConsumerMDB
extends EventLogConsumerMDB{}
@MessageDriven(name = "CfgEventLogConsumerMDB", activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Topic"),
@ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
@ActivationConfigProperty(propertyName = "destination", propertyValue = "topic/com.xst.dao.ctl.IEventLogEntry"),
@ActivationConfigProperty(propertyName = "messageSelector", propertyValue = "loggerCategory LIKE 'com.store.dataloader.download_id=configurator::%'"),
@ActivationConfigProperty(propertyName = "subscriptionDurability", propertyValue = "Durable"),
@ActivationConfigProperty(propertyName = "clientId", propertyValue = "CfgEventLogConsumerMDB"),
@ActivationConfigProperty(propertyName = "subscriptionName", propertyValue = "ConfiguratorEventLogs") }, messageListenerInterface = MessageListener.class)
public class CfgEventLogConsumerMDB extends EventLogConsumerMDB {}
@MessageDriven(name = "OfflineEventLogConsumerMDB", activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Topic"),
@ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
@ActivationConfigProperty(propertyName = "destination", propertyValue = "topic/com.xst.dao.ctl.IEventLogEntry"),
@ActivationConfigProperty(propertyName = "messageSelector", propertyValue = "loggerCategory LIKE 'com.sysadmin.data.failover%'"),
@ActivationConfigProperty(propertyName = "subscriptionDurability", propertyValue = "Durable"),
@ActivationConfigProperty(propertyName = "clientId", propertyValue = "OfflineEventLogConsumerMDB"),
@ActivationConfigProperty(propertyName = "subscriptionName", propertyValue = "StoreOfflineEventLogs")}, messageListenerInterface = MessageListener.class)
public class OfflineEventLogConsumerMDB
extends EventLogConsumerMDB {}
I'll try the logging as well and see if there if JBoss reports anything regarding the ejb-jar.