[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=14336311#comment-14336311
]
ASF subversion and git services commented on PROTON-824:
Commit 37a0d6b07708beb2eeb21cd2bd97bd756f33ee71 in qpid-proton's branch
refs/heads/master from Clifford Jansen
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=37a0d6b ]
PROTON-824: idle timeout test on Windows: make selector PN_ERROR handling more
like POSIX, especially for broken connections
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-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)
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-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=14330136#comment-14330136
]
Rafael H. Schloming commented on PROTON-824:
PN_TRACE_FRM will log to stderr by default. Python's print statements are going
to stdout. You can send the print statements to stderr and see if that helps.
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)
