[jira] [Commented] (QPID-3677) Asserting does not work correctly from JMS

[ https://issues.apache.org/jira/browse/QPID-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427186#comment-13427186 ] Gordon Sim commented on QPID-3677: -- Does your address have an assertion in it? Does it

[jira] [Created] (QPID-4182) Define a reasonable default for the 'minimumAlertRepeatGap'

Alex Rudyy created QPID-4182: Summary: Define a reasonable default for the 'minimumAlertRepeatGap' Key: QPID-4182 URL: https://issues.apache.org/jira/browse/QPID-4182 Project: Qpid Issue Type:

[jira] [Updated] (QPID-4171) persistent messages from a non-transactional session can be enqueued out of order

[ https://issues.apache.org/jira/browse/QPID-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4171: - Affects Version/s: (was: 0.19) (was: 0.18) Fix Version/s:

[jira] [Resolved] (QPID-4091) [Java Broker] Incorrect handling of timeout values on DtxSetTimeout

[ https://issues.apache.org/jira/browse/QPID-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4091. -- Resolution: Fixed Assignee: Robbie Gemmell (was: Rob Godfrey) Rob made some changes,

[jira] [Updated] (QPID-4182) Define a reasonable default for the 'minimumAlertRepeatGap'

[ https://issues.apache.org/jira/browse/QPID-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-4182: - Attachment: 0001-QPID-4182-Set-the-default-minimumAlertRepeatGap-valu.patch Attached a patch resolving

[jira] [Assigned] (QPID-4182) Define a reasonable default for the 'minimumAlertRepeatGap'

[ https://issues.apache.org/jira/browse/QPID-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-4182: Assignee: Philip Harvey (was: Alex Rudyy) Phil, Could you please review the patch?

[jira] [Updated] (QPID-4182) Define a reasonable default for the 'minimumAlertRepeatGap'

[ https://issues.apache.org/jira/browse/QPID-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-4182: - Status: Ready To Review (was: In Progress) Define a reasonable default for the

[jira] [Updated] (QPID-4174) QMF events for (dis)connecting a client to have few more parameters

[ https://issues.apache.org/jira/browse/QPID-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec updated QPID-4174: Attachment: (was: 0001_QPID-4174_AllowTCPconn-info.patch) QMF events for (dis)connecting a

[jira] [Updated] (QPID-4174) QMF events for (dis)connecting a client to have few more parameters

[ https://issues.apache.org/jira/browse/QPID-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec updated QPID-4174: Component/s: (was: Java Client) Qpid Managment Framework Description: I

[jira] [Commented] (QPID-4174) QMF events for (dis)connecting a client to have few more parameters

[ https://issues.apache.org/jira/browse/QPID-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427237#comment-13427237 ] Pavel Moravec commented on QPID-4174: - I changed the JIRA description as per my comment

[jira] [Updated] (QPID-4174) QMF events for (dis)connecting a client to have few more parameters

[ https://issues.apache.org/jira/browse/QPID-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec updated QPID-4174: Attachment: 0001-connect-event-more-QMF-parameters Except for changing management-schema.xml and

[jira] [Created] (QPID-4183) [Java Broker] AMQP 1.0 implementation broken by management adaptation layer

Rob Godfrey created QPID-4183: - Summary: [Java Broker] AMQP 1.0 implementation broken by management adaptation layer Key: QPID-4183 URL: https://issues.apache.org/jira/browse/QPID-4183 Project: Qpid

[jira] [Updated] (QPID-4183) [Java Broker] AMQP 1.0 implementation broken by management adaptation layer

[ https://issues.apache.org/jira/browse/QPID-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-4183: -- Status: Ready To Review (was: In Progress) [Java Broker] AMQP 1.0 implementation broken by

Re: Deadlock

Well this is a bug in the libraries, I've been looking at the code and here is (probably obvious for you :) ) problem: 1. Thread 1 acquires the FailoverMutex 2. Thread 2 acquires the MessageDeliveryLock 3. Thread 1 tries to acquire the MessageDeliveryLock 4. Thread 2 tries to acquire the

[jira] [Commented] (QPID-3216) Deadlock between _lock (in AMQSession#DisptcherThread) and _messageDeliveryLock (in AMQSession.java)

[ https://issues.apache.org/jira/browse/QPID-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427244#comment-13427244 ] rabii eugen commented on QPID-3216: --- So... what is the solution for this problem? We are

[jira] [Resolved] (QPID-4183) [Java Broker] AMQP 1.0 implementation broken by management adaptation layer

[ https://issues.apache.org/jira/browse/QPID-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4183. -- Resolution: Fixed Fix Version/s: 0.19 Changes seem reasonable (obviously there are

[jira] [Updated] (QPID-4182) Define a reasonable default for the 'minimumAlertRepeatGap'

[ https://issues.apache.org/jira/browse/QPID-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-4182: - Attachment: (was: 0001-QPID-4182-Set-the-default-minimumAlertRepeatGap-valu.patch) Define a

[jira] [Updated] (QPID-4182) Define a reasonable default for the 'minimumAlertRepeatGap'

[ https://issues.apache.org/jira/browse/QPID-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-4182: - Attachment: 0001-QPID-4182-Set-the-default-minimumAlertRepeatGap-valu.patch Define a reasonable

[jira] [Resolved] (QPID-4182) Define a reasonable default for the 'minimumAlertRepeatGap'

[ https://issues.apache.org/jira/browse/QPID-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Harvey resolved QPID-4182. - Resolution: Fixed Assignee: Robbie Gemmell (was: Philip Harvey) Reviewed and tested -

[jira] [Assigned] (QPID-4172) [Java Broker] Virtualhost tasks should reset their thread name upon completion

[ https://issues.apache.org/jira/browse/QPID-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Harvey reassigned QPID-4172: --- Assignee: Philip Harvey [Java Broker] Virtualhost tasks should reset their thread name

[jira] [Updated] (QPID-4172) [Java Broker] Virtualhost tasks should reset their thread name upon completion

[ https://issues.apache.org/jira/browse/QPID-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Harvey updated QPID-4172: Attachment: 0001-QPID-4172-HouseKeepingTask-now-reverts-thread-name-b.patch attached patch -

[jira] [Updated] (QPID-4172) [Java Broker] Virtualhost tasks should reset their thread name upon completion

[ https://issues.apache.org/jira/browse/QPID-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Harvey updated QPID-4172: Status: Ready To Review (was: In Progress) [Java Broker] Virtualhost tasks should reset their

[jira] [Assigned] (QPID-4172) [Java Broker] Virtualhost tasks should reset their thread name upon completion

[ https://issues.apache.org/jira/browse/QPID-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Harvey reassigned QPID-4172: --- Assignee: Alex Rudyy (was: Philip Harvey) please review patch [Java

[jira] [Assigned] (QPID-4172) [Java Broker] Virtualhost tasks should reset their thread name upon completion

[ https://issues.apache.org/jira/browse/QPID-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-4172: Assignee: Robbie Gemmell (was: Alex Rudyy) Reviewed with no comments. Robbie, Could you please

[jira] [Assigned] (QPID-4173) [Java Broker] disable the subscription state operational logging by default

[ https://issues.apache.org/jira/browse/QPID-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Harvey reassigned QPID-4173: --- Assignee: Philip Harvey [Java Broker] disable the subscription state operational logging

[jira] [Assigned] (QPID-4174) QMF events for (dis)connecting a client to have few more parameters

[ https://issues.apache.org/jira/browse/QPID-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned QPID-4174: -- Assignee: Ted Ross QMF events for (dis)connecting a client to have few more parameters

Re: Request for inclusion in 0.18

Another request for inclusion into 0.18: QPID-4183 This fixes a problem whereby the AMQP 1.0 support in the Java broker was inadvertently broken by some of the management work. The changes to the broker are isolated to the AMQP 1.0 support layer and have been reviewed by Robbie. Cheers, Rob

[jira] [Comment Edited] (QPID-4173) [Java Broker] disable the subscription state operational logging by default

[ https://issues.apache.org/jira/browse/QPID-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427338#comment-13427338 ] Alex Rudyy edited comment on QPID-4173 at 8/2/12 2:12 PM: --

[jira] [Updated] (QPID-4173) [Java Broker] disable the subscription state operational logging by default

[ https://issues.apache.org/jira/browse/QPID-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-4173: - Attachment: 0001-QPID-4173-Switch-off-subscription.state-logger-to-re.patch Attached a patch resolving

[jira] [Updated] (QPID-4173) [Java Broker] disable the subscription state operational logging by default

[ https://issues.apache.org/jira/browse/QPID-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-4173: - Status: Ready To Review (was: In Progress) [Java Broker] disable the subscription state operational

[jira] [Assigned] (QPID-4173) [Java Broker] disable the subscription state operational logging by default

[ https://issues.apache.org/jira/browse/QPID-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Harvey reassigned QPID-4173: --- Assignee: Robbie Gemmell (was: Philip Harvey) Reviewed and tested by me. Robbie - please can

[jira] [Commented] (QPID-4183) [Java Broker] AMQP 1.0 implementation broken by management adaptation layer

[ https://issues.apache.org/jira/browse/QPID-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427362#comment-13427362 ] Justin Ross commented on QPID-4183: ---

Re: Review Request: patches for mingw

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6302/#review9755 --- Ship it! This looks good. The only serious comment I have applies

[jira] [Commented] (QPID-4182) Define a reasonable default for the 'minimumAlertRepeatGap'

[ https://issues.apache.org/jira/browse/QPID-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427371#comment-13427371 ] Robbie Gemmell commented on QPID-4182: -- Patch applied. Define a

[jira] [Commented] (QPID-4183) [Java Broker] AMQP 1.0 implementation broken by management adaptation layer

[ https://issues.apache.org/jira/browse/QPID-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427376#comment-13427376 ] Rob Godfrey commented on QPID-4183: --- Merged from trunk to 0.18 [Java

[jira] [Updated] (QPID-4183) [Java Broker] AMQP 1.0 implementation broken by management adaptation layer

[ https://issues.apache.org/jira/browse/QPID-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-4183: -- Fix Version/s: 0.18 [Java Broker] AMQP 1.0 implementation broken by management adaptation layer

[jira] [Resolved] (QPID-4172) [Java Broker] Virtualhost tasks should reset their thread name upon completion

[ https://issues.apache.org/jira/browse/QPID-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4172. -- Resolution: Fixed Patch applied. [Java Broker] Virtualhost tasks should reset

[jira] [Resolved] (QPID-4173) [Java Broker] disable the subscription state operational logging by default

[ https://issues.apache.org/jira/browse/QPID-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4173. -- Resolution: Fixed Patch applied. [Java Broker] disable the subscription state

[jira] [Commented] (QPID-4100) New HA federation links do not fail over

[ https://issues.apache.org/jira/browse/QPID-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427405#comment-13427405 ] Alan Conway commented on QPID-4100: --- Proposal to fix the bug: 1. For the security issue:

[jira] [Created] (QPID-4184) queue alert notifications are not being logged by default

Robbie Gemmell created QPID-4184: Summary: queue alert notifications are not being logged by default Key: QPID-4184 URL: https://issues.apache.org/jira/browse/QPID-4184 Project: Qpid Issue

Re: Review Request: patches for mingw

On Aug. 2, 2012, 12:04 a.m., Andrew Stitcher wrote: http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/CMakeLists.txt, line 39 https://reviews.apache.org/r/6302/diff/1/?file=132723#file132723line39 Perhaps it makes sense to move src/driver.c into src/sys/posix/driver.c?

[jira] [Updated] (QPID-4184) queue alert notifications are not being logged by default

[ https://issues.apache.org/jira/browse/QPID-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4184: - Status: Ready To Review (was: In Progress) queue alert notifications are not being logged

[jira] [Assigned] (QPID-4184) queue alert notifications are not being logged by default

[ https://issues.apache.org/jira/browse/QPID-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-4184: Assignee: Robbie Gemmell queue alert notifications are not being logged by default

[jira] [Assigned] (QPID-4184) queue alert notifications are not being logged by default

[ https://issues.apache.org/jira/browse/QPID-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-4184: Assignee: Alex Rudyy (was: Robbie Gemmell) Alex, can you review this change please?

[jira] [Resolved] (QPID-4184) queue alert notifications are not being logged by default

[ https://issues.apache.org/jira/browse/QPID-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-4184. -- Resolution: Fixed Reviewed with no comments queue alert notifications are not being

Yet more requests for inclusion in 0.18

Hi Justin, I would like to request that the following JIRAs/commits be considered for inclusion in 0.18: https://issues.apache.org/jira/browse/QPID-4184 http://svn.apache.org/viewvc?view=revisionrevision=1368597 This changes the broker log4j config to turn queue threshold notifications back on,

Re: Review Request: patches for mingw

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6302/#review9775 ---

Re: Review Request: qpidd refactor

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/5833/ --- (Updated Aug. 2, 2012, 7:19 p.m.) Review request for qpid, Alan Conway and

Re: Review Request: patches for mingw

On Aug. 2, 2012, 12:04 a.m., Andrew Stitcher wrote: http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/include/proton/types.h, line 40 https://reviews.apache.org/r/6302/diff/1/?file=132727#file132727line40 I think it might be better to keep pn_socket_t out of a header

What libraries/versions for proton?

I was building proton-c and the build fails in messenger.c, trying to include uuid/uuid.h. There's a uuid library for C, but it defines different types than proton is expecting. Can anyone tell me which uuid library is expected? It's looking for a *system* library for uuid. -- Joseph B.

Re: What libraries/versions for proton?

On Thu, 2012-08-02 at 15:55 -0400, Joseph Ottinger wrote: I was building proton-c and the build fails in messenger.c, trying to include uuid/uuid.h. There's a uuid library for C, but it defines different types than proton is expecting. Can anyone tell me which uuid library is expected? It's

[jira] [Resolved] (QPID-2367) Early Initialization of File Descriptors Conflicts With Daemon Best Practices

[ https://issues.apache.org/jira/browse/QPID-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved QPID-2367. --- Resolution: Fixed Fix Version/s: 0.19 Early Initialization of File Descriptors

[jira] [Commented] (QPID-3677) Asserting does not work correctly from JMS

[ https://issues.apache.org/jira/browse/QPID-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427578#comment-13427578 ] Michael Chrostowski commented on QPID-3677: --- Gordon, I think you're right and

Re: Review Request: qpidd refactor

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/5833/ --- (Updated Aug. 2, 2012, 8:25 p.m.) Review request for qpid, Alan Conway and

Re: What libraries/versions for proton?

It's Fedora 17, with a fairly clean install at that. Uuid and uuid-develop, plus libuuid, if memory serves, so as far as I can tell it should be pretty normal. On Thursday, August 2, 2012, Andrew Stitcher astitc...@redhat.com wrote: On Thu, 2012-08-02 at 15:55 -0400, Joseph Ottinger wrote: I

Re: What libraries/versions for proton?

On Thu, Aug 02, 2012 at 04:48:42PM -0400, Joseph Ottinger wrote: It's Fedora 17, with a fairly clean install at that. Uuid and uuid-develop, plus libuuid, if memory serves, so as far as I can tell it should be pretty normal. You need to have libuuid-devel, which provides the headers needed

Re: What libraries/versions for proton?

On Thu, Aug 02, 2012 at 04:48:42PM -0400, Joseph Ottinger wrote: It's Fedora 17, with a fairly clean install at that. Uuid and uuid-develop, plus libuuid, if memory serves, so as far as I can tell it should be pretty normal. I should also mention (at least on Fedora systems) a way to find

Re: Review Request: qpidd refactor

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/5833/ --- (Updated Aug. 2, 2012, 9:17 p.m.) Review request for qpid, Alan Conway and

[jira] [Updated] (QPID-4178) qpidd refactor

[ https://issues.apache.org/jira/browse/QPID-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated QPID-4178: - Attachment: refactor_store_impact.patch Slight tweak to previous patch, avoiding unintentional commenting

Address: Name cannot be null

I've written the initial Perl language bindings on top of what Swig gives us in Qpid. I'm now porting the examples in cpp/bindings/qpid/examples/perl over to use the newer code but am hitting this weird problem. (code can be found here [1]) In the client/server examples, things start up nicely:

0.18 release update - RC2 is out

Hi, everyone. I've produced RC2 at revision 1368514. Get it here: http://people.apache.org/~jross/qpid-0.18-rc2/ I'm going to be away on vacation until the 13th of August. If no changes are requested before then, I'll propose RC2 (after I've signed it) for our release vote when I return.