queue full on activemq topic
Matthias L. Jugel
However, after some time I get this error about queue full on my
sending actors side. The activemq server sits on another computer so
there may be some network lag involved, but not that much.
Leo.
ERROR [20100907-14:14:42.295] Exception when invoking
actor [Actor[retweets-live:1284192023375]]
with message [start]
java.lang.IllegalStateException: Queue full
at java.util.AbstractQueue.add(AbstractQueue.java:71)
at
se.scalablesolutions.akka.dispatch.ExecutorBasedEventDrivenDispatcher.dispatch(ExecutorBasedEventDrivenDispatcher.scala:
81)
at
se.scalablesolutions.akka.dispatch.MessageInvocation.send(MessageHandling.scala:
33)
at
se.scalablesolutions.akka.actor.LocalActorRef.postMessageToMailbox(ActorRef.scala:
992)
at se.scalablesolutions.akka.actor.ScalaActorRef$class.
$bang(ActorRef.scala:1565)
at se.scalablesolutions.akka.actor.LocalActorRef.$bang(ActorRef.scala:
660)
at twire.server.reflector.LiveRetweetEventProducer$$anonfun$receive$1$
$anonfun$apply$1.apply(LiveRetweetEventProducer.scala:21)
at twire.server.reflector.LiveRetweetEventProducer$$anonfun$receive$1$
$anonfun$apply$1.apply(LiveRetweetEventProducer.scala:20)
at scala.collection.Iterator$class.foreach(Iterator.scala:631)
at twimpact.db.StreamReader.foreach(StreamReader.scala:24)
Viktor Klang
Is that a question? *confused*
Cheers,
--
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
--
Viktor Klang,
Code Connoisseur
Work: www.akkasource.com
Code: github.com/viktorklang
Follow: twitter.com/viktorklang
Read: klangism.tumblr.com
Matthias L. Jugel
should not come to a full queue if none is listening or am I
misunderstanding something here?
I have now updated to activemq 5.4.0 and camel 2.4.0 and until now the
problem has not occurred.
Leo.
On Sep 7, 3:08 pm, Viktor Klang <viktor.kl...@gmail.com> wrote:
> Hello Leo,
>
> Is that a question? *confused*
>
> Cheers,
>
> On Tue, Sep 7, 2010 at 2:58 PM, Matthias L. Jugel
> > .
Viktor Klang
I'll leave it at that and let some of the other awesome Akka committers chime in.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
Martin Krasser
assuming that you're using a producer actor similar to the following:
class MyProducer extends Actor with Producer with Oneway {
def endpointUri = "activemq:topic:retweets-live"
}
When you send a message to this actor with
myProducer ! "whatever"
then the "whatever" message is only added to the actors mailbox after
the ! method returned. Adding the message to the "retweets-live" topic
is done asynchronously. If adding messages to an ActiveMQ topic is much
slower (or not possible at all) than adding messages to the actor's
mailbox, then the mailbox can grow to its maximum size, leading to an
exception that you reported.
If you want to wait for the producer actor to add the message to the
topic, then you'll need to use !!:
myProducer !! "whatever"
and instruct the actor to reply to the original sender (which is not
done by default when the producer actor implements Oneway)
class MyProducer extends Actor with Producer with Oneway {
def endpointUri = "activemq:topic:retweets-live"
override protected def receiveAfterProduce = {
case msg => self.reply("message added to topic")
}
}
In this case the producer actor's mailbox will not grow (but messages
still might pile up somewhere else). Does that help?
Cheers,
Martin
Matthias L. Jugel schrieb:
--
Martin Krasser
blog: http://krasserm.blogspot.com
code: http://github.com/krasserm
twitter: http://twitter.com/mrt1nz
Viktor Klang
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
Martin Krasser
> Nicely explained Martin, thanks!
Thanks. Will try to find some time to add this to the akka-camel docs.
> <mailto:viktor.kl...@gmail.com>> wrote:
>
>
> Hello Leo,
>
> Is that a question? *confused*
>
> Cheers,
>
> On Tue, Sep 7, 2010 at 2:58 PM, Matthias L. Jugel
> <matthias.ju...@gmail.com
> <mailto:matthias.ju...@gmail.com>>wrote:
> <mailto:akka...@googlegroups.com>.
> To unsubscribe from this group, send email to
> akka-user+...@googlegroups.com
> <mailto:akka-user%2Bunsu...@googlegroups.com><akka-user%2Bunsubscribe@googlegroups
> .com>
> .
> For more options, visit this group at
> http://groups.google.com/group/akka-user?hl=en.
>
>
> --
> Viktor Klang,
> Code Connoisseur
> Work: www.akkasource.com <http://www.akkasource.com>
> Code: github.com/viktorklang <http://github.com/viktorklang>
> Follow: twitter.com/viktorklang
> <http://twitter.com/viktorklang>
> Read: klangism.tumblr.com <http://klangism.tumblr.com>
>
>
>
>
>
>
>
> --
> Martin Krasser
>
> blog: http://krasserm.blogspot.com
> code: http://github.com/krasserm
> twitter: http://twitter.com/mrt1nz
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Akka User List" group.
> To post to this group, send email to akka...@googlegroups.com
> <mailto:akka...@googlegroups.com>.
> To unsubscribe from this group, send email to
> akka-user+...@googlegroups.com
> <mailto:akka-user%2Bunsu...@googlegroups.com>.
> For more options, visit this group at
> http://groups.google.com/group/akka-user?hl=en.
>
>
>
>
> --
> Viktor Klang,
> Code Connoisseur
> Work: www.akkasource.com <http://www.akkasource.com>
> Code: github.com/viktorklang <http://github.com/viktorklang>
> Follow: twitter.com/viktorklang <http://twitter.com/viktorklang>
> Read: klangism.tumblr.com <http://klangism.tumblr.com>
Viktor Klang
Viktor Klang schrieb:
Nicely explained Martin, thanks!
Thanks. Will try to find some time to add this to the akka-camel docs.
On the topic of mailboxes, here's what I'm currently working on:
http://github.com/jboner/akka/blob/safe_mailboxes/akka-actor/src/main/scala/dispatch/MessageHandling.scala#L73
Martin Krasser
>
>
> On Wed, Sep 8, 2010 at 8:53 PM, Martin Krasser
> <kras...@googlemail.com <mailto:kras...@googlemail.com>> wrote:
>
> Viktor Klang schrieb:
>
> Nicely explained Martin, thanks!
>
>
> Thanks. Will try to find some time to add this to the akka-camel docs.
>
>
> On the topic of mailboxes, here's what I'm currently working on:
> http://github.com/jboner/akka/blob/safe_mailboxes/akka-actor/src/main/scala/dispatch/MessageHandling.scala#L73
Like it. Maybe a high pushTimeOut value is an even better solution in
this case than using !! and an overriden receiveAfterProduce. Will wait
for your work to get into master to play with it and defer documentation.
>
>
>
>
> On Wed, Sep 8, 2010 at 8:36 PM, Martin Krasser
> <kras...@googlemail.com <mailto:kras...@googlemail.com>
> <mailto:kras...@googlemail.com
> <mailto:viktor.kl...@gmail.com
> <mailto:viktor.kl...@gmail.com>>> wrote:
>
> Hello Leo,
>
> Is that a question? *confused*
>
> Cheers,
>
> On Tue, Sep 7, 2010 at 2:58 PM, Matthias L. Jugel
> <matthias.ju...@gmail.com
> <mailto:matthias.ju...@gmail.com>
> <mailto:matthias.ju...@gmail.com
> <mailto:akka...@googlegroups.com
> <mailto:akka...@googlegroups.com>>.
>
> To unsubscribe from this group, send email to
> akka-user+...@googlegroups.com
> <mailto:akka-user%2Bunsu...@googlegroups.com>
>
> <mailto:akka-user%2Bunsu...@googlegroups.com
> <mailto:akka-user%252Buns...@googlegroups.com>><akka-user%2Bunsubscribe@googlegroups
>
>
> .com>
> .
> For more options, visit this group at
> http://groups.google.com/group/akka-user?hl=en.
>
> --
> Viktor Klang,
> Code Connoisseur
> Work: www.akkasource.com
> <http://www.akkasource.com> <http://www.akkasource.com>
> Code: github.com/viktorklang
> <http://github.com/viktorklang> <http://github.com/viktorklang>
> Follow: twitter.com/viktorklang
> <http://twitter.com/viktorklang>
> <http://twitter.com/viktorklang>
> Read: klangism.tumblr.com
> <http://klangism.tumblr.com> <http://klangism.tumblr.com>
>
>
>
>
>
>
> -- Martin Krasser
>
> blog: http://krasserm.blogspot.com
> code: http://github.com/krasserm
> twitter: http://twitter.com/mrt1nz
>
>
> -- You received this message because you are subscribed
> to the Google
> Groups "Akka User List" group.
> To post to this group, send email to
> akka...@googlegroups.com <mailto:akka...@googlegroups.com>
> <mailto:akka...@googlegroups.com
> <mailto:akka...@googlegroups.com>>.
>
> To unsubscribe from this group, send email to
> akka-user+...@googlegroups.com
> <mailto:akka-user%2Bunsu...@googlegroups.com>
> <mailto:akka-user%2Bunsu...@googlegroups.com
> <mailto:akka-user%252Buns...@googlegroups.com>>.
>
> For more options, visit this group at
> http://groups.google.com/group/akka-user?hl=en.
>
>
>
>
> --
> Viktor Klang,
> Code Connoisseur
> Work: www.akkasource.com <http://www.akkasource.com>
> <http://www.akkasource.com>
> Code: github.com/viktorklang <http://github.com/viktorklang>
> <http://github.com/viktorklang>
> Follow: twitter.com/viktorklang
> <http://twitter.com/viktorklang> <http://twitter.com/viktorklang>
> Read: klangism.tumblr.com <http://klangism.tumblr.com>
> <http://klangism.tumblr.com>
>
>
> --
> You received this message because you are subscribed to the
> Google Groups "Akka User List" group.
> To post to this group, send email to
Viktor Klang
Viktor Klang schrieb:Like it. Maybe a high pushTimeOut value is an even better solution in this case than using !! and an overriden receiveAfterProduce. Will wait for your work to get into master to play with it and defer documentation.
On Wed, Sep 8, 2010 at 8:53 PM, Martin Krasser <kras...@googlemail.com <mailto:kras...@googlemail.com>> wrote:
Viktor Klang schrieb:
Nicely explained Martin, thanks!
Thanks. Will try to find some time to add this to the akka-camel docs.
On the topic of mailboxes, here's what I'm currently working on:
http://github.com/jboner/akka/blob/safe_mailboxes/akka-actor/src/main/scala/dispatch/MessageHandling.scala#L73
A high pushTimeout would mean blocking the sender until timeout, which could be dangerous if set high, having a 1-2 second push timeout could help alleviate the pressure on the producer. WDYT?
Jonas Bonér
--
Jonas Bonér
Specialist at Large
http://akkasource.org
twtr: @jboner
"Viktor Klang" <viktor...@gmail.com> wrote:
>>> akka-user+...@googlegroups.com<akka-user%2Bunsu...@googlegroups.com>
>>> <mailto:akka-user%2Bunsu...@googlegroups.com<akka-user%252Buns...@googlegroups.com>
>>> ><akka-user%2Bunsubscribe@googlegroups
>>>
>>> .com>
>>> .
>>> For more options, visit this group at
>>> http://groups.google.com/group/akka-user?hl=en.
>>>
>>> --
>>> Viktor Klang,
>>> Code Connoisseur
>>> Work: www.akkasource.com <http://www.akkasource.com>
>>> Code: github.com/viktorklang <http://github.com/viktorklang>
>>> Follow: twitter.com/viktorklang
>>> <http://twitter.com/viktorklang>
>>> Read: klangism.tumblr.com <http://klangism.tumblr.com>
>>>
>>>
>>>
>>>
>>>
>>>
>>> -- Martin Krasser
>>>
>>> blog: http://krasserm.blogspot.com
>>> code: http://github.com/krasserm
>>> twitter: http://twitter.com/mrt1nz
>>>
>>>
>>> -- You received this message because you are subscribed to the
>>> Google
>>> Groups "Akka User List" group.
>>> To post to this group, send email to akka...@googlegroups.com
>>> <mailto:akka...@googlegroups.com>.
>>>
>>> To unsubscribe from this group, send email to
>>> akka-user+...@googlegroups.com<akka-user%2Bunsu...@googlegroups.com>
>>> <mailto:akka-user%2Bunsu...@googlegroups.com<akka-user%252Buns...@googlegroups.com>
>>> >.
>>>
>>> For more options, visit this group at
>>> http://groups.google.com/group/akka-user?hl=en.
>>>
>>>
>>>
>>>
>>> --
>>> Viktor Klang,
>>> Code Connoisseur
>>> Work: www.akkasource.com <http://www.akkasource.com>
>>> Code: github.com/viktorklang <http://github.com/viktorklang>
>>> Follow: twitter.com/viktorklang <http://twitter.com/viktorklang>
>>> Read: klangism.tumblr.com <http://klangism.tumblr.com>
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Akka User List" group.
>>> To post to this group, send email to akka...@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> akka-user+...@googlegroups.com<akka-user%2Bunsu...@googlegroups.com>
>>> .
>>> For more options, visit this group at
>>> http://groups.google.com/group/akka-user?hl=en.
>>>
>>
>>
>> --
>> Martin Krasser
>>
>> blog: http://krasserm.blogspot.com
>> code: http://github.com/krasserm
>> twitter: http://twitter.com/mrt1nz
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Akka User List" group.
>> To post to this group, send email to akka...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> akka-user+...@googlegroups.com<akka-user%2Bunsu...@googlegroups.com>
>> .
>> For more options, visit this group at
>> http://groups.google.com/group/akka-user?hl=en.
>>
>>
>
>
>--
>Viktor Klang,
>Code Connoisseur
>Work: www.akkasource.com
>Code: github.com/viktorklang
>Follow: twitter.com/viktorklang
>Read: klangism.tumblr.com
>
Martin Krasser
>
>
> On Wed, Sep 8, 2010 at 9:07 PM, Martin Krasser
>
> Viktor Klang schrieb:
>
>
>
> On Wed, Sep 8, 2010 at 8:53 PM, Martin Krasser
> <kras...@googlemail.com <mailto:kras...@googlemail.com>
> <mailto:kras...@googlemail.com>>> wrote:
>
> Viktor Klang schrieb:
>
> Nicely explained Martin, thanks!
>
>
> Thanks. Will try to find some time to add this to the
> akka-camel docs.
>
>
> On the topic of mailboxes, here's what I'm currently working on:
> http://github.com/jboner/akka/blob/safe_mailboxes/akka-actor/src/main/scala/dispatch/MessageHandling.scala#L73
>
>
> Like it. Maybe a high pushTimeOut value is an even better solution
> in this case than using !! and an overriden receiveAfterProduce.
> Will wait for your work to get into master to play with it and
> defer documentation.
>
>
> A high pushTimeout would mean blocking the sender until timeout, which
> could be dangerous if set high, having a 1-2 second push timeout could
> help alleviate the pressure on the producer. WDYT?
I was thinking about a pushTimout value of 2*x where x is the average
time for adding a message to a certain ActiveMQ topic. But that was only
a first thought, not sure if it's a good starting point.
> <mailto:akka-user%2Bunsu...@googlegroups.com
> <mailto:akka-user%252Buns...@googlegroups.com>
> <mailto:akka-user%252Buns...@googlegroups.com
> <mailto:akka-user%25252Bun...@googlegroups.com>>><akka-user%2Bunsubscribe@googlegroups
> <mailto:akka...@googlegroups.com
> <mailto:akka...@googlegroups.com>
> <mailto:akka...@googlegroups.com
> <mailto:akka...@googlegroups.com>>>.
>
> To unsubscribe from this group, send email to
> akka-user+...@googlegroups.com
> <mailto:akka-user%2Bunsu...@googlegroups.com>
> <mailto:akka-user%2Bunsu...@googlegroups.com
> <mailto:akka-user%252Buns...@googlegroups.com>>
> <mailto:akka-user%2Bunsu...@googlegroups.com
> <mailto:akka-user%252Buns...@googlegroups.com>
> <mailto:akka-user%252Buns...@googlegroups.com
> <mailto:akka-user%25252Bun...@googlegroups.com>>>.
>
>
> For more options, visit this group at
> http://groups.google.com/group/akka-user?hl=en.
>
>
>
>
> -- Viktor Klang,
> Code Connoisseur
> Work: www.akkasource.com <http://www.akkasource.com>
> <http://www.akkasource.com>
> <http://www.akkasource.com>
> Code: github.com/viktorklang
> <http://github.com/viktorklang> <http://github.com/viktorklang>
> <http://github.com/viktorklang>
> Follow: twitter.com/viktorklang
> <http://twitter.com/viktorklang>
> <http://twitter.com/viktorklang>
> <http://twitter.com/viktorklang>
>
> Read: klangism.tumblr.com
> <http://klangism.tumblr.com> <http://klangism.tumblr.com>
> <http://klangism.tumblr.com>
>
>
> -- You received this message because you are
> subscribed to the
> Google Groups "Akka User List" group.
> To post to this group, send email to
> akka...@googlegroups.com
> <mailto:akka...@googlegroups.com>
Matthias L. Jugel
I selected the !! operation fix as it gives me some flow control.
Thanks,
Leo.
On Sep 9, 7:12 am, Martin Krasser <krass...@googlemail.com> wrote:
> Viktor Klang schrieb:
>
>
>
>
>
>
>
>
>
>
>
> > <krass...@googlemail.com <mailto:krass...@googlemail.com>> wrote:
>
> > Viktor Klang schrieb:
>
> > On Wed, Sep 8, 2010 at 8:53 PM, Martin Krasser
> > <mailto:krass...@googlemail.com
>
> > Viktor Klang schrieb:
>
> > Nicely explained Martin, thanks!
>
> > Thanks. Will try to find some time to add this to the
> > akka-camel docs.
>
> > On the topic of mailboxes, here's what I'm currently working on:
> > Like it. Maybe a high pushTimeOut value is an even better solution
> > in this case than using !! and an overriden receiveAfterProduce.
> > Will wait for your work to get into master to play with it and
> > defer documentation.
>
> > A high pushTimeout would mean blocking the sender until timeout, which
> > could be dangerous if set high, having a 1-2 second push timeout could
> > help alleviate the pressure on the producer. WDYT?
>
> I was thinking about a pushTimout value of 2*x where x is the average
> time for adding a message to a certain ActiveMQ topic. But that was only
> a first thought, not sure if it's a good starting point.
>
>
>
>
>
>
>
>
>
> > On Wed, Sep 8, 2010 at 8:36 PM, Martin Krasser
> > <mailto:krass...@googlemail.com>
> > <mailto:krass...@googlemail.com <mailto:krass...@googlemail.com>>
> > <mailto:krass...@googlemail.com
> > <mailto:krass...@googlemail.com>
>
> > <mailto:krass...@googlemail.com
>
> read more »
√iktor Klang
Has there been any update on this? I did have other items to work on.
I selected the !! operation fix as it gives me some flow control.
What's your mailbox capacity set to?
What version of Akka are you using?
Have you've tried using push-timeout?
Cheers,
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
--
Matthias L. Jugel
on coding.
Actually, I use the defaults (the docs say unbounded mailbox). It is
akka 0.10.
Leo.
On Oct 8, 10:05 am, √iktor Klang <viktor.kl...@gmail.com> wrote:
> On Fri, Oct 8, 2010 at 9:13 AM, Matthias L. Jugel
> <matthias.ju...@gmail.com>wrote:
> > > > <mailto:akka...@googlegroups.com>...
>
> read more »
√iktor Klang
Sorry for the delay, I was not looking into the ML recently and kept
on coding.
Actually, I use the defaults (the docs say unbounded mailbox). It is
akka 0.10.
Hi Leo,
can you verify whether it works on 1.0-SNAPSHOT (master) or not?
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
Matthias L. Jugel
compile 2.7.7. and then fails to find scala-library 2.7.7 in my local
maven2 repo. I don't understand why it does not even try to
download...
champloo:akka leo$ sbt update
Getting Scala 2.7.7 ...
downloading http://repo1.maven.org/maven2/org/scala-lang/scala-compiler/2.7.7/scala-compiler-2.7.7.jar
...
[SUCCESSFUL ] org.scala-lang#scala-compiler;2.7.7!scala-compiler.jar
(14688ms)
:: problems summary ::
:::: WARNINGS
[NOT FOUND ] org.scala-lang#scala-library;2.7.7!scala-library.jar
(0ms)
==== Maven2 Local: tried
Any ideas?
Leo.
On Oct 13, 12:47 pm, √iktor Klang <viktor.kl...@gmail.com> wrote:
> On Wed, Oct 13, 2010 at 12:42 PM, Matthias L. Jugel <
>
> > > > > > at...
>
> read more »
√iktor Klang
I'd like to. However, sbt is not helping me. It downloads scala-
compile 2.7.7. and then fails to find scala-library 2.7.7 in my local
maven2 repo. I don't understand why it does not even try to
download...
champloo:akka leo$ sbt update
Getting Scala 2.7.7 ...
downloading http://repo1.maven.org/maven2/org/scala-lang/scala-compiler/2.7.7/scala-compiler-2.7.7.jar
...
[SUCCESSFUL ] org.scala-lang#scala-compiler;2.7.7!scala-compiler.jar
(14688ms)
:: problems summary ::
:::: WARNINGS
[NOT FOUND ] org.scala-lang#scala-library;2.7.7!scala-library.jar
(0ms)
==== Maven2 Local: tried
Any ideas?
No clue, what did you change to get it to break?
>
> read more »
--
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
Matthias L. Jugel
so I can try.
Leo.
On Oct 13, 2:37 pm, √iktor Klang <viktor.kl...@gmail.com> wrote:
> On Wed, Oct 13, 2010 at 2:32 PM, Matthias L. Jugel <matthias.ju...@gmail.com
>
>
>
>
>
>
>
>
> > wrote:
> > I'd like to. However, sbt is not helping me. It downloads scala-
> > compile 2.7.7. and then fails to find scala-library 2.7.7 in my local
> > maven2 repo. I don't understand why it does not even try to
> > download...
>
> > champloo:akka leo$ sbt update
> > Getting Scala 2.7.7 ...
> > downloading
>
> read more »
Matthias L. Jugel
nothing to change to break it.
Leo.
On Oct 13, 2:37 pm, √iktor Klang <viktor.kl...@gmail.com> wrote:
> On Wed, Oct 13, 2010 at 2:32 PM, Matthias L. Jugel <matthias.ju...@gmail.com
>
>
>
>
>
>
>
>
> > wrote:
> > I'd like to. However, sbt is not helping me. It downloads scala-
> > compile 2.7.7. and then fails to find scala-library 2.7.7 in my local
> > maven2 repo. I don't understand why it does not even try to
> > download...
>
> > champloo:akka leo$ sbt update
> > Getting Scala 2.7.7 ...
> > downloading
>
> read more »
Matthias L. Jugel
last missing part for me to be able to test 1.0-SNAPSHOT
Leo.
On Oct 13, 12:47 pm, √iktor Klang <viktor.kl...@gmail.com> wrote:
> On Wed, Oct 13, 2010 at 12:42 PM, Matthias L. Jugel <
>
> > > > > > at...
>
> read more »
Matthias L. Jugel
a non-existant repository (http://eaio.com/maven2 gives a 404 not
found) and sjson-0.8 is also not available.
I am going to revert back to the 0.10 config for now to concentrate on
other issues. Let me know when I can try again.
Leo.
On Oct 14, 7:51 pm, "Matthias L. Jugel" <matthias.ju...@gmail.com>
> > > > > > > ...
>
> read more »
√iktor Klang
Actually, it is a bit of a pain with maven2. The UUID library used has
a non-existant repository (http://eaio.com/maven2 gives a 404 not
found) and sjson-0.8 is also not available.
Have you've added the embedded_repo to your repositories?
I am going to revert back to the 0.10 config for now to concentrate on
other issues. Let me know when I can try again.
You can try again when you have added the embedded repository to your pom.
> > > > > > > ...
>
> read more »
--
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
Matthias L. Jugel
works great.
However, even though flow control is enabled in ActiveMQ I get a queue
full in my actor on the subscriber side.
From what I can determine Internally, Akka takes the entry from the
ActiveMQ topic and pushes it forward to the Akka Actor using the bang
operator. Since it does not care much about the receiving actor the
mailbox runs over after some time. So the publisher is never
throttled.
I am trying to test this with 1.0-SNAPSHOT. I have published the
packages to my ~/.m2 repo but for an unknown reason only a few of the
modules are recognised. I guess akka-actor is what was akka-core
before? However, it is one of the modules, not recognised. Sometimes
maven scares me ...
Leo.
On Oct 8, 9:13 am, "Matthias L. Jugel" <matthias.ju...@gmail.com>
wrote:
>
> read more »
Martin Krasser
> Looks like the queue full on the publisher side is now fixed. Using !!
> works great.
> However, even though flow control is enabled in ActiveMQ I get a queue
> full in my actor on the subscriber side.
> From what I can determine Internally, Akka takes the entry from the
> ActiveMQ topic and pushes it forward to the Akka Actor using the bang
> operator. Since it does not care much about the receiving actor the
> mailbox runs over after some time. So the publisher is never
> throttled.
You need install a bounded mailbox for the subscriber. The threads that
read from the ActiveMQ topic and put messages to the actor mailbox are
then blocked. These threads are managed by Camel (and are independent of
the threads managed by Akka). When an exception is thrown (after a
pushTimeout) by a full actor mailbox, there should be even ways for
ActiveMQ to do a re-delivery (after some delay). Refer to the ActiveMQ
and Camel docs for details.
>> read more �
Matthias L. Jugel
up the error handler to do redelivery (or throw away messages).
After reading the camel docs I have added this to my camel-
context.xml:
<camel:camelContext errorHandlerRef="deadLetterErrorHandler"
xmlns="http://camel.apache.org/schema/spring">
<errorHandler id="deadLetterErrorHandler" type="DeadLetterChannel"
deadLetterUri="log:dead">
<redeliveryPolicy maximumRedeliveries="2" redeliveryDelay="1000"
logHandled="true"
asyncDelayedRedelivery="true"/>
</errorHandler>
</camel:camelContext>
However, I still get this message:
ERROR [2010-10-17 16:05:53,886] DefaultErrorHandler: Failed delivery
for exchangeId: ID:tw001-36075-1287319061404-0:41:1:1:60048. Exhausted
after delivery attempt: 1 caught: java.lang.IllegalStateException:
Queue full
at java.util.AbstractQueue.add(AbstractQueue.java:71)
at
81)
at
se.scalablesolutions.akka.dispatch.MessageInvocation.send(MessageHandling.scala:
33)
at
se.scalablesolutions.akka.actor.LocalActorRef.postMessageToMailbox(ActorRef.scala:
at se.scalablesolutions.akka.actor.ScalaActorRef$class.
$bang(ActorRef.scala:1565)
and subsequently:
ERROR [2010-10-17 16:05:53,889] EndpointMessageListener: Caused by:
[org.apache.camel.RuntimeCamelException -
java.lang.IllegalStateException: Queue full]
org.apache.camel.RuntimeCamelException:
java.lang.IllegalStateException: Queue full
at
org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:
1126)
at
org.apache.camel.component.jms.EndpointMessageListener.onMessage(EndpointMessageListener.java:
105)
at
org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:
560)
at
org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:
498)
at
org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:
467)
at
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:
323)
at
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:
261)
at org.springframework.jms.listener.DefaultMessageListenerContainer
$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:
1056)
at org.springframework.jms.listener.DefaultMessageListenerContainer
$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:
1048)
at org.springframework.jms.listener.DefaultMessageListenerContainer
$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:
947)
at java.lang.Thread.run(Thread.java:637)
Caused by: java.lang.IllegalStateException: Queue full
at java.util.AbstractQueue.add(AbstractQueue.java:71)
at
81)
at
se.scalablesolutions.akka.dispatch.MessageInvocation.send(MessageHandling.scala:
33)
at
se.scalablesolutions.akka.actor.LocalActorRef.postMessageToMailbox(ActorRef.scala:
at se.scalablesolutions.akka.actor.ScalaActorRef$class.
$bang(ActorRef.scala:1565)
at se.scalablesolutions.akka.actor.LocalActorRef.$bang(ActorRef.scala:
660)
On Oct 17, 6:52 am, Martin Krasser <krass...@googlemail.com> wrote:
> Am 16.10.10 23:46, schrieb Matthias L.Jugel:
>
> > Looks like the queue full on the publisher side is now fixed. Using !!
> > works great.
> > However, even though flow control is enabled in ActiveMQ I get a queue
> > full in my actor on the subscriber side.
> > From what I can determine Internally, Akka takes the entry from the
> > ActiveMQ topic and pushes it forward to the Akka Actor using the bang
> > operator. Since it does not care much about the receiving actor the
> > mailbox runs over after some time. So the publisher is never
> > throttled.
>
> You need install a bounded mailbox for the subscriber. The threads that
> read from the ActiveMQ topic and put messages to the actor mailbox are
> then blocked. These threads are managed by Camel (and are independent of
> the threads managed by Akka). When an exception is thrown (after a
> pushTimeout) by a full actor mailbox, there should be even ways for
> ActiveMQ to do a re-delivery (after some delay). Refer to the ActiveMQ
> and Camel docs for details.
>
>
>
>
>
>
>
> > I am trying to test this with 1.0-SNAPSHOT. I have published the
> > packages to my ~/.m2 repo but for an unknown reason only a few of the
> > modules are recognised. I guess akka-actor is what was akka-core
> > before? However, it is one of the modules, not recognised. Sometimes
> > maven scares me ...
>
> > Leo.
>
>
> read more »
Martin Krasser
https://www.assembla.com/spaces/akka/tickets/473-allow-consumer-actors-to-customize-their-own-routes
Not sure if I'll address that for Akka 1.0 because
- applications can already install custom routes (e.g. with specific
error handlers) to any actor and
- global error handler are often sufficient
Am 17.10.10 17:59, schrieb Martin Krasser:
> Hi Matthias,
>
> I'm getting an XML parser error with your XML config. Here's what I've
> used locally
>
> <camel:errorHandler id="deadLetterErrorHandler"
> type="DeadLetterChannel" deadLetterUri="log:dead">
> <camel:redeliveryPolicy maximumRedeliveries="2" redeliveryDelay="1000"
> logHandled="true" asyncDelayedRedelivery="true"/>
> </camel:errorHandler>
>
> <camel:camelContext id="camelContext"
> errorHandlerRef="deadLetterErrorHandler">
> <!-- ... -->
> </camel:camelContext>
>
> ...
>
> With this configuration in place, messages that couldn't be added to
> the mailbox are redelivered, as expected.
>
> Please note that this configuration applies to *all* routes to
> consumer actors (which shouldn't be a problem in most cases). To have
> a redelivery policy for a single consumer actor, a custom route to
> that actor must be installed ATM (see akka-camel docs). I'll think
> about an extension to akka-camel to make this more easy for consumer
> actor implementors.
>
> Hope that helps.
>
> Cheers,
> Martin
>
>
> Am 17.10.10 16:11, schrieb Matthias L. Jugel:
Martin Krasser
I'm getting an XML parser error with your XML config. Here's what I've
used locally
<camel:errorHandler id="deadLetterErrorHandler" type="DeadLetterChannel"
deadLetterUri="log:dead">
<camel:redeliveryPolicy maximumRedeliveries="2" redeliveryDelay="1000"
logHandled="true" asyncDelayedRedelivery="true"/>
</camel:errorHandler>
<camel:camelContext id="camelContext"
errorHandlerRef="deadLetterErrorHandler">
<!-- ... -->
</camel:camelContext>
...
With this configuration in place, messages that couldn't be added to the
mailbox are redelivered, as expected.
Please note that this configuration applies to *all* routes to consumer
actors (which shouldn't be a problem in most cases). To have a
redelivery policy for a single consumer actor, a custom route to that
actor must be installed ATM (see akka-camel docs). I'll think about an
extension to akka-camel to make this more easy for consumer actor
implementors.
Hope that helps.
Cheers,
Martin
Am 17.10.10 16:11, schrieb Matthias L. Jugel:
Jonas Bonér
I just love this team.
> --
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To post to this group, send email to akka...@googlegroups.com.
> To unsubscribe from this group, send email to
> akka-user+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/akka-user?hl=en.
>
>
--
Jonas Bonér
work: http://akkasource.org
code: http://github.com/jboner
blog: http://jonasboner.com
twtr: @jboner
Matthias L. Jugel
Now I have setup a test maven application to play around with things:
http://github.com/thinkberg/Akka-Camel-Test
Running inside my IDEA it will work perfectly and changing the
Thread.sleep() value in the subscriber will trigger queue full
exceptions. Inside IDEA the whole Spring setup works including adding
the camel:errorHandler.
My last problem now is that after packaging it does not work anymore
and Spring has a hard time with the schema files. It may be due to the
type of packaging (jar-with-dependencies), but I am not sure as all
the necessary files seem to end up in the final jar.
To create the necessary file:
mvn -P executable-jar package
now you can run:
java -jar target/akka-camel-test-1.1-jar-with-dependencies.jar
subscriber
and
java -jar target/akka-camel-test-1.1-jar-with-dependencies.jar
publisher
Both did not run throwing immediately this:
INFO [2010-10-18 16:39:11,664] ClassPathXmlApplicationContext:
Refreshing
org.springframework.context.support.ClassPathXmlApplicationContext@5f7a8a02:
startup date [Mon Oct 18 16:39:11 CEST 2010]; root of context
hierarchy
INFO [2010-10-18 16:39:11,727] XmlBeanDefinitionReader: Loading XML
bean definitions from class path resource [subscriber-context.xml]
Exception in thread "main"
org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
Configuration problem: Unable to locate Spring NamespaceHandler for
XML schema namespace [http://camel.apache.org/schema/spring]
Offending resource: class path resource [subscriber-context.xml]
at
org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:
68)
at
org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:
85)
at
org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:
80)
at
org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.error(BeanDefinitionParserDelegate.java:
284)
at
org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:
1332)
at
org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:
1325)
at
org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:
135)
at
org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:
93)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:
493)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:
390)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:
334)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:
302)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:
143)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:
178)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:
149)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:
212)
at
org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:
126)
at
org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:
92)
at
org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:
130)
at
org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:
467)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:
397)
at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:
139)
at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:
83)
at twimpact.akka.camel.AkkaCamelTest$.main(AkkaCamelTest.scala:24)
at twimpact.akka.camel.AkkaCamelTest.main(AkkaCamelTest.scala)
You will help me a lot here, as this is the last part to get our
trends back running.
Leo.
Martin Krasser
Thanks for preparing a sample app. I'll take look at it as soon as I
can. I'm quite busy at the moment with other things but should have time
for it on Wed. Maybe someone else wants to jump in (?) ...
Cheers,
Martin
Am 18.10.10 16:57, schrieb Matthias L. Jugel:
Jonas Bonér
Martin Krasser
look at ... will give an update soon.
Am 20.10.10 09:41, schrieb Jonas Bon�r:
--
Jonas Bonér
On 20 October 2010 09:45, Martin Krasser <kras...@googlemail.com> wrote:
> This seems to be a configuration issue in the app. I'm about to take a look
> at ... will give an update soon.
>
> Am 20.10.10 09:41, schrieb Jonas Bonér:
--
Matthias L. Jugel
to a directory and starting using
java -cp thejarfiles twimpact.akka.camel.AkkaCamelTest subscriber
Now it runs, so it is actually the problem with the packaging. Looks
like I will have to dig out my old launcher from SnipSnap that just
unpacks the jar files on launch, sets the class path and runs the main
class. jar-with-dependencies is just stupid when it comes to conflict
resolving, so I guess the problem lies with the fact that it
overwrites files with the same name from different jars.
Leo.
On Oct 20, 9:45 am, Martin Krasser <krass...@googlemail.com> wrote:
> This seems to be a configuration issue in the app. I'm about to take a
> look at ... will give an update soon.
>
>
>
>
>
>
>
>
>
> > If you feel it is a bug please file a ticket.
>
√iktor Klang
I have done a simple test, copying all dependent jar files using maven
to a directory and starting using
java -cp thejarfiles twimpact.akka.camel.AkkaCamelTest subscriber
Now it runs, so it is actually the problem with the packaging. Looks
like I will have to dig out my old launcher from SnipSnap that just
unpacks the jar files on launch, sets the class path and runs the main
class. jar-with-dependencies is just stupid when it comes to conflict
resolving, so I guess the problem lies with the fact that it
overwrites files with the same name from different jars.
Ouch,
good catch.
Martin Krasser
Am 20.10.10 10:14, schrieb Matthias L. Jugel:
> I have done a simple test, copying all dependent jar files using maven
> to a directory and starting using
>
> java -cp thejarfiles twimpact.akka.camel.AkkaCamelTest subscriber
>
> Now it runs, so it is actually the problem with the packaging. Looks
> like I will have to dig out my old launcher from SnipSnap that just
> unpacks the jar files on launch, sets the class path and runs the main
> class. jar-with-dependencies is just stupid when it comes to conflict
> resolving, so I guess the problem lies with the fact that it
> overwrites files with the same name from different jars.
>
> Leo.
>
>
> On Oct 20, 9:45 am, Martin Krasser<krass...@googlemail.com> wrote:
>> This seems to be a configuration issue in the app. I'm about to take a
>> look at ... will give an update soon.
>>
>> Am 20.10.10 09:41, schrieb Jonas Bon�r:
Martin Krasser
Among other features, it allows you to install custom error handlers for
routes to individual consumer actors. So there's no need any more to
install the error handler globally. More at
http://doc.akkasource.org/Camel#intercepting-route-construction.
Am 17.10.10 18:10, schrieb Martin Krasser:
√iktor Klang
Awesome, great work Martin! :)
On Nov 10, 2010 10:01 AM, "Martin Krasser" <kras...@googlemail.com> wrote:
I finally had some time to resolve that ticket and pushed it to master. Among other features, it allows you to install custom error handlers for routes to individual consumer actors. So there's no need any more to install the error handler globally. More at http://doc.akkasource.org/Camel#intercepting-route-construction.
Am 17.10.10 18:10, schrieb Martin Krasser:
>
> I also created a ticket for that:
>
> https://www.assembla.com/spaces/akka/tickets/473-allow-c...