[jira] [Updated] (PROTON-825) BlockingReceiver.receive() uses 100% CPU.
[ https://issues.apache.org/jira/browse/PROTON-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-825: --- Assignee: Ted Ross (was: Alan Conway) BlockingReceiver.receive() uses 100% CPU. - Key: PROTON-825 URL: https://issues.apache.org/jira/browse/PROTON-825 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: 0.9 Environment: F20 Built from master 2/19. Reporter: Jeff Ortel Assignee: Ted Ross Calling BlockingReceiver.receive(timeout=10) blocks the caller for 10 seconds but uses 100% CPU. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (PROTON-825) BlockingReceiver.receive() uses 100% CPU.
[ https://issues.apache.org/jira/browse/PROTON-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway reassigned PROTON-825: -- Assignee: Alan Conway BlockingReceiver.receive() uses 100% CPU. - Key: PROTON-825 URL: https://issues.apache.org/jira/browse/PROTON-825 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: 0.9 Environment: F20 Built from master 2/19. Reporter: Jeff Ortel Assignee: Alan Conway Calling BlockingReceiver.receive(timeout=10) blocks the caller for 10 seconds but uses 100% CPU. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-825) BlockingReceiver.receive() uses 100% CPU.
[ https://issues.apache.org/jira/browse/PROTON-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-825: Assignee: Alan Conway (was: Ted Ross) BlockingReceiver.receive() uses 100% CPU. - Key: PROTON-825 URL: https://issues.apache.org/jira/browse/PROTON-825 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: 0.9 Environment: F20 Built from master 2/19. Reporter: Jeff Ortel Assignee: Alan Conway Calling BlockingReceiver.receive(timeout=10) blocks the caller for 10 seconds but uses 100% CPU. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-824) Windows fails testIdleTimeout with assert p.conn.remote_condition
[
https://issues.apache.org/jira/browse/PROTON-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1495#comment-1495
]
Chuck Rolke commented on PROTON-824:
Here's what's happening. All of the Program's reactor callbacks are firing and
each is passing its assertions.
But when the main program continues from Reactor(p).run() then p.conn does not
have a remote_condition any more.
Any thoughts?
{noformat}
1: start
1: INFO: on_reactor_init
1: INFO: on_connection_remote_open
1: INFO: on_timer_task
1: INFO: on_connection_remote_close
1: INFO:self.conn : proton.Connection 0x2704610 ~ 0x27be2f0
1: INFO:self.conn.remote_condition :
Condition('amqp:resource-limit-exceeded', 'local-idle-timeout expired')
1: INFO: p.conn : proton.Connection 0x2704610 ~ 0x27be2f0
1: INFO: p.conn.remote_condition : None
1: proton_tests.engine.AAAServerTest.testIdleTimeout ...
proton_tests.engine.AAAServerTest.testIdleTimeout ...
fail
1: Error during test: Traceback (most recent call last):
1: File D:/Users/crolke/git/rh-qpid-proton/tests/python/proton-test, line
355, in run
1: phase()
1: File
D:\Users\crolke\git\rh-qpid-proton\tests\python\proton_tests\engine.py, line
1894, in testIdleTimeout
1: assert p.conn.remote_condition
1: AssertionError
{noformat}
Windows fails testIdleTimeout with assert p.conn.remote_condition
-
Key: PROTON-824
URL: https://issues.apache.org/jira/browse/PROTON-824
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Affects Versions: 0.9
Environment: Windows Server 2008 or 2012
Visual studio 2010, x86
Reporter: Chuck Rolke
{noformat}
1: proton_tests.engine.ServerTest.testIdleTimeout .
fail
1: Error during test: Traceback (most recent call last):
1: File D:/Users/crolke/git/rh-qpid-proton/tests/python/proton-test,
line 355, in run
1: phase()
1: File
D:\Users\crolke\git\rh-qpid-proton\tests\python\proton_tests\engine.py,
line 1919 (or so), in testIdleTimeout
1: assert p.conn.remote_condition
1: AssertionError
{noformat}
Playing with Program explicit timeout (trying 10 instead of 3) gets the test
to pass sometimes. It passes sometimes with 3 as well but normally fails.
In debugging this it looks like there as no synchronization between what a
test will show through print statements and what the proton library shows
through PN_TRACE_FRM statements. Are there any hints to lining these up?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (PROTON-825) BlockingReceiver.receive() uses 100% CPU.
[ https://issues.apache.org/jira/browse/PROTON-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-825. Resolution: Fixed Fix Version/s: 0.9 BlockingReceiver.receive() uses 100% CPU. - Key: PROTON-825 URL: https://issues.apache.org/jira/browse/PROTON-825 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: 0.9 Environment: F20 Built from master 2/19. Reporter: Jeff Ortel Assignee: Alan Conway Fix For: 0.9 Calling BlockingReceiver.receive(timeout=10) blocks the caller for 10 seconds but uses 100% CPU. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-825) BlockingReceiver.receive() uses 100% CPU.
[ https://issues.apache.org/jira/browse/PROTON-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14333485#comment-14333485 ] ASF subversion and git services commented on PROTON-825: Commit 4244875ddd74f41d67f4fca11166fc6d43bc4d93 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=4244875 ] PROTON-825: BlockingReceiver.receive() uses 100% CPU. Fixed in BlockingConnection, by setting BlockingConnection's timeout on it's Container. NOTE: Prior to this fix you can work around the problem as follows: - self.connection = BlockingConnection(url, timeout=timeout) + container = proton.reactor.Container() + container.timeout = timeout + self.connection = BlockingConnection(url, timeout=timeout, container=container) Timeout can be None to wait without limit until something is available. BlockingReceiver.receive() uses 100% CPU. - Key: PROTON-825 URL: https://issues.apache.org/jira/browse/PROTON-825 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: 0.9 Environment: F20 Built from master 2/19. Reporter: Jeff Ortel Assignee: Alan Conway Calling BlockingReceiver.receive(timeout=10) blocks the caller for 10 seconds but uses 100% CPU. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [jira] [Commented] (PROTON-824) Windows fails testIdleTimeout with assert p.conn.remote_condition
Looking at the driver and frame traces, it appears that the Windows
IOCP code is dropping an error condition on close or is just taking
longer to report the closed condition than its Linux counterpart.
I am taking a closer look and will report back.
Cliff
On Mon, Feb 23, 2015 at 7:29 AM, Chuck Rolke (JIRA) j...@apache.org wrote:
[
https://issues.apache.org/jira/browse/PROTON-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1495#comment-1495
]
Chuck Rolke commented on PROTON-824:
Here's what's happening. All of the Program's reactor callbacks are firing
and each is passing its assertions.
But when the main program continues from Reactor(p).run() then p.conn does
not have a remote_condition any more.
Any thoughts?
{noformat}
1: start
1: INFO: on_reactor_init
1: INFO: on_connection_remote_open
1: INFO: on_timer_task
1: INFO: on_connection_remote_close
1: INFO:self.conn : proton.Connection 0x2704610 ~ 0x27be2f0
1: INFO:self.conn.remote_condition :
Condition('amqp:resource-limit-exceeded', 'local-idle-timeout expired')
1: INFO: p.conn : proton.Connection 0x2704610 ~ 0x27be2f0
1: INFO: p.conn.remote_condition : None
1: proton_tests.engine.AAAServerTest.testIdleTimeout ...
proton_tests.engine.AAAServerTest.testIdleTimeout ...
fail
1: Error during test: Traceback (most recent call last):
1: File D:/Users/crolke/git/rh-qpid-proton/tests/python/proton-test,
line 355, in run
1: phase()
1: File
D:\Users\crolke\git\rh-qpid-proton\tests\python\proton_tests\engine.py,
line 1894, in testIdleTimeout
1: assert p.conn.remote_condition
1: AssertionError
{noformat}
Windows fails testIdleTimeout with assert p.conn.remote_condition
-
Key: PROTON-824
URL: https://issues.apache.org/jira/browse/PROTON-824
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Affects Versions: 0.9
Environment: Windows Server 2008 or 2012
Visual studio 2010, x86
Reporter: Chuck Rolke
{noformat}
1: proton_tests.engine.ServerTest.testIdleTimeout .
fail
1: Error during test: Traceback (most recent call last):
1: File D:/Users/crolke/git/rh-qpid-proton/tests/python/proton-test,
line 355, in run
1: phase()
1: File
D:\Users\crolke\git\rh-qpid-proton\tests\python\proton_tests\engine.py,
line 1919 (or so), in testIdleTimeout
1: assert p.conn.remote_condition
1: AssertionError
{noformat}
Playing with Program explicit timeout (trying 10 instead of 3) gets the test
to pass sometimes. It passes sometimes with 3 as well but normally fails.
In debugging this it looks like there as no synchronization between what a
test will show through print statements and what the proton library shows
through PN_TRACE_FRM statements. Are there any hints to lining these up?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (PROTON-825) BlockingReceiver.receive() uses 100% CPU.
[ https://issues.apache.org/jira/browse/PROTON-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14333545#comment-14333545 ] ASF subversion and git services commented on PROTON-825: Commit 20d574bc95c2d69c02ab58435e52fa52559fcb5b in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=20d574b ] PROTON-825: BlockingReceiver.receive() uses 100% CPU. Missing in previous fix: convert timeout=None to max timeout for reactor. BlockingReceiver.receive() uses 100% CPU. - Key: PROTON-825 URL: https://issues.apache.org/jira/browse/PROTON-825 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: 0.9 Environment: F20 Built from master 2/19. Reporter: Jeff Ortel Assignee: Alan Conway Fix For: 0.9 Calling BlockingReceiver.receive(timeout=10) blocks the caller for 10 seconds but uses 100% CPU. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Errors relating to PN_MILLIS_MAX - need to clean and rebuild.
My latest made changes that are not picked up automatically by cmake, so if you see an error about a missing constant PN_MILLIS_MAX please clean and rebuild to force re-generation of swig code. I'll take a look at the cmake swig rules and see if I can fix the missing dependency so this happens automatically.
[jira] [Commented] (PROTON-825) BlockingReceiver.receive() uses 100% CPU.
[ https://issues.apache.org/jira/browse/PROTON-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14333981#comment-14333981 ] ASF subversion and git services commented on PROTON-825: Commit 92d049935fe0c9eb2ccc8430414c05ec12eefe94 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=92d0499 ] PROTON-825: BlockingReceiver.receive() does not respect it's timeout. BlockingReceiver.receive() uses 100% CPU. - Key: PROTON-825 URL: https://issues.apache.org/jira/browse/PROTON-825 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: 0.9 Environment: F20 Built from master 2/19. Reporter: Jeff Ortel Assignee: Alan Conway Fix For: 0.9 Calling BlockingReceiver.receive(timeout=10) blocks the caller for 10 seconds but uses 100% CPU. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-825) BlockingReceiver.receive() uses 100% CPU.
[ https://issues.apache.org/jira/browse/PROTON-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14334012#comment-14334012 ] ASF subversion and git services commented on PROTON-825: Commit c6d1c8a7a54f6bbeb1f6f81375d71e73e42f5999 in qpid-proton's branch refs/heads/master from [~chug] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=c6d1c8a ] PROTON-825: repair broken Windows VS2008 build BlockingReceiver.receive() uses 100% CPU. - Key: PROTON-825 URL: https://issues.apache.org/jira/browse/PROTON-825 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: 0.9 Environment: F20 Built from master 2/19. Reporter: Jeff Ortel Assignee: Alan Conway Fix For: 0.9 Calling BlockingReceiver.receive(timeout=10) blocks the caller for 10 seconds but uses 100% CPU. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
