You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rafael H. Schloming (JIRA)" <qp...@incubator.apache.org> on 2008/05/16 14:17:56 UTC
[jira] Commented: (QPID-962) ConnectionTest takes too long to run
[ https://issues.apache.org/jira/browse/QPID-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597438#action_12597438 ]
Rafael H. Schloming commented on QPID-962:
------------------------------------------
I believe there is a deeper issue here with connection negotiation. Regardless of the number of retries or the timeouts involved, these tests should pass almost instantaneously. I know one issue is that AMQConnectionDelegate_0_8.makeBrokerConnection missed some updates from the merge. The M2.x code in makeBrokerConnection tries to attain either the CONNECTION_OPEN or CONNECTION_CLOSED states, whereas the trunk code tries to only attain CONNECTION_OPEN. The former behavior seems more correct to me. I have the M2x version merged in my local checkout, however this causes a few issues that I have yet to look into.
> ConnectionTest takes too long to run
> ------------------------------------
>
> Key: QPID-962
> URL: https://issues.apache.org/jira/browse/QPID-962
> Project: Qpid
> Issue Type: Bug
> Components: Java Tests
> Affects Versions: M3
> Reporter: Aidan Skinner
> Fix For: M3
>
> Attachments: ConnectionText.patch.txt
>
>
> ConnectionTest takes 90-odd seconds to run, which is both frustrating and possibly indicative of a problem. Some investigation required.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.