On 1 May 2008, at 22:52, sk123 wrote:
Hi,
I using Active MQ 5.0. In this test I send 4000 event in batches for
50 at
an interval of 725 milliseconds. I run the test and receive all the
events
and shut down the broker. When the broker is started again it throws
these
exceptions:
2008-0
Hi,
I'm just starting with the 5.2 snapshot today. I know very little about
activemq. The release notes for 5.2 suggest that ldap authorization is
working.
I want to use the http servlet and REST interface. But processes must
authenticate before being able to send or receive. I need to
aut
On Thu, May 1, 2008 at 5:32 PM, C45 <[EMAIL PROTECTED]> wrote:
>
> I was wondering if there is a file that logs the various bug fixes that went
> into 5.2-SNAPHOT?
>
> I checked the obvious places (README, NOTICE files...) in the source
> distribution at:
>
>
> http://people.apache.org/repo/m
I was wondering if there is a file that logs the various bug fixes that went
into 5.2-SNAPHOT?
I checked the obvious places (README, NOTICE files...) in the source
distribution at:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/activemq/apache-activemq/5.2-SNAPSHOT/
but was una
Michele Mazzucco wrote:
Filip,
if you mean on the client side, I have a thread pool configured to
create max 100 threads.
there could still be a thread leak in your application somewhere
about -Xmx, that's the maximum amount of memory. Why are you telling
me that by decreasing that value t
Hi,
I using Active MQ 5.0. In this test I send 4000 event in batches for 50 at
an interval of 725 milliseconds. I run the test and receive all the events
and shut down the broker. When the broker is started again it throws these
exceptions:
2008-05-01 14:50:31,659 [main] INFO
org.apache.activem
Filip,
if you mean on the client side, I have a thread pool configured to
create max 100 threads.
about -Xmx, that's the maximum amount of memory. Why are you telling
me that by decreasing that value there would be more space for
threads?
Michele
On Thu, May 1, 2008 at 7:50 PM, Filip Hanik - De
On Thu, May 1, 2008 at 2:16 PM, seven_ephors <[EMAIL PROTECTED]> wrote:
>
> I am using the TopicPublisher.java code in the 5.0.0\example\src directory,
> with slight modifications. It seem to work pretty well, but when I have
> large number of messages, it always stop working after certain numb
I am running into the exact same issue that is described in
http://issues.apache.org/activemq/browse/AMQ-734
But per the report, the fix is in 4.1.1 (which is what I am running).
Could someone tell me if perhaps 4.1.1 is similarly affected
despite the fix? Has anyone seen this problem wi
I am using the TopicPublisher.java code in the 5.0.0\example\src directory,
with slight modifications. It seem to work pretty well, but when I have
large number of messages, it always stop working after certain number of
messages are published. For a BytesMessage with data size of 256X128, I can
Yes. If each time the broker starts, you give it a new, randmomly generated
name, then it will end up creating/using a new message store.
BTW, these two bridge configurations are allowed
<-
AB A <-> B
->
But this one is not, which is what you we
when it happens, do a thread dump to make sure you don't have a thread
leak (too many threads)
then lower your -Xmx setting, this will make more room in the JVM for
threads,
Filip
Michele Mazzucco wrote:
Hi all,
I'm facing the following error while using AMQ 5.0
ERROR efaultMessageListene
Thanks, Joe. Looks like taking out the "duplex=true", while keeping in the
random brokerName, solved the issue.
Now, am I right in assuming that random broker names will wreak havoc on
durable subscriptions and message recovery? Do most people hand-edit the
configuration of each deployed server
test
You can't have both brokers connect to each other with duplex connections.
Joe
-Original Message-
From: matt hoffman [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 01, 2008 1:50 PM
To: users@activemq.apache.org
Subject: Re: Help with embedded brokers
Ok, I gave that a shot. I set the
What's happening is that you have two brokers with the same name trying to
connect with one another. The exception throws people off because they
always perceive it mean that it has something to do with their client, which
is not always the case. Whenever you see the "NC_" prefix associated with
t
Ok, I gave that a shot. I set the broker name to a randomly-generated UUID
(which has implications for durable subscriptions and data recovery should a
broker go down, I imagine, but it's for the sake of testing). I still got
errors, so I set the network connector name to the same value. It mad
Hi,
you can try specifying different name for every broker. It should help.
Regards
--
Dejan Bosanac
www.scriptinginjava.net
On Thu, May 1, 2008 at 5:29 PM, matt hoffman <[EMAIL PROTECTED]> wrote:
> I'm having a lot of trouble getting embedded brokers to work as they
> should. I'm using them i
Hi all,
I'm facing the following error while using AMQ 5.0
ERROR efaultMessageListenerContainer - Setup of JMS message listener
invoker failed - trying to recover
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.
I'm having a lot of trouble getting embedded brokers to work as they
should. I'm using them in my case mainly to ease configuration -- I want to
be able to run several instances of the same code and have them discover
each other and communicate, without needing a single server already running.
T
Can you verify that things work fine when using a Java client to receive
the messages? If so, it sounds like a C++ client bug - I recommend
raising a JIRA issue and attaching a sample program if you can cook one
up quickly.
Nate
> -Original Message-
> From: rahuljoshi80 [mailto:[EMAIL PR
JBoss answer
"/The connection factories provided by a Resource Adapter (RA) are
typically not available for use by clients that are outside of the
application server. That is, the JCA specification is intended to
provided resources to the application server, and relies upon behavior
on the par
Rob Davies wrote:
On 1 May 2008, at 00:02, Filip Hanik - Dev Lists wrote:
There doesnt seem to be a way of limiting how messages are delivered
to the client.
the ActiveMQMessageConsumer.unconsumedMessages seems to fill up, all
to quickly, and eventually cause an OOME
we have this setting on
hi
I am using activemq5.0 with jboss4.2.2.i want to persist the messages, i
configured jbdcPersistance in my broker xml file. Now the problem is that
for persisting the messages i have to provide the DataSource. if i do a
lookup for exists datasource which i created for my application, it is not
24 matches
Mail list logo
