Re: redelivery limit not working for transaction timeout?

>>>  It is confusing since the descriptor for the MDB has the
transaction-timeout set, but i assume this is ignored for 'not-supported'

Correct.   Since the message isn't participating in a transaction, the
transaction timeout doesn't apply.

>>> I guess you would need to look at the code, but is there anyway a
message go back on the queue, and not get the redelivery incremented?

Not that I can think of.

>>> (I just had an evil thought...maybe the code could be physically
sending the message onto the queue again when there is a timeout on the session
bean.....hence would not get the redelivery incremented.....)

You could test this by instrumenting the app code to print
"msg.getJMSMessageId()", which is unique for each message.  You can
also test this by checking out the JMS statistics - the total message count will
increase with each new message, but won't increase for a redelivery.

In addition, you could enable JMS debugging.  I think you can do this via the on
the console -> wl server -> debug pages, or by adding one of more flags on
the JVM command line:

-Dweblogic.Debug.DebugJMSBackEnd=true
-Dweblogic.Debug.DebugJMSXA=true
-Dweblogic.Debug.DebugJMSFrontEnd=true
-Dweblogic.Debug.DebugJMSCommon=true
-Dweblogic.Debug.DebugJMSConfig=true
-Dweblogic.Debug.DebugJMSStore=true
-Dweblogic.Debug.DebugJMSBoot=true

I think its likely that only the first two or three debug flags are helpful  in
your case.

).