[jira] [Updated] (PROTON-1709) Python binding: ApplicationEvent causing memory growth

[Justin Ross (JIRA)]

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

Justin Ross updated PROTON-1709:

Fix Version/s: (was: proton-c-0.19.0)
   proton-c-0.20.0

> Python binding: ApplicationEvent causing memory growth
> --
>
> Key: PROTON-1709
> URL: https://issues.apache.org/jira/browse/PROTON-1709
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: python-binding
>Affects Versions: proton-c-0.18.1
>Reporter: Xin Chen
>Assignee: Justin Ross
>  Labels: leak
> Fix For: proton-c-0.20.0
>
>
> ApplicationEvent creates a new EventType object in the constructor. The 
> EventType object adds itself to the TYPES dict always, even for the same 
> typename. There is no way for the application to avoid this by providing an 
> EventType object directly. Repro code below:
> {code:java}
> import threading
> from proton.reactor import Container, ApplicationEvent, EventInjector
> class Program:
> def __init__(self, injector):
> self.injector = injector
> def on_reactor_init(self, event):
> event.reactor.selectable(self.injector)
> def on_hello(self, event):
> print(event.subject)
> def on_done(self, event):
> event.subject.stop()
> e = EventInjector()
> r = Container(Program(e))
> t = threading.Thread(target=r.run)
> t.start()
> for i in range(1, 1000):
> e.trigger(ApplicationEvent("hello", subject=str(i)))
> e.trigger(ApplicationEvent("done", subject=r))
> t.join()
> {code}



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

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

[jira] [Updated] (PROTON-1455) Problem building on Ubuntu xenial with g++

[Justin Ross (JIRA)]

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

Justin Ross updated PROTON-1455:

Fix Version/s: (was: proton-c-0.19.0)
   proton-c-0.20.0

> Problem building on Ubuntu xenial with g++
> --
>
> Key: PROTON-1455
> URL: https://issues.apache.org/jira/browse/PROTON-1455
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: build, proton-c
>Reporter: Irina Boverman
>Assignee: Justin Ross
> Fix For: proton-c-0.20.0
>
>
>  31%] Building CXX object 
> proton-c/CMakeFiles/qpid-proton.dir/src/messenger/transform.c.o
> cd /proton/build/proton-c && /usr/bin/c++  -std=c++11  -Dqpid_proton_EXPORTS 
> -I/proton/build/proton-c/src -I/proton/build/proton-c/include 
> -I/proton/proton-c/src -I/proton/proton-c/include  -fvisibility=hidden -O2 -g 
> -DNDEBUG -fPIC   -Werror -Wall -pedantic-errors -Wno-format 
> -Wno-variadic-macros   -o 
> CMakeFiles/qpid-proton.dir/src/messenger/transform.c.o -c 
> /proton/proton-c/src/messenger/transform.c
> [ 31%] Building CXX object 
> proton-c/CMakeFiles/qpid-proton.dir/src/platform/platform.c.o
> cd /proton/build/proton-c && /usr/bin/c++  -std=c++11  -Dqpid_proton_EXPORTS 
> -DUSE_ATOLL -DUSE_CLOCK_GETTIME -DUSE_STRERROR_R -I/proton/build/proton-c/src 
> -I/proton/build/proton-c/include -I/proton/proton-c/src 
> -I/proton/proton-c/include  -fvisibility=hidden -O2 -g -DNDEBUG -fPIC   
> -Werror -Wall -pedantic-errors -Wno-format -Wno-variadic-macros   -o 
> CMakeFiles/qpid-proton.dir/src/platform/platform.c.o -c 
> /proton/proton-c/src/platform/platform.c
> /proton/proton-c/src/platform/platform.c: In function 'void 
> pn_i_strerror(int, char*, size_t)':
> /proton/proton-c/src/platform/platform.c:92:34: error: ignoring return value 
> of 'char* strerror_r(int, char*, size_t)', declared with attribute 
> warn_unused_result [-Werror=unused-result]
>strerror_r(errnum, buf, buflen);
>   ^
> cc1plus: all warnings being treated as errors
> proton-c/CMakeFiles/qpid-proton.dir/build.make:1081: recipe for target 
> 'proton-c/CMakeFiles/qpid-proton.dir/src/platform/platform.c.o' failed
> make[2]: Leaving directory '/proton/build'
> make[2]: *** [proton-c/CMakeFiles/qpid-proton.dir/src/platform/platform.c.o] 
> Error 1



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

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

[jira] [Updated] (PROTON-1671) Warn on conversions from the proton::returned type

[Justin Ross (JIRA)]

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

Justin Ross updated PROTON-1671:

Fix Version/s: (was: proton-c-0.19.0)
   proton-c-0.20.0

> Warn on conversions from the proton::returned type
> --
>
> Key: PROTON-1671
> URL: https://issues.apache.org/jira/browse/PROTON-1671
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Reporter: Justin Ross
>Assignee: Justin Ross
> Fix For: proton-c-0.20.0
>
>
> Using the converted return type can easily result in thread-unsafe code.



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

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

[jira] [Updated] (PROTON-1468) [python] attempting to pip install on windows should fail gracefully

[Justin Ross (JIRA)]

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

Justin Ross updated PROTON-1468:

Fix Version/s: proton-c-0.20.0

> [python] attempting to pip install on windows should fail gracefully
> 
>
> Key: PROTON-1468
> URL: https://issues.apache.org/jira/browse/PROTON-1468
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: python-binding
>Affects Versions: proton-c-0.17.0
>Reporter: Ken Giusti
>Assignee: Justin Ross
> Fix For: proton-c-0.20.0
>
>
> Until PROTON-1467 is fixed, attempting to pip install the python packages on 
> windows should immediately fail with a user-friendly message instead of 
> attempting to build the C extension and fail with a cryptic compiler error.



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

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

[jira] [Updated] (PROTON-261) pn_delivery_local_state and pn_delivery_remote_state can return a zero value (outside that defined by the pn_disposition_t enum)

[Justin Ross (JIRA)]

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

Justin Ross updated PROTON-261:
---
Priority: Minor  (was: Major)

> pn_delivery_local_state and pn_delivery_remote_state can return a zero value 
> (outside that defined by the pn_disposition_t enum)
> 
>
> Key: PROTON-261
> URL: https://issues.apache.org/jira/browse/PROTON-261
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Affects Versions: 0.5
>Reporter: Keith Wall
>Assignee: Justin Ross
>Priority: Minor
>  Labels: api
> Fix For: proton-c-0.20.0
>
>
> In proton-c, pn_delivery_local_state and pn_delivery_remote_state are defined 
> as returning an pn_disposition_t:
> PN_EXTERN pn_disposition_t pn_delivery_local_state(pn_delivery_t *delivery);
> PN_EXTERN pn_disposition_t pn_delivery_remote_state(pn_delivery_t *delivery);
> with pn_disposition_t defined as:
> typedef enum pn_disposition_t {
>   PN_RECEIVED=1,
>   PN_ACCEPTED=2,
>   PN_REJECTED=3,
>   PN_RELEASED=4,
>   PN_MODIFIED=5
> } pn_disposition_t;
> However, there are circumstances when the proton-c implementation returns a 
> value outside this enumeration - value 0 - coming for the struct 
> initialisation in pn_delivery().  What does this value mean and how is an 
> application supposed to react to this value?   Are there an implicit 
> restrictions regarding when an application may call 
> pn_delivery_local_state/pn_delivery_remote_state?
> btw.  This question arises from work on PROTON-257.  Proton-jni (Swig 
> generated code - so called "Proper enums" - see 
> http://www.swig.org/Doc2.0/Java.html#Java_proper_enums_classes) is failing to 
> decode the enum when testing the state of a newly created Delivery.
> test(org.apache.qpid.proton.systemtests.ProtonEngineExampleTest)  Time 
> elapsed: 0.109 sec  <<< ERROR!
> java.lang.IllegalArgumentException: No enum class 
> org.apache.qpid.proton.jni.pn_disposition_t with value 0
> at 
> org.apache.qpid.proton.jni.pn_disposition_t.swigToEnum(pn_disposition_t.java:32)
> at 
> org.apache.qpid.proton.jni.Proton.pn_delivery_local_state(Proton.java:624)
> at 
> org.apache.qpid.proton.engine.jni.JNIDelivery.getLocalState(JNIDelivery.java:100)
> at 
> org.apache.qpid.proton.systemtests.ProtonEngineExampleTest.test(ProtonEngineExampleTest.java:190)



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

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

[jira] [Updated] (PROTON-261) pn_delivery_local_state and pn_delivery_remote_state can return a zero value (outside that defined by the pn_disposition_t enum)

[Justin Ross (JIRA)]

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

Justin Ross updated PROTON-261:
---
Issue Type: Improvement  (was: Bug)

> pn_delivery_local_state and pn_delivery_remote_state can return a zero value 
> (outside that defined by the pn_disposition_t enum)
> 
>
> Key: PROTON-261
> URL: https://issues.apache.org/jira/browse/PROTON-261
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Affects Versions: 0.5
>Reporter: Keith Wall
>Assignee: Justin Ross
>  Labels: api
> Fix For: proton-c-0.20.0
>
>
> In proton-c, pn_delivery_local_state and pn_delivery_remote_state are defined 
> as returning an pn_disposition_t:
> PN_EXTERN pn_disposition_t pn_delivery_local_state(pn_delivery_t *delivery);
> PN_EXTERN pn_disposition_t pn_delivery_remote_state(pn_delivery_t *delivery);
> with pn_disposition_t defined as:
> typedef enum pn_disposition_t {
>   PN_RECEIVED=1,
>   PN_ACCEPTED=2,
>   PN_REJECTED=3,
>   PN_RELEASED=4,
>   PN_MODIFIED=5
> } pn_disposition_t;
> However, there are circumstances when the proton-c implementation returns a 
> value outside this enumeration - value 0 - coming for the struct 
> initialisation in pn_delivery().  What does this value mean and how is an 
> application supposed to react to this value?   Are there an implicit 
> restrictions regarding when an application may call 
> pn_delivery_local_state/pn_delivery_remote_state?
> btw.  This question arises from work on PROTON-257.  Proton-jni (Swig 
> generated code - so called "Proper enums" - see 
> http://www.swig.org/Doc2.0/Java.html#Java_proper_enums_classes) is failing to 
> decode the enum when testing the state of a newly created Delivery.
> test(org.apache.qpid.proton.systemtests.ProtonEngineExampleTest)  Time 
> elapsed: 0.109 sec  <<< ERROR!
> java.lang.IllegalArgumentException: No enum class 
> org.apache.qpid.proton.jni.pn_disposition_t with value 0
> at 
> org.apache.qpid.proton.jni.pn_disposition_t.swigToEnum(pn_disposition_t.java:32)
> at 
> org.apache.qpid.proton.jni.Proton.pn_delivery_local_state(Proton.java:624)
> at 
> org.apache.qpid.proton.engine.jni.JNIDelivery.getLocalState(JNIDelivery.java:100)
> at 
> org.apache.qpid.proton.systemtests.ProtonEngineExampleTest.test(ProtonEngineExampleTest.java:190)



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

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

[jira] [Updated] (PROTON-261) pn_delivery_local_state and pn_delivery_remote_state can return a zero value (outside that defined by the pn_disposition_t enum)

[Justin Ross (JIRA)]

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

Justin Ross updated PROTON-261:
---
Fix Version/s: (was: proton-c-0.19.0)
   proton-c-0.20.0

> pn_delivery_local_state and pn_delivery_remote_state can return a zero value 
> (outside that defined by the pn_disposition_t enum)
> 
>
> Key: PROTON-261
> URL: https://issues.apache.org/jira/browse/PROTON-261
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Affects Versions: 0.5
>Reporter: Keith Wall
>Assignee: Justin Ross
>Priority: Minor
>  Labels: api
> Fix For: proton-c-0.20.0
>
>
> In proton-c, pn_delivery_local_state and pn_delivery_remote_state are defined 
> as returning an pn_disposition_t:
> PN_EXTERN pn_disposition_t pn_delivery_local_state(pn_delivery_t *delivery);
> PN_EXTERN pn_disposition_t pn_delivery_remote_state(pn_delivery_t *delivery);
> with pn_disposition_t defined as:
> typedef enum pn_disposition_t {
>   PN_RECEIVED=1,
>   PN_ACCEPTED=2,
>   PN_REJECTED=3,
>   PN_RELEASED=4,
>   PN_MODIFIED=5
> } pn_disposition_t;
> However, there are circumstances when the proton-c implementation returns a 
> value outside this enumeration - value 0 - coming for the struct 
> initialisation in pn_delivery().  What does this value mean and how is an 
> application supposed to react to this value?   Are there an implicit 
> restrictions regarding when an application may call 
> pn_delivery_local_state/pn_delivery_remote_state?
> btw.  This question arises from work on PROTON-257.  Proton-jni (Swig 
> generated code - so called "Proper enums" - see 
> http://www.swig.org/Doc2.0/Java.html#Java_proper_enums_classes) is failing to 
> decode the enum when testing the state of a newly created Delivery.
> test(org.apache.qpid.proton.systemtests.ProtonEngineExampleTest)  Time 
> elapsed: 0.109 sec  <<< ERROR!
> java.lang.IllegalArgumentException: No enum class 
> org.apache.qpid.proton.jni.pn_disposition_t with value 0
> at 
> org.apache.qpid.proton.jni.pn_disposition_t.swigToEnum(pn_disposition_t.java:32)
> at 
> org.apache.qpid.proton.jni.Proton.pn_delivery_local_state(Proton.java:624)
> at 
> org.apache.qpid.proton.engine.jni.JNIDelivery.getLocalState(JNIDelivery.java:100)
> at 
> org.apache.qpid.proton.systemtests.ProtonEngineExampleTest.test(ProtonEngineExampleTest.java:190)



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

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

[jira] [Updated] (PROTON-893) Calling session.close() on non-active session causes client segfault

[Justin Ross (JIRA)]

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

Justin Ross updated PROTON-893:
---
Fix Version/s: (was: proton-c-0.19.0)
   proton-c-0.20.0

> Calling session.close() on non-active session causes client segfault
> 
>
> Key: PROTON-893
> URL: https://issues.apache.org/jira/browse/PROTON-893
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: python-binding
>Affects Versions: 0.9.1
> Environment: packages:
> qpid-proton-c-0.9-3
> qpid-proton-c-devel-0.9-3
> python-qpid-proton-0.9-3
>Reporter: Petr Matousek
>Assignee: Justin Ross
>Priority: Minor
>  Labels: crash, reproducer
> Fix For: proton-c-0.20.0
>
> Attachments: session_close_con.py, session_close_ssn.py, 
> stacktrace.txt
>
>
> Calling the session.close() on non-active session causes client segfault (see 
> the attached reproducer session_close_con.py).
> Moreover calling connection.session().close() causes client seqfault even if 
> the session shall be in active state (see the attached reproducer 
> session_close_ssn.py).



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

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

[jira] [Updated] (PROTON-1468) [python] attempting to pip install on windows should fail gracefully

[Justin Ross (JIRA)]

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

Justin Ross updated PROTON-1468:

Fix Version/s: (was: proton-c-0.19.0)

> [python] attempting to pip install on windows should fail gracefully
> 
>
> Key: PROTON-1468
> URL: https://issues.apache.org/jira/browse/PROTON-1468
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: python-binding
>Affects Versions: proton-c-0.17.0
>Reporter: Ken Giusti
>Assignee: Justin Ross
> Fix For: proton-c-0.20.0
>
>
> Until PROTON-1467 is fixed, attempting to pip install the python packages on 
> windows should immediately fail with a user-friendly message instead of 
> attempting to build the C extension and fail with a cryptic compiler error.



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

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

[jira] [Updated] (PROTON-1515) Python sender client doesn't check actual link state and continues to send messages even if link is down

[Justin Ross (JIRA)]

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

Justin Ross updated PROTON-1515:

Fix Version/s: (was: proton-c-0.19.0)
   proton-c-0.20.0

> Python sender client doesn't check actual link state and continues to send 
> messages even if link is down
> 
>
> Key: PROTON-1515
> URL: https://issues.apache.org/jira/browse/PROTON-1515
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: python-binding
> Environment: RHEL7.3
> Jboss AMQ 7
> python-qpid-proton.x86_64-0.14.0-1.el7
>Reporter: Dmitrii Puzikov
>Assignee: Justin Ross
> Fix For: proton-c-0.20.0
>
> Attachments: sender.log
>
>
> Steps to reproduce:
> 1. Start broker
> 2. Create queue
> 3. Start sending e.g. 10 messages with python sender
> 4. Kill broker
> 5. Notice that client continues send messages and raises exception only after 
> all 10 messages were sent.
> Actual behavior: Python sender client ignores link failure until all messages 
> were sent and only then raises an exception/ begins re-connection attempmts.
> Expected behavior: Client should stop sending messages and raise exception or 
> try to begin re-connection attempts if reconnect option is set.
> Please, see sender.log. Global handler was added for event logging purposes. 
> It just prints event/handler name.



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

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

[jira] [Updated] (PROTON-1599) Add deprecation warnings to the C API

[Justin Ross (JIRA)]

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

Justin Ross updated PROTON-1599:

Fix Version/s: (was: proton-c-0.19.0)
   proton-c-0.20.0

> Add deprecation warnings to the C API
> -
>
> Key: PROTON-1599
> URL: https://issues.apache.org/jira/browse/PROTON-1599
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Reporter: Ken Giusti
>Assignee: Justin Ross
>Priority: Trivial
>  Labels: api
> Fix For: proton-c-0.20.0
>
>
> Once PROTON-225 is implemented, we should eventually remove the old 
> interfaces after marking them deprecated.
> Example:
> #ifdef __GNUC__
> #define DEPRECATED(func) func __attribute__ ((deprecated))
> #elif defined(_MSC_VER)
> #define DEPRECATED(func) __declspec(deprecated) func
> #else
> #pragma message("WARNING: You need to implement DEPRECATED for this compiler")
> #define DEPRECATED(func) func
> #endif



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

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

[jira] [Commented] (PROTON-1477) Problem building qpid-proton 0.17.0 in Fedora rawhide

[Irina Boverman (JIRA)]

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

Irina Boverman commented on PROTON-1477:


No, this is no longer an issue (proton 0.18.1 build).

> Problem building qpid-proton 0.17.0 in Fedora rawhide
> -
>
> Key: PROTON-1477
> URL: https://issues.apache.org/jira/browse/PROTON-1477
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: build
> Environment: x86_64
>Reporter: Irina Boverman
>Assignee: Justin Ross
> Fix For: proton-c-0.19.0
>
>
> [ 39%] Swig source
> cd /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl && 
> /usr/bin/cmake -E make_directory 
> /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl
> make[2]: Leaving directory '/builddir/build/BUILD/qpid-proton-0.17.0'
> cd /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl && 
> /usr/bin/swig -perl -outdir 
> /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl -shadow 
> -I/builddir/build/BUILD/qpid-proton-0.17.0/proton-c/src 
> -I/builddir/build/BUILD/qpid-proton-0.17.0/proton-c/include -I/usr/include 
> -I/usr/lib64/perl5/CORE -o 
> /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl/perlPERL_wrap.c
>  /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl/perl.i
> make[2]: Leaving directory '/builddir/build/BUILD/qpid-proton-0.17.0'
> cc1plus: error: -Wformat-security ignored without -Wformat 
> [-Werror=format-security]
> cc1plus: all warnings being treated as errors
> make[2]: *** 
> [proton-c/bindings/cpp/CMakeFiles/qpid-proton-cpp.dir/build.make:66: 
> proton-c/bindings/cpp/CMakeFiles/qpid-proton-cpp.dir/src/binary.cpp.o] Error 1



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

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

Re: Proposal to create Docker images for Qpid components.

[Irina Boverman]

For review and comments:

https://github.com/irinabov/docker-qpid-cpp-broker
https://github.com/irinabov/docker-qpid-dispatch-router
--
Regards, Irina.

On Thu, Dec 7, 2017 at 3:35 PM, Ken Giusti  wrote:

> Hey!
>
> Just following up on this thread.  What's the status?
>
> thanks,
>
> -K
>
> On Tue, Jul 11, 2017 at 11:27 AM, Robbie Gemmell
>  wrote:
> > On 29 June 2017 at 17:52, Irina Boverman  wrote:
> >> Thank you all who thoughtfully responded to this proposal. This is a
> >> summary as I understood it and my comments regarding these points.
> >>
> >> (1) Qpid community is in favour of creating and maintaining docker
> images
> >> for cpp/java brokers
> >> and dispatch router. OS choice is less important, as long as the user
> can
> >> connect to the broker/router port. We only need to support one OS
> choice.
> >>
> >> I think this is a good start. It covers a use case when someone wants to
> >> test or deploy client apps against broker/router conveniently running
> as a
> >> docker service.
> >>
> >> I think there might be another use case for those users who want to
> develop
> >> client apps in a known environment with client libraries already
> installed
> >> for them to work with. I think the OS choice is important to these users
> >> because they may have a preference/better knowledge of this particular
> OS.
> >> Please consider this use case.
> >>
> >> (2) Docker images should be of minimal size.
> >>
> >> As a concept, I fully agree with it. However, community support for
> >> official images also makes sense to me. These images go through review
> and
> >> testing, as well as, get patches for CVEs. There is a whole
> infrastructure
> >> in place in Fedora to build docker images, etc following best practices
> >> from OCI.
> >>
> >> Official images range in size between 120 to 200 mb, and have 10+ mil of
> >> downloads, so the size does not appear to be an obstacle to adopting
> them.
> >> It is my opinion that future official images will evolve to be better
> >> aligned with how they are used, for example "server" and "workstation",
> etc.
> >>
> >> REPOSITORY  TAG IMAGE ID
> >> CREATED SIZE
> >> docker.io/ubuntulatest  ebcd9d4fca80
> >> 6 weeks ago 117.9 MB
> >> docker.io/debianlatest  e5599115b6a6
> >> 5 months ago123 MB
> >> docker.io/centoslatest  67591570dd29
> >> 6 months ago191.8 MB
> >> docker.io/fedoralatest  a1e614f0f30e
> >> 6 months ago197.1 MB
> >>
> >> We can also modify the base image to remove some items if we think they
> are
> >> not needed.
> >>
> >
> > I think using a base OS image is fine, and your text and Justin's link
> > suggests there are likely to be improvements in some regards in this
> > area too. There is also nothing stopping a further image as minimal
> > size option based on Alpine etc, but obviously components would need
> > to work and be supported there first and it wasn't clear that is
> > currently always true.
> >
> >> My personal preference is to start with fedora image because this
> >> distribution has latest upstream releases for qpid packages, and I am
> the
> >> maintainer for a number of these packages.
> >
> > I think we possibly need some clarity around the end result here, as
> > it could strongly influence this particular area.
> >
> > For images to be considered 'official' Apache Qpid artifacts
> > maintained directly by the project, they and their Qpid related
> > contents would really need to be fully managed in concert with the
> > projects release process. For example, if such an image were utilising
> > packages to incorporate their relevant Qpid bits then I think it
> > follows those packages would similarly need to be considered
> > 'official' and handled similarly. Utilising the Qpid packages from
> > Fedora distributions for example, wouldn't be appropriate in an
> > 'official Apache Qpid' image since they are not directly managed
> > artifacts of the Apache Qpid project.
> >
> > There wouldn't be an issue in simply considering such images to be a
> > community-created convenience binaries based on the projects source
> > release, as e.g. the existing Fedora packages themselves already are,
> > but they wouldn't be considered 'official' Apache Qpid artifacts. It
> > is worth saying this isn't particularly unusual, for example httpd
> > direct people to their source releases but do reference various third
> > party binaries for Windows users, and don't seem to be involved with
> > the docker images for httpd, with members of the docker community
> > instead handling that.
> >
> > I think either approach works here, having distribution based packages
> > obviously has certain advantages for users and the project, so its
> > probably more of a question around 

[jira] [Commented] (PROTON-1711) SSL_IMPL none SASL_IMPL none build attempts to build c-ssl-tests and fails

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PROTON-1711:


Github user astitcher commented on the issue:

https://github.com/apache/qpid-proton/pull/131
  
@RoddieKieley  I've fixed this issue now - can you close the PR (stupidly I 
forgot to add that to the commit).


> SSL_IMPL none SASL_IMPL none build attempts to build c-ssl-tests and fails
> --
>
> Key: PROTON-1711
> URL: https://issues.apache.org/jira/browse/PROTON-1711
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
> Environment: Fedora 25
> OSX 10.11.6
>Reporter: Roddie Kieley
>Assignee: Andrew Stitcher
> Fix For: proton-c-0.19.0
>
>
> When building a default build via 'cmake ../qpid-proton' everything builds as 
> expected. However after using 'ccmake ../qpid-proton' and setting SSL_IMPL to 
> none we see:
> Fedora 25
> {code}
> .
> .
> .
> [ 76%] Linking C executable c-data-tests
> [ 76%] Built target c-data-tests
> [ 77%] Building C object proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/ssl.c.o
> [ 77%] Linking C executable c-ssl-tests
> CMakeFiles/c-ssl-tests.dir/ssl.c.o: In function `test_ssl_protocols':
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:29:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:31:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:33:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:36:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:37:
>  undefined reference to `pn_ssl_domain_set_protocols'
> CMakeFiles/c-ssl-tests.dir/ssl.c.o:/home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:38:
>  more undefined references to `pn_ssl_domain_set_protocols' follow
> collect2: error: ld returned 1 exit status
> proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/build.make:95: recipe for 
> target 'proton-c/src/tests/c-ssl-tests' failed
> gmake[2]: *** [proton-c/src/tests/c-ssl-tests] Error 1
> CMakeFiles/Makefile2:2435: recipe for target 
> 'proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all' failed
> gmake[1]: *** [proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all] Error 2
> Makefile:140: recipe for target 'all' failed
> gmake: *** [all] Error 2
> [rkieley@i7t450s 6]$
> {code}
> OSX 10.11.6
> {code}
> .
> .
> .
> [ 76%] Building C object 
> proton-c/src/tests/CMakeFiles/c-engine-tests.dir/engine.c.o
> [ 76%] Linking C executable c-engine-tests
> [ 76%] Built target c-engine-tests
> [ 77%] Building C object proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/ssl.c.o
> [ 77%] Linking C executable c-ssl-tests
> Undefined symbols for architecture x86_64:
>   "_pn_ssl_domain_set_protocols", referenced from:
>   _test_ssl_protocols in ssl.c.o
> ld: symbol(s) not found for architecture x86_64
> clang: error: linker command failed with exit code 1 (use -v to see 
> invocation)
> gmake[2]: *** [proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/build.make:96: 
> proton-c/src/tests/c-ssl-tests] Error 1
> gmake[1]: *** [CMakeFiles/Makefile2:2436: 
> proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all] Error 2
> gmake: *** [Makefile:141: all] Error 2
> earth:153 rkieley$
> {code}
> Note that I also had disabled the bindings as well as set SASL_IMPL to none.



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

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

[jira] [Commented] (PROTON-1711) SSL_IMPL none SASL_IMPL none build attempts to build c-ssl-tests and fails

[ASF subversion and git services (JIRA)]

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

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

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

PROTON-1711: Make build/test work without any SSL implementation
- Added missing stub function
- Skip ssl test if there is no ssl impl.


> SSL_IMPL none SASL_IMPL none build attempts to build c-ssl-tests and fails
> --
>
> Key: PROTON-1711
> URL: https://issues.apache.org/jira/browse/PROTON-1711
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
> Environment: Fedora 25
> OSX 10.11.6
>Reporter: Roddie Kieley
>Assignee: Andrew Stitcher
>
> When building a default build via 'cmake ../qpid-proton' everything builds as 
> expected. However after using 'ccmake ../qpid-proton' and setting SSL_IMPL to 
> none we see:
> Fedora 25
> {code}
> .
> .
> .
> [ 76%] Linking C executable c-data-tests
> [ 76%] Built target c-data-tests
> [ 77%] Building C object proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/ssl.c.o
> [ 77%] Linking C executable c-ssl-tests
> CMakeFiles/c-ssl-tests.dir/ssl.c.o: In function `test_ssl_protocols':
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:29:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:31:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:33:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:36:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:37:
>  undefined reference to `pn_ssl_domain_set_protocols'
> CMakeFiles/c-ssl-tests.dir/ssl.c.o:/home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:38:
>  more undefined references to `pn_ssl_domain_set_protocols' follow
> collect2: error: ld returned 1 exit status
> proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/build.make:95: recipe for 
> target 'proton-c/src/tests/c-ssl-tests' failed
> gmake[2]: *** [proton-c/src/tests/c-ssl-tests] Error 1
> CMakeFiles/Makefile2:2435: recipe for target 
> 'proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all' failed
> gmake[1]: *** [proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all] Error 2
> Makefile:140: recipe for target 'all' failed
> gmake: *** [all] Error 2
> [rkieley@i7t450s 6]$
> {code}
> OSX 10.11.6
> {code}
> .
> .
> .
> [ 76%] Building C object 
> proton-c/src/tests/CMakeFiles/c-engine-tests.dir/engine.c.o
> [ 76%] Linking C executable c-engine-tests
> [ 76%] Built target c-engine-tests
> [ 77%] Building C object proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/ssl.c.o
> [ 77%] Linking C executable c-ssl-tests
> Undefined symbols for architecture x86_64:
>   "_pn_ssl_domain_set_protocols", referenced from:
>   _test_ssl_protocols in ssl.c.o
> ld: symbol(s) not found for architecture x86_64
> clang: error: linker command failed with exit code 1 (use -v to see 
> invocation)
> gmake[2]: *** [proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/build.make:96: 
> proton-c/src/tests/c-ssl-tests] Error 1
> gmake[1]: *** [CMakeFiles/Makefile2:2436: 
> proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all] Error 2
> gmake: *** [Makefile:141: all] Error 2
> earth:153 rkieley$
> {code}
> Note that I also had disabled the bindings as well as set SASL_IMPL to none.



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

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

[GitHub] qpid-proton issue #131: PROTON-1711: SSL_IMPL none SASL_IMPL none build atte...

[astitcher]

Github user astitcher commented on the issue:

https://github.com/apache/qpid-proton/pull/131
  
@RoddieKieley  I've fixed this issue now - can you close the PR (stupidly I 
forgot to add that to the commit).


---

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

[jira] [Resolved] (PROTON-1711) SSL_IMPL none SASL_IMPL none build attempts to build c-ssl-tests and fails

[Andrew Stitcher (JIRA)]

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

Andrew Stitcher resolved PROTON-1711.
-
   Resolution: Fixed
Fix Version/s: proton-c-0.19.0

> SSL_IMPL none SASL_IMPL none build attempts to build c-ssl-tests and fails
> --
>
> Key: PROTON-1711
> URL: https://issues.apache.org/jira/browse/PROTON-1711
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
> Environment: Fedora 25
> OSX 10.11.6
>Reporter: Roddie Kieley
>Assignee: Andrew Stitcher
> Fix For: proton-c-0.19.0
>
>
> When building a default build via 'cmake ../qpid-proton' everything builds as 
> expected. However after using 'ccmake ../qpid-proton' and setting SSL_IMPL to 
> none we see:
> Fedora 25
> {code}
> .
> .
> .
> [ 76%] Linking C executable c-data-tests
> [ 76%] Built target c-data-tests
> [ 77%] Building C object proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/ssl.c.o
> [ 77%] Linking C executable c-ssl-tests
> CMakeFiles/c-ssl-tests.dir/ssl.c.o: In function `test_ssl_protocols':
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:29:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:31:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:33:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:36:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:37:
>  undefined reference to `pn_ssl_domain_set_protocols'
> CMakeFiles/c-ssl-tests.dir/ssl.c.o:/home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:38:
>  more undefined references to `pn_ssl_domain_set_protocols' follow
> collect2: error: ld returned 1 exit status
> proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/build.make:95: recipe for 
> target 'proton-c/src/tests/c-ssl-tests' failed
> gmake[2]: *** [proton-c/src/tests/c-ssl-tests] Error 1
> CMakeFiles/Makefile2:2435: recipe for target 
> 'proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all' failed
> gmake[1]: *** [proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all] Error 2
> Makefile:140: recipe for target 'all' failed
> gmake: *** [all] Error 2
> [rkieley@i7t450s 6]$
> {code}
> OSX 10.11.6
> {code}
> .
> .
> .
> [ 76%] Building C object 
> proton-c/src/tests/CMakeFiles/c-engine-tests.dir/engine.c.o
> [ 76%] Linking C executable c-engine-tests
> [ 76%] Built target c-engine-tests
> [ 77%] Building C object proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/ssl.c.o
> [ 77%] Linking C executable c-ssl-tests
> Undefined symbols for architecture x86_64:
>   "_pn_ssl_domain_set_protocols", referenced from:
>   _test_ssl_protocols in ssl.c.o
> ld: symbol(s) not found for architecture x86_64
> clang: error: linker command failed with exit code 1 (use -v to see 
> invocation)
> gmake[2]: *** [proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/build.make:96: 
> proton-c/src/tests/c-ssl-tests] Error 1
> gmake[1]: *** [CMakeFiles/Makefile2:2436: 
> proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all] Error 2
> gmake: *** [Makefile:141: all] Error 2
> earth:153 rkieley$
> {code}
> Note that I also had disabled the bindings as well as set SASL_IMPL to none.



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

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

[jira] [Commented] (DISPATCH-884) Add schema property to allow configurable TLS protocol versions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on DISPATCH-884:
-

Github user ssorj commented on a diff in the pull request:

https://github.com/apache/qpid-dispatch/pull/224#discussion_r155647815
  
--- Diff: src/connection_manager.c ---
@@ -45,6 +45,7 @@ struct qd_config_ssl_profile_t {
 char*ssl_certificate_file;
 char*ssl_private_key_file;
 char*ciphers;
+char*protocols;
--- End diff --

*ssl_protocols?


> Add schema property to allow configurable TLS protocol versions
> ---
>
> Key: DISPATCH-884
> URL: https://issues.apache.org/jira/browse/DISPATCH-884
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Container
>Affects Versions: 1.1.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
> Fix For: 1.1.0
>
>




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

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

[jira] [Assigned] (PROTON-1711) SSL_IMPL none SASL_IMPL none build attempts to build c-ssl-tests and fails

[Andrew Stitcher (JIRA)]

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

Andrew Stitcher reassigned PROTON-1711:
---

Assignee: Andrew Stitcher

> SSL_IMPL none SASL_IMPL none build attempts to build c-ssl-tests and fails
> --
>
> Key: PROTON-1711
> URL: https://issues.apache.org/jira/browse/PROTON-1711
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
> Environment: Fedora 25
> OSX 10.11.6
>Reporter: Roddie Kieley
>Assignee: Andrew Stitcher
>
> When building a default build via 'cmake ../qpid-proton' everything builds as 
> expected. However after using 'ccmake ../qpid-proton' and setting SSL_IMPL to 
> none we see:
> Fedora 25
> {code}
> .
> .
> .
> [ 76%] Linking C executable c-data-tests
> [ 76%] Built target c-data-tests
> [ 77%] Building C object proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/ssl.c.o
> [ 77%] Linking C executable c-ssl-tests
> CMakeFiles/c-ssl-tests.dir/ssl.c.o: In function `test_ssl_protocols':
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:29:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:31:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:33:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:36:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:37:
>  undefined reference to `pn_ssl_domain_set_protocols'
> CMakeFiles/c-ssl-tests.dir/ssl.c.o:/home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:38:
>  more undefined references to `pn_ssl_domain_set_protocols' follow
> collect2: error: ld returned 1 exit status
> proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/build.make:95: recipe for 
> target 'proton-c/src/tests/c-ssl-tests' failed
> gmake[2]: *** [proton-c/src/tests/c-ssl-tests] Error 1
> CMakeFiles/Makefile2:2435: recipe for target 
> 'proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all' failed
> gmake[1]: *** [proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all] Error 2
> Makefile:140: recipe for target 'all' failed
> gmake: *** [all] Error 2
> [rkieley@i7t450s 6]$
> {code}
> OSX 10.11.6
> {code}
> .
> .
> .
> [ 76%] Building C object 
> proton-c/src/tests/CMakeFiles/c-engine-tests.dir/engine.c.o
> [ 76%] Linking C executable c-engine-tests
> [ 76%] Built target c-engine-tests
> [ 77%] Building C object proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/ssl.c.o
> [ 77%] Linking C executable c-ssl-tests
> Undefined symbols for architecture x86_64:
>   "_pn_ssl_domain_set_protocols", referenced from:
>   _test_ssl_protocols in ssl.c.o
> ld: symbol(s) not found for architecture x86_64
> clang: error: linker command failed with exit code 1 (use -v to see 
> invocation)
> gmake[2]: *** [proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/build.make:96: 
> proton-c/src/tests/c-ssl-tests] Error 1
> gmake[1]: *** [CMakeFiles/Makefile2:2436: 
> proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all] Error 2
> gmake: *** [Makefile:141: all] Error 2
> earth:153 rkieley$
> {code}
> Note that I also had disabled the bindings as well as set SASL_IMPL to none.



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

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

[jira] [Commented] (DISPATCH-884) Add schema property to allow configurable TLS protocol versions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on DISPATCH-884:
-

Github user ssorj commented on a diff in the pull request:

https://github.com/apache/qpid-dispatch/pull/224#discussion_r155649659
  
--- Diff: include/qpid/dispatch/server.h ---
@@ -305,6 +305,12 @@ typedef struct qd_server_config_t {
  */
 char *ciphers;
 
+/**
+ * This list is a space separated string of the allowed TLS protocols. 
The current possibilities are TLSv1 TLSv1.1 TLSv1.2.
+ * For example, if you want to permit only TLS V.1.1 and TLSv1.2, your 
value for the protocols would be TLSv1.1 TLSv1.2. If this attribute is not set, 
then all the TLS protocols are allowed.
--- End diff --

"TLS V.1.1" -> "TLSv1.1"


> Add schema property to allow configurable TLS protocol versions
> ---
>
> Key: DISPATCH-884
> URL: https://issues.apache.org/jira/browse/DISPATCH-884
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Container
>Affects Versions: 1.1.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
> Fix For: 1.1.0
>
>




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

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

[jira] [Commented] (DISPATCH-884) Add schema property to allow configurable TLS protocol versions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on DISPATCH-884:
-

Github user ssorj commented on a diff in the pull request:

https://github.com/apache/qpid-dispatch/pull/224#discussion_r155652198
  
--- Diff: include/qpid/dispatch/server.h ---
@@ -305,6 +305,12 @@ typedef struct qd_server_config_t {
  */
 char *ciphers;
 
+/**
+ * This list is a space separated string of the allowed TLS protocols. 
The current possibilities are TLSv1 TLSv1.1 TLSv1.2.
--- End diff --

A possible enhancement is to sub spaces for commas and document it as a 
comma-separated list.


> Add schema property to allow configurable TLS protocol versions
> ---
>
> Key: DISPATCH-884
> URL: https://issues.apache.org/jira/browse/DISPATCH-884
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Container
>Affects Versions: 1.1.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
> Fix For: 1.1.0
>
>




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

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

[jira] [Commented] (DISPATCH-884) Add schema property to allow configurable TLS protocol versions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on DISPATCH-884:
-

Github user ssorj commented on a diff in the pull request:

https://github.com/apache/qpid-dispatch/pull/224#discussion_r155651659
  
--- Diff: python/qpid_dispatch/management/qdrouter.json ---
@@ -515,7 +515,12 @@
 "type": "string",
 "description": "Specifies the enabled ciphers so the 
SSL Ciphers can be hardened. In other words, use this field to disable weak 
ciphers. The ciphers are specified in the format understood by the OpenSSL 
library. For example, ciphers can be set to 
ALL:!aNULL:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP; -- The full list 
of allowed ciphers can be viewed using the openssl ciphers command",
 "create": true
-},
+},  
+"protocols": {
+"type": "string",
+"description": "This list is a space separated string 
of the allowed TLS protocols. The current possibilities are TLSv1 TLSv1.1 
TLSv1.2. For example, if you want to permit only TLS V.1.1 and TLSv1.2, your 
value for the protocols would be TLSv1.1 TLSv1.2. If this attribute is not set, 
then all the TLS protocols are allowed.",
--- End diff --

"then all the protocols are allowed" is not quite right.  If unset, it 
defers to the system-wide configuration.


> Add schema property to allow configurable TLS protocol versions
> ---
>
> Key: DISPATCH-884
> URL: https://issues.apache.org/jira/browse/DISPATCH-884
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Container
>Affects Versions: 1.1.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
> Fix For: 1.1.0
>
>




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

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

[jira] [Commented] (DISPATCH-884) Add schema property to allow configurable TLS protocol versions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on DISPATCH-884:
-

Github user ssorj commented on a diff in the pull request:

https://github.com/apache/qpid-dispatch/pull/224#discussion_r155647744
  
--- Diff: src/connection_manager.c ---
@@ -45,6 +45,7 @@ struct qd_config_ssl_profile_t {
 char*ssl_certificate_file;
 char*ssl_private_key_file;
 char*ciphers;
--- End diff --

*ssl_ciphers?


> Add schema property to allow configurable TLS protocol versions
> ---
>
> Key: DISPATCH-884
> URL: https://issues.apache.org/jira/browse/DISPATCH-884
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Container
>Affects Versions: 1.1.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
> Fix For: 1.1.0
>
>




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

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

[GitHub] qpid-dispatch pull request #224: DISPATCH-884 - Added schema property protoc...

[ssorj]

Github user ssorj commented on a diff in the pull request:

https://github.com/apache/qpid-dispatch/pull/224#discussion_r155647815
  
--- Diff: src/connection_manager.c ---
@@ -45,6 +45,7 @@ struct qd_config_ssl_profile_t {
 char*ssl_certificate_file;
 char*ssl_private_key_file;
 char*ciphers;
+char*protocols;
--- End diff --

*ssl_protocols?


---

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

[GitHub] qpid-dispatch pull request #224: DISPATCH-884 - Added schema property protoc...

[ssorj]

Github user ssorj commented on a diff in the pull request:

https://github.com/apache/qpid-dispatch/pull/224#discussion_r155652198
  
--- Diff: include/qpid/dispatch/server.h ---
@@ -305,6 +305,12 @@ typedef struct qd_server_config_t {
  */
 char *ciphers;
 
+/**
+ * This list is a space separated string of the allowed TLS protocols. 
The current possibilities are TLSv1 TLSv1.1 TLSv1.2.
--- End diff --

A possible enhancement is to sub spaces for commas and document it as a 
comma-separated list.


---

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

[GitHub] qpid-dispatch pull request #224: DISPATCH-884 - Added schema property protoc...

[ssorj]

Github user ssorj commented on a diff in the pull request:

https://github.com/apache/qpid-dispatch/pull/224#discussion_r155651659
  
--- Diff: python/qpid_dispatch/management/qdrouter.json ---
@@ -515,7 +515,12 @@
 "type": "string",
 "description": "Specifies the enabled ciphers so the 
SSL Ciphers can be hardened. In other words, use this field to disable weak 
ciphers. The ciphers are specified in the format understood by the OpenSSL 
library. For example, ciphers can be set to 
ALL:!aNULL:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP; -- The full list 
of allowed ciphers can be viewed using the openssl ciphers command",
 "create": true
-},
+},  
+"protocols": {
+"type": "string",
+"description": "This list is a space separated string 
of the allowed TLS protocols. The current possibilities are TLSv1 TLSv1.1 
TLSv1.2. For example, if you want to permit only TLS V.1.1 and TLSv1.2, your 
value for the protocols would be TLSv1.1 TLSv1.2. If this attribute is not set, 
then all the TLS protocols are allowed.",
--- End diff --

"then all the protocols are allowed" is not quite right.  If unset, it 
defers to the system-wide configuration.


---

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

[GitHub] qpid-dispatch pull request #224: DISPATCH-884 - Added schema property protoc...

[ssorj]

Github user ssorj commented on a diff in the pull request:

https://github.com/apache/qpid-dispatch/pull/224#discussion_r155647744
  
--- Diff: src/connection_manager.c ---
@@ -45,6 +45,7 @@ struct qd_config_ssl_profile_t {
 char*ssl_certificate_file;
 char*ssl_private_key_file;
 char*ciphers;
--- End diff --

*ssl_ciphers?


---

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

[GitHub] qpid-dispatch pull request #224: DISPATCH-884 - Added schema property protoc...

[ssorj]

Github user ssorj commented on a diff in the pull request:

https://github.com/apache/qpid-dispatch/pull/224#discussion_r155649659
  
--- Diff: include/qpid/dispatch/server.h ---
@@ -305,6 +305,12 @@ typedef struct qd_server_config_t {
  */
 char *ciphers;
 
+/**
+ * This list is a space separated string of the allowed TLS protocols. 
The current possibilities are TLSv1 TLSv1.1 TLSv1.2.
+ * For example, if you want to permit only TLS V.1.1 and TLSv1.2, your 
value for the protocols would be TLSv1.1 TLSv1.2. If this attribute is not set, 
then all the TLS protocols are allowed.
--- End diff --

"TLS V.1.1" -> "TLSv1.1"


---

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

Re: Proposal to create Docker images for Qpid components.

[Ken Giusti]

Hey!

Just following up on this thread.  What's the status?

thanks,

-K

On Tue, Jul 11, 2017 at 11:27 AM, Robbie Gemmell
 wrote:
> On 29 June 2017 at 17:52, Irina Boverman  wrote:
>> Thank you all who thoughtfully responded to this proposal. This is a
>> summary as I understood it and my comments regarding these points.
>>
>> (1) Qpid community is in favour of creating and maintaining docker images
>> for cpp/java brokers
>> and dispatch router. OS choice is less important, as long as the user can
>> connect to the broker/router port. We only need to support one OS choice.
>>
>> I think this is a good start. It covers a use case when someone wants to
>> test or deploy client apps against broker/router conveniently running as a
>> docker service.
>>
>> I think there might be another use case for those users who want to develop
>> client apps in a known environment with client libraries already installed
>> for them to work with. I think the OS choice is important to these users
>> because they may have a preference/better knowledge of this particular OS.
>> Please consider this use case.
>>
>> (2) Docker images should be of minimal size.
>>
>> As a concept, I fully agree with it. However, community support for
>> official images also makes sense to me. These images go through review and
>> testing, as well as, get patches for CVEs. There is a whole infrastructure
>> in place in Fedora to build docker images, etc following best practices
>> from OCI.
>>
>> Official images range in size between 120 to 200 mb, and have 10+ mil of
>> downloads, so the size does not appear to be an obstacle to adopting them.
>> It is my opinion that future official images will evolve to be better
>> aligned with how they are used, for example "server" and "workstation", etc.
>>
>> REPOSITORY  TAG IMAGE ID
>> CREATED SIZE
>> docker.io/ubuntulatest  ebcd9d4fca80
>> 6 weeks ago 117.9 MB
>> docker.io/debianlatest  e5599115b6a6
>> 5 months ago123 MB
>> docker.io/centoslatest  67591570dd29
>> 6 months ago191.8 MB
>> docker.io/fedoralatest  a1e614f0f30e
>> 6 months ago197.1 MB
>>
>> We can also modify the base image to remove some items if we think they are
>> not needed.
>>
>
> I think using a base OS image is fine, and your text and Justin's link
> suggests there are likely to be improvements in some regards in this
> area too. There is also nothing stopping a further image as minimal
> size option based on Alpine etc, but obviously components would need
> to work and be supported there first and it wasn't clear that is
> currently always true.
>
>> My personal preference is to start with fedora image because this
>> distribution has latest upstream releases for qpid packages, and I am the
>> maintainer for a number of these packages.
>
> I think we possibly need some clarity around the end result here, as
> it could strongly influence this particular area.
>
> For images to be considered 'official' Apache Qpid artifacts
> maintained directly by the project, they and their Qpid related
> contents would really need to be fully managed in concert with the
> projects release process. For example, if such an image were utilising
> packages to incorporate their relevant Qpid bits then I think it
> follows those packages would similarly need to be considered
> 'official' and handled similarly. Utilising the Qpid packages from
> Fedora distributions for example, wouldn't be appropriate in an
> 'official Apache Qpid' image since they are not directly managed
> artifacts of the Apache Qpid project.
>
> There wouldn't be an issue in simply considering such images to be a
> community-created convenience binaries based on the projects source
> release, as e.g. the existing Fedora packages themselves already are,
> but they wouldn't be considered 'official' Apache Qpid artifacts. It
> is worth saying this isn't particularly unusual, for example httpd
> direct people to their source releases but do reference various third
> party binaries for Windows users, and don't seem to be involved with
> the docker images for httpd, with members of the docker community
> instead handling that.
>
> I think either approach works here, having distribution based packages
> obviously has certain advantages for users and the project, so its
> probably more of a question around what people are actually expecting
> and/or looking to contribute towards here.
>
>> Fedora community is also working on its own docker registry (it will have
>> stable and test registries), has koji support for building images and
>> guidelines for naming and versioning them.
>>
>> (3). What upstream releases will be dockerised?
>>
>> I would like to propose to start with latest released version. We will
>> maintain at most 1 version 

[jira] [Commented] (PROTON-1711) SSL_IMPL none SASL_IMPL none build attempts to build c-ssl-tests and fails

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PROTON-1711:


Github user astitcher commented on the issue:

https://github.com/apache/qpid-proton/pull/131
  
Oops - I guess I did that when I added in the ssl tests.


> SSL_IMPL none SASL_IMPL none build attempts to build c-ssl-tests and fails
> --
>
> Key: PROTON-1711
> URL: https://issues.apache.org/jira/browse/PROTON-1711
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
> Environment: Fedora 25
> OSX 10.11.6
>Reporter: Roddie Kieley
>
> When building a default build via 'cmake ../qpid-proton' everything builds as 
> expected. However after using 'ccmake ../qpid-proton' and setting SSL_IMPL to 
> none we see:
> Fedora 25
> {code}
> .
> .
> .
> [ 76%] Linking C executable c-data-tests
> [ 76%] Built target c-data-tests
> [ 77%] Building C object proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/ssl.c.o
> [ 77%] Linking C executable c-ssl-tests
> CMakeFiles/c-ssl-tests.dir/ssl.c.o: In function `test_ssl_protocols':
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:29:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:31:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:33:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:36:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:37:
>  undefined reference to `pn_ssl_domain_set_protocols'
> CMakeFiles/c-ssl-tests.dir/ssl.c.o:/home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:38:
>  more undefined references to `pn_ssl_domain_set_protocols' follow
> collect2: error: ld returned 1 exit status
> proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/build.make:95: recipe for 
> target 'proton-c/src/tests/c-ssl-tests' failed
> gmake[2]: *** [proton-c/src/tests/c-ssl-tests] Error 1
> CMakeFiles/Makefile2:2435: recipe for target 
> 'proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all' failed
> gmake[1]: *** [proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all] Error 2
> Makefile:140: recipe for target 'all' failed
> gmake: *** [all] Error 2
> [rkieley@i7t450s 6]$
> {code}
> OSX 10.11.6
> {code}
> .
> .
> .
> [ 76%] Building C object 
> proton-c/src/tests/CMakeFiles/c-engine-tests.dir/engine.c.o
> [ 76%] Linking C executable c-engine-tests
> [ 76%] Built target c-engine-tests
> [ 77%] Building C object proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/ssl.c.o
> [ 77%] Linking C executable c-ssl-tests
> Undefined symbols for architecture x86_64:
>   "_pn_ssl_domain_set_protocols", referenced from:
>   _test_ssl_protocols in ssl.c.o
> ld: symbol(s) not found for architecture x86_64
> clang: error: linker command failed with exit code 1 (use -v to see 
> invocation)
> gmake[2]: *** [proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/build.make:96: 
> proton-c/src/tests/c-ssl-tests] Error 1
> gmake[1]: *** [CMakeFiles/Makefile2:2436: 
> proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all] Error 2
> gmake: *** [Makefile:141: all] Error 2
> earth:153 rkieley$
> {code}
> Note that I also had disabled the bindings as well as set SASL_IMPL to none.



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

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

[jira] [Commented] (PROTON-1711) SSL_IMPL none SASL_IMPL none build attempts to build c-ssl-tests and fails

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PROTON-1711:


Github user astitcher commented on the issue:

https://github.com/apache/qpid-proton/pull/131
  
The tests should still pass if SSL_IMPL is none as there is a stub 
implementation. If not then we need to fix that bug.


> SSL_IMPL none SASL_IMPL none build attempts to build c-ssl-tests and fails
> --
>
> Key: PROTON-1711
> URL: https://issues.apache.org/jira/browse/PROTON-1711
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
> Environment: Fedora 25
> OSX 10.11.6
>Reporter: Roddie Kieley
>
> When building a default build via 'cmake ../qpid-proton' everything builds as 
> expected. However after using 'ccmake ../qpid-proton' and setting SSL_IMPL to 
> none we see:
> Fedora 25
> {code}
> .
> .
> .
> [ 76%] Linking C executable c-data-tests
> [ 76%] Built target c-data-tests
> [ 77%] Building C object proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/ssl.c.o
> [ 77%] Linking C executable c-ssl-tests
> CMakeFiles/c-ssl-tests.dir/ssl.c.o: In function `test_ssl_protocols':
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:29:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:31:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:33:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:36:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:37:
>  undefined reference to `pn_ssl_domain_set_protocols'
> CMakeFiles/c-ssl-tests.dir/ssl.c.o:/home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:38:
>  more undefined references to `pn_ssl_domain_set_protocols' follow
> collect2: error: ld returned 1 exit status
> proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/build.make:95: recipe for 
> target 'proton-c/src/tests/c-ssl-tests' failed
> gmake[2]: *** [proton-c/src/tests/c-ssl-tests] Error 1
> CMakeFiles/Makefile2:2435: recipe for target 
> 'proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all' failed
> gmake[1]: *** [proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all] Error 2
> Makefile:140: recipe for target 'all' failed
> gmake: *** [all] Error 2
> [rkieley@i7t450s 6]$
> {code}
> OSX 10.11.6
> {code}
> .
> .
> .
> [ 76%] Building C object 
> proton-c/src/tests/CMakeFiles/c-engine-tests.dir/engine.c.o
> [ 76%] Linking C executable c-engine-tests
> [ 76%] Built target c-engine-tests
> [ 77%] Building C object proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/ssl.c.o
> [ 77%] Linking C executable c-ssl-tests
> Undefined symbols for architecture x86_64:
>   "_pn_ssl_domain_set_protocols", referenced from:
>   _test_ssl_protocols in ssl.c.o
> ld: symbol(s) not found for architecture x86_64
> clang: error: linker command failed with exit code 1 (use -v to see 
> invocation)
> gmake[2]: *** [proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/build.make:96: 
> proton-c/src/tests/c-ssl-tests] Error 1
> gmake[1]: *** [CMakeFiles/Makefile2:2436: 
> proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all] Error 2
> gmake: *** [Makefile:141: all] Error 2
> earth:153 rkieley$
> {code}
> Note that I also had disabled the bindings as well as set SASL_IMPL to none.



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

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

[GitHub] qpid-proton issue #131: PROTON-1711: SSL_IMPL none SASL_IMPL none build atte...

[astitcher]

Github user astitcher commented on the issue:

https://github.com/apache/qpid-proton/pull/131
  
Oops - I guess I did that when I added in the ssl tests.


---

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

[GitHub] qpid-proton issue #131: PROTON-1711: SSL_IMPL none SASL_IMPL none build atte...

[astitcher]

Github user astitcher commented on the issue:

https://github.com/apache/qpid-proton/pull/131
  
The tests should still pass if SSL_IMPL is none as there is a stub 
implementation. If not then we need to fix that bug.


---

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

[jira] [Updated] (PROTON-1477) Problem building qpid-proton 0.17.0 in Fedora rawhide

[Justin Ross (JIRA)]

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

Justin Ross updated PROTON-1477:

Fix Version/s: (was: proton-c-0.19.0)

> Problem building qpid-proton 0.17.0 in Fedora rawhide
> -
>
> Key: PROTON-1477
> URL: https://issues.apache.org/jira/browse/PROTON-1477
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: build
> Environment: x86_64
>Reporter: Irina Boverman
>Assignee: Justin Ross
>
> [ 39%] Swig source
> cd /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl && 
> /usr/bin/cmake -E make_directory 
> /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl
> make[2]: Leaving directory '/builddir/build/BUILD/qpid-proton-0.17.0'
> cd /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl && 
> /usr/bin/swig -perl -outdir 
> /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl -shadow 
> -I/builddir/build/BUILD/qpid-proton-0.17.0/proton-c/src 
> -I/builddir/build/BUILD/qpid-proton-0.17.0/proton-c/include -I/usr/include 
> -I/usr/lib64/perl5/CORE -o 
> /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl/perlPERL_wrap.c
>  /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl/perl.i
> make[2]: Leaving directory '/builddir/build/BUILD/qpid-proton-0.17.0'
> cc1plus: error: -Wformat-security ignored without -Wformat 
> [-Werror=format-security]
> cc1plus: all warnings being treated as errors
> make[2]: *** 
> [proton-c/bindings/cpp/CMakeFiles/qpid-proton-cpp.dir/build.make:66: 
> proton-c/bindings/cpp/CMakeFiles/qpid-proton-cpp.dir/src/binary.cpp.o] Error 1



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

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

[jira] [Closed] (PROTON-1477) Problem building qpid-proton 0.17.0 in Fedora rawhide

[Justin Ross (JIRA)]

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

Justin Ross closed PROTON-1477.
---

> Problem building qpid-proton 0.17.0 in Fedora rawhide
> -
>
> Key: PROTON-1477
> URL: https://issues.apache.org/jira/browse/PROTON-1477
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: build
> Environment: x86_64
>Reporter: Irina Boverman
>Assignee: Justin Ross
>
> [ 39%] Swig source
> cd /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl && 
> /usr/bin/cmake -E make_directory 
> /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl
> make[2]: Leaving directory '/builddir/build/BUILD/qpid-proton-0.17.0'
> cd /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl && 
> /usr/bin/swig -perl -outdir 
> /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl -shadow 
> -I/builddir/build/BUILD/qpid-proton-0.17.0/proton-c/src 
> -I/builddir/build/BUILD/qpid-proton-0.17.0/proton-c/include -I/usr/include 
> -I/usr/lib64/perl5/CORE -o 
> /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl/perlPERL_wrap.c
>  /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl/perl.i
> make[2]: Leaving directory '/builddir/build/BUILD/qpid-proton-0.17.0'
> cc1plus: error: -Wformat-security ignored without -Wformat 
> [-Werror=format-security]
> cc1plus: all warnings being treated as errors
> make[2]: *** 
> [proton-c/bindings/cpp/CMakeFiles/qpid-proton-cpp.dir/build.make:66: 
> proton-c/bindings/cpp/CMakeFiles/qpid-proton-cpp.dir/src/binary.cpp.o] Error 1



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

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

[jira] [Resolved] (PROTON-1477) Problem building qpid-proton 0.17.0 in Fedora rawhide

[Irina Boverman (JIRA)]

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

Irina Boverman resolved PROTON-1477.

Resolution: Cannot Reproduce

> Problem building qpid-proton 0.17.0 in Fedora rawhide
> -
>
> Key: PROTON-1477
> URL: https://issues.apache.org/jira/browse/PROTON-1477
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: build
> Environment: x86_64
>Reporter: Irina Boverman
>Assignee: Justin Ross
> Fix For: proton-c-0.19.0
>
>
> [ 39%] Swig source
> cd /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl && 
> /usr/bin/cmake -E make_directory 
> /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl
> make[2]: Leaving directory '/builddir/build/BUILD/qpid-proton-0.17.0'
> cd /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl && 
> /usr/bin/swig -perl -outdir 
> /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl -shadow 
> -I/builddir/build/BUILD/qpid-proton-0.17.0/proton-c/src 
> -I/builddir/build/BUILD/qpid-proton-0.17.0/proton-c/include -I/usr/include 
> -I/usr/lib64/perl5/CORE -o 
> /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl/perlPERL_wrap.c
>  /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl/perl.i
> make[2]: Leaving directory '/builddir/build/BUILD/qpid-proton-0.17.0'
> cc1plus: error: -Wformat-security ignored without -Wformat 
> [-Werror=format-security]
> cc1plus: all warnings being treated as errors
> make[2]: *** 
> [proton-c/bindings/cpp/CMakeFiles/qpid-proton-cpp.dir/build.make:66: 
> proton-c/bindings/cpp/CMakeFiles/qpid-proton-cpp.dir/src/binary.cpp.o] Error 1



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

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

[jira] [Assigned] (PROTON-1690) JMH Benchmarks for baseline performance of Message encoding/decoding

[Robbie Gemmell (JIRA)]

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

Robbie Gemmell reassigned PROTON-1690:
--

Assignee: Robbie Gemmell

> JMH Benchmarks for baseline performance of Message encoding/decoding
> 
>
> Key: PROTON-1690
> URL: https://issues.apache.org/jira/browse/PROTON-1690
> Project: Qpid Proton
>  Issue Type: New Feature
>  Components: proton-j
>Reporter: Francesco Nigro
>Assignee: Robbie Gemmell
>Priority: Minor
>
> Using a standard and reliable tool to quantify the performances of critical 
> components would be useful to measure the effects of any changes in the 
> engine.
> Currently lo standard the facto for such measurements is JMH 
> (http://openjdk.java.net/projects/code-tools/jmh/) hence it is highly 
> desiderable to use it to avoid the JVM to perform un-wanted (ie unrealistic 
> in production uses) optimizations that could trick the results of any 
> handrolled measurements.



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

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

[jira] [Commented] (PROTON-1690) JMH Benchmarks for baseline performance of Message encoding/decoding

[ASF subversion and git services (JIRA)]

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

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

Commit 9f26806d8e015d0ed71d82f429be84bf55ec4aa9 in qpid-proton-j's branch 
refs/heads/master from [~gemmellr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton-j.git;h=9f26806 ]

PROTON-1690: add missing relativePath element to avoid build errors in some 
cases, fix formatting of error message and correct typo


> JMH Benchmarks for baseline performance of Message encoding/decoding
> 
>
> Key: PROTON-1690
> URL: https://issues.apache.org/jira/browse/PROTON-1690
> Project: Qpid Proton
>  Issue Type: New Feature
>  Components: proton-j
>Reporter: Francesco Nigro
>Priority: Minor
>
> Using a standard and reliable tool to quantify the performances of critical 
> components would be useful to measure the effects of any changes in the 
> engine.
> Currently lo standard the facto for such measurements is JMH 
> (http://openjdk.java.net/projects/code-tools/jmh/) hence it is highly 
> desiderable to use it to avoid the JVM to perform un-wanted (ie unrealistic 
> in production uses) optimizations that could trick the results of any 
> handrolled measurements.



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

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

[jira] [Commented] (PROTON-1708) [proton-j] Improve performance of proton-j codec

[ASF subversion and git services (JIRA)]

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

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

Commit c82762676a7863debcc140e512a17518fa4129ab in qpid-proton-j's branch 
refs/heads/master from [~gemmellr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton-j.git;h=c827626 ]

PROTON-1708: simplify the look-ahead for list entry types


> [proton-j] Improve performance of proton-j codec
> 
>
> Key: PROTON-1708
> URL: https://issues.apache.org/jira/browse/PROTON-1708
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-j
>Affects Versions: proton-j-0.23.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
> Fix For: proton-j-0.24.0
>
>
> Several areas in the proton-j codec can be improved to provide overall 
> improvements in both the encode and decode of AMQP types as well as reduce GC 
> overhead with reduction in allocations of intermediate and helper objects.



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

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

[jira] [Commented] (PROTON-1690) JMH Benchmarks for baseline performance of Message encoding/decoding

[ASF subversion and git services (JIRA)]

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

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

Commit 3b33dce01d472ceb93b8b55a1c7ca57909748fa0 in qpid-proton-j's branch 
refs/heads/master from [~gemmellr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton-j.git;h=3b33dce ]

PROTON-1690: merge PR for JMH based perf tests of specific encoding+decoding 
tasks

This closes #12


> JMH Benchmarks for baseline performance of Message encoding/decoding
> 
>
> Key: PROTON-1690
> URL: https://issues.apache.org/jira/browse/PROTON-1690
> Project: Qpid Proton
>  Issue Type: New Feature
>  Components: proton-j
>Reporter: Francesco Nigro
>Priority: Minor
>
> Using a standard and reliable tool to quantify the performances of critical 
> components would be useful to measure the effects of any changes in the 
> engine.
> Currently lo standard the facto for such measurements is JMH 
> (http://openjdk.java.net/projects/code-tools/jmh/) hence it is highly 
> desiderable to use it to avoid the JVM to perform un-wanted (ie unrealistic 
> in production uses) optimizations that could trick the results of any 
> handrolled measurements.



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

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

[jira] [Commented] (PROTON-1690) JMH Benchmarks for baseline performance of Message encoding/decoding

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PROTON-1690:


Github user asfgit closed the pull request at:

https://github.com/apache/qpid-proton-j/pull/12


> JMH Benchmarks for baseline performance of Message encoding/decoding
> 
>
> Key: PROTON-1690
> URL: https://issues.apache.org/jira/browse/PROTON-1690
> Project: Qpid Proton
>  Issue Type: New Feature
>  Components: proton-j
>Reporter: Francesco Nigro
>Priority: Minor
>
> Using a standard and reliable tool to quantify the performances of critical 
> components would be useful to measure the effects of any changes in the 
> engine.
> Currently lo standard the facto for such measurements is JMH 
> (http://openjdk.java.net/projects/code-tools/jmh/) hence it is highly 
> desiderable to use it to avoid the JVM to perform un-wanted (ie unrealistic 
> in production uses) optimizations that could trick the results of any 
> handrolled measurements.



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

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

[jira] [Commented] (PROTON-1690) JMH Benchmarks for baseline performance of Message encoding/decoding

[ASF subversion and git services (JIRA)]

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

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

Commit 1eecf25e10e8c6f18aeef2f31e115f5369749115 in qpid-proton-j's branch 
refs/heads/master from [~nigro@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton-j.git;h=1eecf25 ]

PROTON-1690 JMH Benchmarks for baseline performance of Message encoding/decoding


> JMH Benchmarks for baseline performance of Message encoding/decoding
> 
>
> Key: PROTON-1690
> URL: https://issues.apache.org/jira/browse/PROTON-1690
> Project: Qpid Proton
>  Issue Type: New Feature
>  Components: proton-j
>Reporter: Francesco Nigro
>Priority: Minor
>
> Using a standard and reliable tool to quantify the performances of critical 
> components would be useful to measure the effects of any changes in the 
> engine.
> Currently lo standard the facto for such measurements is JMH 
> (http://openjdk.java.net/projects/code-tools/jmh/) hence it is highly 
> desiderable to use it to avoid the JVM to perform un-wanted (ie unrealistic 
> in production uses) optimizations that could trick the results of any 
> handrolled measurements.



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

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

[jira] [Updated] (PROTON-1690) JMH Benchmarks for baseline performance of Message encoding/decoding

[Robbie Gemmell (JIRA)]

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

Robbie Gemmell updated PROTON-1690:
---
Fix Version/s: proton-j-0.24.0

> JMH Benchmarks for baseline performance of Message encoding/decoding
> 
>
> Key: PROTON-1690
> URL: https://issues.apache.org/jira/browse/PROTON-1690
> Project: Qpid Proton
>  Issue Type: New Feature
>  Components: proton-j
>Reporter: Francesco Nigro
>Assignee: Robbie Gemmell
>Priority: Minor
> Fix For: proton-j-0.24.0
>
>
> Using a standard and reliable tool to quantify the performances of critical 
> components would be useful to measure the effects of any changes in the 
> engine.
> Currently lo standard the facto for such measurements is JMH 
> (http://openjdk.java.net/projects/code-tools/jmh/) hence it is highly 
> desiderable to use it to avoid the JVM to perform un-wanted (ie unrealistic 
> in production uses) optimizations that could trick the results of any 
> handrolled measurements.



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

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

[GitHub] qpid-proton-j pull request #12: PROTON-1690 JMH Benchmarks for baseline perf...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/qpid-proton-j/pull/12


---

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

[jira] [Commented] (PROTON-1711) SSL_IMPL none SASL_IMPL none build attempts to build c-ssl-tests and fails

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PROTON-1711:


GitHub user RoddieKieley opened a pull request:

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

PROTON-1711: SSL_IMPL none SASL_IMPL none build attempts to build c-s…

…sl-tests and fails

Added simple check to only build c-ssl-tests if SSL_IMPL was not none.

NOTE: This simple change also exposes the fact that the python binding does 
not build with SSL_IMPL none and all other configuration variables default at 
the moment. I disabled the python binding for a successful build as I didn't 
need it at the moment.

Should be addressed here or via separate issue?

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/RoddieKieley/qpid-proton PROTON-1711

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-proton/pull/131.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #131


commit 84f2ae514606fb69e6f985f911d4a966c20fc75a
Author: circleci 
Date:   2017-12-07T15:28:07Z

PROTON-1711: SSL_IMPL none SASL_IMPL none build attempts to build 
c-ssl-tests and fails

Added simple check to only build c-ssl-tests if SSL_IMPL was not none.




> SSL_IMPL none SASL_IMPL none build attempts to build c-ssl-tests and fails
> --
>
> Key: PROTON-1711
> URL: https://issues.apache.org/jira/browse/PROTON-1711
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
> Environment: Fedora 25
> OSX 10.11.6
>Reporter: Roddie Kieley
>
> When building a default build via 'cmake ../qpid-proton' everything builds as 
> expected. However after using 'ccmake ../qpid-proton' and setting SSL_IMPL to 
> none we see:
> Fedora 25
> {code}
> .
> .
> .
> [ 76%] Linking C executable c-data-tests
> [ 76%] Built target c-data-tests
> [ 77%] Building C object proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/ssl.c.o
> [ 77%] Linking C executable c-ssl-tests
> CMakeFiles/c-ssl-tests.dir/ssl.c.o: In function `test_ssl_protocols':
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:29:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:31:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:33:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:36:
>  undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:37:
>  undefined reference to `pn_ssl_domain_set_protocols'
> CMakeFiles/c-ssl-tests.dir/ssl.c.o:/home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:38:
>  more undefined references to `pn_ssl_domain_set_protocols' follow
> collect2: error: ld returned 1 exit status
> proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/build.make:95: recipe for 
> target 'proton-c/src/tests/c-ssl-tests' failed
> gmake[2]: *** [proton-c/src/tests/c-ssl-tests] Error 1
> CMakeFiles/Makefile2:2435: recipe for target 
> 'proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all' failed
> gmake[1]: *** [proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all] Error 2
> Makefile:140: recipe for target 'all' failed
> gmake: *** [all] Error 2
> [rkieley@i7t450s 6]$
> {code}
> OSX 10.11.6
> {code}
> .
> .
> .
> [ 76%] Building C object 
> proton-c/src/tests/CMakeFiles/c-engine-tests.dir/engine.c.o
> [ 76%] Linking C executable c-engine-tests
> [ 76%] Built target c-engine-tests
> [ 77%] Building C object proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/ssl.c.o
> [ 77%] Linking C executable c-ssl-tests
> Undefined symbols for architecture x86_64:
>   "_pn_ssl_domain_set_protocols", referenced from:
>   _test_ssl_protocols in ssl.c.o
> ld: symbol(s) not found for architecture x86_64
> clang: error: linker command failed with exit code 1 (use -v to see 
> invocation)
> gmake[2]: *** [proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/build.make:96: 
> proton-c/src/tests/c-ssl-tests] Error 1
> gmake[1]: *** [CMakeFiles/Makefile2:2436: 
> proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all] Error 2
> gmake: *** [Makefile:141: all] Error 2
> earth:153 rkieley$
> {code}
> Note that I also had disabled the bindings as well as set SASL_IMPL to none.



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

[GitHub] qpid-proton pull request #131: PROTON-1711: SSL_IMPL none SASL_IMPL none bui...

[RoddieKieley]

GitHub user RoddieKieley opened a pull request:

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

PROTON-1711: SSL_IMPL none SASL_IMPL none build attempts to build c-s…

…sl-tests and fails

Added simple check to only build c-ssl-tests if SSL_IMPL was not none.

NOTE: This simple change also exposes the fact that the python binding does 
not build with SSL_IMPL none and all other configuration variables default at 
the moment. I disabled the python binding for a successful build as I didn't 
need it at the moment.

Should be addressed here or via separate issue?

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/RoddieKieley/qpid-proton PROTON-1711

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-proton/pull/131.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #131


commit 84f2ae514606fb69e6f985f911d4a966c20fc75a
Author: circleci 
Date:   2017-12-07T15:28:07Z

PROTON-1711: SSL_IMPL none SASL_IMPL none build attempts to build 
c-ssl-tests and fails

Added simple check to only build c-ssl-tests if SSL_IMPL was not none.




---

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

[jira] [Commented] (DISPATCH-896) Update connections to use promises returned by latest dispatch-management

[ASF subversion and git services (JIRA)]

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

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

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

DISPATCH-896 Fix HTML errors on page


> Update connections to use promises returned by latest dispatch-management
> -
>
> Key: DISPATCH-896
> URL: https://issues.apache.org/jira/browse/DISPATCH-896
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Console
>Affects Versions: 1.0.0
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>Priority: Minor
>
> The npm library that wraps management commands for javascript clients has 
> been updated to use promises. The stand-alone console can be updated to use 
> these promises instead of callbacks. This simplifies the code a bit and makes 
> it more readable/mantainable.



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

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

[jira] [Commented] (DISPATCH-896) Update connections to use promises returned by latest dispatch-management

[ASF subversion and git services (JIRA)]

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

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

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

DISPATCH-896 Use promises to connect


> Update connections to use promises returned by latest dispatch-management
> -
>
> Key: DISPATCH-896
> URL: https://issues.apache.org/jira/browse/DISPATCH-896
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Console
>Affects Versions: 1.0.0
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>Priority: Minor
>
> The npm library that wraps management commands for javascript clients has 
> been updated to use promises. The stand-alone console can be updated to use 
> these promises instead of callbacks. This simplifies the code a bit and makes 
> it more readable/mantainable.



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

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

[jira] [Created] (DISPATCH-896) Update connections to use promises returned by latest dispatch-management

[Ernest Allen (JIRA)]

Ernest Allen created DISPATCH-896:
-

 Summary: Update connections to use promises returned by latest 
dispatch-management
 Key: DISPATCH-896
 URL: https://issues.apache.org/jira/browse/DISPATCH-896
 Project: Qpid Dispatch
  Issue Type: Improvement
  Components: Console
Affects Versions: 1.0.0
Reporter: Ernest Allen
Assignee: Ernest Allen
Priority: Minor


The npm library that wraps management commands for javascript clients has been 
updated to use promises. The stand-alone console can be updated to use these 
promises instead of callbacks. This simplifies the code a bit and makes it more 
readable/mantainable.



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

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

[jira] [Commented] (DISPATCH-895) qpid-dispatch crashes with a SEGFAULT in libqpid-proton

[ASF subversion and git services (JIRA)]

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

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

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

DISPATCH-895 - Check if underlying proton links are not closed before calling 
into proton. The underlying links/sessions on a connection are cleaned up 
silently by proton when a connection drops.


> qpid-dispatch crashes with a SEGFAULT in libqpid-proton
> ---
>
> Key: DISPATCH-895
> URL: https://issues.apache.org/jira/browse/DISPATCH-895
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Routing Engine
>Affects Versions: 0.8.0
> Environment: OS: Red Hat Enterprise Linux 7.4
> Arch: x86_64
> Installed Packages
> Name: qpid-cpp-client
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 4.4 M
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : Libraries for Qpid C++ client applications
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : Run-time libraries for AMQP client applications developed using 
> Qpid
> : C++. Clients exchange messages with an AMQP message broker using
> : the AMQP protocol.
> Name: qpid-cpp-server
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 5.2 M
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : An AMQP message broker daemon
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : A message broker daemon that receives stores and routes 
> messages using
> : the open AMQP messaging protocol.
> Name: qpid-cpp-server-linearstore
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 797 k
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : Red Hat persistence extension to the Qpid messaging sytem
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : Red Hat persistence extension to the Qpid AMQP broker: 
> persistent message
> : storage using a libaio-based asynchronous journal.
> Name: qpid-dispatch-debuginfo
> Arch: x86_64
> Version : 0.8.0
> Release : 10.el7
> Size: 2.1 M
> Repo: installed
> Summary : Debug information for package qpid-dispatch
> URL : http://qpid.apache.org/
> License : ASL 2.0
> Description : This package provides debug information for package 
> qpid-dispatch.
> : Debug information is useful when developing applications that 
> use this
> : package or when debugging this package.
> Name: qpid-dispatch-router
> Arch: x86_64
> Version : 0.8.0
> Release : 10.el7
> Size: 1.0 M
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : The Qpid Dispatch Router executable
> URL : http://qpid.apache.org/
> License : ASL 2.0
> Description : The Qpid Dispatch Router executable.
> Name: qpid-proton-c
> Arch: x86_64
> Version : 0.16.0
> Release : 7.el7
> Size: 334 k
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : C libraries for Qpid Proton
> URL : http://qpid.apache.org/proton/
> License : ASL 2.0
> Description : C libraries for Qpid Proton.
> Name: qpid-proton-debuginfo
> Arch: x86_64
> Version : 0.16.0
> Release : 7.el7
> Size: 6.8 M
> Repo: installed
> Summary : Debug information for package qpid-proton
> URL : http://qpid.apache.org/proton/
> License : ASL 2.0
> Description : This package provides debug information for package qpid-proton.
> : Debug information is useful when developing applications that 
> use this
> : package or when debugging this package.
> Name: qpid-qmf
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 476 k
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : The QPID Management Framework
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : The Qpid Management Framework is a general-purpose management 
> bus built on Qpid
> : messaging. It takes advantage of the scalability, security, and 
> rich
> : capabilities of Qpid to provide flexible and easy-to-use 
> manageability to a
> : large set of applications.
> Name

[jira] [Resolved] (DISPATCH-895) qpid-dispatch crashes with a SEGFAULT in libqpid-proton

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy resolved DISPATCH-895.

Resolution: Fixed

> qpid-dispatch crashes with a SEGFAULT in libqpid-proton
> ---
>
> Key: DISPATCH-895
> URL: https://issues.apache.org/jira/browse/DISPATCH-895
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Routing Engine
>Affects Versions: 0.8.0
> Environment: OS: Red Hat Enterprise Linux 7.4
> Arch: x86_64
> Installed Packages
> Name: qpid-cpp-client
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 4.4 M
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : Libraries for Qpid C++ client applications
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : Run-time libraries for AMQP client applications developed using 
> Qpid
> : C++. Clients exchange messages with an AMQP message broker using
> : the AMQP protocol.
> Name: qpid-cpp-server
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 5.2 M
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : An AMQP message broker daemon
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : A message broker daemon that receives stores and routes 
> messages using
> : the open AMQP messaging protocol.
> Name: qpid-cpp-server-linearstore
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 797 k
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : Red Hat persistence extension to the Qpid messaging sytem
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : Red Hat persistence extension to the Qpid AMQP broker: 
> persistent message
> : storage using a libaio-based asynchronous journal.
> Name: qpid-dispatch-debuginfo
> Arch: x86_64
> Version : 0.8.0
> Release : 10.el7
> Size: 2.1 M
> Repo: installed
> Summary : Debug information for package qpid-dispatch
> URL : http://qpid.apache.org/
> License : ASL 2.0
> Description : This package provides debug information for package 
> qpid-dispatch.
> : Debug information is useful when developing applications that 
> use this
> : package or when debugging this package.
> Name: qpid-dispatch-router
> Arch: x86_64
> Version : 0.8.0
> Release : 10.el7
> Size: 1.0 M
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : The Qpid Dispatch Router executable
> URL : http://qpid.apache.org/
> License : ASL 2.0
> Description : The Qpid Dispatch Router executable.
> Name: qpid-proton-c
> Arch: x86_64
> Version : 0.16.0
> Release : 7.el7
> Size: 334 k
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : C libraries for Qpid Proton
> URL : http://qpid.apache.org/proton/
> License : ASL 2.0
> Description : C libraries for Qpid Proton.
> Name: qpid-proton-debuginfo
> Arch: x86_64
> Version : 0.16.0
> Release : 7.el7
> Size: 6.8 M
> Repo: installed
> Summary : Debug information for package qpid-proton
> URL : http://qpid.apache.org/proton/
> License : ASL 2.0
> Description : This package provides debug information for package qpid-proton.
> : Debug information is useful when developing applications that 
> use this
> : package or when debugging this package.
> Name: qpid-qmf
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 476 k
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : The QPID Management Framework
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : The Qpid Management Framework is a general-purpose management 
> bus built on Qpid
> : messaging. It takes advantage of the scalability, security, and 
> rich
> : capabilities of Qpid to provide flexible and easy-to-use 
> manageability to a
> : large set of applications.
> Name: qpid-tools
> Arch: noarch
> Version : 1.36.0
> Release : 9.el7
> Size: 384 k
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : Management and diagostic tools for Apache Qpid
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : Management and diagnostic tools for Apache Qpid brokers and 
> clients.
>Reporter: Saurabh Badhwar
>   

[jira] [Updated] (DISPATCH-895) qpid-dispatch crashes with a SEGFAULT in libqpid-proton

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy updated DISPATCH-895:
---
Fix Version/s: 1.1.0

> qpid-dispatch crashes with a SEGFAULT in libqpid-proton
> ---
>
> Key: DISPATCH-895
> URL: https://issues.apache.org/jira/browse/DISPATCH-895
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Routing Engine
>Affects Versions: 0.8.0
> Environment: OS: Red Hat Enterprise Linux 7.4
> Arch: x86_64
> Installed Packages
> Name: qpid-cpp-client
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 4.4 M
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : Libraries for Qpid C++ client applications
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : Run-time libraries for AMQP client applications developed using 
> Qpid
> : C++. Clients exchange messages with an AMQP message broker using
> : the AMQP protocol.
> Name: qpid-cpp-server
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 5.2 M
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : An AMQP message broker daemon
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : A message broker daemon that receives stores and routes 
> messages using
> : the open AMQP messaging protocol.
> Name: qpid-cpp-server-linearstore
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 797 k
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : Red Hat persistence extension to the Qpid messaging sytem
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : Red Hat persistence extension to the Qpid AMQP broker: 
> persistent message
> : storage using a libaio-based asynchronous journal.
> Name: qpid-dispatch-debuginfo
> Arch: x86_64
> Version : 0.8.0
> Release : 10.el7
> Size: 2.1 M
> Repo: installed
> Summary : Debug information for package qpid-dispatch
> URL : http://qpid.apache.org/
> License : ASL 2.0
> Description : This package provides debug information for package 
> qpid-dispatch.
> : Debug information is useful when developing applications that 
> use this
> : package or when debugging this package.
> Name: qpid-dispatch-router
> Arch: x86_64
> Version : 0.8.0
> Release : 10.el7
> Size: 1.0 M
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : The Qpid Dispatch Router executable
> URL : http://qpid.apache.org/
> License : ASL 2.0
> Description : The Qpid Dispatch Router executable.
> Name: qpid-proton-c
> Arch: x86_64
> Version : 0.16.0
> Release : 7.el7
> Size: 334 k
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : C libraries for Qpid Proton
> URL : http://qpid.apache.org/proton/
> License : ASL 2.0
> Description : C libraries for Qpid Proton.
> Name: qpid-proton-debuginfo
> Arch: x86_64
> Version : 0.16.0
> Release : 7.el7
> Size: 6.8 M
> Repo: installed
> Summary : Debug information for package qpid-proton
> URL : http://qpid.apache.org/proton/
> License : ASL 2.0
> Description : This package provides debug information for package qpid-proton.
> : Debug information is useful when developing applications that 
> use this
> : package or when debugging this package.
> Name: qpid-qmf
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 476 k
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : The QPID Management Framework
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : The Qpid Management Framework is a general-purpose management 
> bus built on Qpid
> : messaging. It takes advantage of the scalability, security, and 
> rich
> : capabilities of Qpid to provide flexible and easy-to-use 
> manageability to a
> : large set of applications.
> Name: qpid-tools
> Arch: noarch
> Version : 1.36.0
> Release : 9.el7
> Size: 384 k
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : Management and diagostic tools for Apache Qpid
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : Management and diagnostic tools for Apache Qpid brokers and 
> clients.
>Reporter: Saurabh Badhwar
>  

[jira] [Assigned] (DISPATCH-895) qpid-dispatch crashes with a SEGFAULT in libqpid-proton

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy reassigned DISPATCH-895:
--

Assignee: Ganesh Murthy

> qpid-dispatch crashes with a SEGFAULT in libqpid-proton
> ---
>
> Key: DISPATCH-895
> URL: https://issues.apache.org/jira/browse/DISPATCH-895
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Routing Engine
>Affects Versions: 0.8.0
> Environment: OS: Red Hat Enterprise Linux 7.4
> Arch: x86_64
> Installed Packages
> Name: qpid-cpp-client
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 4.4 M
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : Libraries for Qpid C++ client applications
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : Run-time libraries for AMQP client applications developed using 
> Qpid
> : C++. Clients exchange messages with an AMQP message broker using
> : the AMQP protocol.
> Name: qpid-cpp-server
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 5.2 M
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : An AMQP message broker daemon
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : A message broker daemon that receives stores and routes 
> messages using
> : the open AMQP messaging protocol.
> Name: qpid-cpp-server-linearstore
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 797 k
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : Red Hat persistence extension to the Qpid messaging sytem
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : Red Hat persistence extension to the Qpid AMQP broker: 
> persistent message
> : storage using a libaio-based asynchronous journal.
> Name: qpid-dispatch-debuginfo
> Arch: x86_64
> Version : 0.8.0
> Release : 10.el7
> Size: 2.1 M
> Repo: installed
> Summary : Debug information for package qpid-dispatch
> URL : http://qpid.apache.org/
> License : ASL 2.0
> Description : This package provides debug information for package 
> qpid-dispatch.
> : Debug information is useful when developing applications that 
> use this
> : package or when debugging this package.
> Name: qpid-dispatch-router
> Arch: x86_64
> Version : 0.8.0
> Release : 10.el7
> Size: 1.0 M
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : The Qpid Dispatch Router executable
> URL : http://qpid.apache.org/
> License : ASL 2.0
> Description : The Qpid Dispatch Router executable.
> Name: qpid-proton-c
> Arch: x86_64
> Version : 0.16.0
> Release : 7.el7
> Size: 334 k
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : C libraries for Qpid Proton
> URL : http://qpid.apache.org/proton/
> License : ASL 2.0
> Description : C libraries for Qpid Proton.
> Name: qpid-proton-debuginfo
> Arch: x86_64
> Version : 0.16.0
> Release : 7.el7
> Size: 6.8 M
> Repo: installed
> Summary : Debug information for package qpid-proton
> URL : http://qpid.apache.org/proton/
> License : ASL 2.0
> Description : This package provides debug information for package qpid-proton.
> : Debug information is useful when developing applications that 
> use this
> : package or when debugging this package.
> Name: qpid-qmf
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 476 k
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : The QPID Management Framework
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : The Qpid Management Framework is a general-purpose management 
> bus built on Qpid
> : messaging. It takes advantage of the scalability, security, and 
> rich
> : capabilities of Qpid to provide flexible and easy-to-use 
> manageability to a
> : large set of applications.
> Name: qpid-tools
> Arch: noarch
> Version : 1.36.0
> Release : 9.el7
> Size: 384 k
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : Management and diagostic tools for Apache Qpid
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : Management and diagnostic tools for Apache Qpid brokers and 
> clients.
>Reporter: Saurabh 

[jira] [Created] (QPIDJMS-349) JMS transactions should fail when messages are published into non-existinng destinations using anonymous producer

[Alex Rudyy (JIRA)]

Alex Rudyy created QPIDJMS-349:
--

 Summary: JMS transactions should fail when messages are published 
into non-existinng destinations using anonymous producer
 Key: QPIDJMS-349
 URL: https://issues.apache.org/jira/browse/QPIDJMS-349
 Project: Qpid JMS
  Issue Type: Bug
  Components: qpid-jms-client
Affects Versions: 0.27.0, 0.26.0, 0.25.0, 0.24.0
Reporter: Alex Rudyy


The current client implementation allows to commit JMS transaction 
successfully, when message is published into non-existing destination over 
anonymous relay within a transaction. Though, only part of the messages within 
the transaction reaches their destinations. This situation can potentially 
result in message loss, as the client application would consider such 
transaction successful. The exception {{"javax.jms.InvalidDestinationException: 
Unknown destination 'nonExistingQueue' [condition = amqp:not-found]"}} is 
reported into {{ExceptionListener}} but client allows to commit the JMS 
transaction successfully. If no {{ExceptionListener}} is set, the exception is 
logged. 

It seems, the JMS client is failing to deliver JMS transaction contract, when 
publishing messages using anonymous producer.  Atomicity (all or nothing) is 
not guaranteed in this case.

The following code snippet demonstrate the problem:
{code}
try( Connection connection =
connectionFactory.createConnection(username, password))
{
Session session = connection.createSession(true,
Session.SESSION_TRANSACTED);
MessageProducer messageProducer = session.createProducer(null);
Queue nonExistingQueue = session.createQueue("nonExistingQueue");
messageProducer.send(nonExistingQueue,
session.createTextMessage("testMessage"));
session.commit();
}
{code}

>From AMQP point of view both broker and client behaviours are fully AMQP 
>compliant.
The implementations conform the requirements of specification "Using the 
Anonymous Terminus for Message Routing" [1] as per section "2.2.2 Routing 
Errors" :
{quote}
If the source of the link supports the rejected outcome, and the message has 
not already been settled by the sender, then the routing node MUST reject the 
message.
{quote}

On attach, the client specifies the following outcomes on the source:
{noformat}
outcomes=[amqp:accepted:list,amqp:rejected:list,amqp:released:list,amqp:modified:list]}
{noformat}

When Broker receives a message for non-existing destination, the anonymous
relay implementation returns rejected outcome, as 'rejected' outcome is in the 
list of source supported outcomes. The Broker replies with settled disposition 
having rejected outcome and error 'not-found'. Here is an example of disposition
{noformat}
Disposition{role=receiver,first=1,last=1,settled=true,state=TransactionalState{txnId=\x00\x00\x00\x00,outcome=Rejected{error=Error{condition=not-found,description=Unknown
destination 'nonExistingQueue'
{noformat}

Thus, the AMQP transaction can be committed successfully in this case, as the 
message is settled and has final outcome.

I am wondering whether a better approach  would be to stop supporting 
"rejected" outcome for anonymous producer on transacted sessions. That would 
cause the broker to detach the link with an error and mark the transaction as 
rollback only. Thus, any commit issued from the client will fail in this case.

[1] 
https://www.oasis-open.org/apps/org/workgroup/amqp/download.php/61723/amqp-anonterm-v1.0-wd03.pdf



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

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

[jira] [Commented] (QPIDJMS-327) QPid JMS has no support for the content-type AMQP properties

[Robbie Gemmell (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPIDJMS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281688#comment-16281688
 ] 

Robbie Gemmell commented on QPIDJMS-327:


It isn't implemented as it was previously discussed that functionality, at 
least those specific vendor properties, would likely be removed from the 
mapping document and considered a detail for specific implementers, since it is 
not necessary for implementing JMS.

> QPid JMS has no support for the content-type AMQP properties
> 
>
> Key: QPIDJMS-327
> URL: https://issues.apache.org/jira/browse/QPIDJMS-327
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Reporter: Leo Riguspi
>
> The content-type AMQP property cannot be set. According to the specifications 
> it should be set via the Jms property JMS_AMQP_ContentType, however this 
> results in nothing being set.
> NOTE: there is a similar issue (albeit different) for the content-encoding 
> property (see [https://issues.apache.org/jira/browse/QPIDJMS-295])



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

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

[jira] [Assigned] (QPID-8061) [Broker-J] [AMQP 0-8..0-9-1] Decaring exchange with not existing alternate binding crashes the Broker

[Alex Rudyy (JIRA)]

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

Alex Rudyy reassigned QPID-8061:


Assignee: Keith Wall  (was: Alex Rudyy)

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

[jira] [Updated] (QPID-8061) [Broker-J] [AMQP 0-8..0-9-1] Declaring exchange with not existing alternate binding crashes the Broker

[Alex Rudyy (JIRA)]

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

Alex Rudyy updated QPID-8061:
-
Summary: [Broker-J] [AMQP 0-8..0-9-1] Declaring exchange with not existing 
alternate binding crashes the Broker  (was: [Broker-J] [AMQP 0-8..0-9-1] 
Decaring exchange with not existing alternate binding crashes the Broker)

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

[jira] [Assigned] (QPID-8060) [Broker-J] [AMQP 0-8..0-9-1] Declaring queue with not existing alternate binding crashes the Broker

[Alex Rudyy (JIRA)]

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

Alex Rudyy reassigned QPID-8060:


Assignee: Keith Wall  (was: Alex Rudyy)

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

[jira] [Updated] (QPID-8060) [Broker-J] [AMQP 0-8..0-9-1] Declaring queue with not existing alternate binding crashes the Broker

[Alex Rudyy (JIRA)]

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

Alex Rudyy updated QPID-8060:
-
Status: Reviewable  (was: In Progress)

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

[jira] [Assigned] (QPID-8061) [Broker-J] [AMQP 0-8..0-9-1] Decaring exchange with not existing alternate binding crashes the Broker

[Alex Rudyy (JIRA)]

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

Alex Rudyy reassigned QPID-8061:


Assignee: Alex Rudyy

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

[jira] [Updated] (QPID-8061) [Broker-J] [AMQP 0-8..0-9-1] Decaring exchange with not existing alternate binding crashes the Broker

[Alex Rudyy (JIRA)]

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

Alex Rudyy updated QPID-8061:
-
Status: Reviewable  (was: In Progress)

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

[jira] [Commented] (QPID-8061) [Broker-J] [AMQP 0-8..0-9-1] Decaring exchange with not existing alternate binding crashes the Broker

[ASF subversion and git services (JIRA)]

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

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

Commit 38c04f8cfa08e9552f83c7276aa32d4a427c3c5d in qpid-broker-j's branch 
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=38c04f8 ]

QPID-8061: [Broker-J] [AMQP 0-8..0-9-1] Handle unknown alternate exchange on 
exchange declaration


> [Broker-J] [AMQP 0-8..0-9-1] Decaring exchange with not existing alternate 
> binding crashes the Broker
> -
>
> Key: QPID-8061
> URL: https://issues.apache.org/jira/browse/QPID-8061
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
> Fix For: qpid-java-broker-7.0.1
>
>
> Declaration of exchange with not existing alternate binding crashes the 
> Broker as below:
> {noformat}
> org.apache.qpid.server.configuration.IllegalConfigurationException: Cannot 
> create alternate binding for 'test' : Alternate binding destination 
> 'not_existing' cannot be found.
>   at 
> org.apache.qpid.server.exchange.AbstractExchange.validateOrCreateAlternateBinding(AbstractExchange.java:1057)
>   at 
> org.apache.qpid.server.exchange.AbstractExchange.onCreate(AbstractExchange.java:192)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject.doCreation(AbstractConfiguredObject.java:1273)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:893)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:866)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:637)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:630)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submitWrappedTask(TaskExecutorImpl.java:165)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submit(TaskExecutorImpl.java:153)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject.doOnConfigThread(AbstractConfiguredObject.java:629)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject.createAsync(AbstractConfiguredObject.java:865)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObjectTypeFactory.createAsync(AbstractConfiguredObjectTypeFactory.java:75)
>   at 
> org.apache.qpid.server.model.ConfiguredObjectFactoryImpl.createAsync(ConfiguredObjectFactoryImpl.java:145)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject.addChildAsync(AbstractConfiguredObject.java:2143)
>   at 
> org.apache.qpid.server.virtualhost.AbstractVirtualHost.addChildAsync(AbstractVirtualHost.java:857)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2100)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2095)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:637)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:630)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:320)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:360)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:313)
>   at 
> com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:111)
>   at 
> com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:58)
>   at 
> com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:75)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.qpid.server.bytebuffer.QpidByteBufferFactory.lambda$null$0(QpidByteBufferFactory.java:464)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Client code:
> {code}
> 

[jira] [Commented] (QPID-8060) [Broker-J] [AMQP 0-8..0-9-1] Declaring queue with not existing alternate binding crashes the Broker

[ASF subversion and git services (JIRA)]

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

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

Commit 268f3fb68887208ce17987ed4d783e44073f9be8 in qpid-broker-j's branch 
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=268f3fb ]

QPID-8060: [Broker-J] [AMQP 0-8..0-9-1] Handle unknown alternate exchange on 
queue declaration


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

[jira] [Assigned] (QPID-8060) [Broker-J] [AMQP 0-8..0-9-1] Declaring queue with not existing alternate binding crashes the Broker

[Alex Rudyy (JIRA)]

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

Alex Rudyy reassigned QPID-8060:


Assignee: Alex Rudyy

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

[jira] [Updated] (QPID-8060) [Broker-J] [AMQP 0-8..0-9-1] Declaring queue with not existing alternate binding crashes the Broker

[Alex Rudyy (JIRA)]

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

Alex Rudyy updated QPID-8060:
-
Description: 
Declaring queue with not existing alternate binding crashes the Broker with the 
following stack trace:
{noformat}
org.apache.qpid.server.configuration.IllegalConfigurationException: Cannot 
create alternate binding for 'test' : Alternate binding destination 
'not_existing' cannot be found.
at 
org.apache.qpid.server.queue.AbstractQueue.validateOrCreateAlternateBinding(AbstractQueue.java:3537)
at 
org.apache.qpid.server.queue.AbstractQueue.onCreate(AbstractQueue.java:320)
at 
org.apache.qpid.server.model.AbstractConfiguredObject.doCreation(AbstractConfiguredObject.java:1273)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:893)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:866)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:637)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:630)
at 
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
at 
org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submitWrappedTask(TaskExecutorImpl.java:165)
at 
org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submit(TaskExecutorImpl.java:153)
at 
org.apache.qpid.server.model.AbstractConfiguredObject.doOnConfigThread(AbstractConfiguredObject.java:629)
at 
org.apache.qpid.server.model.AbstractConfiguredObject.createAsync(AbstractConfiguredObject.java:865)
at 
org.apache.qpid.server.model.AbstractConfiguredObjectTypeFactory.createAsync(AbstractConfiguredObjectTypeFactory.java:75)
at 
org.apache.qpid.server.queue.QueueFactory.createAsync(QueueFactory.java:58)
at 
org.apache.qpid.server.model.ConfiguredObjectFactoryImpl.createAsync(ConfiguredObjectFactoryImpl.java:145)
at 
org.apache.qpid.server.model.AbstractConfiguredObject.addChildAsync(AbstractConfiguredObject.java:2143)
at 
org.apache.qpid.server.virtualhost.AbstractVirtualHost.addChildAsync(AbstractVirtualHost.java:857)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2100)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2095)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:637)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:630)
at 
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
at 
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:320)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:360)
at 
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:313)
at 
com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:111)
at 
com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:58)
at 
com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:75)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at 
org.apache.qpid.server.bytebuffer.QpidByteBufferFactory.lambda$null$0(QpidByteBufferFactory.java:464)
at java.lang.Thread.run(Thread.java:745)
{noformat}

Client code:
{code}
Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
AMQSession amqSession = (AMQSession)session;
final Map arguments = new HashMap<>();
arguments.put("alternateExchange", "not_existing");
amqSession.sendCreateQueue("test", false, true, false, arguments);
{code}

  was:
Decaring queue with not existing alternate binding crashes the Broker with the 
following stack trace:
{noformat}
org.apache.qpid.server.configuration.IllegalConfigurationException: Cannot 
create alternate binding for 'test' : Alternate binding destination 
'not_existing' cannot be found.
at 
org.apache.qpid.server.queue.AbstractQueue.validateOrCreateAlternateBinding(AbstractQueue.java:3537)
at 
org.apache.qpid.server.queue.AbstractQueue.onCreate(AbstractQueue.java:320)
at 

[jira] [Updated] (QPID-8060) [Broker-J] [AMQP 0-8..0-9-1] Declaring queue with not existing alternate binding crashes the Broker

[Alex Rudyy (JIRA)]

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

Alex Rudyy updated QPID-8060:
-
Summary: [Broker-J] [AMQP 0-8..0-9-1] Declaring queue with not existing 
alternate binding crashes the Broker  (was: [Broker-J] [AMQP 0-8..0-9-1] 
Decaring queue with not existing alternate binding crashes the Broker)

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

[jira] [Created] (QPID-8061) [Broker-J] [AMQP 0-8..0-9-1] Decaring exchange with not existing alternate binding crashes the Broker

[Alex Rudyy (JIRA)]

Alex Rudyy created QPID-8061:


 Summary: [Broker-J] [AMQP 0-8..0-9-1] Decaring exchange with not 
existing alternate binding crashes the Broker
 Key: QPID-8061
 URL: https://issues.apache.org/jira/browse/QPID-8061
 Project: Qpid
  Issue Type: Bug
  Components: Broker-J
Affects Versions: qpid-java-broker-7.0.0
Reporter: Alex Rudyy
 Fix For: qpid-java-broker-7.0.1


Declaration of exchange with not existing alternate binding crashes the Broker 
as below:
{noformat}
org.apache.qpid.server.configuration.IllegalConfigurationException: Cannot 
create alternate binding for 'test' : Alternate binding destination 
'not_existing' cannot be found.
at 
org.apache.qpid.server.exchange.AbstractExchange.validateOrCreateAlternateBinding(AbstractExchange.java:1057)
at 
org.apache.qpid.server.exchange.AbstractExchange.onCreate(AbstractExchange.java:192)
at 
org.apache.qpid.server.model.AbstractConfiguredObject.doCreation(AbstractConfiguredObject.java:1273)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:893)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:866)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:637)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:630)
at 
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
at 
org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submitWrappedTask(TaskExecutorImpl.java:165)
at 
org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submit(TaskExecutorImpl.java:153)
at 
org.apache.qpid.server.model.AbstractConfiguredObject.doOnConfigThread(AbstractConfiguredObject.java:629)
at 
org.apache.qpid.server.model.AbstractConfiguredObject.createAsync(AbstractConfiguredObject.java:865)
at 
org.apache.qpid.server.model.AbstractConfiguredObjectTypeFactory.createAsync(AbstractConfiguredObjectTypeFactory.java:75)
at 
org.apache.qpid.server.model.ConfiguredObjectFactoryImpl.createAsync(ConfiguredObjectFactoryImpl.java:145)
at 
org.apache.qpid.server.model.AbstractConfiguredObject.addChildAsync(AbstractConfiguredObject.java:2143)
at 
org.apache.qpid.server.virtualhost.AbstractVirtualHost.addChildAsync(AbstractVirtualHost.java:857)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2100)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2095)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:637)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:630)
at 
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
at 
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:320)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:360)
at 
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:313)
at 
com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:111)
at 
com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:58)
at 
com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:75)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at 
org.apache.qpid.server.bytebuffer.QpidByteBufferFactory.lambda$null$0(QpidByteBufferFactory.java:464)
at java.lang.Thread.run(Thread.java:745)
{noformat}

Client code:
{code}
Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
AMQSession amqSession = (AMQSession)session;

final Map arguments = new HashMap<>();
arguments.put("alternateExchange", "not_existing");
amqSession.sendExchangeDeclare("test", "direct",false, true, false, arguments, 
false);
{code}



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

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

[jira] [Created] (QPID-8060) [Broker-J] [AMQP 0-8..0-9-1] Decaring queue with not existing alternate binding crashes the Broker

[Alex Rudyy (JIRA)]

Alex Rudyy created QPID-8060:


 Summary: [Broker-J] [AMQP 0-8..0-9-1] Decaring queue with not 
existing alternate binding crashes the Broker
 Key: QPID-8060
 URL: https://issues.apache.org/jira/browse/QPID-8060
 Project: Qpid
  Issue Type: Bug
  Components: Broker-J
Affects Versions: qpid-java-broker-7.0.0
Reporter: Alex Rudyy
 Fix For: qpid-java-broker-7.0.1


Decaring queue with not existing alternate binding crashes the Broker with the 
following stack trace:
{noformat}
org.apache.qpid.server.configuration.IllegalConfigurationException: Cannot 
create alternate binding for 'test' : Alternate binding destination 
'not_existing' cannot be found.
at 
org.apache.qpid.server.queue.AbstractQueue.validateOrCreateAlternateBinding(AbstractQueue.java:3537)
at 
org.apache.qpid.server.queue.AbstractQueue.onCreate(AbstractQueue.java:320)
at 
org.apache.qpid.server.model.AbstractConfiguredObject.doCreation(AbstractConfiguredObject.java:1273)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:893)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:866)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:637)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:630)
at 
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
at 
org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submitWrappedTask(TaskExecutorImpl.java:165)
at 
org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submit(TaskExecutorImpl.java:153)
at 
org.apache.qpid.server.model.AbstractConfiguredObject.doOnConfigThread(AbstractConfiguredObject.java:629)
at 
org.apache.qpid.server.model.AbstractConfiguredObject.createAsync(AbstractConfiguredObject.java:865)
at 
org.apache.qpid.server.model.AbstractConfiguredObjectTypeFactory.createAsync(AbstractConfiguredObjectTypeFactory.java:75)
at 
org.apache.qpid.server.queue.QueueFactory.createAsync(QueueFactory.java:58)
at 
org.apache.qpid.server.model.ConfiguredObjectFactoryImpl.createAsync(ConfiguredObjectFactoryImpl.java:145)
at 
org.apache.qpid.server.model.AbstractConfiguredObject.addChildAsync(AbstractConfiguredObject.java:2143)
at 
org.apache.qpid.server.virtualhost.AbstractVirtualHost.addChildAsync(AbstractVirtualHost.java:857)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2100)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2095)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:637)
at 
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:630)
at 
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
at 
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:320)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:360)
at 
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:313)
at 
com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:111)
at 
com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:58)
at 
com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:75)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at 
org.apache.qpid.server.bytebuffer.QpidByteBufferFactory.lambda$null$0(QpidByteBufferFactory.java:464)
at java.lang.Thread.run(Thread.java:745)
{noformat}

Client code:
{code}
Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
AMQSession amqSession = (AMQSession)session;
final Map arguments = new HashMap<>();
arguments.put("alternateExchange", "not_existing");
amqSession.sendCreateQueue("test", false, true, false, arguments);
{code}



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

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