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/03/22 13:57:32 UTC
[jira] Created: (QPID-429) Client contains lots of distinct
timeouts these need to be consolidated and exposed to client applications
Client contains lots of distinct timeouts these need to be consolidated and exposed to client applications
----------------------------------------------------------------------------------------------------------
Key: QPID-429
URL: https://issues.apache.org/jira/browse/QPID-429
Project: Qpid
Issue Type: Bug
Components: Java Client
Reporter: Martin Ritchie
Timeouts such as AMQProtocolSession.LAST_WRITE_FUTURE_JOIN_TIMEOUT (default: 2 minutes) cannot be set these values should be configurable and exposed to the client.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-429) Client contains lots of distinct
timeouts these need to be consolidated and exposed to client applications
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483131 ]
Martin Ritchie commented on QPID-429:
-------------------------------------
Remember to update wiki when resolved :
http://cwiki.apache.org/confluence/display/qpid/Qpid+Java+FAQ
> Client contains lots of distinct timeouts these need to be consolidated and exposed to client applications
> ----------------------------------------------------------------------------------------------------------
>
> Key: QPID-429
> URL: https://issues.apache.org/jira/browse/QPID-429
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Reporter: Martin Ritchie
>
> Timeouts such as AMQProtocolSession.LAST_WRITE_FUTURE_JOIN_TIMEOUT (default: 2 minutes) cannot be set these values should be configurable and exposed to the client.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-429) Client contains lots of distinct
timeouts these need to be consolidated and exposed to client applications
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-429:
--------------------------------
Fix Version/s: M3
> Client contains lots of distinct timeouts these need to be consolidated and exposed to client applications
> ----------------------------------------------------------------------------------------------------------
>
> Key: QPID-429
> URL: https://issues.apache.org/jira/browse/QPID-429
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Reporter: Martin Ritchie
> Fix For: M3
>
>
> Timeouts such as AMQProtocolSession.LAST_WRITE_FUTURE_JOIN_TIMEOUT (default: 2 minutes) cannot be set these values should be configurable and exposed to the client.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-429) Client contains lots of distinct
timeouts these need to be consolidated and exposed to client applications
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486624 ]
Martin Ritchie commented on QPID-429:
-------------------------------------
AMQConnection.DEFAULT_TIMEOUT = 30s
AMQProtocolHandler.DEFAULT_SYNC_TIMEOUT = 30s
> Client contains lots of distinct timeouts these need to be consolidated and exposed to client applications
> ----------------------------------------------------------------------------------------------------------
>
> Key: QPID-429
> URL: https://issues.apache.org/jira/browse/QPID-429
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Reporter: Martin Ritchie
>
> Timeouts such as AMQProtocolSession.LAST_WRITE_FUTURE_JOIN_TIMEOUT (default: 2 minutes) cannot be set these values should be configurable and exposed to the client.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-429) Client contains lots of distinct
timeouts these need to be consolidated and exposed to client applications
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marnie McCormack updated QPID-429:
----------------------------------
Fix Version/s: (was: M4)
Descoping items not being worked on for M4 into Unknown Fix Version for now
> Client contains lots of distinct timeouts these need to be consolidated and exposed to client applications
> ----------------------------------------------------------------------------------------------------------
>
> Key: QPID-429
> URL: https://issues.apache.org/jira/browse/QPID-429
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
>
> Timeouts such as AMQProtocolSession.LAST_WRITE_FUTURE_JOIN_TIMEOUT (default: 2 minutes) cannot be set these values should be configurable and exposed to the client.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.