[
https://issues.apache.org/jira/browse/QPID-3012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kennedy resolved QPID-3012.
----------------------------------
Resolution: Fixed
Accepted, but raises the following points:
1. Should we paramaterise this, and have an N = 50 version that runs in the
system tests, and an N=500 (or more) long running version?
2. Should we add a test somewhere for the case of N >> CPUs *concurrent*
connections, and validate our thread pooling strategy in a similar way?
3. Test is badly named...
> ConnectionCloseTest creates an extreme number of connections
> ------------------------------------------------------------
>
> Key: QPID-3012
> URL: https://issues.apache.org/jira/browse/QPID-3012
> Project: Qpid
> Issue Type: Test
> Components: Java Broker, Java Client
> Affects Versions: 0.8
> Reporter: Robbie Gemmell
> Assignee: Andrew Kennedy
> Priority: Minor
> Fix For: 0.9
>
>
> ConnectionCloseTest creates and closes 1000 connections to the broker during
> its run. It seems reasonable the same behaviour could be tested with far
> fewer connections, say 100, making the test take far less time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
