che.org/cms/configuring.html
>
>> -Original Message-
>> From: Pravin Kundal [mailto:[EMAIL PROTECTED]
>> Sent: Monday, May 21, 2007 12:34 PM
>> To: users@activemq.apache.org
>> Subject: RE: Implementation of multithreading model on CMS ActiveMQ
>>
>>
>>
Monday, May 21, 2007 12:34 PM
>> To: users@activemq.apache.org
>> Subject: RE: Implementation of multithreading model on CMS ActiveMQ
>>
>>
>> I am trying to test it out using stomp.
>> But it is giving me exceptions
>> On Consumer Client: ActiveMQConnectionFactory
vemq.apache.org/cms/configuring.html
> >
> >> -Original Message-
> >> From: Pravin Kundal [mailto:[EMAIL PROTECTED]
> >> Sent: Monday, May 21, 2007 12:34 PM
> >> To: users@activemq.apache.org
> >> Subject: RE: Implementation of multithreading model on CMS
l should be "tcp://localhost:61613?wireFormat=stomp"
>
> See http://activemq.apache.org/cms/configuring.html
>
>> -Original Message-
>> From: Pravin Kundal [mailto:[EMAIL PROTECTED]
>> Sent: Monday, May 21, 2007 12:34 PM
>> To: users@activemq.apache.org
&g
ache.org
> Subject: RE: Implementation of multithreading model on CMS ActiveMQ
>
>
> I am trying to test it out using stomp.
> But it is giving me exceptions
> On Consumer Client: ActiveMQConnectionFactory - unknown
> Transport Factory.
>
> I tried with following brokerURI's
&
I am trying to test it out using stomp.
But it is giving me exceptions
On Consumer Client: ActiveMQConnectionFactory - unknown Transport Factory.
I tried with following brokerURI's
std::string brokerURI = "stomp://localhost:61613"
"?wireFormat=stomp"
Sorry,
I missed the second line of link. I could access it. Thanks
Pravin Kundal wrote:
>
> I couldn't access the link below.
>
> Is it the same example that Apache-ActiveMQ ship with the CMS library?
>
> Thanks a lot.
>
>
> Mittler, Nathan wrote:
>>
>>
>>>
>>> In the case I will need t
I couldn't access the link below.
Is it the same example that Apache-ActiveMQ ship with the CMS library?
Thanks a lot.
Mittler, Nathan wrote:
>
>
>>
>> In the case I will need to implement the concurrency control
>> over the session, so that only one thread can use the
>> session, as se
>
> In the case I will need to implement the concurrency control
> over the session, so that only one thread can use the
> session, as sessions are implemented for serial use? Rght?
Yes, you should add your own concurrency control for the session.
>
> I tried the first case in which i imple
Thank you Sir for you immediate reply !
Ok now in the case where
"The ActiveMQ-CPP implementation, however, will allow you to share a session
across threads."
In the case I will need to implement the concurrency control over the
session, so that only one thread can use the session, as sessi
The formal JMS/CMS definition of a Session implies that each thread
would get its own session. The ActiveMQ-CPP implementation, however,
will allow you to share a session across threads.
For consumers, it should be known that each session has a single message
dispatch thread, so a slow asynchro
11 matches
Mail list logo