Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
7.3.6.GA
-
False
-
False
-
Undefined
-
Description
We spotted an issue with Message Driven Beans when running inside image registry.redhat.io/jboss-eap-7/eap73-openjdk8-openshift-rhel7;
Basically it looks like that the following settings on the MDB do not work any more and the MDB doesn't receive messages from the configured queue:
@ActivationConfigProperty(propertyName = "destination", propertyValue = "inQueue"), @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "connectionFactoryLookup", propertyValue = "java:jboss/RemoteJmsXA"), @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge")
A workaround exists and consists in replacing the EAP specific property "destination" wit h the standard property "destinationLookup":
@ActivationConfigProperty(propertyName = "destinationLookup", propertyValue = "java:/jms/amq/queue/inQueue"), @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"), @ActivationConfigProperty(propertyName = "connectionFactoryLookup", propertyValue = "java:jboss/RemoteJmsXA")
Please note we could not reproduce the issue locally (i.e. outside OpenShift) using the zip distribution jboss-eap-7.3.6.zip; this suggests the issue is related to the eap73-openjdk8-openshift-rhel7 image.
Please also note that the application used to reproduce the issue is an adapted version of the EAP quick-start helloworld-mdb.