Hello Gordon,
I have send the logs over email to you.
A few things : We are using mrg version 0.14; you re right about amq.fanout
would be better, but indeed we want to filter messages, it may be not
obvious from this example - a trivial one, but in the real scenario, an
amq.topic exchange is
On 11/21/2012 09:00 AM, eugene wrote:
Hello Gordon,
I have send the logs over email to you.
A few things : We are using mrg version 0.14; you re right about amq.fanout
would be better, but indeed we want to filter messages, it may be not
obvious from this example - a trivial one, but in the
Logs in the email again.
This is a bit confusing now. So, the queue gets deleted, the message goes to
the the amq.topic exchange.
Then it must be routed to the Topic that I have if the binding key and
routing key match.
I do have the binding ket set to : TEST_QUEUE, but there is no routing key
On 11/21/2012 09:51 AM, eugene wrote:
Logs in the email again.
This is a bit confusing now. So, the queue gets deleted, the message goes to
the the amq.topic exchange.
Then it must be routed to the Topic that I have if the binding key and
routing key match.
Yes, the routing through the
Just a sec, I think I've removed the exclusive myself during some tests,
today.
Sorry about this.
--
View this message in context:
http://apache-qpid-developers.2158895.n2.nabble.com/Alternate-Exchange-with-auto-delete-queue-tp7583361p7583389.html
Sent from the Apache Qpid developers mailing
On 11/21/2012 10:41 AM, eugene wrote:
Just a sec, I think I've removed the exclusive myself during some tests,
today.
That's good. Does it work if you add it back in? If not send me the logs
again. Thanks for your patience, we will get there in the end!
Oh darn. :)
You have stated the obvious here, but I somehow forgot about it in this mess
with routing/binding keys :
No, that will be done for you when you send it to the queue in the first .
Darn this is still not working for me.
Here is the consumer flow:
AMQTopic topic =
On 11/21/2012 11:29 AM, eugene wrote:
Darn this is still not working for me.
Here is the consumer flow:
AMQTopic topic = (AMQTopic)session.createTopic(amq.topic/TEST_QUEUE);
MessageConsumer consumer = session.createConsumer(topic);
consumer.setMessageListener(new MyMessageListener());
Yes sir!! connection.start() on the listener side fixed it. :)
This is still interesting, how come I got connected in the very first place
if connection.start() was not called...
Anyhow, the implementation in real case scenario is this: we have a bunch of
Services running around some
On 11/21/2012 01:05 PM, eugene wrote:
Yes sir!! connection.start() on the listener side fixed it. :)
This is still interesting, how come I got connected in the very first place
if connection.start() was not called...
The Connection.start() call is only strictly required for applications
with
[
https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13501970#comment-13501970
]
Robbie Gemmell commented on QPID-:
--
I'm not aware of any plans to do so, no.
[
https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13501973#comment-13501973
]
Robbie Gemmell commented on QPID-:
--
I'm going to resolve this JIRA now as it seems
[
https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved QPID-.
--
Resolution: Not A Problem
Java broker queue creation questions
On Nov. 21, 2012, 2:57 p.m., Andrew Stitcher wrote:
This is not an acceptable change to me. The problem is purely a windows one
and the assert provides a valuable check for the Unix platform.
Basically I think the windows implementation of PollableQueue is just wrong
- or rather
Gordon Sim created QPID-4452:
Summary: issuing and handling of producer credit not implemented
Key: QPID-4452
URL: https://issues.apache.org/jira/browse/QPID-4452
Project: Qpid
Issue Type: Bug
Hiram Chirino created QPID-4453:
---
Summary: ObjectMessage /w no body improperly converted to an AMQP
message.
Key: QPID-4453
URL: https://issues.apache.org/jira/browse/QPID-4453
Project: Qpid
I have three issues fixed that I would like to merge onto the release
branch for 0.20:
(1) QPID-4448[1]: fix credit checking on 0-10 path when message is of
1.0 format
(2) QPID-4451[2]: wait for outgoing messages to settle when closing
(3) QPID-4452[3]: fix credit for producers
Of these
[
https://issues.apache.org/jira/browse/QPID-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4453:
Attachment: QPID-4453.patch
attaching possible fix.
ObjectMessage /w no body
Hiram Chirino created QPID-4454:
---
Summary: getJMSReplyTo() != the value set with setJMSReplyTo()
Key: QPID-4454
URL: https://issues.apache.org/jira/browse/QPID-4454
Project: Qpid
Issue Type:
[
https://issues.apache.org/jira/browse/QPID-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4454:
Component/s: Java Client
getJMSReplyTo() != the value set with setJMSReplyTo()
[
https://issues.apache.org/jira/browse/QPID-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey reassigned QPID-4453:
-
Assignee: Rob Godfrey
ObjectMessage /w no body improperly converted to an AMQP message.
[
https://issues.apache.org/jira/browse/QPID-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey resolved QPID-4453.
---
Resolution: Fixed
Fix Version/s: 0.21
ObjectMessage /w no body improperly converted to an
Correction, JIRA: https://issues.apache.org/jira/browse/QPID-4453
On 21 November 2012 21:33, Rob Godfrey rob.j.godf...@gmail.com wrote:
I have one request for inclusion:
QPID-4453[1] : ObjectMessage /w no body improperly converted to an AMQP
message.
This change only affects the AMQP 1.0
Hiram Chirino created QPID-4455:
---
Summary: Queue browsers were not returning jms messages
Key: QPID-4455
URL: https://issues.apache.org/jira/browse/QPID-4455
Project: Qpid
Issue Type: Bug
[
https://issues.apache.org/jira/browse/QPID-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4455:
Attachment: QPID-4455.patch
attaching possible fix.
Queue browsers were not
[
https://issues.apache.org/jira/browse/QPID-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey updated QPID-4455:
--
Summary: [AMQP 1.0 JMS Client] Queue browsers were not returning jms
messages (was: Queue browsers
[
https://issues.apache.org/jira/browse/QPID-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey reassigned QPID-4455:
-
Assignee: Rob Godfrey
[AMQP 1.0 JMS Client] Queue browsers were not returning jms messages
[
https://issues.apache.org/jira/browse/QPID-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey resolved QPID-4455.
---
Resolution: Fixed
Fix Version/s: 0.21
[AMQP 1.0 JMS Client] Queue browsers were not
and another one (thanks to Hiram)
QPID-4455[1] : Queue browsers were not returning jms messages
Again this is isolated to the AMQP 1.0 JMS Client
-- Rob
[1] JIRA: https://issues.apache.org/jira/browse/QPID-4455
change on trunk: http://svn.apache.org/viewvc?view=revisionrevision=1412280
On
Robbie Gemmell created QPID-4456:
Summary: update the Java broker-only release package to account
for changes in plugin system
Key: QPID-4456
URL: https://issues.apache.org/jira/browse/QPID-4456
[
https://issues.apache.org/jira/browse/QPID-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4457:
Attachment: QPID-4457.patch
Attaching patch file the adds the joram test suite. Still needs work
Hiram Chirino created QPID-4457:
---
Summary: Test the against Joram JMS test suite.
Key: QPID-4457
URL: https://issues.apache.org/jira/browse/QPID-4457
Project: Qpid
Issue Type: Bug
On Nov. 21, 2012, 2:57 p.m., Andrew Stitcher wrote:
This is not an acceptable change to me. The problem is purely a windows one
and the assert provides a valuable check for the Unix platform.
Basically I think the windows implementation of PollableQueue is just wrong
- or rather
Robbie Gemmell created QPID-4458:
Summary: switch the velocity jar dependencies in gentools/lib to
being retrieved with ivy
Key: QPID-4458
URL: https://issues.apache.org/jira/browse/QPID-4458
[
https://issues.apache.org/jira/browse/QPID-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13502452#comment-13502452
]
Robbie Gemmell commented on QPID-4456:
--
Changes made in:
[
https://issues.apache.org/jira/browse/QPID-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13502467#comment-13502467
]
Robbie Gemmell commented on QPID-4458:
--
Change made at:
[
https://issues.apache.org/jira/browse/QPID-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell reassigned QPID-4458:
Assignee: Robbie Gemmell
switch the velocity jar dependencies in gentools/lib to being
37 matches
Mail list logo
