[jira] [Updated] (DISPATCH-616) Arithmetic operations not allowed on void * pointer
[ https://issues.apache.org/jira/browse/DISPATCH-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adel Boutros updated DISPATCH-616: -- Description: arithmetic on a void* is illegal in both C and C++: http://stackoverflow.com/questions/3523145/pointer-arithmetic-for-void-pointer-in-c https://gcc.gnu.org/onlinedocs/gcc-4.8.0/gcc/Pointer-Arith.html > Arithmetic operations not allowed on void * pointer > --- > > Key: DISPATCH-616 > URL: https://issues.apache.org/jira/browse/DISPATCH-616 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros > Attachments: > 0006-Arithmetic-operations-not-allowed-on-void-pointer.patch > > > arithmetic on a void* is illegal in both C and C++: > > http://stackoverflow.com/questions/3523145/pointer-arithmetic-for-void-pointer-in-c > https://gcc.gnu.org/onlinedocs/gcc-4.8.0/gcc/Pointer-Arith.html -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-615) SunStudio doesn't convert pointers to bool correctly
[ https://issues.apache.org/jira/browse/DISPATCH-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adel Boutros updated DISPATCH-615: -- Description: improper pointer/integer combination: op "=" (PyObject * to bool) > SunStudio doesn't convert pointers to bool correctly > > > Key: DISPATCH-615 > URL: https://issues.apache.org/jira/browse/DISPATCH-615 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros > Attachments: > 0005-SunStudio-doesn-t-convert-pointers-to-bool-correctly.patch > > > improper pointer/integer combination: op "=" (PyObject * to bool) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-621) Add missing string.h include for Solaris compiler
[ https://issues.apache.org/jira/browse/DISPATCH-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adel Boutros updated DISPATCH-621: -- Attachment: 0011-Add-missing-string.h-include-for-Solaris-compiler.patch > Add missing string.h include for Solaris compiler > - > > Key: DISPATCH-621 > URL: https://issues.apache.org/jira/browse/DISPATCH-621 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros > Attachments: > 0011-Add-missing-string.h-include-for-Solaris-compiler.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-623) Unreachable code (qd_field_iterator_free after a return statement) detected on Solaris
[ https://issues.apache.org/jira/browse/DISPATCH-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adel Boutros updated DISPATCH-623: -- Attachment: 0013-Unreachable-code-qd_field_iterator_free-after-a-retu.patch > Unreachable code (qd_field_iterator_free after a return statement) detected > on Solaris > -- > > Key: DISPATCH-623 > URL: https://issues.apache.org/jira/browse/DISPATCH-623 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros > Attachments: > 0013-Unreachable-code-qd_field_iterator_free-after-a-retu.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-622) use "-lpthread" instead of "-pthread" as compiler error to avoid undefined symbol on Solaris
[ https://issues.apache.org/jira/browse/DISPATCH-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adel Boutros updated DISPATCH-622: -- Attachment: 0012-use-lpthread-instead-of-pthread-as-compiler-error-to.patch > use "-lpthread" instead of "-pthread" as compiler error to avoid undefined > symbol on Solaris > > > Key: DISPATCH-622 > URL: https://issues.apache.org/jira/browse/DISPATCH-622 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros > Attachments: > 0012-use-lpthread-instead-of-pthread-as-compiler-error-to.patch > > > Undefined symbol _mcount : CMakeFiles/qpid-dispatch.dir/bitmask.c.o -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-618) Revert eventfd on Solaris
[ https://issues.apache.org/jira/browse/DISPATCH-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adel Boutros updated DISPATCH-618: -- Attachment: 0008-Revert-eventfd-on-Solaris.patch > Revert eventfd on Solaris > - > > Key: DISPATCH-618 > URL: https://issues.apache.org/jira/browse/DISPATCH-618 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros > Attachments: 0008-Revert-eventfd-on-Solaris.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-616) Arithmetic operations not allowed on void * pointer
[ https://issues.apache.org/jira/browse/DISPATCH-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adel Boutros updated DISPATCH-616: -- Attachment: 0006-Arithmetic-operations-not-allowed-on-void-pointer.patch > Arithmetic operations not allowed on void * pointer > --- > > Key: DISPATCH-616 > URL: https://issues.apache.org/jira/browse/DISPATCH-616 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros > Attachments: > 0006-Arithmetic-operations-not-allowed-on-void-pointer.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-619) Use memalign instead of posix_memalign which is not defined on Solaris
[ https://issues.apache.org/jira/browse/DISPATCH-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adel Boutros updated DISPATCH-619: -- Attachment: 0009-Use-memalign-instead-of-posix_memalign-which-is-not-.patch > Use memalign instead of posix_memalign which is not defined on Solaris > -- > > Key: DISPATCH-619 > URL: https://issues.apache.org/jira/browse/DISPATCH-619 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros > Attachments: > 0009-Use-memalign-instead-of-posix_memalign-which-is-not-.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-620) no-strict-aliasing is only supported with GCC
[ https://issues.apache.org/jira/browse/DISPATCH-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adel Boutros updated DISPATCH-620: -- Attachment: 0010-no-strict-aliasing-is-only-supported-with-GCC.patch > no-strict-aliasing is only supported with GCC > - > > Key: DISPATCH-620 > URL: https://issues.apache.org/jira/browse/DISPATCH-620 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros > Attachments: 0010-no-strict-aliasing-is-only-supported-with-GCC.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-617) Define HOST_NAME_MAX on Unix OSes where _POSIX_HOST_NAME_MAX is defined instead
[ https://issues.apache.org/jira/browse/DISPATCH-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adel Boutros updated DISPATCH-617: -- Attachment: 0007-Define-HOST_NAME_MAX-on-Unix-OSes-where-_POSIX_HOST_.patch > Define HOST_NAME_MAX on Unix OSes where _POSIX_HOST_NAME_MAX is defined > instead > --- > > Key: DISPATCH-617 > URL: https://issues.apache.org/jira/browse/DISPATCH-617 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros > Attachments: > 0007-Define-HOST_NAME_MAX-on-Unix-OSes-where-_POSIX_HOST_.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-615) SunStudio doesn't convert pointers to bool correctly
[ https://issues.apache.org/jira/browse/DISPATCH-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adel Boutros updated DISPATCH-615: -- Attachment: 0005-SunStudio-doesn-t-convert-pointers-to-bool-correctly.patch > SunStudio doesn't convert pointers to bool correctly > > > Key: DISPATCH-615 > URL: https://issues.apache.org/jira/browse/DISPATCH-615 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros > Attachments: > 0005-SunStudio-doesn-t-convert-pointers-to-bool-correctly.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-612) Add support for GCC equivalent compiler options
[ https://issues.apache.org/jira/browse/DISPATCH-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adel Boutros updated DISPATCH-612: -- Attachment: 0002-Add-support-for-GCC-equivalent-compiler-options.patch > Add support for GCC equivalent compiler options > --- > > Key: DISPATCH-612 > URL: https://issues.apache.org/jira/browse/DISPATCH-612 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros > Attachments: > 0002-Add-support-for-GCC-equivalent-compiler-options.patch > > > Some compiler flags used are only for GCC -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-613) Remove semi-column not needed after function definition
[ https://issues.apache.org/jira/browse/DISPATCH-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adel Boutros updated DISPATCH-613: -- Attachment: 0003-Remove-semi-column-not-needed-after-function-definit.patch > Remove semi-column not needed after function definition > --- > > Key: DISPATCH-613 > URL: https://issues.apache.org/jira/browse/DISPATCH-613 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros > Attachments: > 0003-Remove-semi-column-not-needed-after-function-definit.patch > > > Empty statement (an extra ";") causes error on Solaris -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-623) Unreachable code (qd_field_iterator_free after a return statement) detected on Solaris
Adel Boutros created DISPATCH-623: - Summary: Unreachable code (qd_field_iterator_free after a return statement) detected on Solaris Key: DISPATCH-623 URL: https://issues.apache.org/jira/browse/DISPATCH-623 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.7.0 Reporter: Adel Boutros -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-622) use "-lpthread" instead of "-pthread" as compiler error to avoid undefined symbol on Solaris
Adel Boutros created DISPATCH-622: - Summary: use "-lpthread" instead of "-pthread" as compiler error to avoid undefined symbol on Solaris Key: DISPATCH-622 URL: https://issues.apache.org/jira/browse/DISPATCH-622 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.7.0 Reporter: Adel Boutros Undefined symbol _mcount : CMakeFiles/qpid-dispatch.dir/bitmask.c.o -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-616) Arithmetic operations not allowed on void * pointer
Adel Boutros created DISPATCH-616: - Summary: Arithmetic operations not allowed on void * pointer Key: DISPATCH-616 URL: https://issues.apache.org/jira/browse/DISPATCH-616 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.7.0 Reporter: Adel Boutros -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-621) Add missing string.h include for Solaris compiler
Adel Boutros created DISPATCH-621: - Summary: Add missing string.h include for Solaris compiler Key: DISPATCH-621 URL: https://issues.apache.org/jira/browse/DISPATCH-621 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.7.0 Reporter: Adel Boutros -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-620) no-strict-aliasing is only supported with GCC
Adel Boutros created DISPATCH-620: - Summary: no-strict-aliasing is only supported with GCC Key: DISPATCH-620 URL: https://issues.apache.org/jira/browse/DISPATCH-620 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.7.0 Reporter: Adel Boutros -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-615) SunStudio doesn't convert pointers to bool correctly
Adel Boutros created DISPATCH-615: - Summary: SunStudio doesn't convert pointers to bool correctly Key: DISPATCH-615 URL: https://issues.apache.org/jira/browse/DISPATCH-615 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.7.0 Reporter: Adel Boutros -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-617) Define HOST_NAME_MAX on Unix OSes where _POSIX_HOST_NAME_MAX is defined instead
Adel Boutros created DISPATCH-617: - Summary: Define HOST_NAME_MAX on Unix OSes where _POSIX_HOST_NAME_MAX is defined instead Key: DISPATCH-617 URL: https://issues.apache.org/jira/browse/DISPATCH-617 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.7.0 Reporter: Adel Boutros -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-614) strerror_r on Solaris does not return char*
Adel Boutros created DISPATCH-614: - Summary: strerror_r on Solaris does not return char* Key: DISPATCH-614 URL: https://issues.apache.org/jira/browse/DISPATCH-614 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.7.0 Reporter: Adel Boutros -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-618) Revert eventfd on Solaris
Adel Boutros created DISPATCH-618: - Summary: Revert eventfd on Solaris Key: DISPATCH-618 URL: https://issues.apache.org/jira/browse/DISPATCH-618 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.7.0 Reporter: Adel Boutros -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-619) Use memalign instead of posix_memalign which is not defined on Solaris
Adel Boutros created DISPATCH-619: - Summary: Use memalign instead of posix_memalign which is not defined on Solaris Key: DISPATCH-619 URL: https://issues.apache.org/jira/browse/DISPATCH-619 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.7.0 Reporter: Adel Boutros -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-613) Remove semi-column not needed after function definition
Adel Boutros created DISPATCH-613: - Summary: Remove semi-column not needed after function definition Key: DISPATCH-613 URL: https://issues.apache.org/jira/browse/DISPATCH-613 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.7.0 Reporter: Adel Boutros Empty statement (an extra ";") causes error on Solaris -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-612) Add support for GCC equivalent compiler options
Adel Boutros created DISPATCH-612: - Summary: Add support for GCC equivalent compiler options Key: DISPATCH-612 URL: https://issues.apache.org/jira/browse/DISPATCH-612 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.7.0 Reporter: Adel Boutros Some compiler flags used are only for GCC -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7546) [Java Broker] Allow the system tests to be run using the Qpid JMS client for AMQP 1.0 testing
[ https://issues.apache.org/jira/browse/QPID-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15834731#comment-15834731 ] ASF subversion and git services commented on QPID-7546: --- Commit 1779941 from [~k-wall] in branch 'java/trunk' [ https://svn.apache.org/r1779941 ] QPID-7546: [System Tests] Fix MultipleAuthenticationManagersTest, PersistentStoreTest, SplitStoreTest and ClientAcknowledgeTest on AMQP 1.0 persistent profiles > [Java Broker] Allow the system tests to be run using the Qpid JMS client for > AMQP 1.0 testing > - > > Key: QPID-7546 > URL: https://issues.apache.org/jira/browse/QPID-7546 > Project: Qpid > Issue Type: Test > Components: Java Tests >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Attachments: > 0001-QPID-7546-Allow-overriding-of-jms-spec-artifact-in-o.patch > > > Currently the system tests use the JMS client for AMQP 0-8/9/10 and so the > AMQP 1.0 protocol implementation does not get as thoroughly tested. > We should aim to move all the system tests such that they can be run with > either client -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7628) [java] update to current apache parent pom
[ https://issues.apache.org/jira/browse/QPID-7628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15834446#comment-15834446 ] ASF subversion and git services commented on QPID-7628: --- Commit 1779923 from [~k-wall] in branch 'java/trunk' [ https://svn.apache.org/r1779923 ] QPID-7628: Avoid maven build warning "not cross platform compatible" since updating to the new parent POM > [java] update to current apache parent pom > -- > > Key: QPID-7628 > URL: https://issues.apache.org/jira/browse/QPID-7628 > Project: Qpid > Issue Type: Task > Components: Java Broker, Java Client >Reporter: Robbie Gemmell >Assignee: Keith Wall > Fix For: qpid-java-7.0 > > > It would be good to update the build(s) to use the current apache parent pom, > v18, to better align our various components in terms of plugin usage etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7565) Refactor API/mechanism used to effect state change
[
https://issues.apache.org/jira/browse/QPID-7565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7565:
-
Fix Version/s: Future
> Refactor API/mechanism used to effect state change
> --
>
> Key: QPID-7565
> URL: https://issues.apache.org/jira/browse/QPID-7565
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
>Reporter: Keith Wall
> Fix For: Future
>
>
> Currently the state changes are driven by updates to attribute
> {{desiredState}}. This is implemented internally as annotated state change
> methods which are called reflectively. The current approach has a number of
> disadvantages, most notedly, that it is not obvious how these methods should
> interact when overriding objects also provide their own private state change
> methods whose annotations intersect.
> We should reimplement state change in a simpler way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7611) [Java Broker] Enable tracer messages that will produce certain logging while passing through the broker
[
https://issues.apache.org/jira/browse/QPID-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15834227#comment-15834227
]
Keith Wall commented on QPID-7611:
--
Would this not mostly duplicate the functionality provided by
{{UserOrConnectionSpecific}} inclusion rules? I can already turn on per user
or per connection logging. Do we need the extra feature?
> [Java Broker] Enable tracer messages that will produce certain logging while
> passing through the broker
> ---
>
> Key: QPID-7611
> URL: https://issues.apache.org/jira/browse/QPID-7611
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker
>Reporter: Lorenz Quack
> Fix For: Future
>
>
> From IRC:
> {code}
> As an aside / new functionality idea … it might be neat to allow
> us to annotate messages in some way so that they generate logging statements
> as they go by… so you can use them like tracer bullets without overwhelming
> the whole system with logs
> I like that idea
> Rabbit also has this: http://www.rabbitmq.com/firehose.html
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7559) [Java Broker] Potentially improve performance by refactoring QueueConsumerManager
[
https://issues.apache.org/jira/browse/QPID-7559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7559:
-
Fix Version/s: Future
> [Java Broker] Potentially improve performance by refactoring
> QueueConsumerManager
> -
>
> Key: QPID-7559
> URL: https://issues.apache.org/jira/browse/QPID-7559
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
>Reporter: Lorenz Quack
> Fix For: Future
>
>
> In {{org.apache.qpid.server.queue.AbstractQueue#deliverSingleMessage}} we
> currently call {{_queueConsumerManager.setNotified()}} twice to guard against
> a race condition (a message becoming available just before a consumer is
> moved from notified to interested). We could potentially optimise this by
> merging the Notified and Interested lists.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7611) [Java Broker] Enable tracer messages that will produce certain logging while passing through the broker
[
https://issues.apache.org/jira/browse/QPID-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7611:
-
Fix Version/s: Future
> [Java Broker] Enable tracer messages that will produce certain logging while
> passing through the broker
> ---
>
> Key: QPID-7611
> URL: https://issues.apache.org/jira/browse/QPID-7611
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker
>Reporter: Lorenz Quack
> Fix For: Future
>
>
> From IRC:
> {code}
> As an aside / new functionality idea … it might be neat to allow
> us to annotate messages in some way so that they generate logging statements
> as they go by… so you can use them like tracer bullets without overwhelming
> the whole system with logs
> I like that idea
> Rabbit also has this: http://www.rabbitmq.com/firehose.html
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7566) [Java Broker] Potentially improve performance by separating IO from processing of commands
[ https://issues.apache.org/jira/browse/QPID-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7566: - Fix Version/s: Future > [Java Broker] Potentially improve performance by separating IO from > processing of commands > -- > > Key: QPID-7566 > URL: https://issues.apache.org/jira/browse/QPID-7566 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Lorenz Quack > Fix For: Future > > > Currently, when the broker receives a AMQP command the response is handled > synchronously in the same IO thread. We could try to separate those steps > into three distinct asynchronous tasks: receive message, process, send > response. This could help us making more efficient use of the IO bandwidth by > pipe-lining the IO workload. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7610) [Java Broker] MemorySystemConfig should override the default preferenceStoreAttributes
[
https://issues.apache.org/jira/browse/QPID-7610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15834219#comment-15834219
]
Keith Wall commented on QPID-7610:
--
Low priority for 7.0 - Lorenz believes this is a one line change.
> [Java Broker] MemorySystemConfig should override the default
> preferenceStoreAttributes
> --
>
> Key: QPID-7610
> URL: https://issues.apache.org/jira/browse/QPID-7610
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
>Reporter: Lorenz Quack
>Priority: Minor
> Fix For: qpid-java-7.0
>
>
> The MemorySystemConfig should override the preferenceStoreAttributes and
> provide a "Memory" type to make embedding the broker easier.
> from an IRC conversation:
> {code}
> [...]
> It would make sense if the Memory one overrode it to Memory then
> no?
> yeah - or to NoOp really
> It's my understanding they're used with the admin UI, so if they
> were Noop then something wouldn't work?
> yes, it looks like we could improve it
> [...]
> to the point that jameshowe makes - I agree, noop isn't really
> right… we want a memory type, or to have MemorySystemConfig implement the
> provider interface
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7610) [Java Broker] MemorySystemConfig should override the default preferenceStoreAttributes
[
https://issues.apache.org/jira/browse/QPID-7610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7610:
-
Fix Version/s: qpid-java-7.0
> [Java Broker] MemorySystemConfig should override the default
> preferenceStoreAttributes
> --
>
> Key: QPID-7610
> URL: https://issues.apache.org/jira/browse/QPID-7610
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
>Reporter: Lorenz Quack
>Priority: Minor
> Fix For: qpid-java-7.0
>
>
> The MemorySystemConfig should override the preferenceStoreAttributes and
> provide a "Memory" type to make embedding the broker easier.
> from an IRC conversation:
> {code}
> [...]
> It would make sense if the Memory one overrode it to Memory then
> no?
> yeah - or to NoOp really
> It's my understanding they're used with the admin UI, so if they
> were Noop then something wouldn't work?
> yes, it looks like we could improve it
> [...]
> to the point that jameshowe makes - I agree, noop isn't really
> right… we want a memory type, or to have MemorySystemConfig implement the
> provider interface
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7573) [Java Broker] Document new operational logging for configured object lifecycle and management operations
[
https://issues.apache.org/jira/browse/QPID-7573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7573:
-
Priority: Minor (was: Major)
> [Java Broker] Document new operational logging for configured object
> lifecycle and management operations
>
>
> Key: QPID-7573
> URL: https://issues.apache.org/jira/browse/QPID-7573
> Project: Qpid
> Issue Type: Improvement
> Components: Documentation, Java Broker
>Affects Versions: qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2,
> qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1,
> qpid-java-7.0
>Reporter: Alex Rudyy
>Priority: Minor
> Fix For: qpid-java-7.0
>
>
> Operational logging for life cycle and management operations for
> Authentication Providers, Keystores, Trustores, ACL Providers, etc is missed
> in Broker documentation.
> An example of missed operational logging:
> {noformat}
> CREATE = ATH-1001 : Create "{0}"
> OPEN = ATH-1002 : Open
> CLOSE = ATH-1003 : Close
> DELETE = ATH-1004 : Delete "{0}"
> OPERATION = ATH-1005 : Operation : {0}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7573) [Java Broker] Document new operational logging for configured object lifecycle and management operations
[
https://issues.apache.org/jira/browse/QPID-7573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7573:
-
Fix Version/s: qpid-java-7.0
> [Java Broker] Document new operational logging for configured object
> lifecycle and management operations
>
>
> Key: QPID-7573
> URL: https://issues.apache.org/jira/browse/QPID-7573
> Project: Qpid
> Issue Type: Improvement
> Components: Documentation, Java Broker
>Affects Versions: qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2,
> qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1,
> qpid-java-7.0
>Reporter: Alex Rudyy
> Fix For: qpid-java-7.0
>
>
> Operational logging for life cycle and management operations for
> Authentication Providers, Keystores, Trustores, ACL Providers, etc is missed
> in Broker documentation.
> An example of missed operational logging:
> {noformat}
> CREATE = ATH-1001 : Create "{0}"
> OPEN = ATH-1002 : Open
> CLOSE = ATH-1003 : Close
> DELETE = ATH-1004 : Delete "{0}"
> OPERATION = ATH-1005 : Operation : {0}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
