[jira] [Created] (PROTON-1755) How do create sessions and links dynamically once the connection is open ?
Priyanka Mathur created PROTON-1755: --- Summary: How do create sessions and links dynamically once the connection is open ? Key: PROTON-1755 URL: https://issues.apache.org/jira/browse/PROTON-1755 Project: Qpid Proton Issue Type: Bug Components: proton-j Affects Versions: proton-j-0.25.0 Reporter: Priyanka Mathur Hi Proton-j folks, We use proton-j library for establishing a connection and sending/receiving messages over it.Until now we never had the need to *add* a new session or new link to an existing and *opened* connection. Now that we have multiplexing, we have the need to add a new session (and)/or add a new link to already existing and opened connection. My question is how do I do that ? Once we start the reactor, we receive several callbacks and callbacks of importance here are 1. onConnectionInit 2. onConnectionBound -> we start a session 3. onLinkInit -> we start a link 4. onLinkRemoteOpen -> we check if link has opened and the connection is now established. Question is now that connection is opened, how do I add a new session to the already opened connection ? how do I add a new link to the already opened session ? Is there any such support from proton-j ? As AMQP protocol clearly should support it. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-919) Display a warning when running Dispatch tests if python-unittest2 is not installed
[ https://issues.apache.org/jira/browse/DISPATCH-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341570#comment-16341570 ] ASF GitHub Bot commented on DISPATCH-919: - GitHub user ganeshmurthy opened a pull request: https://github.com/apache/qpid-dispatch/pull/248 DISPATCH-919 - Modified CMakeLists.txt to warn when python-unittest2 … …is not present. When it is not present, no tests will be run You can merge this pull request into a Git repository by running: $ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-919 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/248.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #248 commit 320c8ca066737a44f5504f59794b937f73150dc8 Author: Ganesh Murthy Date: 2018-01-26T20:46:10Z DISPATCH-919 - Modified CMakeLists.txt to warn when python-unittest2 is not present. When it is not present, no tests will be run > Display a warning when running Dispatch tests if python-unittest2 is not > installed > -- > > Key: DISPATCH-919 > URL: https://issues.apache.org/jira/browse/DISPATCH-919 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests >Affects Versions: 1.0.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Minor > > Because of changes made to DISPATCH-894 we now require python-unittest2 > package to be installed to be able to run the system tests. For anyone moving > from Dispatch 1.0.0 to 1.1.0, this information is not obvious. (we do have > this information in the readme) > Please display a visible warning (python-unittest2 needs to be installed in > order to run tests) when a unit test is run (or if the entire test suite is > run) without having python-unittest2 installed. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #248: DISPATCH-919 - Modified CMakeLists.txt to w...
GitHub user ganeshmurthy opened a pull request: https://github.com/apache/qpid-dispatch/pull/248 DISPATCH-919 - Modified CMakeLists.txt to warn when python-unittest2 ⦠â¦is not present. When it is not present, no tests will be run You can merge this pull request into a Git repository by running: $ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-919 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/248.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #248 commit 320c8ca066737a44f5504f59794b937f73150dc8 Author: Ganesh Murthy Date: 2018-01-26T20:46:10Z DISPATCH-919 - Modified CMakeLists.txt to warn when python-unittest2 is not present. When it is not present, no tests will be run --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-904) Add charts to overview page
[ https://issues.apache.org/jira/browse/DISPATCH-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-904. --- Resolution: Implemented Fix Version/s: 1.1.0 > Add charts to overview page > --- > > Key: DISPATCH-904 > URL: https://issues.apache.org/jira/browse/DISPATCH-904 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Affects Versions: 1.0.0 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Major > Fix For: 1.1.0 > > > a. Total message throughput rate > b. Total outstanding messages (messages in flight) > c. List of most active clients with their message throughput and rates > d. more to come -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-917) Factor out common html/js/css between stand-alone and hawtio2 plugin into separate npm module
[ https://issues.apache.org/jira/browse/DISPATCH-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-917. --- Resolution: Done Fix Version/s: 1.1.0 The following pages are now loaded from an npm package (dispatch-console-pages): * Login * Overview * Entities * Topology * Charts * Schema > Factor out common html/js/css between stand-alone and hawtio2 plugin into > separate npm module > - > > Key: DISPATCH-917 > URL: https://issues.apache.org/jira/browse/DISPATCH-917 > Project: Qpid Dispatch > Issue Type: Task > Components: Console >Affects Versions: 1.0.0 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Major > Fix For: 1.1.0 > > > To avoid duplication of html/js/css between the stand-alone console and the > hawtio2 plugin, as much html/js/css as possible should be moved info a > separate npm module. > This new npm module is named dispatch-console-pages. > * The package.json file should be updated to pull in the new module > * The index.html should be modified to refer to the new js and css file > locations > * dispatchPlugin.js should be modified to inform angularjs of the new html > template locations. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-917) Factor out common html/js/css between stand-alone and hawtio2 plugin into separate npm module
[ https://issues.apache.org/jira/browse/DISPATCH-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341472#comment-16341472 ] ASF subversion and git services commented on DISPATCH-917: -- Commit 732382457c7cc4c31ddef7fc44a4b0acb65c049e in qpid-dispatch's branch refs/heads/master from [~eallen] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=7323824 ] DISPATCH-917 Force npm to use latest dispatch-* packages > Factor out common html/js/css between stand-alone and hawtio2 plugin into > separate npm module > - > > Key: DISPATCH-917 > URL: https://issues.apache.org/jira/browse/DISPATCH-917 > Project: Qpid Dispatch > Issue Type: Task > Components: Console >Affects Versions: 1.0.0 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Major > > To avoid duplication of html/js/css between the stand-alone console and the > hawtio2 plugin, as much html/js/css as possible should be moved info a > separate npm module. > This new npm module is named dispatch-console-pages. > * The package.json file should be updated to pull in the new module > * The index.html should be modified to refer to the new js and css file > locations > * dispatchPlugin.js should be modified to inform angularjs of the new html > template locations. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1592) [proton-python] accessing properties of event.receiver in on_link_opened throws exception
[
https://issues.apache.org/jira/browse/PROTON-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-1592:
Fix Version/s: (was: proton-c-0.18.0)
proton-c-future
> [proton-python] accessing properties of event.receiver in on_link_opened
> throws exception
> -
>
> Key: PROTON-1592
> URL: https://issues.apache.org/jira/browse/PROTON-1592
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Reporter: Jiri Daněk
>Assignee: Alan Conway
>Priority: Major
> Labels: regression
> Fix For: proton-c-future
>
>
> Apply the following patch to the {{tx-recv.py}} example
> {code}
> diff --git a/examples/python/tx_recv.py b/examples/python/tx_recv.py
> index 4baddcf5..54f3b489 100755
> --- a/examples/python/tx_recv.py
> +++ b/examples/python/tx_recv.py
> @@ -40,6 +40,9 @@ class TxRecv(MessagingHandler, TransactionHandler):
> self.container.declare_transaction(self.conn, handler=self)
> self.transaction = None
>
> + def on_link_opened(self, event):
> + event.receiver.drain_mode = True
> +
> def on_message(self, event):
> print(event.message.body)
> self.transaction.accept(event.delivery)
> {code}
> Now run first {{tx_send.py}}, then this {{tx_recv.py}}. The second command
> throws exception
> {noformat}
> $ LD_LIBRARY_PATH=`pwd`/lib64 PYTHONPATH=`pwd`/lib64/proton/bindings/python
> python ../examples/python/tx_recv.py
> Traceback (most recent call last):
> File "../examples/python/tx_recv.py", line 79, in
> Container(TxRecv(opts.address, opts.messages, opts.batch_size)).run()
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/reactor.py",
> line 148, in run
> while self.process(): pass
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/reactor.py",
> line 174, in process
> self._check_errors()
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/reactor.py",
> line 170, in _check_errors
> _compat.raise_(exc, value, tb)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
> line 4068, in dispatch
> ev.dispatch(self.handler)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
> line 3977, in dispatch
> result = dispatch(handler, type.method, self)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
> line 3857, in dispatch
> return handler.on_unhandled(method, *args)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/reactor.py",
> line 876, in on_unhandled
> event.dispatch(handler)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
> line 3980, in dispatch
> self.dispatch(h, type)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
> line 3977, in dispatch
> result = dispatch(handler, type.method, self)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
> line 3855, in dispatch
> return m(*args)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/handlers.py",
> line 298, in on_link_remote_open
> self.on_link_opened(event)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/handlers.py",
> line 313, in on_link_opened
> dispatch(self.delegate, 'on_link_opened', event)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
> line 3855, in dispatch
> return m(*args)
> File "../examples/python/tx_recv.py", line 44, in on_link_opened
> event.receiver.drain_mode = True
> AttributeError: 'NoneType' object has no attribute 'drain_mode'
> {noformat}
> To see this is a regression, repeat now with python-qpid-proton 0.17.0 from
> Pypi. With this previous release, there is success.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (PROTON-1592) [proton-python] accessing properties of event.receiver in on_link_opened throws exception
[
https://issues.apache.org/jira/browse/PROTON-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross reopened PROTON-1592:
-
> [proton-python] accessing properties of event.receiver in on_link_opened
> throws exception
> -
>
> Key: PROTON-1592
> URL: https://issues.apache.org/jira/browse/PROTON-1592
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Reporter: Jiri Daněk
>Assignee: Alan Conway
>Priority: Major
> Labels: regression
> Fix For: proton-c-0.18.0
>
>
> Apply the following patch to the {{tx-recv.py}} example
> {code}
> diff --git a/examples/python/tx_recv.py b/examples/python/tx_recv.py
> index 4baddcf5..54f3b489 100755
> --- a/examples/python/tx_recv.py
> +++ b/examples/python/tx_recv.py
> @@ -40,6 +40,9 @@ class TxRecv(MessagingHandler, TransactionHandler):
> self.container.declare_transaction(self.conn, handler=self)
> self.transaction = None
>
> + def on_link_opened(self, event):
> + event.receiver.drain_mode = True
> +
> def on_message(self, event):
> print(event.message.body)
> self.transaction.accept(event.delivery)
> {code}
> Now run first {{tx_send.py}}, then this {{tx_recv.py}}. The second command
> throws exception
> {noformat}
> $ LD_LIBRARY_PATH=`pwd`/lib64 PYTHONPATH=`pwd`/lib64/proton/bindings/python
> python ../examples/python/tx_recv.py
> Traceback (most recent call last):
> File "../examples/python/tx_recv.py", line 79, in
> Container(TxRecv(opts.address, opts.messages, opts.batch_size)).run()
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/reactor.py",
> line 148, in run
> while self.process(): pass
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/reactor.py",
> line 174, in process
> self._check_errors()
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/reactor.py",
> line 170, in _check_errors
> _compat.raise_(exc, value, tb)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
> line 4068, in dispatch
> ev.dispatch(self.handler)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
> line 3977, in dispatch
> result = dispatch(handler, type.method, self)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
> line 3857, in dispatch
> return handler.on_unhandled(method, *args)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/reactor.py",
> line 876, in on_unhandled
> event.dispatch(handler)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
> line 3980, in dispatch
> self.dispatch(h, type)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
> line 3977, in dispatch
> result = dispatch(handler, type.method, self)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
> line 3855, in dispatch
> return m(*args)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/handlers.py",
> line 298, in on_link_remote_open
> self.on_link_opened(event)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/handlers.py",
> line 313, in on_link_opened
> dispatch(self.delegate, 'on_link_opened', event)
> File
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
> line 3855, in dispatch
> return m(*args)
> File "../examples/python/tx_recv.py", line 44, in on_link_opened
> event.receiver.drain_mode = True
> AttributeError: 'NoneType' object has no attribute 'drain_mode'
> {noformat}
> To see this is a regression, repeat now with python-qpid-proton 0.17.0 from
> Pypi. With this previous release, there is success.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-1734) [cpp] container.stop() doesn't work when called from non-proactor thread.
[
https://issues.apache.org/jira/browse/PROTON-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross reassigned PROTON-1734:
---
Assignee: Andrew Stitcher (was: Alan Conway)
> [cpp] container.stop() doesn't work when called from non-proactor thread.
> -
>
> Key: PROTON-1734
> URL: https://issues.apache.org/jira/browse/PROTON-1734
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding
>Affects Versions: proton-c-0.19.0
>Reporter: Alan Conway
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.21.0
>
>
> Using the below code
> {code}
> #include
> #include
> #include
> int main( int, char** )
> {
> try
> {
> proton::container c;
> c.auto_stop( false );
> auto containerThread = std::thread([&]() { std::cout << "CONTAINER IS
> RUNNING" << std::endl;
>
> c.run(); std::cout << "CONTAINER IS DONE" << std::endl; });
> std::this_thread::sleep_for( std::chrono::seconds( 2 ));
> std::cout << "STOPPING CONTAINER" << std::endl;
> c.stop();
> std::cout << "WAITING FOR CONTAINER" << std::endl;
> containerThread.join();
> return 0;
> }
> catch( std::exception& e )
> {
> std::cerr << e.what() << std::endl;
> }
> return 1;
> }
> {code}
> via
> {code}
> [rkieley@i7t450s build]$ g++ -g -Wall -Wextra -Wpointer-arith -Wconversion
> -Wformat -Wformat-security -Wformat-y2k -Wsign-promo -Wcast-qual -g3 -ggdb3
> -Wunused-variable -fno-eliminate-unused-debug-types -O3 -DNDEBUG -fPIC
> -DPN_CPP_HAS_LAMBDAS=0 -std=gnu++11 ../attachments/test.cpp
> -lqpid-proton-cpp -lqpid-proton-core -lqpid-proton-proactor -lrt -lpthread -o
> test
> {code}
> With both PROACTOR epoll and libuv I see the following when run:
> {quote}
> [New Thread 0x73c95700 (LWP 20312)]
> CONTAINER IS RUNNING
> STOPPING CONTAINER
> WAITING FOR CONTAINER
> ^C
> Thread 1 "test" received signal SIGINT, Interrupt.
> {quote}
> When I use CTRL-C to stop waiting after running via gdb and waiting 2 minutes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-911) Add link and address level counters at the global router level
[ https://issues.apache.org/jira/browse/DISPATCH-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341390#comment-16341390 ] ASF GitHub Bot commented on DISPATCH-911: - GitHub user ganeshmurthy opened a pull request: https://github.com/apache/qpid-dispatch/pull/247 DISPATCH-911 - Added global delivery counts You can merge this pull request into a Git repository by running: $ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-911 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/247.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #247 commit 2e4896c9dd4db64499b2809cbf7e07df5f9c2258 Author: Ganesh Murthy Date: 2018-01-26T18:12:12Z DISPATCH-911 - Added global delivery counts > Add link and address level counters at the global router level > -- > > Key: DISPATCH-911 > URL: https://issues.apache.org/jira/browse/DISPATCH-911 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Management Agent >Affects Versions: 1.0.0 >Reporter: Ernest Allen >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.1.0 > > > Link already has the following counters - > presettledCount > droppedPresettledCount > acceptedCount > rejectedCount > releasedCount > modifiedCount > Address already has the following counters > deliveriesIngress > deliveriesEgress > deliveriesTransit > 1. Add the above link and address counters to the global router level as well. > 2. Add routeContainerDeliveriesEgress and routeContainerDeliveriesIngress as > address and global counters > 3. Add router memory footprint as a global statistic -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #247: DISPATCH-911 - Added global delivery counts
GitHub user ganeshmurthy opened a pull request: https://github.com/apache/qpid-dispatch/pull/247 DISPATCH-911 - Added global delivery counts You can merge this pull request into a Git repository by running: $ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-911 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/247.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #247 commit 2e4896c9dd4db64499b2809cbf7e07df5f9c2258 Author: Ganesh Murthy Date: 2018-01-26T18:12:12Z DISPATCH-911 - Added global delivery counts --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-91) AmqpNetLite does not include large_content test
[ https://issues.apache.org/jira/browse/QPIDIT-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-91. -- Resolution: Fixed > AmqpNetLite does not include large_content test > --- > > Key: QPIDIT-91 > URL: https://issues.apache.org/jira/browse/QPIDIT-91 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > Fix For: 0.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (QPIDIT-92) AmqpNetLite types_test Receiver compile error with Lite v2.0.0
[ https://issues.apache.org/jira/browse/QPIDIT-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet reopened QPIDIT-92: > AmqpNetLite types_test Receiver compile error with Lite v2.0.0 > -- > > Key: QPIDIT-92 > URL: https://issues.apache.org/jira/browse/QPIDIT-92 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug >Reporter: Chuck Rolke >Priority: Major > Fix For: 0.1.0 > > > A small API change requires a source code update. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDIT-91) AmqpNetLite does not include large_content test
[ https://issues.apache.org/jira/browse/QPIDIT-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPIDIT-91: --- Fix Version/s: 0.1.0 > AmqpNetLite does not include large_content test > --- > > Key: QPIDIT-91 > URL: https://issues.apache.org/jira/browse/QPIDIT-91 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > Fix For: 0.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (QPIDIT-91) AmqpNetLite does not include large_content test
[ https://issues.apache.org/jira/browse/QPIDIT-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet reopened QPIDIT-91: > AmqpNetLite does not include large_content test > --- > > Key: QPIDIT-91 > URL: https://issues.apache.org/jira/browse/QPIDIT-91 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > Fix For: 0.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDIT-92) AmqpNetLite types_test Receiver compile error with Lite v2.0.0
[ https://issues.apache.org/jira/browse/QPIDIT-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPIDIT-92: --- Fix Version/s: 0.1.0 > AmqpNetLite types_test Receiver compile error with Lite v2.0.0 > -- > > Key: QPIDIT-92 > URL: https://issues.apache.org/jira/browse/QPIDIT-92 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug >Reporter: Chuck Rolke >Priority: Major > Fix For: 0.1.0 > > > A small API change requires a source code update. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-92) AmqpNetLite types_test Receiver compile error with Lite v2.0.0
[ https://issues.apache.org/jira/browse/QPIDIT-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-92. -- Resolution: Fixed > AmqpNetLite types_test Receiver compile error with Lite v2.0.0 > -- > > Key: QPIDIT-92 > URL: https://issues.apache.org/jira/browse/QPIDIT-92 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug >Reporter: Chuck Rolke >Priority: Major > Fix For: 0.1.0 > > > A small API change requires a source code update. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (QPIDIT-35) Add Dispatch Router to Jenkins CI
[ https://issues.apache.org/jira/browse/QPIDIT-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet reopened QPIDIT-35: > Add Dispatch Router to Jenkins CI > - > > Key: QPIDIT-35 > URL: https://issues.apache.org/jira/browse/QPIDIT-35 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task > Components: AMQP Types Test, JMS Message Test >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Add a pair of tasks to Jenkins CI: > * Build Dispatch Router from git checkout of master > * Add tests for AMQP types and JMS messages to use Dispatch Router as a broker > Dispatch Router can be configured in both brokerless and multiple brokered > topologies. The tests need to run against both of these configurations. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-35) Add Dispatch Router to Jenkins CI
[ https://issues.apache.org/jira/browse/QPIDIT-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-35. -- Resolution: Fixed > Add Dispatch Router to Jenkins CI > - > > Key: QPIDIT-35 > URL: https://issues.apache.org/jira/browse/QPIDIT-35 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task > Components: AMQP Types Test, JMS Message Test >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Add a pair of tasks to Jenkins CI: > * Build Dispatch Router from git checkout of master > * Add tests for AMQP types and JMS messages to use Dispatch Router as a broker > Dispatch Router can be configured in both brokerless and multiple brokered > topologies. The tests need to run against both of these configurations. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDIT-35) Add Dispatch Router to Jenkins CI
[ https://issues.apache.org/jira/browse/QPIDIT-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPIDIT-35: --- Fix Version/s: 0.1.0 > Add Dispatch Router to Jenkins CI > - > > Key: QPIDIT-35 > URL: https://issues.apache.org/jira/browse/QPIDIT-35 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task > Components: AMQP Types Test, JMS Message Test >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Add a pair of tasks to Jenkins CI: > * Build Dispatch Router from git checkout of master > * Add tests for AMQP types and JMS messages to use Dispatch Router as a broker > Dispatch Router can be configured in both brokerless and multiple brokered > topologies. The tests need to run against both of these configurations. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
***UNCHECKED*** [jira] [Closed] (QPIDIT-50) Large content Sender.cpp does not compile
[
https://issues.apache.org/jira/browse/QPIDIT-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet closed QPIDIT-50.
--
> Large content Sender.cpp does not compile
> -
>
> Key: QPIDIT-50
> URL: https://issues.apache.org/jira/browse/QPIDIT-50
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: AMQP Large Content Test
> Environment: Fedora 23, GCC 5.3.1
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
>Priority: Major
> Fix For: 0.1.0
>
>
> {noformat}
> /home/chug/git/qpid-interop-test/shims/qpid-proton-cpp/src/qpidit/amqp_large_content_test/Sender.cpp:57:42:
>
> error: base operand of ‘->’ has non-pointer type ‘Json::Value::const_iterator
> {aka Json::ValueConstIterator}’
> totSizeMb = i->asInt();
> ^
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-49) Quickstart needs to describe C++ dependencies
[ https://issues.apache.org/jira/browse/QPIDIT-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-49. -- > Quickstart needs to describe C++ dependencies > - > > Key: QPIDIT-49 > URL: https://issues.apache.org/jira/browse/QPIDIT-49 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug > Components: Documentation >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > Fix For: 0.1.0 > > > In particular json-cpp-devel. Without it cmake, make completes with no C++ > shim produced. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
***UNCHECKED*** [jira] [Updated] (QPIDIT-50) Large content Sender.cpp does not compile
[
https://issues.apache.org/jira/browse/QPIDIT-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet updated QPIDIT-50:
---
Fix Version/s: 0.1.0
> Large content Sender.cpp does not compile
> -
>
> Key: QPIDIT-50
> URL: https://issues.apache.org/jira/browse/QPIDIT-50
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: AMQP Large Content Test
> Environment: Fedora 23, GCC 5.3.1
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
>Priority: Major
> Fix For: 0.1.0
>
>
> {noformat}
> /home/chug/git/qpid-interop-test/shims/qpid-proton-cpp/src/qpidit/amqp_large_content_test/Sender.cpp:57:42:
>
> error: base operand of ‘->’ has non-pointer type ‘Json::Value::const_iterator
> {aka Json::ValueConstIterator}’
> totSizeMb = i->asInt();
> ^
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDIT-49) Quickstart needs to describe C++ dependencies
[ https://issues.apache.org/jira/browse/QPIDIT-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPIDIT-49: --- Fix Version/s: 0.1.0 > Quickstart needs to describe C++ dependencies > - > > Key: QPIDIT-49 > URL: https://issues.apache.org/jira/browse/QPIDIT-49 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug > Components: Documentation >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > Fix For: 0.1.0 > > > In particular json-cpp-devel. Without it cmake, make completes with no C++ > shim produced. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
***UNCHECKED*** [jira] [Closed] (QPIDIT-55) Proton install dir is hard coded into cmake
[ https://issues.apache.org/jira/browse/QPIDIT-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-55. -- > Proton install dir is hard coded into cmake > --- > > Key: QPIDIT-55 > URL: https://issues.apache.org/jira/browse/QPIDIT-55 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug > Components: Installation >Reporter: Chuck Rolke >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > Attachments: QPIDIT-55-cmake-find-proton.patch > > > Recent commits in cmake force proton to be at /usr/local. This does not work > for me. > We should swipe qpid-cpp/amqp code and consume proton the same way. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-56) Rhea installs to /usr/lib regardless of cmake install dir
[
https://issues.apache.org/jira/browse/QPIDIT-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet closed QPIDIT-56.
--
> Rhea installs to /usr/lib regardless of cmake install dir
> -
>
> Key: QPIDIT-56
> URL: https://issues.apache.org/jira/browse/QPIDIT-56
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: Rhea JavaScript Shim
> Environment: Fedora 23 x64, bash
>Reporter: Chuck Rolke
>Assignee: Kim van der Riet
>Priority: Major
> Fix For: 0.1.0
>
>
> {noformat}
> export INSTALLPREFIX=/opt/local
> cd ${QPID_INTEROP_TEST_HOME}/build
> cmake -DCMAKE_BUILD_TYPE=Debug \
> -DCMAKE_INSTALL_PREFIX=${INSTALLPREFIX} \
> -DPROTON_INSTALL_DIR=${INSTALLPREFIX} \
> ..
> {noformat}
> Fails when npm can't create a directory in /usr/lib
> {noformat}
> npm ERR! Error: EACCES, mkdir '/usr/lib/node_modules/rhea'
> npm ERR! { [Error: EACCES, mkdir '/usr/lib/node_modules/rhea']
> npm ERR! errno: 3,
> npm ERR! code: 'EACCES',
> npm ERR! path: '/usr/lib/node_modules/rhea',
> npm ERR! fstream_type: 'Directory',
> npm ERR! fstream_path: '/usr/lib/node_modules/rhea',
> npm ERR! fstream_class: 'DirWriter',
> npm ERR! fstream_stack:
> npm ERR![ '/usr/lib/node_modules/fstream/lib/dir-writer.js:36:23',
> npm ERR! '/usr/lib/node_modules/mkdirp/index.js:37:53',
> npm ERR! 'Object.oncomplete (fs.js:108:15)' ] }
> npm ERR!
> npm ERR! Please try running this command again as root/Administrator.
> {noformat}
> My policy is to never run local builds as root. I have /opt/local set up as
> the target workspace for my local installs. Typically I build/install
> * qpid-proton
> * qpid-python
> * qpid-cpp
> * qpid-dispatch
> * qpid-interop-test
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-51) Method needed to skip sensing broker type
[ https://issues.apache.org/jira/browse/QPIDIT-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-51. -- > Method needed to skip sensing broker type > - > > Key: QPIDIT-51 > URL: https://issues.apache.org/jira/browse/QPIDIT-51 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug >Reporter: Chuck Rolke >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > I'm running a test broker from [Amqp.NET > Lite|https://github.com/Azure/amqpnetlite]. This broker has no claims of > being fit to run in production but it is an excellent non-qpid-proton test > bed for interoperability tests. > The Lite broker has a restriction that if it is configured to use SASL then > it always uses SASL regardless of how the client connects and negotiates AMQP > security layers. This causes a connection problem with the current setup of > QPIDIT. Although the QPIDIT tests proper do not use SASL the broker-type > sensing code does. The net result is that the test can't connect to the > broker. > This issue tracks a solution for this problem. Possible resolutions at the > CLI level are: > * CLI switch to inhibit sensing the broker type. > * CLI switch to force the test to assume a given broker type. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
***UNCHECKED*** [jira] [Updated] (QPIDIT-62) Add AMQP.Net Lite client shims
[ https://issues.apache.org/jira/browse/QPIDIT-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPIDIT-62: --- Fix Version/s: 0.1.0 > Add AMQP.Net Lite client shims > -- > > Key: QPIDIT-62 > URL: https://issues.apache.org/jira/browse/QPIDIT-62 > Project: Apache QPID Interoperability Test Suite > Issue Type: New Feature > Components: .Net Lite Shim > Environment: .NET Core or Mono to compile/run client >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > Fix For: 0.1.0 > > > [AMQP.Net Lite|https://github.com/Azure/amqpnetlite] is a mature AMQP client > and a good candidate for inclusion in this test suite. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDIT-70) [amqpnetlite] Receiver shim does not properly encode json results
[
https://issues.apache.org/jira/browse/QPIDIT-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet updated QPIDIT-70:
---
Affects Version/s: (was: Future)
> [amqpnetlite] Receiver shim does not properly encode json results
> -
>
> Key: QPIDIT-70
> URL: https://issues.apache.org/jira/browse/QPIDIT-70
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: .Net Lite Shim
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
>Priority: Major
> Fix For: 0.1.0
>
>
> Strings containing a backslash fail and the rules governing backslashes are
> not clear.
> In debug tests with the console printing the sent/received payloads
> AmqpNetLite and ProtonCpp show:
> Sender (both cases):
> {noformat}
> '["", "12345", "Hello, world",
> "x01x02x03x04x05abcdex80x81xfexff"]'
> {noformat}
> ProtonCpp works by returning:
> {noformat}
> binary
> ["","12345","Hello,
> world","\\x01\\x02\\x03\\x04\\x05abcde\\x80\\x81\\xfe\\xff"]
> {noformat}
> AmqpNetLite fails by returning:
> {noformat}
> ["", "12345", "Hello, world",
> "\x01\x02\x03\x04\x05abcde\x80\x81\xfe\xff"]{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-62) Add AMQP.Net Lite client shims
[ https://issues.apache.org/jira/browse/QPIDIT-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-62. -- > Add AMQP.Net Lite client shims > -- > > Key: QPIDIT-62 > URL: https://issues.apache.org/jira/browse/QPIDIT-62 > Project: Apache QPID Interoperability Test Suite > Issue Type: New Feature > Components: .Net Lite Shim > Environment: .NET Core or Mono to compile/run client >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > Fix For: 0.1.0 > > > [AMQP.Net Lite|https://github.com/Azure/amqpnetlite] is a mature AMQP client > and a good candidate for inclusion in this test suite. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-70) [amqpnetlite] Receiver shim does not properly encode json results
[
https://issues.apache.org/jira/browse/QPIDIT-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet closed QPIDIT-70.
--
> [amqpnetlite] Receiver shim does not properly encode json results
> -
>
> Key: QPIDIT-70
> URL: https://issues.apache.org/jira/browse/QPIDIT-70
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: .Net Lite Shim
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
>Priority: Major
> Fix For: 0.1.0
>
>
> Strings containing a backslash fail and the rules governing backslashes are
> not clear.
> In debug tests with the console printing the sent/received payloads
> AmqpNetLite and ProtonCpp show:
> Sender (both cases):
> {noformat}
> '["", "12345", "Hello, world",
> "x01x02x03x04x05abcdex80x81xfexff"]'
> {noformat}
> ProtonCpp works by returning:
> {noformat}
> binary
> ["","12345","Hello,
> world","\\x01\\x02\\x03\\x04\\x05abcde\\x80\\x81\\xfe\\xff"]
> {noformat}
> AmqpNetLite fails by returning:
> {noformat}
> ["", "12345", "Hello, world",
> "\x01\x02\x03\x04\x05abcde\x80\x81\xfe\xff"]{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDIT-70) [amqpnetlite] Receiver shim does not properly encode json results
[
https://issues.apache.org/jira/browse/QPIDIT-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet updated QPIDIT-70:
---
Fix Version/s: 0.1.0
> [amqpnetlite] Receiver shim does not properly encode json results
> -
>
> Key: QPIDIT-70
> URL: https://issues.apache.org/jira/browse/QPIDIT-70
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: .Net Lite Shim
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
>Priority: Major
> Fix For: 0.1.0
>
>
> Strings containing a backslash fail and the rules governing backslashes are
> not clear.
> In debug tests with the console printing the sent/received payloads
> AmqpNetLite and ProtonCpp show:
> Sender (both cases):
> {noformat}
> '["", "12345", "Hello, world",
> "x01x02x03x04x05abcdex80x81xfexff"]'
> {noformat}
> ProtonCpp works by returning:
> {noformat}
> binary
> ["","12345","Hello,
> world","\\x01\\x02\\x03\\x04\\x05abcde\\x80\\x81\\xfe\\xff"]
> {noformat}
> AmqpNetLite fails by returning:
> {noformat}
> ["", "12345", "Hello, world",
> "\x01\x02\x03\x04\x05abcde\x80\x81\xfe\xff"]{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDIT-71) [amqpnetlite] cmake fails to detect program mono version
[
https://issues.apache.org/jira/browse/QPIDIT-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet updated QPIDIT-71:
---
Fix Version/s: 0.1.0
> [amqpnetlite] cmake fails to detect program mono version
>
>
> Key: QPIDIT-71
> URL: https://issues.apache.org/jira/browse/QPIDIT-71
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: .Net Lite Shim
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
>Priority: Major
> Fix For: 0.1.0
>
>
> The error shows as:
> {noformat}
> CMake Error at shims/amqpnetlite/src/CMakeLists.txt:43 (string):
> string sub-command REPLACE requires at least four arguments.
> {noformat}
> where the missing argument is probably the detected version output string.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-71) [amqpnetlite] cmake fails to detect program mono version
[
https://issues.apache.org/jira/browse/QPIDIT-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet closed QPIDIT-71.
--
> [amqpnetlite] cmake fails to detect program mono version
>
>
> Key: QPIDIT-71
> URL: https://issues.apache.org/jira/browse/QPIDIT-71
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: .Net Lite Shim
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
>Priority: Major
> Fix For: 0.1.0
>
>
> The error shows as:
> {noformat}
> CMake Error at shims/amqpnetlite/src/CMakeLists.txt:43 (string):
> string sub-command REPLACE requires at least four arguments.
> {noformat}
> where the missing argument is probably the detected version output string.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
***UNCHECKED*** [jira] [Closed] (QPIDIT-95) update to use the current v18 apache parent pom
[ https://issues.apache.org/jira/browse/QPIDIT-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-95. -- Resolution: Fixed > update to use the current v18 apache parent pom > --- > > Key: QPIDIT-95 > URL: https://issues.apache.org/jira/browse/QPIDIT-95 > Project: Apache QPID Interoperability Test Suite > Issue Type: Improvement > Components: Installation, Qpid Jms Shim >Affects Versions: 0.1.0 >Reporter: Robbie Gemmell >Priority: Major > Fix For: 0.1.0 > > > update to use the current v18 apache parent pom to better align with all the > other components, aiding in consistent use of plugin versions -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDIT-72) [amqpnetlite] types test Receiver returns wrong value for null message
[ https://issues.apache.org/jira/browse/QPIDIT-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPIDIT-72: --- Fix Version/s: 0.1.0 > [amqpnetlite] types test Receiver returns wrong value for null message > -- > > Key: QPIDIT-72 > URL: https://issues.apache.org/jira/browse/QPIDIT-72 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > Fix For: 0.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-72) [amqpnetlite] types test Receiver returns wrong value for null message
[ https://issues.apache.org/jira/browse/QPIDIT-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-72. -- > [amqpnetlite] types test Receiver returns wrong value for null message > -- > > Key: QPIDIT-72 > URL: https://issues.apache.org/jira/browse/QPIDIT-72 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > Fix For: 0.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDIT-95) update to use the current v18 apache parent pom
[ https://issues.apache.org/jira/browse/QPIDIT-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPIDIT-95: --- Fix Version/s: 0.1.0 > update to use the current v18 apache parent pom > --- > > Key: QPIDIT-95 > URL: https://issues.apache.org/jira/browse/QPIDIT-95 > Project: Apache QPID Interoperability Test Suite > Issue Type: Improvement > Components: Installation, Qpid Jms Shim >Affects Versions: 0.1.0 >Reporter: Robbie Gemmell >Priority: Major > Fix For: 0.1.0 > > > update to use the current v18 apache parent pom to better align with all the > other components, aiding in consistent use of plugin versions -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (QPIDIT-95) update to use the current v18 apache parent pom
[ https://issues.apache.org/jira/browse/QPIDIT-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet reopened QPIDIT-95: > update to use the current v18 apache parent pom > --- > > Key: QPIDIT-95 > URL: https://issues.apache.org/jira/browse/QPIDIT-95 > Project: Apache QPID Interoperability Test Suite > Issue Type: Improvement > Components: Installation, Qpid Jms Shim >Affects Versions: 0.1.0 >Reporter: Robbie Gemmell >Priority: Major > > update to use the current v18 apache parent pom to better align with all the > other components, aiding in consistent use of plugin versions -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDIT-88) Need to specify supported AMQP types per shim
[ https://issues.apache.org/jira/browse/QPIDIT-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPIDIT-88: --- Fix Version/s: 0.1.0 > Need to specify supported AMQP types per shim > - > > Key: QPIDIT-88 > URL: https://issues.apache.org/jira/browse/QPIDIT-88 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug >Reporter: Chuck Rolke >Priority: Major > Fix For: 0.1.0 > > > The AMQP.Net Lite (Lite) shim does not support any of the AMQP Decimal types. > Tests may be run with _--exclude-type decimal128 --exclude-type decimal64 > --exclude-type decimal32_ to avoid the failures but that applies to all > sender/receiver shim pairs and not just to the Lite shim. > When the test runs Lite Sender against Lite Receiver it fails in a reasonable > amout of time. But with Lite Sender and ProtonCpp Receiver the test times out > after 800 seconds before failing. The Lite Sender throws right away but the > Cpp Receiver waits dutifully for the message stream. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-90) AmqpNetLite large content shims fail in interop test but work standalone
[
https://issues.apache.org/jira/browse/QPIDIT-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet closed QPIDIT-90.
--
> AmqpNetLite large content shims fail in interop test but work standalone
>
>
> Key: QPIDIT-90
> URL: https://issues.apache.org/jira/browse/QPIDIT-90
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: .Net Lite Shim, AMQP Large Content Test
> Environment: Fedora 25;
> Mono JIT compiler version 4.4.2 (Stable 4.4.2.11/f72fe45 Tue Aug 2 08:14:37
> UTC 2016);
> Python 2.7.13
> Intermediary: Qpid-Dispatch router, master branch 20170818.
>Reporter: Chuck Rolke
>Priority: Major
> Attachments: QPIDIT-90_log-and-conf.txt
>
>
> Large content test fails under the test suite sending any of the five AMQP
> types.
> The amqpnetlite Receiver fails receiving a message:
> {noformat}
> Message message = receiverlink.Receive(200 * 1000);
> {noformat}
> That line should wait 200 seconds for a message but does not.
> The same test code works when run standalone from command prompts.
> The console logs and router configuration file to be attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-88) Need to specify supported AMQP types per shim
[ https://issues.apache.org/jira/browse/QPIDIT-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-88. -- > Need to specify supported AMQP types per shim > - > > Key: QPIDIT-88 > URL: https://issues.apache.org/jira/browse/QPIDIT-88 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug >Reporter: Chuck Rolke >Priority: Major > Fix For: 0.1.0 > > > The AMQP.Net Lite (Lite) shim does not support any of the AMQP Decimal types. > Tests may be run with _--exclude-type decimal128 --exclude-type decimal64 > --exclude-type decimal32_ to avoid the failures but that applies to all > sender/receiver shim pairs and not just to the Lite shim. > When the test runs Lite Sender against Lite Receiver it fails in a reasonable > amout of time. But with Lite Sender and ProtonCpp Receiver the test times out > after 800 seconds before failing. The Lite Sender throws right away but the > Cpp Receiver waits dutifully for the message stream. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-95) update to use the current v18 apache parent pom
[ https://issues.apache.org/jira/browse/QPIDIT-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-95. -- > update to use the current v18 apache parent pom > --- > > Key: QPIDIT-95 > URL: https://issues.apache.org/jira/browse/QPIDIT-95 > Project: Apache QPID Interoperability Test Suite > Issue Type: Improvement > Components: Installation, Qpid Jms Shim >Affects Versions: 0.1.0 >Reporter: Robbie Gemmell >Priority: Major > > update to use the current v18 apache parent pom to better align with all the > other components, aiding in consistent use of plugin versions -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-1) Initial code import
[ https://issues.apache.org/jira/browse/QPIDIT-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-1. - > Initial code import > --- > > Key: QPIDIT-1 > URL: https://issues.apache.org/jira/browse/QPIDIT-1 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Import initial implementation code. This code is experimental in nature and > is designed to give an idea on how to implement this project. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-16) Place Qpid JMS shim build management under Maven
[ https://issues.apache.org/jira/browse/QPIDIT-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-16. -- > Place Qpid JMS shim build management under Maven > > > Key: QPIDIT-16 > URL: https://issues.apache.org/jira/browse/QPIDIT-16 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Currently, the Qpid JMS shim builds using a bash script which calls javac > directly. There is no install script. Jars dependencies not already handled > by Maven elsewhere are located in a local jars folder. > As other Qpid Java projects use Maven to manage jars dependencies, builds and > installs, it makes sense to use it for this also. This should remove the > need for scripts, and will also make the jars directory disappear. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-2) Add command-line options to control which shims and/or AMQP type combinations to run
[
https://issues.apache.org/jira/browse/QPIDIT-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet closed QPIDIT-2.
-
> Add command-line options to control which shims and/or AMQP type combinations
> to run
>
>
> Key: QPIDIT-2
> URL: https://issues.apache.org/jira/browse/QPIDIT-2
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Task
> Components: AMQP Types Test
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
> Fix For: 0.1.0
>
>
> Currently, simple_type_test accepts {{\-\-exclude-type}} and
> {{\-\-exclude-shim}} command-line arguments to limit the number of tests that
> are run. These arguments subtract from the list of known types and shims
> respectively.
> A comprehensive approach which allows a specific shim/type combinations to be
> specified as well as excluded needs to be developed. For example, using
> {{\-\-include-test }}, {{\-\-include-shim }} and/or
> {{\-\-include-type }} would be mutually exclusive of the
> {{\-\-exclude\-*}} counterparts, and would start with and empty set and
> include only those types listed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-13) Submit patch to Proton for AMQP type support needed by ProtonPython shim
[
https://issues.apache.org/jira/browse/QPIDIT-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet closed QPIDIT-13.
--
> Submit patch to Proton for AMQP type support needed by ProtonPython shim
>
>
> Key: QPIDIT-13
> URL: https://issues.apache.org/jira/browse/QPIDIT-13
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Task
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
> Fix For: 0.1.0
>
>
> This is a tracker task, which will be considered completed when the patch
> referred to below is successfully submitted to the Proton project.
> The Proton Python binding needs to be patched with the file located in
> {{etc/proton-python-amqp-types.patch}} file in git before it can be used with
> the ProtonPython shims. This patch adds support for AMQP types not natively
> supported in Python, and allow a simple mechanism to force the use of a
> specific AMQP type.
> This patch needs to be proposed and submitted to the Qpid Proton sub-project.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-20) Add ability to detect broker, skip tests that fail for that broker
[ https://issues.apache.org/jira/browse/QPIDIT-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-20. -- > Add ability to detect broker, skip tests that fail for that broker > -- > > Key: QPIDIT-20 > URL: https://issues.apache.org/jira/browse/QPIDIT-20 > Project: Apache QPID Interoperability Test Suite > Issue Type: Improvement > Components: AMQP Types Test, JMS Message Test >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > The Qpid broker will not handle some AMQP types correctly, and will attempt > to read the body of these types as descriptors. This bug covered elsewhere. > However, this issue causes the AMQP tests using these types to fail when the > Qpid broker is in use. However, the A-MQ broker works ok. > Until now, the types that do not work have had to be commented out of the > test before running it in order to complete the test when using Qpid as the > broker. This is ugly and error-prone, and certainly does not lend itself to > automatic testing environments. > A method needs to be devised that can detect the broker in use, and > automatically exclude or skip tests that are known to fail with an > appropriate message. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
***UNCHECKED*** [jira] [Closed] (QPIDIT-17) Add JMS test suite
[ https://issues.apache.org/jira/browse/QPIDIT-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-17. -- > Add JMS test suite > -- > > Key: QPIDIT-17 > URL: https://issues.apache.org/jira/browse/QPIDIT-17 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task > Components: JMS Message Test >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > The existing test, the Simple Type Test is centred around the AMQP 1.0 simple > types, and is designed to send AMQP types between clients to check > interoperability. > However, in the world of JMS, this approach is not ideal, as there is no > direct mapping between JMS message types and AMQP simple types. The idea is > to add another test, which is centred around the five basic JMS message types > rather than the AMQP types. This will allow these message types to drive the > test values rather than the AMQP types, and will provide a more efficient > mechanism for testing JMS interoperability between clients. While it may be > possible to test between non-JMS clients, it makes sense that one or more JMS > clients (such as qpid-jms) always be one of the two test clients. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-22) Add ability to run on Jenkins CI
[ https://issues.apache.org/jira/browse/QPIDIT-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-22. -- > Add ability to run on Jenkins CI > > > Key: QPIDIT-22 > URL: https://issues.apache.org/jira/browse/QPIDIT-22 > Project: Apache QPID Interoperability Test Suite > Issue Type: Improvement >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Run the tests on Jenkins continuous integration system. For this to be > realized, the location of dependent components needs to be parameterized, as > they can no longer be in the usual installed locations. This includes: > * qpid-proton > * qpid-jms -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-18) Use existing structured text representation standard for communicating between test and shims
[ https://issues.apache.org/jira/browse/QPIDIT-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-18. -- > Use existing structured text representation standard for communicating > between test and shims > - > > Key: QPIDIT-18 > URL: https://issues.apache.org/jira/browse/QPIDIT-18 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > The passing of structured data between the test framework and the shims on > the command-line is currently using a python-like format which is > hand-encoded in the various shims. However, a more standard format (such as > JSON) which has library support in many target languages would remove an > entire layer of potential bugs and testing would be beneficial. > I propose replacing the current hand-encoded implementation in the test > framework and in the Python and JMS shims with JSON. Comments on this choice > and the suitability of other potential libs is welcome. I hope to start a > thread on this topic. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-21) Add shims for C++ client
[ https://issues.apache.org/jira/browse/QPIDIT-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-21. -- > Add shims for C++ client > > > Key: QPIDIT-21 > URL: https://issues.apache.org/jira/browse/QPIDIT-21 > Project: Apache QPID Interoperability Test Suite > Issue Type: New Feature > Components: AMQP Types Test, JMS Message Test, Proton C++ Shim >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Add a set of shims for the Proton C++ client: > * Sender for SimpeTypeTest > * Receiver for SimpleTypeTest > * Sender for JmsMessageTest > * Receiver for JmsMessageTest -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-24) Broker identification failure blocks tests
[ https://issues.apache.org/jira/browse/QPIDIT-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-24. -- > Broker identification failure blocks tests > -- > > Key: QPIDIT-24 > URL: https://issues.apache.org/jira/browse/QPIDIT-24 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug > Components: AMQP Types Test, JMS Message Test >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Both the AMQP type test and the JMS message test use a small Python script to > connect to the broker and retrieve the connection properties, among which are > the broker name and version. > The broker name is used to skip tests depending on the broker being used in > the test. The broker product name is used for this purpose. If the process > of retrieving the connection properties fails for any reason, then the test > does not run, but exits with an error message. This behavior needs to be > changed such that the test will run but no test skipping will take place. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-25) Change shim architecture to accomodate non-queueing brokers
[ https://issues.apache.org/jira/browse/QPIDIT-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-25. -- > Change shim architecture to accomodate non-queueing brokers > --- > > Key: QPIDIT-25 > URL: https://issues.apache.org/jira/browse/QPIDIT-25 > Project: Apache QPID Interoperability Test Suite > Issue Type: Improvement > Components: Proton Python Shim, Qpid Jms Shim >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > > Some brokers do not supply queuing capabilities. For such brokers, it is > necessary to first open a consumer or listener before sending test data. This > will allow messages to be buffered locally rather than on the broker. > Change the architecture of the shims such that the receiver is started first, > and then later processed for buffered messages. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-32) Use Maven to build Java components
[ https://issues.apache.org/jira/browse/QPIDIT-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-32. -- > Use Maven to build Java components > -- > > Key: QPIDIT-32 > URL: https://issues.apache.org/jira/browse/QPIDIT-32 > Project: Apache QPID Interoperability Test Suite > Issue Type: Improvement >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > Attachments: 0001-QPIDIT-32-misc-improvements-for-the-new-poms.patch > > > Currently the Java components are built using copies of dependent jar files > in the jar directory and some simple bash scripts invoking javac and jar. > Upgrade this so that dependency management and classpath management as well > as the java builds are more robustly maintained using Apache Maven (which is > a trend already established in other Qpid projects). -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
***UNCHECKED*** [jira] [Closed] (QPIDIT-35) Add Dispatch Router to Jenkins CI
[ https://issues.apache.org/jira/browse/QPIDIT-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-35. -- > Add Dispatch Router to Jenkins CI > - > > Key: QPIDIT-35 > URL: https://issues.apache.org/jira/browse/QPIDIT-35 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task > Components: AMQP Types Test, JMS Message Test >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > > Add a pair of tasks to Jenkins CI: > * Build Dispatch Router from git checkout of master > * Add tests for AMQP types and JMS messages to use Dispatch Router as a broker > Dispatch Router can be configured in both brokerless and multiple brokered > topologies. The tests need to run against both of these configurations. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-34) Update to jsoncpp text format has broken test harness for all C++ shims
[ https://issues.apache.org/jira/browse/QPIDIT-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-34. -- > Update to jsoncpp text format has broken test harness for all C++ shims > --- > > Key: QPIDIT-34 > URL: https://issues.apache.org/jira/browse/QPIDIT-34 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug > Components: Proton C++ Shim >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > An update to the jsoncpp package has removed the trailing '\n' char from > output of a JSON map. The Python test control program removes the last char > from the received string without testing for the presence of '\n', and this > causes an error when trying to parse the string. > This error affects all C++ shims. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
***UNCHECKED*** [jira] [Closed] (QPIDIT-47) Add Rhea javascript shim for AMQP types test
[ https://issues.apache.org/jira/browse/QPIDIT-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-47. -- > Add Rhea javascript shim for AMQP types test > > > Key: QPIDIT-47 > URL: https://issues.apache.org/jira/browse/QPIDIT-47 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task > Components: AMQP Types Test, Rhea JavaScript Shim >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Add a send and receive shim for the Rhea AMQP javascript client -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
***UNCHECKED*** [jira] [Assigned] (QPID-8085) [Broker-J][AMQP 1.0] Optimize the sending of flow performatives from broker sending link endpoint
[ https://issues.apache.org/jira/browse/QPID-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-8085: Assignee: (was: Alex Rudyy) > [Broker-J][AMQP 1.0] Optimize the sending of flow performatives from broker > sending link endpoint > - > > Key: QPID-8085 > URL: https://issues.apache.org/jira/browse/QPID-8085 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.0 >Reporter: Alex Rudyy >Priority: Major > > The broker sending link endpoint sends flow performatives when more than > half of the credits issued by receiving link endpoint is used. Such behaviour > is spec compliant, though, it might effect the messaging throughput as the > unnecessary flows consume bandwidth and might impact the performance. > We can simply restrict the sending link endpoint to send flow only in reply > to incoming flows with echo= true or drain=true. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-33) Add JMS message headers and properties to test suite
[ https://issues.apache.org/jira/browse/QPIDIT-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-33. -- > Add JMS message headers and properties to test suite > > > Key: QPIDIT-33 > URL: https://issues.apache.org/jira/browse/QPIDIT-33 > Project: Apache QPID Interoperability Test Suite > Issue Type: Improvement > Components: JMS Message Test, Proton C++ Shim, Proton Python Shim, > Qpid Jms Shim >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Currently, the JMS message tests do not support message headers or properties > as a part of the test, only message bodies are tested. This enhancement will > add combinations of message headers and properties to the message bodies and > check that these are correctly sent and received. It should also check for > those properties that should be set by the client publish method. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-36) Allow receiver and sender to operate concurrently for operation against Dispatch Router
[ https://issues.apache.org/jira/browse/QPIDIT-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-36. -- > Allow receiver and sender to operate concurrently for operation against > Dispatch Router > --- > > Key: QPIDIT-36 > URL: https://issues.apache.org/jira/browse/QPIDIT-36 > Project: Apache QPID Interoperability Test Suite > Issue Type: Sub-task > Components: AMQP Types Test, JMS Message Test >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Currently the test framework is a single-threaded program which first sends > test messages by executing the send shim, then receives them by executing the > receive shim. This will work as long as the broker can store messages in > queues until the receive shim can retrieve them. > When testing against the Dispatch Router in a brokerless configuration, there > is no entity which can store-and-forward messages. For this case, it is > necessary that the receiver is first started, and while it is running, the > sender then sends messages. This requires concurrent execution of both shims. > The test frameworks need to be modified to allow for the concurrent execution > of both shims. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
***UNCHECKED*** [jira] [Updated] (QPID-8085) [Broker-J][AMQP 1.0] Optimize the sending of flow performatives from broker sending link endpoint
[ https://issues.apache.org/jira/browse/QPID-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8085: - Status: Reviewable (was: In Progress) > [Broker-J][AMQP 1.0] Optimize the sending of flow performatives from broker > sending link endpoint > - > > Key: QPID-8085 > URL: https://issues.apache.org/jira/browse/QPID-8085 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.0 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > > The broker sending link endpoint sends flow performatives when more than > half of the credits issued by receiving link endpoint is used. Such behaviour > is spec compliant, though, it might effect the messaging throughput as the > unnecessary flows consume bandwidth and might impact the performance. > We can simply restrict the sending link endpoint to send flow only in reply > to incoming flows with echo= true or drain=true. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
***UNCHECKED*** [jira] [Assigned] (QPID-8085) [Broker-J][AMQP 1.0] Optimize the sending of flow performatives from broker sending link endpoint
[ https://issues.apache.org/jira/browse/QPID-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-8085: Assignee: Alex Rudyy > [Broker-J][AMQP 1.0] Optimize the sending of flow performatives from broker > sending link endpoint > - > > Key: QPID-8085 > URL: https://issues.apache.org/jira/browse/QPID-8085 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.0 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > > The broker sending link endpoint sends flow performatives when more than > half of the credits issued by receiving link endpoint is used. Such behaviour > is spec compliant, though, it might effect the messaging throughput as the > unnecessary flows consume bandwidth and might impact the performance. > We can simply restrict the sending link endpoint to send flow only in reply > to incoming flows with echo= true or drain=true. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-38) Artemis broker-added properties not handled correctly in python receive shim
[ https://issues.apache.org/jira/browse/QPIDIT-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-38. -- > Artemis broker-added properties not handled correctly in python receive shim > > > Key: QPIDIT-38 > URL: https://issues.apache.org/jira/browse/QPIDIT-38 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug > Components: Proton Python Shim >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > The Artemis broker adds properties to messages that were not on the sent > message. Thus, received messages cannot be assumed to have only the > properties with which they were sent. The python receive shim is not handling > this correctly and fails when it encounters an Artemis-added property. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
***UNCHECKED*** [jira] [Commented] (QPID-8085) [Broker-J][AMQP 1.0] Optimize the sending of flow performatives from broker sending link endpoint
[ https://issues.apache.org/jira/browse/QPID-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341305#comment-16341305 ] ASF subversion and git services commented on QPID-8085: --- Commit 667609be6186841d43af43fd88eb6172299667f8 in qpid-broker-j's branch refs/heads/master from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=667609b ] QPID-8085: [Broker-J] Send flow in response to drain request even when credit is 0 > [Broker-J][AMQP 1.0] Optimize the sending of flow performatives from broker > sending link endpoint > - > > Key: QPID-8085 > URL: https://issues.apache.org/jira/browse/QPID-8085 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.0 >Reporter: Alex Rudyy >Priority: Major > > The broker sending link endpoint sends flow performatives when more than > half of the credits issued by receiving link endpoint is used. Such behaviour > is spec compliant, though, it might effect the messaging throughput as the > unnecessary flows consume bandwidth and might impact the performance. > We can simply restrict the sending link endpoint to send flow only in reply > to incoming flows with echo= true or drain=true. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
***UNCHECKED*** [jira] [Updated] (QPIDIT-109) Add ability to run Proton Python shims under Python 3
[ https://issues.apache.org/jira/browse/QPIDIT-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPIDIT-109: Fix Version/s: 0.2.0 > Add ability to run Proton Python shims under Python 3 > - > > Key: QPIDIT-109 > URL: https://issues.apache.org/jira/browse/QPIDIT-109 > Project: Apache QPID Interoperability Test Suite > Issue Type: Improvement >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.2.0 > > > Currently the shims run under Python 2.7, so add Python 3 as additional shim > type. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDIT-106) Cmake does not find custom-installed maven
[
https://issues.apache.org/jira/browse/QPIDIT-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet updated QPIDIT-106:
Fix Version/s: 0.2.0
> Cmake does not find custom-installed maven
> --
>
> Key: QPIDIT-106
> URL: https://issues.apache.org/jira/browse/QPIDIT-106
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: Installation
>Affects Versions: 0.1.0
> Environment: RHEL7, CentOS7
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
> Fix For: 0.2.0
>
>
> When building qpid-interop-test on a platform where Maven is custom-installed
> directly from the Apache web site (owing to the packaged version being too
> early a version to work), the installed {{mvn}} command is not found by the
> installer and installation is aborted.
> This occurs where maven is installed into a custom location such as
> {{/usr/local/maven}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8085) [Broker-J][AMQP 1.0] Optimize the sending of flow performatives from broker sending link endpoint
[ https://issues.apache.org/jira/browse/QPID-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341304#comment-16341304 ] ASF subversion and git services commented on QPID-8085: --- Commit c49dc0f473c6e727caa1143cb155774607bc23a2 in qpid-broker-j's branch refs/heads/master from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=c49dc0f ] QPID-8085: [Broker-J][AMQP 1.0] Optimize the sending of flow performatives from broker sending link endpoint > [Broker-J][AMQP 1.0] Optimize the sending of flow performatives from broker > sending link endpoint > - > > Key: QPID-8085 > URL: https://issues.apache.org/jira/browse/QPID-8085 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.0 >Reporter: Alex Rudyy >Priority: Major > > The broker sending link endpoint sends flow performatives when more than > half of the credits issued by receiving link endpoint is used. Such behaviour > is spec compliant, though, it might effect the messaging throughput as the > unnecessary flows consume bandwidth and might impact the performance. > We can simply restrict the sending link endpoint to send flow only in reply > to incoming flows with echo= true or drain=true. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPIDIT-65) Add command-line controls to JMS_hdrs_props_test to control test more precisely
[
https://issues.apache.org/jira/browse/QPIDIT-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet resolved QPIDIT-65.
Resolution: Fixed
> Add command-line controls to JMS_hdrs_props_test to control test more
> precisely
> ---
>
> Key: QPIDIT-65
> URL: https://issues.apache.org/jira/browse/QPIDIT-65
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Improvement
> Components: JMS Headers and Properties Test
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Minor
> Fix For: 0.2.0
>
>
> The JMS hdrs_props_test needs additional command-line parameters to control
> the test precisely. Since the test by default uses only the JMS_MESSAGE_TYPE
> for this test, the --{include, exclude}-type paramter has no effect at
> present, but should be used to change/modify the base message type. In
> addition, a parameter switching on/off the headers and parameters is needed,
> also a control for the type of header and type of parameters used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-94) Does not install correctly on Python 2.6 (used by early versions of RHEL)
[ https://issues.apache.org/jira/browse/QPIDIT-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-94. -- > Does not install correctly on Python 2.6 (used by early versions of RHEL) > - > > Key: QPIDIT-94 > URL: https://issues.apache.org/jira/browse/QPIDIT-94 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > > The install scripts have Python 2.7 hard-coded into the paths. This is > causing parts of the install to fail. The correct python path needs to be > detected and used for installation. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-42) Split JMS message test into two separate tests: message bodies, and message headers/properties
[ https://issues.apache.org/jira/browse/QPIDIT-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-42. -- > Split JMS message test into two separate tests: message bodies, and message > headers/properties > -- > > Key: QPIDIT-42 > URL: https://issues.apache.org/jira/browse/QPIDIT-42 > Project: Apache QPID Interoperability Test Suite > Issue Type: Improvement > Components: JMS Headers and Properties Test, JMS Message Test, Qpid > Jms Shim >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > The current JMS messages test includes both JMS message bodies and JMS > message headers and properties. The test is structured in a way that all the > headers and properties test run on each of the JMS body combinations. This > results in an excessively long test, and does not improve coverage. > By splitting the tests into a separate JMS message test and JMS > headers/properties test, this problem can be eliminated. The message test > will be far shorter and can specialize its tests for message bodies; > similarly the headers/properties test can also specialize. Any expansion of > the number of tests won't result in a massive increase in the number of tests > that run (as is currently the case). -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (QPIDIT-65) Add command-line controls to JMS_hdrs_props_test to control test more precisely
[
https://issues.apache.org/jira/browse/QPIDIT-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet reopened QPIDIT-65:
Accidentally closed
> Add command-line controls to JMS_hdrs_props_test to control test more
> precisely
> ---
>
> Key: QPIDIT-65
> URL: https://issues.apache.org/jira/browse/QPIDIT-65
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Improvement
> Components: JMS Headers and Properties Test
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Minor
> Fix For: 0.2.0
>
>
> The JMS hdrs_props_test needs additional command-line parameters to control
> the test precisely. Since the test by default uses only the JMS_MESSAGE_TYPE
> for this test, the --{include, exclude}-type paramter has no effect at
> present, but should be used to change/modify the base message type. In
> addition, a parameter switching on/off the headers and parameters is needed,
> also a control for the type of header and type of parameters used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-40) Sender and Receiver threads don't stop when tests end in some error conditions
[ https://issues.apache.org/jira/browse/QPIDIT-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-40. -- > Sender and Receiver threads don't stop when tests end in some error conditions > -- > > Key: QPIDIT-40 > URL: https://issues.apache.org/jira/browse/QPIDIT-40 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > In some tests, a failure either in the client under test or in the test > harness itself can result in one or both of the client shims failing to stop > because they are waiting indefinitely for the test conditions to be met (such > as receiving the required number of messages, or receiving send confirmations > for sent messages). The multi-threaded approach recently added to allow for > brokerless agents such as qpid dispatch router mean that waiting for the send > and receive threads to join is no longer sufficient, and threads that are > still running must be terminated or killed. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-52) Make qpid-interop-test installable
[ https://issues.apache.org/jira/browse/QPIDIT-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-52. -- > Make qpid-interop-test installable > -- > > Key: QPIDIT-52 > URL: https://issues.apache.org/jira/browse/QPIDIT-52 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > The qpid-interop-test suite is not installable. Making it so will make it > easy for users to use against a variety of brokers in a variety of different > platforms. > The install should follow normal Python install procedures and locations as > it is primarily a Python program. The shims, although written in a variety of > different languages, are primarily required resources for the main Python > test programs. Hence they should be installed accordingly. > Local and system installs should be possible. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-41) Rearrange test directory structure to better organize tests and shims
[
https://issues.apache.org/jira/browse/QPIDIT-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet closed QPIDIT-41.
--
> Rearrange test directory structure to better organize tests and shims
> -
>
> Key: QPIDIT-41
> URL: https://issues.apache.org/jira/browse/QPIDIT-41
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Improvement
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
> Fix For: 0.1.0
>
>
> The current directory structure for qpid-interop-test needs some improvements
> to make it more consistent and easier to manage shims and tests:
> * All tests should reside in the same directory
> (src/python/qpid-interop-test), and the test name is the key to the shims
> directory structure for finding the Sender and Receiver shims.
> * JMS shims should be located in a directory named identically to the name of
> the test for which it is written, and located in
> shims/qpid-jms/src/main/java/org/apace/qpid/qpid_interop_test. There are only
> two shims, called Sender.java and Receiver.java. The Java package is
> consequently "org.apache.qpid.interop_test..
> * Python shims should be located in a directory named identically to the name
> of the test for which it is written, and located in
> shims/qpid-proton-python/src. There are only two shims, called Sender.py and
> Receiver.py.
> * C++ shims should be located in a directory named identically to the name of
> the test for which it is written, and located in
> shims/qpid-proton-cpp/src/qpidit. There are only two shims, called
> Sender.{hpp,cpp} and Receiver.{hpp,cpp}. The shim namespace is conseqnently
> qpidit..
> {noformat}
> qpid-interop-test
> +-shims
> | +-qpid-jms
> | | +-src
> | | +-main
> | | +-java
> | | +-org
> | | +-apache
> | | +-qpid
> | | +-qpid-interop-test
> | | +-
> | | | +-Receiver.java
> | | | +-Sender.java
> | | +-
> | | +-Receiver.java
> | | +-Sender.java
> | +-qpid-proton-cpp
> | | +-src
> | | +-qpidit
> | | +-
> | | | +- Receiver.cpp
> | | | +- Receiver.hpp
> | | | +- Sender.cpp
> | | | +- Sender.hpp
> | | +-
> | | +- Receiver.cpp
> | | +- Receiver.hpp
> | | +- Sender.cpp
> | | +- Sender.hpp
> | +-qpid-proton-python
> | +-src
> | +-
> | | +-Sender.py
> | | +-Receiver.py
> | +-
> | +-Sender.py
> | +-Receiver.py
> +-src
> +-python
> +-qpid-interop-test
> +-
> +-
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-53) Eliminate use of authentication when collecting broker connection properties
[ https://issues.apache.org/jira/browse/QPIDIT-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-53. -- > Eliminate use of authentication when collecting broker connection properties > > > Key: QPIDIT-53 > URL: https://issues.apache.org/jira/browse/QPIDIT-53 > Project: Apache QPID Interoperability Test Suite > Issue Type: Improvement >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > Attachments: QPIDIT-53-01.patch > > > When the tests use the broker_properties.py module to read the broker > connection properties, it uses anonymous authentication. The rest of the test > does not use authentication. > To bring the test to a uniform non-use of authentication, this should be > disabled for this module. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-48) Add test options which allow separate addresses for the sender and receiver
[ https://issues.apache.org/jira/browse/QPIDIT-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-48. -- > Add test options which allow separate addresses for the sender and receiver > --- > > Key: QPIDIT-48 > URL: https://issues.apache.org/jira/browse/QPIDIT-48 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task > Components: AMQP Distributed Transactions Test, AMQP Features Test, > AMQP Large Content Test, AMQP Types Test, JMS Headers and Properties Test, > JMS Message Test >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > For tests which use the dispatch router, it is possible for the sender and > receiver to use separate nodes (and hence use separate addresses). Add > command-line options for sender-addr and receiver-addr. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-44) Add AMQP large content test
[ https://issues.apache.org/jira/browse/QPIDIT-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-44. -- > Add AMQP large content test > --- > > Key: QPIDIT-44 > URL: https://issues.apache.org/jira/browse/QPIDIT-44 > Project: Apache QPID Interoperability Test Suite > Issue Type: New Feature > Components: AMQP Large Content Test >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Add a test for large message content in AMQP messages. The large content > needs to be in both the message body (for types that have variable size > capabilities) and applicable message headers and properties. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-57) Cmake installer should check for presence of Node.js and Rhea client
[ https://issues.apache.org/jira/browse/QPIDIT-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-57. -- > Cmake installer should check for presence of Node.js and Rhea client > > > Key: QPIDIT-57 > URL: https://issues.apache.org/jira/browse/QPIDIT-57 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug > Components: Installation >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Currently the presence of both node.js and Rhea are assumed. The cmake > installer should check for the presence of node.js, and if that is present, > then for Rhea itself. If found, then the Rhea tests should be enabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-60) Create a HOWTO file on writing a new test
[ https://issues.apache.org/jira/browse/QPIDIT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-60. -- > Create a HOWTO file on writing a new test > - > > Key: QPIDIT-60 > URL: https://issues.apache.org/jira/browse/QPIDIT-60 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task > Components: Documentation >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Write a HOWTO file which lays out the steps in writing a new test. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-59) Create a HOWTO file on writing a new shim
[ https://issues.apache.org/jira/browse/QPIDIT-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-59. -- > Create a HOWTO file on writing a new shim > - > > Key: QPIDIT-59 > URL: https://issues.apache.org/jira/browse/QPIDIT-59 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task > Components: Documentation >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Create a file which lays out how to write a shim. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-65) Add command-line controls to JMS_hdrs_props_test to control test more precisely
[
https://issues.apache.org/jira/browse/QPIDIT-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet closed QPIDIT-65.
--
> Add command-line controls to JMS_hdrs_props_test to control test more
> precisely
> ---
>
> Key: QPIDIT-65
> URL: https://issues.apache.org/jira/browse/QPIDIT-65
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Improvement
> Components: JMS Headers and Properties Test
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Minor
> Fix For: 0.2.0
>
>
> The JMS hdrs_props_test needs additional command-line parameters to control
> the test precisely. Since the test by default uses only the JMS_MESSAGE_TYPE
> for this test, the --{include, exclude}-type paramter has no effect at
> present, but should be used to change/modify the base message type. In
> addition, a parameter switching on/off the headers and parameters is needed,
> also a control for the type of header and type of parameters used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-66) Shims should install into a libexec directory, not into the Python site-packages path
[ https://issues.apache.org/jira/browse/QPIDIT-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-66. -- > Shims should install into a libexec directory, not into the Python > site-packages path > - > > Key: QPIDIT-66 > URL: https://issues.apache.org/jira/browse/QPIDIT-66 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug > Components: Installation >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Currently, the shims are installed into a shims subdirectory in the Python > install path for qpid_interop_test. This is not a standard install convention > or location and will cause confusion for users. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-67) Compile errors after recent header cleanup in Proton C++ bindings
[ https://issues.apache.org/jira/browse/QPIDIT-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-67. -- > Compile errors after recent header cleanup in Proton C++ bindings > - > > Key: QPIDIT-67 > URL: https://issues.apache.org/jira/browse/QPIDIT-67 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug > Components: Proton C++ Shim >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > After a recent checkin on Proton's C++ binding which cleans up headers, the > compile of the various C++ shims failed. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-73) Rhea shim char type broken by recent updates to Rhea
[ https://issues.apache.org/jira/browse/QPIDIT-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-73. -- > Rhea shim char type broken by recent updates to Rhea > > > Key: QPIDIT-73 > URL: https://issues.apache.org/jira/browse/QPIDIT-73 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug > Components: Rhea JavaScript Shim >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Recent changes to Rhea have changed the way AMQP char types are handled. The > Rhea shims do not align with the new method of handling char types. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-69) JMS tests fail with "Import Error: no module names jms_types"
[ https://issues.apache.org/jira/browse/QPIDIT-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-69. -- > JMS tests fail with "Import Error: no module names jms_types" > - > > Key: QPIDIT-69 > URL: https://issues.apache.org/jira/browse/QPIDIT-69 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug > Components: JMS Headers and Properties Test, JMS Message Test >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Recent installs of qpid-interop-test do not run the JMS tests correctly, as > every test fails with "Import Error: no module names jms_types". > An initial investigation shows that jms_types.py is missing from the > installed directory. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-82) JMS tests fail intermittently with null message
[
https://issues.apache.org/jira/browse/QPIDIT-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet closed QPIDIT-82.
--
> JMS tests fail intermittently with null message
> ---
>
> Key: QPIDIT-82
> URL: https://issues.apache.org/jira/browse/QPIDIT-82
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: JMS Headers and Properties Test, JMS Message Test
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
> Fix For: 0.1.0
>
>
> Running the JMS tests sometimes results in one or two tests failing with the
> following:
> {noformat}
> AssertionError: JMS message body error:
> sent:{'none': [None]}
> received:{u'none': []}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
***UNCHECKED*** [jira] [Closed] (QPIDIT-84) Update README, QUICKSTART, add a users' guide
[ https://issues.apache.org/jira/browse/QPIDIT-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-84. -- > Update README, QUICKSTART, add a users' guide > - > > Key: QPIDIT-84 > URL: https://issues.apache.org/jira/browse/QPIDIT-84 > Project: Apache QPID Interoperability Test Suite > Issue Type: Improvement > Components: Documentation >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
***UNCHECKED*** [jira] [Closed] (QPIDIT-83) JAVA classpath points to maven repository rather than installed location
[ https://issues.apache.org/jira/browse/QPIDIT-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-83. -- > JAVA classpath points to maven repository rather than installed location > > > Key: QPIDIT-83 > URL: https://issues.apache.org/jira/browse/QPIDIT-83 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug > Components: Installation >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > After installation, a copy of the jars are installed both to the target > location and the maven repository. The classpath is using the maven > repository path first, and causing the Qpid JMS shims to be run from this > location rather than from the installed location. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-97) Release qpid-interop-test 0.1.0
[ https://issues.apache.org/jira/browse/QPIDIT-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-97. -- > Release qpid-interop-test 0.1.0 > --- > > Key: QPIDIT-97 > URL: https://issues.apache.org/jira/browse/QPIDIT-97 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Release qpid-interop-test version 0.1.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-96) Improvements in Java component management
[ https://issues.apache.org/jira/browse/QPIDIT-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPIDIT-96. -- > Improvements in Java component management > - > > Key: QPIDIT-96 > URL: https://issues.apache.org/jira/browse/QPIDIT-96 > Project: Apache QPID Interoperability Test Suite > Issue Type: Improvement > Components: Installation >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.1.0 > > > Robbie Gemmell has pointed out that there are some issues around handling of > the Java components in the pom files, also in the QUICKSTART.md instructions. > The instructions should not instruct the local build of qpid-jms, rather rely > on Maven to find the artifacts it needs. > The dependencies in the jms shim pom file should be moved to the project pom > file, and use properties to define the version numbers, this allows for the > versions of artifacts to be modified from the command-line. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-98) Change Proton C++ Receiver shims to use latest non-deprecated API calls
[
https://issues.apache.org/jira/browse/QPIDIT-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet closed QPIDIT-98.
--
> Change Proton C++ Receiver shims to use latest non-deprecated API calls
> ---
>
> Key: QPIDIT-98
> URL: https://issues.apache.org/jira/browse/QPIDIT-98
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Improvement
> Components: Proton C++ Shim
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Minor
> Fix For: 0.1.0
>
>
> After recent updates to the Proton C++, calls to {{proton::value::get<>()}}
> are deprecated with warnings. Change the code to use the recommended
> {{proton::get<>()}} calls instead.
> There is also a possibility that the use of {{proton::default_container}} is
> also deprecated, but it is currently not producing a warning.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-61) Condense common code from the Python tests into a test module.
[
https://issues.apache.org/jira/browse/QPIDIT-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341274#comment-16341274
]
Kim van der Riet commented on QPIDIT-61:
The above commit did some major refactoring in the (currently) 4 tests. A new
module {{qit_common}} was created, and the following were placed into it which
is common between the test classes:
{{QitTestTypeMap}} which was previously in module test_type_map, is a parent
class for the test values used in a test;
{{QitCommonTestOptions}} contains the command-line options common to all tests;
{{QitTestCase}} contains the abstract parent class for all QIT test cases. It
adds methods which record the time taken for each test case;
{{QitTest}} is the abstract base class for the test itself. It handles common
pre-test tasks such as creating the shim map, creating the argparse object,
modifying the shim map if needed depending on the options selected, and
detecting the broker connection properties to identify the broker.
{{QitJmsTest}} is a specialized version of {{QitTest}} which also sets up a
Java classpath and handles shims which are embedded in a jar.
> Condense common code from the Python tests into a test module.
> --
>
> Key: QPIDIT-61
> URL: https://issues.apache.org/jira/browse/QPIDIT-61
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Task
> Components: AMQP Large Content Test, AMQP Types Test, JMS Headers
> and Properties Test, JMS Message Test
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Minor
>
> Each test was written independently of the others. While this is a quick way
> to start, it has not lead to a lot of duplicated code and common patterns. It
> would help maintenance and readability of the code if the common bits were
> placed into a test library.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-61) Condense common code from the Python tests into a test module.
[
https://issues.apache.org/jira/browse/QPIDIT-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341263#comment-16341263
]
Kim van der Riet commented on QPIDIT-61:
Commit 58a8b9ae47cecfc9cb9370ded292be0bc9ec3ffe in qpid-interop-test's branch
refs/heads/master from [~kpvdr]
[ [https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=58a8b9a] ]
QPIDIT-93: Added xUnit logging by using {{--xunit-log}} parameter; Refactoring
of test classes, added {{qpid_interop_test.run_all}} which runs all tests
> Condense common code from the Python tests into a test module.
> --
>
> Key: QPIDIT-61
> URL: https://issues.apache.org/jira/browse/QPIDIT-61
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Task
> Components: AMQP Large Content Test, AMQP Types Test, JMS Headers
> and Properties Test, JMS Message Test
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Minor
>
> Each test was written independently of the others. While this is a quick way
> to start, it has not lead to a lot of duplicated code and common patterns. It
> would help maintenance and readability of the code if the common bits were
> placed into a test library.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-911) Add link and address level counters at the global router level
[ https://issues.apache.org/jira/browse/DISPATCH-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-911: --- Description: Link already has the following counters - presettledCount droppedPresettledCount acceptedCount rejectedCount releasedCount modifiedCount Address already has the following counters deliveriesIngress deliveriesEgress deliveriesTransit 1. Add the above link and address counters to the global router level as well. 2. Add routeContainerDeliveriesEgress and routeContainerDeliveriesIngress as address and global counters 3. Add router memory footprint as a global statistic was: Link already has the following counters - presettledCount droppedPresettledCount acceptedCount rejectedCount releasedCount modifiedCount Address already has the following counters deliveriesIngress deliveriesEgress deliveriesTransit deliveriesToContainer deliveriesFromContainer 1. Add the above link and address counters to the global router level as well. 2. Add routeContainerDeliveriesEgress and routeContainerDeliveriesIngress as address and global counters 3. Add router memory footprint as a global statistic > Add link and address level counters at the global router level > -- > > Key: DISPATCH-911 > URL: https://issues.apache.org/jira/browse/DISPATCH-911 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Management Agent >Affects Versions: 1.0.0 >Reporter: Ernest Allen >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.1.0 > > > Link already has the following counters - > presettledCount > droppedPresettledCount > acceptedCount > rejectedCount > releasedCount > modifiedCount > Address already has the following counters > deliveriesIngress > deliveriesEgress > deliveriesTransit > 1. Add the above link and address counters to the global router level as well. > 2. Add routeContainerDeliveriesEgress and routeContainerDeliveriesIngress as > address and global counters > 3. Add router memory footprint as a global statistic -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8086) [Broker-J] Create tool to permit recovery from QPID-8066
[
https://issues.apache.org/jira/browse/QPID-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy resolved QPID-8086.
--
Resolution: Fixed
The tool implementation looks OK to me, though, it is really a
{{ConfigurationRecordPurger}} rather than {{OrphanConfigurationRecordPurger}},
as it can delete any configuration entry and it does not check whether it is
orphan or not. Potentially, it can be further improved to evaluate the orphan
records based on information stored in the store rather than from command line
arguments {{-targetUuid}}. As it is unlikely, that anyone would ever ran into
the defect, I am ok to leave the implementation as it is.
> [Broker-J] Create tool to permit recovery from QPID-8066
>
>
> Key: QPID-8086
> URL: https://issues.apache.org/jira/browse/QPID-8086
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Keith Wall
>Assignee: Keith Wall
>Priority: Major
> Fix For: qpid-java-broker-7.0.1, qpid-java-6.1.6
>
>
> Defect QPID-8066 has the potential to leave the Broker in a state where it
> cannot be restarted. The recovery phase, on encountering the orphan records,
> throws an exception and this puts the virtualhost into an {{ERROR}} state.
> There is no facility in Broker-J to recover from this short of recreation of
> the virtualhost.
> If the configuration store is backed by JDBC, then a workaround is to connect
> to the database and remove the offending rows. Unfortunately if the
> virtualhost is backed by BDB (for configuration) or BDB HA, the user has no
> convenient way to recover the situation. BDB JE has no command line
> interface so a Java program would have to be written with knowledge of the
> store's structure. The HA case is further complicated by the fact that
> sufficient nodes would have to be available to provide quorum within the
> group.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (QPID-8086) [Broker-J] Create tool to permit recovery from QPID-8066
[
https://issues.apache.org/jira/browse/QPID-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy reopened QPID-8086:
--
> [Broker-J] Create tool to permit recovery from QPID-8066
>
>
> Key: QPID-8086
> URL: https://issues.apache.org/jira/browse/QPID-8086
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Keith Wall
>Assignee: Keith Wall
>Priority: Major
> Fix For: qpid-java-broker-7.0.1, qpid-java-6.1.6
>
>
> Defect QPID-8066 has the potential to leave the Broker in a state where it
> cannot be restarted. The recovery phase, on encountering the orphan records,
> throws an exception and this puts the virtualhost into an {{ERROR}} state.
> There is no facility in Broker-J to recover from this short of recreation of
> the virtualhost.
> If the configuration store is backed by JDBC, then a workaround is to connect
> to the database and remove the offending rows. Unfortunately if the
> virtualhost is backed by BDB (for configuration) or BDB HA, the user has no
> convenient way to recover the situation. BDB JE has no command line
> interface so a Java program would have to be written with knowledge of the
> store's structure. The HA case is further complicated by the fact that
> sufficient nodes would have to be available to provide quorum within the
> group.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8086) [Broker-J] Create tool to permit recovery from QPID-8066
[
https://issues.apache.org/jira/browse/QPID-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341157#comment-16341157
]
Alex Rudyy commented on QPID-8086:
--
Please port the tool into the required branches
> [Broker-J] Create tool to permit recovery from QPID-8066
>
>
> Key: QPID-8086
> URL: https://issues.apache.org/jira/browse/QPID-8086
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Keith Wall
>Assignee: Keith Wall
>Priority: Major
> Fix For: qpid-java-broker-7.0.1, qpid-java-6.1.6
>
>
> Defect QPID-8066 has the potential to leave the Broker in a state where it
> cannot be restarted. The recovery phase, on encountering the orphan records,
> throws an exception and this puts the virtualhost into an {{ERROR}} state.
> There is no facility in Broker-J to recover from this short of recreation of
> the virtualhost.
> If the configuration store is backed by JDBC, then a workaround is to connect
> to the database and remove the offending rows. Unfortunately if the
> virtualhost is backed by BDB (for configuration) or BDB HA, the user has no
> convenient way to recover the situation. BDB JE has no command line
> interface so a Java program would have to be written with knowledge of the
> store's structure. The HA case is further complicated by the fact that
> sufficient nodes would have to be available to provide quorum within the
> group.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-93) Optionally produce xUnit XML report with test results
[
https://issues.apache.org/jira/browse/QPIDIT-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341151#comment-16341151
]
Kim van der Riet commented on QPIDIT-93:
The attached example xUnit file jms_hdrs_props_test.2018-01-26T09-45-29.xml
contains a random single failure with trace obtained from the QpidJms sender
shim.
> Optionally produce xUnit XML report with test results
> -
>
> Key: QPIDIT-93
> URL: https://issues.apache.org/jira/browse/QPIDIT-93
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Jiri Daněk
>Assignee: Kim van der Riet
>Priority: Minor
> Attachments: amqp_types_test.2018-01-26T09-24-24.xml,
> jms_hdrs_props_test.2018-01-26T09-45-29.xml, xunit.xsd
>
>
> Something like the following should do the job. Instead of
> https://pypi.python.org/pypi/unittest-xml-reporting, it might be possible to
> maybe switch from unittest package to py.test, which has xUnit reports built
> in.
> {noformat}
> diff --git a/src/python/qpid_interop_test/jms_messages_test.py
> b/src/python/qpid_interop_test/jms_messages_test.py
> index 3b54510..3b94f3a 100755
> --- a/src/python/qpid_interop_test/jms_messages_test.py
> +++ b/src/python/qpid_interop_test/jms_messages_test.py
> @@ -24,19 +24,17 @@ Module to test JMS message types across different APIs
> from json import dumps
> from os import getenv, path
> +import xmlrunner
> from proton import symbol
> from qpid_interop_test.test_type_map import TestTypeMap
> @@ -302,7 +300,7 @@ class TestOptions(object):
> Class controlling command-line arguments used to control the test.
> """
> def __init__(self, shim_map):
> -parser = argparse.ArgumentParser(description='Qpid-interop AMQP
> client interoparability test suite '
> +parser = argparse.ArgumentParser(description='Qpid-interop AMQP
> client interoperability test suite '
> 'for JMS message types')
> parser.add_argument('--sender', action='store',
> default='localhost:5672', metavar='IP-ADDR:PORT',
> help='Node to which test suite will send
> messages.')
> @@ -313,6 +311,8 @@ class TestOptions(object):
> parser.add_argument('--broker-type', action='store',
> metavar='BROKER_NAME',
> help='Disable test of broker type (using
> connection properties) by specifying the broker' +
> ' name, or "None".')
> +parser.add_argument('--xunit-report-dir', action='store',
> metavar='REPORTS_DIRECTORY',
> +help='Generate xUnit report into
> REPORTS_DIRECTORY/TEST--.xml')
> type_group = parser.add_mutually_exclusive_group()
> type_group.add_argument('--include-type', action='append',
> metavar='JMS_MESSAGE-TYPE',
> help='Name of JMS message type to include.
> Supported types:\n%s' %
> @@ -421,6 +421,7 @@ if __name__ == '__main__':
> TEST_SUITE.addTest(unittest.makeSuite(test_case_class))
>
> # Finally, run all the dynamically created tests
> -RES = unittest.TextTestRunner(verbosity=2).run(TEST_SUITE)
> +#RES = unittest.TextTestRunner(verbosity=2).run(TEST_SUITE) # type:
> unittest.TextTestResult
> +RES = xmlrunner.XMLTestRunner(verbosity=2).run(TEST_SUITE) # type:
> unittest.TextTestResult
> if not RES.wasSuccessful():
> sys.exit(1)
> {noformat}
> The main "problem" seems that each test has completely separate main method
> and builds up options from scratch. Adding this to every test would mean some
> unnecessary duplication. So maybe refactor this somewhat at first? On the
> other hand, there are good reasons to keep the tests simple...
> What do you think?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDIT-93) Optionally produce xUnit XML report with test results
[
https://issues.apache.org/jira/browse/QPIDIT-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet updated QPIDIT-93:
---
Attachment: jms_hdrs_props_test.2018-01-26T09-45-29.xml
> Optionally produce xUnit XML report with test results
> -
>
> Key: QPIDIT-93
> URL: https://issues.apache.org/jira/browse/QPIDIT-93
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Jiri Daněk
>Assignee: Kim van der Riet
>Priority: Minor
> Attachments: amqp_types_test.2018-01-26T09-24-24.xml,
> jms_hdrs_props_test.2018-01-26T09-45-29.xml, xunit.xsd
>
>
> Something like the following should do the job. Instead of
> https://pypi.python.org/pypi/unittest-xml-reporting, it might be possible to
> maybe switch from unittest package to py.test, which has xUnit reports built
> in.
> {noformat}
> diff --git a/src/python/qpid_interop_test/jms_messages_test.py
> b/src/python/qpid_interop_test/jms_messages_test.py
> index 3b54510..3b94f3a 100755
> --- a/src/python/qpid_interop_test/jms_messages_test.py
> +++ b/src/python/qpid_interop_test/jms_messages_test.py
> @@ -24,19 +24,17 @@ Module to test JMS message types across different APIs
> from json import dumps
> from os import getenv, path
> +import xmlrunner
> from proton import symbol
> from qpid_interop_test.test_type_map import TestTypeMap
> @@ -302,7 +300,7 @@ class TestOptions(object):
> Class controlling command-line arguments used to control the test.
> """
> def __init__(self, shim_map):
> -parser = argparse.ArgumentParser(description='Qpid-interop AMQP
> client interoparability test suite '
> +parser = argparse.ArgumentParser(description='Qpid-interop AMQP
> client interoperability test suite '
> 'for JMS message types')
> parser.add_argument('--sender', action='store',
> default='localhost:5672', metavar='IP-ADDR:PORT',
> help='Node to which test suite will send
> messages.')
> @@ -313,6 +311,8 @@ class TestOptions(object):
> parser.add_argument('--broker-type', action='store',
> metavar='BROKER_NAME',
> help='Disable test of broker type (using
> connection properties) by specifying the broker' +
> ' name, or "None".')
> +parser.add_argument('--xunit-report-dir', action='store',
> metavar='REPORTS_DIRECTORY',
> +help='Generate xUnit report into
> REPORTS_DIRECTORY/TEST--.xml')
> type_group = parser.add_mutually_exclusive_group()
> type_group.add_argument('--include-type', action='append',
> metavar='JMS_MESSAGE-TYPE',
> help='Name of JMS message type to include.
> Supported types:\n%s' %
> @@ -421,6 +421,7 @@ if __name__ == '__main__':
> TEST_SUITE.addTest(unittest.makeSuite(test_case_class))
>
> # Finally, run all the dynamically created tests
> -RES = unittest.TextTestRunner(verbosity=2).run(TEST_SUITE)
> +#RES = unittest.TextTestRunner(verbosity=2).run(TEST_SUITE) # type:
> unittest.TextTestResult
> +RES = xmlrunner.XMLTestRunner(verbosity=2).run(TEST_SUITE) # type:
> unittest.TextTestResult
> if not RES.wasSuccessful():
> sys.exit(1)
> {noformat}
> The main "problem" seems that each test has completely separate main method
> and builds up options from scratch. Adding this to every test would mean some
> unnecessary duplication. So maybe refactor this somewhat at first? On the
> other hand, there are good reasons to keep the tests simple...
> What do you think?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
