On Sat, Aug 23, 2008 at 1:59 PM, Ryan Moquin <[EMAIL PROTECTED]> wrote:
> Hi Gert,
>
> I actually decided to do that rather than go the the stack trace way, since
> it seemed like it still going to be like searching for a needle in a
> haystack. Anyhow, I tried to reproduce this problem using basically a
> simple jms bridge service archive where I setup my JMS service units the
> same as my full blown project. When I did that, I was able to pump 2000
> messages across them without any problems at a rate of one message per 50
> ms.
>
> So, basically I've shot my whole theory out of the water that it has
> anything to do with ActiveMQ refusing messages. I guess I'll need to add a
> servicemix-bean component to forward requests to the jms provider rather
> than from the jms consumer to the jms provider.
>
> I'll keep working on it until I get it because I really need to figure out
> this problem since it's hindering several projects now. No idea why all of
> a sudden the problem became so severe.
You're now running in circles. And yet I still haven't seen a simple
thread dump and your servicemix.properties file.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Blog: http://bruceblog.org/
