[jira] [Resolved] (DISPATCH-527) The $displayname address is currently available. It should not be available to external users
[ https://issues.apache.org/jira/browse/DISPATCH-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-527. Resolution: Fixed > The $displayname address is currently available. It should not be available > to external users > - > > Key: DISPATCH-527 > URL: https://issues.apache.org/jira/browse/DISPATCH-527 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 0.7.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy > Fix For: 0.8.0 > > > The $displayname service is currently exposed. Unexpose it so that people > cannot communicate to this address. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-42) Split JMS message test into two separate tests: message bodies, and message headers/properties
[ https://issues.apache.org/jira/browse/QPIDIT-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576365#comment-15576365 ] ASF subversion and git services commented on QPIDIT-42: --- Commit 424d23636b8ba4e4e02b27585c5214b9c1bf937f 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=424d236 ] QPIDIT-42: JMS headers/properties test finalized. > Split JMS message test into two separate tests: message bodies, and message > headers/properties > -- > > Key: QPIDIT-42 > URL: https://issues.apache.org/jira/browse/QPIDIT-42 > Project: Apache QPID IT > Issue Type: Improvement > Components: JmsMessageTest, Qpid Jms Shim >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > The current JMS messages test includes both JMS message bodies and JMS > message headers and properties. The test is structured in a way that all the > headers and properties test run on each of the JMS body combinations. This > results in an excessively long test, and does not improve coverage. > By splitting the tests into a separate JMS message test and JMS > headers/properties test, this problem can be eliminated. The message test > will be far shorter and can specialize its tests for message bodies; > similarly the headers/properties test can also specialize. Any expansion of > the number of tests won't result in a massive increase in the number of tests > that run (as is currently the case). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPIDIT-42) Split JMS message test into two separate tests: message bodies, and message headers/properties
Kim van der Riet created QPIDIT-42: -- Summary: Split JMS message test into two separate tests: message bodies, and message headers/properties Key: QPIDIT-42 URL: https://issues.apache.org/jira/browse/QPIDIT-42 Project: Apache QPID IT Issue Type: Improvement Components: JmsMessageTest, Qpid Jms Shim Reporter: Kim van der Riet Assignee: Kim van der Riet The current JMS messages test includes both JMS message bodies and JMS message headers and properties. The test is structured in a way that all the headers and properties test run on each of the JMS body combinations. This results in an excessively long test, and does not improve coverage. By splitting the tests into a separate JMS message test and JMS headers/properties test, this problem can be eliminated. The message test will be far shorter and can specialize its tests for message bodies; similarly the headers/properties test can also specialize. Any expansion of the number of tests won't result in a massive increase in the number of tests that run (as is currently the case). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPIDIT-41) Rearrange test directory structure to better organize tests and shims
[
https://issues.apache.org/jira/browse/QPIDIT-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet resolved QPIDIT-41.
Resolution: Fixed
> Rearrange test directory structure to better organize tests and shims
> -
>
> Key: QPIDIT-41
> URL: https://issues.apache.org/jira/browse/QPIDIT-41
> Project: Apache QPID IT
> Issue Type: Improvement
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>
> The current directory structure for qpid-interop-test needs some improvements
> to make it more consistent and easier to manage shims and tests:
> * All tests should reside in the same directory
> (src/python/qpid-interop-test), and the test name is the key to the shims
> directory structure for finding the Sender and Receiver shims.
> * JMS shims should be located in a directory named identically to the name of
> the test for which it is written, and located in
> shims/qpid-jms/src/main/java/org/apace/qpid/qpid_interop_test. There are only
> two shims, called Sender.java and Receiver.java. The Java package is
> consequently "org.apache.qpid.interop_test..
> * Python shims should be located in a directory named identically to the name
> of the test for which it is written, and located in
> shims/qpid-proton-python/src. There are only two shims, called Sender.py and
> Receiver.py.
> * C++ shims should be located in a directory named identically to the name of
> the test for which it is written, and located in
> shims/qpid-proton-cpp/src/qpidit. There are only two shims, called
> Sender.{hpp,cpp} and Receiver.{hpp,cpp}. The shim namespace is conseqnently
> qpidit..
> {noformat}
> qpid-interop-test
> +-shims
> | +-qpid-jms
> | | +-src
> | | +-main
> | | +-java
> | | +-org
> | | +-apache
> | | +-qpid
> | | +-qpid-interop-test
> | | +-
> | | | +-Receiver.java
> | | | +-Sender.java
> | | +-
> | | +-Receiver.java
> | | +-Sender.java
> | +-qpid-proton-cpp
> | | +-src
> | | +-qpidit
> | | +-
> | | | +- Receiver.cpp
> | | | +- Receiver.hpp
> | | | +- Sender.cpp
> | | | +- Sender.hpp
> | | +-
> | | +- Receiver.cpp
> | | +- Receiver.hpp
> | | +- Sender.cpp
> | | +- Sender.hpp
> | +-qpid-proton-python
> | +-src
> | +-
> | | +-Sender.py
> | | +-Receiver.py
> | +-
> | +-Sender.py
> | +-Receiver.py
> +-src
> +-python
> +-qpid-interop-test
> +-
> +-
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-527) The $displayname address is currently available. It should not be available to external users
[ https://issues.apache.org/jira/browse/DISPATCH-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576349#comment-15576349 ] ASF subversion and git services commented on DISPATCH-527: -- Commit 27b2c91ea110a2828db49c5790ad0b275473d99f in qpid-dispatch's branch refs/heads/master from [~ganeshmurthy] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=27b2c91 ] DISPATCH-527 - Removed address "displayname". This address cannot be publicly accessed anymore > The $displayname address is currently available. It should not be available > to external users > - > > Key: DISPATCH-527 > URL: https://issues.apache.org/jira/browse/DISPATCH-527 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 0.7.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy > Fix For: 0.8.0 > > > The $displayname service is currently exposed. Unexpose it so that people > cannot communicate to this address. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-527) The $displayname address is currently available. It should not be available to external users
[ https://issues.apache.org/jira/browse/DISPATCH-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576297#comment-15576297 ] ASF subversion and git services commented on DISPATCH-527: -- Commit 3774f5d73c865f03ba5ff44a3465d49370aa48ed in qpid-dispatch's branch refs/heads/master from [~ganeshmurthy] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=3774f5d ] DISPATCH-527 - Removed address > The $displayname address is currently available. It should not be available > to external users > - > > Key: DISPATCH-527 > URL: https://issues.apache.org/jira/browse/DISPATCH-527 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 0.7.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy > Fix For: 0.8.0 > > > The $displayname service is currently exposed. Unexpose it so that people > cannot communicate to this address. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1325) Python "buffer" type in Message body should map to a known encoding type
[
https://issues.apache.org/jira/browse/PROTON-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway updated PROTON-1325:
Fix Version/s: 0.16.0
> Python "buffer" type in Message body should map to a known encoding type
>
>
> Key: PROTON-1325
> URL: https://issues.apache.org/jira/browse/PROTON-1325
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: 0.14.0
>Reporter: Brian Bouterse
>Assignee: Alan Conway
> Fix For: 0.16.0
>
>
> If I try to send a message like this it fails due to an encoding error.
> from proton import Message
> Message(body=buffer('asdf'))
> If you try to send this and fail to specify an encoding, you will get an
> encoding traceback like this one.
> Traceback (most recent call last):
> File "/usr/lib64/python2.7/threading.py", line 804, in __bootstrap_inner
> self.run()
> File "/home/vagrant/devel/kombu/kombu/transport/qpid.py", line 1367, in run
> Container(HelloWorld("localhost:5672", self._w,
> self.outbound_messages)).run()
> File "/usr/lib64/python2.7/site-packages/proton/reactor.py", line 133, in
> run
> while self.process(): pass
> File "/usr/lib64/python2.7/site-packages/proton/reactor.py", line 159, in
> process
> self._check_errors()
> File "/usr/lib64/python2.7/site-packages/proton/reactor.py", line 155, in
> _check_errors
> _compat.raise_(exc, value, tb)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 4022, in
> dispatch
> ev.dispatch(self.handler)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3934, in
> dispatch
> self.dispatch(h, type)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3931, in
> dispatch
> result = dispatch(handler, type.method, self)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3812, in
> dispatch
> return m(*args)
> File "/usr/lib64/python2.7/site-packages/proton/handlers.py", line 40, in
> on_link_flow
> self.on_sendable(event)
> File "/usr/lib64/python2.7/site-packages/proton/handlers.py", line 62, in
> on_sendable
> dispatch(self.delegate, 'on_sendable', event)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3812, in
> dispatch
> return m(*args)
> File "/home/vagrant/devel/kombu/kombu/transport/qpid.py", line 1351, in
> on_sendable
> event.sender.send(message)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2997, in
> send
> return obj.send(self, tag=tag)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 1116, in
> send
> encoded = self.encode()
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 1099, in
> encode
> self._pre_encode()
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 843, in
> _pre_encode
> body.put_object(self.body)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2271, in
> put_object
> putter(self, obj)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2114, in
> put_dict
> self.put_object(v)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2270, in
> put_object
> putter = self.put_mappings[obj.__class__]
> KeyError:
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1325) Python "buffer" type in Message body should map to a known encoding type
[
https://issues.apache.org/jira/browse/PROTON-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway resolved PROTON-1325.
-
Resolution: Fixed
> Python "buffer" type in Message body should map to a known encoding type
>
>
> Key: PROTON-1325
> URL: https://issues.apache.org/jira/browse/PROTON-1325
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: 0.14.0
>Reporter: Brian Bouterse
>Assignee: Alan Conway
>
> If I try to send a message like this it fails due to an encoding error.
> from proton import Message
> Message(body=buffer('asdf'))
> If you try to send this and fail to specify an encoding, you will get an
> encoding traceback like this one.
> Traceback (most recent call last):
> File "/usr/lib64/python2.7/threading.py", line 804, in __bootstrap_inner
> self.run()
> File "/home/vagrant/devel/kombu/kombu/transport/qpid.py", line 1367, in run
> Container(HelloWorld("localhost:5672", self._w,
> self.outbound_messages)).run()
> File "/usr/lib64/python2.7/site-packages/proton/reactor.py", line 133, in
> run
> while self.process(): pass
> File "/usr/lib64/python2.7/site-packages/proton/reactor.py", line 159, in
> process
> self._check_errors()
> File "/usr/lib64/python2.7/site-packages/proton/reactor.py", line 155, in
> _check_errors
> _compat.raise_(exc, value, tb)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 4022, in
> dispatch
> ev.dispatch(self.handler)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3934, in
> dispatch
> self.dispatch(h, type)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3931, in
> dispatch
> result = dispatch(handler, type.method, self)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3812, in
> dispatch
> return m(*args)
> File "/usr/lib64/python2.7/site-packages/proton/handlers.py", line 40, in
> on_link_flow
> self.on_sendable(event)
> File "/usr/lib64/python2.7/site-packages/proton/handlers.py", line 62, in
> on_sendable
> dispatch(self.delegate, 'on_sendable', event)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3812, in
> dispatch
> return m(*args)
> File "/home/vagrant/devel/kombu/kombu/transport/qpid.py", line 1351, in
> on_sendable
> event.sender.send(message)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2997, in
> send
> return obj.send(self, tag=tag)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 1116, in
> send
> encoded = self.encode()
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 1099, in
> encode
> self._pre_encode()
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 843, in
> _pre_encode
> body.put_object(self.body)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2271, in
> put_object
> putter(self, obj)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2114, in
> put_dict
> self.put_object(v)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2270, in
> put_object
> putter = self.put_mappings[obj.__class__]
> KeyError:
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1325) Python "buffer" type in Message body should map to a known encoding type
[
https://issues.apache.org/jira/browse/PROTON-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576167#comment-15576167
]
ASF subversion and git services commented on PROTON-1325:
-
Commit 05deba72edebd0cf1e7bf148ba7e99ab2fb62bfe in qpid-proton's branch
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=05deba7 ]
PROTON-1325: Python "buffer" type should map to AMQP "binary"
Add an automatic mapping from a python buffer object to the AMQP binary type.
In the other direction, AMQP "binary" maps to the python "bytes" or "str" type,
as before.
> Python "buffer" type in Message body should map to a known encoding type
>
>
> Key: PROTON-1325
> URL: https://issues.apache.org/jira/browse/PROTON-1325
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: 0.14.0
>Reporter: Brian Bouterse
>Assignee: Alan Conway
>
> If I try to send a message like this it fails due to an encoding error.
> from proton import Message
> Message(body=buffer('asdf'))
> If you try to send this and fail to specify an encoding, you will get an
> encoding traceback like this one.
> Traceback (most recent call last):
> File "/usr/lib64/python2.7/threading.py", line 804, in __bootstrap_inner
> self.run()
> File "/home/vagrant/devel/kombu/kombu/transport/qpid.py", line 1367, in run
> Container(HelloWorld("localhost:5672", self._w,
> self.outbound_messages)).run()
> File "/usr/lib64/python2.7/site-packages/proton/reactor.py", line 133, in
> run
> while self.process(): pass
> File "/usr/lib64/python2.7/site-packages/proton/reactor.py", line 159, in
> process
> self._check_errors()
> File "/usr/lib64/python2.7/site-packages/proton/reactor.py", line 155, in
> _check_errors
> _compat.raise_(exc, value, tb)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 4022, in
> dispatch
> ev.dispatch(self.handler)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3934, in
> dispatch
> self.dispatch(h, type)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3931, in
> dispatch
> result = dispatch(handler, type.method, self)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3812, in
> dispatch
> return m(*args)
> File "/usr/lib64/python2.7/site-packages/proton/handlers.py", line 40, in
> on_link_flow
> self.on_sendable(event)
> File "/usr/lib64/python2.7/site-packages/proton/handlers.py", line 62, in
> on_sendable
> dispatch(self.delegate, 'on_sendable', event)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3812, in
> dispatch
> return m(*args)
> File "/home/vagrant/devel/kombu/kombu/transport/qpid.py", line 1351, in
> on_sendable
> event.sender.send(message)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2997, in
> send
> return obj.send(self, tag=tag)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 1116, in
> send
> encoded = self.encode()
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 1099, in
> encode
> self._pre_encode()
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 843, in
> _pre_encode
> body.put_object(self.body)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2271, in
> put_object
> putter(self, obj)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2114, in
> put_dict
> self.put_object(v)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2270, in
> put_object
> putter = self.put_mappings[obj.__class__]
> KeyError:
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton issue #83: [Go binding] Replaced c handler based flowcontroller ...
Github user alanconway commented on the issue: https://github.com/apache/qpid-proton/pull/83 Add module tests to proton_test.go. As you can see right now it is empty which is not ideal (!) The actual tests are in electron/electron_tests.go and the examples are also auto-tested by ctest. We should really have unit tests for proton itself though so if you want to start that off, please do :) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPIDJMS-214) update to proton-j 0.15.0
[ https://issues.apache.org/jira/browse/QPIDJMS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPIDJMS-214. Resolution: Fixed > update to proton-j 0.15.0 > - > > Key: QPIDJMS-214 > URL: https://issues.apache.org/jira/browse/QPIDJMS-214 > Project: Qpid JMS > Issue Type: Improvement > Components: qpid-jms-client >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > Fix For: 0.20.0 > > > update to the latest proton-j release -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-201) Consumer handling of no drain response can unsubscribe a durable subscription
[ https://issues.apache.org/jira/browse/QPIDJMS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576093#comment-15576093 ] ASF subversion and git services commented on QPIDJMS-201: - Commit 22a517d76f67dcae61318ff858781066d6855ed3 in qpid-jms's branch refs/heads/master from Robert Gemmell [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=22a517d ] QPIDJMS-214: fixup and re-enable tests for QPIDJMS-201 following the proton-j update > Consumer handling of no drain response can unsubscribe a durable subscription > - > > Key: QPIDJMS-201 > URL: https://issues.apache.org/jira/browse/QPIDJMS-201 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Affects Versions: 0.10.0 >Reporter: Timothy Bish >Assignee: Timothy Bish > Fix For: 0.11.0 > > > When a MessageConsumer fails to receive a response to a drain request it > closes the consumer instance which triggers the link to be closed, if that > happens to be a consumer on a durable subscription it also results in the > subscription being unsubscribed. The handler needs to detach the receiver in > this case instead of closing it. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-214) update to proton-j 0.15.0
[ https://issues.apache.org/jira/browse/QPIDJMS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576092#comment-15576092 ] ASF subversion and git services commented on QPIDJMS-214: - Commit 22a517d76f67dcae61318ff858781066d6855ed3 in qpid-jms's branch refs/heads/master from Robert Gemmell [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=22a517d ] QPIDJMS-214: fixup and re-enable tests for QPIDJMS-201 following the proton-j update > update to proton-j 0.15.0 > - > > Key: QPIDJMS-214 > URL: https://issues.apache.org/jira/browse/QPIDJMS-214 > Project: Qpid JMS > Issue Type: Improvement > Components: qpid-jms-client >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > Fix For: 0.20.0 > > > update to the latest proton-j release -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1326) Compilation failures against OpenSSL v1.1.0
[ https://issues.apache.org/jira/browse/PROTON-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576078#comment-15576078 ] Ken Giusti commented on PROTON-1326: fyi: Totally untested, but there seems to be a new API that allows access to those internal structure fields: int DH_set0_pqg(DH *dh, BIGNUM *p, BIGNUM *q, BIGNUM *g); > Compilation failures against OpenSSL v1.1.0 > --- > > Key: PROTON-1326 > URL: https://issues.apache.org/jira/browse/PROTON-1326 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.14.0, 0.15.0 >Reporter: Ken Giusti > Fix For: 0.16.0 > > > Openssl changes the API in a way that breaks proton's openssl implementation. > Proton/C can not compile against Openssl version 1.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton pull request #83: [Go binding] Replaced c handler based flowcont...
Github user astitcher closed the pull request at: https://github.com/apache/qpid-proton/pull/83 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1327) Go binding should not use any proton-c handlers
[ https://issues.apache.org/jira/browse/PROTON-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-1327. - Resolution: Fixed Fix Version/s: 0.16.0 > Go binding should not use any proton-c handlers > --- > > Key: PROTON-1327 > URL: https://issues.apache.org/jira/browse/PROTON-1327 > Project: Qpid Proton > Issue Type: Improvement > Components: go-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.16.0 > > > The go binding studiously avoids using the proton-c reactor infrastructure > except in one place: It uses the proton-c flowcontroller handler for flow > control (if configured). > The flow control handler is very simple so it can be simply implemented in > pure go. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1327) Go binding should not use any proton-c handlers
[ https://issues.apache.org/jira/browse/PROTON-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575982#comment-15575982 ] ASF subversion and git services commented on PROTON-1327: - Commit cd011b6b2927f9a62b63884db723a496d54fe604 in qpid-proton's branch refs/heads/master from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=cd011b6 ] PROTON-1327: [Go binding] Replaced c handler based flowcontroller with native go - The go binding now has no dependency on the proton-c reactor code > Go binding should not use any proton-c handlers > --- > > Key: PROTON-1327 > URL: https://issues.apache.org/jira/browse/PROTON-1327 > Project: Qpid Proton > Issue Type: Improvement > Components: go-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > > The go binding studiously avoids using the proton-c reactor infrastructure > except in one place: It uses the proton-c flowcontroller handler for flow > control (if configured). > The flow control handler is very simple so it can be simply implemented in > pure go. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1327) Go binding should not use any proton-c handlers
Andrew Stitcher created PROTON-1327: --- Summary: Go binding should not use any proton-c handlers Key: PROTON-1327 URL: https://issues.apache.org/jira/browse/PROTON-1327 Project: Qpid Proton Issue Type: Improvement Components: go-binding Reporter: Andrew Stitcher Assignee: Andrew Stitcher The go binding studiously avoids using the proton-c reactor infrastructure except in one place: It uses the proton-c flowcontroller handler for flow control (if configured). The flow control handler is very simple so it can be simply implemented in pure go. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1302) Don't depend on proton-c for OS services (use std library)
[ https://issues.apache.org/jira/browse/PROTON-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-1302. - Resolution: Fixed Fix Version/s: 0.15.0 > Don't depend on proton-c for OS services (use std library) > -- > > Key: PROTON-1302 > URL: https://issues.apache.org/jira/browse/PROTON-1302 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.15.0 > > > For example: > * timestamp::now() uses pn_timestamp_now() but this is part of the platform > code of proton-c and the C++ binding should not depend on it. > * Getting an error string from a failed listener relies on getting a pn_io_t > (from the platform code) from the pn_reactor -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1304) SSL code shouldn't need to know the time (shouldn't use the platform dependent parts of proton-c)
[ https://issues.apache.org/jira/browse/PROTON-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-1304. - Resolution: Fixed Fix Version/s: 0.15.0 > SSL code shouldn't need to know the time (shouldn't use the platform > dependent parts of proton-c) > - > > Key: PROTON-1304 > URL: https://issues.apache.org/jira/browse/PROTON-1304 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.15.0 > > > Currently the interface to OpenSSL keeps it's own cache of sessions separate > from the cache held in OpenSSL itself. > It needs to be able to purge this cache when the entries expire, so it needs > to know the time to figure out how old the cache entries are. > If we eliminate this cache and just use the underlying OpenSSL cache then we > wouldn't need to know the time and this code would be platform independent > (or at least as platform independent as OpenSSL code itself). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1303) Don't use the proton-c url parser
[ https://issues.apache.org/jira/browse/PROTON-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-1303. - Resolution: Fixed Fix Version/s: 0.15.0 > Don't use the proton-c url parser > - > > Key: PROTON-1303 > URL: https://issues.apache.org/jira/browse/PROTON-1303 > Project: Qpid Proton > Issue Type: Improvement > Components: go-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.15.0 > > > Go has it's own standard url parser - it doesn't need to use the rather odd > and somewhat error prone parser in proton-c. > It will be useful to provide some ability to set appropriate defaults for > supplied amqp urls though. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1325) Python "buffer" type in Message body should map to a known encoding type
[
https://issues.apache.org/jira/browse/PROTON-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575929#comment-15575929
]
Alan Conway commented on PROTON-1325:
-
To be clear: I'm planning to treat the python type 'buffer' like the python 3
type 'bytes' which in python 2 is called 'str' (which really means bytes) and
all of the above converting to the AMQP 'binary' type.
> Python "buffer" type in Message body should map to a known encoding type
>
>
> Key: PROTON-1325
> URL: https://issues.apache.org/jira/browse/PROTON-1325
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: 0.14.0
>Reporter: Brian Bouterse
>Assignee: Alan Conway
>
> If I try to send a message like this it fails due to an encoding error.
> from proton import Message
> Message(body=buffer('asdf'))
> If you try to send this and fail to specify an encoding, you will get an
> encoding traceback like this one.
> Traceback (most recent call last):
> File "/usr/lib64/python2.7/threading.py", line 804, in __bootstrap_inner
> self.run()
> File "/home/vagrant/devel/kombu/kombu/transport/qpid.py", line 1367, in run
> Container(HelloWorld("localhost:5672", self._w,
> self.outbound_messages)).run()
> File "/usr/lib64/python2.7/site-packages/proton/reactor.py", line 133, in
> run
> while self.process(): pass
> File "/usr/lib64/python2.7/site-packages/proton/reactor.py", line 159, in
> process
> self._check_errors()
> File "/usr/lib64/python2.7/site-packages/proton/reactor.py", line 155, in
> _check_errors
> _compat.raise_(exc, value, tb)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 4022, in
> dispatch
> ev.dispatch(self.handler)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3934, in
> dispatch
> self.dispatch(h, type)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3931, in
> dispatch
> result = dispatch(handler, type.method, self)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3812, in
> dispatch
> return m(*args)
> File "/usr/lib64/python2.7/site-packages/proton/handlers.py", line 40, in
> on_link_flow
> self.on_sendable(event)
> File "/usr/lib64/python2.7/site-packages/proton/handlers.py", line 62, in
> on_sendable
> dispatch(self.delegate, 'on_sendable', event)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3812, in
> dispatch
> return m(*args)
> File "/home/vagrant/devel/kombu/kombu/transport/qpid.py", line 1351, in
> on_sendable
> event.sender.send(message)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2997, in
> send
> return obj.send(self, tag=tag)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 1116, in
> send
> encoded = self.encode()
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 1099, in
> encode
> self._pre_encode()
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 843, in
> _pre_encode
> body.put_object(self.body)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2271, in
> put_object
> putter(self, obj)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2114, in
> put_dict
> self.put_object(v)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2270, in
> put_object
> putter = self.put_mappings[obj.__class__]
> KeyError:
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-214) update to proton-j 0.15.0
[ https://issues.apache.org/jira/browse/QPIDJMS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575892#comment-15575892 ] ASF subversion and git services commented on QPIDJMS-214: - Commit 4b01adf3a7ffb5c45e1c6d9353efa02cc3937542 in qpid-jms's branch refs/heads/master from Robert Gemmell [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=4b01adf ] QPIDJMS-214: update to proton-j 0.15.0 > update to proton-j 0.15.0 > - > > Key: QPIDJMS-214 > URL: https://issues.apache.org/jira/browse/QPIDJMS-214 > Project: Qpid JMS > Issue Type: Improvement > Components: qpid-jms-client >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > Fix For: 0.20.0 > > > update to the latest proton-j release -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid Proton 0.15.0 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid Proton 0.15.0. Apache Qpid Proton is a messaging library for the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org). It can be used in a wide range of messaging applications including brokers, clients, routers, bridges, proxies, and more. The release is available now from our website: http://qpid.apache.org/download.html Proton-J is also available via Maven Central: http://qpid.apache.org/maven.html Release notes can be found at: http://qpid.apache.org/releases/qpid-proton-0.15.0/release-notes.html Thanks to all involved, Robbie - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPIDJMS-214) update to proton-j 0.15.0
Robbie Gemmell created QPIDJMS-214: -- Summary: update to proton-j 0.15.0 Key: QPIDJMS-214 URL: https://issues.apache.org/jira/browse/QPIDJMS-214 Project: Qpid JMS Issue Type: Improvement Components: qpid-jms-client Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.20.0 update to the latest proton-j release -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPIDJMS-213) update Netty to 4.1.5
[ https://issues.apache.org/jira/browse/QPIDJMS-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPIDJMS-213. Resolution: Fixed > update Netty to 4.1.5 > - > > Key: QPIDJMS-213 > URL: https://issues.apache.org/jira/browse/QPIDJMS-213 > Project: Qpid JMS > Issue Type: Improvement > Components: qpid-jms-client >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 0.20.0 > > > Netty 4.1.x is now the 'main' current version and with important new > functionality it is getting increasingly used over time, we should update too. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1273) Can't run messenger tests simultaneously because of hard coded connection URL (127.0.0.1:12345)
[ https://issues.apache.org/jira/browse/PROTON-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1273: --- Issue Type: Test (was: Bug) > Can't run messenger tests simultaneously because of hard coded connection URL > (127.0.0.1:12345) > --- > > Key: PROTON-1273 > URL: https://issues.apache.org/jira/browse/PROTON-1273 > Project: Qpid Proton > Issue Type: Test > Components: proton-c >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.15.0 > > > This issue has tripped up our build testing and means you are unable to run > simultaneous tests on the same host. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1283) [proton-j] enable the transport impl to accept additional wrapper layers
[ https://issues.apache.org/jira/browse/PROTON-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1283: --- Summary: [proton-j] enable the transport impl to accept additional wrapper layers (was: enable the transport impl to accept additional wrapper layers) > [proton-j] enable the transport impl to accept additional wrapper layers > > > Key: PROTON-1283 > URL: https://issues.apache.org/jira/browse/PROTON-1283 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Andrew Buckley >Assignee: Robbie Gemmell > Fix For: 0.15.0 > > > This would add the ability for users to implement their own transport layers > and have it be usable by the library. > I made a pull request last week which you can see here: > https://github.com/apache/qpid-proton/pull/77 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1291) [proton-j] calling close again on a closed endpoints marks it modified and emits the related event again
[ https://issues.apache.org/jira/browse/PROTON-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1291: --- Summary: [proton-j] calling close again on a closed endpoints marks it modified and emits the related event again (was: calling close again on a closed endpoints marks it modified and emits the related event again) > [proton-j] calling close again on a closed endpoints marks it modified and > emits the related event again > > > Key: PROTON-1291 > URL: https://issues.apache.org/jira/browse/PROTON-1291 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: 0.14.0 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > Fix For: 0.15.0 > > > The trigger for noticing PROTON-1290 was that the endpoint was unexpectedly > marked modified after being closed a second time, with the related close > event also emitted a second time. Neither should occur in this case. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1326) Compilation failures against OpenSSL v1.1.0
Ken Giusti created PROTON-1326: -- Summary: Compilation failures against OpenSSL v1.1.0 Key: PROTON-1326 URL: https://issues.apache.org/jira/browse/PROTON-1326 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.15.0, 0.14.0 Reporter: Ken Giusti Fix For: 0.16.0 Openssl changes the API in a way that breaks proton's openssl implementation. Proton/C can not compile against Openssl version 1.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1323) 0.15.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-1323. Resolution: Fixed > 0.15.0 release tasks > > > Key: PROTON-1323 > URL: https://issues.apache.org/jira/browse/PROTON-1323 > Project: Qpid Proton > Issue Type: Task > Components: release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1323) 0.15.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1323: --- Fix Version/s: (was: 0.15.0) > 0.15.0 release tasks > > > Key: PROTON-1323 > URL: https://issues.apache.org/jira/browse/PROTON-1323 > Project: Qpid Proton > Issue Type: Task > Components: release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1288) c++ provide access to message maps as proton::value
[
https://issues.apache.org/jira/browse/PROTON-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated PROTON-1288:
---
Affects Version/s: 0.15.0
Fix Version/s: (was: 0.15.0)
0.16.0
Unclear anything has been done for this so I'm removing the 0.15.0 fix-version,
bumping to 0.16.0 as it looks to be under consideration already.
> c++ provide access to message maps as proton::value
> ---
>
> Key: PROTON-1288
> URL: https://issues.apache.org/jira/browse/PROTON-1288
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding
>Affects Versions: 0.14.0, 0.15.0
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: 0.16.0
>
>
> We need to provide access to the message property maps as a proton::value.
> Given
> {code}
> std::map my_map;
> proton::message m;
> {code}
> Here are some options:
> 1. Add new message accessor: proton::value& properties_value()
>proton::get(m.properties_value(), my_map)
> 2. Add value() accessor to cached_map
>proton::get(m.properties().value(), my_map)
> 3. Make cached_map : public proton::value()
>proton::get(m.properties(), my_map)
> 3 is neatest, 1 provides a clearer separation between the case where you want
> a convenient cached map vs. you want to decode to your own C++ map, work on
> it, and possibly re-encode it later. I lean towards 3. but open to persuasion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1277) pn_connection_engine API improvements.
[ https://issues.apache.org/jira/browse/PROTON-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-1277. Resolution: Fixed Resolcing as changes have been made in 0.15.0. If there are futher changes still to come, open a new JIRA and link it. > pn_connection_engine API improvements. > -- > > Key: PROTON-1277 > URL: https://issues.apache.org/jira/browse/PROTON-1277 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Affects Versions: 0.14.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.15.0 > > > The pn_connection_engine API needs to be improved to address the following > concerns: > - duplication of types (pn_cbuf_t duplicates pn_bytes_t) > - user-controlled allocation of IO buffers to allow future elimination of > internal proton buffering for 0-copy IO or malloc-restricted environments. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1259) c: libuv multi-threaded example driver.
[ https://issues.apache.org/jira/browse/PROTON-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1259: --- Fix Version/s: (was: 0.15.0) I'm removing the 0.15.0 fix-version, setting to none as its been bumped along a few times already. > c: libuv multi-threaded example driver. > --- > > Key: PROTON-1259 > URL: https://issues.apache.org/jira/browse/PROTON-1259 > Project: Qpid Proton > Issue Type: New Feature > Components: proton-c >Affects Versions: 0.12.2 >Reporter: Alan Conway >Assignee: Alan Conway > > Implement a multi-threaded C++ proton::container implementation also built on > libuv. Demonstrate use of the C connection_engine_t to integrate with an > external proactive IO library. > Strucuture: > - pn_container API to replace reactor (based on C++ container but simplified) > - pn_container_impl SPI to allow multiple container implementations > - libuv implementation of pn_container_impl > - examples baesd on pn_container API, running on libuv (for now, but could > run on any container impl) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1091) [Python binding] AMQP null type not sent on wire according to AMQP specification
[ https://issues.apache.org/jira/browse/PROTON-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1091: --- Fix Version/s: (was: 0.15.0) Unclear if anything has been done for this so I'm removing the 0.15.0 fix-version, setting to none as its been bumped along a few times already. > [Python binding] AMQP null type not sent on wire according to AMQP > specification > > > Key: PROTON-1091 > URL: https://issues.apache.org/jira/browse/PROTON-1091 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > When sending AMQP type null as the content of a message, the Python binding > sends the message with no body at all, and similarly interprets a no-body > AMQP type message as a null type. This violates the AMQP 1.0 specification on > two counts: > * A body MUST be present and be one of three types (section 3.2); > * When sending an AMQP null type, there is an assigned AMQP type code (0x40) > which should be used. > This causes interoperability issues with other clients. For example, the C++ > client can't send a null type to a python client without a failure (or _visa > versa_). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-7379) [Java Broker] Provide a mechanism to extract messages from a vhost message store and replay them into a new vhost
[ https://issues.apache.org/jira/browse/QPID-7379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack resolved QPID-7379. Resolution: Fixed > [Java Broker] Provide a mechanism to extract messages from a vhost message > store and replay them into a new vhost > - > > Key: QPID-7379 > URL: https://issues.apache.org/jira/browse/QPID-7379 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey > Fix For: qpid-java-6.1 > > > QPID-7359 provided operations to extract the config from a virtual host, but > there are not currently any mechanisms to extract the contents of the message > store and replay that into a new vhost. We should add this feature to (for > example) allow people to migrate their data from one vhost type to another -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7447) Java Broker tuning improvements for v6.1 release
[ https://issues.apache.org/jira/browse/QPID-7447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575528#comment-15575528 ] ASF subversion and git services commented on QPID-7447: --- Commit 1764918 from [~godfrer] in branch 'java/trunk' [ https://svn.apache.org/r1764918 ] QPID-7447 : Remove synchronization on StatisticsCounter > Java Broker tuning improvements for v6.1 release > > > Key: QPID-7447 > URL: https://issues.apache.org/jira/browse/QPID-7447 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > > Java Broker tuning improvements for v6.1 release -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7447) Java Broker tuning improvements for v6.1 release
[ https://issues.apache.org/jira/browse/QPID-7447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575525#comment-15575525 ] ASF subversion and git services commented on QPID-7447: --- Commit 1764917 from [~godfrer] in branch 'java/trunk' [ https://svn.apache.org/r1764917 ] QPID-7447 : Fix test failures from last commit > Java Broker tuning improvements for v6.1 release > > > Key: QPID-7447 > URL: https://issues.apache.org/jira/browse/QPID-7447 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > > Java Broker tuning improvements for v6.1 release -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6266) qpid-cpp-0.30 Build Fail - Org.Apache.Qpid.Messaging.dll
[
https://issues.apache.org/jira/browse/QPID-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuck Rolke updated QPID-6266:
--
Attachment: qpid-6266-build-log.txt
Ok, it's been a while since I reviewed all the setup and stuff that is needed
for a windows build. File qpid-6266-build-log.txt is how the build looks when I
run the scripts on my system. The each component is built twice: Debug and
Release.
* First my path is exposed. Not all of this is necessary to build
proton/qpid-cpp but this is what I have.
* The build starts with qpid-cpp-1.35.0 and qpid-proton-0.14.0 unzipped and
untarred in an otherwise empty W: drive.
* I keep my scripts on drive B:\ but they could be anywhere.
* The command set I used was:
{noformat}
W:\>doskey /history
w:
showpath
dir
cd qpid-proton-0.14.0
b:\build_proton ..\qpid-cpp-1.35.0 2012 x64
cd ..\qpid-cpp-1.35.0
dir
b:\build-qpid-cpp.bat 2012 x64
doskey /history
{noformat}
A build has many "not found" and "could not find" log lines that to an
untrained eye may signal problems. I've learned to ignore them.
The most critical things to watch for are that qpid-cpp cmake finds qpid-proton
and that the install parts of the build are complete.
When its all done your artifacts are in
{noformat}
10/14/2016 09:59 AM build_2012_x64
10/14/2016 09:26 AM install_2012_x64
{noformat}
Good luck!
> qpid-cpp-0.30 Build Fail - Org.Apache.Qpid.Messaging.dll
>
>
> Key: QPID-6266
> URL: https://issues.apache.org/jira/browse/QPID-6266
> Project: Qpid
> Issue Type: Bug
> Components: Dot Net Client
>Affects Versions: 0.30
> Environment: Windows XP (x86)
> Windows 7 ( x64).
> Visual Studios 2008, 2010
>Reporter: Fred Cheng
>Assignee: Chuck Rolke
> Attachments: qpid-6266-build-log.txt, qpid-6266-workaround.patch
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> The build instructions in the file INSTALL-WINDOWS in qpid-cpp-0.30 does not
> work. For example, the file said to install
> 1. CMake 2.4
> 2. "cmake -i -G "Visual Studio 9 2008"
> The problem is the CMake 2.4 does not support "Visual Studio 9 2008"
> A second example is that the command -i for cmake has been depreciated in
> current version of cmake.
> The file README-winsdk.txt also appears to be outdated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1325) Python "buffer" type in Message body should map to a known encoding type
[
https://issues.apache.org/jira/browse/PROTON-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575134#comment-15575134
]
Robbie Gemmell commented on PROTON-1325:
Yeah that comment was more for Alan, or anyone else reading the JIRA traffic
and wanting to discuss which of the possibe options to take :)
> Python "buffer" type in Message body should map to a known encoding type
>
>
> Key: PROTON-1325
> URL: https://issues.apache.org/jira/browse/PROTON-1325
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: 0.14.0
>Reporter: Brian Bouterse
>Assignee: Alan Conway
>
> If I try to send a message like this it fails due to an encoding error.
> from proton import Message
> Message(body=buffer('asdf'))
> If you try to send this and fail to specify an encoding, you will get an
> encoding traceback like this one.
> Traceback (most recent call last):
> File "/usr/lib64/python2.7/threading.py", line 804, in __bootstrap_inner
> self.run()
> File "/home/vagrant/devel/kombu/kombu/transport/qpid.py", line 1367, in run
> Container(HelloWorld("localhost:5672", self._w,
> self.outbound_messages)).run()
> File "/usr/lib64/python2.7/site-packages/proton/reactor.py", line 133, in
> run
> while self.process(): pass
> File "/usr/lib64/python2.7/site-packages/proton/reactor.py", line 159, in
> process
> self._check_errors()
> File "/usr/lib64/python2.7/site-packages/proton/reactor.py", line 155, in
> _check_errors
> _compat.raise_(exc, value, tb)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 4022, in
> dispatch
> ev.dispatch(self.handler)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3934, in
> dispatch
> self.dispatch(h, type)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3931, in
> dispatch
> result = dispatch(handler, type.method, self)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3812, in
> dispatch
> return m(*args)
> File "/usr/lib64/python2.7/site-packages/proton/handlers.py", line 40, in
> on_link_flow
> self.on_sendable(event)
> File "/usr/lib64/python2.7/site-packages/proton/handlers.py", line 62, in
> on_sendable
> dispatch(self.delegate, 'on_sendable', event)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3812, in
> dispatch
> return m(*args)
> File "/home/vagrant/devel/kombu/kombu/transport/qpid.py", line 1351, in
> on_sendable
> event.sender.send(message)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2997, in
> send
> return obj.send(self, tag=tag)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 1116, in
> send
> encoded = self.encode()
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 1099, in
> encode
> self._pre_encode()
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 843, in
> _pre_encode
> body.put_object(self.body)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2271, in
> put_object
> putter(self, obj)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2114, in
> put_dict
> self.put_object(v)
> File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2270, in
> put_object
> putter = self.put_mappings[obj.__class__]
> KeyError:
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7447) Java Broker tuning improvements for v6.1 release
[ https://issues.apache.org/jira/browse/QPID-7447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15574950#comment-15574950 ] ASF subversion and git services commented on QPID-7447: --- Commit 1764865 from [~godfrer] in branch 'java/trunk' [ https://svn.apache.org/r1764865 ] QPID-7447 : Cache authorization of publish message results on the session > Java Broker tuning improvements for v6.1 release > > > Key: QPID-7447 > URL: https://issues.apache.org/jira/browse/QPID-7447 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > > Java Broker tuning improvements for v6.1 release -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7459) ProducerFlowControlTest#testSendTimeout test fails sprodically on 0-10 profiles
[
https://issues.apache.org/jira/browse/QPID-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7459:
-
Attachment:
TEST-org.apache.qpid.server.queue.ProducerFlowControlTest.testSendTimeout.txt
> ProducerFlowControlTest#testSendTimeout test fails sprodically on 0-10
> profiles
> ---
>
> Key: QPID-7459
> URL: https://issues.apache.org/jira/browse/QPID-7459
> Project: Qpid
> Issue Type: Bug
> Components: Java Tests
>Reporter: Keith Wall
>Priority: Minor
> Attachments:
> TEST-org.apache.qpid.server.queue.ProducerFlowControlTest.testSendTimeout.txt
>
>
> ProducerFlowControlTest#testSendTimeout test fails sprodically on 0-10
> profiles.
> The test is racey. The test relies on message n-1 causing flow control to be
> imposed before the test can try to send message n. If flow control is not
> imposed before the client tries to send message n, the test will fail. In
> the failing case the client has not processed the incoming MessageStop before
> it sends message n. The test tries tries to prevent this by sync'ing twice.
> This approach is ineffective for 0-10 as the send sync to optimised out and
> does not caused an ExecutionSync.
> The test issue does not affect the usefulness of the feature itself.
> https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-Test-JDK1.8/1801/artifact/trunk/systests/target/surefire-reports/java-mms.0-10/
> {noformat}
> junit.framework.AssertionFailedError: No timeout exception on sending
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNotNull(Assert.java:256)
> at junit.framework.TestCase.assertNotNull(TestCase.java:426)
> at
> org.apache.qpid.server.queue.ProducerFlowControlTest.testSendTimeout(ProducerFlowControlTest.java:284)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-7459) ProducerFlowControlTest#testSendTimeout test fails sprodically on 0-10 profiles
Keith Wall created QPID-7459:
Summary: ProducerFlowControlTest#testSendTimeout test fails
sprodically on 0-10 profiles
Key: QPID-7459
URL: https://issues.apache.org/jira/browse/QPID-7459
Project: Qpid
Issue Type: Bug
Components: Java Tests
Reporter: Keith Wall
Priority: Minor
Attachments:
TEST-org.apache.qpid.server.queue.ProducerFlowControlTest.testSendTimeout.txt
ProducerFlowControlTest#testSendTimeout test fails sprodically on 0-10
profiles.
The test is racey. The test relies on message n-1 causing flow control to be
imposed before the test can try to send message n. If flow control is not
imposed before the client tries to send message n, the test will fail. In the
failing case the client has not processed the incoming MessageStop before it
sends message n. The test tries tries to prevent this by sync'ing twice.
This approach is ineffective for 0-10 as the send sync to optimised out and
does not caused an ExecutionSync.
The test issue does not affect the usefulness of the feature itself.
https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-Test-JDK1.8/1801/artifact/trunk/systests/target/surefire-reports/java-mms.0-10/
{noformat}
junit.framework.AssertionFailedError: No timeout exception on sending
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertNotNull(Assert.java:256)
at junit.framework.TestCase.assertNotNull(TestCase.java:426)
at
org.apache.qpid.server.queue.ProducerFlowControlTest.testSendTimeout(ProducerFlowControlTest.java:284)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-7458) ProducerFlowControlTest#testSendTimeout test fails sprodically on 0-10 profiles
Keith Wall created QPID-7458:
Summary: ProducerFlowControlTest#testSendTimeout test fails
sprodically on 0-10 profiles
Key: QPID-7458
URL: https://issues.apache.org/jira/browse/QPID-7458
Project: Qpid
Issue Type: Bug
Components: Java Tests
Reporter: Keith Wall
Priority: Minor
ProducerFlowControlTest#testSendTimeout test fails sprodically on 0-10
profiles.
The test is racey. The test relies on message n-1 causing flow control to be
imposed before the test can try to send message n. If flow control is not
imposed before the client tries to send message n, the test will fail. In the
failing case the client has not processed the incoming MessageStop before it
sends message n. The test tries tries to prevent this by sync'ing twice.
This approach is ineffective for 0-10 as the send sync to optimised out and
does not caused an ExecutionSync.
The test issue does not affect the usefulness of the feature itself.
https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-Test-JDK1.8/1801/artifact/trunk/systests/target/surefire-reports/java-mms.0-10/
{noformat}
junit.framework.AssertionFailedError: No timeout exception on sending
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertNotNull(Assert.java:256)
at junit.framework.TestCase.assertNotNull(TestCase.java:426)
at
org.apache.qpid.server.queue.ProducerFlowControlTest.testSendTimeout(ProducerFlowControlTest.java:284)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7379) [Java Broker] Provide a mechanism to extract messages from a vhost message store and replay them into a new vhost
[ https://issues.apache.org/jira/browse/QPID-7379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15574852#comment-15574852 ] ASF subversion and git services commented on QPID-7379: --- Commit 1764849 from [~godfrer] in branch 'java/trunk' [ https://svn.apache.org/r1764849 ] QPID-7379 : Revert renaming of extractConfig > [Java Broker] Provide a mechanism to extract messages from a vhost message > store and replay them into a new vhost > - > > Key: QPID-7379 > URL: https://issues.apache.org/jira/browse/QPID-7379 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey > Fix For: qpid-java-6.1 > > > QPID-7359 provided operations to extract the config from a virtual host, but > there are not currently any mechanisms to extract the contents of the message > store and replay that into a new vhost. We should add this feature to (for > example) allow people to migrate their data from one vhost type to another -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (QPID-7379) [Java Broker] Provide a mechanism to extract messages from a vhost message store and replay them into a new vhost
[ https://issues.apache.org/jira/browse/QPID-7379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack reopened QPID-7379: Assignee: (was: Lorenz Quack) > [Java Broker] Provide a mechanism to extract messages from a vhost message > store and replay them into a new vhost > - > > Key: QPID-7379 > URL: https://issues.apache.org/jira/browse/QPID-7379 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey > Fix For: qpid-java-6.1 > > > QPID-7359 provided operations to extract the config from a virtual host, but > there are not currently any mechanisms to extract the contents of the message > store and replay that into a new vhost. We should add this feature to (for > example) allow people to migrate their data from one vhost type to another -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7379) [Java Broker] Provide a mechanism to extract messages from a vhost message store and replay them into a new vhost
[
https://issues.apache.org/jira/browse/QPID-7379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15574835#comment-15574835
]
Lorenz Quack commented on QPID-7379:
I just came across another issue that had escaped my review before:
{{VirtualHost#extractConfig}} was renamed to {{exportConfig}}.
This has three issues:
* It breaks backwards compatibility
* If we go forward with the rename then probably {{Broker#extractConfig}}
should also be renamed
* This broker the WMC which still calls {{extractConfig}} in {{VirtualHost.js}}
> [Java Broker] Provide a mechanism to extract messages from a vhost message
> store and replay them into a new vhost
> -
>
> Key: QPID-7379
> URL: https://issues.apache.org/jira/browse/QPID-7379
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
>Reporter: Rob Godfrey
>Assignee: Lorenz Quack
> Fix For: qpid-java-6.1
>
>
> QPID-7359 provided operations to extract the config from a virtual host, but
> there are not currently any mechanisms to extract the contents of the message
> store and replay that into a new vhost. We should add this feature to (for
> example) allow people to migrate their data from one vhost type to another
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6266) qpid-cpp-0.30 Build Fail - Org.Apache.Qpid.Messaging.dll
[ https://issues.apache.org/jira/browse/QPID-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15574560#comment-15574560 ] Vladimir Vesic commented on QPID-6266: -- Thank you very much [~chug] ! So the prerequisites are Qpid C++ 1.35.0 ( https://qpid.apache.org/releases/qpid-cpp-1.35.0/ ) and Qpid Proton 0.14.0 ( http://qpid.apache.org/releases/qpid-proton-0.14.0/ ) And i should put them in same installing folder and than run your script in Qpid c++ folder ? Or do i need to use version 0.3 of qpid cpp ? Thanks in advance ! > qpid-cpp-0.30 Build Fail - Org.Apache.Qpid.Messaging.dll > > > Key: QPID-6266 > URL: https://issues.apache.org/jira/browse/QPID-6266 > Project: Qpid > Issue Type: Bug > Components: Dot Net Client >Affects Versions: 0.30 > Environment: Windows XP (x86) > Windows 7 ( x64). > Visual Studios 2008, 2010 >Reporter: Fred Cheng >Assignee: Chuck Rolke > Attachments: qpid-6266-workaround.patch > > Original Estimate: 120h > Remaining Estimate: 120h > > The build instructions in the file INSTALL-WINDOWS in qpid-cpp-0.30 does not > work. For example, the file said to install > 1. CMake 2.4 > 2. "cmake -i -G "Visual Studio 9 2008" > The problem is the CMake 2.4 does not support "Visual Studio 9 2008" > A second example is that the command -i for cmake has been depreciated in > current version of cmake. > The file README-winsdk.txt also appears to be outdated. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
