After spending close to 2 months trying to get ActiveMQ to work reliably we
have finaly decided to give up.
If some of you remember we were planning on using ActiveMQ to distribute
pricing information for traders. As we were not able to get past some of
the issues we have with ActiveMQ it was de
Yes thanks for that. Test ran results posted.
nmittler wrote:
>
> Robert,
> I've captured what you have to do to change the timeout here
> http://issues.apache.org/activemq/browse/AMQCPP-157
>
> Regards,
> Nate
>
>
>>
>> Yes please tell me where to change the code for th etime out I will re
Yes please tell me where to change the code for th etime out I will re
compile and try.
James.Strachan wrote:
>
> On 17/12/2007, Nathan Mittler <[EMAIL PROTECTED]> wrote:
>> Hey James,
>> I've captured the details here
>> http://issues.apache.org/activemq/browse/AMQCPP-157
>
> Ah great, thanks.
The stack trace from the CPP client was added to one of the posts in this
thread.
I do think it is related to flow control.
James.Strachan wrote:
>
> On 17/12/2007, Hellweek <[EMAIL PROTECTED]> wrote:
>>
>> When performing the test with C# consumers the CPP pr
> On Dec 14, 2007 4:50 PM, Hellweek <[EMAIL PROTECTED]> wrote:
>>
>> thats my thought also. however C# to C# work C++ to c++ works but C# to
>> C++
>> wont. Seems very odd.
>>
>>
>> nmittler wrote:
>> >
>> > Hey Rob,
>> > Ag
;> I've captured this in a JIRA issue here:
>>>
>>> https://issues.apache.org/activemq/browse/AMQCPP-157
>>>
>>> We'll do our best to get this resolved soon!
>>>
>>> Regards,
>>> Nate
>>>
>>> On Dec 11, 20
This is good news. Please let me know if there is anything I can do.
I would love to retest this once it has been marked as resolved.
James.Strachan wrote:
>
> On 12/12/2007, Hellweek <[EMAIL PROTECTED]> wrote:
>>
>> Well my first impression was wrong also.
.
yg_cvg wrote:
>
> Ah, I see. That's different from the impression I was initially getting
> from your post. In particular, our clients would be Java servlets, so we
> might not run into these issues. I am in the process of making some
> stress tests myself right now.
&g
It appears that it does not support C++ and is not as mature as ActiveMQ.
Hellweek wrote:
>
> I will examine this option today. Thanks for the heads up.
>
> Jonathan Share wrote:
>>
>> Hellweek wrote:
>>>
>>> Hello,
>>>
>>> I kno
only plan on using the C++ and C# API's and had no
real need for testing JAVA.
James.Strachan wrote:
>
> On 11/12/2007, Hellweek <[EMAIL PROTECTED]> wrote:
>>
>> I pulled the 5.0 down yesterday. As well as the 5.0 RC1, RC2, RC3
>
> Cool thanks. BTW in your pr
we're
> considering using ActiveMQ for a big highly distributed network, but we
> have no idea how it would perform in such a setting.
>
>
> Hellweek wrote:
>>
>>
>> Hello,
>>
>> I know what I am about to post will upset a few people, however I thi
activemq/browse/AMQCPP-157
>>
>> We'll do our best to get this resolved soon!
>>
>> Regards,
>> Nate
>>
>> On Dec 11, 2007, at 9:10 AM, Hellweek wrote:
>>
>> >
>> > As promised I have created a c++ test program (TestProducerBug) tha
I had no real need for a JAVA API as such it was not included in our
evaluation.
James.Strachan wrote:
>
> On 11/12/2007, Hellweek <[EMAIL PROTECTED]> wrote:
>>
>> I pulled the 5.0 down yesterday. As well as the 5.0 RC1, RC2, RC3
>
> Cool thanks. BTW in you
tivemq/browse/AMQCPP-157
>
> We'll do our best to get this resolved soon!
>
> Regards,
> Nate
>
> On Dec 11, 2007, at 9:10 AM, Hellweek wrote:
>
>>
>> As promised I have created a c++ test program (TestProducerBug) that
>> will
>> create
I will examine this option today. Thanks for the heads up.
Jonathan Share wrote:
>
> Hellweek wrote:
>>
>> Hello,
>>
>> I know what I am about to post will upset a few people, however I think
>> it
>> is important that I document my experience wi
Place a breakpoint on the MessageListner in the C# program.
In very little time the producer will throw an exception.
Hellweek wrote:
>
>
> Hello,
>
> I know what I am about to post will upset a few people, however I think it
> is important that I document my experience with
I pulled the 5.0 down yesterday. As well as the 5.0 RC1, RC2, RC3
James.Strachan wrote:
>
> On 11/12/2007, Hellweek <[EMAIL PROTECTED]> wrote:
>>
>> Most of this testing was done with the 5.0 trunk.
>
> How long ago BTW? Only we've had a 5.0 trunk for abo
production I am still commited to
seeing these issues resolved.
What I have found is the CPP and C# clients dont play nice with each other.
Sample code will follow later today that will allow you guys to recreate
most of the issues I see.
James.Strachan wrote:
>
> On 10/12/2007, Hellweek &
Hello,
I know what I am about to post will upset a few people, however I think it
is important that I document my experience with ActiveMQ in the hopes that
others like me can have an understanding of the issues that you will face.
A little history.
I am not new to Open Source projects, have b
any
issues it has with stability and reliability. I personaly will be
recomending that we get SonicMQ it is stable and does not require me to
spend weeks figuring out issues that are not releated to my code.
Hellweek wrote:
>
> We are alos experiancing the exact same issue. It seems related
We are alos experiancing the exact same issue. It seems related to large
number of producers sending over one connection/session. I can verify this
behaviour is the same in the 4.1.1 broker and the 5.0 broker. It does not
mater what CPP client is used. 2.1 or 2.1.1 or 2.1.2.
We have broken d
For the past 2 weeks we have been testing ActiveMQ to answer this question
ourself. Here is what we found.
Creating a Connection takes one thread.
Creating a Session takes one thread.
Creating a NON Persisted Topic with a messageListner takes one thread, when
the topic is no longer used the thre
For the past 2 weeks we have been testing ActiveMQ to answer this question
ourself. Here is what we found.
Creating a Connection takes one thread.
Creating a Session takes one thread.
Creating a NON Persisted Topic with a messageListner takes one thread, when
the topic is no longer used the thre
23 matches
Mail list logo
