[jbossts-issues] [JBoss JIRA] (JBTM-1573) Transaction timeout incompatible with block forever
Tom Jenkinson (JIRA)
jira-events at lists.jboss.org
Mon Mar 25 11:56:42 EDT 2013
[ https://issues.jboss.org/browse/JBTM-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Jenkinson moved BLACKTIE-324 to JBTM-1573:
----------------------------------------------
Project: JBoss Transaction Manager (was: Blacktie)
Key: JBTM-1573 (was: BLACKTIE-324)
Component/s: BlackTie
BlackTie
(was: atmibroker-tx)
(was: All C++ )
Fix Version/s: 5.0.0.Final
(was: 5.0.0.Final)
> Transaction timeout incompatible with block forever
> ---------------------------------------------------
>
> Key: JBTM-1573
> URL: https://issues.jboss.org/browse/JBTM-1573
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie, BlackTie
> Reporter: Tom Jenkinson
> Assignee: Amos Feng
> Fix For: 5.0.0.Final
>
> Attachments: blocking call.log
>
>
> Currently we set a transaction timeout (e.g. in TestRollbackOnly.cxx we call tx_set_transaction_timeout)
> This ends up putting a timetolive on the message of the same duration.
> Now, if this message is not received within the period of time it will expire.
> However we also use a block forever waiting for the response.
> This can lead to a call never returning.
> i.e.
> server advertises queue
> client sends message with small timeout (e.g. 4) and then blocks forever waiting response
> server gets round to advertising queue 5 seconds later but never sees the clients initial request
> client is blocked forever
> I realise that we are meant to block forever when a client issues a tpcall under transactional conditions but something needs to be done as this can easily happen on slow machines?
> Perhaps we need to make use of the DLQ to wake up the blocked client with an error message??
> Perhaps the client doesn't block forever and just calls txrollback if nothing is heard back??
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbossts-issues
mailing list