[jira] [Commented] (PROTON-905) Long-lived connections leak sessions and links

2015-10-28 Thread Ken Giusti (JIRA)

[ 
https://issues.apache.org/jira/browse/PROTON-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978548#comment-14978548
 ] 

Ken Giusti commented on PROTON-905:
---

I think that we should bump this off until post 0.11 and bump the priority down 
to major. 

This bug doesn't affect any application that uses proton's event-based 
processing model.  This model is the preferred usage (as opposed to the 'walk 
all {links,deliveries,sessions} looking for work to do).

AFAIK - all the proton client code now uses the event-based approach.

I've tested this against qpidd-0.34 (event-based implementation) and there is 
no memory buildup.

Lastly, this is not a regression as it's been present at least as far back as 
the 0.9 series.

> Long-lived connections leak sessions and links
> --
>
> Key: PROTON-905
> URL: https://issues.apache.org/jira/browse/PROTON-905
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: 0.9.1, 0.10
>Reporter: Ken Giusti
>Assignee: Rafael H. Schloming
>Priority: Critical
> Fix For: 0.11
>
> Attachments: test-send.py
>
>
> I found this issue while debugging a crash dump of qpidd.
> Long lived connections do not free its sessions/link.
> This only applies when NOT using the event model.  The version of qpidd I 
> tested against (0.30) still uses the iterative model.  Point to consider, I 
> don't know why this is the case.
> Details:  I have a test script that opens a single connection, then 
> continually creates sessions/links over that connection, sending one message 
> before closing and freeing the sessions/links.  See attached.
> Over time the qpidd run time consumes all memory on the system and is killed 
> by OOM.  To be clear, I'm using drain to remove all sent messages - there is 
> no message build up.
> On debugging this, I'm finding thousands of session objects on the 
> connections free sessions weakref list.  Every one of those sessions has a 
> refcount of one.
> Once the connection is finalized, all session objects are freed.  But until 
> then, freed sessions continue to accumulate indefinitely.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (PROTON-905) Long-lived connections leak sessions and links

2015-07-30 Thread Robbie Gemmell (JIRA)

[ 
https://issues.apache.org/jira/browse/PROTON-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14647951#comment-14647951
 ] 

Robbie Gemmell commented on PROTON-905:
---

Ok, I've bumped the versions accordingly.

 Long-lived connections leak sessions and links
 --

 Key: PROTON-905
 URL: https://issues.apache.org/jira/browse/PROTON-905
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-c
Affects Versions: 0.9.1, 0.10
Reporter: Ken Giusti
Assignee: Rafael H. Schloming
Priority: Critical
 Fix For: 0.11

 Attachments: test-send.py


 I found this issue while debugging a crash dump of qpidd.
 Long lived connections do not free its sessions/link.
 This only applies when NOT using the event model.  The version of qpidd I 
 tested against (0.30) still uses the iterative model.  Point to consider, I 
 don't know why this is the case.
 Details:  I have a test script that opens a single connection, then 
 continually creates sessions/links over that connection, sending one message 
 before closing and freeing the sessions/links.  See attached.
 Over time the qpidd run time consumes all memory on the system and is killed 
 by OOM.  To be clear, I'm using drain to remove all sent messages - there is 
 no message build up.
 On debugging this, I'm finding thousands of session objects on the 
 connections free sessions weakref list.  Every one of those sessions has a 
 refcount of one.
 Once the connection is finalized, all session objects are freed.  But until 
 then, freed sessions continue to accumulate indefinitely.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (PROTON-905) Long-lived connections leak sessions and links

2015-07-28 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/PROTON-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14644749#comment-14644749
 ] 

ASF subversion and git services commented on PROTON-905:


Commit 4c84dd7c3c708fd823116876cd65885a628f92ff in qpid-proton's branch 
refs/heads/master from [~kgiusti]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=4c84dd7 ]

PROTON-905: Revert PROTON-905: fix to prevent crash with latest qpidd

This reverts commit d9ce3cfd0916ae3719cb39a83a6174c5f88b10bb.

The latest qpidd is crashing due to the PROTON-905 fix whilst running
the HA tests.


 Long-lived connections leak sessions and links
 --

 Key: PROTON-905
 URL: https://issues.apache.org/jira/browse/PROTON-905
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-c
Affects Versions: 0.9.1
Reporter: Ken Giusti
Assignee: Rafael H. Schloming
Priority: Critical
 Fix For: 0.10

 Attachments: test-send.py


 I found this issue while debugging a crash dump of qpidd.
 Long lived connections do not free its sessions/link.
 This only applies when NOT using the event model.  The version of qpidd I 
 tested against (0.30) still uses the iterative model.  Point to consider, I 
 don't know why this is the case.
 Details:  I have a test script that opens a single connection, then 
 continually creates sessions/links over that connection, sending one message 
 before closing and freeing the sessions/links.  See attached.
 Over time the qpidd run time consumes all memory on the system and is killed 
 by OOM.  To be clear, I'm using drain to remove all sent messages - there is 
 no message build up.
 On debugging this, I'm finding thousands of session objects on the 
 connections free sessions weakref list.  Every one of those sessions has a 
 refcount of one.
 Once the connection is finalized, all session objects are freed.  But until 
 then, freed sessions continue to accumulate indefinitely.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (PROTON-905) Long-lived connections leak sessions and links

2015-07-28 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/PROTON-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14644751#comment-14644751
 ] 

ASF subversion and git services commented on PROTON-905:


Commit 0fa93bcbc0b5cb2988254eadf1bbd8a7f62f87eb in qpid-proton's branch 
refs/heads/master from [~kgiusti]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=0fa93bc ]

PROTON-905: Revert PROTON-905: fix leak of session/links when not using events

This reverts commit 653f4e5fe2b9307dccced0a5a85028d1ca67c66a.

This patch causes crashes in qpidd when running its HA tests.


 Long-lived connections leak sessions and links
 --

 Key: PROTON-905
 URL: https://issues.apache.org/jira/browse/PROTON-905
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-c
Affects Versions: 0.9.1
Reporter: Ken Giusti
Assignee: Rafael H. Schloming
Priority: Critical
 Fix For: 0.10

 Attachments: test-send.py


 I found this issue while debugging a crash dump of qpidd.
 Long lived connections do not free its sessions/link.
 This only applies when NOT using the event model.  The version of qpidd I 
 tested against (0.30) still uses the iterative model.  Point to consider, I 
 don't know why this is the case.
 Details:  I have a test script that opens a single connection, then 
 continually creates sessions/links over that connection, sending one message 
 before closing and freeing the sessions/links.  See attached.
 Over time the qpidd run time consumes all memory on the system and is killed 
 by OOM.  To be clear, I'm using drain to remove all sent messages - there is 
 no message build up.
 On debugging this, I'm finding thousands of session objects on the 
 connections free sessions weakref list.  Every one of those sessions has a 
 refcount of one.
 Once the connection is finalized, all session objects are freed.  But until 
 then, freed sessions continue to accumulate indefinitely.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (PROTON-905) Long-lived connections leak sessions and links

2015-07-28 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/PROTON-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14644750#comment-14644750
 ] 

ASF subversion and git services commented on PROTON-905:


Commit 0fa93bcbc0b5cb2988254eadf1bbd8a7f62f87eb in qpid-proton's branch 
refs/heads/master from [~kgiusti]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=0fa93bc ]

PROTON-905: Revert PROTON-905: fix leak of session/links when not using events

This reverts commit 653f4e5fe2b9307dccced0a5a85028d1ca67c66a.

This patch causes crashes in qpidd when running its HA tests.


 Long-lived connections leak sessions and links
 --

 Key: PROTON-905
 URL: https://issues.apache.org/jira/browse/PROTON-905
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-c
Affects Versions: 0.9.1
Reporter: Ken Giusti
Assignee: Rafael H. Schloming
Priority: Critical
 Fix For: 0.10

 Attachments: test-send.py


 I found this issue while debugging a crash dump of qpidd.
 Long lived connections do not free its sessions/link.
 This only applies when NOT using the event model.  The version of qpidd I 
 tested against (0.30) still uses the iterative model.  Point to consider, I 
 don't know why this is the case.
 Details:  I have a test script that opens a single connection, then 
 continually creates sessions/links over that connection, sending one message 
 before closing and freeing the sessions/links.  See attached.
 Over time the qpidd run time consumes all memory on the system and is killed 
 by OOM.  To be clear, I'm using drain to remove all sent messages - there is 
 no message build up.
 On debugging this, I'm finding thousands of session objects on the 
 connections free sessions weakref list.  Every one of those sessions has a 
 refcount of one.
 Once the connection is finalized, all session objects are freed.  But until 
 then, freed sessions continue to accumulate indefinitely.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (PROTON-905) Long-lived connections leak sessions and links

2015-07-28 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/PROTON-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14644748#comment-14644748
 ] 

ASF subversion and git services commented on PROTON-905:


Commit 4c84dd7c3c708fd823116876cd65885a628f92ff in qpid-proton's branch 
refs/heads/master from [~kgiusti]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=4c84dd7 ]

PROTON-905: Revert PROTON-905: fix to prevent crash with latest qpidd

This reverts commit d9ce3cfd0916ae3719cb39a83a6174c5f88b10bb.

The latest qpidd is crashing due to the PROTON-905 fix whilst running
the HA tests.


 Long-lived connections leak sessions and links
 --

 Key: PROTON-905
 URL: https://issues.apache.org/jira/browse/PROTON-905
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-c
Affects Versions: 0.9.1
Reporter: Ken Giusti
Assignee: Rafael H. Schloming
Priority: Critical
 Fix For: 0.10

 Attachments: test-send.py


 I found this issue while debugging a crash dump of qpidd.
 Long lived connections do not free its sessions/link.
 This only applies when NOT using the event model.  The version of qpidd I 
 tested against (0.30) still uses the iterative model.  Point to consider, I 
 don't know why this is the case.
 Details:  I have a test script that opens a single connection, then 
 continually creates sessions/links over that connection, sending one message 
 before closing and freeing the sessions/links.  See attached.
 Over time the qpidd run time consumes all memory on the system and is killed 
 by OOM.  To be clear, I'm using drain to remove all sent messages - there is 
 no message build up.
 On debugging this, I'm finding thousands of session objects on the 
 connections free sessions weakref list.  Every one of those sessions has a 
 refcount of one.
 Once the connection is finalized, all session objects are freed.  But until 
 then, freed sessions continue to accumulate indefinitely.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (PROTON-905) Long-lived connections leak sessions and links

2015-06-19 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/PROTON-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14593407#comment-14593407
 ] 

ASF subversion and git services commented on PROTON-905:


Commit 653f4e5fe2b9307dccced0a5a85028d1ca67c66a in qpid-proton's branch 
refs/heads/master from [~kgiusti]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=653f4e5 ]

PROTON-905: fix leak of session/links when not using events


 Long-lived connections leak sessions and links
 --

 Key: PROTON-905
 URL: https://issues.apache.org/jira/browse/PROTON-905
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-c
Affects Versions: 0.9.1
Reporter: Ken Giusti
Assignee: Ken Giusti
Priority: Blocker
 Fix For: 0.10

 Attachments: test-send.py


 I found this issue while debugging a crash dump of qpidd.
 Long lived connections do not free its sessions/link.
 This only applies when NOT using the event model.  The version of qpidd I 
 tested against (0.30) still uses the iterative model.  Point to consider, I 
 don't know why this is the case.
 Details:  I have a test script that opens a single connection, then 
 continually creates sessions/links over that connection, sending one message 
 before closing and freeing the sessions/links.  See attached.
 Over time the qpidd run time consumes all memory on the system and is killed 
 by OOM.  To be clear, I'm using drain to remove all sent messages - there is 
 no message build up.
 On debugging this, I'm finding thousands of session objects on the 
 connections free sessions weakref list.  Every one of those sessions has a 
 refcount of one.
 Once the connection is finalized, all session objects are freed.  But until 
 then, freed sessions continue to accumulate indefinitely.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (PROTON-905) Long-lived connections leak sessions and links

2015-06-11 Thread Ken Giusti (JIRA)

[ 
https://issues.apache.org/jira/browse/PROTON-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14581918#comment-14581918
 ] 

Ken Giusti commented on PROTON-905:
---

reviewboard link:

https://reviews.apache.org/r/35355/

 Long-lived connections leak sessions and links
 --

 Key: PROTON-905
 URL: https://issues.apache.org/jira/browse/PROTON-905
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-c
Affects Versions: 0.9.1
Reporter: Ken Giusti
Assignee: Ken Giusti
Priority: Blocker
 Fix For: 0.10

 Attachments: test-send.py


 I found this issue while debugging a crash dump of qpidd.
 Long lived connections do not free its sessions/link.
 This only applies when NOT using the event model.  The version of qpidd I 
 tested against (0.30) still uses the iterative model.  Point to consider, I 
 don't know why this is the case.
 Details:  I have a test script that opens a single connection, then 
 continually creates sessions/links over that connection, sending one message 
 before closing and freeing the sessions/links.  See attached.
 Over time the qpidd run time consumes all memory on the system and is killed 
 by OOM.  To be clear, I'm using drain to remove all sent messages - there is 
 no message build up.
 On debugging this, I'm finding thousands of session objects on the 
 connections free sessions weakref list.  Every one of those sessions has a 
 refcount of one.
 Once the connection is finalized, all session objects are freed.  But until 
 then, freed sessions continue to accumulate indefinitely.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)