Bug 1267241 - java.lang.ClassCastException: org.jboss.resource.adapter.jms.JmsConnectionFactoryImpl cannot be cast to javax.jms.XAConnectionFactory
Summary: java.lang.ClassCastException: org.jboss.resource.adapter.jms.JmsConnectionFac...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: eap-docs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-29 12:36 UTC by vellingiri
Modified: 2015-10-28 15:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Build Name: 22815, Administration and Configuration Guide-6.3-1 Build Date: 19-11-2014 09:29:31 Topic ID: 23310-623866 [Latest]
Last Closed: 2015-10-28 15:00:34 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description vellingiri 2015-09-29 12:36:02 UTC 
Title: Configure a Generic JMS Resource Adapter for Use with a Third-party JMS Provider

Describe the issue:
Even though the Topic and queue is created as XA.

05:34:33,039 ERROR [org.jboss.resource.adapter.jms.inflow.JmsActivation] (default-threads - 1) Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@1517225f(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@8e868bdc destination=testTopic destinationType=javax.jms.Topic acknowledgeMode=Auto-acknowledge subscriptionDurability=false reconnectInterval=10 reconnectAttempts=-1 user=admin password=<not shown> maxMessages=1 minSession=1 maxSession=15 connectionFactory=TestTopicCF): java.lang.ClassCastException: org.jboss.resource.adapter.jms.JmsConnectionFactoryImpl cannot be cast to javax.jms.XAConnectionFactory
	at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupConnection(JmsActivation.java:437) [generic-jms-ra-jar-1.0.7.Final-redhat-1.jar:1.0.7.Final-redhat-1]

Request Help
Comment 1 anrobert 2015-10-28 15:05:47 UTC 
This issue cannot be resolved via a documentation BZ. Please contact Red Hat Technical Support to debug this particular issue: https://access.redhat.com/support/contact/technicalSupport/
Note You need to log in before you can comment on or make changes to this bug.