I am facing the same problem while starting the broker using init.d
configuration. If i start it normally it comes up fine. Any guesses on why
this I am getting "cannot find beans declaration" error using init.d ???
--
View this message in context:
http://activemq.2283324.n4.nabble.com/org-xml-
We just ran into the warning below indicating that we've exceeded the memory
available on a Topic.
WARNING: Async error occurred: javax.jms.ResourceAllocationException: Usage
Manager memory limit reached. Stopping producer
(ID:hoeplx3764-34102-1345832926291-0:2:2:1) to prevent flooding
topic:/
One thing you didn't mention that could be helpful is whether you are using
the failover protocol. I would think that any network interruption would
be handled by the failover layer and automatically reconnect the consumer.
Other than that, have you noticed any pattern to the connection, such as
Title: Signature
Hi Matt or whomever can help,
We finally rolled out SMX 4.4.1 with AMQ 5.5.x to our production
environment a few weeks ago. Yeah, it takes a while to get through
testing.
Anyway, we're still seeing the stuck queue condition even with the
AM
I've been trying to figure out this problem I've been having with
apache NMS for at least a week now, so I decided maybe I would try to post
here and see if anyone has experienced similar issues. In my situation, we
have about 5-7 producers all producing to one topic, and then we have
Sweets, thanks,
Finally i was not alone thinking this about fuse-leveldb :)
2012/8/27 Gary Tully
> that is fixed on trunk with https://issues.apache.org/jira/browse/AMQ-3890
>
> On 27 August 2012 20:19, Sébastien Lorber
> wrote:
> > Yes i know and i have excluded the problematic fusemq-leveldb
that is fixed on trunk with https://issues.apache.org/jira/browse/AMQ-3890
On 27 August 2012 20:19, Sébastien Lorber wrote:
> Yes i know and i have excluded the problematic fusemq-leveldb
>
> But wouldn't it be better to put this dependency as optional so that users
> wouldn't have to do themselv
Yes i know and i have excluded the problematic fusemq-leveldb
But wouldn't it be better to put this dependency as optional so that users
wouldn't have to do themselves the exclusion?
Because retrieving hadoop, scala... that's pretty "heavy" for just the
leveldb feature, and will cause conflicts f
On 27 August 2012 15:53, Sébastien Lorber wrote:
...
> And it will produce conflicts by default to many jetty users like me i
> guess.
This has come up before; I think
http://mail-archives.apache.org/mod_mbox/activemq-users/201206.mbox/%3CCA+GjePWRZn-ZgY0=eg3bjmi8zxqhnyya36us7fmk684eh_c...@mail.g
Sebastien,
I do not know if you know that you could around this issue by using the
exclusion option at
http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html.
--Claudio
>
> From: Sébastien Lorber
>To: users@activemq
Francesco,
This is a bug and you should create a jira issue for this so that it can get
fixed.
--Claudio
>
> From: Francesco Romano
>To: users@activemq.apache.org
>Sent: Monday, August 27, 2012 2:40 AM
>Subject: Re: NIO+SSL How retrieve the SSL session certif
Thanks, the only problem with the onPause flag option is that when I pause my
message listener I want messages to stay on the broker. By the time the code
runs in the message listener the message will have been downloaded from the
broker particularly as this method is asynchronous.
Will have a
Hi Sharma
I will try that (turn off the dedicated task runner) and advise, please see
below the answers to the questions that you have asked.
1. how many processors/cores do your machines have?
16 cores
2. are your clients (producers/consumers) local to the broker on the same
machine but
Hmm, actually, if you do setMessageListener(null) on
the DefaultMessageListenerContainer, it will throw an
IllegalArgumentException in checkMessageListener(), so, that shouldn't work.
The stop(), start(), isRunning() methods do seem like a good option to
pause the listener via spring. The other wa
That's a lot of threads. You might wanna turn off the dedicated task runner
via either the activemq connection factory (in code) or via config (
http://activemq.apache.org/how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker-.html
).
A couple of questions from the thread dump analysis:
1.
not at the moment, a temp queue always keeps messages in memory. I
know this has come up before and i think it is a sensible enhancement
to allow the pending message cursor to be configured for a temp
destination such that a temp destination need not be limited by
memory.
Can you raise a jira issue
Hello,
After some troubles with the following stacktrace while running my
webapplication with Jetty,
java.lang.NoSuchMethodError:
org.eclipse.jdt.internal.compiler.CompilationResult.getProblems()[Lorg/eclipse/jdt/core/compiler/CategorizedProblem;
at
org.apache.jasper.compiler.JDTCompiler
Hi,
after some experiments, it seems that maybe one part of the problem is that
temp-queue messages are not spooled to disk. Is there a possibility to tell
ActiveMQ 5.5 to spool them to the temp store as well?
Another issue I noticed, after purging a queue with non-persistent
messages, the space
Hi,
in one of the instances I didn't find anything in the broker log, just in
the client log, in the second log I found the same log entry in both client
and server:
javax.jms.ResourceAllocationException: Usage Manager Memory Limit reached.
Stopping producer (ID:hostname:26:33:1) to prevent flood
Hi,
I am using a Asynchronous MessageListener with onMessage within a
DefaultMessageListenerContainer. My service is then deployed into tomcat.
I would like to know if there is a recommended way for
activating/deactivating my messagelistener programatically? It seems like
quite a reasonable or co
what is out put to the broker log when it stops processing? It should
report the limit that is reached.
The pendingQueueCursor will stop caching messages when the systemusage
limit reaches 70%, but it won't spool to disk. The persistent messages
will just remain in the store till they are needed.
Hi Gary,
sorry for getting back to this rather old issue, but I just got an issue in
the field (twice) with the configuration below. The broker stopped
accepting messages after it reached the 64MB memory limit, instead of
spooling them out to disk. It basically is the previously discussed
configur
22 matches
Mail list logo
