Does OC4J's built-in JMS support transactions?

Question

I am using Oracle App Server 10.1.3.4 and OC4J 10.1.3.4, with the built-in OC4J JMS implementation. I have created a simple MDB that receives messages in the onMessage() method, and rolls back the transaction by throwing a runtime exception. (I have also tried rolling back the transaction by calling messageDrivenContext.setRollbackOnly().) In either case, the result is the same. The message is basically lost and never redelivered. If the transaction is rolled back, shouldn't the message be added back to the queue for redelivery? I have waited several minutes, and no redelivery ever occurs.
My code looks something like this:
@MessageDriven(activationConfig = {
          @ActivationConfigProperty(propertyName = "ConnectionFactoryJndiName",
                    propertyValue = "jms/QueueConnectionFactory"),
          @ActivationConfigProperty(propertyName = "DestinationName", propertyValue = "jms/MyQueue"),
          @ActivationConfigProperty(propertyName = "DestinationType", propertyValue = "javax.jms.Queue"),
          @ActivationConfigProperty(propertyName = "ReceiverThreads", propertyValue = "5")
@TransactionManagement(TransactionManagementType.CONTAINER)
@TransactionAttribute(TransactionAttributeType.REQUIRED)
public class BidOptimizeMDB implements MessageListener {
     public final void onMessage(final Message msg) {
          throw new EJBException();
In jms.xml:
<queue-connection-factory name="jms/QueueConnectionFactory" location="jms/QueueConnectionFactory" />
<queue name="MyQueue" location="jms/SEMBidQueue" persistence-file="MyQueue">

Answer 1

You "care if it is a global transaction" because you use the corresponding annotation .
@TransactionManagement(TransactionManagementType.CONTAINER)
@TransactionAttribute(TransactionAttributeType.REQUIRED)This makes OC4J start a global transaction. Your config uses a non-xa connection factory that does not obey the Transaction Manager and setRollbackOnly does not work for this reason.
There is another problem with your setup.
"For message-driven beans using the OEMS JMS (in-memory or file-based) message service provider, <Required> is supported only if you access this message service provider using the Oracle JMS Connector. For more information, see [Restrictions When Accessing a Message Service Provider Without a J2CA Resource Adapter|http://download.oracle.com/docs/cd/B32110_01/web.1013/b28221/undejdev010.htm#CCHFAAAH]" .
You need to use an instance of JMS Connector (predefined or your own) for proper transaction enlistment of OC4J JMS.
The built-in JMS connector mentioned by you publishes connection factories at the following locations:
OracleASjms/MyXAQCF     
OracleASjms/MyQCF
OracleASjms/MyXATCF     
OracleASjms/MyTCF
OracleASjms/MyXACF     
OracleASjms/MyCF
For your case you need OracleASjms/MyXACF or OracleASjms/MyXACF . Do not bypass the JMS Connector by using the OC4J JMS connection factories such as jms/XAConnectionFactory directly when you intend to use transactions.
Hope this helps.
Gera