thread
safe and adhere to the JMS spec.
I will assume ActiveMQ messageProducer.send method is thread safe.
Cheers
James.Strachan wrote:
>
> On 3/1/07, Albert Strasheim <[EMAIL PROTECTED]> wrote:
>> Hello all
>>
>> On Thu, 01 Mar 2007, Paul French wrote:
>>
Is ActiveMQMessageProducer.send thread safe?
--
View this message in context:
http://www.nabble.com/Is-ActiveMQMessageProducer.send-thread-safe--tf3325927s2354.html#a9246594
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
On 2/20/07, Paul French <[EMAIL PROTECTED]> wrote:
>>
>> Any ideas?
>
> Am afraid not. Someone might have to get the profiler out. Any chance
> you can create a JUnit test that reproduces the slowdown?
>
>
>
>>
>> Is...
>>
>> produc
Any ideas?
Is...
producer.send(tempQueue, jmsResponse);
an async send still when I have specified the connection as async?
(tempQueue is obtained from the JMSReplyTo property of a received message)
Paul French wrote:
>
> The temp queue is obtained from the JMSR
The temp queue is obtained from the JMSReplyTo property of the received
message.
I specify Async send in the connection factory as follows:
TRUE
James.Strachan wrote:
>
> On 2/19/07, Paul French <[EMAIL PROTECTED]> wrote:
>>
>> I don't unders
null since we do
not know the destination
connection.start();
Each call does...
producer.send(tempQueue, jmsResponse);
Any idea why this is significanly slower then a call to a pre-defined known
queue.
James.Strachan wrote:
>
> On 2/17/07, Paul French <[EMAIL PRO
You need to give more info since it is not clear what you are trying to do.
The Listener Container you have configured will start 50 threads all waiting
to consume messages.
Give more info and I will be happy to help.
cafe wrote:
>
> I have an app where I’m using spring 2.0 and activeMQ4.1.0.
I am using the defualt install of activeMQ 4.1.0
I've turned off persistence and increased memory-manager setting to 500MB
I've also updated the startup script so that the java heap can increase to
1G of memory if required
The messaging layer of my app is simple. The client creates a temp queue o
connection is re-established will
ActiveMQ maintain my current temporary queues?
Paul French wrote:
>
> For me this is a continuation of.
>
> http://www.nabble.com/Async-Exception%3A-Broken-Pipe-t3160498s2354.html#a8765808
>
> ...but I have now taking the advice from
Hold fire on this one, it could be a garbage collection problem causing the
long pause. I've got parallel garbage collection switched on so I would not
expect all threads to stop so it is a strange one.
Paul French wrote:
>
> For me this is a continuation of
For me this is a continuation of.
http://www.nabble.com/Async-Exception%3A-Broken-Pipe-t3160498s2354.html#a8765808
...but I have now taking the advice from the above post and have refined the
problem I am having.
Environment
I am now using the latest 4.2 snapshot as requested (29th Jan 200
ach Connection created in ActiveMQ tends to create a socket and
> a thread on the broker side. So you could increase the parallelism of
> your client while reducing load on the broker by just creating a
> single connection and reusing it across many sessions in your client.
>
>
&
I'll give it a try over the weekend and will let you know.
Thanks
rajdavies wrote:
>
> do the errors exist on the latest 4.2 snapshot?
>
--
View this message in context:
http://www.nabble.com/Async-Exception%3A-Broken-Pipe-tf3160498.html#a8776795
Sent from the ActiveMQ - User mailing list
meout---out-of-memory--exceptions-t3028623.html#a8414639
Paul French wrote:
>
> Hello,
>
> I have a single client laptop that connects to the broker on another
> machine, creates a temp queue and sends text messages to a main queue. The
> client also starts a listener consumer
- Removing consumer:
ID:T1000-2.frenchiesys
tems.com-32850-1170420532869-1:0:-1:1
DEBUG TransportConnection- Stopped connection:
/192.168.160.89:32851
Paul French wrote:
>
> Hello,
>
> I have a single client laptop that connects to the broke
Hello,
I have a single client laptop that connects to the broker on another
machine, creates a temp queue and sends text messages to a main queue. The
client also starts a listener consumer to consume the replies given on the
temp queue.
The server consumes messages from the main queue does some
16 matches
Mail list logo