Hello Ramesh,
Yes, you are correct, I did not set the UserFirstXAForRedelivery option. For
now I am using the Provider specific alternative. It also serves our needs
well. If time permits I will give the redelivery a try. I will send the link
to the instructions for setting up genericjmsra with OracleAQ soon.
Is it OK if I just use the format from one of your blogs and just update the
content for OracleAQ?
Thanks!
Best Regards,
Shailesh
Ramesh Parthasarathy wrote:
>
> Hi Shailesh,
> Redelivery is always tricky ! Since there is more than one XA (one
> for every delivery) involved, there is always the challenge of how we
> manage the XA resource state transitions at the broker side.Could you
> set gra log level to FINEST and send us the logs. Also i assume you
> have not set "UseFirstXAForRedelivery"
>
> Thanks
> -Ramesh
>
> Shailesh Kini wrote:
>> Hi Ramesh,
>>
>> I will document the steps after I am done with the some testing. So far I
>> am
>> able to dequeue the message and process it in a XA transaction.
>> Everything
>> works if i set the redelivery count to 0.
>>
>> I have some issues configuring DMD. I have setup the reconnect interval,
>> reconnect interval, enabled DMD to true and set the DMD CF and
>> Destination
>> in the activation spec. The connection factories and destinations are
>> successfully created.
>> After I set the redelivery count to 5 the GRA code loops and tries to
>> process the message 5 times if the MDB fails. After the redelivery count
>> is
>> maxed out, GRA calls the SyncDeliveryHelper's sendMessageToDMD() to push
>> the
>> message to DMD.
>>
>> Here's my question regarding DMD.
>> 1. The redeliverRequired return true and GRA calls
>> localXar.prepare(null);
>> passes a null to prepare. This causes the OracleXAResource to throw
>> OracleXAException. Is there any particular reason why a null is passed to
>> this prepare call?
>>
>> Hope to hear from you soon.
>> Thanks and Best Regards,
>>
>> Shailesh
>>
>>
>> Thanks Shailesh,
>> Could you please make the steps available (through a blog/article),
>> we can publish it through the generic jms ra site.
>>
>> -Ramesh
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_genericjmsra.dev.java.net
> For additional commands, e-mail: users-help_at_genericjmsra.dev.java.net
>
>
>
--
View this message in context: http://www.nabble.com/GenericJMSRA-problems-configuration-for-AQ-conecction.-tp13120991p14373905.html
Sent from the Users of Generic Resource Adapter for JMS mailing list archive at Nabble.com.