activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dejan Bosanac <de...@nighttale.net>
Subject Re: AMQ 5.2 no longer sets persistent header for STOMP
Date Tue, 28 Apr 2009 10:06:47 GMT
Hi Roger,

sounds like a bug. Can you file a Jira issue for this?

Cheers
--
Dejan Bosanac

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net


On Tue, Apr 28, 2009 at 7:48 AM, Roger Hoover <roger.hoover@gmail.com>wrote:

> Hi,
>
> In AMQ 4.1, if a message is persistent, the broker will pass a 'persistent'
> header with value 'true' when a message is consumed from a queue.  This is
> no longer the case in AMQ 5.2.  Is this a bug or a purposeful decision?
>
> Thanks,
>
> Roger
>
>
> #!/usr/bin/env perl
>
> use strict;
> use Net::Stomp;
> use Data::Dumper;
>
> my $stomp = Net::Stomp->new( { 'hostname' => 'localhost', 'port' => '61613'
> } );
> $stomp->connect( { 'login' => 'hello', 'passcode' => 'there' } );
>
> $stomp->send({ 'destination' => '/queue/testPersistence', 'body' => 'test',
> 'persistent' => 'true' } );
>
> $stomp->subscribe(
>  {   'destination'             => '/queue/testPersistence',
>      'ack'                   => 'client',
>      'activemq.prefetchSize' => 1
>  }
> );
> my $frame = $stomp->receive_frame();
> $stomp->ack({'frame' => $frame});
> print "Received frame: " . Dumper($frame);
> $stomp->disconnect();
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message