[
https://issues.apache.org/jira/browse/ARTEMIS-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906674#comment-15906674
]
Justin Bertram commented on ARTEMIS-1032:
-----------------------------------------
So, you are using a JCA based JMS connection factory with the JMS bridge which,
as I noted previously, is an invalid configuration. You should configure the
JMS bridge to use a non-JCA based, normal JMS connection factory just as you
would do for any remote JMS client connecting to WebSphereMQ. You just need to
configure the JNDI properties for WebSphereMQ in the JMS bridge configuration
and you'll be set.
To be clear, the JMS bridge is a pretty basic and generic component. It's not
necessarily meant to be used in an application server which provides a JCA
implementation and doesn't benefit from any of the things that components
usually benefit from by using JCA (e.g. connection pooling, automatic
transaction enlistment, etc.).
{quote}
where can I find I cannot use JCA provider for JMS bridge ?
{quote}
I'm not exactly sure what you're asking here. Can you clarify your question?
> 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.
> Assignee: Justin Bertram
>
> 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)
