You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2007/02/19 15:48:05 UTC

[jira] Created: (QPID-380) Propogated timeout on connection close does not reduce between session close.

Propogated timeout on connection close does not reduce between session close.
-----------------------------------------------------------------------------

                 Key: QPID-380
                 URL: https://issues.apache.org/jira/browse/QPID-380
             Project: Qpid
          Issue Type: Bug
          Components: Java Client
            Reporter: Martin Ritchie


Currently the same timeout is used for closing each session. This can result in the call to close(timeout) taking much longer than the specified timeout. The timeout vaule used needs to be reduced for each of the subsequent method syncwrite calls.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (QPID-380) Propogated timeout on connection close does not reduce between session close.

Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marnie McCormack updated QPID-380:
----------------------------------

    Fix Version/s:     (was: M4)

Descoping items not being worked on for M4 into Unknown Fix Version for now

> Propogated timeout on connection close does not reduce between session close.
> -----------------------------------------------------------------------------
>
>                 Key: QPID-380
>                 URL: https://issues.apache.org/jira/browse/QPID-380
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>            Reporter: Martin Ritchie
>            Assignee: Martin Ritchie
>
> Currently the same timeout is used for closing each session. This can result in the call to close(timeout) taking much longer than the specified timeout. The timeout vaule used needs to be reduced for each of the subsequent method syncwrite calls.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (QPID-380) Propogated timeout on connection close does not reduce between session close.

Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ritchie reassigned QPID-380:
-----------------------------------

    Assignee: Martin Ritchie

> Propogated timeout on connection close does not reduce between session close.
> -----------------------------------------------------------------------------
>
>                 Key: QPID-380
>                 URL: https://issues.apache.org/jira/browse/QPID-380
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>            Reporter: Martin Ritchie
>         Assigned To: Martin Ritchie
>
> Currently the same timeout is used for closing each session. This can result in the call to close(timeout) taking much longer than the specified timeout. The timeout vaule used needs to be reduced for each of the subsequent method syncwrite calls.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (QPID-380) Propogated timeout on connection close does not reduce between session close.

Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ritchie updated QPID-380:
--------------------------------

    Fix Version/s: M3

> Propogated timeout on connection close does not reduce between session close.
> -----------------------------------------------------------------------------
>
>                 Key: QPID-380
>                 URL: https://issues.apache.org/jira/browse/QPID-380
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>            Reporter: Martin Ritchie
>             Fix For: M3
>
>
> Currently the same timeout is used for closing each session. This can result in the call to close(timeout) taking much longer than the specified timeout. The timeout vaule used needs to be reduced for each of the subsequent method syncwrite calls.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (QPID-380) Propogated timeout on connection close does not reduce between session close.

Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ritchie reassigned QPID-380:
-----------------------------------

    Assignee:     (was: Martin Ritchie)

> Propogated timeout on connection close does not reduce between session close.
> -----------------------------------------------------------------------------
>
>                 Key: QPID-380
>                 URL: https://issues.apache.org/jira/browse/QPID-380
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>            Reporter: Martin Ritchie
>
> Currently the same timeout is used for closing each session. This can result in the call to close(timeout) taking much longer than the specified timeout. The timeout vaule used needs to be reduced for each of the subsequent method syncwrite calls.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.