[jira] [Commented] (QPID-8074) [Qpid JMS AMQP 0-x] Build framework to run JMS client system tests

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-8074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324782#comment-16324782
 ] 

ASF subversion and git services commented on QPID-8074:
---

Commit bd45904717146ab3f2bc18585df658fc61a44d7b in qpid-jms-amqp-0-x's branch 
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms-amqp-0-x.git;h=bd45904 ]

QPID-8074: [JMS AMQP 0-x][System Tests] Copy client specific test 
MessageCompressionTest from Broker-J sources


> [Qpid JMS AMQP 0-x] Build framework to run JMS client system tests
> --
>
> Key: QPID-8074
> URL: https://issues.apache.org/jira/browse/QPID-8074
> Project: Qpid
>  Issue Type: Improvement
>  Components: JMS AMQP 0-x
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>
> A number of JMS AMQP 0-x  client tests exist in Broker-J system test suite. 
> We need to move those tests from Broker-J source tree into JMS AMQP 0-x 
> sources. In order to do so, we need to build a new test framework which would 
> allow us to start Broker-J (and potentially Cpp Broker) and run the system 
> tests against the started broker.
> The test suite should use our virtualhost per test pattern. Check 
> {{BrokerAdmin}} idea in broker system tests.
> One wrinkle would be Java 8 - the tests would need Java 8 to run, even though 
> we want the client to remain Java 7 compatible.
> We could also write a broker admin allowing the tests to be run against the 
> CPPBroker



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-8075) BrokerAgent not working for me

[Justin Ross (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324730#comment-16324730
 ] 

Justin Ross commented on QPID-8075:
---

Note to myself.

{noformat}
[jross@localhost qpid-cpp-ssorj (master)]$ python test.py
('REQUEST', '\x01\x00\x00\x00\x00\x00\x00\x00')
('type', )
('WAIT', '\x01\x00\x00\x00\x00\x00\x00\x00')
('TEST', u'\x01\x00\x00\x00\x00\x00\x00\x00', '==', 
'\x01\x00\x00\x00\x00\x00\x00\x00')
('types', , '==', )
[Queue({u'_schema_id': {u'_package_name': 'org.apache.qpid.broker', 
u'_class_name': 'queue', u'_type': '_data', u'_hash': 
UUID('84ce326e-2cbd-6899-80d7-6267d3327e0f')}, u'_create_ts': 
ulong(1515794503270032316L), u'_delete_ts': ulong(0L), u'_object_id': 
{u'_object_name': 
'org.apache.qpid.broker:queue:59210997-d906-4157-a0f0-15f9ff625231_59210997-d906-4157-a0f0-15f9ff625231-93851ac0-1332-403f-a3bb-e22eae2c53c0',
 u'_agent_epoch': ulong(35L)}, u'_values': {u'unackedMessages': uint(0L), 
u'consumerCountLow': uint(0L), u'byteFtdDequeues': ulong(0L), 
u'discardsOverflow': ulong(0L), u'byteFtdDepth': ulong(0L), u'consumerCount': 
uint(1L), u'byteFtdEnqueues': ulong(0L), u'bytePersistEnqueues': ulong(0L), 
u'discardsPurge': ulong(0L), u'msgFtdEnqueues': ulong(0L), u'msgFtdDequeues': 
ulong(0L), u'discardsRing': ulong(0L), u'flowStoppedCount': uint(0L), 
u'acquires': ulong(0L), u'unackedMessagesHigh': uint(0L), u'autoDelete': True, 
u'redirectPeer': '', u'durable': False, u'creator': 'anonymous', 
u'msgTxnEnqueues': ulong(0L), u'redirectSource': False, u'arguments': {}, 
u'messageLatencyMax': ulong(0L), u'reroutes': ulong(0L), u'exclusive': False, 
u'msgTotalEnqueues': ulong(0L), u'releases': ulong(0L), u'bytePersistDequeues': 
ulong(0L), u'msgTotalDequeues': ulong(0L), u'flowStopped': False, 
u'bindingCountLow': uint(0L), u'vhostRef': {u'_object_name': 
'org.apache.qpid.broker:vhost:org.apache.qpid.broker:broker:amqp-broker,/'}, 
u'bindingCount': uint(1L), u'byteTxnEnqueues': ulong(0L), u'byteDepth': 
ulong(0L), u'msgTxnDequeues': ulong(0L), u'unackedMessagesLow': uint(0L), 
u'messageLatencyMin': int32(0), u'name': 
'59210997-d906-4157-a0f0-15f9ff625231_59210997-d906-4157-a0f0-15f9ff625231-93851ac0-1332-403f-a3bb-e22eae2c53c0',
 u'discardsLvq': ulong(0L), u'consumerCountHigh': uint(1L), 
u'discardsSubscriber': ulong(0L), u'messageLatencyCount': ulong(0L), 
u'msgPersistDequeues': ulong(0L), u'bindingCountHigh': uint(1L), 
u'byteTotalDequeues': ulong(0L), u'msgFtdDepth': ulong(0L), 
u'msgPersistEnqueues': ulong(0L), u'discardsTtl': ulong(0L), 
u'messageLatencyAvg': int32(0), u'byteTotalEnqueues': ulong(0L), u'msgDepth': 
ulong(0L), u'byteTxnDequeues': ulong(0L)}, u'_update_ts': 
ulong(1515794503270866086L)})]
[jross@localhost qpid-cpp-ssorj (master)]$ python3 test.py
REQUEST b'\x01\x00\x00\x00\x00\x00\x00\x00'
type 
WAIT b'\x01\x00\x00\x00\x00\x00\x00\x00'
TEST  == b'\x01\x00\x00\x00\x00\x00\x00\x00'
types  == 
TEST  == b'\x01\x00\x00\x00\x00\x00\x00\x00'
types  == 
Traceback (most recent call last):
  File "test.py", line 4, in 
print(ba.getAllQueues())
  File "/home/jross/code/qpid-cpp-ssorj/management/python/lib/qmf/client.py", 
line 296, in getAllQueues
def getAllQueues(self): return self._getAll(Queue)
  File "/home/jross/code/qpid-cpp-ssorj/management/python/lib/qmf/client.py", 
line 275, in _getAll
return [cls(self, x) for x in self._classQuery(cls.__name__.lower())]
  File "/home/jross/code/qpid-cpp-ssorj/management/python/lib/qmf/client.py", 
line 260, in _classQuery
return self._retry(f)
  File "/home/jross/code/qpid-cpp-ssorj/management/python/lib/qmf/client.py", 
line 221, in _retry
return f(*args, **kwargs)
  File "/home/jross/code/qpid-cpp-ssorj/management/python/lib/qmf/client.py", 
line 256, in f
response = self._request('_query_request', query)
  File "/home/jross/code/qpid-cpp-ssorj/management/python/lib/qmf/client.py", 
line 230, in _request
return self._client.call(Message(body=content, properties=props, 
subject="broker"))
  File "/home/jross/code/qpid-cpp-ssorj/management/python/lib/qmf/client.py", 
line 118, in call
return self.wait(self.send(request))
  File "/home/jross/code/qpid-cpp-ssorj/management/python/lib/qmf/client.py", 
line 143, in wait
self.connection.wait(wakeup, msg="Waiting for response")
  File "/usr/lib64/python3.6/site-packages/proton/utils.py", line 271, in wait
raise Timeout(txt)
proton.Timeout: Connection amqp://localhost:56721 timed out: Waiting for 
response
{noformat}

> BrokerAgent not working for me
> --
>
> Key: QPID-8075
> URL: https://issues.apache.org/jira/browse/QPID-8075
> Project: Qpid
>  Issue Type: Bug
>  Components: QMF
>Affects Versions: qpid-cpp-1.37.0
> Environment: Fedora 25, fully up to date
> via dnf I installed:
> qpid-proton-c-0.17.0-5.fc25.x86_64
> qpid-cpp-server-1.36.0-1.fc25.x86_64
> 

[jira] [Updated] (QPID-8075) BrokerAgent not working for me

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated QPID-8075:
--
Fix Version/s: qpid-cpp-1.38.0

> BrokerAgent not working for me
> --
>
> Key: QPID-8075
> URL: https://issues.apache.org/jira/browse/QPID-8075
> Project: Qpid
>  Issue Type: Bug
>  Components: QMF
>Affects Versions: qpid-cpp-1.37.0
> Environment: Fedora 25, fully up to date
> via dnf I installed:
> qpid-proton-c-0.17.0-5.fc25.x86_64
> qpid-cpp-server-1.36.0-1.fc25.x86_64
> pip freeze in my virtual environment is:
> python-qpid-proton==0.19.0
> qpid-tools==1.37.0
> Note this is with Python 3.5.4
> Note that qpid-tools is a checkout that includes this commit 
> 0ffa89e177346e68bdeb5a24b9f25190c983bd34 because I need it, and the version 
> on PyPI does not include it.
>Reporter: Brian Bouterse
>Assignee: Justin Ross
>Priority: Blocker
> Fix For: qpid-cpp-1.38.0
>
>
> 1. Start qpidd and verify that it starts
> 2. Verify it's listening on 5762 using `sudo netstat -planet | grep 5672`
> 3. Telnet connect to it with `telnet localhost 5672` observe that it connects
> Try to connect it to with qmf.BrokerAgent
> from qmf.client import BrokerAgent, ReconnectDelays
> conn_opts = {'url': 'amqp://localhost:5672'}
> ba = BrokerAgent.connect(**conn_opts)
> ba.getAllQueues()
> I get this exception after 10 seconds:
>   File "/home/vagrant/devel/kombu/kombu/transport/qpid.py", line 586, in 
> exchange_declare
> self._broker.addExchange(type, exchange, options)
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 344, in addExchange
> self._method('create', args)
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 233, in _method
> response = self._retry(self._request, '_method_request', content)
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 215, in _retry
> return f(*args, **kwargs)
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 224, in _request
> return self._client.call(Message(body=content, properties=props, 
> subject="broker"))
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 118, in call
> return self.wait(self.send(request))
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 137, in wait
> self.connection.wait(wakeup, msg="Waiting for response")
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/proton/utils.py",
>  line 292, in wait
> raise Timeout(txt)
> proton.Timeout: Connection amqp://localhost:5672 timed out: Waiting for 
> response
> What is interesting is that on the same system with simply_send.py (the 
> standard example) it connects and sends with the exact same url. I do that 
> with this:
> (pulp) [vagrant@pulp3 devel]$ python simple_send.py --address 
> 'amqp://localhost:5672' -m 1
> all messages confirmed
> The 'all messages confirmed' suggests that everything went fine and the 
> reactor called on_accepted().
> So I conclude that BrokerAgent is somehow fundamentally not working or my 
> environment is screwed up somehow.
> This same commit checkout was working with Python 2.7. I don't have that 
> environment handy currently, but I suspect this is somehow broken with Python 
> 3.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (QPID-8075) BrokerAgent not working for me

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross reassigned QPID-8075:
-

Assignee: Justin Ross

> BrokerAgent not working for me
> --
>
> Key: QPID-8075
> URL: https://issues.apache.org/jira/browse/QPID-8075
> Project: Qpid
>  Issue Type: Bug
>  Components: QMF
>Affects Versions: qpid-cpp-1.37.0
> Environment: Fedora 25, fully up to date
> via dnf I installed:
> qpid-proton-c-0.17.0-5.fc25.x86_64
> qpid-cpp-server-1.36.0-1.fc25.x86_64
> pip freeze in my virtual environment is:
> python-qpid-proton==0.19.0
> qpid-tools==1.37.0
> Note this is with Python 3.5.4
> Note that qpid-tools is a checkout that includes this commit 
> 0ffa89e177346e68bdeb5a24b9f25190c983bd34 because I need it, and the version 
> on PyPI does not include it.
>Reporter: Brian Bouterse
>Assignee: Justin Ross
>Priority: Blocker
> Fix For: qpid-cpp-1.38.0
>
>
> 1. Start qpidd and verify that it starts
> 2. Verify it's listening on 5762 using `sudo netstat -planet | grep 5672`
> 3. Telnet connect to it with `telnet localhost 5672` observe that it connects
> Try to connect it to with qmf.BrokerAgent
> from qmf.client import BrokerAgent, ReconnectDelays
> conn_opts = {'url': 'amqp://localhost:5672'}
> ba = BrokerAgent.connect(**conn_opts)
> ba.getAllQueues()
> I get this exception after 10 seconds:
>   File "/home/vagrant/devel/kombu/kombu/transport/qpid.py", line 586, in 
> exchange_declare
> self._broker.addExchange(type, exchange, options)
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 344, in addExchange
> self._method('create', args)
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 233, in _method
> response = self._retry(self._request, '_method_request', content)
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 215, in _retry
> return f(*args, **kwargs)
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 224, in _request
> return self._client.call(Message(body=content, properties=props, 
> subject="broker"))
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 118, in call
> return self.wait(self.send(request))
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 137, in wait
> self.connection.wait(wakeup, msg="Waiting for response")
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/proton/utils.py",
>  line 292, in wait
> raise Timeout(txt)
> proton.Timeout: Connection amqp://localhost:5672 timed out: Waiting for 
> response
> What is interesting is that on the same system with simply_send.py (the 
> standard example) it connects and sends with the exact same url. I do that 
> with this:
> (pulp) [vagrant@pulp3 devel]$ python simple_send.py --address 
> 'amqp://localhost:5672' -m 1
> all messages confirmed
> The 'all messages confirmed' suggests that everything went fine and the 
> reactor called on_accepted().
> So I conclude that BrokerAgent is somehow fundamentally not working or my 
> environment is screwed up somehow.
> This same commit checkout was working with Python 2.7. I don't have that 
> environment handy currently, but I suspect this is somehow broken with Python 
> 3.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-8075) BrokerAgent not working for me

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated QPID-8075:
--
Affects Version/s: (was: qpid-python-1.37.0)
   qpid-cpp-1.37.0

> BrokerAgent not working for me
> --
>
> Key: QPID-8075
> URL: https://issues.apache.org/jira/browse/QPID-8075
> Project: Qpid
>  Issue Type: Bug
>  Components: QMF
>Affects Versions: qpid-cpp-1.37.0
> Environment: Fedora 25, fully up to date
> via dnf I installed:
> qpid-proton-c-0.17.0-5.fc25.x86_64
> qpid-cpp-server-1.36.0-1.fc25.x86_64
> pip freeze in my virtual environment is:
> python-qpid-proton==0.19.0
> qpid-tools==1.37.0
> Note this is with Python 3.5.4
> Note that qpid-tools is a checkout that includes this commit 
> 0ffa89e177346e68bdeb5a24b9f25190c983bd34 because I need it, and the version 
> on PyPI does not include it.
>Reporter: Brian Bouterse
>Assignee: Justin Ross
>Priority: Blocker
> Fix For: qpid-cpp-1.38.0
>
>
> 1. Start qpidd and verify that it starts
> 2. Verify it's listening on 5762 using `sudo netstat -planet | grep 5672`
> 3. Telnet connect to it with `telnet localhost 5672` observe that it connects
> Try to connect it to with qmf.BrokerAgent
> from qmf.client import BrokerAgent, ReconnectDelays
> conn_opts = {'url': 'amqp://localhost:5672'}
> ba = BrokerAgent.connect(**conn_opts)
> ba.getAllQueues()
> I get this exception after 10 seconds:
>   File "/home/vagrant/devel/kombu/kombu/transport/qpid.py", line 586, in 
> exchange_declare
> self._broker.addExchange(type, exchange, options)
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 344, in addExchange
> self._method('create', args)
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 233, in _method
> response = self._retry(self._request, '_method_request', content)
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 215, in _retry
> return f(*args, **kwargs)
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 224, in _request
> return self._client.call(Message(body=content, properties=props, 
> subject="broker"))
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 118, in call
> return self.wait(self.send(request))
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 137, in wait
> self.connection.wait(wakeup, msg="Waiting for response")
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/proton/utils.py",
>  line 292, in wait
> raise Timeout(txt)
> proton.Timeout: Connection amqp://localhost:5672 timed out: Waiting for 
> response
> What is interesting is that on the same system with simply_send.py (the 
> standard example) it connects and sends with the exact same url. I do that 
> with this:
> (pulp) [vagrant@pulp3 devel]$ python simple_send.py --address 
> 'amqp://localhost:5672' -m 1
> all messages confirmed
> The 'all messages confirmed' suggests that everything went fine and the 
> reactor called on_accepted().
> So I conclude that BrokerAgent is somehow fundamentally not working or my 
> environment is screwed up somehow.
> This same commit checkout was working with Python 2.7. I don't have that 
> environment handy currently, but I suspect this is somehow broken with Python 
> 3.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-8074) [Qpid JMS AMQP 0-x] Build framework to run JMS client system tests

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-8074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324698#comment-16324698
 ] 

ASF subversion and git services commented on QPID-8074:
---

Commit 738a72b8806757530a36df3496a7ddc9cd291001 in qpid-jms-amqp-0-x's branch 
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms-amqp-0-x.git;h=738a72b ]

QPID-8074: [JMS AMQP 0-x][System Tests] Copy client specific test 
JMSXUserIDTest from Broker-J sources


> [Qpid JMS AMQP 0-x] Build framework to run JMS client system tests
> --
>
> Key: QPID-8074
> URL: https://issues.apache.org/jira/browse/QPID-8074
> Project: Qpid
>  Issue Type: Improvement
>  Components: JMS AMQP 0-x
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>
> A number of JMS AMQP 0-x  client tests exist in Broker-J system test suite. 
> We need to move those tests from Broker-J source tree into JMS AMQP 0-x 
> sources. In order to do so, we need to build a new test framework which would 
> allow us to start Broker-J (and potentially Cpp Broker) and run the system 
> tests against the started broker.
> The test suite should use our virtualhost per test pattern. Check 
> {{BrokerAdmin}} idea in broker system tests.
> One wrinkle would be Java 8 - the tests would need Java 8 to run, even though 
> we want the client to remain Java 7 compatible.
> We could also write a broker admin allowing the tests to be run against the 
> CPPBroker



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (DISPATCH-911) New management call to return overall router network statistics

[Ernest Allen (JIRA)]

Ernest Allen created DISPATCH-911:
-

 Summary: New management call to return overall router network 
statistics
 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


We need overview charts that display:
  - the throughput rate for the router network
  - network load
  - average latency

For the throughput rate:
This is derived from the sum of router.address.deliveriesEgress for all 
addresses on all routers in the network.

For network load:
This is derived from the sum of the router.link.undeliveredCount and 
router.link.unsettledCount for all endpoint links on the network.

For the average latency:
A new attribute needs to be created. Each ingress message needs to be annotated 
with an ingress timestamp. When the message egresses the network, the total 
time 'in-flight' needs to be calculated and accumulated in the egress router's 
new router.address.deliveriesEgressDuration attribute. Average latency can be 
calculated using this statistic and the throughput statistic.

Add a new management action of "SUM" that recognizes a new application_proptery 
of filter. The SUM action sums the given attribute(s) from all routers. The 
filter determines which records are included.

To calculate load, the request looks like:
{
body: ['undeliveredCount', 'unsettledCount'],
application_properties: {
operation: 'SUM',
type: 'org.apache.qpid.dispatch.router.link',
filter: {'linkType': 'endpoint'}
}
}
This would return:
{
attributeNames: ['undeliveredCount', 'unsettledCount'],
values: [, ]
}
where the sums are for all routers for all links with linkType == endpoint 

For the throughput request:
{
body: ['deliveriesEgress'],
application_properties: {
operation: 'SUM',
type: 'org.apache.qpid.dispatch.router.address',
filter: {'name': '*'}  // or name:  for a single address
}
}
This would return:
{
attributeNames: ['deliveriesEgress'],
values: []
}
where the sum is for all routers for all address.names that matched the name 
given in the filter.

For the latancy request:
{
body: ['deliveriesEgress', 'deliveriesEgressDuration'],
application_properties: {
operation: 'SUM',
type: 'org.apache.qpid.dispatch.router.address',
filter: {'name': '*'} // or name:  for a single address
}
}
This would return:
{
attributeNames: ['deliveriesEgress', 'deliveriesEgressDuration'],
values: [, ]
}
where the sums are for all routers for all address.names that matched the name 
given in the filter.

Note: If annotating messages with timestamps for the deliveriesEgressDuration 
attribute is too much of a performance hit, an additional management call is 
needed to enable and disable this behavior.

Bonus: This new 'SUM' request can be used to replace the existing request that 
sums logStats accross routers. 




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-8074) [Qpid JMS AMQP 0-x] Build framework to run JMS client system tests

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-8074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324684#comment-16324684
 ] 

ASF subversion and git services commented on QPID-8074:
---

Commit 2dfc8e4d09b3a8b639387478c70e8d689afea8d1 in qpid-jms-amqp-0-x's branch 
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms-amqp-0-x.git;h=2dfc8e4 ]

QPID-8074: [JMS AMQP 0-x][System Tests] Copy client specific test 
AMQPEncodedMapMessageTest from Broker-J sources


> [Qpid JMS AMQP 0-x] Build framework to run JMS client system tests
> --
>
> Key: QPID-8074
> URL: https://issues.apache.org/jira/browse/QPID-8074
> Project: Qpid
>  Issue Type: Improvement
>  Components: JMS AMQP 0-x
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>
> A number of JMS AMQP 0-x  client tests exist in Broker-J system test suite. 
> We need to move those tests from Broker-J source tree into JMS AMQP 0-x 
> sources. In order to do so, we need to build a new test framework which would 
> allow us to start Broker-J (and potentially Cpp Broker) and run the system 
> tests against the started broker.
> The test suite should use our virtualhost per test pattern. Check 
> {{BrokerAdmin}} idea in broker system tests.
> One wrinkle would be Java 8 - the tests would need Java 8 to run, even though 
> we want the client to remain Java 7 compatible.
> We could also write a broker admin allowing the tests to be run against the 
> CPPBroker



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-8074) [Qpid JMS AMQP 0-x] Build framework to run JMS client system tests

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-8074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324669#comment-16324669
 ] 

ASF subversion and git services commented on QPID-8074:
---

Commit 2938de83c2052ca451c30eae4d4abb7c82f32519 in qpid-jms-amqp-0-x's branch 
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms-amqp-0-x.git;h=2938de8 ]

QPID-8074: [JMS AMQP 0-x][System Tests] Copy client specific test 
ExistingSocketTest from Broker-J sources


> [Qpid JMS AMQP 0-x] Build framework to run JMS client system tests
> --
>
> Key: QPID-8074
> URL: https://issues.apache.org/jira/browse/QPID-8074
> Project: Qpid
>  Issue Type: Improvement
>  Components: JMS AMQP 0-x
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>
> A number of JMS AMQP 0-x  client tests exist in Broker-J system test suite. 
> We need to move those tests from Broker-J source tree into JMS AMQP 0-x 
> sources. In order to do so, we need to build a new test framework which would 
> allow us to start Broker-J (and potentially Cpp Broker) and run the system 
> tests against the started broker.
> The test suite should use our virtualhost per test pattern. Check 
> {{BrokerAdmin}} idea in broker system tests.
> One wrinkle would be Java 8 - the tests would need Java 8 to run, even though 
> we want the client to remain Java 7 compatible.
> We could also write a broker admin allowing the tests to be run against the 
> CPPBroker



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: dispatch tests failing (Re: [1/2] qpid-proton git commit: PROTON-1727 [epoll] fix file descriptor leak on reconnect)

[Gordon Sim]

On 10/01/18 10:19, Gordon Sim wrote:
I see two if the dispatch system tests failing after the following 
commit to proton (they all when run against a proton lib before this 
patch). Subsequent commits to proton don't help either - dispatch tests 
fail against latest proton master also.


The tests that fail are system_tests_user_id_proxy and system_tests_policy.


The problem I believe is that this change moves the retrieval of the 
remote address from pconnection_start to pconnection_connected_lh and 
this means that when the router tries to get the hostname for the 
connection (to do policy checks) in the connection_bound event, it 
hasn't yet been retrieved.


I don't really understand the issue this change is trying to fix, so not 
sure how best to address the issue yet. Any ideas?


-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-8075) BrokerAgent not working for me

[Justin Ross (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324548#comment-16324548
 ] 

Justin Ross commented on QPID-8075:
---

I have a suspicion that this is because the request and response correlation 
IDs aren't matching on Python 3.  Trying it out.

> BrokerAgent not working for me
> --
>
> Key: QPID-8075
> URL: https://issues.apache.org/jira/browse/QPID-8075
> Project: Qpid
>  Issue Type: Bug
>  Components: QMF
>Affects Versions: qpid-python-1.37.0
> Environment: Fedora 25, fully up to date
> via dnf I installed:
> qpid-proton-c-0.17.0-5.fc25.x86_64
> qpid-cpp-server-1.36.0-1.fc25.x86_64
> pip freeze in my virtual environment is:
> python-qpid-proton==0.19.0
> qpid-tools==1.37.0
> Note this is with Python 3.5.4
> Note that qpid-tools is a checkout that includes this commit 
> 0ffa89e177346e68bdeb5a24b9f25190c983bd34 because I need it, and the version 
> on PyPI does not include it.
>Reporter: Brian Bouterse
>Priority: Blocker
>
> 1. Start qpidd and verify that it starts
> 2. Verify it's listening on 5762 using `sudo netstat -planet | grep 5672`
> 3. Telnet connect to it with `telnet localhost 5672` observe that it connects
> Try to connect it to with qmf.BrokerAgent
> from qmf.client import BrokerAgent, ReconnectDelays
> conn_opts = {'url': 'amqp://localhost:5672'}
> ba = BrokerAgent.connect(**conn_opts)
> ba.getAllQueues()
> I get this exception after 10 seconds:
>   File "/home/vagrant/devel/kombu/kombu/transport/qpid.py", line 586, in 
> exchange_declare
> self._broker.addExchange(type, exchange, options)
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 344, in addExchange
> self._method('create', args)
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 233, in _method
> response = self._retry(self._request, '_method_request', content)
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 215, in _retry
> return f(*args, **kwargs)
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 224, in _request
> return self._client.call(Message(body=content, properties=props, 
> subject="broker"))
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 118, in call
> return self.wait(self.send(request))
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py",
>  line 137, in wait
> self.connection.wait(wakeup, msg="Waiting for response")
>   File 
> "/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/proton/utils.py",
>  line 292, in wait
> raise Timeout(txt)
> proton.Timeout: Connection amqp://localhost:5672 timed out: Waiting for 
> response
> What is interesting is that on the same system with simply_send.py (the 
> standard example) it connects and sends with the exact same url. I do that 
> with this:
> (pulp) [vagrant@pulp3 devel]$ python simple_send.py --address 
> 'amqp://localhost:5672' -m 1
> all messages confirmed
> The 'all messages confirmed' suggests that everything went fine and the 
> reactor called on_accepted().
> So I conclude that BrokerAgent is somehow fundamentally not working or my 
> environment is screwed up somehow.
> This same commit checkout was working with Python 2.7. I don't have that 
> environment handy currently, but I suspect this is somehow broken with Python 
> 3.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPID-8075) BrokerAgent not working for me

[Brian Bouterse (JIRA)]

Brian Bouterse created QPID-8075:


 Summary: BrokerAgent not working for me
 Key: QPID-8075
 URL: https://issues.apache.org/jira/browse/QPID-8075
 Project: Qpid
  Issue Type: Bug
  Components: QMF
Affects Versions: qpid-python-1.37.0
 Environment: Fedora 25, fully up to date
via dnf I installed:
qpid-proton-c-0.17.0-5.fc25.x86_64
qpid-cpp-server-1.36.0-1.fc25.x86_64

pip freeze in my virtual environment is:
python-qpid-proton==0.19.0
qpid-tools==1.37.0

Note this is with Python 3.5.4

Note that qpid-tools is a checkout that includes this commit 
0ffa89e177346e68bdeb5a24b9f25190c983bd34 because I need it, and the version on 
PyPI does not include it.
Reporter: Brian Bouterse
Priority: Blocker


1. Start qpidd and verify that it starts
2. Verify it's listening on 5762 using `sudo netstat -planet | grep 5672`
3. Telnet connect to it with `telnet localhost 5672` observe that it connects

Try to connect it to with qmf.BrokerAgent

from qmf.client import BrokerAgent, ReconnectDelays
conn_opts = {'url': 'amqp://localhost:5672'}
ba = BrokerAgent.connect(**conn_opts)
ba.getAllQueues()

I get this exception after 10 seconds:

  File "/home/vagrant/devel/kombu/kombu/transport/qpid.py", line 586, in 
exchange_declare
self._broker.addExchange(type, exchange, options)
  File 
"/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py", 
line 344, in addExchange
self._method('create', args)
  File 
"/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py", 
line 233, in _method
response = self._retry(self._request, '_method_request', content)
  File 
"/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py", 
line 215, in _retry
return f(*args, **kwargs)
  File 
"/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py", 
line 224, in _request
return self._client.call(Message(body=content, properties=props, 
subject="broker"))
  File 
"/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py", 
line 118, in call
return self.wait(self.send(request))
  File 
"/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/qmf/client.py", 
line 137, in wait
self.connection.wait(wakeup, msg="Waiting for response")
  File 
"/home/vagrant/.virtualenvs/pulp/lib64/python3.5/site-packages/proton/utils.py",
 line 292, in wait
raise Timeout(txt)
proton.Timeout: Connection amqp://localhost:5672 timed out: Waiting for response

What is interesting is that on the same system with simply_send.py (the 
standard example) it connects and sends with the exact same url. I do that with 
this:

(pulp) [vagrant@pulp3 devel]$ python simple_send.py --address 
'amqp://localhost:5672' -m 1
all messages confirmed

The 'all messages confirmed' suggests that everything went fine and the reactor 
called on_accepted().

So I conclude that BrokerAgent is somehow fundamentally not working or my 
environment is screwed up somehow.

This same commit checkout was working with Python 2.7. I don't have that 
environment handy currently, but I suspect this is somehow broken with Python 3.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (DISPATCH-910) Inter-router connections with dir 'in' have no host name

[Ernest Allen (JIRA)]

Ernest Allen created DISPATCH-910:
-

 Summary: Inter-router connections with dir 'in' have no host name
 Key: DISPATCH-910
 URL: https://issues.apache.org/jira/browse/DISPATCH-910
 Project: Qpid Dispatch
  Issue Type: Bug
  Components: Management Agent
Affects Versions: 1.0.0
Reporter: Ernest Allen


There is no host name reported for inter-router connections with dir of 'in'

- start a 2 or more router network
router {
mode: interior
id: A
}
listener {
host: 0.0.0.0
saslMechanisms: ANONYMOUS
port: 5672
}

# listener for connectors from B
listener {
host: 0.0.0.0
role: inter-router
saslMechanisms: ANONYMOUS
port: 2000
}
---
router {
mode: interior
id: B
}
listener {
host: 0.0.0.0
saslMechanisms: ANONYMOUS
port: 22001
}

# connect to A
connector {
host: 0.0.0.0
role: inter-router
saslMechanisms: ANONYMOUS
port: 2000
}

- qdstat -c
$ qdstat -c
Connections
  id  host  container role  dir  security   
  authentication  tenant
 ===
  1 B inter-router  in   
no-security  anonymous-user  
  2 175fa6eb-b616-4c1c-9af9-a8ac121d76a0  normalin   
no-security  no-auth 

Connection #2 is from qdstat.
Connection 1 is from Router B. The host should not be blank, but it is.

The host is correct for dir 'out' connections.
$ qdstat -b 0.0.0.0:22001 -c
Connections
  id  host  container role  dir  
security authentication  tenant
  ==
  1   0.0.0.0:2000  A inter-router  out  
no-security  anonymous-user  
  2 a5c4c524-53de-4b4f-896e-1bf15c30f993  normalin   
no-security  no-auth 




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-909) Handle inter-router connections with no host and no name

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324459#comment-16324459
 ] 

ASF subversion and git services commented on DISPATCH-909:
--

Commit 8468525688a5985b2f54e3aba8afe8749362c695 in qpid-dispatch's branch 
refs/heads/master from [~eallen]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=8468525 ]

DISPATCH-909 Preparing for new overview charts page


> Handle inter-router connections with no host and no name
> 
>
> Key: DISPATCH-909
> URL: https://issues.apache.org/jira/browse/DISPATCH-909
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Console
>Affects Versions: 1.0.0
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>
> inter-router connections with direction of 'in' now have no host and a 
> connection name of connection/. When there are multiple routers, the trees on 
> the Overview and Entities page show several connections with blank names.
> The trees on the Overview and Entities pages should construct a name 
> including the connection's container. This will differentiate the connections.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (DISPATCH-909) Handle inter-router connections with no host and no name

[Ernest Allen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DISPATCH-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ernest Allen resolved DISPATCH-909.
---
Resolution: Fixed

> Handle inter-router connections with no host and no name
> 
>
> Key: DISPATCH-909
> URL: https://issues.apache.org/jira/browse/DISPATCH-909
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Console
>Affects Versions: 1.0.0
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>
> inter-router connections with direction of 'in' now have no host and a 
> connection name of connection/. When there are multiple routers, the trees on 
> the Overview and Entities page show several connections with blank names.
> The trees on the Overview and Entities pages should construct a name 
> including the connection's container. This will differentiate the connections.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-909) Handle inter-router connections with no host and no name

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324460#comment-16324460
 ] 

ASF subversion and git services commented on DISPATCH-909:
--

Commit c36f3af0d1ad38d90dd5b738bc3e40577f07ae1d in qpid-dispatch's branch 
refs/heads/master from [~eallen]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=c36f3af ]

DISPATCH-909 Work around no host on some connections


> Handle inter-router connections with no host and no name
> 
>
> Key: DISPATCH-909
> URL: https://issues.apache.org/jira/browse/DISPATCH-909
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Console
>Affects Versions: 1.0.0
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>
> inter-router connections with direction of 'in' now have no host and a 
> connection name of connection/. When there are multiple routers, the trees on 
> the Overview and Entities page show several connections with blank names.
> The trees on the Overview and Entities pages should construct a name 
> including the connection's container. This will differentiate the connections.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (PROTON-1732) [OSX] Enable swig for the Travis CI build

[Roddie Kieley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roddie Kieley resolved PROTON-1732.
---
Resolution: Resolved

PR updated and committed with assistance from [~astitcher].

> [OSX] Enable swig for the Travis CI build
> -
>
> Key: PROTON-1732
> URL: https://issues.apache.org/jira/browse/PROTON-1732
> Project: Qpid Proton
>  Issue Type: Sub-task
>  Components: proton-c
>Affects Versions: proton-c-0.19.0
> Environment: Travis CI
> Xcode 7.3, 9
>Reporter: Roddie Kieley
>Priority: Minor
> Fix For: proton-c-future
>
>
> Comparing the current travis builds for linux and osx we see that the linux 
> builds cover ruby whereas the osx builds do not. Swig is required for this to 
> occur.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-909) Handle inter-router connections with no host and no name

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324375#comment-16324375
 ] 

ASF subversion and git services commented on DISPATCH-909:
--

Commit 770edaf17e40bdf40add2b3ecfdc00a0897ee9ad in qpid-dispatch's branch 
refs/heads/master from [~eallen]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=770edaf ]

DISPATCH-909 Handle inter-router connections with blank host


> Handle inter-router connections with no host and no name
> 
>
> Key: DISPATCH-909
> URL: https://issues.apache.org/jira/browse/DISPATCH-909
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Console
>Affects Versions: 1.0.0
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>
> inter-router connections with direction of 'in' now have no host and a 
> connection name of connection/. When there are multiple routers, the trees on 
> the Overview and Entities page show several connections with blank names.
> The trees on the Overview and Entities pages should construct a name 
> including the connection's container. This will differentiate the connections.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPID-8060) [Broker-J] [AMQP 0-8..0-9-1] Declaring queue that specifies an alternate binding that does not exist crashes the Broker

[Alex Rudyy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy resolved QPID-8060.
--
Resolution: Fixed

Merges look good to me

> [Broker-J] [AMQP 0-8..0-9-1] Declaring queue that specifies an alternate 
> binding that does not exist crashes the Broker
> ---
>
> Key: QPID-8060
> URL: https://issues.apache.org/jira/browse/QPID-8060
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
>Assignee: Keith Wall
> Fix For: qpid-java-broker-7.0.1
>
>
> Declaring queue with not existing alternate binding crashes the Broker with 
> the following stack trace:
> {noformat}
> org.apache.qpid.server.configuration.IllegalConfigurationException: Cannot 
> create alternate binding for 'test' : Alternate binding destination 
> 'not_existing' cannot be found.
>   at 
> org.apache.qpid.server.queue.AbstractQueue.validateOrCreateAlternateBinding(AbstractQueue.java:3537)
>   at 
> org.apache.qpid.server.queue.AbstractQueue.onCreate(AbstractQueue.java:320)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject.doCreation(AbstractConfiguredObject.java:1273)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:893)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:866)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:637)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:630)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submitWrappedTask(TaskExecutorImpl.java:165)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submit(TaskExecutorImpl.java:153)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject.doOnConfigThread(AbstractConfiguredObject.java:629)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject.createAsync(AbstractConfiguredObject.java:865)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObjectTypeFactory.createAsync(AbstractConfiguredObjectTypeFactory.java:75)
>   at 
> org.apache.qpid.server.queue.QueueFactory.createAsync(QueueFactory.java:58)
>   at 
> org.apache.qpid.server.model.ConfiguredObjectFactoryImpl.createAsync(ConfiguredObjectFactoryImpl.java:145)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject.addChildAsync(AbstractConfiguredObject.java:2143)
>   at 
> org.apache.qpid.server.virtualhost.AbstractVirtualHost.addChildAsync(AbstractVirtualHost.java:857)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2100)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2095)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:637)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:630)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:320)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:360)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:313)
>   at 
> com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:111)
>   at 
> com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:58)
>   at 
> com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:75)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.qpid.server.bytebuffer.QpidByteBufferFactory.lambda$null$0(QpidByteBufferFactory.java:464)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Client code:
> {code}
> Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
> AMQSession amqSession = (AMQSession)session;
> final Map arguments = new 

[jira] [Resolved] (QPID-8017) [Broker-J] [BDB] JE log events written at JUL level FINE and below not included in the log produced by a BrokerLogger

[Alex Rudyy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy resolved QPID-8017.
--
Resolution: Fixed

Committed changes look reasonable to me

> [Broker-J] [BDB]  JE log events written at JUL level FINE and below not 
> included in the log produced by a BrokerLogger
> --
>
> Key: QPID-8017
> URL: https://issues.apache.org/jira/browse/QPID-8017
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J
>Affects Versions: qpid-java-6.1, qpid-java-broker-7.0.0
>Reporter: Keith Wall
>Priority: Minor
> Fix For: qpid-java-broker-7.0.1
>
> Attachments: 
> 0001-QPID-8017-Broker-J-Propagate-logger-rules-into-JUL-l.patch
>
>
> Reproduction:
> * Add {{NameAndLevel}} logger inclusion rule BrokerLogger {{file}} for source 
> {{com.sleepycat.je.*}} with Level.ALL
> * Add a BDB HA VHN/VHN
> * Expected behaviour:  verbose logging from JE.  Actual behaviour:  moderate 
> logging only
> For instance, JE writes the following message at {{FINE}} which should be 
> logged by the handler as {{TRACE}}  but it is absent.
> {noformat}
> 2017-11-07 10:42:15,467 TRACE [Cleaner-1] (c.s.j.c.UtilizationCalculator) - 
> [default] Clean file none: predicted min util is below minUtilization, 
> current util min: 20 max: 20, predicted util min: 20 max: 20
> {noformat}
> There is a workaround for the functional problem, albeit a restart is 
> required and the ability to change the process's system properties.  Use the 
> normal JUL system property {{java.util.logging.config.file}}.  Set this to 
> the location of a logging.properties file with the {{com.sleepycat.je}} 
> logger set to the desired level.  Once the JVM is restarted, the Broker's log 
> files will include the logging.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1730) Update tox.ini environment list to include py36

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PROTON-1730:


Github user kgiusti closed the pull request at:

https://github.com/apache/qpid-proton/pull/134


> Update tox.ini environment list to include py36
> ---
>
> Key: PROTON-1730
> URL: https://issues.apache.org/jira/browse/PROTON-1730
> Project: Qpid Proton
>  Issue Type: Test
>  Components: python-binding
>Affects Versions: proton-c-0.19.0
>Reporter: Ken Giusti
>Assignee: Ken Giusti
>Priority: Minor
> Fix For: proton-c-0.20.0
>
>
> Python version 3.6 is the current stable version of python.  The 
> proton-c/tox.ini.in file does not include py36 as a test environment for the 
> python-tox tests so the unit tests do not run under the latest version of 
> python.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (PROTON-1730) Update tox.ini environment list to include py36

[Ken Giusti (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Giusti resolved PROTON-1730.

Resolution: Fixed

> Update tox.ini environment list to include py36
> ---
>
> Key: PROTON-1730
> URL: https://issues.apache.org/jira/browse/PROTON-1730
> Project: Qpid Proton
>  Issue Type: Test
>  Components: python-binding
>Affects Versions: proton-c-0.19.0
>Reporter: Ken Giusti
>Assignee: Ken Giusti
>Priority: Minor
> Fix For: proton-c-0.20.0
>
>
> Python version 3.6 is the current stable version of python.  The 
> proton-c/tox.ini.in file does not include py36 as a test environment for the 
> python-tox tests so the unit tests do not run under the latest version of 
> python.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1730) Update tox.ini environment list to include py36

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PROTON-1730:


Github user kgiusti commented on the issue:

https://github.com/apache/qpid-proton/pull/134
  
Merged 


> Update tox.ini environment list to include py36
> ---
>
> Key: PROTON-1730
> URL: https://issues.apache.org/jira/browse/PROTON-1730
> Project: Qpid Proton
>  Issue Type: Test
>  Components: python-binding
>Affects Versions: proton-c-0.19.0
>Reporter: Ken Giusti
>Assignee: Ken Giusti
>Priority: Minor
> Fix For: proton-c-0.20.0
>
>
> Python version 3.6 is the current stable version of python.  The 
> proton-c/tox.ini.in file does not include py36 as a test environment for the 
> python-tox tests so the unit tests do not run under the latest version of 
> python.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-proton pull request #134: PROTON-1730: add python version 3.6 to tox te...

[kgiusti]

Github user kgiusti closed the pull request at:

https://github.com/apache/qpid-proton/pull/134


---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-proton issue #134: PROTON-1730: add python version 3.6 to tox tests

[kgiusti]

Github user kgiusti commented on the issue:

https://github.com/apache/qpid-proton/pull/134
  
Merged 


---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1730) Update tox.ini environment list to include py36

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on PROTON-1730:
-

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

PROTON-1730: add python version 3.6 to tox tests


> Update tox.ini environment list to include py36
> ---
>
> Key: PROTON-1730
> URL: https://issues.apache.org/jira/browse/PROTON-1730
> Project: Qpid Proton
>  Issue Type: Test
>  Components: python-binding
>Affects Versions: proton-c-0.19.0
>Reporter: Ken Giusti
>Assignee: Ken Giusti
>Priority: Minor
> Fix For: proton-c-0.20.0
>
>
> Python version 3.6 is the current stable version of python.  The 
> proton-c/tox.ini.in file does not include py36 as a test environment for the 
> python-tox tests so the unit tests do not run under the latest version of 
> python.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (QPIDIT-108) [C++ shim] Update use of Json::Reader and Json::FastWriter which are deprecated

[Kim van der Riet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDIT-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet reassigned QPIDIT-108:
---

Assignee: Kim van der Riet

> [C++ shim] Update use of Json::Reader and Json::FastWriter which are 
> deprecated
> ---
>
> Key: QPIDIT-108
> URL: https://issues.apache.org/jira/browse/QPIDIT-108
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Task
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>
> Recent versions of Fedora are warning that use of {{Json::Reader}} and 
> {{Json::FastWriter}} are now deprecated. Check that whatever replaces this 
> will at a minimum run on RHEL7 / CentOS7.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPIDIT-108) [C++ shim] Update use of Json::Reader and Json::FastWriter which are deprecated

[Kim van der Riet (JIRA)]

Kim van der Riet created QPIDIT-108:
---

 Summary: [C++ shim] Update use of Json::Reader and 
Json::FastWriter which are deprecated
 Key: QPIDIT-108
 URL: https://issues.apache.org/jira/browse/QPIDIT-108
 Project: Apache QPID Interoperability Test Suite
  Issue Type: Task
Reporter: Kim van der Riet


Recent versions of Fedora are warning that use of {{Json::Reader}} and 
{{Json::FastWriter}} are now deprecated. Check that whatever replaces this will 
at a minimum run on RHEL7 / CentOS7.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-65) Add command-line controls to JMS_hdrs_props_test to control test more precisely

[Kim van der Riet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDIT-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-65:
---
Fix Version/s: 0.2.0

> 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
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-107) Add support for JMS message properties in ProtonCpp shim

[Kim van der Riet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDIT-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-107:

Fix Version/s: 0.2.0

> Add support for JMS message properties in ProtonCpp shim
> 
>
> Key: QPIDIT-107
> URL: https://issues.apache.org/jira/browse/QPIDIT-107
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Task
>  Components: Proton C++ Shim
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
> Fix For: 0.2.0
>
>
> Currently the properties section of the test is disabled because the C++ 
> bindings did not support access to message properties at the time the shim 
> was first written.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPIDIT-65) Add command-line controls to JMS_hdrs_props_test to control test more precisely

[Kim van der Riet (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPIDIT-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324232#comment-16324232
 ] 

Kim van der Riet commented on QPIDIT-65:


Currently the message properties portion of the test is commented out because 
the C++ shims do not handle message properties. This was because at the time 
they were written, the Proton C++ binding API did not support message property 
access. This has now been resolved.

Once the C++ shims can handle properties, then the properties section of these 
tests can be enabled.

> 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
>
> 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
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1728) [proton-c] Reorganize the source tree now that Proton J is split off

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PROTON-1728:


Github user astitcher commented on the issue:

https://github.com/apache/qpid-proton/pull/132
  
Can I suggest breaking this down into 3 separate changes (PRs branches 
etc.):
* Removal of deprecated bindings
* Removal of obsolete doc
* Moving the remainder to new locations and fixing up build

I think it'll be easier to see what's going on in the important part (the 
third) if there were fewer individual commits to look at. This would be easier 
I think if you just remove all the stuff from the tree.

In any case the removals are much easier to review/test individually.


> [proton-c] Reorganize the source tree now that Proton J is split off
> 
>
> Key: PROTON-1728
> URL: https://issues.apache.org/jira/browse/PROTON-1728
> Project: Qpid Proton
>  Issue Type: Task
>  Components: proton-c
>Reporter: Justin Ross
>Assignee: Justin Ross
> Fix For: proton-c-0.20.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-proton issue #132: PROTON-1728: WIP: Reorganize the source tree and rem...

[astitcher]

Github user astitcher commented on the issue:

https://github.com/apache/qpid-proton/pull/132
  
Can I suggest breaking this down into 3 separate changes (PRs branches 
etc.):
* Removal of deprecated bindings
* Removal of obsolete doc
* Moving the remainder to new locations and fixing up build

I think it'll be easier to see what's going on in the important part (the 
third) if there were fewer individual commits to look at. This would be easier 
I think if you just remove all the stuff from the tree.

In any case the removals are much easier to review/test individually.


---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Comment Edited] (QPIDIT-65) Add command-line controls to JMS_hdrs_props_test to control test more precisely

[Kim van der Riet (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPIDIT-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324218#comment-16324218
 ] 

Kim van der Riet edited comment on QPIDIT-65 at 1/12/18 4:48 PM:
-

Commit d6d837edd719ad1a548621d1394d18d981013d6c 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=d6d837e ]

QPIDIT-65: Added \-\-{include,exclude}\-hdr and \-\-{include,exclude}\-prop 
options, and implemented them. The \-\-exclude\-{hdr,prop} option allows the 
value "ALL" to exclude all values from the test.



was (Author: jira-bot):
Commit d6d837edd719ad1a548621d1394d18d981013d6c 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=d6d837e ]

QPIDIT-65: Added \-\-{include,exclude}-hdr and --{include,exclude}-prop 
options, and implemented them. The \-\-exclude-{hdr,prop} option allows the 
value "ALL" to exclude all values from the test.


> 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
>
> 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
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Comment Edited] (QPIDIT-65) Add command-line controls to JMS_hdrs_props_test to control test more precisely

[Kim van der Riet (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPIDIT-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324218#comment-16324218
 ] 

Kim van der Riet edited comment on QPIDIT-65 at 1/12/18 4:46 PM:
-

Commit d6d837edd719ad1a548621d1394d18d981013d6c 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=d6d837e ]

QPIDIT-65: Added \-\-{include,exclude}-hdr and --{include,exclude}-prop 
options, and implemented them. The \-\-exclude-{hdr,prop} option allows the 
value "ALL" to exclude all values from the test.



was (Author: jira-bot):
Commit d6d837edd719ad1a548621d1394d18d981013d6c 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=d6d837e ]

QPIDIT-65: Added --{include,exclude}-hdr and --{include,exclude}-prop options, 
and implemented them. The --exclude-{hdr,prop} option allows the value "ALL" to 
exclude all values from the test.


> 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
>
> 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
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPIDIT-65) Add command-line controls to JMS_hdrs_props_test to control test more precisely

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPIDIT-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324218#comment-16324218
 ] 

ASF subversion and git services commented on QPIDIT-65:
---

Commit d6d837edd719ad1a548621d1394d18d981013d6c 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=d6d837e ]

QPIDIT-65: Added --{include,exclude}-hdr and --{include,exclude}-prop options, 
and implemented them. The --exclude-{hdr,prop} option allows the value "ALL" to 
exclude all values from the test.


> 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
>
> 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
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Comment Edited] (QPIDIT-65) Add command-line controls to JMS_hdrs_props_test to control test more precisely

[Kim van der Riet (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPIDIT-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324203#comment-16324203
 ] 

Kim van der Riet edited comment on QPIDIT-65 at 1/12/18 4:38 PM:
-

Add {{\-\-include-hdr}} and {{\-\-exclude-hdr}} to control headers in test.
Add {{\-\-include-prop}} and {{\-\-exclude-prop}} to control properties in test.
Allow the exclude options to use the value {{ALL}} to exclude all headers or 
properties.

Currently each value runs as a single test, this is making the test very long 
and inefficient.
For headers, figure out a way to combine the values for each header into a 
single test running multiple messages, one message per value.
Where headers are combined, a single test containing messages with the cross 
product of the values of the headers should work.


was (Author: kpvdr):
Add {{\-\-include-hdr}} and {{\-\-exclude-hdr}} to control headers in test.
Add {{\-\-include-prop}} and {\-\-exclude-prop}} to control properties in test.
Allow the exclude options to use the value {{ALL}} to exclude all headers or 
properties.

Currently each value runs as a single test, this is making the test very long 
and inefficient.
For headers, figure out a way to combine the values for each header into a 
single test running multiple messages, one message per value.
Where headers are combined, a single test containing messages with the cross 
product of the values of the headers should work.

> 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
>
> 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
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPIDIT-65) Add command-line controls to JMS_hdrs_props_test to control test more precisely

[Kim van der Riet (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPIDIT-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324203#comment-16324203
 ] 

Kim van der Riet commented on QPIDIT-65:


Add {{\-\-include-hdr}} and {{\-\-exclude-hdr}} to control headers in test.
Add {{\-\-include-prop}} and {\-\-exclude-prop}} to control properties in test.
Allow the exclude options to use the value {{ALL}} to exclude all headers or 
properties.

Currently each value runs as a single test, this is making the test very long 
and inefficient.
For headers, figure out a way to combine the values for each header into a 
single test running multiple messages, one message per value.
Where headers are combined, a single test containing messages with the cross 
product of the values of the headers should work.

> 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
>
> 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
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1730) Update tox.ini environment list to include py36

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PROTON-1730:


Github user astitcher commented on the issue:

https://github.com/apache/qpid-proton/pull/134
  
Looks good to me


> Update tox.ini environment list to include py36
> ---
>
> Key: PROTON-1730
> URL: https://issues.apache.org/jira/browse/PROTON-1730
> Project: Qpid Proton
>  Issue Type: Test
>  Components: python-binding
>Affects Versions: proton-c-0.19.0
>Reporter: Ken Giusti
>Assignee: Ken Giusti
>Priority: Minor
> Fix For: proton-c-0.20.0
>
>
> Python version 3.6 is the current stable version of python.  The 
> proton-c/tox.ini.in file does not include py36 as a test environment for the 
> python-tox tests so the unit tests do not run under the latest version of 
> python.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-proton issue #134: PROTON-1730: add python version 3.6 to tox tests

[astitcher]

Github user astitcher commented on the issue:

https://github.com/apache/qpid-proton/pull/134
  
Looks good to me


---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1732) [OSX] Enable swig for the Travis CI build

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PROTON-1732:


Github user asfgit closed the pull request at:

https://github.com/apache/qpid-proton/pull/135


> [OSX] Enable swig for the Travis CI build
> -
>
> Key: PROTON-1732
> URL: https://issues.apache.org/jira/browse/PROTON-1732
> Project: Qpid Proton
>  Issue Type: Sub-task
>  Components: proton-c
>Affects Versions: proton-c-0.19.0
> Environment: Travis CI
> Xcode 7.3, 9
>Reporter: Roddie Kieley
>Priority: Minor
> Fix For: proton-c-future
>
>
> Comparing the current travis builds for linux and osx we see that the linux 
> builds cover ruby whereas the osx builds do not. Swig is required for this to 
> occur.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1732) [OSX] Enable swig for the Travis CI build

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on PROTON-1732:
-

Commit 836df5f4cfa7f1bcee985fae0f483b27be72d345 in qpid-proton's branch 
refs/heads/master from [~rkieley]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=836df5f ]

PROTON-1732: [OSX] Enable swig for the Travis CI build

Closes #135


> [OSX] Enable swig for the Travis CI build
> -
>
> Key: PROTON-1732
> URL: https://issues.apache.org/jira/browse/PROTON-1732
> Project: Qpid Proton
>  Issue Type: Sub-task
>  Components: proton-c
>Affects Versions: proton-c-0.19.0
> Environment: Travis CI
> Xcode 7.3, 9
>Reporter: Roddie Kieley
>Priority: Minor
> Fix For: proton-c-future
>
>
> Comparing the current travis builds for linux and osx we see that the linux 
> builds cover ruby whereas the osx builds do not. Swig is required for this to 
> occur.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-proton pull request #135: PROTON-1732: [OSX] Enable swig for the Travis...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/qpid-proton/pull/135


---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-dispatch issue #241: DISPATCH-906 Create procedure for integrating disp...

[bhardesty]

Github user bhardesty commented on the issue:

https://github.com/apache/qpid-dispatch/pull/241
  
@jdanekrh @enkeys I updated the example keytab attribute. I just set it to 
the default location indicated in the Cyrus SASL docs 
(https://www.cyrusimap.org/sasl/sasl/options.html#gssapi).


---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-906) Document Kerberos integration

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324181#comment-16324181
 ] 

ASF GitHub Bot commented on DISPATCH-906:
-

Github user bhardesty commented on the issue:

https://github.com/apache/qpid-dispatch/pull/241
  
@jdanekrh @enkeys I updated the example keytab attribute. I just set it to 
the default location indicated in the Cyrus SASL docs 
(https://www.cyrusimap.org/sasl/sasl/options.html#gssapi).


> Document Kerberos integration
> -
>
> Key: DISPATCH-906
> URL: https://issues.apache.org/jira/browse/DISPATCH-906
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Documentation
>Reporter: Ben Hardesty
>Assignee: Ben Hardesty
>
> Document requirements and for accepting Kerberos authenticated connections.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-906) Document Kerberos integration

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324169#comment-16324169
 ] 

ASF GitHub Bot commented on DISPATCH-906:
-

Github user philfest commented on the issue:

https://github.com/apache/qpid-dispatch/pull/241
  
Nicely done @bhardesty. Looks ready to merge (from a docs pov) to me.


> Document Kerberos integration
> -
>
> Key: DISPATCH-906
> URL: https://issues.apache.org/jira/browse/DISPATCH-906
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Documentation
>Reporter: Ben Hardesty
>Assignee: Ben Hardesty
>
> Document requirements and for accepting Kerberos authenticated connections.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-dispatch issue #241: DISPATCH-906 Create procedure for integrating disp...

[philfest]

Github user philfest commented on the issue:

https://github.com/apache/qpid-dispatch/pull/241
  
Nicely done @bhardesty. Looks ready to merge (from a docs pov) to me.


---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (PROTON-1742) there is no send example that works well with selected_recv

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross reassigned PROTON-1742:
---

Assignee: Gordon Sim  (was: Justin Ross)

> there is no send example that works well with selected_recv
> ---
>
> Key: PROTON-1742
> URL: https://issues.apache.org/jira/browse/PROTON-1742
> Project: Qpid Proton
>  Issue Type: Improvement
>Reporter: Gordon Sim
>Assignee: Gordon Sim
>Priority: Minor
> Fix For: proton-c-0.21.0
>
> Attachments: selected_recv_cpp_test.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: dispatch tests failing (Re: [1/2] qpid-proton git commit: PROTON-1727 [epoll] fix file descriptor leak on reconnect)

[Robbie Gemmell]

Showing the same on TravisCI, e.g:
https://travis-ci.org/apache/qpid-dispatch/builds/324311983

On 10 January 2018 at 10:19, Gordon Sim  wrote:
> I see two if the dispatch system tests failing after the following commit to
> proton (they all when run against a proton lib before this patch).
> Subsequent commits to proton don't help either - dispatch tests fail against
> latest proton master also.
>
> The tests that fail are system_tests_user_id_proxy and system_tests_policy.
>
> On 22/12/17 17:13, acon...@apache.org wrote:
>>
>> Repository: qpid-proton
>> Updated Branches:
>>refs/heads/master b462433e3 -> 223e6d012
>>
>>
>> PROTON-1727 [epoll] fix file descriptor leak on reconnect
>>
>> Fix a file descriptor leak when a host name resolves to multiple socket
>> addresses and connecting to the first address fails.
>>
>>
>> Project: http://git-wip-us.apache.org/repos/asf/qpid-proton/repo
>> Commit: http://git-wip-us.apache.org/repos/asf/qpid-proton/commit/8d91e54c
>> Tree: http://git-wip-us.apache.org/repos/asf/qpid-proton/tree/8d91e54c
>> Diff: http://git-wip-us.apache.org/repos/asf/qpid-proton/diff/8d91e54c
>>
>> Branch: refs/heads/master
>> Commit: 8d91e54c4445f8f7fcac44150de5ee2da34a3571
>> Parents: b462433
>> Author: Alan Conway 
>> Authored: Thu Dec 21 12:01:07 2017 -0500
>> Committer: Alan Conway 
>> Committed: Fri Dec 22 12:11:08 2017 -0500
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> For additional commands, e-mail: dev-h...@qpid.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (PROTON-1742) there is no send example that works well with selected_recv

[Gordon Sim (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gordon Sim resolved PROTON-1742.

Resolution: Fixed

> there is no send example that works well with selected_recv
> ---
>
> Key: PROTON-1742
> URL: https://issues.apache.org/jira/browse/PROTON-1742
> Project: Qpid Proton
>  Issue Type: Improvement
>Reporter: Gordon Sim
>Assignee: Justin Ross
>Priority: Minor
> Fix For: proton-c-0.21.0
>
> Attachments: selected_recv_cpp_test.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1742) there is no send example that works well with selected_recv

[Gordon Sim (JIRA)]

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

Gordon Sim commented on PROTON-1742:


variant of simple_Send added for python and c++ that sets the property to allow 
selected_recv example to be observed.

I did try to add a test for the c++ side (see attached patch) but of course as 
it runs against the dummy broker, and that doesn't support selectors, it 
doesn't work. Attached it here just in case it is of use later.

> there is no send example that works well with selected_recv
> ---
>
> Key: PROTON-1742
> URL: https://issues.apache.org/jira/browse/PROTON-1742
> Project: Qpid Proton
>  Issue Type: Improvement
>Reporter: Gordon Sim
>Assignee: Justin Ross
>Priority: Minor
> Fix For: proton-c-0.21.0
>
> Attachments: selected_recv_cpp_test.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1742) there is no send example that works well with selected_recv

[Gordon Sim (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gordon Sim updated PROTON-1742:
---
Attachment: selected_recv_cpp_test.patch

> there is no send example that works well with selected_recv
> ---
>
> Key: PROTON-1742
> URL: https://issues.apache.org/jira/browse/PROTON-1742
> Project: Qpid Proton
>  Issue Type: Improvement
>Reporter: Gordon Sim
>Assignee: Justin Ross
>Priority: Minor
> Fix For: proton-c-0.21.0
>
> Attachments: selected_recv_cpp_test.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1742) there is no send example that works well with selected_recv

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on PROTON-1742:
-

Commit 9234c2a54e13da900a60e0380bf7fe7185b6bb0d in qpid-proton's branch 
refs/heads/master from [~gsim]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=9234c2a ]

PROTON-1742: add sender that can be used with selected recv


> there is no send example that works well with selected_recv
> ---
>
> Key: PROTON-1742
> URL: https://issues.apache.org/jira/browse/PROTON-1742
> Project: Qpid Proton
>  Issue Type: Improvement
>Reporter: Gordon Sim
>Assignee: Justin Ross
>Priority: Minor
> Fix For: proton-c-0.21.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (DISPATCH-909) Handle inter-router connections with no host and no name

[Ernest Allen (JIRA)]

Ernest Allen created DISPATCH-909:
-

 Summary: Handle inter-router connections with no host and no name
 Key: DISPATCH-909
 URL: https://issues.apache.org/jira/browse/DISPATCH-909
 Project: Qpid Dispatch
  Issue Type: Bug
  Components: Console
Affects Versions: 1.0.0
Reporter: Ernest Allen
Assignee: Ernest Allen


inter-router connections with direction of 'in' now have no host and a 
connection name of connection/. When there are multiple routers, the trees on 
the Overview and Entities page show several connections with blank names.

The trees on the Overview and Entities pages should construct a name including 
the connection's container. This will differentiate the connections.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1741) selected_recv example doesn't work

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated PROTON-1741:

Fix Version/s: proton-c-0.20.0

> selected_recv example doesn't work
> --
>
> Key: PROTON-1741
> URL: https://issues.apache.org/jira/browse/PROTON-1741
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: examples
>Reporter: Gordon Sim
> Fix For: proton-c-0.20.0
>
>
> The cpp example explicitly sets the selector to be binary, which is 
> incorrect. It should be a string.
> For the python example, if run with python 2, the selector string will also 
> be binary as it isn't explicitly marked as utf8.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (PROTON-1741) selected_recv example doesn't work

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross reassigned PROTON-1741:
---

Assignee: Gordon Sim

> selected_recv example doesn't work
> --
>
> Key: PROTON-1741
> URL: https://issues.apache.org/jira/browse/PROTON-1741
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: examples
>Reporter: Gordon Sim
>Assignee: Gordon Sim
> Fix For: proton-c-0.20.0
>
>
> The cpp example explicitly sets the selector to be binary, which is 
> incorrect. It should be a string.
> For the python example, if run with python 2, the selector string will also 
> be binary as it isn't explicitly marked as utf8.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1742) there is no send example that works well with selected_recv

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated PROTON-1742:

Fix Version/s: proton-c-0.21.0

> there is no send example that works well with selected_recv
> ---
>
> Key: PROTON-1742
> URL: https://issues.apache.org/jira/browse/PROTON-1742
> Project: Qpid Proton
>  Issue Type: Improvement
>Reporter: Gordon Sim
>Priority: Minor
> Fix For: proton-c-0.21.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (PROTON-1742) there is no send example that works well with selected_recv

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross reassigned PROTON-1742:
---

Assignee: Justin Ross

> there is no send example that works well with selected_recv
> ---
>
> Key: PROTON-1742
> URL: https://issues.apache.org/jira/browse/PROTON-1742
> Project: Qpid Proton
>  Issue Type: Improvement
>Reporter: Gordon Sim
>Assignee: Justin Ross
>Priority: Minor
> Fix For: proton-c-0.21.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-104) Add test for JMS shared subscriptions

[Kim van der Riet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDIT-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-104:

Affects Version/s: 0.1.0

> Add test for JMS shared subscriptions
> -
>
> Key: QPIDIT-104
> URL: https://issues.apache.org/jira/browse/QPIDIT-104
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: New Feature
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Priority: Minor
>
> JMS 2.0 allows for shared subscriptions. These are supported in the Artemis 
> and ActiveMQ brokers, and in the Qpid-jms client.
> Add a test which will check interoperability for the JMS client vs other 
> clients (C++ and Python to start with).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-76) Add Qpid Proton Go shim for amqp_types_test

[Kim van der Riet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDIT-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-76:
---
Affects Version/s: 0.1.0

> Add Qpid Proton Go shim for amqp_types_test
> ---
>
> Key: QPIDIT-76
> URL: https://issues.apache.org/jira/browse/QPIDIT-76
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: New Feature
>Affects Versions: 0.1.0
> Environment: go 1.7, 1.8, maybe 1.6
>Reporter: Jiri Daněk
>Assignee: Jiri Daněk
>Priority: Minor
>
> Qpid Proton Go is a AMQP client currently in development. Some AMQP types are 
> not yet supported.
> (my personal motivation for looking into this is to eventually write shim for 
> activemq-client (an OpenWire protocol library); not sure if interop with 
> other protocols is even in the scope of the QPIDIT project; so I want to get 
> more familiar with it first)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-43) Add AMQP messaging features test

[Kim van der Riet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDIT-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-43:
---
Affects Version/s: 0.1.0

> Add AMQP messaging features test
> 
>
> Key: QPIDIT-43
> URL: https://issues.apache.org/jira/browse/QPIDIT-43
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: New Feature
>  Components: AMQP Features Test
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>
> Add a new test set which will run on all client shims which will test 
> messaging features:
> * Anonymous Relay
> * Credit management
> * Time to Live (TTL)
> * Queue browsing
> * Container ID
> * Standard Connection Properties
> (and possibly more...)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-74) Add command-line switch to enable SASL

[Kim van der Riet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDIT-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-74:
---
Affects Version/s: 0.1.0

> Add command-line switch to enable SASL
> --
>
> Key: QPIDIT-74
> URL: https://issues.apache.org/jira/browse/QPIDIT-74
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Minor
>
> Currently, SASL is not used for tests. Create a switch to enable SASL and/or 
> control its mechanisms. This will entail adding this to the broker_properties 
> module, as well as to all shims. The SASL details will need to be sent to the 
> shim in JSON format.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-78) Add AMQP local transaction test

[Kim van der Riet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDIT-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-78:
---
Affects Version/s: 0.1.0

> Add AMQP local transaction test
> ---
>
> Key: QPIDIT-78
> URL: https://issues.apache.org/jira/browse/QPIDIT-78
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: New Feature
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Minor
>
> Add an AMQP local transaction test. This will test a local transaction where 
> the scope of the transaction will be limited to a single client. Multiple 
> actions may be performed on multiple queues and need to comply with the 
> atomic constraints imposed by the transaction.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-39) Make qpid-jms-client version a parameter of Maven build

[Kim van der Riet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDIT-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-39:
---
Affects Version/s: 0.1.0

> Make qpid-jms-client version a parameter of Maven build
> ---
>
> Key: QPIDIT-39
> URL: https://issues.apache.org/jira/browse/QPIDIT-39
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Improvement
>  Components: Qpid Jms Shim
>Affects Versions: 0.1.0
>Reporter: Jiri Daněk
>Assignee: Kim van der Riet
>Priority: Critical
>
> I wish to be able to change the version of qpid-jms-client library used in 
> the jms shim. This would allow running the test with older versions of the 
> library and also with various proprietary builds of the library.
> One possible way to implement this would be to make the library version a 
> maven attribute and to switch between geronimo-jms_1.1_spec and the 2.0 
> version using maven profile, e.g.:
> {noformat}
> mvn -Pjms11 -Dqpid-jms-client.version=0.11.0.mycompany-1 package
> mvn -Pjms20 -Dqpid-jms-client.version=0.20.0 package
> {noformat}
> On a related task, it might be helpful to use Maven to produce an uberjar, a 
> jar that bundles all runtime dependencies in itself. It would simplify 
> running the shim from the test program, because then there would be no 
> classpath to deal with.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-64) Add command-line controls for AMQP_large_content_test to control size

[Kim van der Riet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDIT-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-64:
---
Affects Version/s: 0.1.0

> Add command-line controls for AMQP_large_content_test to control size
> -
>
> Key: QPIDIT-64
> URL: https://issues.apache.org/jira/browse/QPIDIT-64
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Improvement
>  Components: AMQP Large Content Test
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Minor
>
> Add a command-line parameter to control the inclusion/exclusion of the size 
> of the messages to be tested in MBytes. Currently, the test uses 1, 10, 100 
> (MBytes) for testing and is fixed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-65) Add command-line controls to JMS_hdrs_props_test to control test more precisely

[Kim van der Riet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDIT-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-65:
---
Affects Version/s: 0.1.0

> 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
>
> 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
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-61) Condense common code from the Python tests into a test module.

[Kim van der Riet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDIT-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-61:
---
Affects Version/s: 0.1.0

> 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
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-58) Add auto-detection of shims

[Kim van der Riet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDIT-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-58:
---
Affects Version/s: 0.1.0

> Add auto-detection of shims
> ---
>
> Key: QPIDIT-58
> URL: https://issues.apache.org/jira/browse/QPIDIT-58
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Minor
>
> Currently the shims are included by hard-coding paths into the test files. A 
> small change in directory structure will enable the shims to be auto-detected 
> at run-time and included if present.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-12) Implement AMQP type array for QpidJms shim

[Kim van der Riet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDIT-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-12:
---
Affects Version/s: 0.1.0

> Implement AMQP type array for QpidJms shim
> --
>
> Key: QPIDIT-12
> URL: https://issues.apache.org/jira/browse/QPIDIT-12
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Task
>  Components: Qpid Jms Shim
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Minor
>
> The AMQP type array has not been implemented in the QpidJms shim.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-107) Add support for JMS message properties in ProtonCpp shim

[Kim van der Riet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDIT-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-107:

Affects Version/s: (was: 0.2.0)
   0.1.0

> Add support for JMS message properties in ProtonCpp shim
> 
>
> Key: QPIDIT-107
> URL: https://issues.apache.org/jira/browse/QPIDIT-107
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Task
>  Components: Proton C++ Shim
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>
> Currently the properties section of the test is disabled because the C++ 
> bindings did not support access to message properties at the time the shim 
> was first written.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-105) Getting started with AMQP.Net Lite in Fedora

[Kim van der Riet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDIT-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-105:

Affects Version/s: 0.1.0

> Getting started with AMQP.Net Lite in Fedora
> 
>
> Key: QPIDIT-105
> URL: https://issues.apache.org/jira/browse/QPIDIT-105
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: New Feature
>  Components: .Net Lite Shim
>Affects Versions: 0.1.0
> Environment: Fedora 25
> mono 4.4.2
>Reporter: Chuck Rolke
>Assignee: Kim van der Riet
>
> h4. Introduction
> With package mono version 4.4.2 installed on Fedora the system is capable of 
> compiling and running the AMQP.Net Lite shim tests. The remaining part of the 
> puzzle is acquiring a pre-compiled AMQP.Net Lite executable library. Here's 
> one solution.
> This note is not a feature request so much as it is a blog about one way to 
> do it.
> h4. Fetch AMQP.Net Lite 2.0.0 from NuGet
> Saved as file *get-lite.sh* in the top level directory it may be dot sourced 
> to pick up the definition of AMQPNETLITE_LIB_DIR.
> {noformat}
> #!/bin/bash
> #
> # file: get-lite.sh
> #
> litedir=amqpnetlite-lib-dir
> if [[ ! -d $litedir ]]; then
> mkdir $litedir
> cd$litedir
> wget https://www.nuget.org/api/v2/package/AMQPNetLite/2.0.0
> mv2.0.0 amqpnetlite.2.0.0.nupkg
> unzip   amqpnetlite.2.0.0.nupkg
> cd ..
> fi
> export AMQPNETLITE_LIB_DIR=`pwd`/$litedir/lib/net45
> {noformat}
> .h4 Build qpid-interop-test including AMQP.Net Lite
> Include the Lite library definition in the CMake command line
> {noformat}
> cmake -DAMQPNETLITE_LIB_DIR=${AMQPNETLITE_LIB_DIR} ...
> {noformat}
> Expect confirmation that the Lite library was picked up by CMake
> {noformat}
> -- BUILD_AMQPNETLITE = ON
> {noformat}
> h4. Run test with the AMQP.Net Lite shims
> Define the library location and specify the shims.
> {noformat}
> export 
> AMQPNETLITE_LIB_DIR=${QPID_INTEROP_TEST_HOME}/amqpnetlite-lib-dir/lib/net45
> ./src/python/qpid_interop_test/amqp_types_test.py \
> --include-shim ProtonCpp \
> --include-shim ProtonPython \
> --include-shim AmqpNetLite 
> {noformat}
> h4. Further integration
> This should get you started with the AMQP.Net Lite library. I've tried a few 
> things to auto-detect the library and use it if present. None of those 
> attempts is yet worthy.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (QPIDIT-105) Getting started with AMQP.Net Lite in Fedora

[Kim van der Riet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDIT-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet reassigned QPIDIT-105:
---

Assignee: Kim van der Riet

> Getting started with AMQP.Net Lite in Fedora
> 
>
> Key: QPIDIT-105
> URL: https://issues.apache.org/jira/browse/QPIDIT-105
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: New Feature
>  Components: .Net Lite Shim
> Environment: Fedora 25
> mono 4.4.2
>Reporter: Chuck Rolke
>Assignee: Kim van der Riet
>
> h4. Introduction
> With package mono version 4.4.2 installed on Fedora the system is capable of 
> compiling and running the AMQP.Net Lite shim tests. The remaining part of the 
> puzzle is acquiring a pre-compiled AMQP.Net Lite executable library. Here's 
> one solution.
> This note is not a feature request so much as it is a blog about one way to 
> do it.
> h4. Fetch AMQP.Net Lite 2.0.0 from NuGet
> Saved as file *get-lite.sh* in the top level directory it may be dot sourced 
> to pick up the definition of AMQPNETLITE_LIB_DIR.
> {noformat}
> #!/bin/bash
> #
> # file: get-lite.sh
> #
> litedir=amqpnetlite-lib-dir
> if [[ ! -d $litedir ]]; then
> mkdir $litedir
> cd$litedir
> wget https://www.nuget.org/api/v2/package/AMQPNetLite/2.0.0
> mv2.0.0 amqpnetlite.2.0.0.nupkg
> unzip   amqpnetlite.2.0.0.nupkg
> cd ..
> fi
> export AMQPNETLITE_LIB_DIR=`pwd`/$litedir/lib/net45
> {noformat}
> .h4 Build qpid-interop-test including AMQP.Net Lite
> Include the Lite library definition in the CMake command line
> {noformat}
> cmake -DAMQPNETLITE_LIB_DIR=${AMQPNETLITE_LIB_DIR} ...
> {noformat}
> Expect confirmation that the Lite library was picked up by CMake
> {noformat}
> -- BUILD_AMQPNETLITE = ON
> {noformat}
> h4. Run test with the AMQP.Net Lite shims
> Define the library location and specify the shims.
> {noformat}
> export 
> AMQPNETLITE_LIB_DIR=${QPID_INTEROP_TEST_HOME}/amqpnetlite-lib-dir/lib/net45
> ./src/python/qpid_interop_test/amqp_types_test.py \
> --include-shim ProtonCpp \
> --include-shim ProtonPython \
> --include-shim AmqpNetLite 
> {noformat}
> h4. Further integration
> This should get you started with the AMQP.Net Lite library. I've tried a few 
> things to auto-detect the library and use it if present. None of those 
> attempts is yet worthy.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-105) Getting started with AMQP.Net Lite in Fedora

[Kim van der Riet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDIT-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-105:

Affects Version/s: (was: 0.1.0)

> Getting started with AMQP.Net Lite in Fedora
> 
>
> Key: QPIDIT-105
> URL: https://issues.apache.org/jira/browse/QPIDIT-105
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: New Feature
>  Components: .Net Lite Shim
> Environment: Fedora 25
> mono 4.4.2
>Reporter: Chuck Rolke
>Assignee: Kim van der Riet
>
> h4. Introduction
> With package mono version 4.4.2 installed on Fedora the system is capable of 
> compiling and running the AMQP.Net Lite shim tests. The remaining part of the 
> puzzle is acquiring a pre-compiled AMQP.Net Lite executable library. Here's 
> one solution.
> This note is not a feature request so much as it is a blog about one way to 
> do it.
> h4. Fetch AMQP.Net Lite 2.0.0 from NuGet
> Saved as file *get-lite.sh* in the top level directory it may be dot sourced 
> to pick up the definition of AMQPNETLITE_LIB_DIR.
> {noformat}
> #!/bin/bash
> #
> # file: get-lite.sh
> #
> litedir=amqpnetlite-lib-dir
> if [[ ! -d $litedir ]]; then
> mkdir $litedir
> cd$litedir
> wget https://www.nuget.org/api/v2/package/AMQPNetLite/2.0.0
> mv2.0.0 amqpnetlite.2.0.0.nupkg
> unzip   amqpnetlite.2.0.0.nupkg
> cd ..
> fi
> export AMQPNETLITE_LIB_DIR=`pwd`/$litedir/lib/net45
> {noformat}
> .h4 Build qpid-interop-test including AMQP.Net Lite
> Include the Lite library definition in the CMake command line
> {noformat}
> cmake -DAMQPNETLITE_LIB_DIR=${AMQPNETLITE_LIB_DIR} ...
> {noformat}
> Expect confirmation that the Lite library was picked up by CMake
> {noformat}
> -- BUILD_AMQPNETLITE = ON
> {noformat}
> h4. Run test with the AMQP.Net Lite shims
> Define the library location and specify the shims.
> {noformat}
> export 
> AMQPNETLITE_LIB_DIR=${QPID_INTEROP_TEST_HOME}/amqpnetlite-lib-dir/lib/net45
> ./src/python/qpid_interop_test/amqp_types_test.py \
> --include-shim ProtonCpp \
> --include-shim ProtonPython \
> --include-shim AmqpNetLite 
> {noformat}
> h4. Further integration
> This should get you started with the AMQP.Net Lite library. I've tried a few 
> things to auto-detect the library and use it if present. None of those 
> attempts is yet worthy.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPIDIT-107) Add support for JMS message properties in ProtonCpp shim

[Kim van der Riet (JIRA)]

Kim van der Riet created QPIDIT-107:
---

 Summary: Add support for JMS message properties in ProtonCpp shim
 Key: QPIDIT-107
 URL: https://issues.apache.org/jira/browse/QPIDIT-107
 Project: Apache QPID Interoperability Test Suite
  Issue Type: Task
  Components: Proton C++ Shim
Affects Versions: 0.2.0
Reporter: Kim van der Riet
Assignee: Kim van der Riet


Currently the properties section of the test is disabled because the C++ 
bindings did not support access to message properties at the time the shim was 
first written.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (PROTON-1741) selected_recv example doesn't work

[Gordon Sim (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gordon Sim resolved PROTON-1741.

Resolution: Fixed

> selected_recv example doesn't work
> --
>
> Key: PROTON-1741
> URL: https://issues.apache.org/jira/browse/PROTON-1741
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: examples
>Reporter: Gordon Sim
>
> The cpp example explicitly sets the selector to be binary, which is 
> incorrect. It should be a string.
> For the python example, if run with python 2, the selector string will also 
> be binary as it isn't explicitly marked as utf8.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (PROTON-1742) there is no send example that works well with selected_recv

[Gordon Sim (JIRA)]

Gordon Sim created PROTON-1742:
--

 Summary: there is no send example that works well with 
selected_recv
 Key: PROTON-1742
 URL: https://issues.apache.org/jira/browse/PROTON-1742
 Project: Qpid Proton
  Issue Type: Improvement
Reporter: Gordon Sim
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1741) selected_recv example doesn't work

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on PROTON-1741:
-

Commit 833859f664ad5e75071495ed0ca9c7ab4e4865d0 in qpid-proton's branch 
refs/heads/master from [~gsim]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=833859f ]

PROTON-1741: send selector as string


> selected_recv example doesn't work
> --
>
> Key: PROTON-1741
> URL: https://issues.apache.org/jira/browse/PROTON-1741
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: examples
>Reporter: Gordon Sim
>
> The cpp example explicitly sets the selector to be binary, which is 
> incorrect. It should be a string.
> For the python example, if run with python 2, the selector string will also 
> be binary as it isn't explicitly marked as utf8.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (PROTON-1741) selected_recv example doesn't work

[Gordon Sim (JIRA)]

Gordon Sim created PROTON-1741:
--

 Summary: selected_recv example doesn't work
 Key: PROTON-1741
 URL: https://issues.apache.org/jira/browse/PROTON-1741
 Project: Qpid Proton
  Issue Type: Bug
  Components: examples
Reporter: Gordon Sim


The cpp example explicitly sets the selector to be binary, which is incorrect. 
It should be a string.

For the python example, if run with python 2, the selector string will also be 
binary as it isn't explicitly marked as utf8.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (QPID-8032) [AMQP1.0] AsyncAutoCommitTransaction optimisation

[Keith Wall (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-8032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keith Wall reassigned QPID-8032:


Assignee: Keith Wall

> [AMQP1.0] AsyncAutoCommitTransaction optimisation
> -
>
> Key: QPID-8032
> URL: https://issues.apache.org/jira/browse/QPID-8032
> Project: Qpid
>  Issue Type: Improvement
>  Components: Broker-J
>Reporter: Keith Wall
>Assignee: Keith Wall
> Fix For: qpid-java-broker-7.0.1
>
>
> Some AMQP 1.0 messaging use-cases would benefit from the 
> {{AsyncAutoCommitTransactions}} optimisation that is already in use on the 
> older protocols.
> For instance, for a publisher sending persistent settled messages, currently 
> each message is written to disk and sync before the next message is the 
> buffer is processed,.  With this optimisation, the syncs would be allowed to 
> coalesce.  
> Care needs to be taken when the work includes actions that aren't 
> non-transactional transfers to ensure that transactions remain ACID.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-6933) Factor out a JMS client neutral messaging test suite from system tests

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16323789#comment-16323789
 ] 

ASF subversion and git services commented on QPID-6933:
---

Commit cb36ee7b0cdc26416ef921a0f8e17cd0ef70bdec 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=cb36ee7 ]

QPID-6933: [System Tests] Remove AMQP 0-x client specific ConnectionTest after 
moving test into client system tests


> Factor out a JMS client neutral messaging test suite from system tests
> --
>
> Key: QPID-6933
> URL: https://issues.apache.org/jira/browse/QPID-6933
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Tests
>Reporter: Keith Wall
>Assignee: Alex Rudyy
>
> The existing system testsuite is in a poor state.
> * It is poorly structured
> * Mixes different types of test.  i.e. messaging behaviour with those that 
> test features of the Java Broker (e.g. REST).
> * Many of the tests refer directly to the implementation classes of the Qpid 
> Client 0-8..0-10 client meaning the tests cannot be run using the new client.
> As a first step, we want to factor out a separate messaging system test suite:
> * The tests in this suite will be JMS client neutral.
> * Written in terms of JNDI/JMS client
> * Configurations/Broker observations will be performed via a clean 
> Broker-neutral facade. For instance
> **  a mechanism to cause the queue to be created of a particular type.
> ** a mechanism to observe a queue depth.
> * The tests will be classified by feature (to be defined)
> * The classification system will be used to drive an exclusion feature (to be 
> defined).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Closed] (QPID-8040) [Broker-J] Uncaught java.nio.channels.CancelledKeyException seen during Broker shutdown

[Alex Rudyy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-8040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy closed QPID-8040.

Resolution: Fixed

Resolving JIRA as the required changes have been implemented and ported into 
7.0.x branch

> [Broker-J] Uncaught java.nio.channels.CancelledKeyException seen during 
> Broker shutdown
> ---
>
> Key: QPID-8040
> URL: https://issues.apache.org/jira/browse/QPID-8040
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.1.0
>Reporter: Keith Wall
>Assignee: Keith Wall
>Priority: Minor
> Fix For: qpid-java-broker-7.0.1
>
> Attachments: 
> TEST-org.apache.qpid.systest.management.amqp.AmqpManagementTest.testInvokeOperationReturningMap
>
>
> The following exception was trapped by the UncaughtExceptionHandler during a 
> shutdown of the Broker.  The would have caused a abnormal termination.   I 
> expect it could also happen during a HA virtualhost mastership change too.
> This code hasn't changed, so I think the problem is probably longstanding.
> {noformat}
> 2017-11-10 20:30:04,540  DEBUG [QpidJMS Connection Executor: 
> ID:51dec5e7-faf9-4b92-89ec-16396a27a101:1] o.a.q.j.u.ThreadPoolUtils Shutdown 
> of ExecutorService: 
> java.util.concurrent.ScheduledThreadPoolExecutor@6fbbe33[Terminated, pool 
> size = 0, active threads = 0, queued tasks = 0, completed tasks = 24] is 
> shutdown: true and terminated: true took: 0.000 seconds.
> 2017-11-10 20:30:04,540  DEBUG [VirtualHostNode-test-Config] 
> o.a.q.s.c.u.TaskExecutorImpl Stopping task executor 
> virtualhost-test-preferences
> 2017-11-10 20:30:04,544  DEBUG [VirtualHostNode-test-Config] 
> o.a.q.s.c.u.TaskExecutorImpl Task executor is stopped
> 2017-11-10 20:30:04,543  ERROR [Selector-Port-amqp] 
> o.a.q.t.u.InternalBrokerHolder Uncaught exception from thread 
> Selector-Port-amqp
> java.nio.channels.CancelledKeyException: null
>   at sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:73)
>   at sun.nio.ch.SelectionKeyImpl.interestOps(SelectionKeyImpl.java:82)
>   at 
> java.nio.channels.spi.AbstractSelectableChannel.register(AbstractSelectableChannel.java:204)
>   at 
> org.apache.qpid.server.transport.SelectorThread$SelectionTask.processSelectionKeys(SelectorThread.java:240)
>   at 
> org.apache.qpid.server.transport.SelectorThread$SelectionTask.performSelect(SelectorThread.java:326)
>   at 
> org.apache.qpid.server.transport.SelectorThread$SelectionTask.run(SelectorThread.java:97)
>   at 
> org.apache.qpid.server.transport.SelectorThread.run(SelectorThread.java:528)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at 
> org.apache.qpid.server.bytebuffer.QpidByteBufferFactory.lambda$null$0(QpidByteBufferFactory.java:464)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org