Bug 778124 (SOA-636) - SOA-P cannot be fully integrated with Tibco EMS
Summary: SOA-P cannot be fully integrated with Tibco EMS
Keywords:
Status: CLOSED NOTABUG
Alias: SOA-636
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB, JBoss Messaging, Configuration
Version: 4.2 CP02
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.3 GA
Assignee: Kevin Conner
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-07-21 08:19 UTC by Jiri Pechanec
Modified: 2008-09-12 03:41 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-09-12 03:41:06 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBQA-1738 0 Major Closed Verify Tibco integration to ESB with JCA resource adapter, setup Hudson job to run with "jms-provider" tests 2014-03-25 15:20:48 UTC
Red Hat Issue Tracker SOA-636 0 Critical Closed SOA-P cannot be fully integrated with Tibco EMS 2014-03-25 15:20:47 UTC

Description Jiri Pechanec 2008-07-21 08:19:21 UTC
project_key: SOA

I tried to integrate Tibco EMS to enable JMS/JCA provider for it

I followed the steps in the document http://wiki.jboss.org/wiki/IntegrationWithTibcoEMS

Unfortunately the integration does not work as the exception is thrown
09:49:17,384 ERROR [JmsActivation] Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@d5cd23(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@13e9963 destination=queue/pt_tx_bpm_gw isTopic=false tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=1 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
java.lang.ClassCastException: com.tibco.tibjms.naming.TibjmsFederatedQueue
        at org.jboss.jms.client.container.SessionAspect.handleCreateConnectionConsumer(SessionAspect.java:766)
        at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect1.invoke(SessionAspect1.java)
        at org.jboss.jms.client.delegate.ClientConnectionDelegate$createConnectionConsumer_7915292773999367429.invokeNext(ClientConnectionDelegate$createConnectionConsumer_7915292773999367429.java)
        at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
        at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
        at org.jboss.jms.client.delegate.ClientConnectionDelegate$createConnectionConsumer_7915292773999367429.invokeNext(ClientConnectionDelegate$createConnectionConsumer_7915292773999367429.java)
        at org.jboss.jms.client.delegate.ClientConnectionDelegate.createConnectionConsumer(ClientConnectionDelegate.java)
        at org.jboss.jms.client.JBossConnection.createConnectionConsumer(JBossConnection.java:140)
        at org.jboss.resource.adapter.jms.inflow.JmsServerSessionPool.setupConsumer(JmsServerSessionPool.java:288)
        at org.jboss.resource.adapter.jms.inflow.JmsServerSessionPool.start(JmsServerSessionPool.java:91)
        at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupSessionPool(JmsActivation.java:551)
        at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:323)
        at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:259)
        at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:605)
        at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
        at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
        at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756)
        at java.lang.Thread.run(Thread.java:595)

I have not tried to get JBM out to test if the integration works without it

Comment 1 Jiri Pechanec 2008-07-21 08:20:44 UTC
Link: Added: This issue related JBQA-1738


Comment 2 Jiri Pechanec 2008-07-21 09:06:07 UTC
Forgot to set providerAdapterJNDI="java:/TIBCOJMSProvider"


Note You need to log in before you can comment on or make changes to this bug.