[jira] [Closed] (QPID-2084) 0-10 code path does not appear to throw exception on consume from non-existent queue
[
https://issues.apache.org/jira/browse/QPID-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross closed QPID-2084.
-
> 0-10 code path does not appear to throw exception on consume from
> non-existent queue
>
>
> Key: QPID-2084
> URL: https://issues.apache.org/jira/browse/QPID-2084
> Project: Qpid
> Issue Type: Bug
>Reporter: Martin Ritchie
>Assignee: Andrew Kennedy
>
> Running the new DynamicQueueExchangeCreateTest, the test appears to throw the
> exception on close rather than the consume.
> ch=0 id=0 ExecutionException(errorCode=NOT_FOUND, commandId=2, classCode=7,
> commandCode=4, fieldIndex=0, description=not-found:
> Queue not found: DynamicQueueExchangeCreateTest-testQueueDeclare
> (qpid/broker/SessionAdapter.cpp:743), errorInfo={})
> org.apache.qpid.transport.SessionException: ch=0 id=0
> ExecutionException(errorCode=NOT_FOUND, commandId=2, classCode=7,
> commandCode=4, fieldIndex=0, description=not-found: Queue not found:
> DynamicQueueExchangeCreateTest-testQueueDeclare
> (qpid/broker/SessionAdapter.cpp:743), errorInfo={})
> at org.apache.qpid.transport.Session.sync(Session.java:701)
> at org.apache.qpid.transport.Session.sync(Session.java:674)
> at
> org.apache.qpid.client.AMQSession_0_10.sendClose(AMQSession_0_10.java:342)
> at org.apache.qpid.client.AMQSession.close(AMQSession.java:667)
> at org.apache.qpid.client.AMQSession.close(AMQSession.java:633)
> at
> org.apache.qpid.client.AMQConnection.closeAllSessions(AMQConnection.java:1113)
> at
> org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:1008)
> at
> org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:997)
> at org.apache.qpid.client.AMQConnection.close(AMQConnection.java:981)
> at org.apache.qpid.client.AMQConnection.close(AMQConnection.java:972)
> at org.apache.qpid.client.AMQConnection.close(AMQConnection.java:967)
> at
> org.apache.qpid.test.utils.QpidTestCase.tearDown(QpidTestCase.java:875)
> at
> org.apache.qpid.test.utils.QpidTestCase.runBare(QpidTestCase.java:224)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:270)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4122) Remove ANONYMOUS from mechanisms allowed in ACL tests
[ https://issues.apache.org/jira/browse/QPID-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4122: -- Component/s: C++ Tests > Remove ANONYMOUS from mechanisms allowed in ACL tests > - > > Key: QPID-4122 > URL: https://issues.apache.org/jira/browse/QPID-4122 > Project: Qpid > Issue Type: Test > Components: C++ Tests >Reporter: Alan Conway >Assignee: michael goulish >Priority: Minor > > With the anonymous mechanism allowed its easy to get a false positive if you > accidentally fail to set an authentication mechanism at all in a security > test, since you can always connect with ANONYMOUS. This is especially the > case where there are multiple elements that need to be authenticated, for > example a test harness starting an admin tool which talks to a broker, or > brokers talking to each other in a cluster. It might be safer to remove > ANONYMOUS and ensure that every element in a security-related test does > authenticate properly. A quick check shows that removing ANONYMOUS causes > multilple tests to fail. It is possible that the tests are OK and those > connections don't need authentication, but it might be clearer to require > authentication from all players in a security related test. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3954) Durable option for qpid-cpp-benchmark does not create durable queues like it should
[ https://issues.apache.org/jira/browse/QPID-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-3954: -- Component/s: C++ Tools > Durable option for qpid-cpp-benchmark does not create durable queues like it > should > --- > > Key: QPID-3954 > URL: https://issues.apache.org/jira/browse/QPID-3954 > Project: Qpid > Issue Type: Bug > Components: C++ Tools >Reporter: Andy Goldstein >Priority: Minor > Attachments: QPID-3954.patch > > > Running the following command should test using durable queues (based on the > description of the --durable option): > qpid-cpp-benchmark --ack-frequency=1000 --content-size 4096 -m 2 --durable > Unfortunately, the queue that is created (benchmark-0), is not created as > durable. This can be verified with the --no-delete option: > qpid-config queues > Queue NameAttributes > = > acfefc4c-fde2-4abb-82b3-94a9db84f729:0.0 auto-del excl > benchmark-0 > Although the start_receive() method attempts to make the queue durable, it > looks like it is too late at this point, as I believe the queue gets created > earlier, when recreate_queues() is called. > I'm attaching a patch that updates the logic in recreate_queues to support > durable queues. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4190) Performance issue with new HA
[ https://issues.apache.org/jira/browse/QPID-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4190: -- Component/s: C++ Clustering > Performance issue with new HA > - > > Key: QPID-4190 > URL: https://issues.apache.org/jira/browse/QPID-4190 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Reporter: Andy Goldstein > > When testing out the new HA implementation, I've noticed that if you rate > limit your senders and receivers appropriately, the system runs in a steady > state without any noticeable degradation in throughput. But if you instead > increase the rate above the "comfortable" threshold, the end-to-end send and > receive rates vary greatly. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5225) qpid address MalformedAddress for parentheses
[
https://issues.apache.org/jira/browse/QPID-5225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross closed QPID-5225.
-
Resolution: Information Provided
> qpid address MalformedAddress for parentheses
> -
>
> Key: QPID-5225
> URL: https://issues.apache.org/jira/browse/QPID-5225
> Project: Qpid
> Issue Type: Bug
> Components: Python Client
> Environment: Ubuntu 12.04
> qpid 0.14
> qpid-tools 0.12
>Reporter: Kai Qiang Wu
>
> I used Qpid Messaging API (Python), and when created(receiver) use following
> address:
> nova/compute.test,123(bill)@192.168.51.57-443 ; {"node": {"x-declare":
> {"auto-delete": true, "durable": true}, "type": "topic"}, "create": "always",
> "link": {"x-declare": {"auto-delete": false, "exclusive": false, "durable":
> false}, "durable": true, "name": "compute.test,123(bill)@192.168.51.57-443"}}
> But the qpid would complain for address parse for the error like this:
> File "/usr/lib/python2.7/dist-packages/qpid/messaging/endpoints.py", line
> 607, in receiver
>raise e
> MalformedAddress: unrecognized characters line:1,21: for that address,
> I did check, qpid doc said address BNF:
> http://qpid.apache.org/components/programming/book/section-addresses.html#section-address-string-bnf
> it not have token for "(" match, but I am confused when use qpid-config,
> I can create topic like following,
> qpid-config add exchange topic "nova/compute.test,123(bill)@192.168.51.57"
> -a admin/qpid@localhost
> So it seems not right not follow same rule, or I missed something.
> Thanks
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5225) qpid address MalformedAddress for parentheses
[
https://issues.apache.org/jira/browse/QPID-5225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-5225:
--
Component/s: Python Client
> qpid address MalformedAddress for parentheses
> -
>
> Key: QPID-5225
> URL: https://issues.apache.org/jira/browse/QPID-5225
> Project: Qpid
> Issue Type: Bug
> Components: Python Client
> Environment: Ubuntu 12.04
> qpid 0.14
> qpid-tools 0.12
>Reporter: Kai Qiang Wu
>
> I used Qpid Messaging API (Python), and when created(receiver) use following
> address:
> nova/compute.test,123(bill)@192.168.51.57-443 ; {"node": {"x-declare":
> {"auto-delete": true, "durable": true}, "type": "topic"}, "create": "always",
> "link": {"x-declare": {"auto-delete": false, "exclusive": false, "durable":
> false}, "durable": true, "name": "compute.test,123(bill)@192.168.51.57-443"}}
> But the qpid would complain for address parse for the error like this:
> File "/usr/lib/python2.7/dist-packages/qpid/messaging/endpoints.py", line
> 607, in receiver
>raise e
> MalformedAddress: unrecognized characters line:1,21: for that address,
> I did check, qpid doc said address BNF:
> http://qpid.apache.org/components/programming/book/section-addresses.html#section-address-string-bnf
> it not have token for "(" match, but I am confused when use qpid-config,
> I can create topic like following,
> qpid-config add exchange topic "nova/compute.test,123(bill)@192.168.51.57"
> -a admin/qpid@localhost
> So it seems not right not follow same rule, or I missed something.
> Thanks
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5303) AMQP 1.0 -> 0-10 doesn't map 'exchange' delivery property
[ https://issues.apache.org/jira/browse/QPID-5303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-5303: -- Component/s: C++ Broker > AMQP 1.0 -> 0-10 doesn't map 'exchange' delivery property > - > > Key: QPID-5303 > URL: https://issues.apache.org/jira/browse/QPID-5303 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Reporter: Daniel Evans > > When a publisher publishes an AMQP 1.0 message to an exchange (i.e. > amqp://0.0.0.0/someExchange), a regular AMQP 0-10 subscriber will be > delivered a message that doesn't include the exchange delivery property. > Since the translation here seems to be intending to present the "normal" > users of the broker with the same model regardless of whether the message > source was 1.0, I'm assuming it would be more correct to have that delivery > property set. We use it in some of our AMQP applications. > I poked around and part of the problem seems to be that the name of the > exchange resolved from the 1.0 address has long been discarded by the time > the broker is delivering the message from the queue. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5320) Need to avoid python_test timing out and causing erronous test failures
[ https://issues.apache.org/jira/browse/QPID-5320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-5320: -- Component/s: C++ Tests > Need to avoid python_test timing out and causing erronous test failures > --- > > Key: QPID-5320 > URL: https://issues.apache.org/jira/browse/QPID-5320 > Project: Qpid > Issue Type: Improvement > Components: C++ Tests >Affects Versions: 0.25 >Reporter: Andrew Stitcher > > Having started running automated test runs, a common "failure" that is > occurring in various places is that the python_test run times out after 25 > mins (1500s) whilst seemingly still making progress. This has happened on > underpowered and highly loaded machines, but doesn't happen on individual > developer machines because they tend to be fast machines and not to be > overloaded when running builds. > Tactically to avoid this issue we probably just need to split the test up > into a few shorter test runs. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6124) FreeBSD ports, testing welcome
[
https://issues.apache.org/jira/browse/QPID-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-6124:
--
Component/s: Packaging
> FreeBSD ports, testing welcome
> --
>
> Key: QPID-6124
> URL: https://issues.apache.org/jira/browse/QPID-6124
> Project: Qpid
> Issue Type: Improvement
> Components: Packaging
>Affects Versions: 0.30
>Reporter: Johan Ström
> Attachments: qpid-ports.tar.gz
>
>
> Hi,
> with the work put into qpid 0.30, it now builds fine on FreeBSD.
> I have put some effort into making proper FreeBSD Ports (packages) for qpid,
> and I'd like to share my work.
> The ports:
> * devel/py-qpid-qmf
> * devel/qpid-proton
> * net/qpid-tools
> * net/qpidd
> devel/py-qpid already exists, so that is not covered.
> They all build fine with the default options, however some bindings are
> broken:
> * devel/qpid-proton
> ** Ruby bindings does not build, libuuid problems
> ** PHP bindings does not build. zend.h problems
> * net/qpidd
> ** Perl bindings does not build. See comments in QPID-6008 for details.
> I have not gone through any great lengths trying to fix this, as I currently
> don't need these bindings.
> The tar-ball attached contains all ports, extract in /usr/ports.
> In addition, to build net/qpidd, /usr/ports/(UIDs|GIDs) needs to be patched:
> {code}
> --- GIDs 2014-09-26 23:35:39.815616975 +0200
> +++ GIDs2014-09-24 21:44:28.369065757 +0200
> @@ -297,5 +297,6 @@
> tvheadend:*:984:
> puppetdb:*:985:
> kamailio:*:986:
> +qpidd:*:987:
> nogroup:*:65533:
> nobody:*:65534:
> --- UIDs 2014-09-26 23:35:37.259916310 +0200
> +++ UIDs2014-09-26 08:53:53.478772009 +0200
> @@ -305,4 +305,5 @@
> tvheadend:*:984:984::0:0:TV Headend:/usr/local/etc/tvheadend:/bin/sh
> puppetdb:*:985:985::0:0:PuppetDB Daemon
> pseudo-user:/nonexistent:/usr/sbin/nologin
> kamailio:*:986:986::0:0:kamailio daemon:/nonexistent:/usr/sbin/nologin
> +qpidd:*:987:987::0:0:kamailio daemon:/nonexistent:/usr/sbin/nologin
> nobody:*:65534:65534::0:0:Unprivileged user:/nonexistent:/usr/sbin/nologin
> {code}
> All ports passes portlint and poudriere testport on FreeBSD 10.0-RELEASE-p7,
> amd64.
> I have not tried to build on 9.3, there might be minor issues.
> My hope is mainly that these comes to some use for other users, but also that
> someone more involved with the qpid project is willing to adopt these ports,
> and ultimately maintain them in the real ports tree.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5521) Timestamping Received Messages in milliseconds
[ https://issues.apache.org/jira/browse/QPID-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-5521. - Resolution: Incomplete > Timestamping Received Messages in milliseconds > -- > > Key: QPID-5521 > URL: https://issues.apache.org/jira/browse/QPID-5521 > Project: Qpid > Issue Type: Wish >Reporter: Emilio González Mora > Labels: features > > Hi. > In order to trace high speed messages, add to messages a timestamp just in > seconds is not enough. Would be possible to include milliseconds. > Many thanks. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6311) SessionAdapter.cpp:198: bad use of ? :
[
https://issues.apache.org/jira/browse/QPID-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-6311:
--
Component/s: C++ Broker
> SessionAdapter.cpp:198: bad use of ? :
> --
>
> Key: QPID-6311
> URL: https://issues.apache.org/jira/browse/QPID-6311
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
>Reporter: David Binderman
>Priority: Minor
>
> qpid-0.28/cpp/src/qpid/broker/SessionAdapter.cpp:198]: (style) Same
> expression in both branches of ternary operator.
> Source code is
> } else if (exchange->isBound(queue, key.empty() ? 0 : &key, args.count()
> > 0 ? &args : &args)) {
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6471) qpid_messaging gem 0.30.0 installation fails on missing Logger.h
[ https://issues.apache.org/jira/browse/QPID-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-6471: -- Component/s: Ruby Client > qpid_messaging gem 0.30.0 installation fails on missing Logger.h > > > Key: QPID-6471 > URL: https://issues.apache.org/jira/browse/QPID-6471 > Project: Qpid > Issue Type: Bug > Components: Ruby Client >Affects Versions: 0.30 > Environment: Fedora 19 >Reporter: Ondrej Prazak >Priority: Minor > > When qpid-cpp version is lower than 0.30, > gem installation results in the following: > https://gist.github.com/xprazak2/94d8eaf0afc746576f51 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6822) Failure on: qpid-config add queue --durable "queue-id"
[
https://issues.apache.org/jira/browse/QPID-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-6822:
--
Component/s: C++ Broker
> Failure on: qpid-config add queue --durable "queue-id"
> --
>
> Key: QPID-6822
> URL: https://issues.apache.org/jira/browse/QPID-6822
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
>Affects Versions: 0.32
> Environment: RedHat 7.1
>Reporter: Peter Lacko
>Assignee: Kim van der Riet
>
> Attempt to create durable queue fails with:
> {noformat}
> $ qpid-config add queue --durable "queue"
> Failed: Exception: Exception from Agent: {u'error_code': 7, u'error_text':
> 'Queue queue: create() failed: jexception 0x010c
> EmptyFilePool::createSymLink() threw JERR__SYMLINK: Symbolic link
> operation failed (file=/var/lib/qpidd/.qpidd/qls/p001/efp/2048k/in_use
> /85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl symlink=/var/lib/qpidd/.qpidd
> /qls/jrnl2/queue/85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl errno=13
> (Permission denied)) (/builddir/build/BUILD/qpid-cpp-0.34/src/qpid/linearstore
> /MessageStoreImpl.cpp:425)'}
> {noformat}
> Queue is created succesfully without {{--durable}} parameter.
> Problem occures after doing {{yum update}}. All qpid packages versions listed
> below, before and after performing update:
> {noformat}
> $ diff qpid-before-update.txt qpid-after-update.txt
> 1,10c1,10
> < python-gofer-qpid.noarch 2.6.6-1.git.48.3141846.el7
> < python-qpid.x86_64 0.32-3.el7 @epel
> < python-qpid-common.x86_64 0.32-3.el7 @epel
> < python-qpid-qmf.x86_64 0.28-29.el7 @epel
> < qpid-cpp-client.x86_64 0.32-3.el7 @epel
> < qpid-cpp-server.x86_64 0.32-3.el7 @epel
> < qpid-cpp-server-store.x86_64
> < qpid-proton-c.x86_64 0.9-3.el7 @epel
> < qpid-qmf.x86_640.28-29.el7 @epel
> < qpid-tools.x86_64 0.32-3.el7 @epel
> ---
> > python-gofer-qpid.noarch 2.6.6-2.el7 @pulp-2.7-beta
> > python-qpid.noarch 0.32-9.el7 @epel
> > python-qpid-common.noarch 0.32-9.el7 @epel
> > python-qpid-qmf.x86_64 0.32-1.el7 @epel
> > qpid-cpp-client.x86_64 0.34-4.el7 @epel
> > qpid-cpp-server.x86_64 0.34-4.el7 @epel
> > qpid-cpp-server-linearstore.x86_64
> > qpid-proton-c.x86_64 0.10-2.el7 @epel
> > qpid-qmf.x86_640.32-1.el7 @epel
> > qpid-tools.noarch 0.32-9.el7 @epel
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-6811) Client API throws exception from destructors causing applications to terminate
[ https://issues.apache.org/jira/browse/QPID-6811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-6811. - Resolution: Won't Fix This against the long deprecated qpid::client API. > Client API throws exception from destructors causing applications to terminate > -- > > Key: QPID-6811 > URL: https://issues.apache.org/jira/browse/QPID-6811 > Project: Qpid > Issue Type: Bug >Affects Versions: 0.32 > Environment: All >Reporter: Venkatesan > Attachments: qpid_dtor_crash.patch > > > Client API has couple of classes like ScopedUnlock which do "reverse" RAII - > unlock in ctor and lock in dtor. When locking fails in the destructor, it is > not handled and an exception is thrown. This causes application to crash when > the exception is thrown while stack is being unwound. > Scoped unlock does not seem the correct approach. Instead of freeing a > resource in the destructor whose failure is not catastrophic, ScopedUnlock > tries to acquire a resource on exit which can fail and there is no way this > can be communicated back to the code! > This class should be done away with and an explicit resource acquisition with > proper failure handling semantics should be used. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6641) [Windows C++] WinSDK scripts do not suppport VS2013 and recent Boost releases
[ https://issues.apache.org/jira/browse/QPID-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-6641: -- Component/s: C++ Build > [Windows C++] WinSDK scripts do not suppport VS2013 and recent Boost releases > - > > Key: QPID-6641 > URL: https://issues.apache.org/jira/browse/QPID-6641 > Project: Qpid > Issue Type: Bug > Components: C++ Build >Affects Versions: qpid-cpp-0.34 > Environment: Windows, WinSDK >Reporter: Chuck Rolke >Assignee: Chuck Rolke > > WinSDK build scripts need an update: > * VS2013 > * Boost 1.58 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4087) Add payload compression to qpid client libraries
[ https://issues.apache.org/jira/browse/QPID-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4087: -- Component/s: Java Client C++ Client > Add payload compression to qpid client libraries > > > Key: QPID-4087 > URL: https://issues.apache.org/jira/browse/QPID-4087 > Project: Qpid > Issue Type: New Feature > Components: C++ Client, Java Client >Reporter: Noel O'Connor > > Add a configurable compression option to the AMQP binding URL which would > turn on compression on the client for both producers and receivers. A > configurable threshold value could also be added to ensure that compression > is only done on a certain payload size or greater. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5433) Expiry related headers are not working as expected.
[ https://issues.apache.org/jira/browse/QPID-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-5433. - Resolution: Incomplete Can't tell which client this is about. > Expiry related headers are not working as expected. > --- > > Key: QPID-5433 > URL: https://issues.apache.org/jira/browse/QPID-5433 > Project: Qpid > Issue Type: Bug >Reporter: Bhanu > > Hi, > I have tested with the expiry_time and ttl headers in Python SWIG wrapper of > AMQP library. None of them is working as expected with ActiveMQ. > Also while setting JMSTemplate's timeToLive while using the AMQP-JMS-Client, > messages are not received. > Can somebody please take a look here on whats going wrong? > I am using ActiveMQ as my broker here. > Thanks, > Bhanu -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4867) Failed cmake build on RHEL5 0.22 RC4
[ https://issues.apache.org/jira/browse/QPID-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4867: -- Component/s: C++ Build > Failed cmake build on RHEL5 0.22 RC4 > > > Key: QPID-4867 > URL: https://issues.apache.org/jira/browse/QPID-4867 > Project: Qpid > Issue Type: Bug > Components: C++ Build >Affects Versions: 0.22 > Environment: RHEL 5.8 >Reporter: Jimmy Jones > > Fresh RHEL 5.8 VM: > sudo yum install cmake boost-devel e2fsprogs-devel pkgconfig gcc-c++ make > ruby doxygen graphviz > tar xvzf qpid-cpp-0.22.tar.gz > cd qpidc-0.22 > mkdir BLD > cd BLD > cmake .. > make > Scanning dependencies of target docs-user-api > Invalid value for DOT_IMAGE_FORMAT: `PNG'. Using the default. > Error: tag INPUT: input source > `/home/jimmy/qpidc-0.22/docs/api/doxygen_mainpage.h' does not exist > make[2]: *** [docs/api/CMakeFiles/docs-user-api] Error 1 > make[1]: *** [docs/api/CMakeFiles/docs-user-api.dir/all] Error 2 > make: *** [all] Error 2 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5432) Durable Subscriptions from QPid messenger API
[ https://issues.apache.org/jira/browse/QPID-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-5432. - Resolution: Won't Fix > Durable Subscriptions from QPid messenger API > - > > Key: QPID-5432 > URL: https://issues.apache.org/jira/browse/QPID-5432 > Project: Qpid > Issue Type: Improvement >Reporter: Bhanu > > Hi, > Currently AMQP Messenger API does not support durable subscriptions. Can this > feature be added soon please? > Thanks, > bhanu -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5128) C++ specific release sources missing the Perl LICENSE file
[ https://issues.apache.org/jira/browse/QPID-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-5128. - Resolution: Not A Problem > C++ specific release sources missing the Perl LICENSE file > -- > > Key: QPID-5128 > URL: https://issues.apache.org/jira/browse/QPID-5128 > Project: Qpid > Issue Type: Bug > Components: C++ Build >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce > > When the qpid-cpp release tarball is used to build and install Qpid, the Perl > portion of the install fails. The reason is that the LICENSE file that's > expected in the Perl directory is not being included in the release tarball. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5128) C++ specific release sources missing the Perl LICENSE file
[ https://issues.apache.org/jira/browse/QPID-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-5128: -- Component/s: C++ Build > C++ specific release sources missing the Perl LICENSE file > -- > > Key: QPID-5128 > URL: https://issues.apache.org/jira/browse/QPID-5128 > Project: Qpid > Issue Type: Bug > Components: C++ Build >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce > > When the qpid-cpp release tarball is used to build and install Qpid, the Perl > portion of the install fails. The reason is that the LICENSE file that's > expected in the Perl directory is not being included in the release tarball. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5919) C++ ipv6_test does not detect IPv6 properly
[
https://issues.apache.org/jira/browse/QPID-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-5919:
--
Component/s: C++ Tests
> C++ ipv6_test does not detect IPv6 properly
> ---
>
> Key: QPID-5919
> URL: https://issues.apache.org/jira/browse/QPID-5919
> Project: Qpid
> Issue Type: Bug
> Components: C++ Tests
>Affects Versions: 0.28
> Environment: Fedora 19 linux, IPv6-enabled default installation
>Reporter: Chuck Rolke
>
> ipv6_test uses
> {noformat}
> if ip -f inet6 -o addr | cut -f 9 -s -d' ' | grep global > /dev/null ; then
> echo "IPv6 addresses configured continuing"
> else
> echo "No global IPv6 addresses configured - skipping test"
> exit 0
> fi
> {noformat}
> to detect IPv6. On my system this returns false and IPv6 test does not run.
> A naked './hello_world' then my broker sees a connection from ::1, the IPv6
> localhost address. IPv6 is there, it works, and the system uses it.
> Self test AclHost.cpp uses a different IPv6 detection method
> {noformat}
> bool haveIPv6(true);
> try {
> sys::SocketAddress sa("::1", "");
> sa.firstAddress();
> } catch (qpid::Exception) {
> haveIPv6 = false;
> }
> {noformat}
> It creates a SocketAddress and uses it. If it can resolve "::1" then IPv6 is
> there.
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6952) [AMQP 1.0 C++ and Python Client] Temporary queues broken if using queue name instead of Address.
[
https://issues.apache.org/jira/browse/QPID-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-6952:
--
Component/s: C++ Client
> [AMQP 1.0 C++ and Python Client] Temporary queues broken if using queue name
> instead of Address.
>
>
> Key: QPID-6952
> URL: https://issues.apache.org/jira/browse/QPID-6952
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Environment: Red Hat Enterprise Linux Server release 6.7 (Santiago)
> The _qpid-cpp_ code has been built with _qpid-proton_ version 0.10.
> The broker is ActiveMQ 5.12.1.
> The protocol used in AMQP 1.0.
>Reporter: Håkan Johansson
> Attachments: cpp_experiment.cc, experiment.py
>
>
> I create a temporary queue by creating a receiver with {{"#"}} as queue name.
> So far so good. The problem comes when I try to send a reply on that queue.
> If I use the {{Address}}, then it works, but not if I use the resulting queue
> name.
> In C++ this is easy to work around, just use the result from
> {{receiver.getAddress()}} when setting the reply-to queue and use the sender
> constructor that takes an {{Address}} object.
> In Python this becomes a bit of a problem since the SWIG:ed methods gets rid
> of the {{Address}} object and returns a string instead. I have to call the
> private method {{message._getReplyTo()}} to get it to work. If I use
> {{message.reply_to}} or {{message.getReplyTo()}} I get a string instead,
> which does not work.
> If I use the reply-to queue name when creating the sender, a queue named
> {{"temp-queue:"}} is created (the actual queue name is something like
> {{"temp-queue://ID:myhostname-48781-1447769813910-2:47564:0"}}).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6357) Qpid Python package setup.py scripts should support 'develop'
[
https://issues.apache.org/jira/browse/QPID-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-6357:
--
Component/s: Python Client
> Qpid Python package setup.py scripts should support 'develop'
> -
>
> Key: QPID-6357
> URL: https://issues.apache.org/jira/browse/QPID-6357
> Project: Qpid
> Issue Type: Bug
> Components: Python Client
>Affects Versions: 0.31
>Reporter: Brian Bouterse
>Priority: Minor
>
> I went to install qpid.messaging from source today and I did what I always
> do: sudo python setup.py develop
> It told me:
> {{{
> usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
>or: setup.py --help [cmd1 cmd2 ...]
>or: setup.py --help-commands
>or: setup.py cmd --help
> error: invalid command 'develop'
> }}}
> The goal is to have my checkout in place while still being installed on my
> system path. Perhaps this is an RFE, but I feel it's a common practice so I
> filed it as a bug.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7130) qpid C++ with SSL authentication returning dummy string from Connection::getAuthenticatedUsername()
[
https://issues.apache.org/jira/browse/QPID-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-7130:
--
Component/s: C++ Client
> qpid C++ with SSL authentication returning dummy string from
> Connection::getAuthenticatedUsername()
> ---
>
> Key: QPID-7130
> URL: https://issues.apache.org/jira/browse/QPID-7130
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Client
>Affects Versions: qpid-cpp-0.34
> Environment: Fedora 21 Linux
>Reporter: Domen Vrankar
>Assignee: Gordon Sim
>Priority: Minor
> Labels: features, patch
> Fix For: qpid-cpp-1.35.0
>
> Attachments:
> 0001-qpid-messaging-Connection-getAuthenticatedUsername.patch,
> 0002-Added-getLocalAuthId-to-all-socket-classes.patch,
> 0003-Added-virtual-keyword-to-functions-BSDSocket-getKeyL.patch,
> 0004-Added-getPeerAuthId-as-an-alias-for-getClientAuthId-.patch,
> 0005-Deleted-old-getClientAuthId-function-that-was-replac.patch
>
>
> When using Qpid C++ without SASL or with authentication disabled you can do:
> qpid_message.setUserId(qpid_connection_.getAuthenticatedUsername());
> and message can be received on remote location.
> Without SASL "ANONYMOUS" string is returned.
> With SASL but without authentication "anonymous" string is returned.
> In both cases message isn't rejected by broker.
> With SASL and SLL authentication "dummy" is returned. This string is rejected
> by broker and also doesn't help with identifying who sent the message.
> First patch fixes this by reading local certificate authentication id the
> same way as SslSocket::getClientAuthId does but for local instead of peer
> certificate.
> Second patch adds getLocalAuthId to all other classes derived from Socket
> (not certain if this is necessary that's why it's in a separate patch).
> Third patch adds virtual keyword to BSDSocket getKeyLen, getClientAuthId and
> ~BSDSocket() functions since this class is parent class of SslSocket. (Since
> with C++11 and later compilers final and override keywords can be used to
> find such errors perhaps two macros should be defined and used throughout the
> code e.g.:
> create file qpid_cpp.hpp
> #if __cplusplus <= 199711L
> #define QPID_CPP_OVERRIDE
> #define QPID_CPP_FINAL
> #else
> #define QPID_CPP_OVERRIDE override
> #define QPID_CPP_FINAL final
> #endif
> and then used somewhere:
> #include "qpid_cpp.hpp"
> struct A {
> virtual void foo() QPID_CPP_FINAL; // A::foo is final
> virtual void bar();
> virtual void bas();
> };
>
> struct B QPID_CPP_FINAL : A { // struct B is final
> void foo(); // Error: foo cannot be overridden as it's final in A
> void bar() QPID_CPP_OVERRIDE;
> int bas() QPID_CPP_OVERRIDE; // Error: wrong bar signature used
> void baf() QPID_CPP_OVERRIDE; // Error: function doesn't override
> anything
> };
>
> struct C : B { // Error: B is final
> };
> )
> Fourth patch adds getPeerAuthId as alias for getClientAuthId since current
> name is meaningful only on broker side (on client side it returns broker
> authentication id).
> Fifth patch removes getClientAuthId altogether (split into a separate patch
> as I am not certain if this function can be accessed from outside Qpid
> internal implementation and should remain as is).
> How to test:
> Build qpid with SASL and SSL.
> Create ssl certificate store.
> Run qpid with:
> qpidd --ssl-cert-db ${CERT_DB_DIR} --ssl-cert-password-file /tmp/password.txt
> --ssl-cert-name 127.0.0.1 --ssl-require-client-authentication --acl-file
> ${ACL_DIR}/acl_file.acl --auth yes
> ACL file should contain:
> acl allow send@QPID all # sender cert
> acl allow receive@QPID all # receiver cert
> acl deny all all
> On sending client use:
> qpid_message.setUserId(qpid_connection_.getAuthenticatedUsername());
> On receiving client use:
> qpid_message.getUserId();
> Message should be delivered and Id's should be the same and matching sender
> certificate nickname.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6534) [Java Client] Add a pooled connection factory
[ https://issues.apache.org/jira/browse/QPID-6534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-6534: -- Component/s: Java Client > [Java Client] Add a pooled connection factory > - > > Key: QPID-6534 > URL: https://issues.apache.org/jira/browse/QPID-6534 > Project: Qpid > Issue Type: Improvement > Components: Java Client >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: qpid-java-6.0 > > > When interacting with frameworks it is often the case that connections are > created, used and then closed frequently. Creating a connection has a high > overhead and thus it would be advantageous to provide a connection factory > which can pool connections that can be reused. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6179) [Java Client] Connection establishment can send invalid frame sequence when retrying
[
https://issues.apache.org/jira/browse/QPID-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-6179:
--
Component/s: Java Client
> [Java Client] Connection establishment can send invalid frame sequence when
> retrying
>
>
> Key: QPID-6179
> URL: https://issues.apache.org/jira/browse/QPID-6179
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
> Fix For: qpid-java-6.0
>
>
> Occasionally one sees erroneous protocol traces such as illustrated by the
> following:
> {noformat}
> [apache.qpid.client.AMQConnectionDelegate_8_0] Connecting to
> broker:tcp://localhost:10002?connectdelay='500'&retries='0'
> [transport.network.io.IoNetworkTransport] SO_RCVBUF : 65535
> [transport.network.io.IoNetworkTransport] SO_SNDBUF : 65535
> [transport.network.io.IoNetworkTransport] TCP_NODELAY : true
> [qpid.client.state.StateWaiter] New StateWaiter :AMQState: id = 4 name:
> CONNECTION_OPEN:[AMQState: id = 4 name: CONNECTION_OPEN, AMQState: id = 6
> name: CONNECTION_CLOSED]
> [qpid.protocol] SEND:
> [org.apache.qpid.client.protocol.AMQProtocolHandler@501fdcfb] AMQP1109
> [apache.qpid.client.AMQConnection] Connection 3 now connected from
> /127.0.0.1:50631 to localhost/127.0.0.1:10002
> [apache.qpid.client.AMQConnection] Are we connected:true
> [apache.qpid.client.AMQConnection] Connected with ProtocolHandler Version:0-9
> [apache.qpid.client.AMQConnectionDelegate_8_0] Write channel open frame for
> channel id
>
> # What on earth
> {noformat}
> The issue stems from a prior connection attempt which has reached the
> connection open stage, but then (for some reason) closed.
> We can rectify this issue by using a new StateManager for each connection
> attempt.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4628) System level tests for selector functionality
[ https://issues.apache.org/jira/browse/QPID-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4628: -- Component/s: C++ Tests > System level tests for selector functionality > - > > Key: QPID-4628 > URL: https://issues.apache.org/jira/browse/QPID-4628 > Project: Qpid > Issue Type: Sub-task > Components: C++ Tests >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > > There is good coverage of the low level selector language parsing and > evaluation in unit tests. But currently no system level tests for the overall > selector functionality. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2084) 0-10 code path does not appear to throw exception on consume from non-existent queue
[
https://issues.apache.org/jira/browse/QPID-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-2084:
--
Fix Version/s: (was: Future)
> 0-10 code path does not appear to throw exception on consume from
> non-existent queue
>
>
> Key: QPID-2084
> URL: https://issues.apache.org/jira/browse/QPID-2084
> Project: Qpid
> Issue Type: Bug
>Reporter: Martin Ritchie
>Assignee: Andrew Kennedy
>
> Running the new DynamicQueueExchangeCreateTest, the test appears to throw the
> exception on close rather than the consume.
> ch=0 id=0 ExecutionException(errorCode=NOT_FOUND, commandId=2, classCode=7,
> commandCode=4, fieldIndex=0, description=not-found:
> Queue not found: DynamicQueueExchangeCreateTest-testQueueDeclare
> (qpid/broker/SessionAdapter.cpp:743), errorInfo={})
> org.apache.qpid.transport.SessionException: ch=0 id=0
> ExecutionException(errorCode=NOT_FOUND, commandId=2, classCode=7,
> commandCode=4, fieldIndex=0, description=not-found: Queue not found:
> DynamicQueueExchangeCreateTest-testQueueDeclare
> (qpid/broker/SessionAdapter.cpp:743), errorInfo={})
> at org.apache.qpid.transport.Session.sync(Session.java:701)
> at org.apache.qpid.transport.Session.sync(Session.java:674)
> at
> org.apache.qpid.client.AMQSession_0_10.sendClose(AMQSession_0_10.java:342)
> at org.apache.qpid.client.AMQSession.close(AMQSession.java:667)
> at org.apache.qpid.client.AMQSession.close(AMQSession.java:633)
> at
> org.apache.qpid.client.AMQConnection.closeAllSessions(AMQConnection.java:1113)
> at
> org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:1008)
> at
> org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:997)
> at org.apache.qpid.client.AMQConnection.close(AMQConnection.java:981)
> at org.apache.qpid.client.AMQConnection.close(AMQConnection.java:972)
> at org.apache.qpid.client.AMQConnection.close(AMQConnection.java:967)
> at
> org.apache.qpid.test.utils.QpidTestCase.tearDown(QpidTestCase.java:875)
> at
> org.apache.qpid.test.utils.QpidTestCase.runBare(QpidTestCase.java:224)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:270)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5780) Can Improve memory use by rearranging struct to remove padding holes
[ https://issues.apache.org/jira/browse/QPID-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-5780: -- Component/s: C++ Client C++ Broker > Can Improve memory use by rearranging struct to remove padding holes > > > Key: QPID-5780 > URL: https://issues.apache.org/jira/browse/QPID-5780 > Project: Qpid > Issue Type: Improvement > Components: C++ Broker, C++ Client >Reporter: Andrew Stitcher >Priority: Minor > > The C/C++ language rules allow compilers to add extra padding in the middle > of structs .Generally this is done to maintain the correct ABI alignment for > the members. > This means that by paying attention to the sizes of the members you can > eliminate the padding simply by putting the largest members (with the biggest > alignment constraint) first then the next then the next down to bitfields (if > you are using them). > Removing the padding can reduce the space used by structs and this can be > significant if enough of them are allocated. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2065) New WCF channel using Qpid cpp client libraries
[ https://issues.apache.org/jira/browse/QPID-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2065: -- Labels: legacy-wcf-client (was: ) > New WCF channel using Qpid cpp client libraries > --- > > Key: QPID-2065 > URL: https://issues.apache.org/jira/browse/QPID-2065 > Project: Qpid > Issue Type: New Feature >Affects Versions: 0.6 > Environment: Microsoft Windows >Reporter: Cliff Jansen >Assignee: Steve Huston > Labels: legacy-wcf-client > Fix For: 0.6 > > Attachments: cj.zip > > > Client software is provided that leverages the existing Qpid C++ libraries to > offer a rich programming environment and runtime support for .NET application > developers on the Windows platform. > The initial focus is on an AMQP Windows Communication Foundation (WCF) > channel with transaction support and full programmatic access to AMQP message > properties. > Follow on work will include broker management capabilities. > This first patch provides a basic WCF implementation that supports both > WCF-to-WCF and WCF-to-non-WCF applications. > Functional tests and sample programs are further provided in related patches. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5741) Now that Proton 0.7 has released don't warn if we try to build with it
[ https://issues.apache.org/jira/browse/QPID-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-5741: -- Component/s: C++ Build > Now that Proton 0.7 has released don't warn if we try to build with it > -- > > Key: QPID-5741 > URL: https://issues.apache.org/jira/browse/QPID-5741 > Project: Qpid > Issue Type: Improvement > Components: C++ Build >Affects Versions: 0.28, 0.29 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Minor > Fix For: 0.28, 0.29 > > > Proton 0.7 seems to work work as well with qpid as 0.6 (at least in the build > tests). We should no longer print a scary warning if we build with Proton 0.7 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5336) Script interpreters need to be found on the path and not have hardcoded locations
[
https://issues.apache.org/jira/browse/QPID-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-5336:
--
Component/s: C++ Tests
> Script interpreters need to be found on the path and not have hardcoded
> locations
> -
>
> Key: QPID-5336
> URL: https://issues.apache.org/jira/browse/QPID-5336
> Project: Qpid
> Issue Type: Bug
> Components: C++ Tests
>Affects Versions: 0.25
> Environment: Freebsd
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
> Fix For: 0.27
>
>
> The qpid test scripts will not run under FreeBSD because they have a
> hardcoded notion that bash is found at /bin/bash. However under FreeBSD it is
> actually found in /usr/local/bin/bash.
> We need to change the line which says {{"\#\!/bin/bash"}} to
> {{"\#\!/usr/bin/env bash"}}
> There are actually a small number of places where other script interpreters
> have their location hardcoded too - python. ruby and perl. These all need to
> be {{"\#\!/usr/bin/env ..."}}.
> The *only* script interpreter (that we use) that can be hardcoded is
> {{/bin/sh}} as this is its guaranteed location.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5520) qpid-python-test should not fail for skipped tests.
[ https://issues.apache.org/jira/browse/QPID-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-5520: -- Component/s: Python Test Suite > qpid-python-test should not fail for skipped tests. > --- > > Key: QPID-5520 > URL: https://issues.apache.org/jira/browse/QPID-5520 > Project: Qpid > Issue Type: Bug > Components: Python Test Suite >Reporter: Alan Conway > Fix For: 0.27 > > > The qpid-python-test script has a facility for skipping tests (by > raising a Skipped exception) which works fine BUT if tests are skipped > the script exits with non-0 status - i.e. failure. It should exit with a 0 > exit status (success) unless there are actual failures. > See discussion at: > http://apache-qpid-developers.2158895.n2.nabble.com/qpid-python-test-script-should-skipped-tests-be-considered-failures-td7592307.html -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7400) Allow Proton 0.14 to be used without warning
[ https://issues.apache.org/jira/browse/QPID-7400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-7400: -- Component/s: C++ Build > Allow Proton 0.14 to be used without warning > > > Key: QPID-7400 > URL: https://issues.apache.org/jira/browse/QPID-7400 > Project: Qpid > Issue Type: Improvement > Components: C++ Build >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: qpid-cpp-1.35.0 > > > Proton 0.14 has been released, and built and tested with qpid-cpp 1.35 > without problem. So qpid-cpp should not warn on this version of Proton any > longer. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-1) Use JMSException subclass in place of NotImplementException
[ https://issues.apache.org/jira/browse/QPID-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-1: --- Component/s: Java Client > Use JMSException subclass in place of NotImplementException > --- > > Key: QPID-1 > URL: https://issues.apache.org/jira/browse/QPID-1 > Project: Qpid > Issue Type: Bug > Components: Java Client >Reporter: Gordon Sim >Priority: Minor > > e.g. for setJMSDestination() on AbstractJMSMessage > 2006-09-11 12:28:59,568 [Hermes ThreadPool-2] ERROR > hermes.impl.DefaultHermesImpl - Code is not implemented > org.apache.commons.lang.NotImplementedException: Code is not implemented > at > org.apache.qpid.client.message.AbstractJMSMessage.setJMSDestination(AbstractJMSMessage.java:182) > at hermes.impl.DefaultHermesImpl.duplicate(DefaultHermesImpl.java:793) > at > hermes.browser.tasks.CopyOrMoveMessagesTask.createMessage(CopyOrMoveMessagesTask.java:89) > Even better if we can actually implement the behaviour! -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2) BytesMessage.readByte() does not throw MessageEOFException
[ https://issues.apache.org/jira/browse/QPID-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2: --- Component/s: Java Client > BytesMessage.readByte() does not throw MessageEOFException > -- > > Key: QPID-2 > URL: https://issues.apache.org/jira/browse/QPID-2 > Project: Qpid > Issue Type: Bug > Components: Java Client >Reporter: Gordon Sim >Assignee: Robert Greig > > Instead you get: > > java.nio.BufferUnderflowException > at java.nio.Buffer.nextGetIndex(Buffer.java:398) > at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:117) > at org.apache.mina.common.support.BaseByteBuffer.get(BaseByteBuffer.java:202) > at > org.apache.qpid.client.message.JMSBytesMessage.readByte(JMSBytesMessage.java:161) -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-140) topictest script assumes that sh==bash
[ https://issues.apache.org/jira/browse/QPID-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-140: - Component/s: C++ Tests > topictest script assumes that sh==bash > -- > > Key: QPID-140 > URL: https://issues.apache.org/jira/browse/QPID-140 > Project: Qpid > Issue Type: Bug > Components: C++ Tests > Environment: Linux >Reporter: Andrew Stitcher >Assignee: Alan Conway >Priority: Minor > Attachments: topictest.patch > > > the topictest script has #!/bin/sh but then uses bash features, this works in > distros where sh==bash but not those where they are separate. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4940) Remove unmaintained/obsolete QMF code
[
https://issues.apache.org/jira/browse/QPID-4940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-4940:
--
Component/s: QMF
> Remove unmaintained/obsolete QMF code
> -
>
> Key: QPID-4940
> URL: https://issues.apache.org/jira/browse/QPID-4940
> Project: Qpid
> Issue Type: Improvement
> Components: QMF
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
> Fix For: 0.25
>
>
> From email from Ken Giusti to \{users,dev\}@qpid.apache.org
> There's some old QMF-related code in our repo that appears to be quite dead.
> First, there's stuff that I'm almost certain is stone cold dead. AFAIK, this
> shouldn't be used by anyone. It certainly isn't being maintained.
> Specifically:
> * qpid/extras/qmf/src/py/qmf2-prototype
> ** experimental stuff done while developing QMFv2.
> * qpid/cpp/\{include,src\}/qmf/engine
> ** an attempt to re-write QMFv1 in C++.
> * qpid/cpp/bindings/qmf
> ** multi-language bindings for the above 'engine' code
> There's other stuff that appears to have shuffled off the mortal coil, but
> may simply be in a deep coma. These would be the old QMFv1 agent and onsole
> libraries:
> * qpid/cpp/\{include,src\}/qpid/agent
> * qpid/cpp/\{include,src\}/qpid/console
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4928) Some of C++ CMake build tests need to start/stop a broker themselves
[ https://issues.apache.org/jira/browse/QPID-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4928: -- Component/s: C++ Tests > Some of C++ CMake build tests need to start/stop a broker themselves > > > Key: QPID-4928 > URL: https://issues.apache.org/jira/browse/QPID-4928 > Project: Qpid > Issue Type: Improvement > Components: C++ Tests >Reporter: Andrew Stitcher > > CMake has a companion tool CTest which can be used to run tests individually. > This means that each of the tests must be self contained. > Currently a bunch of the tests rely on a previous test "start_broker" to > start a required broker which is stopped by a subsequent test "stop_broker". > The start and stop steps should be brought into the individual tests that > need a broker. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4927) C++ CMake tests need to use valgrind the same way that the autotools build does
[ https://issues.apache.org/jira/browse/QPID-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4927: -- Component/s: C++ Tests > C++ CMake tests need to use valgrind the same way that the autotools build > does > --- > > Key: QPID-4927 > URL: https://issues.apache.org/jira/browse/QPID-4927 > Project: Qpid > Issue Type: Improvement > Components: C++ Tests >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.25 > > > To catch the same range of errors the cmake build tests need to use valgrind > to run the C++ broker and C++ clients in the tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5306) Improve cmake testing structure
[ https://issues.apache.org/jira/browse/QPID-5306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-5306: -- Component/s: C++ Tests > Improve cmake testing structure > --- > > Key: QPID-5306 > URL: https://issues.apache.org/jira/browse/QPID-5306 > Project: Qpid > Issue Type: Improvement > Components: C++ Tests >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.25 > > > Improve run_test test wrapper script so that it can run tests in various > different ways. > This is necessary to allow tests to run in a different directory from the > build directory that corresponds to the source cmake file. > It is also useful to allow consolidation of the various test scripts: So far > some of the starting and stopping broker work in tests has been centralised > into this script too. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5305) Valgrind reports uninitialised values sent to system call in legacystore
[ https://issues.apache.org/jira/browse/QPID-5305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-5305: -- Component/s: C++ Broker > Valgrind reports uninitialised values sent to system call in legacystore > > > Key: QPID-5305 > URL: https://issues.apache.org/jira/browse/QPID-5305 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.25 > Environment: unix >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.25 > > > Running the legacystore tests under valgrind highlight that it doesn't > initialise all the values it sends to disk. > Even if these bytes are actually never used when the store is read, having > this behaviour makes it hard to use valgrind to check that the store doesn't > have other problems. > There is a compile time option to enable initialising of the full written > buffer, I think it is wise to enable this option always, so that testing > using valgrind is productive. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5215) Legacystore: Import rest of tests and utilities
[ https://issues.apache.org/jira/browse/QPID-5215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-5215: -- Component/s: C++ Broker > Legacystore: Import rest of tests and utilities > --- > > Key: QPID-5215 > URL: https://issues.apache.org/jira/browse/QPID-5215 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.25 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4627) Implement remaining special identifiers
[ https://issues.apache.org/jira/browse/QPID-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4627: -- Component/s: C++ Broker > Implement remaining special identifiers > --- > > Key: QPID-4627 > URL: https://issues.apache.org/jira/browse/QPID-4627 > Project: Qpid > Issue Type: Sub-task > Components: C++ Broker >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > > The remaining JMS specified identifiers are: > amqp.correlation_id > amqp.message_id > amqp.creation_time > amqp.jms_type > The ones remaining from the AMQP Apache filters spec are: > amqp.to > amqp.reply_to > amqp.absolute_expiration_time > - amqp.durable (it's not clear this is really there as distinct from > amqp.delivery_mode) > - amqp.delivery_count (it's not clear this is really there as distinct from > amqp.redelivered) > In order to implement these special identifiers there will need to be extra > work to abstract some of these values from the 0-10 or 1-0 message code. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-1601) Parameterize the amqp url used in qmf tests
[ https://issues.apache.org/jira/browse/QPID-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-1601: -- Component/s: QMF > Parameterize the amqp url used in qmf tests > --- > > Key: QPID-1601 > URL: https://issues.apache.org/jira/browse/QPID-1601 > Project: Qpid > Issue Type: Improvement > Components: QMF > Environment: [jross@qpid-test ruby]$ uname -a > Linux qpid-test.lab.bos.redhat.com 2.6.18-92.1.6.el5 #1 SMP Fri Jun 20 > 02:36:06 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux > [jross@qpid-test ruby]$ ruby -v > ruby 1.8.5 (2006-08-25) [x86_64-linux] > [jross@qpid-test ruby]$ cat /etc/redhat-release > Red Hat Enterprise Linux Server release 5.2 (Tikanga) >Reporter: Justin Ross >Assignee: Ted Ross > Labels: old_ruby_test_suite_component > Fix For: 0.5 > > Attachments: ruby-parameterize-qmf-test-port.patch > > > Right now there's a hard coded url of amqp://localhost:5672. This prevents > us from running automated tests on systems that already have a broker running > at the default port, for other purposes. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5030) JMS client to use C++ broker selectors
[ https://issues.apache.org/jira/browse/QPID-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-5030: -- Labels: patch (was: ) > JMS client to use C++ broker selectors > -- > > Key: QPID-5030 > URL: https://issues.apache.org/jira/browse/QPID-5030 > Project: Qpid > Issue Type: Sub-task > Components: Java Client >Reporter: Andrew Stitcher > Labels: patch > Attachments: Translator.java > > > As the current C++ broker selector work stands it is compliant with the > registered amqp 1.0 filter extension, but the JMS client will not use the C++ > broker selectors for anything still falling back to the client side selectors. > We should allow the JMS client to use the c++ broker selectors. > There are roughly 2 ways to do this and both may be needed: > For amqp 1.0 we need the client to translate the JMS specified identifiers to > the ones specified in the extension and to use a filter - this may never be > work sensible to do in the existing client. > For earlier protocol versions, we probably need to add code to the C++ broker > which accepts the extra subscription property that the java client uses for > the selector and add some code which recognises the JMS identifiers instead > of the amqp extension identifiers. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5030) JMS client to use C++ broker selectors
[ https://issues.apache.org/jira/browse/QPID-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-5030: -- Component/s: Java Client > JMS client to use C++ broker selectors > -- > > Key: QPID-5030 > URL: https://issues.apache.org/jira/browse/QPID-5030 > Project: Qpid > Issue Type: Sub-task > Components: Java Client >Reporter: Andrew Stitcher > Labels: patch > Attachments: Translator.java > > > As the current C++ broker selector work stands it is compliant with the > registered amqp 1.0 filter extension, but the JMS client will not use the C++ > broker selectors for anything still falling back to the client side selectors. > We should allow the JMS client to use the c++ broker selectors. > There are roughly 2 ways to do this and both may be needed: > For amqp 1.0 we need the client to translate the JMS specified identifiers to > the ones specified in the extension and to use a filter - this may never be > work sensible to do in the existing client. > For earlier protocol versions, we probably need to add code to the C++ broker > which accepts the extra subscription property that the java client uses for > the selector and add some code which recognises the JMS identifiers instead > of the amqp extension identifiers. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4545) AMQP 1.0 support doesn't work under cmake build
[ https://issues.apache.org/jira/browse/QPID-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4545: -- Component/s: C++ Build > AMQP 1.0 support doesn't work under cmake build > --- > > Key: QPID-4545 > URL: https://issues.apache.org/jira/browse/QPID-4545 > Project: Qpid > Issue Type: Bug > Components: C++ Build >Affects Versions: 0.20 >Reporter: Gordon Sim >Assignee: Gordon Sim >Priority: Critical > Fix For: 0.21 > > Attachments: QPID-4545.patch > > > Dues to required internal symbols being hidden now > (http://svn.apache.org/viewvc/qpid/trunk/qpid/cpp/src/CMakeLists.txt?r1=1406353&r2=1406352&pathrev=1406353). -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7693) SSL client socket leaks a file descriptor
[ https://issues.apache.org/jira/browse/QPID-7693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-7693: -- Component/s: C++ Client > SSL client socket leaks a file descriptor > - > > Key: QPID-7693 > URL: https://issues.apache.org/jira/browse/QPID-7693 > Project: Qpid > Issue Type: Bug > Components: C++ Client >Affects Versions: qpid-cpp-1.36.0 >Reporter: Gordon Sim >Assignee: Gordon Sim > Fix For: qpid-cpp-1.37.0 > > > A prototype socket is create for every client ssl socket, even though that > prototype socket is actually only needed/used for server sockets. The > prototype socket is not closed when the SslSocket instance is closed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2711) Add version and icon resources to Windows C++ exe/dll files
[ https://issues.apache.org/jira/browse/QPID-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2711: -- Component/s: C++ Build > Add version and icon resources to Windows C++ exe/dll files > --- > > Key: QPID-2711 > URL: https://issues.apache.org/jira/browse/QPID-2711 > Project: Qpid > Issue Type: Improvement > Components: C++ Build >Affects Versions: 0.7 >Reporter: Chuck Rolke >Assignee: Ted Ross > Fix For: 0.7 > > Attachments: qpid_cpp-add-win32-version-and-icon-5.patch, > qpid-icon.ico > > > Windows DLL and EXE files produced by qpid/cpp need a version resource and > the EXE files need an icon. This issue tracks the addition of those resources. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2755) Windows SDK has no README
[ https://issues.apache.org/jira/browse/QPID-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2755: -- Component/s: C++ Documentation > Windows SDK has no README > - > > Key: QPID-2755 > URL: https://issues.apache.org/jira/browse/QPID-2755 > Project: Qpid > Issue Type: Bug > Components: C++ Documentation >Reporter: Chuck Rolke >Assignee: Ted Ross > Fix For: 0.7 > > Attachments: add_winsdk_readme_file.patch > > > The winsdk file is produced with no README. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2764) WinSdk cpp examples do not compile
[ https://issues.apache.org/jira/browse/QPID-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2764: -- Component/s: C++ Client > WinSdk cpp examples do not compile > -- > > Key: QPID-2764 > URL: https://issues.apache.org/jira/browse/QPID-2764 > Project: Qpid > Issue Type: Bug > Components: C++ Client > Environment: windows sdk >Reporter: Chuck Rolke >Assignee: Ted Ross > Fix For: 0.7 > > Attachments: qpid_cpp_examples_messaging-add-qpidtypes.patch > > > The vcproj files for the \examples directory are missing a reference to the > relatively new qpidtypes.lib. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2805) The windows resource version for qmfengine dll is hard coded to an unusable value
[ https://issues.apache.org/jira/browse/QPID-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2805: -- Component/s: C++ Build > The windows resource version for qmfengine dll is hard coded to an unusable > value > - > > Key: QPID-2805 > URL: https://issues.apache.org/jira/browse/QPID-2805 > Project: Qpid > Issue Type: Bug > Components: C++ Build > Environment: windows sdk build >Reporter: Chuck Rolke >Assignee: Ted Ross > Fix For: 0.7 > > Attachments: Unpin_qmfengine_version.patch > > > One line in the cmake for cpp/qmf.dll confuses the "windows resource version" > that ones sees from windows explorer with the "image version" that is > embedded in the binary optional header. > The cmake must be changed so that all dll files created by a bld-winsdk.ps1 > build have the same windows resource version. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2785) QpidTypes.pdb is not installed
[ https://issues.apache.org/jira/browse/QPID-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2785: -- Component/s: C++ Build > QpidTypes.pdb is not installed > -- > > Key: QPID-2785 > URL: https://issues.apache.org/jira/browse/QPID-2785 > Project: Qpid > Issue Type: Bug > Components: C++ Build > Environment: Windows build >Reporter: Chuck Rolke >Assignee: Ted Ross > Fix For: 0.7 > > Attachments: qpidtypes-pdb-missing.patch > > > The qpidtypes.pdb and qpidtypesd.pdb files are missing from the WinSDK. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2865) Cpp messaging examples compile problems for x64
[ https://issues.apache.org/jira/browse/QPID-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2865: -- Component/s: C++ Client > Cpp messaging examples compile problems for x64 > --- > > Key: QPID-2865 > URL: https://issues.apache.org/jira/browse/QPID-2865 > Project: Qpid > Issue Type: Improvement > Components: C++ Client >Reporter: Chuck Rolke > Fix For: 0.7 > > Attachments: > qpid_cpp_examples_messaging-FixConcurrentCompilesX64.patch > > > When compiling the x64 cpp/examples/messaging suite in x64 mode there are > errors because all the BuildLog files go to the same place. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3902) Add formal message categories to C++ Broker log messages
[
https://issues.apache.org/jira/browse/QPID-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-3902:
--
Component/s: C++ Broker
> Add formal message categories to C++ Broker log messages
>
>
> Key: QPID-3902
> URL: https://issues.apache.org/jira/browse/QPID-3902
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker
>Reporter: Chuck Rolke
> Fix For: 0.17
>
> Attachments: qpid-log-src-tabbed2.txt
>
>
> h3. This is a proposal to add log categories to C++ Broker log messages.
> h4. Problem Statement
> There are difficulties working with C++ Broker logging when appplying a log
> filter criterion. What precise FILTERTEXT can a user specify for:
> {noformat}
> --log-enable debug+:FILTERTEXT
> {noformat}
> Even after the fix from QPID-3891 it is not intuitive what to specify for a
> FILTERTEXT and any useful filter requires detailed knowledge of the source
> code.
> h4. Proposal
> A log category is a high-level classification of the nature of the logged
> event that is not tied to a particular source module or code function name.
> This log category would become the target for FILTERTEXT log filters.
> The following list is the proposed log category definition. Each log category
> name is followed by a list of source code directory names that would
> generally produce logs using that log category.
> ||Category||Source code directory||
> |Security|acl ssl gssapi sasl cyrus|
> |Broker | broker|
> |Management| agent console qmf|
> |Amqp|amqp_0_10 framing|
> |System| log sys types xml thread mutex fork pipe time ...|
> |HA| cluster ha replication|
> |Messaging| messaging client|
> |Store| store|
> |IO| tcp rdma AsynchIO socket epoll|
> |Test| |
> |Unspecified| |
> There is no strict rule that a module produce only log entries of a specific
> category.
> The category would be inserted into each log message after the time of day
> but before the message text.
> {noformat}
> 2012-03-06 16:55:38 [Management] SEND PackageInd
> package=org.apache.qpid.broker to=schema.package
> {noformat}
> A user could then filter log messages by using the category names:
> {noformat}
> --log-enable debug+:Management
> {noformat}
> This scheme would have a number of benefits:
> 1. On a per-message basis the filter comparisons would be using enumeration
> values and not strings.
> 2. The feature could be documented sensibly.
> 3. Log files would be easier to interpret manually or by event management
> systems.
> The classifications could be phased in gradually. The current
> QPID_LOG(LEVEL, MESSAGE) would produce [Unspecfied] events while the new
> QPID_LOG_CAT(LEVEL, CATEGORY, MESSAGE) would produce events using an actual
> category.
> Similar additions are made for the QPID_MSG entries.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3901) 0.16 Release issues for Windows
[ https://issues.apache.org/jira/browse/QPID-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-3901: -- Component/s: C++ Client > 0.16 Release issues for Windows > --- > > Key: QPID-3901 > URL: https://issues.apache.org/jira/browse/QPID-3901 > Project: Qpid > Issue Type: Bug > Components: C++ Client >Reporter: Chuck Rolke >Assignee: Chuck Rolke > Fix For: 0.16, 0.17 > > > This issue collects various minor issues related to the 0.16 Release and > Windows. > The expectation is that the only issues solved here are of trivial, NO-JIRA > complexity. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2667) Cpp INSTALL-WINDOWS build instructions are out of date
[ https://issues.apache.org/jira/browse/QPID-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2667: -- Component/s: C++ Build > Cpp INSTALL-WINDOWS build instructions are out of date > -- > > Key: QPID-2667 > URL: https://issues.apache.org/jira/browse/QPID-2667 > Project: Qpid > Issue Type: Improvement > Components: C++ Build >Reporter: Chuck Rolke >Assignee: Ted Ross > Fix For: 0.7 > > Attachments: cpp_install_windows.patch > > > The instructions for building qpid/cpp under windows are out-of-date. Some > time ago CMake was instituted to autogenerate visual studio project and > solution files. The instructions still refer to the old solution files which > are gone. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2952) Qpid Cpp Messaging .NET Binding - Address constructor mishandles Name and Type fields
[ https://issues.apache.org/jira/browse/QPID-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2952: -- Component/s: .NET Client > Qpid Cpp Messaging .NET Binding - Address constructor mishandles Name and > Type fields > - > > Key: QPID-2952 > URL: https://issues.apache.org/jira/browse/QPID-2952 > Project: Qpid > Issue Type: Bug > Components: .NET Client >Affects Versions: 0.8 > Environment: Windows builds >Reporter: Chuck Rolke >Assignee: Chuck Rolke > Fix For: 0.9 > > > Attempts to set the address Type property actually set the Name property. > Found during development of unit tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2939) Qpid .NET Messaging Binding has stray references and using statements
[ https://issues.apache.org/jira/browse/QPID-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2939: -- Component/s: .NET Client > Qpid .NET Messaging Binding has stray references and using statements > - > > Key: QPID-2939 > URL: https://issues.apache.org/jira/browse/QPID-2939 > Project: Qpid > Issue Type: Improvement > Components: .NET Client >Affects Versions: 0.9 > Environment: Windows build >Reporter: Chuck Rolke >Assignee: Chuck Rolke > Fix For: 0.9 > > > Various projects in the .NET Binding for Qpid Messaging have references to > assemblies that are not needed. Further, several source modules have 'using' > clauses that are not needed. > Aside from being ordinary 'bad form', the extra references create false > dependencies on .NET Framework 3.5 that prevent a user from conveniently > refactoring the code to use .NET Framework 2.0. Nothing in the .NET Binding > depends on any features of any .NET Framework beyond v2.0. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2933) Messaging .NET binding has several assembly properties misnamed
[ https://issues.apache.org/jira/browse/QPID-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2933: -- Component/s: .NET Client > Messaging .NET binding has several assembly properties misnamed > --- > > Key: QPID-2933 > URL: https://issues.apache.org/jira/browse/QPID-2933 > Project: Qpid > Issue Type: Bug > Components: .NET Client >Affects Versions: 0.9 > Environment: Windows build for .NET Binding >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Minor > Fix For: 0.9 > > > Several files have cut-paste errors in AssemblyInfo.cs files, misnaming > AssemblyTitle and AssemblyProduct -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2924) Refactor WinSDK to create separate debug and release /bin directories
[ https://issues.apache.org/jira/browse/QPID-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2924: -- Component/s: C++ Client > Refactor WinSDK to create separate debug and release /bin directories > - > > Key: QPID-2924 > URL: https://issues.apache.org/jira/browse/QPID-2924 > Project: Qpid > Issue Type: Improvement > Components: C++ Client >Affects Versions: 0.7 > Environment: WinSDK build >Reporter: Chuck Rolke >Assignee: Chuck Rolke > Fix For: 0.7 > > > In the current WinSDK the \bin directory has become overloaded and difficult > to use. > The directory currently holds: > * Boost (debug and release) > * Qpid libraries (debug and release) > * MSVC runtime (release) > * .NET Messaging Binding libraries (debug) > A user may: > 1. To Compile/Run Debug > 1a. C++ - Load the project and go > 1b. .NET - Load the project and go. > 2. To Compile/Run Release > 2a. C++ - Load the project, flip the settings, and go > 2b. .NET - Unpack the release libraries from zip, load the project, flip > settings and references, and go > After building the examples the \bin directory has 78 files in it. > As a developer this isn't really that bad. But for a new user it gets harder > to explain, particularly for the .NET examples. Between debug and release, > C++ (.vcproj) projects have a simple way to specify differently-named > libraries and differently named output files. .NET (.csproj) projects are not > so simple: changing the names of a dependent library involve removing a > reference and adding a references to the new file, and there is no great way > at all to change the name of an output file. > Currently the bld-winsdk procedure produces two zip files, one each for x86 > and x64 platforms. I propose to change the build to produce four zip files: > x86-debug, x86-release, x64-debug, and x64-release. This has advantages and > disadvantages: > Advantages: > * Each \bin directory is smaller and more easily understood > * The directory arrangement prevents a user from mixing libraries from > incompatible (debug vs release) component builds. > * Customer's will have an easier time copying the kit's basic binary > distribution as the debug and release parts are separate, and > * Customer will not have to unzip and manage debug and release versions of a > files that share the same name. > * Kit consumers have already asked for this. > Disadvantages: > * There will be extra copies of identical example source files and project > setting files. > Implementing this will involve NO CHANGE to the qpid messaging library > compile settings, minor changes to the .NET binding settings, and some > moderate hacking in the bld-winsdk.ps1 script. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2863) Propagate WinSDK Build Version numbers to the Messaging .NET Binding
[ https://issues.apache.org/jira/browse/QPID-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2863: -- Component/s: .NET Client > Propagate WinSDK Build Version numbers to the Messaging .NET Binding > > > Key: QPID-2863 > URL: https://issues.apache.org/jira/browse/QPID-2863 > Project: Qpid > Issue Type: Improvement > Components: .NET Client > Environment: WinSDK build >Reporter: Chuck Rolke > Fix For: 0.7 > > Attachments: dotnet-binding-versioning.patch > > > CMake propagates Windows version numbers to all the Qpid components in > WinSDK. The Cpp Messaging .NET Binding DLLs do not pick up the version > numbers. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2866) Remove unneeded build files and directory
[ https://issues.apache.org/jira/browse/QPID-2866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2866: -- Component/s: C++ Client > Remove unneeded build files and directory > - > > Key: QPID-2866 > URL: https://issues.apache.org/jira/browse/QPID-2866 > Project: Qpid > Issue Type: Improvement > Components: C++ Client >Reporter: Chuck Rolke > Fix For: 0.7 > > Attachments: cpp_bindings_qpid_dotnet-DeleteBldDirectory.patch > > > Changes made in QPID-2827 make some files obsolete. This action removes them. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2923) Qpid Messaging .NET Binding fails to translate exceptions from C++ to .NET
[
https://issues.apache.org/jira/browse/QPID-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-2923:
--
Component/s: .NET Client
> Qpid Messaging .NET Binding fails to translate exceptions from C++ to .NET
> --
>
> Key: QPID-2923
> URL: https://issues.apache.org/jira/browse/QPID-2923
> Project: Qpid
> Issue Type: Bug
> Components: .NET Client
>Affects Versions: 0.7
> Environment: Windows
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
> Fix For: 0.7
>
>
> While adding the FailoverUpdate object a problem in the .NET Binding's scheme
> of error handling showed up. This issue will document the original problem
> and show a proposed coding pattern to make it better.
> Two versions of the FailoverUpdates constructor:
> *
> Original Version
> *
> FailoverUpdates::FailoverUpdates(Connection ^ connection) :
> failoverupdatesp(new
> ::qpid::messaging::FailoverUpdates(*(connection->NativeConnection)))
> {
> }
> This looks OK to me from a pure C++ standpoint. The problem comes from the
> environment in which this code runs. It is called by a managed C# or other
> .NET caller and it calls into the unmanaged C++ Qpid Messaging code. Using
> this code when the C++ code throws, the exception goes to a handler that does
> not understand what to do with it.
> A. If the user has no try-catch in the .NET calling code then a popup box
> shows:
> ---
> Microsoft Visual C++ Runtime Library
> ---
> Runtime Error!
> Program: ...\src\Debug\csharp.map.sender.vshost.exe
> This application has requested the Runtime to terminate it in an unusual
> way.
> Please contact the application's support team for more information.
> "in an unusual way"? What does that mean? This is not good.
> *
> Improved Version
> *
> FailoverUpdates::FailoverUpdates(Connection ^ connection)
> {
> System::Exception ^ newException = nullptr;
> try {
> failoverupdatesp = new
> ::qpid::messaging::FailoverUpdates(*(connection->NativeConnection));
> }
> catch (const ::qpid::types::Exception & error) {
> String ^ errmsg = gcnew String(error.what());
> newException= gcnew QpidException(errmsg);
> }
> if (newException != nullptr) {
> throw newException;
> }
> }
> The idea is to catch the exception from native C++ and rethrow it as a
> System::Exception.
> B. Now the user sees:
> An unhandled exception of type 'Org.Apache.Qpid.Messaging.QpidException'
> occurred in org.apache.qpid.messagingd.dll
> Additional information: Connection has not yet been opened
> (..\..\cpp\src\qpid\client\Connection.cpp:139)
>
> I think the beauty of using a member initialization list is overshadowed by
> the fact that the original version mishandles exceptions. I intend to replace
> all instances of the .NET binding's constructors with the same pattern.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2915) Qpid Cpp Messaging .NET Binding does not properly handle Qpid type VAR_VOID
[ https://issues.apache.org/jira/browse/QPID-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2915: -- Component/s: .NET Client > Qpid Cpp Messaging .NET Binding does not properly handle Qpid type VAR_VOID > --- > > Key: QPID-2915 > URL: https://issues.apache.org/jira/browse/QPID-2915 > Project: Qpid > Issue Type: Bug > Components: .NET Client >Reporter: Chuck Rolke >Assignee: Chuck Rolke > Fix For: 0.7 > > > Sending nullptr or receiving Qpid type VAR_VOID causes the binding to fail. > Sending nullptr should send a VAR_VOID value to Messaging. > Receiving a VAR_VOID should send a nullptr in place of an actual object to > .NET binding clients. > The Message decoder will display a zero-length string when ToString() > processes a nullptr. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2918) Assembly mis-named in csharp.example.declare_queues
[ https://issues.apache.org/jira/browse/QPID-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2918: -- Component/s: .NET Client > Assembly mis-named in csharp.example.declare_queues > --- > > Key: QPID-2918 > URL: https://issues.apache.org/jira/browse/QPID-2918 > Project: Qpid > Issue Type: Bug > Components: .NET Client >Affects Versions: 0.7 >Reporter: Chuck Rolke >Assignee: Chuck Rolke > Fix For: 0.7 > > > Cut and paste error has assembly misnamed in an example. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2922) Qpid Cpp Messaging .NET Binding does not implement FailoverUpdate class
[ https://issues.apache.org/jira/browse/QPID-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2922: -- Component/s: .NET Client > Qpid Cpp Messaging .NET Binding does not implement FailoverUpdate class > --- > > Key: QPID-2922 > URL: https://issues.apache.org/jira/browse/QPID-2922 > Project: Qpid > Issue Type: Bug > Components: .NET Client >Affects Versions: 0.7 > Environment: Windows builds >Reporter: Chuck Rolke >Assignee: Chuck Rolke > Fix For: 0.7 > > > The FailoverUpdate class is missing. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2906) Qpid WinSDK .NET Binding does not support Release configuration
[ https://issues.apache.org/jira/browse/QPID-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2906: -- Component/s: .NET Client > Qpid WinSDK .NET Binding does not support Release configuration > --- > > Key: QPID-2906 > URL: https://issues.apache.org/jira/browse/QPID-2906 > Project: Qpid > Issue Type: Improvement > Components: .NET Client >Reporter: Chuck Rolke > Fix For: 0.7 > > > The .NET binding to C++ Messaging does not include Release mode. The Release > mode compile issues were fixed in QPID-2895. This issue tracks the > propagation of improvements into the WinSDK. Several other issues surrounding > the WinSDK also need cleanup. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4427) C++ Messaging Client .NET Binding failed to wrap Receiver.close() managed exception
[ https://issues.apache.org/jira/browse/QPID-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4427: -- Component/s: .NET Client > C++ Messaging Client .NET Binding failed to wrap Receiver.close() managed > exception > --- > > Key: QPID-4427 > URL: https://issues.apache.org/jira/browse/QPID-4427 > Project: Qpid > Issue Type: Bug > Components: .NET Client >Affects Versions: 0.18 >Reporter: Chuck Rolke >Assignee: Chuck Rolke > Fix For: 0.19 > > > Issue QPID-2923 covered the reasons wrapping the unmanaged native exceptions > and returning managed exceptions to the .NET application. > This issue covers one instance that didn't get the treatment. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2827) QPID Cpp WinSDK does not contain 64-bit libraries
[ https://issues.apache.org/jira/browse/QPID-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2827: -- Component/s: C++ Client > QPID Cpp WinSDK does not contain 64-bit libraries > - > > Key: QPID-2827 > URL: https://issues.apache.org/jira/browse/QPID-2827 > Project: Qpid > Issue Type: Improvement > Components: C++ Client > Environment: Windows >Reporter: Chuck Rolke >Assignee: Ted Ross > Fix For: 0.7 > > Attachments: restore-less-than-char.patch, x64-qwip-07.patch > > > The kit build procedure and the hard-coded kit example files support 32-bit > Win32 only. This issue tracks the addition of the x64 platform. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2913) QPID Cpp Messaging Libraries for WinSDK Are Not Signed
[ https://issues.apache.org/jira/browse/QPID-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2913: -- Component/s: C++ Client > QPID Cpp Messaging Libraries for WinSDK Are Not Signed > -- > > Key: QPID-2913 > URL: https://issues.apache.org/jira/browse/QPID-2913 > Project: Qpid > Issue Type: Improvement > Components: C++ Client >Reporter: Chuck Rolke >Assignee: Chuck Rolke > Fix For: 0.7 > > > The DLLs produced for Qpid Cpp Messaging binding are signed only in Debug > mode. Also, the sessionreceiver object is never signed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-105) Research and install generic logging system for C++ broker
[ https://issues.apache.org/jira/browse/QPID-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-105: - Component/s: C++ Broker > Research and install generic logging system for C++ broker > -- > > Key: QPID-105 > URL: https://issues.apache.org/jira/browse/QPID-105 > Project: Qpid > Issue Type: Task > Components: C++ Broker >Reporter: Carl Trieloff >Assignee: Carl Trieloff > Fix For: M2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-1370) LVQ pointer containment / incomplete browse
[ https://issues.apache.org/jira/browse/QPID-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-1370: -- Component/s: C++ Broker > LVQ pointer containment / incomplete browse > --- > > Key: QPID-1370 > URL: https://issues.apache.org/jira/browse/QPID-1370 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: M4 >Reporter: Carl Trieloff > Fix For: M4 > > > It is not clear the way I reference the deque will be safe if stl updates. > This jira is to make lvq insensitive to stl changes + update browse behavior. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4179) Cluster does not replicate exclusive status of queues.
[
https://issues.apache.org/jira/browse/QPID-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-4179:
--
Component/s: C++ Clustering
> Cluster does not replicate exclusive status of queues.
> --
>
> Key: QPID-4179
> URL: https://issues.apache.org/jira/browse/QPID-4179
> Project: Qpid
> Issue Type: Bug
> Components: C++ Clustering
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: 0.19
>
>
> To reproduce run this script:
> -
> QPIDD="qpidd --auth=no -d --cluster-name=foo -p0 --no-data-dir -t
> --load-module=src/.libs/cluster.so --log-to-file"
> PORTA=$($QPIDD qpiddA.log)
> ./examples/messaging/spout -b user/user@localhost:$PORTA "exclQ.A; {create:
> sender, delete:receiver, node:{ x-declare:{ auto-delete: false, exclusive:
> true } } }" "$(date| md5sum)"
> PORTB=$($QPIDD qpiddB.log)
> echo $PORTA $PORTB
> qpid-stat -b localhost:$PORTA -q
> qpid-stat -b localhost:$PORTB -q
> -
> Note the queue is exclusive in the first qpid-stat output and not in the
> second.
> They should be the same.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4391) HA replicating subscriptions should not auto-delete queues
[ https://issues.apache.org/jira/browse/QPID-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4391: -- Component/s: C++ Clustering > HA replicating subscriptions should not auto-delete queues > -- > > Key: QPID-4391 > URL: https://issues.apache.org/jira/browse/QPID-4391 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Reporter: Alan Conway > Fix For: 0.19 > > > Description of problem: > When an auto-delete queue is replicated, the replicating subscription > attempts to auto-delete the queue after it has already been auto-deleted by > the closing of the last non-HA consumer. An issue occurs if a new > auto-delete queue with the same name is created shortly after the deletion of > the previously queue. This can occur when a client subscribes to an > auto-delete queue and is temporarily disconnected from the broker. It is > possible for the cancelled HA subscription to remove the newly created queue > from the queue registry since the old and new queues use the same names. The > HA replicating subscription should not execute the auto-delete logic when the > subscription is cancelled. > Version-Release number of selected component (if applicable): > Qpid 0.18 > How reproducible: > Frequently > Steps to Reproduce: > Race condition between a consumer auto-deleting and recreating a queue of the > same name and the HA replicating subscription auto-deleting the original > queue. If the HA replicating subscription auto-deletes the original queue > after the new queue is created, the new queue is removed from the queue > registry. > > Actual results: > New queue is removed from the queue registry. > Expected results: > HA subscription does not attempt to auto-delete the queue and therefore the > new queue is not removed from the queue registry. > Additional info: https://bugzilla.redhat.com/show_bug.cgi?id=868364 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2266) error sending update: Enqueue capacity threshold exceeded
[ https://issues.apache.org/jira/browse/QPID-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2266: -- Component/s: C++ Clustering > error sending update: Enqueue capacity threshold exceeded > -- > > Key: QPID-2266 > URL: https://issues.apache.org/jira/browse/QPID-2266 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.6 > > > From https://bugzilla.redhat.com/show_bug.cgi?id=509796 > Description of problem: > Adding a new node to a cluster failed with a journal capacity exception. > However the new node was using the default journal size options as was the > existing cluster node so its not clear why this error should occur. > Version-Release number of selected component (if applicable): > qpidd-0.5.752581-22.el5 > rhm-0.5.3206-5.el5 > How reproducible: > Fairly easily > Steps to Reproduce: > 1. start one cluster node > 2. run while perftest --durable true --count 5 --size 8 --summary; do > true; done > 3. while this is running add a new node to the cluster, then stop it, then > re-add it and repeat this for several times until eventually you see an error > Actual results: > 2009-jul-06 05:07:10 notice Journal "perftest0": Created > 2009-jul-06 05:07:11 warning Journal "perftest0": Enqueue capacity threshold > exceeded on queue "perftest0". > 2009-jul-06 05:07:11 error Unexpected exception: Enqueue capacity threshold > exceeded on queue "perftest0". (JournalImpl.cpp:576) > 2009-jul-06 05:07:11 error Connection 10.16.44.221:46092 closed by error: > Enqueue capacity threshold exceeded on queue "perftest0". > (JournalImpl.cpp:576)(501) > 2009-jul-06 05:07:11 error Channel exception: not-attached: Channel 1 is not > attached (qpid/amqp_0_10/SessionHandler.cpp:40) > 2009-jul-06 05:07:11 critical 10.16.44.221:19499(UPDATEE) catch-up connection > closed prematurely 10.16.44.221:19499-1(local,catchup) > 2009-jul-06 05:07:11 notice 10.16.44.221:19499(LEFT) leaving cluster > grs-mrg14-test-cluster > 2009-jul-06 05:07:11 notice Shut down > Expected results: > Should always be able to add the new node since the queue on the original node > in the cluster has the same capacity. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3208) Exchanges make best effort to route messages if there is an error.
[ https://issues.apache.org/jira/browse/QPID-3208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-3208: -- Component/s: C++ Broker > Exchanges make best effort to route messages if there is an error. > -- > > Key: QPID-3208 > URL: https://issues.apache.org/jira/browse/QPID-3208 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.11 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.11 > > > If multiple queues are bound to the same routing key, > then a failure to deliver to one of the queues (e.g. policy limit > error) could prevent delivery on some of the other queues. > The exchange should deliver to every queue that did not > have an error before raising an error. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2894) Reload-ACL command is not on any management tools
[ https://issues.apache.org/jira/browse/QPID-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2894: -- Component/s: C++ Tools > Reload-ACL command is not on any management tools > - > > Key: QPID-2894 > URL: https://issues.apache.org/jira/browse/QPID-2894 > Project: Qpid > Issue Type: Improvement > Components: C++ Tools >Affects Versions: 0.6 >Reporter: Alan Conway >Assignee: Ted Ross > Fix For: 0.15 > > > The reload-ACL command needs to be added to one of the management tools, > probably qpid-config. > Python code to reload the ACL: > import qmf.console > import optparse > qmf = qmf.console.Session() > qmf_broker = qmf.addBroker(opts.broker) > acl = qmf.getObjects(_class="acl")[0] > result = acl.reloadACLFile() > print result.txt -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2236) cmake build fails to build cluster module.
[ https://issues.apache.org/jira/browse/QPID-2236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2236: -- Component/s: C++ Build > cmake build fails to build cluster module. > -- > > Key: QPID-2236 > URL: https://issues.apache.org/jira/browse/QPID-2236 > Project: Qpid > Issue Type: Bug > Components: C++ Build >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Blocker > Fix For: 0.6 > > > On 12/02/2009 07:53 PM, Andrew Stitcher wrote: > > Cmake build is mostly fine - however the clustering module doesn't build > > due to a complication of recent versions of boost. And r886259 breaks > > building the clustering tests (due to missing the new > > tests/cluster.cmake from EXTRA_DIST) -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3105) Alternate-Exchange configuration not communicated between nodes in a cluster
[ https://issues.apache.org/jira/browse/QPID-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-3105: -- Component/s: C++ Clustering > Alternate-Exchange configuration not communicated between nodes in a cluster > > > Key: QPID-3105 > URL: https://issues.apache.org/jira/browse/QPID-3105 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Affects Versions: 0.9 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.9 > > > When an exchange is declared with an alternate-exchange, the > alternate-exchange is not communicated to new members joining the cluster. > See https://bugzilla.redhat.com/show_bug.cgi?id=681331 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-426) Java broker failing python tests
[ https://issues.apache.org/jira/browse/QPID-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-426: - Component/s: Java Broker > Java broker failing python tests > > > Key: QPID-426 > URL: https://issues.apache.org/jira/browse/QPID-426 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: M1 >Reporter: Alan Conway > Fix For: M2 > > > The java broker fails the tests in python/java_failing_0-8.txt > tests_0-8.exchange.RecommendedTypesRuleTests.testTopic > tests_0-8.exchange.RequiredInstancesRuleTests.testAmqTopic > Need to fix on M2 branch, update java_failing_0-8.txt fle and merge to trunk. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3329) Configure C++ client connections to replace url-addresses rather than merging new addresses with old
[ https://issues.apache.org/jira/browse/QPID-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-3329: -- Component/s: C++ Client > Configure C++ client connections to replace url-addresses rather than merging > new addresses with old > > > Key: QPID-3329 > URL: https://issues.apache.org/jira/browse/QPID-3329 > Project: Qpid > Issue Type: Improvement > Components: C++ Client >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.11 > > > Setting the "reconnect-urls" client option actually merges the new URLs with > the old. This patch allows that to be configured: > if "reconnect-urls-replace" is set to true then the old URLs are replaced > instead. This us useful in long-running failover tests that generate an > unlimited series of different broker addresses. The default is the old merge > behaviour as this is safer for a fixed-size cluster: in the event of a > partion you don't want the failover list to be replaced by a list containing > only the losing brokers, that would leave the client stranded. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4072) HA use backup messages in failover.
[ https://issues.apache.org/jira/browse/QPID-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4072: -- Component/s: C++ Clustering > HA use backup messages in failover. > --- > > Key: QPID-4072 > URL: https://issues.apache.org/jira/browse/QPID-4072 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.17 > > > When a backup fails over to a new primary, it already has many/most of the > messages it needs. > ReplicatingSubscription should sync. the primary and backup queues, and not > re-send messages that are already on the backup. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3198) Clustered broker should exit on unknown connection.
[ https://issues.apache.org/jira/browse/QPID-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-3198: -- Component/s: C++ Clustering > Clustered broker should exit on unknown connection. > --- > > Key: QPID-3198 > URL: https://issues.apache.org/jira/browse/QPID-3198 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.11 > > > A clustered broker that receives data for an unknown connection currently > logs a debug message and drops the data. > The broker should exit, as the existence of an unknown connection means it is > out of sync with respect to other brokers in the cluster. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4733) Fix cmake installation of init scripts
[ https://issues.apache.org/jira/browse/QPID-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4733: -- Component/s: C++ Build > Fix cmake installation of init scripts > -- > > Key: QPID-4733 > URL: https://issues.apache.org/jira/browse/QPID-4733 > Project: Qpid > Issue Type: Bug > Components: C++ Build >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.24 > > > The cmake build does not correctly substitute and install the init scripts > qpidd and qpidd-primary. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4176) HA Error handling
[ https://issues.apache.org/jira/browse/QPID-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4176: -- Component/s: C++ Clustering > HA Error handling > - > > Key: QPID-4176 > URL: https://issues.apache.org/jira/browse/QPID-4176 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Affects Versions: 0.17 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.19 > > > Fix error handling so that backup brokers shut down on replication errors. > Previously replication errors were being thrown to the primary, breaking the > replication > session. This would put the primary into an endless futile reconnect attempt. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7696) [Java Broker] Deletion of a temporary queue can crash the broker with certain ACLs
[
https://issues.apache.org/jira/browse/QPID-7696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-7696:
-
Attachment:
QPID-7696-remove-queue-bindings-on-queue-deletion-regardless-availability-unbind-acl-rule.diff
> [Java Broker] Deletion of a temporary queue can crash the broker with certain
> ACLs
> --
>
> Key: QPID-7696
> URL: https://issues.apache.org/jira/browse/QPID-7696
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.1.1
>Reporter: Lorenz Quack
> Fix For: qpid-java-6.1.2
>
> Attachments:
> QPID-7696-remove-queue-bindings-on-queue-deletion-regardless-availability-unbind-acl-rule.diff
>
>
> ACL:
> {noformat}
> ACL ALLOW-LOG testUser CREATE QUEUE temporary="true"
> ACL ALLOW-LOG testUser DELETE QUEUE temporary="true"
> ACL ALLOW-LOG testUser ACCESS ALL
> ACL ALLOW-LOG admin ALL ALL
> ACL DENY-LOG ALL ALL
> {noformat}
> client code:
> {code}
> /* create connection */
> Session session = connection.createSession(true,
> Session.SESSION_TRANSACTED);
> TemporaryQueue temporaryQueue = session.createTemporaryQueue();
> temporaryQueue.delete();
>/* cleanup */
> {code}
> This crashes the broker v6.1.1
> {noformat}
>
> #
> # Unhandled Exception java.security.AccessControlException: Permission DELETE
> is denied for : Binding 'TempQueuec64ba00d-9b7c-44f2-9217-80c954234ce4' on
> Queue 'TempQueuec64ba00d-9b7c-44f2-9217-80c954234ce4' Exchange 'amq.direct'
> in Thread IO-/127.0.0.1:53477
> #
> # Exiting
> #
>
> java.security.AccessControlException: Permission DELETE is denied for :
> Binding 'TempQueuec64ba00d-9b7c-44f2-9217-80c954234ce4' on Queue
> 'TempQueuec64ba00d-9b7c-44f2-9217-80c954234ce4' Exchange 'amq.direct'
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.authorise(AbstractConfiguredObject.java:2959)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.authorise(AbstractConfiguredObject.java:2891)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.authoriseSetAttributes(AbstractConfiguredObject.java:2970)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1659)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1629)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:625)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:240)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:312)
> 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:305)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Process finished with exit code 1
> {noformat}
> I have not tested with other versions of the broker, yet.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7695) [HA] Indefinite hang when new node joins existing group but existing node is unresponsive
[
https://issues.apache.org/jira/browse/QPID-7695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924670#comment-15924670
]
ASF subversion and git services commented on QPID-7695:
---
Commit 1786943 from [~k-wall] in branch 'java/branches/6.0.x'
[ https://svn.apache.org/r1786943 ]
QPID-7695: [HA] Prevent config thread hang if existing node is unresponsive.
Merged from 6.1.x branch with command:
svn merge -c 1786930 ^/qpid/java/branches/6.1.x
Correct null delta at rev. 1786933
> [HA] Indefinite hang when new node joins existing group but existing node is
> unresponsive
> -
>
> Key: QPID-7695
> URL: https://issues.apache.org/jira/browse/QPID-7695
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0.6, qpid-java-6.1.1, qpid-java-broker-7.0.0
>Reporter: Keith Wall
>Assignee: Keith Wall
> Fix For: qpid-java-6.0.7, qpid-java-6.1.2, qpid-java-broker-7.0.0
>
>
> When adding a new node to an existing group, internally Qpid uses
> com.sleepycat.je.rep.util.DbPing#DbPing() to establish initial contact with
> the node and perform some preliminary checks. If this node is somehow
> unresponsive, Qpid (the Broker's Confif Thread) hangs indefinitely and is
> unrecoverable. BDB JE 5.0.104 is in use.
> The Broker Config thread stack trace looks like this:
> {noformat}
> java.lang.Thread.State: RUNNABLE
> at sun.nio.ch.FileDispatcherImpl.read0(FileDispatcherImpl.java:-1)
> at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
> at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
> at sun.nio.ch.IOUtil.read(IOUtil.java:197)
> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
> - locked <0x168d> (a java.lang.Object)
> at
> com.sleepycat.je.rep.utilint.ServiceDispatcher.doServiceHandshake(ServiceDispatcher.java:325)
> at com.sleepycat.je.rep.util.DbPing.getNodeState(DbPing.java:194)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.getRemoteNodeState(ReplicatedEnvironmentFacade.java:1807)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.connectToHelperNodeAndCheckPermittedHosts(ReplicatedEnvironmentFacade.java:1846)
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.getPermittedNodesFromHelper(BDBHAVirtualHostNodeImpl.java:566)
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.validateOnCreate(BDBHAVirtualHostNodeImpl.java:546)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:878)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:865)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:636)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:629)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:240)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submitWrappedTask(TaskExecutorImpl.java:157)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submit(TaskExecutorImpl.java:145)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.doOnConfigThread(AbstractConfiguredObject.java:628)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.createAsync(AbstractConfiguredObject.java:864)
> at
> org.apache.qpid.server.model.AbstractConfiguredObjectTypeFactory.createAsync(AbstractConfiguredObjectTypeFactory.java:75)
> at
> org.apache.qpid.server.model.ConfiguredObjectFactoryImpl.createAsync(ConfiguredObjectFactoryImpl.java:145)
> at
> org.apache.qpid.server.model.BrokerImpl.createVirtualHostNodeAsync(BrokerImpl.java:605)
> at
> org.apache.qpid.server.model.BrokerImpl.addChildAsync(BrokerImpl.java:660)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2094)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2089)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:636)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:629)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:240)
> at
> org.ap
[jira] [Commented] (QPID-7685) [Java Broker, BDB] AsyncRecovery and Queue#enqueue can contend for a BDB Lock potentially bringing down the broker
[
https://issues.apache.org/jira/browse/QPID-7685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924661#comment-15924661
]
ASF subversion and git services commented on QPID-7685:
---
Commit 1786942 from [~k-wall] in branch 'java/branches/6.0.x'
[ https://svn.apache.org/r1786942 ]
QPID-7685: QPID-7701: [BDB] Remove possibility of a lock timeout during message
instance recovery by reading uncommitted data.
Merged from 6.1.x branch with command:
svn merge -c 1786941 ^/qpid/java/branches/6.1.x
> [Java Broker, BDB] AsyncRecovery and Queue#enqueue can contend for a BDB Lock
> potentially bringing down the broker
> --
>
> Key: QPID-7685
> URL: https://issues.apache.org/jira/browse/QPID-7685
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: 0.32, qpid-java-6.0.6, qpid-java-6.1.1,
> qpid-java-broker-7.0.0
>Reporter: Lorenz Quack
>Assignee: Keith Wall
>Priority: Critical
> Fix For: qpid-java-6.0.7, qpid-java-6.1.2, qpid-java-broker-7.0.0
>
>
> This is the scenario:
> BDB message store.
> AsyncRecovery completes recovery of queue Q1. Queue Q2 is still being
> recovered.
> An transacted application sends a message to Q1 but does not commit the
> transaction. This ends up creating an entry in the {{DeliveryDb}} through the
> following call chain:
> > AMQChannel#deliverCurrentMessageIfComplete
> --> AbstractExchange#send
> > LocalTransaction#enqueue(List, EnqueueableMessage,
> ServerTransaction.Action)
> --> AbstractBDBMessageStore.BDBTransaction#enqueueMessage
> > AbstractBDBMessageStore#enqueueMessage
> --> getDeliveryDb().put
> The transaction will hold a write lock on this new DB entry until the
> transaction is committed.
> If it now happens that this entry appears immediately after the last entry of
> Q2 in the database the recovery code will try to read that entry in
> {{AbstractBDBMessageStore#visitMessageInstances(TransactionLogResource,
> MessageInstanceHandler)}}:
> {{cursor.getNext(key, value, LockMode.DEFAULT)}}
> Acquisition of the read lock will timeout after {{je.lock.timeout}} (default:
> 500ms) and after exhaustion of the retries (hard coded to 5) a
> {{StoreException}} will be thrown bringing down the broker with the following
> stack trace (from a broker derived from 0.32):
> {noformat}
>
> #
> # Unhandled Exception
> com.google.common.util.concurrent.UncheckedExecutionException:
> org.apache.qpid.server.store.StoreException: Cannot visit messages in Thread
> pool-2-thread-1
> #
> # Exiting
> #
>
> com.google.common.util.concurrent.UncheckedExecutionException:
> org.apache.qpid.server.store.StoreException: Cannot visit messages
> at
> com.google.common.util.concurrent.Futures.wrapAndThrowUnchecked(Futures.java:1358)
> at
> com.google.common.util.concurrent.Futures.getUnchecked(Futures.java:1344)
> at
> org.apache.qpid.server.virtualhost.AbstractVirtualHost$4.run(AbstractVirtualHost.java:1619)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.qpid.server.store.StoreException: Cannot visit messages
> at
> org.apache.qpid.server.store.berkeleydb.StandardEnvironmentFacade.handleDatabaseException(StandardEnvironmentFacade.java:369)
> at
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.sleepOrThrowOnLockConflict(AbstractBDBMessageStore.java:665)
> at
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.visitMessageInstances(AbstractBDBMessageStore.java:233)
> at
> org.apache.qpid.server.virtualhost.AsynchronousMessageStoreRecoverer$AsynchronousRecoverer.recoverQueue(AsynchronousMessageStoreRecoverer.java:163)
> at
> org.apache.qpid.server.virtualhost.AsynchronousMessageStoreRecoverer$AsynchronousRecoverer.access$900(AsynchronousMessageStoreRecoverer.java:86)
> at
> org.apache.qpid.server.virtualhost.AsynchronousMessageStoreRecoverer$AsynchronousRecoverer$QueueRecov
[jira] [Commented] (QPID-7701) [BDB HA] Cursor#getNext API misuse
[
https://issues.apache.org/jira/browse/QPID-7701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924662#comment-15924662
]
ASF subversion and git services commented on QPID-7701:
---
Commit 1786942 from [~k-wall] in branch 'java/branches/6.0.x'
[ https://svn.apache.org/r1786942 ]
QPID-7685: QPID-7701: [BDB] Remove possibility of a lock timeout during message
instance recovery by reading uncommitted data.
Merged from 6.1.x branch with command:
svn merge -c 1786941 ^/qpid/java/branches/6.1.x
> [BDB HA] Cursor#getNext API misuse
> --
>
> Key: QPID-7701
> URL: https://issues.apache.org/jira/browse/QPID-7701
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Reporter: Keith Wall
>Assignee: Keith Wall
> Fix For: 0.30, 0.32, qpid-java-6.0, qpid-java-6.1
>
>
> The documentation for methods {{com.sleepycat.je.Cursor#getNext}} and
> {{com.sleepycat.je.Cursor#getSearchKeyRange}} notes the following:
> {quote}
> In a replicated environment, an explicit transaction must have been
> specified when opening the cursor, unless read-uncommitted isolation is
> specified via the {{CursorConfig}} or {{LockMode}}
> parameter.
> {quote}
> Currently methods such as
> {{org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.BDBMessageStoreReader#visitDistributedTransactions}}
> do not do this.
> The documentation does not state the implications of not following this
> advice.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7685) [Java Broker, BDB] AsyncRecovery and Queue#enqueue can contend for a BDB Lock potentially bringing down the broker
[
https://issues.apache.org/jira/browse/QPID-7685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924653#comment-15924653
]
ASF subversion and git services commented on QPID-7685:
---
Commit 1786941 from [~k-wall] in branch 'java/branches/6.1.x'
[ https://svn.apache.org/r1786941 ]
QPID-7685: QPID-7701: [BDB] Remove possibility of a lock timeout during message
instance recovery by reading uncommitted data.
Merged from trunk with command:
svn merge -c 1786914 ^/qpid/java/trunk
> [Java Broker, BDB] AsyncRecovery and Queue#enqueue can contend for a BDB Lock
> potentially bringing down the broker
> --
>
> Key: QPID-7685
> URL: https://issues.apache.org/jira/browse/QPID-7685
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: 0.32, qpid-java-6.0.6, qpid-java-6.1.1,
> qpid-java-broker-7.0.0
>Reporter: Lorenz Quack
>Assignee: Keith Wall
>Priority: Critical
> Fix For: qpid-java-6.0.7, qpid-java-6.1.2, qpid-java-broker-7.0.0
>
>
> This is the scenario:
> BDB message store.
> AsyncRecovery completes recovery of queue Q1. Queue Q2 is still being
> recovered.
> An transacted application sends a message to Q1 but does not commit the
> transaction. This ends up creating an entry in the {{DeliveryDb}} through the
> following call chain:
> > AMQChannel#deliverCurrentMessageIfComplete
> --> AbstractExchange#send
> > LocalTransaction#enqueue(List, EnqueueableMessage,
> ServerTransaction.Action)
> --> AbstractBDBMessageStore.BDBTransaction#enqueueMessage
> > AbstractBDBMessageStore#enqueueMessage
> --> getDeliveryDb().put
> The transaction will hold a write lock on this new DB entry until the
> transaction is committed.
> If it now happens that this entry appears immediately after the last entry of
> Q2 in the database the recovery code will try to read that entry in
> {{AbstractBDBMessageStore#visitMessageInstances(TransactionLogResource,
> MessageInstanceHandler)}}:
> {{cursor.getNext(key, value, LockMode.DEFAULT)}}
> Acquisition of the read lock will timeout after {{je.lock.timeout}} (default:
> 500ms) and after exhaustion of the retries (hard coded to 5) a
> {{StoreException}} will be thrown bringing down the broker with the following
> stack trace (from a broker derived from 0.32):
> {noformat}
>
> #
> # Unhandled Exception
> com.google.common.util.concurrent.UncheckedExecutionException:
> org.apache.qpid.server.store.StoreException: Cannot visit messages in Thread
> pool-2-thread-1
> #
> # Exiting
> #
>
> com.google.common.util.concurrent.UncheckedExecutionException:
> org.apache.qpid.server.store.StoreException: Cannot visit messages
> at
> com.google.common.util.concurrent.Futures.wrapAndThrowUnchecked(Futures.java:1358)
> at
> com.google.common.util.concurrent.Futures.getUnchecked(Futures.java:1344)
> at
> org.apache.qpid.server.virtualhost.AbstractVirtualHost$4.run(AbstractVirtualHost.java:1619)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.qpid.server.store.StoreException: Cannot visit messages
> at
> org.apache.qpid.server.store.berkeleydb.StandardEnvironmentFacade.handleDatabaseException(StandardEnvironmentFacade.java:369)
> at
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.sleepOrThrowOnLockConflict(AbstractBDBMessageStore.java:665)
> at
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.visitMessageInstances(AbstractBDBMessageStore.java:233)
> at
> org.apache.qpid.server.virtualhost.AsynchronousMessageStoreRecoverer$AsynchronousRecoverer.recoverQueue(AsynchronousMessageStoreRecoverer.java:163)
> at
> org.apache.qpid.server.virtualhost.AsynchronousMessageStoreRecoverer$AsynchronousRecoverer.access$900(AsynchronousMessageStoreRecoverer.java:86)
> at
> org.apache.qpid.server.virtualhost.AsynchronousMessageStoreRecoverer$AsynchronousRecoverer$QueueRecoveringTask.run(A
[jira] [Commented] (QPID-7701) [BDB HA] Cursor#getNext API misuse
[
https://issues.apache.org/jira/browse/QPID-7701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924654#comment-15924654
]
ASF subversion and git services commented on QPID-7701:
---
Commit 1786941 from [~k-wall] in branch 'java/branches/6.1.x'
[ https://svn.apache.org/r1786941 ]
QPID-7685: QPID-7701: [BDB] Remove possibility of a lock timeout during message
instance recovery by reading uncommitted data.
Merged from trunk with command:
svn merge -c 1786914 ^/qpid/java/trunk
> [BDB HA] Cursor#getNext API misuse
> --
>
> Key: QPID-7701
> URL: https://issues.apache.org/jira/browse/QPID-7701
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Reporter: Keith Wall
>Assignee: Keith Wall
> Fix For: 0.30, 0.32, qpid-java-6.0, qpid-java-6.1
>
>
> The documentation for methods {{com.sleepycat.je.Cursor#getNext}} and
> {{com.sleepycat.je.Cursor#getSearchKeyRange}} notes the following:
> {quote}
> In a replicated environment, an explicit transaction must have been
> specified when opening the cursor, unless read-uncommitted isolation is
> specified via the {{CursorConfig}} or {{LockMode}}
> parameter.
> {quote}
> Currently methods such as
> {{org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.BDBMessageStoreReader#visitDistributedTransactions}}
> do not do this.
> The documentation does not state the implications of not following this
> advice.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7684) [Java Broker, BDB] Close Cursor when LockConflictException is thrown
[
https://issues.apache.org/jira/browse/QPID-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7684:
-
Status: Reviewable (was: In Progress)
> [Java Broker, BDB] Close Cursor when LockConflictException is thrown
>
>
> Key: QPID-7684
> URL: https://issues.apache.org/jira/browse/QPID-7684
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: 0.32, qpid-java-6.0.6, qpid-java-6.1.1,
> qpid-java-broker-7.0.0
>Reporter: Lorenz Quack
>Assignee: Keith Wall
> Fix For: qpid-java-6.0.7, qpid-java-6.1.2, qpid-java-broker-7.0.0
>
>
> Currently, when a LockConflictException is thrown we retry the operation.
> However the retry logic does not adhere to the rules outlined in the BDB JE
> documentation, specifically we do not close and recreate the Cursor.
> To quote the
> [documentation|https://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/LockConflictException.html]:
> {quote}If a lock conflict occurs during a transaction, the transaction may be
> retried by performing the following steps. \[...\]:
> # Close all cursors opened under the transaction.
> # Abort the transaction.
> # Begin a new transaction and repeat the operations.
> {quote}
> The impact of not doing this is unclear.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7684) [Java Broker, BDB] Close Cursor when LockConflictException is thrown
[
https://issues.apache.org/jira/browse/QPID-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924640#comment-15924640
]
ASF subversion and git services commented on QPID-7684:
---
Commit 1786939 from [~k-wall] in branch 'java/branches/6.0.x'
[ https://svn.apache.org/r1786939 ]
QPID-7684: [Java Broker, BDB] Adhere to recommended practice for retrying after
a LockConflictException.
Merged from 6.1.x branch with command:
svn merge -c 1786935 ^/qpid/java/branches/6.1.x
> [Java Broker, BDB] Close Cursor when LockConflictException is thrown
>
>
> Key: QPID-7684
> URL: https://issues.apache.org/jira/browse/QPID-7684
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: 0.32, qpid-java-6.0.6, qpid-java-6.1.1,
> qpid-java-broker-7.0.0
>Reporter: Lorenz Quack
> Fix For: qpid-java-6.0.7, qpid-java-6.1.2, qpid-java-broker-7.0.0
>
>
> Currently, when a LockConflictException is thrown we retry the operation.
> However the retry logic does not adhere to the rules outlined in the BDB JE
> documentation, specifically we do not close and recreate the Cursor.
> To quote the
> [documentation|https://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/LockConflictException.html]:
> {quote}If a lock conflict occurs during a transaction, the transaction may be
> retried by performing the following steps. \[...\]:
> # Close all cursors opened under the transaction.
> # Abort the transaction.
> # Begin a new transaction and repeat the operations.
> {quote}
> The impact of not doing this is unclear.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-7684) [Java Broker, BDB] Close Cursor when LockConflictException is thrown
[
https://issues.apache.org/jira/browse/QPID-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall reassigned QPID-7684:
Assignee: Keith Wall
> [Java Broker, BDB] Close Cursor when LockConflictException is thrown
>
>
> Key: QPID-7684
> URL: https://issues.apache.org/jira/browse/QPID-7684
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: 0.32, qpid-java-6.0.6, qpid-java-6.1.1,
> qpid-java-broker-7.0.0
>Reporter: Lorenz Quack
>Assignee: Keith Wall
> Fix For: qpid-java-6.0.7, qpid-java-6.1.2, qpid-java-broker-7.0.0
>
>
> Currently, when a LockConflictException is thrown we retry the operation.
> However the retry logic does not adhere to the rules outlined in the BDB JE
> documentation, specifically we do not close and recreate the Cursor.
> To quote the
> [documentation|https://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/LockConflictException.html]:
> {quote}If a lock conflict occurs during a transaction, the transaction may be
> retried by performing the following steps. \[...\]:
> # Close all cursors opened under the transaction.
> # Abort the transaction.
> # Begin a new transaction and repeat the operations.
> {quote}
> The impact of not doing this is unclear.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7435) Avoid BDB fetching dummy single byte database entries during message instance recovery
[ https://issues.apache.org/jira/browse/QPID-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7435: - Fix Version/s: qpid-java-6.0.7 > Avoid BDB fetching dummy single byte database entries during message instance > recovery > -- > > Key: QPID-7435 > URL: https://issues.apache.org/jira/browse/QPID-7435 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: qpid-java-6.0.7, qpid-java-6.1 > > > We represent message instances in BDB as a tuple comprising a key (formed of > queue id and message id) and a dummy record (formed of 1 byte). The dummy > record serves no purpose other than to fulfil the contract with JE's > Database#put() which cannot accept a null entry value. > The JE API has a mechanism to instruct a cursor operations to retrieve only > the key values. We can exploit this feature when recovering message > instances to suppress the retrieval of the dummy entry. > On my box, this improves (synchronous) recovery time for a store containing 4 > queues with 2,000,000 messages from about 1min to about 30seconds. This > should benefit any user who uses BDB and has a large store. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7435) Avoid BDB fetching dummy single byte database entries during message instance recovery
[ https://issues.apache.org/jira/browse/QPID-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924632#comment-15924632 ] ASF subversion and git services commented on QPID-7435: --- Commit 1786938 from [~k-wall] in branch 'java/branches/6.0.x' [ https://svn.apache.org/r1786938 ] QPID-7435: [Java Broker] Avoid the retrieval of the dummy single byte entry when traversing message instance cursors. svn merge -c 1762070 ^/qpid/java/branches/6.1.x > Avoid BDB fetching dummy single byte database entries during message instance > recovery > -- > > Key: QPID-7435 > URL: https://issues.apache.org/jira/browse/QPID-7435 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: qpid-java-6.0.7, qpid-java-6.1 > > > We represent message instances in BDB as a tuple comprising a key (formed of > queue id and message id) and a dummy record (formed of 1 byte). The dummy > record serves no purpose other than to fulfil the contract with JE's > Database#put() which cannot accept a null entry value. > The JE API has a mechanism to instruct a cursor operations to retrieve only > the key values. We can exploit this feature when recovering message > instances to suppress the retrieval of the dummy entry. > On my box, this improves (synchronous) recovery time for a store containing 4 > queues with 2,000,000 messages from about 1min to about 30seconds. This > should benefit any user who uses BDB and has a large store. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-7435) Avoid BDB fetching dummy single byte database entries during message instance recovery
[ https://issues.apache.org/jira/browse/QPID-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall closed QPID-7435. Resolution: Fixed > Avoid BDB fetching dummy single byte database entries during message instance > recovery > -- > > Key: QPID-7435 > URL: https://issues.apache.org/jira/browse/QPID-7435 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: qpid-java-6.0.7, qpid-java-6.1 > > > We represent message instances in BDB as a tuple comprising a key (formed of > queue id and message id) and a dummy record (formed of 1 byte). The dummy > record serves no purpose other than to fulfil the contract with JE's > Database#put() which cannot accept a null entry value. > The JE API has a mechanism to instruct a cursor operations to retrieve only > the key values. We can exploit this feature when recovering message > instances to suppress the retrieval of the dummy entry. > On my box, this improves (synchronous) recovery time for a store containing 4 > queues with 2,000,000 messages from about 1min to about 30seconds. This > should benefit any user who uses BDB and has a large store. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
