activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james.strac...@gmail.com>
Subject Re: "Queue is full" problem
Date Thu, 30 Mar 2006 08:34:24 GMT
Have you tried 4.0-RC1 yet?

http://people.apache.org/~chirino/incubator-activemq-4.0-RC1/

it looks like the issue you hit with M4 was a fairly trivial gremlin
caused while trying to register duplicate MBeans in JMX.

James

On 3/20/06, Danielius Jurna <danielius@elitnet.lt> wrote:
> Has anybody taken a look at these problems?
>
> I'd realy like to use ActiveMQ in our project becouse of it's unique features,
> but it seems version 4 is not there yet and version 3.2 has this "Queue is
> full" problem, which we cannot afford...
>
> > Several errors I'm getting from ActiveMQ 4.0-M4:
> >
> > 1. On first connect to activemq I'm getting this error on the client
> > (second time everything is fine.:
> > INFO  Service                        - Sync error occurred:
> > javax.management.InstanceAlreadyExistsException:
> > org.apache.activemq:Type=Queue,Destination=myQueue,BrokerName=localhost
> > javax.management.InstanceAlreadyExistsException:
> > org.apache.activemq:Type=Queue,Destination=myQueue,BrokerName=localhost
> >         at
> > com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySupport.java:4
> >52) at
> > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(De
> >faultMBeanServerInterceptor.java:1410) at
> > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(Defaul
> >tMBeanServerInterceptor.java:936) at
> > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(Default
> >MBeanServerInterceptor.java:337) at
> > com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:49
> >7) at
> > org.apache.activemq.broker.jmx.ManagedRegionBroker.register(ManagedRegionBr
> >oker.java:81) at
> > org.apache.activemq.broker.jmx.ManagedQueueRegion.createDestination(Managed
> >QueueRegion.java:55) at
> > org.apache.activemq.broker.region.AbstractRegion.addDestination(AbstractReg
> >ion.java:76) at
> > org.apache.activemq.broker.region.RegionBroker.addDestination(RegionBroker.
> >java:193) at
> > org.apache.activemq.broker.BrokerFilter.addDestination(BrokerFilter.java:12
> >3) at
> > org.apache.activemq.advisory.AdvisoryBroker.addDestination(AdvisoryBroker.j
> >ava:137) at
> > org.apache.activemq.broker.BrokerFilter.addDestination(BrokerFilter.java:12
> >3) at
> > org.apache.activemq.broker.MutableBrokerFilter.addDestination(MutableBroker
> >Filter.java:135) at
> > org.apache.activemq.broker.region.AbstractRegion.lookup(AbstractRegion.java
> >:214) at
> > org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:1
> >94) at
> > org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:309)
> >         at
> > org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:19
> >2) at org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:107) at
> > org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestina
> >tionBroker.java:97) at
> > org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.jav
> >a:119) at
> > org.apache.activemq.broker.AbstractConnection.processMessage(AbstractConnec
> >tion.java:336) at
> > org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:508)
> >         at
> > org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.ja
> >va:189) at
> > org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnect
> >ion.java:60) at
> > org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelat
> >or.java:82) at
> > org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.jav
> >a:68) at
> > org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNego
> >tiator.java:105) at
> > org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.j
> >ava:77) at
> > org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:136)
> >         at java.lang.Thread.run(Thread.java:595)
> >
> > 2. First I'm filling queue with as many messages as I can (I manage to put
> > about 40000 messages after what my sender blocks - which is normal I
> > guess). Then I start consumer and I get only about 1500 messages, after
> > what my consumer is locked. If I restart my consumer it receives again
> > about 1500 messages and locks. For the consumer I use jencs JCA container
> > which starts 10 message consumer threads. Seems like a problem in 4.0
> > activemq RA (3.2 was working as expected). Debug logs doesn't give any clue
> > (no error, no warning everything seems fine).
> >
> > > On 9 Mar 2006, at 10:36, Danielius Jurna wrote:
> > > > Hello.
> > > >
> > > > I'm running in the "Queue is full" problem (it is mentioned several
> > > > times in
> > > > this mailing list) - when queue is full, activemq stops delivering any
> > > > messages.
> > > > I've read, that in 4.0 this problem should be solved, but this
> > > > release is too
> > > > unstable to use in production (null pointer or class cast exceptions
> > > > occasionaly).
> > >
> > > Could you provide details? FWIW we've fixed the gremlins that caused
> > > ClassCastExceptions after extended periods of time.
> > >
> > > > Any plans to fix that for 3.2?
> > >
> > > No - the "queue is full" problem requires a major rework of the
> > > broker, which is what we did in 4.x
> > >
> > > James
> > > -------
> > > http://radio.weblogs.com/0112098/
>
> --
> ___________________________
> Danielius Jurna
> Senior Software Engineer
> ElitNet UAB
> Draugystes str. 19
> LT-51230 Kaunas, Lithuania
> Phone:  +370 37 352705
> Fax:    +370 37 352718
> e-mail: danielius@elitnet.lt
> http://www.elitnet.lt
>


--

James
-------
http://radio.weblogs.com/0112098/

Mime
View raw message