Results 1 to 2 of 2

Thread: Implication of NOT specifying timeout in tx:method

  1. #1

    Default Implication of NOT specifying timeout in tx:method

    I would like to know the implication of not specifying timeout in tx:method. For example, the code below does not have any timeout specified e..g, as timeout="5"

    Code:
    <tx:method
            	name="find*"
                read-only="true"
                propagation="REQUIRED"
                isolation="READ_COMMITTED"
           	/>
    I understand that the timeout on the datasource has a different implication.

    My question:
    If timeout is not specified on a transaction, will it default to some value? Or, will the timeout value be unbounded and will honor the summation value of all the transactions?

  2. #2
    Join Date
    Jun 2006
    Location
    The Netherlands
    Posts
    13,695

    Default

    Default consultant answer: it depends...

    It depends on your transactional resource, it depends on your driver implementation, it depends on your application server. So no easy answer here.

    Basically if there is no timeout specified it will not timeout, it will leave it to the other resources. However what exactly is going to happen, well depends on all of the above and probably some more.
    Marten Deinum
    Java Consultant / Pragmatist / Open Source Enthousiast / Author


    Pro Spring MVC: With Web Flow
    Conspect

    Have you read the reference guide.
    Use the [ code ] tags, young padawan

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •