Thanks Rob & Robbie. That's quick stuff.
I did manage to do an ant build (was all a bit fingers-crossed, since I'd
never even touched subversion before - but it seemed to work), but it was
good to have the build from the experts to have to try too!
I will need to do some more testing tomorrow
I forced the nightly release job to run a little early, you should now find
binaries with the change included at:
https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Artefact-Release/lastSuccessfulBuild/artifact/trunk/qpid/java/amqp-1-0-client-jms/release/
Alternatively you can use the mave
OK, I've checked in a change to the trunk codebase so that the Qpid
DestinationImpl object no longer implements javax.jms.Queue and
javax.jms.Topic interfaces... I think this should help ActiveMQ to cope
with it...
If you want to test this you'll need to check out the source code from here:
http:
OK... looking up their code tree a bit I see why it gets confused by the
Qpid destination... because the Qpid AMQP 1.0 DestinationImpl implements
both Queue and Topic... I'm not sure why it does that (probably a
historical artefact). If I change that in Qpid, it might make ActiveMQ
happier...
--
Ah interesting... it's ActiveMQ code that is throwing the exception... As
per the JMS contract, the Qpid message producer is setting the
JMSDestination on the message it is sending (in this case a foreign
message, namely an ActiveMQ message). The ActiveMQ message class doesn't
seem to like having
Ok, I think I've found the solution to this.
I want to treat the period from recv to send to be transactional. So
here's what I've got:
pn_messenger_t * pMessenger...
pn_message_t * pMessage(pn_message());
... recv side ...
/* Set incoming window to 1 message */
pn_messenger_set_incoming_windo
Hi Rob,
Here is the stack trace. The line (72) in Listener.java (app code) that is
failing is just:
messageProducer2.send(msg);
where messageProducer2 is a MessageProducer from the Qpid connection/session,
and msg is just a “Message” which was received from Q1 just prior, via the
Openwire t
Hello,
I have two queues and a few services that receive from one queue (call it
"inbox") process the data received, then sends the processed data to the
other queue (call it "outbox"). Is there a sane way using proton to fetch
the content of the message from the "inbox", process the data, send t
Hello,
Where can I find example how to use proton-j api?
I would like to see how to configure ssl and sasl.
Piotr
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apac
Hi Mark,
On 19 February 2014 05:23, Mark Barker wrote:
> Thanks again to Rob and Robbie for their answers thus far!
>
> So I managed to slap (i.e. Frankenstein) together two pieces of
> example/client code in order to attempt to facilitate a bridge of sorts
> between two disparate queues.
>
> Fo
10 matches
Mail list logo
