You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Jon Gorrono <jp...@ucdavis.edu> on 2015/02/03 00:34:51 UTC
freeing up prefetch, if that is what this is (which I doubt)
Greetings,
I'm a new sub and searched far a wide (including archives) for this but am
not hitting...
Scenario is pretty simple setup:
all localhost - consumer (nodejs) and broker (standalone 5.8.0)
A separate producer loaded up about 6000 message, all around 250K each into
a persistent queue
Day 1: in the web console, the number of messages 6192 and browsing there
shows a large number of them on the page...all looks good
Day 2: run a node client to retrieve messages using stomp protocol with
auto ack. Messages spew out to their own instance of a function handler at
a high rate... 400 messages in a very short time before I stop the client
Day 3: change the ack to client-individual and try to patch the client code
to ack (OG code overlooks that) and run a test... 3 messages are delivered
and delivery stops. I figured my code patch the nodejs library sukt and
kill the client.
But the console also only gets delivered 3 messages. I can delete one and
another takes its place.
Restarting activemq (and jetty) does not change anything: always just three.
I set no prefetch limits ... Default prefetch is 1000 afaik so that appears
to not be it.
I want to understand what is happening and use the goal of returning to
they way it was on Day 2 to do that.
Persistent sessions? What is going on here?
Regards
Logs for web console listing of queue contents:
2015-02-02 14:27:18,333 | DEBUG | localhost adding consumer:
ID:blah-53146-1422915407996-3:
1:1:2 for destination: queue://deltas_cmsapi |
org.apache.activemq.broker.region.AbstractRegion | ActiveMQ VMTransport:
vm://localhost#1-2
2015-02-02 14:27:18,336 | DEBUG | queue://deltas_cmsapi add sub:
QueueBrowserSubscription: consumer=ID:blah-53146-1422915407996-3:1:1:2,
destinations=0, dispatched=0, delivered=0, pending=0, dequeues: 0,
dispatched: 3, inflight: 0 | org.apache.activemq.broker.region.Queue |
ActiveMQ VMTransport: vm://localhost#1-2
2015-02-02 14:27:18,337 | DEBUG | deltas_cmsapi toPageIn: 200, Inflight: 0,
pagedInMessages.size 3, enqueueCount: 0, dequeueCount: 0 |
org.apache.activemq.broker.region.Queue | ActiveMQ BrokerService[localhost]
Task-5
2015-02-02 14:27:18,338 | DEBUG | dispatch to browser:
QueueBrowserSubscription: consumer=ID:blah-53146-1422915407996-3:1:1:2,
destinations=1, dispatched=0, delivered=0, pending=0, already
dispatched/paged count: 3 | org.apache.activemq.broker.region.Queue |
ActiveMQ BrokerService[localhost] Task-5
2015-02-02 14:27:18,340 | DEBUG | deltas_cmsapi toPageIn: 200, Inflight: 2,
pagedInMessages.size 3, enqueueCount: 0, dequeueCount: 0 |
org.apache.activemq.broker.region.Queue | ActiveMQ BrokerService[localhost]
Task-5
2015-02-02 14:27:18,340 | DEBUG | dispatch to browser:
QueueBrowserSubscription: consumer=ID:blah-53146-1422915407996-3:1:1:2,
destinations=1, dispatched=2, delivered=0, pending=0, already
dispatched/paged count: 3 | org.apache.activemq.broker.region.Queue |
ActiveMQ BrokerService[localhost] Task-5
2015-02-02 14:27:18,343 | DEBUG | deltas_cmsapi toPageIn: 200, Inflight: 1,
pagedInMessages.size 3, enqueueCount: 0, dequeueCount: 0 |
org.apache.activemq.broker.region.Queue | ActiveMQ BrokerService[localhost]
Task-6
2015-02-02 14:27:18,345 | DEBUG | deltas_cmsapi toPageIn: 200, Inflight: 0,
pagedInMessages.size 3, enqueueCount: 0, dequeueCount: 0 |
org.apache.activemq.broker.region.Queue | ActiveMQ BrokerService[localhost]
Task-6
2015-02-02 14:27:18,346 | DEBUG | remove:
ID:blah-53146-1422915407996-3:1:1:2, lastDeliveredSequenceId:454 |
org.apache.activemq.ActiveMQMessageConsumer | qtp1055629929-41
2015-02-02 14:27:18,347 | DEBUG | Unregistering MBean
org.apache.activemq:type=Broker,brokerName=localhost,destinationType=Queue,destinationName=deltas_cmsapi,endpoint=Consumer,clientId=ID_blah-53146-1422915407996-2_1,consumerId=ID_blah-53146-1422915407996-3_1_1_2
| org.apache.activemq.broker.jmx.ManagementContext | ActiveMQ VMTransport:
vm://localhost#1-2
2015-02-02 14:27:18,347 | DEBUG | localhost removing consumer:
ID:blah-53146-1422915407996-3:1:1:2 for destination: queue://deltas_cmsapi
| org.apache.activemq.broker.region.AbstractRegion | ActiveMQ VMTransport:
vm://localhost#1-2
--
Jon Gorrono
PGP Key: 0x5434509D - http{
pgp.mit.edu:11371/pks/lookup?search=0x5434509D&op=index}
http{middleware.ucdavis.edu}
Re: freeing up prefetch, if that is what this is (which I doubt)
Posted by Jon Gorrono <jp...@ucdavis.edu>.
I'd have to try a fresh install of AMQ and fill it up again... since I am
still seeing this behavior in the webconsole... nobody got time for that :)
I'll try to do that in the next several days, though when I think I have
the breathing room. The steps, in abstract, are really included in the
email:
get amq 5.8.0 (currently on macosx mavericks), run process to full up
queue... view in webconsole,, all messages viewable.
access with stomp client with 'auto' ack -> streams hundreds of messages,
webconsole reflects this, still show tons of messages
add client with 'client-individual' ack subscription, but not ack in
code.... run stomp client, get only three messages and AMQ blocks... look
in webconsole.... same, except without any page hanging: just three
messages.
add code to ack, streams all the messages I want, webconsole still only
showing three (not the same three, due to dequeueing.
I'll post back if I clean and jerk the server.
Thanks
On Fri, Feb 6, 2015 at 2:37 PM, artnaseef <ar...@artnaseef.com> wrote:
> That is very odd. Is it possible you can provide a test, or simple test
> steps that reproduces the problem reliably?
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/freeing-up-prefetch-if-that-is-what-this-is-which-I-doubt-tp4690897p4691189.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
Jon Gorrono
PGP Key: 0x5434509D - http{
pgp.mit.edu:11371/pks/lookup?search=0x5434509D&op=index}
http{middleware.ucdavis.edu}
Re: freeing up prefetch, if that is what this is (which I doubt)
Posted by artnaseef <ar...@artnaseef.com>.
That is very odd. Is it possible you can provide a test, or simple test
steps that reproduces the problem reliably?
--
View this message in context: http://activemq.2283324.n4.nabble.com/freeing-up-prefetch-if-that-is-what-this-is-which-I-doubt-tp4690897p4691189.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: freeing up prefetch, if that is what this is (which I doubt)
Posted by Jon Gorrono <jp...@ucdavis.edu>.
I switched to another nodejs module stomp client with ack abilities and the
whole queue seems to be accessible as long as I ack each message...
that's great, but it teaches me nothing about why the web console suddenly
started, and still, only shows the first (oldest) 3 messages in the queue
any insights welcome
Thanks
On Mon, Feb 2, 2015 at 3:34 PM, Jon Gorrono <jp...@ucdavis.edu> wrote:
>
>
> Greetings,
> I'm a new sub and searched far a wide (including archives) for this but am
> not hitting...
>
> Scenario is pretty simple setup:
> all localhost - consumer (nodejs) and broker (standalone 5.8.0)
>
> A separate producer loaded up about 6000 message, all around 250K each
> into a persistent queue
>
> Day 1: in the web console, the number of messages 6192 and browsing there
> shows a large number of them on the page...all looks good
>
> Day 2: run a node client to retrieve messages using stomp protocol with
> auto ack. Messages spew out to their own instance of a function handler at
> a high rate... 400 messages in a very short time before I stop the client
>
> Day 3: change the ack to client-individual and try to patch the client
> code to ack (OG code overlooks that) and run a test... 3 messages are
> delivered and delivery stops. I figured my code patch the nodejs library
> sukt and kill the client.
>
> But the console also only gets delivered 3 messages. I can delete one and
> another takes its place.
>
> Restarting activemq (and jetty) does not change anything: always just
> three.
>
> I set no prefetch limits ... Default prefetch is 1000 afaik so that
> appears to not be it.
>
> I want to understand what is happening and use the goal of returning to
> they way it was on Day 2 to do that.
>
> Persistent sessions? What is going on here?
>
> Regards
>
> Logs for web console listing of queue contents:
>
> 2015-02-02 14:27:18,333 | DEBUG | localhost adding consumer:
> ID:blah-53146-1422915407996-3:
> 1:1:2 for destination: queue://deltas_cmsapi |
> org.apache.activemq.broker.region.AbstractRegion | ActiveMQ VMTransport:
> vm://localhost#1-2
> 2015-02-02 14:27:18,336 | DEBUG | queue://deltas_cmsapi add sub:
> QueueBrowserSubscription: consumer=ID:blah-53146-1422915407996-3:1:1:2,
> destinations=0, dispatched=0, delivered=0, pending=0, dequeues: 0,
> dispatched: 3, inflight: 0 | org.apache.activemq.broker.region.Queue |
> ActiveMQ VMTransport: vm://localhost#1-2
> 2015-02-02 14:27:18,337 | DEBUG | deltas_cmsapi toPageIn: 200, Inflight:
> 0, pagedInMessages.size 3, enqueueCount: 0, dequeueCount: 0 |
> org.apache.activemq.broker.region.Queue | ActiveMQ BrokerService[localhost]
> Task-5
> 2015-02-02 14:27:18,338 | DEBUG | dispatch to browser:
> QueueBrowserSubscription: consumer=ID:blah-53146-1422915407996-3:1:1:2,
> destinations=1, dispatched=0, delivered=0, pending=0, already
> dispatched/paged count: 3 | org.apache.activemq.broker.region.Queue |
> ActiveMQ BrokerService[localhost] Task-5
> 2015-02-02 14:27:18,340 | DEBUG | deltas_cmsapi toPageIn: 200, Inflight:
> 2, pagedInMessages.size 3, enqueueCount: 0, dequeueCount: 0 |
> org.apache.activemq.broker.region.Queue | ActiveMQ BrokerService[localhost]
> Task-5
> 2015-02-02 14:27:18,340 | DEBUG | dispatch to browser:
> QueueBrowserSubscription: consumer=ID:blah-53146-1422915407996-3:1:1:2,
> destinations=1, dispatched=2, delivered=0, pending=0, already
> dispatched/paged count: 3 | org.apache.activemq.broker.region.Queue |
> ActiveMQ BrokerService[localhost] Task-5
> 2015-02-02 14:27:18,343 | DEBUG | deltas_cmsapi toPageIn: 200, Inflight:
> 1, pagedInMessages.size 3, enqueueCount: 0, dequeueCount: 0 |
> org.apache.activemq.broker.region.Queue | ActiveMQ BrokerService[localhost]
> Task-6
> 2015-02-02 14:27:18,345 | DEBUG | deltas_cmsapi toPageIn: 200, Inflight:
> 0, pagedInMessages.size 3, enqueueCount: 0, dequeueCount: 0 |
> org.apache.activemq.broker.region.Queue | ActiveMQ BrokerService[localhost]
> Task-6
> 2015-02-02 14:27:18,346 | DEBUG | remove:
> ID:blah-53146-1422915407996-3:1:1:2, lastDeliveredSequenceId:454 |
> org.apache.activemq.ActiveMQMessageConsumer | qtp1055629929-41
> 2015-02-02 14:27:18,347 | DEBUG | Unregistering MBean
> org.apache.activemq:type=Broker,brokerName=localhost,destinationType=Queue,destinationName=deltas_cmsapi,endpoint=Consumer,clientId=ID_blah-53146-1422915407996-2_1,consumerId=ID_blah-53146-1422915407996-3_1_1_2
> | org.apache.activemq.broker.jmx.ManagementContext | ActiveMQ VMTransport:
> vm://localhost#1-2
> 2015-02-02 14:27:18,347 | DEBUG | localhost removing consumer:
> ID:blah-53146-1422915407996-3:1:1:2 for destination: queue://deltas_cmsapi
> | org.apache.activemq.broker.region.AbstractRegion | ActiveMQ VMTransport:
> vm://localhost#1-2
>
>
> --
> Jon Gorrono
> PGP Key: 0x5434509D - http{
> pgp.mit.edu:11371/pks/lookup?search=0x5434509D&op=index}
> http{middleware.ucdavis.edu}
>
--
Jon Gorrono
PGP Key: 0x5434509D - http{
pgp.mit.edu:11371/pks/lookup?search=0x5434509D&op=index}
http{middleware.ucdavis.edu}