Hi Darrell,
Derby is the bottleneck for the Journal, in version 4.x by default
the entire message will be moved from the journal into the store (by
default Derby) - which is slow. In reality relational databases
aren't well suited to streaming queued data through. Kaha persistence
on the
Hi,
I'm having a serious problem with a recent AMQ nightly (apache-
activemq-5.0-20070827.124842-62.zip) that is causing almost 1500
threads to be created and sit in the background before the jvm runs
out of memory (OutOfMemoryError: cannot create new native thread).
I have a simple case w
On Wed, Sep 26, 2007 at 11:11:30PM +, David Holroyd wrote:
> I tried to adapt the NMS example code for MSMQ, but it seems to just
> hangs trying to get the message back from MSMQ. Under Computer
> Management, I can see that a public queue gets created, but I've not
> seen any messages listed t
Hi,
I have an application which feeds data based on customers request.
Data Engine -> Active MQ > MV Engine -- Customers
subscribe / unsubscribe to MV Engine using socket & request for data.
We used 4.0 before. We wanted to upgrade to 4.1.1. We did the same tests &
got the
Our system is taking 6~7 seconds to pull a message off of a queue using a
simple selector (id = ?). The queue has about 20,000 messages which are
fairly small. I ran through a quick series of tests and this is what I came
up with.
** NO PERSISTENCE **
# of Messages= 20,000
Avg time to Send
Hi Rob,
Actually, it is pretty straight forward. Here's some code from my test
publisher to illustrate. Note the comment for the first Thread.sleep.
code snippet
...
Context ctx = new InitialContext();
// peer1ConnectionFactory maps to 'peer://groupa'
ConnectionFactory factory =
any info about this?
srasul wrote:
>
> Hi,
>
> We have been having cases recently were people cannnot connect to our
> ActiveMQ (4.1) when using proxies. After lots of digging, i have found
> that the issue may be in this class:
> org.apache.activemq.transport.tcp.TcpTransport and especially i
Hello,
I am new activemq user and also interested with compression. Can you please
tell me how big message has to be to get compressed. Are you using gzip?
What activemq class does compression?
Thank you very much
Diego
rajdavies wrote:
>
> The producer does the compression - so it does n
ok, many thanks for that info.
i was thinking that the consumer would get messages compressed if he
connected with useCompression flag.
rajdavies wrote:
>
> The producer does the compression - so it does need to know that the
> useCompression flag is set
> On Sep 28, 2007, at 4:20 PM, srasul
joe,
do you have a test case for this? This sounds like a bug
cheers,
Rob
http://rajdavies.blogspot.com/
On Sep 28, 2007, at 3:34 PM, ttmdev wrote:
If your client is starting an embedded broker via the vm or peer
connectors
and sends a message immediately after invoking connection.sta
The producer does the compression - so it does need to know that the
useCompression flag is set
On Sep 28, 2007, at 4:20 PM, srasul wrote:
Hi there,
i was doing some testing with compression, and i have found that both
producer and consumer need to have compression enabled in the
connectio
Hi there,
i was doing some testing with compression, and i have found that both
producer and consumer need to have compression enabled in the connection url
for compression to work. is this normal behavior?
I did some testing by doing a network trace and found:
- for compression to work, i have
Hi,
If you get a fresh build of activemq 5.x, it will once again be
compatible with old 4.x clients.
Regards,
Hiram
On 9/28/07, Hiram Chirino <[EMAIL PROTECTED]> wrote:
> I have just verified that a small incompatibility did sneak in. I
> will be fixing this up shortly.
>
> On 9/20/07, DominicT
I have just verified that a small incompatibility did sneak in. I
will be fixing this up shortly.
On 9/20/07, DominicTulley <[EMAIL PROTECTED]> wrote:
>
> What is the expected compatability between a JMS consumer using the AMQ 4.1.1
> libraries and a server running a 5.0 snapshot?
>
> It seems to
If your client is starting an embedded broker via the vm or peer connectors
and sends a message immediately after invoking connection.start(), that
message will most likely fall into a black hole and your client is never
notified of this. This is because the embedded broker has not been fully
acti
It looks like the:
Might not be correctly configured. The JMS Bridge is getting an error
when it tries to create a connection using the above configured
connection factory.
I would suggest that you test out the above connection factory
configuration i
You have created two channels, sorta; the first is topic://doChat and the
second is '/topic/ChatTopic', which does not conform to the url notation
that you should be using. That might be your problem.
I assume that you have your own server-side Java classes that listen for
incoming messages on to
17 matches
Mail list logo