You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Christian Posta <ch...@gmail.com> on 2013/03/27 21:19:19 UTC
Re: Does the ">" destination wildcard require at least one character
preceding it?
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>.
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.