[
https://issues.apache.org/jira/browse/ARTEMIS-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906272#comment-15906272
]
Justin Bertram commented on ARTEMIS-1032:
-----------------------------------------
I'm confused. The message about not being able to set an exception listener is
accurate. Also, it's proper for the bridge to set an exception listener. My
hunch is that you're receiving this because you've configured the JMS bridge to
use a JCA connection factory (i.e. a <pooled-connection-factory> in Wildfly)
which is an invalid configuration. Can you confirm this is the case? If not,
please elaborate on your use-case.
> Cannot call conn.setExceptionListener due Java EE7 JMS spec, inside Wildfly
> 10.x
> --------------------------------------------------------------------------------
>
> Key: ARTEMIS-1032
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1032
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 1.5.3, 2.0.0
> Environment: Wildfly 10.x/ JBoss EAP 7.x
> Reporter: Greg A.
>
> conn.setExceptionListener "must not be used in a Java EE web or EJB
> application. Doing so may cause a JMSException to be thrown though this is
> not guaranteed." from JMS spec
> https://github.com/apache/activemq-artemis/blob/1.5.4/artemis-jms-server/src/main/java/org/apache/activemq/artemis/jms/bridge/impl/JMSBridgeImpl.java#L1013
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
