Hi Subrahmanian,
> Hi all
>
> I currently have the following use-cases for testing the inbound
> communication with Transactions:
>
> *USE CASE 1:*
> Tibco JMS Server --> Generic JMS RA --> MDB End points in AppServer
>
> I am testing whether multiple messages can be sent as part of the Same
> transaction (same XID). I am currently exploring the Transaction
> support and the configurations in Generic JMS RA. If any one has tried
> a similar use-case it would be great if you could share any information.
Let me understand what you mean...
The feature you are exploring is about taking one MDB instance from
appserver and passing multiple messages to it under one transaction.
Is that correct? I think such a capability is not supported at present.
If appserver supports MDB instance pooling, then, multiple messages will
be delivered concurrently to different MDB
instances under different transactions. That is supported. We thought,
this will cover most of customer needs.
>
> *USE CASE 2:*
> The Tibco JMS Server sends a message to the MDB Endpoint in a
> Transactional context
> Tibco JMS Server ==> Generic JMS RA ==> MDB Endpoints --> Database
> operation that fails. (roll back)
> So the message ideally now should be redelivered.
> **
> It would be helpful if anyone has info on import transactions using
> Generic JMS RA and whether such use cases are possible?
Message redelivery is supported.
- Binod.
>
> cheers
>
> ------------------------------------------------------------------------
> *Subramanian Easwaran*
> Borland Software Corporation