I'm in a PHP script.

On 20 November 2012 12:06, Dejan Bosanac <de...@nighttale.net> wrote:

> If it doesn't have to be REST, you can use JMX and JConsole to achieve the
> same.
>
> Regards
> --
> Dejan Bosanac
> ----------------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> dbosa...@redhat.com
> Twitter: @dejanb
> Blog: http://sensatic.net
> ActiveMQ in Action: http://www.manning.com/snyder/
>
>
> On Tue, Nov 20, 2012 at 1:00 PM, James Green <james.mk.gr...@gmail.com>
> wrote:
> > From the console works but has a session "secret" guid which changes
> every
> > few minutes. I have also tried visiting the "Queues" link within CURL
> then
> > visiting the delete link (without a "secret" parameter) without luck.
> >
> >
> > On 20 November 2012 11:51, Dejan Bosanac <de...@nighttale.net> wrote:
> >
> >> Can you try purging it from the web console?
> >>
> >> Regards
> >> --
> >> Dejan Bosanac
> >> ----------------------
> >> Red Hat, Inc.
> >> FuseSource is now part of Red Hat
> >> dbosa...@redhat.com
> >> Twitter: @dejanb
> >> Blog: http://sensatic.net
> >> ActiveMQ in Action: http://www.manning.com/snyder/
> >>
> >>
> >> On Tue, Nov 20, 2012 at 12:36 PM, James Green <james.mk.gr...@gmail.com
> >
> >> wrote:
> >> > Given my reading of that page, an HTTP DELETE on
> >> > http://10.0.0.123:8161/queue/inbound should delete the inbound
> queue...
> >> >
> >> > But I get a 404 instead. The page also talks about mapping but
> there's no
> >> > detail on that.
> >> >
> >> >
> >> >
> >> > On 20 November 2012 11:20, Gaurav Sharma <gaurav.cs.sha...@gmail.com>
> >> wrote:
> >> >
> >> >> Yes, see http://activemq.apache.org/rest.html
> >> >>
> >> >> On Nov 20, 2012, at 3:03, James Green <james.mk.gr...@gmail.com>
> wrote:
> >> >>
> >> >> > Trying to whip up a quick script to test performance.
> >> >> >
> >> >> > It would be really useful to call a URI to purge/delete the queue
> I'm
> >> >> using
> >> >> > between iterations without needing to manually drain it.
> >> >> >
> >> >> > Is there I URI pattern I can use?
> >> >> >
> >> >> > Thanks,
> >> >> >
> >> >> > James
> >> >>
> >>
>

Reply via email to