There are TCK7 issues with TIBCO 8 through the Generic JMS RA.
These tests fail because it is not possible to create (non-XA) auto-ack JMSContext from TIBCO's XA JMS Connection factories.
These tests are configured to use XA CF from TIBCO and expect to be able to create plain (non-XA) JMS Contexts from it (which is is doable from the perspective of the JMS API).
However, the classes from TIBCO contains a bug that prevents it.

The JNDI lookup from the Generic JMS RA fetches a TibjmsFederatedXAQueueConnectionFactory from TIBCO 8.
Calling the createContext() method on this object throws a ClassCassException "TibjmsFederatedXAQueueConnectionFactory can not be cast to TibjmsConnectionFactory".

The issue is located in TIBCO8 tibjms.jar classes:
TibjmsFederatedXAQueueConnectionFactory extends TibjmsxCFImpl that defines the _createJMSContext() method.
In this method, a new TibjmsJMSContext is instantiated.
In the constructor of TibjmsJMSContext, the TibjmsxCFImpl parameter is cast to TibjmsConnectionFactory and this raises the ClassCassException as the TibjmsxCFImpl passed is a TibjmsFederatedXAQueueConnectionFactory that has no relation with TibjmsConnectionFactory.

With this issue in the TIBCO 8 classes, the Generic JMS RA is not able to use a Tibco 8 XA ConnectionFactory to produce plain JMSContext.
The TCK7 contains tests that expects to do so as it is possible from the JMS API point of view.

Until this is fixed in TIBCO 8, we will have TCK7 failures that can be linked to this issue.

For now, I have identified such failures in:

• com.sun.ts.tests.jms.core20.connectionfactorytests
• com.sun.ts.tests.jms.core20.connectiontests