I see ActiveMQ features said it support NIO transport protocol, but I can't
find the document to configure it as other transport protocol.
--
View this message in context:
http://www.nabble.com/How-to-configure-NIO-transport-protocol-tp15641872s2354p15641872.html
Sent from the ActiveMQ - User
I'm having some problems on the client with IConnection.ExceptionListener.
When the ActiveMQ server is shutdown, this Listener is fired in my client
app as expected. However, when I then go and close/dispose of the client
connection, subscription, and messageconsumer during this event the debugger
I set the optimizedAcknowledge flag in the consumer client to patch the
knowledge for boosting performance by following the link below:
http://open.iona.com/wiki/display/ProdInfo/FUSE+Message+Broker+Performance+Tuning+Guide
By setting the optimized Acknowledge, the performance do greatly improve
I am using Apache ActiveMQ 5.0. To my understand, dispatchSync only helpful
when have slower consumers and using the consumers using the same
connection, different sessions. But in my case, all consumer threads are
using different connections.
Thanks,
Zao
On Fri, Feb 22, 2008 at 1:28 AM, Rob Dav
Rob Davies wrote:
Writes are usually fast because of the journaling part of the default
message store
Which version are you using btw?
I'm using 5.0, and like I said in another email, when writing safely
(syncOnWrite="true") performance isn't all that good without write
caching. How do you d
Would love to know how to do that. Can you give me an example of a test case
or where I would find out how to write a test case?
rajdavies wrote:
>
> Could you please provide a test case ?
>
> cheers,
>
> Rob
> On 21 Feb 2008, at 22:52, sparky2708 wrote:
>
>>
>> This started happening since
I created an issue in JIRA and attached a simple test case to it. Please note
that a reconfiguration of Spring to use a different cacheLevel for the
DefaultMessageListenerContainer seems to solve this problem, but I think I
should never loose any messages when using XA, so I created the issue
anyw
zaoliu schrieb:
An issue when testing performance s when I increase the number of consumers
for testing non-persistent messages, the throughput get down very fast. I
can't find the reason for it. Each consumer thread is a separate connection
to the broker.
Below is my result for testing (all usin
Could you please provide a test case ?
cheers,
Rob
On 21 Feb 2008, at 22:52, sparky2708 wrote:
This started happening since we upgraded from 4.1.0. 4.1.0 doesn't
seem to
have this problem.
sparky2708 wrote:
I am getting the same error with SNAPSHOT-5.1:
21/02/2008 08:03:34,335 ERROR [
You can try setting async dispatch on the consumer - see:
http://activemq.apache.org/consumer-dispatch-async.html
A separate task would be used then for dispatching to each consumer
cheers.
Rob
On 21 Feb 2008, at 22:40, Zao Liu wrote:
Another issue I met is when I increase the number of consum
On 21 Feb 2008, at 21:57, rd7 wrote:
Hello,
We are using ActiveMQ 4.1.1 and are in the process of testing
failover (we
have only tested client failover so far).
We have 2 servers (host 1 & host2), each with 1 broker and 2
publishers
each. So, the 2 publishers that are on host1 send m
On 21 Feb 2008, at 19:52, Ben Chobot wrote:
It sounds like you don't have a very firm grasp on what's going on,
under the covers. If you need persistence, have you tried pulling
the power cord from your server and verifying you haven't lost
messages? If you don't care, why do you need pers
12 matches
Mail list logo
