[
https://issues.apache.org/jira/browse/QPID-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross closed QPID-4025.
-----------------------------
Resolution: Cannot Reproduce
> connections leak
> ----------------
>
> Key: QPID-4025
> URL: https://issues.apache.org/jira/browse/QPID-4025
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Affects Versions: 0.16
> Environment: win7
> Reporter: yinshuwei
> Priority: Major
> Labels: patch
>
> I used this command:
> spout -c 110 -b IP:port --content anything "q; {create:always,
> node:{type:queue, durable:true,
> x-declare:{arguments:{qpid.max_count:100,qpid.max_size:1024,qpid.policy_type:reject}}}}"
>
> But I got the exception:"session-busy: Session detached by peer" and the
> log :"2012-05-29 15:55:54 warning Exception received from broker:
> resource-limit-excee
> ded: resource-limit-exceeded: resource-limit-exceeded: Policy exceeded on q,
> pol
> icy: size: max=1024, current=700; count: max=100, current=100; type=reject
> (D:\c
> lib\qpidc-0.16\src\qpid\broker\QueuePolicy.cpp:87) [caused by 103 "
> I think when resource limit exceeded the connection should not be
> closed.Because more seriously,if I reconnect to the server in this case over
> and over,the server's connection limit will exceed.It seems that the client's
> connection is closed,but the server side still keep the connections.But when
> the client exit,the server side connections will be released.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
