You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by "Steve.V." <st...@sas.com> on 2013/01/30 21:46:11 UTC
Does the ">" destination wildcard require at least one character
preceding it?
Regarding the ">" destination
wildcard(http://activemq.apache.org/wildcards.html), I see an example in
http://activemq.apache.org/how-can-i-support-priority-queues.html where is
shows the use of just ">" when setting a destination policy for all queues.
Specifically, the example shows:
<policyEntry queue=">" prioritizedMessages="true"/>
Some testing on a couple of Solaris platforms works when I specify the
actual queue specifically when setting prioritizedMessages to true.
However, it does not when simply specifying ">" in attempt to set
prioritizedMessages to true for all queues.
Does the use of the ">"(recursively match any destination starting from this
name) wildcard require at least one character preceding the greater-than
sign?
-----
Stephen Vincent
--
View this message in context: http://activemq.2283324.n4.nabble.com/Does-the-destination-wildcard-require-at-least-one-character-preceding-it-tp4662468.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Does the ">" destination wildcard require at least one
character preceding it?
Posted by "Steve.V." <st...@sas.com>.
I feel sure that 5.9 invocation failure I mentioned in my last post was
caused by an incomplete extraction of the tar file. I was testing on an
UNIX box running HP-UX 11.31 and its tar command is old. It did not
accommodate the long path names. So, I downloaded the 04Apr 5.9 snapshot
and used gtar command to extract the tar file. In doing so, I was able to
get all of the files. :) I am able to run 5.9, but the bad news is that I
am still experiencing the same intermittent problem where sometimes messages
are dispatched to the consumer, but the MesssageServlet does not send them
in a GET response back to my RESTful API client.
-----
Stephen Vincent
--
View this message in context: http://activemq.2283324.n4.nabble.com/Does-the-destination-wildcard-require-at-least-one-character-preceding-it-tp4662468p4665571.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Does the ">" destination wildcard require at least one
character preceding it?
Posted by "Steve.V." <st...@sas.com>.
I attempted to test it with the 3/27 5.9 snapshot on a UNIX machine running
HP-UX 11.31, but it failed to start due to:
Loading message broker from: xbean:activemq.xml
INFO | Refreshing org.apache.activemq.xbean.XBeanBrokerFactory$1@89cc5e:
startup date [Mon Apr 01 12:57:29 EDT 2013]; root of context hierarchy
INFO | PListStore:[/users/sav/amq/59/data/localhost/tmp_storage] started
INFO | Using Persistence Adapter:
KahaDBPersistenceAdapter[/users/sav/amq/59/data/kahadb]
INFO | KahaDB is version 4
INFO | Recovering from the journal ...
INFO | Recovery replayed 8 operations from the journal in 0.178 seconds.
INFO | Apache ActiveMQ 5.9-SNAPSHOT (localhost,
ID:blah.blah.sas.com-61151-1364835456171-0:1) is starting
INFO | Listening for connections at:
tcp://blah.blah.sas.com:61616?maximumConnections=1000&wireFormat.maxFrameSize=104857600
INFO | Connector openwire Started
INFO | Listening for connections at:
amqp://blah.blah.sas.com:5672?maximumConnections=1000&wireFormat.maxFrameSize=104857600
INFO | Connector amqp Started
INFO | Apache ActiveMQ 5.9-SNAPSHOT (localhost,
ID:blah.blah.sas.com-61151-1364835456171-0:1) started
INFO | For help or more information please see: http://activemq.apache.org
WARN | Could not instantiate listener
org.apache.activemq.web.WebConsoleStarter
java.lang.ClassNotFoundException: org.apache.activemq.web.WebConsoleStarter
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at
org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:429)
at
org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:382)
...snip...
-----
Stephen Vincent
--
View this message in context: http://activemq.2283324.n4.nabble.com/Does-the-destination-wildcard-require-at-least-one-character-preceding-it-tp4662468p4665345.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Does the ">" destination wildcard require at least one
character preceding it?
Posted by "Steve.V." <st...@sas.com>.
Yes, I am still seeing problems. I have tested both 5.7 and 5.8. Sometimes,
messages are de-queued but don't make it to my RESTful client. I don't know
what happens to the messages when this occurs. I assume the consumer
created in the broker's JVM may get them, but my RESTful client's GET
request simply gets a 204 no-content.
-----
Stephen Vincent
--
View this message in context: http://activemq.2283324.n4.nabble.com/Does-the-destination-wildcard-require-at-least-one-character-preceding-it-tp4662468p4665343.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Does the ">" destination wildcard require at least one character
preceding it?
Posted by Christian Posta <ch...@gmail.com>.
Steve,
I'm still a bit curious about this one.
The tests I mentioned previously that were failing I have since found a
solution/explanation.
Are you still seeing the issues related to prioritized messages?
On Tue, Feb 5, 2013 at 8:57 PM, Steve.V. <st...@sas.com> wrote:
> Yes, I am using the default kahaDB as the broker store.
>
> My tests seem to run fine if I access a broker that is running on my PC,
> and
> I specify the prioritizedMessages="true" policy using the queue name
> instead
> of the ">" wildcard. However, they frequently encounter trouble when the
> broker is running on a UNIX box. More frequently on our UNIX boxes that
> run
> HP-UX and Linux.
>
> I just installed a local copy of the 05Feb snapshot of 5.8 on a box running
> HP-UX 11.31, and it failed on the twentieth iteration of the aforementioned
> test. I was thinking that most of my problems where being caused by
> having
> the persistence store on a network drive. While I see more trouble when it
> is on a network drive, recent tests are still failing frequently even when
> the store is local to the UNIX machine.
>
> The results from my tests against the 05Feb snapshot of 5.8 on a UNIX
> machine fail due to messages not being available but should have been. For
> some reason, they appear to be expiring. Here is an excerpt from the 5.8.0
> log:
>
> ...
> ...snip...
> 2013-02-05 22:46:10,041 | DEBUG | queue://testq expiring messages .. |
> org.apache.activemq.broker.region.Queue | ActiveMQ Broker[l
> ocalhost] Scheduler
> 2013-02-05 22:46:10,041 | DEBUG | testq toPageIn: 13, Inflight: 0,
> pagedInMessages.size 0, enqueueCount: 104, dequeueCount: 91 | o
> rg.apache.activemq.broker.region.Queue | ActiveMQ Broker[localhost]
> Scheduler
> 2013-02-05 22:46:10,042 | DEBUG | queue://testq expiring messages done. |
> org.apache.activemq.broker.region.Queue | ActiveMQ Broke
> r[localhost] Scheduler
> 2013-02-05 22:46:10,052 | DEBUG | testq toPageIn: 0, Inflight: 0,
> pagedInMessages.size 13, enqueueCount: 104, dequeueCount: 91 | o
> rg.apache.activemq.broker.region.Queue | ActiveMQ BrokerService[localhost]
> Task-1
> 2013-02-05 22:46:10,101 | DEBUG | Checkpoint started. |
> org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal Checkp
> oint Worker
> 2013-02-05 22:46:10,111 | DEBUG | queue://testq expiring messages .. |
> org.apache.activemq.broker.region.Queue | ActiveMQ Broker[l
> ocalhost] Scheduler
> 2013-02-05 22:46:10,111 | DEBUG | testq toPageIn: 0, Inflight: 0,
> pagedInMessages.size 13, enqueueCount: 104, dequeueCount: 91 | o
> rg.apache.activemq.broker.region.Queue | ActiveMQ Broker[localhost]
> Scheduler
> 2013-02-05 22:46:10,111 | DEBUG | queue://testq expiring messages done. |
> org.apache.activemq.broker.region.Queue | ActiveMQ Broke
> r[localhost] Scheduler
> 2013-02-05 22:46:10,111 | DEBUG | testq toPageIn: 0, Inflight: 0,
> pagedInMessages.size 13, enqueueCount: 104, dequeueCount: 91 | o
> rg.apache.activemq.broker.region.Queue | ActiveMQ BrokerService[localhost]
> Task-1
> 2013-02-05 22:46:10,202 | DEBUG | Checkpoint done. |
> org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal
> Checkpoin
> t Worker
> 2013-02-05 22:46:11,822 | DEBUG | created
> SCEP@18bff68{l(/10.24.8.124:58682)<->r(/10.24.8.124:8161
> ),d=false,open=true,ishut=false,
> oshut=false,rb=false,wb=false,w=true,i=0}-{AsyncHttpConnection@2d2da4
> ,g=HttpGenerator{s=0,h=-1,b=-1,c=-1},p=HttpParser{s=-14,l=0,c
> =0},r=0} | org.eclipse.jetty.io.nio | qtp3916193-28 Selector0
> 2013-02-05 22:46:11,823 | DEBUG | filled 294/294 |
> org.eclipse.jetty.http.HttpParser | qtp3916193-24
> 2013-02-05 22:46:11,823 | DEBUG | REQUEST /api/message on
> AsyncHttpConnection@2d2da4,g=HttpGenerator{s=0,h=-1,b=-1,c=-1},p=HttpPar
> ser{s=-5,l=5,c=0},r=1 | org.eclipse.jetty.server.Server | qtp3916193-24 -
> /api/message?destination=testq&type=queue&clientId=BFB20
> 400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeout=1
> 2013-02-05 22:46:11,823 | DEBUG | scope null||/api/message @
> o.e.j.w.WebAppContext{/admin,file:/c/bb04na2a/vol/home_tst/h6i94/sav/
> amq/58/webapps/admin/} | org.eclipse.jetty.server.handler.ContextHandler |
> qtp3916193-24 - /api/message?destination=testq&type=que
> ue&clientId=BFB20400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeout=1
> 2013-02-05 22:46:11,823 | DEBUG | scope null||/api/message @
> o.e.j.w.WebAppContext{/fileserver,file:/c/bb04na2a/vol/home_tst/h6i94
> /sav/amq/58/webapps/fileserver/} |
> org.eclipse.jetty.server.handler.ContextHandler | qtp3916193-24 -
> /api/message?destination=test
> q&type=queue&clientId=BFB20400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeout=1
> 2013-02-05 22:46:11,823 | DEBUG | scope null||/api/message @
> o.e.j.w.WebAppContext{/api,file:/c/bb04na2a/vol/home_tst/h6i94/sav/am
> q/58/webapps/api/} | org.eclipse.jetty.server.handler.ContextHandler |
> qtp3916193-24 - /api/message?destination=testq&type=queue&c
> lientId=BFB20400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeout=1
> 2013-02-05 22:46:11,824 | DEBUG | context=/api||/message @
> o.e.j.w.WebAppContext{/api,file:/c/bb04na2a/vol/home_tst/h6i94/sav/amq/
> 58/webapps/api/} | org.eclipse.jetty.server.handler.ContextHandler |
> qtp3916193-24 - /api/message?destination=testq&type=queue&cli
> entId=BFB20400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeout=1
> 2013-02-05 22:46:11,824 | DEBUG |
> sessionManager=org.eclipse.jetty.server.session.HashSessionManager@1c64ed8|
> org.eclipse.jetty.s
> erver.session | qtp3916193-24 -
>
> /api/message?destination=testq&type=queue&clientId=BFB20400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeou
> t=1
> 2013-02-05 22:46:11,824 | DEBUG | session=null |
> org.eclipse.jetty.server.session | qtp3916193-24 -
> /api/message?destination=testq
> &type=queue&clientId=BFB20400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeout=1
> 2013-02-05 22:46:11,824 | DEBUG | servlet /api|/message|null ->
> MessageServlet | org.eclipse.jetty.servlet.ServletHandler | qtp391
> 6193-24 -
>
> /api/message?destination=testq&type=queue&clientId=BFB20400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeout=1
> 2013-02-05 22:46:11,824 | DEBUG | chain=null |
> org.eclipse.jetty.servlet.ServletHandler | qtp3916193-24 -
> /api/message?destination
>
> =testq&type=queue&clientId=BFB20400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeout=1
> 2013-02-05 22:46:11,824 | DEBUG | Getting local client
> [BFB20400-700F-11E2-9D8E-0E72C1E2DF3C] | org.apache.activemq.web.MessageSer
> vlet | qtp3916193-24 -
>
> /api/message?destination=testq&type=queue&clientId=BFB20400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeout=1
> ...
> ...snip...
>
>
>
>
> -----
> Stephen Vincent
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Does-the-destination-wildcard-require-at-least-one-character-preceding-it-tp4662468p4662842.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta
Re: Does the ">" destination wildcard require at least one
character preceding it?
Posted by "Steve.V." <st...@sas.com>.
Yes, I am using the default kahaDB as the broker store.
My tests seem to run fine if I access a broker that is running on my PC, and
I specify the prioritizedMessages="true" policy using the queue name instead
of the ">" wildcard. However, they frequently encounter trouble when the
broker is running on a UNIX box. More frequently on our UNIX boxes that run
HP-UX and Linux.
I just installed a local copy of the 05Feb snapshot of 5.8 on a box running
HP-UX 11.31, and it failed on the twentieth iteration of the aforementioned
test. I was thinking that most of my problems where being caused by having
the persistence store on a network drive. While I see more trouble when it
is on a network drive, recent tests are still failing frequently even when
the store is local to the UNIX machine.
The results from my tests against the 05Feb snapshot of 5.8 on a UNIX
machine fail due to messages not being available but should have been. For
some reason, they appear to be expiring. Here is an excerpt from the 5.8.0
log:
...
...snip...
2013-02-05 22:46:10,041 | DEBUG | queue://testq expiring messages .. |
org.apache.activemq.broker.region.Queue | ActiveMQ Broker[l
ocalhost] Scheduler
2013-02-05 22:46:10,041 | DEBUG | testq toPageIn: 13, Inflight: 0,
pagedInMessages.size 0, enqueueCount: 104, dequeueCount: 91 | o
rg.apache.activemq.broker.region.Queue | ActiveMQ Broker[localhost]
Scheduler
2013-02-05 22:46:10,042 | DEBUG | queue://testq expiring messages done. |
org.apache.activemq.broker.region.Queue | ActiveMQ Broke
r[localhost] Scheduler
2013-02-05 22:46:10,052 | DEBUG | testq toPageIn: 0, Inflight: 0,
pagedInMessages.size 13, enqueueCount: 104, dequeueCount: 91 | o
rg.apache.activemq.broker.region.Queue | ActiveMQ BrokerService[localhost]
Task-1
2013-02-05 22:46:10,101 | DEBUG | Checkpoint started. |
org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal Checkp
oint Worker
2013-02-05 22:46:10,111 | DEBUG | queue://testq expiring messages .. |
org.apache.activemq.broker.region.Queue | ActiveMQ Broker[l
ocalhost] Scheduler
2013-02-05 22:46:10,111 | DEBUG | testq toPageIn: 0, Inflight: 0,
pagedInMessages.size 13, enqueueCount: 104, dequeueCount: 91 | o
rg.apache.activemq.broker.region.Queue | ActiveMQ Broker[localhost]
Scheduler
2013-02-05 22:46:10,111 | DEBUG | queue://testq expiring messages done. |
org.apache.activemq.broker.region.Queue | ActiveMQ Broke
r[localhost] Scheduler
2013-02-05 22:46:10,111 | DEBUG | testq toPageIn: 0, Inflight: 0,
pagedInMessages.size 13, enqueueCount: 104, dequeueCount: 91 | o
rg.apache.activemq.broker.region.Queue | ActiveMQ BrokerService[localhost]
Task-1
2013-02-05 22:46:10,202 | DEBUG | Checkpoint done. |
org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal
Checkpoin
t Worker
2013-02-05 22:46:11,822 | DEBUG | created
SCEP@18bff68{l(/10.24.8.124:58682)<->r(/10.24.8.124:8161),d=false,open=true,ishut=false,
oshut=false,rb=false,wb=false,w=true,i=0}-{AsyncHttpConnection@2d2da4,g=HttpGenerator{s=0,h=-1,b=-1,c=-1},p=HttpParser{s=-14,l=0,c
=0},r=0} | org.eclipse.jetty.io.nio | qtp3916193-28 Selector0
2013-02-05 22:46:11,823 | DEBUG | filled 294/294 |
org.eclipse.jetty.http.HttpParser | qtp3916193-24
2013-02-05 22:46:11,823 | DEBUG | REQUEST /api/message on
AsyncHttpConnection@2d2da4,g=HttpGenerator{s=0,h=-1,b=-1,c=-1},p=HttpPar
ser{s=-5,l=5,c=0},r=1 | org.eclipse.jetty.server.Server | qtp3916193-24 -
/api/message?destination=testq&type=queue&clientId=BFB20
400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeout=1
2013-02-05 22:46:11,823 | DEBUG | scope null||/api/message @
o.e.j.w.WebAppContext{/admin,file:/c/bb04na2a/vol/home_tst/h6i94/sav/
amq/58/webapps/admin/} | org.eclipse.jetty.server.handler.ContextHandler |
qtp3916193-24 - /api/message?destination=testq&type=que
ue&clientId=BFB20400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeout=1
2013-02-05 22:46:11,823 | DEBUG | scope null||/api/message @
o.e.j.w.WebAppContext{/fileserver,file:/c/bb04na2a/vol/home_tst/h6i94
/sav/amq/58/webapps/fileserver/} |
org.eclipse.jetty.server.handler.ContextHandler | qtp3916193-24 -
/api/message?destination=test
q&type=queue&clientId=BFB20400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeout=1
2013-02-05 22:46:11,823 | DEBUG | scope null||/api/message @
o.e.j.w.WebAppContext{/api,file:/c/bb04na2a/vol/home_tst/h6i94/sav/am
q/58/webapps/api/} | org.eclipse.jetty.server.handler.ContextHandler |
qtp3916193-24 - /api/message?destination=testq&type=queue&c
lientId=BFB20400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeout=1
2013-02-05 22:46:11,824 | DEBUG | context=/api||/message @
o.e.j.w.WebAppContext{/api,file:/c/bb04na2a/vol/home_tst/h6i94/sav/amq/
58/webapps/api/} | org.eclipse.jetty.server.handler.ContextHandler |
qtp3916193-24 - /api/message?destination=testq&type=queue&cli
entId=BFB20400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeout=1
2013-02-05 22:46:11,824 | DEBUG |
sessionManager=org.eclipse.jetty.server.session.HashSessionManager@1c64ed8 |
org.eclipse.jetty.s
erver.session | qtp3916193-24 -
/api/message?destination=testq&type=queue&clientId=BFB20400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeou
t=1
2013-02-05 22:46:11,824 | DEBUG | session=null |
org.eclipse.jetty.server.session | qtp3916193-24 -
/api/message?destination=testq
&type=queue&clientId=BFB20400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeout=1
2013-02-05 22:46:11,824 | DEBUG | servlet /api|/message|null ->
MessageServlet | org.eclipse.jetty.servlet.ServletHandler | qtp391
6193-24 -
/api/message?destination=testq&type=queue&clientId=BFB20400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeout=1
2013-02-05 22:46:11,824 | DEBUG | chain=null |
org.eclipse.jetty.servlet.ServletHandler | qtp3916193-24 -
/api/message?destination
=testq&type=queue&clientId=BFB20400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeout=1
2013-02-05 22:46:11,824 | DEBUG | Getting local client
[BFB20400-700F-11E2-9D8E-0E72C1E2DF3C] | org.apache.activemq.web.MessageSer
vlet | qtp3916193-24 -
/api/message?destination=testq&type=queue&clientId=BFB20400-700F-11E2-9D8E-0E72C1E2DF3C&readTimeout=1
...
...snip...
-----
Stephen Vincent
--
View this message in context: http://activemq.2283324.n4.nabble.com/Does-the-destination-wildcard-require-at-least-one-character-preceding-it-tp4662468p4662842.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Does the ">" destination wildcard require at least one character
preceding it?
Posted by Christian Posta <ch...@gmail.com>.
Just to make sure, you're using KahaDB as the broker store? The priority
groups are Low (<5), Medium (5) and High (>5). Individual numbers (eg, 9 or
7) are treated as "high" and are not differentiated. That is, you could see
7 before 9. But you shouldn't see 3 before 9.
On Tue, Feb 5, 2013 at 6:08 PM, Steve.V. <st...@sas.com> wrote:
> That last post didn't give you an idea of how many messages it takes
> before I
> see trouble. I have seen it fail after just a few iterations. So, I have
> seen it fail with under 200 messages.
>
>
>
> -----
> Stephen Vincent
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Does-the-destination-wildcard-require-at-least-one-character-preceding-it-tp4662468p4662833.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta
Re: Does the ">" destination wildcard require at least one
character preceding it?
Posted by "Steve.V." <st...@sas.com>.
That last post didn't give you an idea of how many messages it takes before I
see trouble. I have seen it fail after just a few iterations. So, I have
seen it fail with under 200 messages.
-----
Stephen Vincent
--
View this message in context: http://activemq.2283324.n4.nabble.com/Does-the-destination-wildcard-require-at-least-one-character-preceding-it-tp4662468p4662833.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Does the ">" destination wildcard require at least one
character preceding it?
Posted by "Steve.V." <st...@sas.com>.
No, just 13 messages, but I run the test over and over again. Most of the
time it is successful, but sometimes fails. It fails about 10 to 20% of the
time when the broker is running on a 64-bit UNIX machine running HP-UX
11.31.
The test first POSTs two messages with the default priority. Then POSTs 10
messages on the queue separately having priorities of 9, 8, 7, ... 1, and
0. Then POSTs one more message with the default priority. Finally, the
test GETs the messages off the queue.
Thanks,
Stephen V.
-----
Stephen Vincent
--
View this message in context: http://activemq.2283324.n4.nabble.com/Does-the-destination-wildcard-require-at-least-one-character-preceding-it-tp4662468p4662832.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Does the ">" destination wildcard require at least one character
preceding it?
Posted by Christian Posta <ch...@gmail.com>.
So I can recreate a priority message failure in our unit tests similar to
what you're describing. It may be different though, so I'll have to look
closer.
How many messages are you using to test to recreate your scenario? over 200
by chance?
On Fri, Feb 1, 2013 at 1:04 PM, Steve.V. <st...@sas.com> wrote:
> Well, my tester has encountered more prioritized message queue test
> failures
> even though she removed those prefetch=0 policies from the activemq.xml
> config file, and the failures are resolved if she uses a queue name when
> specifying the prioritizedMessages="true" policy, instead of attempting to
> use simply ">" for all queues.
>
> Btw, my REST client is very unhappy when I set consumer.prefetchSize=0 in
> "webapps/demo/WEB-INF/web.xml" via:
>
> <init-param>
> <param-name>destinationOptions</param-name>
> <param-value>consumer.prefetchSize=0</param-value>
> </init-param>
>
> Is that supported for REST API clients?
>
>
>
> -----
> Stephen Vincent
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Does-the-destination-wildcard-require-at-least-one-character-preceding-it-tp4662468p4662656.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta
Re: Does the ">" destination wildcard require at least one
character preceding it?
Posted by "Steve.V." <st...@sas.com>.
Well, my tester has encountered more prioritized message queue test failures
even though she removed those prefetch=0 policies from the activemq.xml
config file, and the failures are resolved if she uses a queue name when
specifying the prioritizedMessages="true" policy, instead of attempting to
use simply ">" for all queues.
Btw, my REST client is very unhappy when I set consumer.prefetchSize=0 in
"webapps/demo/WEB-INF/web.xml" via:
<init-param>
<param-name>destinationOptions</param-name>
<param-value>consumer.prefetchSize=0</param-value>
</init-param>
Is that supported for REST API clients?
-----
Stephen Vincent
--
View this message in context: http://activemq.2283324.n4.nabble.com/Does-the-destination-wildcard-require-at-least-one-character-preceding-it-tp4662468p4662656.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Does the ">" destination wildcard require at least one
character preceding it?
Posted by "Steve.V." <st...@sas.com>.
In summary, my test involves a queue where prioritizedMessages="true". I put
some messages with varying priorities on the queue, and then GET them off to
see if they are retrieved in order of highest priority. My test as a loop
doing that many times. When prefetch is zero, it doesn't take many
iterations before I start seeing some lower priority messages being
retrieved over higher priority messages. So, it seems that there is some
sort of conflict between prefetch=0 and prioritizedMessages="true". My
client app uses the REST API.
Is anyone else seeing that?
I am not sure why my tester added those prefetch entries to the activemq.xml
file. I suspect she may have added them at some point after noticing a
receiveNoWait() that didn't return a message when there were messages on the
queue. By default, my REST API client specifies readTimeout=1 if the
driving application doesn't specify a readTimeout parameter. So, I have
asked my tester to remove the prefetch=0 policy entries from the
activemq.xml config file.
-----
Stephen Vincent
--
View this message in context: http://activemq.2283324.n4.nabble.com/Does-the-destination-wildcard-require-at-least-one-character-preceding-it-tp4662468p4662530.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Does the ">" destination wildcard require at least one
character preceding it?
Posted by "Steve.V." <st...@sas.com>.
More testing indicates that the ">" by itself seems to be ok. It appears
that my test fails when the following is in the "activemq.xml" file:
<policyEntry queue=">" queuePrefetch="0"/>
<policyEntry queue=">" queueBrowserPrefetch="0"/>
If I remove those two lines, and keep:
<policyEntry queue=">" prioritizedMessages="true"/>
then my tests run fine.
-----
Stephen Vincent
--
View this message in context: http://activemq.2283324.n4.nabble.com/Does-the-destination-wildcard-require-at-least-one-character-preceding-it-tp4662468p4662500.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Does the ">" destination wildcard require at least one character
preceding it?
Posted by Christian Posta <ch...@gmail.com>.
aaah, interesting. okay, i'll try to find a solaris box and give it a shot
there.
On Wed, Jan 30, 2013 at 4:39 PM, Steve.V. <st...@sas.com> wrote:
> Version 5.7.0
>
> If it matters, I am specifying the destination policy in the
> "conf/activemq.xml" file that is being read when the server is started.
>
> When server is running on Windows, I don't see the problem. However, when
> I
> run the server on Solaris, I can reproduce the problem.
>
>
>
>
>
> -----
> Stephen Vincent
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Does-the-destination-wildcard-require-at-least-one-character-preceding-it-tp4662468p4662478.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta
Re: Does the ">" destination wildcard require at least one
character preceding it?
Posted by "Steve.V." <st...@sas.com>.
Version 5.7.0
If it matters, I am specifying the destination policy in the
"conf/activemq.xml" file that is being read when the server is started.
When server is running on Windows, I don't see the problem. However, when I
run the server on Solaris, I can reproduce the problem.
-----
Stephen Vincent
--
View this message in context: http://activemq.2283324.n4.nabble.com/Does-the-destination-wildcard-require-at-least-one-character-preceding-it-tp4662468p4662478.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Does the ">" destination wildcard require at least one character
preceding it?
Posted by Christian Posta <ch...@gmail.com>.
It shouldn't. I gave it a try in the unit tests on trunk (changing line 86
and 87 to ">":
http://svn.apache.org/viewvc/activemq/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/store/MessagePriorityTest.java?view=markup
What version are you using?
On Wed, Jan 30, 2013 at 1:46 PM, Steve.V. <st...@sas.com> wrote:
> Regarding the ">" destination
> wildcard(http://activemq.apache.org/wildcards.html), I see an example in
> http://activemq.apache.org/how-can-i-support-priority-queues.html where is
> shows the use of just ">" when setting a destination policy for all queues.
> Specifically, the example shows:
>
> <policyEntry queue=">" prioritizedMessages="true"/>
>
> Some testing on a couple of Solaris platforms works when I specify the
> actual queue specifically when setting prioritizedMessages to true.
> However, it does not when simply specifying ">" in attempt to set
> prioritizedMessages to true for all queues.
>
> Does the use of the ">"(recursively match any destination starting from
> this
> name) wildcard require at least one character preceding the greater-than
> sign?
>
>
>
> -----
> Stephen Vincent
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Does-the-destination-wildcard-require-at-least-one-character-preceding-it-tp4662468.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta