[jira] [Commented] (PROTON-1211) C++ binding exception in message::correlation_id()
[ https://issues.apache.org/jira/browse/PROTON-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301323#comment-15301323 ] ASF subversion and git services commented on PROTON-1211: - Commit b937c85d213fe64a959e259c60ae700904371566 in qpid-proton's branch refs/heads/0.13.x from Clifford Jansen [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=b937c85 ] PROTON-1211: C++ binding - incorrect replacing of message correlation_id > C++ binding exception in message::correlation_id() > -- > > Key: PROTON-1211 > URL: https://issues.apache.org/jira/browse/PROTON-1211 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: 0.13.0, 0.14.0 >Reporter: Cliff Jansen >Assignee: Cliff Jansen >Priority: Blocker > Fix For: 0.13.0 > > Attachments: msgid.cpp > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-343) Router stops accepting connections after load from parallel senders
[ https://issues.apache.org/jira/browse/DISPATCH-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Sharda updated DISPATCH-343: --- Attachment: drivers.tar.gz Ganesh, I am attaching my drivers here (drivers.tar.gz). When you run them against 2 connected routers from your cluster of 3, you should be able to reproduce the crash. Please do make in the extracted folder and run the drivers as follows: ./recv_no_ssl -n 1 amqp://:/examples Separate terminal: ./send_no_ssl -m 10 -n 6 -a amqp://:/examples > Router stops accepting connections after load from parallel senders > --- > > Key: DISPATCH-343 > URL: https://issues.apache.org/jira/browse/DISPATCH-343 > Project: Qpid Dispatch > Issue Type: Bug > Components: Routing Engine >Affects Versions: 0.6.0 >Reporter: Vishal Sharda >Priority: Blocker > Attachments: Connection_aborted.png, Connection_aborted_1.png, > Crash.png, Crash_10S_2R.png, R1.conf, R2.conf, R3.conf, > Sender_router_crash.png, bt_qd_dealloc.png, bt_qdr_link_cleanup_CT.png, > bt_sasl.png, bt_sys_mutex_lock.png, config1_nossl.conf, config2_nossl.conf, > drivers.tar.gz, resource-limit-exceeded.png > > > We ran 2 parallel senders and 2 receivers with each sender sending 5 > messages. After a while we saw that router stopped accepting connections > even from qdstat. We saw various errors in the logs (screenshots attached). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-342) qdrouterd.conf doc calls out router.config.{address,linkRoute,autoLink}
[
https://issues.apache.org/jira/browse/DISPATCH-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300828#comment-15300828
]
Ganesh Murthy commented on DISPATCH-342:
pushed this change up to the site -
https://qpid.apache.org/releases/qpid-dispatch-master/man/qdrouterd.conf.html
> qdrouterd.conf doc calls out router.config.{address,linkRoute,autoLink}
> ---
>
> Key: DISPATCH-342
> URL: https://issues.apache.org/jira/browse/DISPATCH-342
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Documentation
>Affects Versions: 0.6.0
>Reporter: Ted Ross
>Assignee: Ganesh Murthy
> Fix For: 0.6.0
>
>
> Three configuration entities: address, linkRoute, and autoLink are called
> out in the configuration doc with a prefix of router.config.
> This is incorrect syntax. The "router.config" should not be displayed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-182) TransportOptions and TransportSslOptions clone methods are incomplete
[ https://issues.apache.org/jira/browse/QPIDJMS-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300816#comment-15300816 ] ASF subversion and git services commented on QPIDJMS-182: - Commit 19128a577ed90a5b058d73c8617ffee8267a0ec8 in qpid-jms's branch refs/heads/master from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=19128a5 ] QPIDJMS-182 clone methods not copying default port values. > TransportOptions and TransportSslOptions clone methods are incomplete > - > > Key: QPIDJMS-182 > URL: https://issues.apache.org/jira/browse/QPIDJMS-182 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Affects Versions: 0.9.0 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Trivial > Fix For: 0.10.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPIDJMS-182) TransportOptions and TransportSslOptions clone methods are incomplete
Timothy Bish created QPIDJMS-182: Summary: TransportOptions and TransportSslOptions clone methods are incomplete Key: QPIDJMS-182 URL: https://issues.apache.org/jira/browse/QPIDJMS-182 Project: Qpid JMS Issue Type: Bug Components: qpid-jms-client Affects Versions: 0.9.0 Reporter: Timothy Bish Assignee: Timothy Bish Priority: Trivial Fix For: 0.10.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-342) qdrouterd.conf doc calls out router.config.{address,linkRoute,autoLink}
[
https://issues.apache.org/jira/browse/DISPATCH-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300752#comment-15300752
]
ASF GitHub Bot commented on DISPATCH-342:
-
Github user ganeshmurthy closed the pull request at:
https://github.com/apache/qpid-dispatch/pull/77
> qdrouterd.conf doc calls out router.config.{address,linkRoute,autoLink}
> ---
>
> Key: DISPATCH-342
> URL: https://issues.apache.org/jira/browse/DISPATCH-342
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Documentation
>Affects Versions: 0.6.0
>Reporter: Ted Ross
>Assignee: Ganesh Murthy
> Fix For: 0.6.0
>
>
> Three configuration entities: address, linkRoute, and autoLink are called
> out in the configuration doc with a prefix of router.config.
> This is incorrect syntax. The "router.config" should not be displayed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request: DISPATCH-342 - Remove the config route...
Github user ganeshmurthy closed the pull request at: https://github.com/apache/qpid-dispatch/pull/77 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4992) preserve all AMQP properties in JMS AMQP 1.0 API, so AMQP->JMS->AMQP works
[ https://issues.apache.org/jira/browse/QPID-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300714#comment-15300714 ] Rob Godfrey commented on QPID-4992: --- I've raised QPID-7280 about the 0-10 documentation issue > preserve all AMQP properties in JMS AMQP 1.0 API, so AMQP->JMS->AMQP works > -- > > Key: QPID-4992 > URL: https://issues.apache.org/jira/browse/QPID-4992 > Project: Qpid > Issue Type: Improvement > Components: JMS AMQP 1.0 Client >Affects Versions: 0.22 > Environment: all >Reporter: Axel Podehl > > As I understand from QPID-3380 there is no way to retrieve all AMQP header > properties (e.g. contentType) with the Java API. > In my case, I have a generic JMS record program and would want to use > it to record an AMQP message and replay it, simply using the QPid API, but > unless I do some nasty type-casts, important AMQP properties are lost, for > example AMQP content type. > Interestingly enough, if I use the ActiveMQ transport transformer and receive > AMQP messages through the ActiveMQ JMS API, all properties are copied for me: > https://cwiki.apache.org/confluence/display/ACTIVEMQ/AMQP > So receiving an AMQP messages using the ActiveMQ JMS API gives me more > information than with the Qpid AMQP JMS API, which is strange. > Qpid's JMS API should be the expert on AMQP properties, not ActiveMQ's > message transformer. > Wouldn't it make sense to deploy the same mapping of AMQP to JMS properties > (https://cwiki.apache.org/confluence/display/ACTIVEMQ/AMQP) in the QPid API > itself ? > Or at least have an option (e.g. in the ConnectionFactory) to do so ? > That way a bridge of AMQP -> JMS -> AMQP wouldn't loose important information > but could still stick with the real JMS API. > Please note, it's quite common for JMS providers to extend the list of > properties with a set of properties have a 'JMS' (or better a 'JMSX') prefix. > For example MQ: > http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=%2Fcom.ibm.mq.csqzaw.doc%2Fuj25450_.htm -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7280) [Java 0-10 Client] [Documentation] Section 3.1 Java JMS Message Properties is incorrect
[ https://issues.apache.org/jira/browse/QPID-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300717#comment-15300717 ] Rob Godfrey commented on QPID-7280: --- Hi [~jflemer], so the document is clearly wrong in equating mp.content_type with JMSType. The content_type is used by the JMS client to identify the "type" of the message (BytesMessage, TextMessage, MapMessage, etc...) since it describes the nature of the encoding of the message body... so it cannot really be set independently through the JMS client API (though it would be nice to allow TextMessages to set the content type to be text/ and BytesMessages to be /), and obviously it is not great that there is no way to get at the value of content type on the incoming message. Were there other inaccuracies that you found? > [Java 0-10 Client] [Documentation] Section 3.1 Java JMS Message Properties is > incorrect > --- > > Key: QPID-7280 > URL: https://issues.apache.org/jira/browse/QPID-7280 > Project: Qpid > Issue Type: Bug > Components: Documentation, Java Client >Reporter: Rob Godfrey > > As noted by [~jflemer] in > [this|https://issues.apache.org/jira/browse/QPID-4992?focusedCommentId=15300427=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15300427] > comment on QPID-4992 , the documentation regarding the mapping of the > message_properties.content_type field is incorrect -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-7280) [Java 0-10 Client] [Documentation] Section 3.1 Java JMS Message Properties is incorrect
Rob Godfrey created QPID-7280:
-
Summary: [Java 0-10 Client] [Documentation] Section 3.1 Java JMS
Message Properties is incorrect
Key: QPID-7280
URL: https://issues.apache.org/jira/browse/QPID-7280
Project: Qpid
Issue Type: Bug
Components: Documentation, Java Client
Reporter: Rob Godfrey
As noted by [~jflemer] in
{this|https://issues.apache.org/jira/browse/QPID-4992?focusedCommentId=15300427=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15300427}
comment on QPID-4992 , the documentation regarding the mapping of the
message_properties.content_type field is incorrect
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7280) [Java 0-10 Client] [Documentation] Section 3.1 Java JMS Message Properties is incorrect
[
https://issues.apache.org/jira/browse/QPID-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey updated QPID-7280:
--
Description: As noted by [~jflemer] in
[this|https://issues.apache.org/jira/browse/QPID-4992?focusedCommentId=15300427=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15300427]
comment on QPID-4992 , the documentation regarding the mapping of the
message_properties.content_type field is incorrect (was: As noted by
[~jflemer] in
{this|https://issues.apache.org/jira/browse/QPID-4992?focusedCommentId=15300427=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15300427}
comment on QPID-4992 , the documentation regarding the mapping of the
message_properties.content_type field is incorrect)
> [Java 0-10 Client] [Documentation] Section 3.1 Java JMS Message Properties is
> incorrect
> ---
>
> Key: QPID-7280
> URL: https://issues.apache.org/jira/browse/QPID-7280
> Project: Qpid
> Issue Type: Bug
> Components: Documentation, Java Client
>Reporter: Rob Godfrey
>
> As noted by [~jflemer] in
> [this|https://issues.apache.org/jira/browse/QPID-4992?focusedCommentId=15300427=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15300427]
> comment on QPID-4992 , the documentation regarding the mapping of the
> message_properties.content_type field is incorrect
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-343) Router stops accepting connections after load from parallel senders
[
https://issues.apache.org/jira/browse/DISPATCH-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300679#comment-15300679
]
Ganesh Murthy commented on DISPATCH-343:
Vishal, I ran thru the following cases -
1. Two senders and one receiver
I started the senders and receivers like this (in separate terminal windows)
respectively
{noformat}
Senders
python simple_send.py -a 127.0.0.1:5672/examples -m10
python simple_send.py -a 127.0.0.1:5672/examples -m10
Receiver
python simple_recv.py -a 127.0.0.1:5677/examples -m20
{noformat}
The senders are sending 10 messages each and the lone receiver is receiving
all 20 messages. All messages were delivered successfully. No router
crashes reported
2. Three senders and one receiver
{noformat}
Senders
python simple_send.py -a 127.0.0.1:5672/examples -m10
python simple_send.py -a 127.0.0.1:5672/examples -m10
python simple_send.py -a 127.0.0.1:5672/examples -m10
Receiver
python simple_recv.py -a 127.0.0.1:5677/examples -m30
{noformat}
Three senders are sending 10 messages each and the lone receiver received
all 30 messages. All messages were delivered successfully. No router
crashes reported.
3. Three senders and two receivers
{noformat}
Senders
python simple_send.py -a 127.0.0.1:5672/examples -m60
python simple_send.py -a 127.0.0.1:5672/examples -m60
python simple_send.py -a 127.0.0.1:5672/examples -m60
Receivers
python simple_recv.py -a 127.0.0.1:5677/examples -m90
python simple_recv.py -a 127.0.0.1:5677/examples -m90
{noformat}
Three senders sending 60 messages each and 2 receivers receiving 90
messages each. All messages were delivered successfully. No router crashes
reported.
I modified the simple_recv.py to not ignore duplicates.
> Router stops accepting connections after load from parallel senders
> ---
>
> Key: DISPATCH-343
> URL: https://issues.apache.org/jira/browse/DISPATCH-343
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Routing Engine
>Affects Versions: 0.6.0
>Reporter: Vishal Sharda
>Priority: Blocker
> Attachments: Connection_aborted.png, Connection_aborted_1.png,
> Crash.png, Crash_10S_2R.png, R1.conf, R2.conf, R3.conf,
> Sender_router_crash.png, bt_qd_dealloc.png, bt_qdr_link_cleanup_CT.png,
> bt_sasl.png, bt_sys_mutex_lock.png, config1_nossl.conf, config2_nossl.conf,
> resource-limit-exceeded.png
>
>
> We ran 2 parallel senders and 2 receivers with each sender sending 5
> messages. After a while we saw that router stopped accepting connections
> even from qdstat. We saw various errors in the logs (screenshots attached).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (DISPATCH-339) The change from 'routerId' to 'id' and 'addr' to 'host' configuration option is not backwards compatible
[
https://issues.apache.org/jira/browse/DISPATCH-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek closed DISPATCH-339.
---
Config files {ra.conf} and {rb.conf} are now working as intended. Thanks.
> The change from 'routerId' to 'id' and 'addr' to 'host' configuration option
> is not backwards compatible
>
>
> Key: DISPATCH-339
> URL: https://issues.apache.org/jira/browse/DISPATCH-339
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 0.6.0
>Reporter: Jiri Danek
>Assignee: Ganesh Murthy
> Fix For: 0.6.0
>
> Attachments: ra.conf, ra_.conf, ra_local.conf, rb.conf, rb_.conf,
> rb_local.conf
>
>
> I started qdrouterd with the following configuration
> {noformat}
> router {
> mode: interior
> routerId: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> {noformat}
> Running qdstat then prints that Router id is None.
> {code:title=qdstat -g|borderStyle=solid}
> Router Statistics
> attr value
> =
> Mode interior
> Area 0
> Router Id None
> Address Count 0
> Link Count 0
> Node Count 0
> {code}
> Other commands, for example
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> work correctly in this respect.
> If I update my config and use {{id}} instead of {{routerId}}, then qdstat
> prints correct information.
> I'd expect that the config that worked before the routerId/id change would
> continue working.
> If I use {{addr}} in my connectors, then my router does not connect to other
> routers. I had to update the config to using {{host}} and only then it worked
> for me.
> {noformat}
> router {
> mode: interior
> id: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> connector {
> name: to.r.b
> addr: {{ rb_ip }}
> port: 50001
> role: inter-router
> }
> {noformat}
> {noformat}
> router {
> mode: interior
> id: r.b
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> listener {
> role: inter-router
> addr: 0.0.0.0
> port: 50001
> authenticatePeer: no
> }
> {noformat}
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> After I change addr to host and restart both routers,
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)-
> r.b- 1
> {code}
> NOTE: I noticed that if I use routerId or addr, no deprecation warning is
> shown in qdrouterd output with the default log level. As far as I can
> remember, there are deprecation warnings for some features like fixedAddress,
> I think.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (PROTON-1206) c++ core dump in modified helloworld.cpp example
[
https://issues.apache.org/jira/browse/PROTON-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway closed PROTON-1206.
---
Resolution: Not A Problem
False alarm. If you modify the example as shown, there are two connections, one
for sender and one for receiver. The example was only closing one connection
and therefore not exiting because the other was still open. The test runner was
killing the hung process. When the example is modified to close both
connections it functions normally.
> c++ core dump in modified helloworld.cpp example
> -
>
> Key: PROTON-1206
> URL: https://issues.apache.org/jira/browse/PROTON-1206
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding
>Affects Versions: 0.12.2
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: 0.13.0
>
>
> With the following change the helloworld.cpp example core dumps:
> {code}
> modified examples/cpp/helloworld.cpp
> @@ -38,10 +38,6 @@ class hello_world : public proton::messaging_handler {
> hello_world(const std::string& u) : url(u) {}
>
> void on_container_start(proton::container& c) OVERRIDE {
> -c.connect(url);
> -}
> -
> -void on_connection_open(proton::connection& c) OVERRIDE {
> c.open_receiver(url.path());
> c.open_sender(url.path());
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-343) Router stops accepting connections after load from parallel senders
[ https://issues.apache.org/jira/browse/DISPATCH-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300571#comment-15300571 ] Vishal Sharda commented on DISPATCH-343: Ganesh, can you provide the number of messages per sender that you tested with and the sender/receiver code that you used? Also, it would help if you can test some scenarios in which senders outnumber receivers. > Router stops accepting connections after load from parallel senders > --- > > Key: DISPATCH-343 > URL: https://issues.apache.org/jira/browse/DISPATCH-343 > Project: Qpid Dispatch > Issue Type: Bug > Components: Routing Engine >Affects Versions: 0.6.0 >Reporter: Vishal Sharda >Priority: Blocker > Attachments: Connection_aborted.png, Connection_aborted_1.png, > Crash.png, Crash_10S_2R.png, R1.conf, R2.conf, R3.conf, > Sender_router_crash.png, bt_qd_dealloc.png, bt_qdr_link_cleanup_CT.png, > bt_sasl.png, bt_sys_mutex_lock.png, config1_nossl.conf, config2_nossl.conf, > resource-limit-exceeded.png > > > We ran 2 parallel senders and 2 receivers with each sender sending 5 > messages. After a while we saw that router stopped accepting connections > even from qdstat. We saw various errors in the logs (screenshots attached). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPIDJMS-178) ObjectMessage does not always snapshot the store value
[ https://issues.apache.org/jira/browse/QPIDJMS-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved QPIDJMS-178. -- Resolution: Fixed > ObjectMessage does not always snapshot the store value > -- > > Key: QPIDJMS-178 > URL: https://issues.apache.org/jira/browse/QPIDJMS-178 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Affects Versions: 0.9.0 >Reporter: Timothy Bish >Assignee: Timothy Bish > Fix For: 0.10.0 > > > In some cases the ObjectMessage does not take or return a snapshot of the > stored value allowing for changes to one instance being reflected in the > other which is not in accordance with the JMS spec. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-343) Router stops accepting connections after load from parallel senders
[
https://issues.apache.org/jira/browse/DISPATCH-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300538#comment-15300538
]
Ganesh Murthy commented on DISPATCH-343:
We got a VM with Debian 8 and followed installation instructions for
qpid-proton and qpid-dispatch. (Note there is a separate section for Debian in
the proton's INSTALL.md)
I set up a 3 router network like this -
{noformat}
R1 R2
\/
R3
{noformat}
I attached 3 receivers to R3 and 3 senders to R1 all running in parallel. All
messages were delivered successfully to the receivers and did not see any
crashes.
> Router stops accepting connections after load from parallel senders
> ---
>
> Key: DISPATCH-343
> URL: https://issues.apache.org/jira/browse/DISPATCH-343
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Routing Engine
>Affects Versions: 0.6.0
>Reporter: Vishal Sharda
>Priority: Blocker
> Attachments: Connection_aborted.png, Connection_aborted_1.png,
> Crash.png, Crash_10S_2R.png, R1.conf, R2.conf, R3.conf,
> Sender_router_crash.png, bt_qd_dealloc.png, bt_qdr_link_cleanup_CT.png,
> bt_sasl.png, bt_sys_mutex_lock.png, config1_nossl.conf, config2_nossl.conf,
> resource-limit-exceeded.png
>
>
> We ran 2 parallel senders and 2 receivers with each sender sending 5
> messages. After a while we saw that router stopped accepting connections
> even from qdstat. We saw various errors in the logs (screenshots attached).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1211) C++ binding exception in message::correlation_id()
[ https://issues.apache.org/jira/browse/PROTON-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300522#comment-15300522 ] Justin Ross commented on PROTON-1211: - Reviewed by Alan. Approved for 0.13.0. > C++ binding exception in message::correlation_id() > -- > > Key: PROTON-1211 > URL: https://issues.apache.org/jira/browse/PROTON-1211 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: 0.13.0, 0.14.0 >Reporter: Cliff Jansen >Assignee: Cliff Jansen >Priority: Blocker > Fix For: 0.13.0 > > Attachments: msgid.cpp > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4992) preserve all AMQP properties in JMS AMQP 1.0 API, so AMQP->JMS->AMQP works
[
https://issues.apache.org/jira/browse/QPID-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300427#comment-15300427
]
James Flemer commented on QPID-4992:
This affects the AMQP 0-10 JMS implementation as well. The content-type
mapping documented does not really work. The only truly respected type seems
to be {{x-jms-type}} via {{get/setJMSType()}}. Using {{mp.content_type}} and
{{get/setContentType()}} (with a JMS {{BytesMessage}}) does not work as
expected. The tables in the two links below are inaccurate:
https://qpid.apache.org/releases/qpid-0.32/programming/book/ch03s03.html
https://qpid.apache.org/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Miscellaneous.html#JMS-Client-0-10-Miscellaneous-Message-Properties
> preserve all AMQP properties in JMS AMQP 1.0 API, so AMQP->JMS->AMQP works
> --
>
> Key: QPID-4992
> URL: https://issues.apache.org/jira/browse/QPID-4992
> Project: Qpid
> Issue Type: Improvement
> Components: JMS AMQP 1.0 Client
>Affects Versions: 0.22
> Environment: all
>Reporter: Axel Podehl
>
> As I understand from QPID-3380 there is no way to retrieve all AMQP header
> properties (e.g. contentType) with the Java API.
> In my case, I have a generic JMS record program and would want to use
> it to record an AMQP message and replay it, simply using the QPid API, but
> unless I do some nasty type-casts, important AMQP properties are lost, for
> example AMQP content type.
> Interestingly enough, if I use the ActiveMQ transport transformer and receive
> AMQP messages through the ActiveMQ JMS API, all properties are copied for me:
> https://cwiki.apache.org/confluence/display/ACTIVEMQ/AMQP
> So receiving an AMQP messages using the ActiveMQ JMS API gives me more
> information than with the Qpid AMQP JMS API, which is strange.
> Qpid's JMS API should be the expert on AMQP properties, not ActiveMQ's
> message transformer.
> Wouldn't it make sense to deploy the same mapping of AMQP to JMS properties
> (https://cwiki.apache.org/confluence/display/ACTIVEMQ/AMQP) in the QPid API
> itself ?
> Or at least have an option (e.g. in the ConnectionFactory) to do so ?
> That way a bridge of AMQP -> JMS -> AMQP wouldn't loose important information
> but could still stick with the real JMS API.
> Please note, it's quite common for JMS providers to extend the list of
> properties with a set of properties have a 'JMS' (or better a 'JMSX') prefix.
> For example MQ:
> http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=%2Fcom.ibm.mq.csqzaw.doc%2Fuj25450_.htm
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7116) Ability to utilise group information from a LDAP compatible directory
[
https://issues.apache.org/jira/browse/QPID-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-7116:
-
Attachment: WIP-get-ldap-groups.diff
> Ability to utilise group information from a LDAP compatible directory
> -
>
> Key: QPID-7116
> URL: https://issues.apache.org/jira/browse/QPID-7116
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
>Reporter: Keith Wall
> Fix For: qpid-java-6.1
>
> Attachments: WIP-get-ldap-groups.diff
>
>
> The Java Broker can already authenticate users against an LDAP compatible
> directory. It should also be able to use the same information source as a
> source of group information too.
> The authentication provide needs to accept optional attributes governing
> where the group information will be found:
> {{groupSearchContext}} - the base entry for the role search. If not
> specified, the search base is the top-level directory context.
> {{groupSearchFilter}} - the LDAP search filter for selecting group entries.
> A {0} token within the filter will be replaced by the distinguish name of the
> authenticated user.
> {{groupAttributeName}} - the name of the attribute that contains the name of
> the role.
> After the authentication provider has successfully bound (authenticated) the
> user, it should perform a second query for the groups. It should build a
> {{GroupPrincipal}} for each group to which the user belongs and return this
> as part of the AuthenticationResult. If the group search attributes are not
> found, the group search should be skipped.
> A future version if the LDAP Authentication Provider may offer the ability to
> cache the group results for a DN period of time. This would serve to avoid
> hitting the Directory several times authentication (it already hits the
> Directory twice if {{bindWithoutSearch}} is false, this will add a third).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1211) C++ binding exception in message::correlation_id()
[ https://issues.apache.org/jira/browse/PROTON-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300304#comment-15300304 ] Alan Conway commented on PROTON-1211: - This approach using value rather than encoder is equivalent to the previous patch and more consistent since we are trying to phase out use of enocder. Also less error-prone (as this bug shows )since it's impossible to forget the clear(), which is built into op=. Approved for 0.13 > C++ binding exception in message::correlation_id() > -- > > Key: PROTON-1211 > URL: https://issues.apache.org/jira/browse/PROTON-1211 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: 0.13.0, 0.14.0 >Reporter: Cliff Jansen >Assignee: Cliff Jansen >Priority: Blocker > Fix For: 0.13.0 > > Attachments: msgid.cpp > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7000) [Java Broker] Add synthetic VirtualHost which allows management of whole broker
[ https://issues.apache.org/jira/browse/QPID-7000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300270#comment-15300270 ] ASF subversion and git services commented on QPID-7000: --- Commit 1745513 from [~godfrer] in branch 'java/trunk' [ https://svn.apache.org/r1745513 ] QPID-7000 : Use the address of the target of the consumer for route matching in preference to the consumer tag/name > [Java Broker] Add synthetic VirtualHost which allows management of whole > broker > --- > > Key: QPID-7000 > URL: https://issues.apache.org/jira/browse/QPID-7000 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > > Add a synthetic virtualhost / node which allows only access to $management to > allow for management of the whole broker. The $management node in other > virtual hosts should allow management only of the objects within the given > virtual host and connections associated with the vhost -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-347) Negative SASL outome when "requireEncryption" isn't satisfied
Paolo Patierno created DISPATCH-347: --- Summary: Negative SASL outome when "requireEncryption" isn't satisfied Key: DISPATCH-347 URL: https://issues.apache.org/jira/browse/DISPATCH-347 Project: Qpid Dispatch Issue Type: Wish Affects Versions: 0.6.0 Reporter: Paolo Patierno Priority: Minor If we configure the router with requireEncryption set to true but the client connect using a SASL mechanism which doesn't support encryption (i.e. ANONYMOUS, PLAIN, ...) the SASL exchange goes well with a successful outcome but the router close the TCP connection brutally after that. The client doesn't have any reason why it happens. The SASL RFC (https://tools.ietf.org/html/rfc4422) in the "Authentication Outcome" says that "The outcome is not successful if ..." ... "the negotiated security layer (or lack thereof) is not suitable ...". I think that above scenario is a "lack" of requested security so the SASL outcome to the client shouldn't be positive but negative. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (DISPATCH-343) Router stops accepting connections after load from parallel senders
[ https://issues.apache.org/jira/browse/DISPATCH-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300052#comment-15300052 ] Ulf Lilleengen edited comment on DISPATCH-343 at 5/25/16 1:43 PM: -- Vishal, If you have not already done so, it might be an idea to check /var/log/mcelog for hardware issues as well. Not sure if it exists on debian. was (Author: lulf): Vishal, If you have not already done so, it might be an idea to check /var/log/mcelog for hardware issues as well. > Router stops accepting connections after load from parallel senders > --- > > Key: DISPATCH-343 > URL: https://issues.apache.org/jira/browse/DISPATCH-343 > Project: Qpid Dispatch > Issue Type: Bug > Components: Routing Engine >Affects Versions: 0.6.0 >Reporter: Vishal Sharda >Priority: Blocker > Attachments: Connection_aborted.png, Connection_aborted_1.png, > Crash.png, Crash_10S_2R.png, R1.conf, R2.conf, R3.conf, > Sender_router_crash.png, bt_qd_dealloc.png, bt_qdr_link_cleanup_CT.png, > bt_sasl.png, bt_sys_mutex_lock.png, config1_nossl.conf, config2_nossl.conf, > resource-limit-exceeded.png > > > We ran 2 parallel senders and 2 receivers with each sender sending 5 > messages. After a while we saw that router stopped accepting connections > even from qdstat. We saw various errors in the logs (screenshots attached). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-343) Router stops accepting connections after load from parallel senders
[ https://issues.apache.org/jira/browse/DISPATCH-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300052#comment-15300052 ] Ulf Lilleengen commented on DISPATCH-343: - Vishal, If you have not already done so, it might be an idea to check /var/log/mcelog for hardware issues as well. > Router stops accepting connections after load from parallel senders > --- > > Key: DISPATCH-343 > URL: https://issues.apache.org/jira/browse/DISPATCH-343 > Project: Qpid Dispatch > Issue Type: Bug > Components: Routing Engine >Affects Versions: 0.6.0 >Reporter: Vishal Sharda >Priority: Blocker > Attachments: Connection_aborted.png, Connection_aborted_1.png, > Crash.png, Crash_10S_2R.png, R1.conf, R2.conf, R3.conf, > Sender_router_crash.png, bt_qd_dealloc.png, bt_qdr_link_cleanup_CT.png, > bt_sasl.png, bt_sys_mutex_lock.png, config1_nossl.conf, config2_nossl.conf, > resource-limit-exceeded.png > > > We ran 2 parallel senders and 2 receivers with each sender sending 5 > messages. After a while we saw that router stopped accepting connections > even from qdstat. We saw various errors in the logs (screenshots attached). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-339) The change from 'routerId' to 'id' and 'addr' to 'host' configuration option is not backwards compatible
[
https://issues.apache.org/jira/browse/DISPATCH-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross resolved DISPATCH-339.
---
Resolution: Fixed
> The change from 'routerId' to 'id' and 'addr' to 'host' configuration option
> is not backwards compatible
>
>
> Key: DISPATCH-339
> URL: https://issues.apache.org/jira/browse/DISPATCH-339
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 0.6.0
>Reporter: Jiri Danek
>Assignee: Ganesh Murthy
> Fix For: 0.6.0
>
> Attachments: ra.conf, ra_.conf, ra_local.conf, rb.conf, rb_.conf,
> rb_local.conf
>
>
> I started qdrouterd with the following configuration
> {noformat}
> router {
> mode: interior
> routerId: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> {noformat}
> Running qdstat then prints that Router id is None.
> {code:title=qdstat -g|borderStyle=solid}
> Router Statistics
> attr value
> =
> Mode interior
> Area 0
> Router Id None
> Address Count 0
> Link Count 0
> Node Count 0
> {code}
> Other commands, for example
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> work correctly in this respect.
> If I update my config and use {{id}} instead of {{routerId}}, then qdstat
> prints correct information.
> I'd expect that the config that worked before the routerId/id change would
> continue working.
> If I use {{addr}} in my connectors, then my router does not connect to other
> routers. I had to update the config to using {{host}} and only then it worked
> for me.
> {noformat}
> router {
> mode: interior
> id: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> connector {
> name: to.r.b
> addr: {{ rb_ip }}
> port: 50001
> role: inter-router
> }
> {noformat}
> {noformat}
> router {
> mode: interior
> id: r.b
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> listener {
> role: inter-router
> addr: 0.0.0.0
> port: 50001
> authenticatePeer: no
> }
> {noformat}
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> After I change addr to host and restart both routers,
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)-
> r.b- 1
> {code}
> NOTE: I noticed that if I use routerId or addr, no deprecation warning is
> shown in qdrouterd output with the default log level. As far as I can
> remember, there are deprecation warnings for some features like fixedAddress,
> I think.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request: DISPATCH-339 - Set the correct value o...
Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/78 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDJMS-181) Cannot connect Qpid-Broker using the SSL
[ https://issues.apache.org/jira/browse/QPIDJMS-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell closed QPIDJMS-181. -- Resolution: Not A Bug As mentioned on the users list, the exception shows the hostname verification is failing. You need to ensure you connect to a hostname matching the details presented by the server certificate, either by updating your client config or the server certificate as appropriate, or else disable hostname verification (obviously not recommended). Closing this as 'not a bug' until there is evidence to consider otherwise. > Cannot connect Qpid-Broker using the SSL > > > Key: QPIDJMS-181 > URL: https://issues.apache.org/jira/browse/QPIDJMS-181 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Affects Versions: 0.9.0 > Environment: Windows7、jdk,the broker is in linux7.2 >Reporter: Steven > > The below link address is Qpid latest Client API > Documentation,https://qpid.apache.org/releases/qpid-jms-0.9.0/docs/index.html,According > to its configuration with ssl,My Connection URL is > connectionfactory.qpidConnectionfactory = > amqps://QpidServer:5673?transport.trustStoreLocation=F:/AMQP/QpidSSL/clientts.jks=123456,It > reported the following error: > 2016-05-25 17:55:30,230 [main ] - ERROR JmsConnectionFactory >- Failed to create JMS Provider instance for: amqps > Caught exception, exiting. > javax.jms.JMSException: Failed to create connection to: > amqps://QpidServer:5673?transport.trustStoreLocation=F%253A%252FAMQP%252FQpidSSL%252Fclientts.jks=123456 > at > org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:66) > at > org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:172) > at > org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:161) > at org.apache.qpid.jms.example.HelloWorld.test(HelloWorld.java:92) > at org.apache.qpid.jms.example.HelloWorld.main(HelloWorld.java:73) > Caused by: javax.net.ssl.SSLHandshakeException: General SSLEngine problem > at sun.security.ssl.Handshaker.checkThrown(Unknown Source) > at sun.security.ssl.SSLEngineImpl.checkTaskThrown(Unknown Source) > at sun.security.ssl.SSLEngineImpl.readNetRecord(Unknown Source) > at sun.security.ssl.SSLEngineImpl.unwrap(Unknown Source) > at javax.net.ssl.SSLEngine.unwrap(Unknown Source) > at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:927) > at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:871) > at io.netty.handler.ssl.SslHandler.decode(SslHandler.java:827) > at > io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:228) > at > io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:141) > at > io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:340) > at > io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:326) > at > io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785) > at > io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:116) > at > io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:494) > at > io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:461) > at > io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:378) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:350) > at > io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) > at java.lang.Thread.run(Unknown Source) > Caused by: javax.net.ssl.SSLHandshakeException: General SSLEngine problem > at sun.security.ssl.Alerts.getSSLException(Unknown Source) > at sun.security.ssl.SSLEngineImpl.fatal(Unknown Source) > at sun.security.ssl.Handshaker.fatalSE(Unknown Source) > at sun.security.ssl.Handshaker.fatalSE(Unknown Source) > at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source) > at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source) > at sun.security.ssl.Handshaker.processLoop(Unknown Source) > at sun.security.ssl.Handshaker$1.run(Unknown Source) > at sun.security.ssl.Handshaker$1.run(Unknown Source) > at java.security.AccessController.doPrivileged(Native Method) > at sun.security.ssl.Handshaker$DelegatedTask.run(Unknown Source) > at > io.netty.handler.ssl.SslHandler.runDelegatedTasks(SslHandler.java:960) > at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:891) > ... 13 more
[jira] [Commented] (DISPATCH-339) The change from 'routerId' to 'id' and 'addr' to 'host' configuration option is not backwards compatible
[
https://issues.apache.org/jira/browse/DISPATCH-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15299987#comment-15299987
]
ASF GitHub Bot commented on DISPATCH-339:
-
Github user asfgit closed the pull request at:
https://github.com/apache/qpid-dispatch/pull/78
> The change from 'routerId' to 'id' and 'addr' to 'host' configuration option
> is not backwards compatible
>
>
> Key: DISPATCH-339
> URL: https://issues.apache.org/jira/browse/DISPATCH-339
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 0.6.0
>Reporter: Jiri Danek
>Assignee: Ganesh Murthy
> Fix For: 0.6.0
>
> Attachments: ra.conf, ra_.conf, ra_local.conf, rb.conf, rb_.conf,
> rb_local.conf
>
>
> I started qdrouterd with the following configuration
> {noformat}
> router {
> mode: interior
> routerId: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> {noformat}
> Running qdstat then prints that Router id is None.
> {code:title=qdstat -g|borderStyle=solid}
> Router Statistics
> attr value
> =
> Mode interior
> Area 0
> Router Id None
> Address Count 0
> Link Count 0
> Node Count 0
> {code}
> Other commands, for example
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> work correctly in this respect.
> If I update my config and use {{id}} instead of {{routerId}}, then qdstat
> prints correct information.
> I'd expect that the config that worked before the routerId/id change would
> continue working.
> If I use {{addr}} in my connectors, then my router does not connect to other
> routers. I had to update the config to using {{host}} and only then it worked
> for me.
> {noformat}
> router {
> mode: interior
> id: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> connector {
> name: to.r.b
> addr: {{ rb_ip }}
> port: 50001
> role: inter-router
> }
> {noformat}
> {noformat}
> router {
> mode: interior
> id: r.b
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> listener {
> role: inter-router
> addr: 0.0.0.0
> port: 50001
> authenticatePeer: no
> }
> {noformat}
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> After I change addr to host and restart both routers,
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)-
> r.b- 1
> {code}
> NOTE: I noticed that if I use routerId or addr, no deprecation warning is
> shown in qdrouterd output with the default log level. As far as I can
> remember, there are deprecation warnings for some features like fixedAddress,
> I think.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-339) The change from 'routerId' to 'id' and 'addr' to 'host' configuration option is not backwards compatible
[
https://issues.apache.org/jira/browse/DISPATCH-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15299986#comment-15299986
]
ASF subversion and git services commented on DISPATCH-339:
--
Commit 87d0a406c64e6b4a94c009064c8526f1932fd846 in qpid-dispatch's branch
refs/heads/master from [~tr...@redhat.com]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=87d0a40 ]
DISPATCH-339 - [From Ganesh Murthy] Properly handle default values for
host/addr.
This closes #78
> The change from 'routerId' to 'id' and 'addr' to 'host' configuration option
> is not backwards compatible
>
>
> Key: DISPATCH-339
> URL: https://issues.apache.org/jira/browse/DISPATCH-339
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 0.6.0
>Reporter: Jiri Danek
>Assignee: Ganesh Murthy
> Fix For: 0.6.0
>
> Attachments: ra.conf, ra_.conf, ra_local.conf, rb.conf, rb_.conf,
> rb_local.conf
>
>
> I started qdrouterd with the following configuration
> {noformat}
> router {
> mode: interior
> routerId: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> {noformat}
> Running qdstat then prints that Router id is None.
> {code:title=qdstat -g|borderStyle=solid}
> Router Statistics
> attr value
> =
> Mode interior
> Area 0
> Router Id None
> Address Count 0
> Link Count 0
> Node Count 0
> {code}
> Other commands, for example
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> work correctly in this respect.
> If I update my config and use {{id}} instead of {{routerId}}, then qdstat
> prints correct information.
> I'd expect that the config that worked before the routerId/id change would
> continue working.
> If I use {{addr}} in my connectors, then my router does not connect to other
> routers. I had to update the config to using {{host}} and only then it worked
> for me.
> {noformat}
> router {
> mode: interior
> id: r.a
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> connector {
> name: to.r.b
> addr: {{ rb_ip }}
> port: 50001
> role: inter-router
> }
> {noformat}
> {noformat}
> router {
> mode: interior
> id: r.b
> }
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> listener {
> role: inter-router
> addr: 0.0.0.0
> port: 50001
> authenticatePeer: no
> }
> {noformat}
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)
> {code}
> After I change addr to host and restart both routers,
> {code:title=qdstat -n|borderStyle=solid}
> Routers in the Network
> router-id next-hop link
> ===
> r.a(self)-
> r.b- 1
> {code}
> NOTE: I noticed that if I use routerId or addr, no deprecation warning is
> shown in qdrouterd output with the default log level. As far as I can
> remember, there are deprecation warnings for some features like fixedAddress,
> I think.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-342) qdrouterd.conf doc calls out router.config.{address,linkRoute,autoLink}
[
https://issues.apache.org/jira/browse/DISPATCH-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross resolved DISPATCH-342.
---
Resolution: Fixed
> qdrouterd.conf doc calls out router.config.{address,linkRoute,autoLink}
> ---
>
> Key: DISPATCH-342
> URL: https://issues.apache.org/jira/browse/DISPATCH-342
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Documentation
>Affects Versions: 0.6.0
>Reporter: Ted Ross
>Assignee: Ganesh Murthy
> Fix For: 0.6.0
>
>
> Three configuration entities: address, linkRoute, and autoLink are called
> out in the configuration doc with a prefix of router.config.
> This is incorrect syntax. The "router.config" should not be displayed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-342) qdrouterd.conf doc calls out router.config.{address,linkRoute,autoLink}
[
https://issues.apache.org/jira/browse/DISPATCH-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15299952#comment-15299952
]
ASF subversion and git services commented on DISPATCH-342:
--
Commit 6952d9f9572cd0d679be9ee954653b74823af565 in qpid-dispatch's branch
refs/heads/master from [~ganeshmurthy]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=6952d9f ]
DISPATCH-342 - Remove the config router.config from address, link route and
auto link entities
> qdrouterd.conf doc calls out router.config.{address,linkRoute,autoLink}
> ---
>
> Key: DISPATCH-342
> URL: https://issues.apache.org/jira/browse/DISPATCH-342
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Documentation
>Affects Versions: 0.6.0
>Reporter: Ted Ross
>Assignee: Ganesh Murthy
> Fix For: 0.6.0
>
>
> Three configuration entities: address, linkRoute, and autoLink are called
> out in the configuration doc with a prefix of router.config.
> This is incorrect syntax. The "router.config" should not be displayed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-342) qdrouterd.conf doc calls out router.config.{address,linkRoute,autoLink}
[
https://issues.apache.org/jira/browse/DISPATCH-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15299951#comment-15299951
]
ASF subversion and git services commented on DISPATCH-342:
--
Commit 42613e814cd3028a41a9b3bd94b41cdbab624a47 in qpid-dispatch's branch
refs/heads/master from [~ganeshmurthy]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=42613e8 ]
DISPATCH-342 - Remove the config router.config from address, link route and
auto link entities
> qdrouterd.conf doc calls out router.config.{address,linkRoute,autoLink}
> ---
>
> Key: DISPATCH-342
> URL: https://issues.apache.org/jira/browse/DISPATCH-342
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Documentation
>Affects Versions: 0.6.0
>Reporter: Ted Ross
>Assignee: Ganesh Murthy
> Fix For: 0.6.0
>
>
> Three configuration entities: address, linkRoute, and autoLink are called
> out in the configuration doc with a prefix of router.config.
> This is incorrect syntax. The "router.config" should not be displayed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-7264) Model attributes that are derived and secure (such as AutoGeneratedSelfSignedKeyStore) do not get stored encrypted causing Broker to fail on restart
[
https://issues.apache.org/jira/browse/QPID-7264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack resolved QPID-7264.
Resolution: Fixed
changes look good to me
> Model attributes that are derived and secure (such as
> AutoGeneratedSelfSignedKeyStore) do not get stored encrypted causing Broker
> to fail on restart
>
>
> Key: QPID-7264
> URL: https://issues.apache.org/jira/browse/QPID-7264
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2
>Reporter: Keith Wall
>Assignee: Lorenz Quack
>Priority: Minor
>
> Model Attributes that are derived/secure do not get encrypted by the
> configuration encryptor. If you add an {{AutoGeneratedSelfSignedCert}}
> then turn on encryption, the Broker continues to work until it is restarted,
> at which point it fails as it tries to read the secure value as if it were
> AES ciphered data.
> The only feature that currently has such an attribute is
> AutoGeneratedSelfSignedCert. This problem means that
> AutoGeneratedSelfSignedCert cannot be used at if configuration encrpytion is
> also in use.
> The work around is to create the self signed keystore externally
> (keytool/openssl etc), and import into Qpid as a Java or Non-Java Keystore.
> {noformat}
> 12:12:27.170 [main] INFO qpid.message.keystore.create - [Broker] KST-1001 :
> Create "myks"
> 12:12:27.595 [main] ERROR org.apache.qpid.server.Broker - Exception during
> startup
> java.lang.IllegalArgumentException: Unable to encrypt secret
> at
> org.apache.qpid.server.security.encryption.AESKeyFileEncrypter.decrypt(AESKeyFileEncrypter.java:106)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.decryptSecrets(AbstractConfiguredObject.java:2788)
> ~[classes/:na]
> at
> org.apache.qpid.server.store.GenericRecoverer.resolveObjects(GenericRecoverer.java:187)
> ~[classes/:na]
> at
> org.apache.qpid.server.store.GenericRecoverer.performRecover(GenericRecoverer.java:91)
> ~[classes/:na]
> at
> org.apache.qpid.server.store.GenericRecoverer.access$000(GenericRecoverer.java:41)
> ~[classes/:na]
> at
> org.apache.qpid.server.store.GenericRecoverer$1.execute(GenericRecoverer.java:59)
> ~[classes/:na]
> at
> org.apache.qpid.server.store.GenericRecoverer$1.execute(GenericRecoverer.java:55)
> ~[classes/:na]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:270)
> ~[classes/:na]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submitWrappedTask(TaskExecutorImpl.java:154)
> ~[classes/:na]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.run(TaskExecutorImpl.java:182)
> ~[classes/:na]
> at
> org.apache.qpid.server.store.GenericRecoverer.recover(GenericRecoverer.java:54)
> ~[classes/:na]
> at
> org.apache.qpid.server.store.BrokerStoreUpgraderAndRecoverer.perform(BrokerStoreUpgraderAndRecoverer.java:846)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractSystemConfig.activate(AbstractSystemConfig.java:232)
> ~[classes/:na]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[na:1.8.0_66]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:1.8.0_66]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:1.8.0_66]
> at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_66]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1309)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1288)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$8.onSuccess(AbstractConfiguredObject.java:909)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$8.onSuccess(AbstractConfiguredObject.java:903)
> ~[classes/:na]
> at com.google.common.util.concurrent.Futures$6.run(Futures.java:1319)
> ~[guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:457)
> ~[guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.ExecutionList.executeListener(ExecutionList.java:156)
> ~[guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.ExecutionList.add(ExecutionList.java:101)
> ~[guava-18.0.jar:na]
> at
>
[jira] [Commented] (QPID-7279) [Java Broker] with config encryption creating a JDBC VirtualHost fails
[
https://issues.apache.org/jira/browse/QPID-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15299889#comment-15299889
]
Lorenz Quack commented on QPID-7279:
Initially I thought this is related to the attribute being marked as secure
(and thus not only limited to JDBC VHs) but oddly creating a User which also
has a password field marked as secure succeeds.
I suspect that either they are somehow handled differently or the root cause is
a different one.
Further investigation needs to be conducted to find out the full scope of this
issue.
> [Java Broker] with config encryption creating a JDBC VirtualHost fails
> --
>
> Key: QPID-7279
> URL: https://issues.apache.org/jira/browse/QPID-7279
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Reporter: Lorenz Quack
>
> If configuration encryption is enabled on the broker creating a JDBC
> VirtualHost via the WMC fails with the following error:
> {{422 - Encrypted value is not valid Base 64 data: 'myPassword'}}
> Also we might not want to log the content of the invalid data due to its
> potential sensitive nature.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-7279) [Java Broker] with config encryption creating a JDBC VirtualHost fails
Lorenz Quack created QPID-7279:
--
Summary: [Java Broker] with config encryption creating a JDBC
VirtualHost fails
Key: QPID-7279
URL: https://issues.apache.org/jira/browse/QPID-7279
Project: Qpid
Issue Type: Bug
Components: Java Broker
Reporter: Lorenz Quack
If configuration encryption is enabled on the broker creating a JDBC
VirtualHost via the WMC fails with the following error:
{{422 - Encrypted value is not valid Base 64 data: 'myPassword'}}
Also we might not want to log the content of the invalid data due to its
potential sensitive nature.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-7278) [Java Broker] broker crashes when creating a JDBC VirtualHost with invalid JDBC Url
Lorenz Quack created QPID-7278:
--
Summary: [Java Broker] broker crashes when creating a JDBC
VirtualHost with invalid JDBC Url
Key: QPID-7278
URL: https://issues.apache.org/jira/browse/QPID-7278
Project: Qpid
Issue Type: Bug
Components: Java Broker
Reporter: Lorenz Quack
trying to create a JDBC VirtualHost with an invalid JDBC Url like
"jdbc://foo:bar" causes the broker to shutdown due to an uncaught
StoreException:
{code}
org.apache.qpid.server.store.StoreException: Failed to create message store
tables
at
org.apache.qpid.server.store.AbstractJDBCMessageStore.createOrOpenMessageStoreDatabase(AbstractJDBCMessageStore.java:311)
~[classes/:na]
at
org.apache.qpid.server.store.jdbc.GenericAbstractJDBCMessageStore.openMessageStore(GenericAbstractJDBCMessageStore.java:48)
~[classes/:na]
at
org.apache.qpid.server.virtualhost.AbstractVirtualHost.onActivate(AbstractVirtualHost.java:1877)
~[classes/:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
~[na:1.8.0_91]
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
~[na:1.8.0_91]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[na:1.8.0_91]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_91]
at
org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1309)
~[classes/:na]
at
org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1288)
~[classes/:na]
at
org.apache.qpid.server.model.AbstractConfiguredObject$8.onSuccess(AbstractConfiguredObject.java:909)
~[classes/:na]
at
org.apache.qpid.server.model.AbstractConfiguredObject$8.onSuccess(AbstractConfiguredObject.java:903)
~[classes/:na]
at com.google.common.util.concurrent.Futures$6.run(Futures.java:1319)
~[guava-18.0.jar:na]
at
com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:457)
~[guava-18.0.jar:na]
at
com.google.common.util.concurrent.ExecutionList.executeListener(ExecutionList.java:156)
~[guava-18.0.jar:na]
at
com.google.common.util.concurrent.ExecutionList.add(ExecutionList.java:101)
~[guava-18.0.jar:na]
at
com.google.common.util.concurrent.AbstractFuture.addListener(AbstractFuture.java:170)
~[guava-18.0.jar:na]
at
com.google.common.util.concurrent.Futures.addCallback(Futures.java:1322)
~[guava-18.0.jar:na]
at
com.google.common.util.concurrent.Futures.addCallback(Futures.java:1258)
~[guava-18.0.jar:na]
at
org.apache.qpid.server.model.AbstractConfiguredObject.doAttainState(AbstractConfiguredObject.java:902)
~[classes/:na]
at
org.apache.qpid.server.model.AbstractConfiguredObject.access$300(AbstractConfiguredObject.java:81)
~[classes/:na]
at
org.apache.qpid.server.model.AbstractConfiguredObject$1.execute(AbstractConfiguredObject.java:514)
~[classes/:na]
at
org.apache.qpid.server.model.AbstractConfiguredObject$1.execute(AbstractConfiguredObject.java:501)
~[classes/:na]
at
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:562)
~[classes/:na]
at
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:555)
~[classes/:na]
at
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:270)
~[classes/:na]
at
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:342)
~[classes/:na]
at java.security.AccessController.doPrivileged(Native Method)
~[na:1.8.0_91]
at javax.security.auth.Subject.doAs(Subject.java:360) ~[na:1.8.0_91]
at
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:335)
~[classes/:na]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
~[na:1.8.0_91]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
~[na:1.8.0_91]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
~[na:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]
Caused by: java.sql.SQLException: No suitable driver found for
jdbc://dfsdfdf:sadfsdf
at java.sql.DriverManager.getConnection(DriverManager.java:689)
~[na:1.8.0_91]
at java.sql.DriverManager.getConnection(DriverManager.java:247)
~[na:1.8.0_91]
at
org.apache.qpid.server.store.jdbc.DefaultConnectionProvider.getConnection(DefaultConnectionProvider.java:49)
~[classes/:na]
at
org.apache.qpid.server.store.jdbc.GenericJDBCMessageStore.getConnection(GenericJDBCMessageStore.java:121)
[jira] [Created] (QPIDJMS-181) Cannot connect Qpid-Broker using the SSL
Steven created QPIDJMS-181: -- Summary: Cannot connect Qpid-Broker using the SSL Key: QPIDJMS-181 URL: https://issues.apache.org/jira/browse/QPIDJMS-181 Project: Qpid JMS Issue Type: Bug Components: qpid-jms-client Affects Versions: 0.9.0 Environment: Windows7、jdk,the broker is in linux7.2 Reporter: Steven The below link address is Qpid latest Client API Documentation,https://qpid.apache.org/releases/qpid-jms-0.9.0/docs/index.html,According to its configuration with ssl,My Connection URL is connectionfactory.qpidConnectionfactory = amqps://QpidServer:5673?transport.trustStoreLocation=F:/AMQP/QpidSSL/clientts.jks=123456,It reported the following error: 2016-05-25 17:55:30,230 [main ] - ERROR JmsConnectionFactory - Failed to create JMS Provider instance for: amqps Caught exception, exiting. javax.jms.JMSException: Failed to create connection to: amqps://QpidServer:5673?transport.trustStoreLocation=F%253A%252FAMQP%252FQpidSSL%252Fclientts.jks=123456 at org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:66) at org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:172) at org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:161) at org.apache.qpid.jms.example.HelloWorld.test(HelloWorld.java:92) at org.apache.qpid.jms.example.HelloWorld.main(HelloWorld.java:73) Caused by: javax.net.ssl.SSLHandshakeException: General SSLEngine problem at sun.security.ssl.Handshaker.checkThrown(Unknown Source) at sun.security.ssl.SSLEngineImpl.checkTaskThrown(Unknown Source) at sun.security.ssl.SSLEngineImpl.readNetRecord(Unknown Source) at sun.security.ssl.SSLEngineImpl.unwrap(Unknown Source) at javax.net.ssl.SSLEngine.unwrap(Unknown Source) at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:927) at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:871) at io.netty.handler.ssl.SslHandler.decode(SslHandler.java:827) at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:228) at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:141) at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:340) at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:326) at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785) at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:116) at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:494) at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:461) at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:378) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:350) at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) at java.lang.Thread.run(Unknown Source) Caused by: javax.net.ssl.SSLHandshakeException: General SSLEngine problem at sun.security.ssl.Alerts.getSSLException(Unknown Source) at sun.security.ssl.SSLEngineImpl.fatal(Unknown Source) at sun.security.ssl.Handshaker.fatalSE(Unknown Source) at sun.security.ssl.Handshaker.fatalSE(Unknown Source) at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source) at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source) at sun.security.ssl.Handshaker.processLoop(Unknown Source) at sun.security.ssl.Handshaker$1.run(Unknown Source) at sun.security.ssl.Handshaker$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.security.ssl.Handshaker$DelegatedTask.run(Unknown Source) at io.netty.handler.ssl.SslHandler.runDelegatedTasks(SslHandler.java:960) at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:891) ... 13 more Caused by: java.security.cert.CertificateException: No name matching QpidServer found at sun.security.util.HostnameChecker.matchDNS(Unknown Source) at sun.security.util.HostnameChecker.match(Unknown Source) at sun.security.ssl.X509TrustManagerImpl.checkIdentity(Unknown Source) at sun.security.ssl.X509TrustManagerImpl.checkIdentity(Unknown Source) at sun.security.ssl.X509TrustManagerImpl.checkTrusted(Unknown Source) at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source) ... 22 more If I was using the following connection URL: connectionfactory.qpidConnectionfactory =
[jira] [Resolved] (QPID-7223) [Java Broker] Broker does not decrement consumer statistics "unacknowledgedBytes" and "unacknowledgedMessages" after receiving message.release command for 0.10 AMQP proto
[ https://issues.apache.org/jira/browse/QPID-7223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved QPID-7223. --- Resolution: Fixed I think this change looks good > [Java Broker] Broker does not decrement consumer statistics > "unacknowledgedBytes" and "unacknowledgedMessages" after receiving > message.release command for 0.10 AMQP protocol > - > > Key: QPID-7223 > URL: https://issues.apache.org/jira/browse/QPID-7223 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2 >Reporter: Alex Rudyy >Assignee: Rob Godfrey > > On receiving message.release command consumer statistics counters > "unacknowledgedBytes" and "unacknowledgedMessages" are not decremented -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7000) [Java Broker] Add synthetic VirtualHost which allows management of whole broker
[ https://issues.apache.org/jira/browse/QPID-7000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15299688#comment-15299688 ] ASF subversion and git services commented on QPID-7000: --- Commit 1745453 from [~godfrer] in branch 'java/trunk' [ https://svn.apache.org/r1745453 ] QPID-7000 : Avoid NPE when passed a null vhost name > [Java Broker] Add synthetic VirtualHost which allows management of whole > broker > --- > > Key: QPID-7000 > URL: https://issues.apache.org/jira/browse/QPID-7000 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > > Add a synthetic virtualhost / node which allows only access to $management to > allow for management of the whole broker. The $management node in other > virtual hosts should allow management only of the objects within the given > virtual host and connections associated with the vhost -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7203) Model loses audit information
[
https://issues.apache.org/jira/browse/QPID-7203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7203:
-
Status: Reviewable (was: In Progress)
> Model loses audit information
> --
>
> Key: QPID-7203
> URL: https://issues.apache.org/jira/browse/QPID-7203
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: 0.30, 0.32, qpid-java-6.0, qpid-java-6.0.1
>Reporter: Keith Wall
>Assignee: Keith Wall
> Fix For: qpid-java-6.1
>
>
> The Broker is supposed to save audit information on each object:
> {{createdBy}}, {{createdDate}}, {{lastUpdatedBy}}, {{lastUpdatedDate}}. This
> feature is broken and has been so since at least 0.30.
> The values are persisted properly to the message store, but on recovery, they
> only make it as far as the attribute map backing the configured object. The
> mechanics of ACO fails to reunite the attribute value with the field
> underlying each attribute. As a result the audit trail is unreliable.
> The problem would affect any storable derived attribute. Other storable
> derived attributes AutoGeneratedSelfSignedKeyStore and SiteSpecificTrustStore
> use {{postResolve}} to reunite the attribute with the field.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-7203) Model loses audit information
[
https://issues.apache.org/jira/browse/QPID-7203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall reassigned QPID-7203:
Assignee: Keith Wall
> Model loses audit information
> --
>
> Key: QPID-7203
> URL: https://issues.apache.org/jira/browse/QPID-7203
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: 0.30, 0.32, qpid-java-6.0, qpid-java-6.0.1
>Reporter: Keith Wall
>Assignee: Keith Wall
> Fix For: qpid-java-6.1
>
>
> The Broker is supposed to save audit information on each object:
> {{createdBy}}, {{createdDate}}, {{lastUpdatedBy}}, {{lastUpdatedDate}}. This
> feature is broken and has been so since at least 0.30.
> The values are persisted properly to the message store, but on recovery, they
> only make it as far as the attribute map backing the configured object. The
> mechanics of ACO fails to reunite the attribute value with the field
> underlying each attribute. As a result the audit trail is unreliable.
> The problem would affect any storable derived attribute. Other storable
> derived attributes AutoGeneratedSelfSignedKeyStore and SiteSpecificTrustStore
> use {{postResolve}} to reunite the attribute with the field.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7203) Model loses audit information
[
https://issues.apache.org/jira/browse/QPID-7203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7203:
-
Assignee: Lorenz Quack (was: Keith Wall)
> Model loses audit information
> --
>
> Key: QPID-7203
> URL: https://issues.apache.org/jira/browse/QPID-7203
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: 0.30, 0.32, qpid-java-6.0, qpid-java-6.0.1
>Reporter: Keith Wall
>Assignee: Lorenz Quack
> Fix For: qpid-java-6.1
>
>
> The Broker is supposed to save audit information on each object:
> {{createdBy}}, {{createdDate}}, {{lastUpdatedBy}}, {{lastUpdatedDate}}. This
> feature is broken and has been so since at least 0.30.
> The values are persisted properly to the message store, but on recovery, they
> only make it as far as the attribute map backing the configured object. The
> mechanics of ACO fails to reunite the attribute value with the field
> underlying each attribute. As a result the audit trail is unreliable.
> The problem would affect any storable derived attribute. Other storable
> derived attributes AutoGeneratedSelfSignedKeyStore and SiteSpecificTrustStore
> use {{postResolve}} to reunite the attribute with the field.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7203) Model loses audit information
[
https://issues.apache.org/jira/browse/QPID-7203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7203:
-
Fix Version/s: qpid-java-6.1
> Model loses audit information
> --
>
> Key: QPID-7203
> URL: https://issues.apache.org/jira/browse/QPID-7203
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: 0.30, 0.32, qpid-java-6.0, qpid-java-6.0.1
>Reporter: Keith Wall
> Fix For: qpid-java-6.1
>
>
> The Broker is supposed to save audit information on each object:
> {{createdBy}}, {{createdDate}}, {{lastUpdatedBy}}, {{lastUpdatedDate}}. This
> feature is broken and has been so since at least 0.30.
> The values are persisted properly to the message store, but on recovery, they
> only make it as far as the attribute map backing the configured object. The
> mechanics of ACO fails to reunite the attribute value with the field
> underlying each attribute. As a result the audit trail is unreliable.
> The problem would affect any storable derived attribute. Other storable
> derived attributes AutoGeneratedSelfSignedKeyStore and SiteSpecificTrustStore
> use {{postResolve}} to reunite the attribute with the field.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7203) Model loses audit information
[
https://issues.apache.org/jira/browse/QPID-7203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15299655#comment-15299655
]
ASF subversion and git services commented on QPID-7203:
---
Commit 1745450 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1745450 ]
QPID-7203: [Java Broker] Strengthen unit tests
> Model loses audit information
> --
>
> Key: QPID-7203
> URL: https://issues.apache.org/jira/browse/QPID-7203
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: 0.30, 0.32, qpid-java-6.0, qpid-java-6.0.1
>Reporter: Keith Wall
>
> The Broker is supposed to save audit information on each object:
> {{createdBy}}, {{createdDate}}, {{lastUpdatedBy}}, {{lastUpdatedDate}}. This
> feature is broken and has been so since at least 0.30.
> The values are persisted properly to the message store, but on recovery, they
> only make it as far as the attribute map backing the configured object. The
> mechanics of ACO fails to reunite the attribute value with the field
> underlying each attribute. As a result the audit trail is unreliable.
> The problem would affect any storable derived attribute. Other storable
> derived attributes AutoGeneratedSelfSignedKeyStore and SiteSpecificTrustStore
> use {{postResolve}} to reunite the attribute with the field.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-4397) C++ Broker Improve log statement for expired messages
[ https://issues.apache.org/jira/browse/QPID-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-4397. -- Resolution: Fixed Fix Version/s: qpid-cpp-next > C++ Broker Improve log statement for expired messages > - > > Key: QPID-4397 > URL: https://issues.apache.org/jira/browse/QPID-4397 > Project: Qpid > Issue Type: Improvement > Components: C++ Broker >Affects Versions: 0.18 >Reporter: Chuck Rolke >Assignee: Chuck Rolke > Fix For: qpid-cpp-next > > > Log statements for expired messages contain no information about what message > was expired. The proposal is to add something about the message to the log > statement. > Change: > QPID_LOG(debug, "Message expired from queue '" << name << "'"); > To: > QPID_LOG(debug, "Message '" << msg << "' expired from queue '" << name "'"); -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4397) C++ Broker Improve log statement for expired messages
[ https://issues.apache.org/jira/browse/QPID-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15299580#comment-15299580 ] ASF subversion and git services commented on QPID-4397: --- Commit 1745448 from [~gsim] in branch 'qpid/trunk' [ https://svn.apache.org/r1745448 ] QPID-4397: log more detail for expired messages when debug enabled > C++ Broker Improve log statement for expired messages > - > > Key: QPID-4397 > URL: https://issues.apache.org/jira/browse/QPID-4397 > Project: Qpid > Issue Type: Improvement > Components: C++ Broker >Affects Versions: 0.18 >Reporter: Chuck Rolke >Assignee: Chuck Rolke > > Log statements for expired messages contain no information about what message > was expired. The proposal is to add something about the message to the log > statement. > Change: > QPID_LOG(debug, "Message expired from queue '" << name << "'"); > To: > QPID_LOG(debug, "Message '" << msg << "' expired from queue '" << name "'"); -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
