I figured out the issue.  I was playing around with different ways of using
the ServiceMixClient to avoid NPEs I seemed to get when reusing the
DeliveryChannel or ComponentContext.  I ended trying an example that
simplified communications to the point that messages were created without
specifying a MEP (I think is the right acronym) type for the message and
defaults to InOut.  As a result, I wasn't setting the exchange status to
done and therefore I hung all the threads in the container.

Now that that's fixed, I seem to be working without hanging threads and with
NPEs, though unfortunately.. my memory still steadily grows as the app runs,
so there is a memory leak somewhere.  I'm not sure if it's because ActiveMQ
isn't removing messages off of the Queue, but I guess I'll find out when I
profile everything.

I'll update the ticket I opened (it never fails that as soon as I open a
ticket, I magically figure out the problem).

Thanks for the help!

On Sat, Aug 23, 2008 at 7:50 PM, Ryan Moquin <[EMAIL PROTECTED]> wrote:

> I forgot Gert mentioned to open a Jira, I opened one and attached a simple
> project that can be used to reproduce this issue along with instructions on
> how I reproduced it:
>
> https://issues.apache.org/activemq/browse/SM-1519
>
> On Sat, Aug 23, 2008 at 4:49 PM, Bruce Snyder <[EMAIL PROTECTED]>wrote:
>
>> 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/
>>
>
>

Reply via email to