One more thing I thought was interesting just in case you might want to
start with the new JMS endpoint which is commented in the bridge-jms-one-su
in the sample I attached in the previous message, was that if you use the
new servicemix-jms endpoint to send to the servicemix-bean component, it
will deadlock after 1 message and when you ctrl-c Servicemix, you will see a
JMS reply acknowledgement error. I guessing that it's not a result of the
ctrl-c, but a reason why the whole thing hangs.
Ryan
On Sat, Aug 23, 2008 at 6:04 PM, Ryan Moquin <[EMAIL PROTECTED]> wrote:
> Hi Bruce,
>
> I know, I thought it would be better to get you a simple case you could run
> and then do whatever you wanted with. Attached is a barebones Service
> Archive that includes two jms SUs that each connect to a topic, along with a
> simple servicemix-bean component that takes an input message from one jms SU
> and sends it to the other jms SU using a ServicemixClient. This test app
> behaves EXACTLY how my application does. I ran it as the only service. All
> I did was drop the service archive into the hotdeploy, started up service
> mix and then ran the included client by executing the jar file in the target
> directory, which is an executable jar. The jar is created by one-jar so it
> is a self contained jar. Obviously you'll want to build it with maven2
> first.
>
> Attached is the maven2 project for you. I figured this is better than
> going back and forth with the stack traces.
>
> Some notes on this app and problem I've found:
>
> This is exact scenario works perfectly without the servicemix-bean
> component. So if you bridge the two jms SUs, then you won't have any
> problems.
>
> If you uncomment the new servicemix-jms endpoint in the bridge-jms-one-su
> project, and comment the old one, the application will freeze after the
> first message, and that's apparently because the new JMS endpoints are
> synchronous by default?
>
> Let me know if you need anything else, but this should give you everything
> you need.
>
> Ryan
>
>
> 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/
>>
>
>
