[jira] [Commented] (PROTON-326) proton-c ServerTest.testIdleTimeout sometimes fails, causing test suite to hang forever
[
https://issues.apache.org/jira/browse/PROTON-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13676849#comment-13676849
]
Philip Harvey commented on PROTON-326:
--
Note that I would normally have captured a core dump to analyse where the tests
were stuck, but this was on a bare-bones machine without gdb installed :-(
proton-c ServerTest.testIdleTimeout sometimes fails, causing test suite to
hang forever
---
Key: PROTON-326
URL: https://issues.apache.org/jira/browse/PROTON-326
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Affects Versions: 0.4
Environment: Linux
Reporter: Philip Harvey
I ran the python test suite against proton-c today and noticed that
ServerTest.testIdleTimeout failed with the following output:
{noformat}
proton_tests.engine.ServerTest.testIdleTimeout
..ERROR amqp:resource-limit-exceeded
local-idle-timeout expired
fail
Error during test: Traceback (most recent call last):
File ./tests/python/proton-test, line 340, in run
phase()
File /.../workspace/proton/tests/python/proton_tests/engine.py, line
1412, in testIdleTimeout
assert self.conn.state == (Endpoint.LOCAL_ACTIVE |
Endpoint.REMOTE_ACTIVE), Connection terminated
AssertionError: Connection terminated
{noformat}
This test usually succeeds so I guess it contains a race condition.
Something that is arguably more problematic is that this failure causes the
test suite to hang. The suite proceeds to run the other tests, but does not
terminate when it reaches the end. On Linux, I actually had to kill the
process rather than ctrl-c-ing it.
I cannot reproduce the test failure, but I do find that if I make it fail
(for example, by modifying the assert on line 1412 to always fail) then the
suite hangs every time.
It's obviously undesirable for a failing test to cause the entire suite to
hang.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (PROTON-327) proton-c: soak.MessengerTests.test_relay_C_SSL sometimes fails
Philip Harvey created PROTON-327: Summary: proton-c: soak.MessengerTests.test_relay_C_SSL sometimes fails Key: PROTON-327 URL: https://issues.apache.org/jira/browse/PROTON-327 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Environment: Linux Reporter: Philip Harvey Today I observed the following test failure on my CI server. This is the first time I've seen the test fail. It passed when I re-ran it. Here is the test output: proton_tests.soak.MessengerTests.test_relay_C_SSL (from pythontests) Failing for the past 1 build (Since Failed#122 ) Took 1 min 0 sec. add description Error Message Command '['msgr-send', '-a', 'amqps://0.0.0.0:58694/X0Y,amqps://0.0.0.0:58694/X1Y,amqps://0.0.0.0:58694/X2Y,amqps://0.0.0.0:58694/X3Y,amqps://0.0.0.0:58694/X4Y', '-c', '85', '-R', '-t', '60']' failed Stacktrace Error during test: Traceback (most recent call last): File ./tests/python/proton-test, line 340, in run phase() File /.../proton/tests/python/proton_tests/soak.py, line 310, in test_relay_C_SSL self._do_relay_test(MessengerReceiverC(), MessengerReceiverC(), MessengerSenderC(), amqps) File /.../proton/tests/python/proton_tests/soak.py, line 220, in _do_relay_test self._do_test(iterations) File /.../proton/tests/python/proton_tests/soak.py, line 96, in _do_test assert S.status() == 0, Command '%s' failed % str(S.cmdline()) AssertionError: Command '['msgr-send', '-a', 'amqps://0.0.0.0:58694/X0Y,amqps://0.0.0.0:58694/X1Y,amqps://0.0.0.0:58694/X2Y,amqps://0.0.0.0:58694/X3Y,amqps://0.0.0.0:58694/X4Y', '-c', '85', '-R', '-t', '60']' failed -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-200) [Proton-c] Credit distribution by messenger is not balanced across all links
[ https://issues.apache.org/jira/browse/PROTON-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-200: --- Fix Version/s: (was: 0.4) 0.5 [Proton-c] Credit distribution by messenger is not balanced across all links Key: PROTON-200 URL: https://issues.apache.org/jira/browse/PROTON-200 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.3 Reporter: Ken Giusti Assignee: Ken Giusti Fix For: 0.5 Attachments: proton-200.patch, upstream-credit.patch The method used to distribute credit to receiving links may lead to starvation when the number of receiving links is the available credit. The distribution algorithm always starts with the same link - see messenger.c::pn_messenger_flow() -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-234) Add lots of logging to better understand inner working of proton
[ https://issues.apache.org/jira/browse/PROTON-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-234: --- Fix Version/s: 0.5 Add lots of logging to better understand inner working of proton Key: PROTON-234 URL: https://issues.apache.org/jira/browse/PROTON-234 Project: Qpid Proton Issue Type: Improvement Components: proton-c Reporter: Bozo Dragojevic Fix For: 0.5 Add lots of logging to proton to ease understnding of it's inner workings Introduce object naming facility as some layers are coupled really loosely for now the logging route will just dump everything out to stderr, as it was before This is currently one giant commit off 0.3: https://github.com/ttlj/qpid-proton/commits/upstream-logging It doesn't merge quite cleanly to trunk. If this is interesting thing to have I'd be willing to merge or rebase whichever is preferred. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-231) Allow messenger to be used inside an event loop
[ https://issues.apache.org/jira/browse/PROTON-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-231: --- Fix Version/s: 0.5 Allow messenger to be used inside an event loop --- Key: PROTON-231 URL: https://issues.apache.org/jira/browse/PROTON-231 Project: Qpid Proton Issue Type: Improvement Reporter: Bozo Dragojevic Fix For: 0.5 We use proton in multithreaded application. Network part is run by a separate threadpool (currently singlethreaded) but it needfs it's own event loop. The code below allows us to use messenger api in this context, before we can invest the time to switch to using the engine directly. https://github.com/ttlj/qpid-proton/commits/upstream-wakeup -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-288) Make it possible to start the server later during the test
[ https://issues.apache.org/jira/browse/PROTON-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-288: --- Fix Version/s: 0.5 Make it possible to start the server later during the test -- Key: PROTON-288 URL: https://issues.apache.org/jira/browse/PROTON-288 Project: Qpid Proton Issue Type: Bug Reporter: Bozo Dragojevic Fix For: 0.5 Attachments: 0001-Make-it-possible-to-start-the-server-later-during-th.patch, 0001-PROTON-288-Make-it-possible-to-start-the-server-late.patch I'm seeing weird behavior of messenger if the server is not around. The attached patch adds such capability to the messenger test class. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-274) Proton-C Sending a message to an non existant Service Bus entity suceeds
[
https://issues.apache.org/jira/browse/PROTON-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming updated PROTON-274:
---
Fix Version/s: 0.5
Proton-C Sending a message to an non existant Service Bus entity suceeds
Key: PROTON-274
URL: https://issues.apache.org/jira/browse/PROTON-274
Project: Qpid Proton
Issue Type: Bug
Affects Versions: 0.4
Reporter: Arun Dsouza
Priority: Minor
Fix For: 0.5
## Background ##
I am using Proton-C to communicate with a queue in Windows Azure Service Bus.
According to the Proton-C Samples the way to check if an operation suceeded
is use the pn_messenger_errno function. Its declaration is as follows
/** Returns the error code for the Messenger.
*
* @param[in] messenger the messenger to check for errors
*
* @return an error code or zero if there is no error
* @see error.h
*/
PN_EXTERN int pn_messenger_errno(pn_messenger_t *messenger);
Bug
Now If I try to send to a SB queue that DOES NOT exist. pn_messenger_errno
returns 0.
However if I try to send to an entity in an NON EXISTANT SB namespace.
pn_messenger_errno correctly returns a non 0 error code
### Relavent Proton Traces #
Connected to INT7-27689-0-2.servicebus.int7.windows-int.net:5671
- SASL
[0x9871400:0] - SASL-INIT @65 [:PLAIN,
b\x00owner\x00dexww###]
- SASL
[0x9871400:0] - SASL-MECHANISMS @64 [@PN_SYMBOL[:PLAIN, :EXTERNAL]]
[0x9871400:0] - SASL-OUTCOME @68 [0, bWelcome!]
- AMQP
[0x986c740:0] - OPEN @16 [1fcb1ed4-67a6-42d8-aaef-7e8aed0d5977,
INT7-27689-0-2.servicebus.int7.windows-int.net, null, null, null, null,
null, null, null]
[0x986c740:1] - BEGIN @17 [null, 0, 1024, 1024]
[0x986c740:1] - ATTACH @18 [sender-xxx, 1, false, null, null, @40
[zgflsmhbbfyle1, 0, null, 0, false, null, null, null, null, null, null],
@41 [zgflsmhbbfyle1, 0, null, 0, false, null, null], null, null, 0]
- AMQP
[0x986c740:0] - OPEN @16 [305ab36b6dba436a9c0b58546df87c7b_G1, null,
65536, 4999, 6, null, null, null, null, null]
[0x986c740:0] - BEGIN @17 [1, 1, 1024, 1024, 7, null, null, null]
[0x986c740:0] - ATTACH @18 [sender-xxx, 1, true, null, null, @40
[zgflsmhbbfyle1, 0, null, 0, false, null, null, null, null, null, null],
null, null, null, 0, null, null, null, null]
[0x986c740:0] - DETACH @22 [1, true, @29 [:amqp:not-found, The messaging
entity 'sb://int7-27689-0-2.servicebus.int7.windows-int.net/zgflsmhbbfyle1'
could not be
found..TrackingId:305ab36b6dba436a9c0b58546df87c7b_G1,TimeStamp:3/21/2013
9:44:53 PM, {:com.microsoft:stack-trace=\x0d\x0aServer stack trace:
\x0d\x0a\x0d\x0a\x0d\x0aException rethrown at [0]: \x0d\x0a at
Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult
result) in
d:\bt\109356\private\source\ServiceBus\Clients\Microsoft.ServiceBus.Messaging\Common\AsyncResult.cs:line
411\x0d\x0a at
Microsoft.Cloud.ServiceBus.Gateway.Runtime.AmqpGatewayProvider.Microsoft.Cloud.ServiceBus.Gateway.Runtime.IAmqpGatewayProvider.EndResolveAndAuthorize(IAsyncResult
result, Int64 containerId, Int32 partitionId, String entityName,
DateTime authorizationValidToUtc) in
d:\bt\109356\private\source\ServiceBus\Service\Messaging\Microsoft.Cloud.ServiceBus.Messaging\Amqp\AmqpGatewayProvider.cs:line
89\x0d\x0a at Microsoft.Cloud.ServiceBus.Gateway.Runtime.AmqpGatewa
LINK ERROR (amqp:not-found) The messaging entity
'sb://int7-27689-0-2.servicebus.int7.windows-int.net/zgflsmhbbfyle1' could
not be
found..TrackingId:305ab36b6dba436a9c0b58546df87c7b_G1,TimeStamp:3/21/2013
9:44:53 PM
[0x986c740:1] - DETACH @22 [1, true, null]
[0x986c740:0] - CLOSE @24 [null]
[0x986c740:0] - END @23 [@29 [:amqp:not-found, The messaging entity
'sb://int7-27689-0-2.servicebus.int7.windows-int.net/zgflsmhbbfyle1' could
not be
found..TrackingId:305ab36b6dba436a9c0b58546df87c7b_G1,TimeStamp:3/21/2013
9:44:53 PM, {:com.microsoft:stack-trace=\x0d\x0aServer stack trace:
\x0d\x0a\x0d\x0a\x0d\x0aException rethrown at [0]: \x0d\x0a at
Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult
result) in
d:\bt\109356\private\source\ServiceBus\Clients\Microsoft.ServiceBus.Messaging\Common\AsyncResult.cs:line
411\x0d\x0a at
Microsoft.Cloud.ServiceBus.Gateway.Runtime.AmqpGatewayProvider.Microsoft.Cloud.ServiceBus.Gateway.Runtime.IAmqpGatewayProvider.EndResolveAndAuthorize(IAsyncResult
result, Int64 containerId, Int32 partitionId, String entityName,
DateTime authorizationValidToUtc) in
d:\bt\109356\private\source\ServiceBus\Service\Messaging\Microsoft.Cloud.ServiceBus.Messaging\Amqp\AmqpGatewayProvider.cs:line
89\x0d\x0a at
[jira] [Updated] (PROTON-290) Allow querying of unsent messages by tracker
[ https://issues.apache.org/jira/browse/PROTON-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-290: --- Fix Version/s: 0.5 Allow querying of unsent messages by tracker Key: PROTON-290 URL: https://issues.apache.org/jira/browse/PROTON-290 Project: Qpid Proton Issue Type: New Feature Reporter: Bozo Dragojevic Fix For: 0.5 messenger.status(tracker) returns PENDING until the message is either accepted or rejected by the recipient. Allow distinguishing between buffered locally and transmitted messages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-317) Feature Enhancement - API Exposure of underlying references to internal atoms
[
https://issues.apache.org/jira/browse/PROTON-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming updated PROTON-317:
---
Fix Version/s: 0.5
Feature Enhancement - API Exposure of underlying references to internal atoms
-
Key: PROTON-317
URL: https://issues.apache.org/jira/browse/PROTON-317
Project: Qpid Proton
Issue Type: Improvement
Components: proton-c
Affects Versions: 0.3
Environment: Linux / C implementation
Reporter: Frank Quinn
Fix For: 0.5
We're currently creating a pn_message_t and iterating over it using the
pn_data_t data type and the various convenience methods surrounding it. This
is great for iteration but we were also hoping to have a way to *mark* a
point in the payload for future realignment. I looked at get_message_id() but
that always seems to return NULL.
Let's take a pseudo example:
pn_data_rewind (pn_data);
while (pn_data_next (pn_data))
{
pn_atom_t atom = pn_data_get_atom (pn_data);
if(this_atom_might_be_useful)
{
// Mark this for potential modification later
}
}
if (changes_are_required_based_on_a_combination_of_circumstances)
{
// Jump to earlier marker(s)
// put in relevant update(s)
}
Is there anything we could use for this sort of use case? I want to avoid
having to iterate *again* to find values, and I also want to be able to write
functions which don't move (or move, then reset) the internal buffer pointers
in proton. If there was something like a get_position() or set_position(),
that would be perfect.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-325) Python lists are truncated when None is encountered
[ https://issues.apache.org/jira/browse/PROTON-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-325: --- Fix Version/s: 0.5 Python lists are truncated when None is encountered --- Key: PROTON-325 URL: https://issues.apache.org/jira/browse/PROTON-325 Project: Qpid Proton Issue Type: Bug Components: proton-c Reporter: Ernest Allen Fix For: 0.5 When receiving a message that has a list with a None, all subsequent values in the list are lost. To reproduce: - modify program send.py by adding msg.properties = [one, two, None, three, four] before the mng.put(msg) line - launch example program recv.py - run modified send.py and notice the list truncation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (PROTON-322) Extend the native Ruby array and hash classes to work with the Data type
[ https://issues.apache.org/jira/browse/PROTON-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce resolved PROTON-322. - Resolution: Fixed Extend the native Ruby array and hash classes to work with the Data type Key: PROTON-322 URL: https://issues.apache.org/jira/browse/PROTON-322 Project: Qpid Proton Issue Type: Improvement Components: proton-c Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce Fix For: 0.5 Currently Ruby developers have to explicitly create instances of either Qpid::Proton::Data::List, Qpid::Proton::Data::Array or Qpid::Proton::Data::Map to get access to helper methods for interaction with Qpid::Proton::Data. But this too tightly couples the user to Proton-specific code for non-messaging related functions. Instead, we should leverage Ruby metaprogramming and add the needed functions to the standard Ruby classes directly. That way developers wouldn't need to refactor existing code to work with Proton. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (PROTON-329) Centos 6.4 build failure: Could NOT find PerlLibs
Evgeny Minkevich created PROTON-329: --- Summary: Centos 6.4 build failure: Could NOT find PerlLibs Key: PROTON-329 URL: https://issues.apache.org/jira/browse/PROTON-329 Project: Qpid Proton Issue Type: Bug Affects Versions: 0.4 Environment: Centos 6.4 x86_64 Reporter: Evgeny Minkevich Priority: Minor mkdir build cd build [tcs@centos build]$ cmake -DCMAKE_INSTALL_PREFIX=/usr .. PN_VERSION: 0.4 ... -- Could NOT find PerlLibs (missing: PERL_LIBRARY PERL_INCLUDE_PATH) ... [tcs@centos build]$ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (PROTON-330) Centos 6.4 build failure: Could NOT find Java
Evgeny Minkevich created PROTON-330: --- Summary: Centos 6.4 build failure: Could NOT find Java Key: PROTON-330 URL: https://issues.apache.org/jira/browse/PROTON-330 Project: Qpid Proton Issue Type: Bug Affects Versions: 0.4 Environment: Centos 6.4 x86_64 Reporter: Evgeny Minkevich Priority: Minor [tcs@centos build]$ echo $M2_HOME /home/tcs/apache-maven-3.0.5 [tcs@centos build]$ echo $JAVA_HOME /usr/lib/jvm/jre-1.6.0-openjdk.x86_64 [tcs@centos build]$ cmake -DCMAKE_INSTALL_PREFIX=/usr .. PN_VERSION: 0.4 -- Could NOT find Java (missing: Java_JAR_EXECUTABLE Java_JAVAC_EXECUTABLE Java_JAVAH_EXECUTABLE Java_JAVADOC_EXECUTABLE) -- Cannot find both Java and Maven: testing disabled for Proton-J and JNI Bindings -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PROTON-330) Centos 6.4 build failure: Could NOT find Java
[ https://issues.apache.org/jira/browse/PROTON-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13677792#comment-13677792 ] Evgeny Minkevich commented on PROTON-330: - My issue might be related to explicitly defining MAKE_INSTALLPREFIX. I think it might be an incorrect way to run it. Centos 6.4 build failure: Could NOT find Java - Key: PROTON-330 URL: https://issues.apache.org/jira/browse/PROTON-330 Project: Qpid Proton Issue Type: Bug Affects Versions: 0.4 Environment: Centos 6.4 x86_64 Reporter: Evgeny Minkevich Priority: Minor [tcs@centos build]$ echo $M2_HOME /home/tcs/apache-maven-3.0.5 [tcs@centos build]$ echo $JAVA_HOME /usr/lib/jvm/jre-1.6.0-openjdk.x86_64 [tcs@centos build]$ cmake -DCMAKE_INSTALL_PREFIX=/usr .. PN_VERSION: 0.4 -- Could NOT find Java (missing: Java_JAR_EXECUTABLE Java_JAVAC_EXECUTABLE Java_JAVAH_EXECUTABLE Java_JAVADOC_EXECUTABLE) -- Cannot find both Java and Maven: testing disabled for Proton-J and JNI Bindings -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
