Hmm, to answer my own question
You need to do the following (in python, using stomp.py):
dest = '/temp-queue/my-temp-queue'
conn.start()
conn.connect()
conn.subscribe(destination=dest, ack='auto', headers={'persistent' :
'true'})
conn.send('test', destination=dest)
By se
Hi Dejan,
I've been looking in this area and think I see the problem.
When I create a consumer on a temp queue using STOMP, e.g.
/temp-queue/my-queue the broker creates an internal queue called, e.g.
/remote-temp-queue/ID:vtb-generic-51.cern.ch-58055-1255502987724-4:1:1
If I go and look via JMX
Oh I see. I didn't look at your example carefully enough. Thanks!
On Tue, Sep 8, 2009 at 11:04 AM, nmittal wrote:
>
> Roger, single connection is needed only in one script. So the requester
> would
> have one connection and the responder would have another. I was using 2
> connections in the r
Roger, single connection is needed only in one script. So the requester would
have one connection and the responder would have another. I was using 2
connections in the requester and that was breaking it. I think, temporary
queues are tied to a single instance of the connection.
thanks
Nishant
Hi Roger,
I agree with you. I'm not sure if that's the problem, it was just my first
guess looking at the code. Will take a look at it more closely and see if
there's a problem on a broker side.
Cheers
--
Dejan Bosanac
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://
Hi Dejan,
I'm not seeing how this feature is useful if you have to have a single
connection. Usually, the whole point of request/response, is to have the
request processed elsewhere by some other process (perhaps on another
machine) with it's own connection. If it only works on the same connecti
Dejan, you are right. It started working as soon as I used one connection.
thanks for your help.
NIshant
Dejan Bosanac wrote:
>
> Hi Nishant,
>
> just committed a test case that shows that stomp works nice with temp
> destinations
>
> here it is
>
> public void testTempDestination() thr
Hi Nishant,
just committed a test case that shows that stomp works nice with temp
destinations
here it is
public void testTempDestination() throws Exception {
String frame = "CONNECT\n" + "login: system\n" + "passcode:
manager\n\n" + Stomp.NULL;
stompConnection.sendFrame(fra
Dejan, Thanks for your reply. I have been trying that... I am trying with 2
stomp connections, one that subscribes to '/temp-queue/tq' and one that
sends a message to /queue/Queue.Data with reply to as the above temp-queue.
my client code is below..
my $stomp = Net::Stomp->new( { hostname => "192
Hi,
use /temp-topic/ or /temp-queue/ prefixes (instead of /topic/ and /queue/)
for destination names and ActiveMQ will create temporary destinations.
Cheers
--
Dejan Bosanac
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nig
10 matches
Mail list logo