logged with a possible patch: https://issues.apache.org/jira/browse/AMQ-5211
boday wrote
FYI, I was able to reproduce this issue…its because a queue with no name
was created when using JMX to send messages in between queues...I'll log a
ticket with more info...
--
View this message
FYI, I was able to reproduce this issue…its because a queue with no name was
created when using JMX to send messages in between queues...I'll log a
ticket with more info...
--
View this message in context:
any other thoughts on this? we have seen this several times now when we
bound AMQ (using mkahadb)...have had to archive the entire data directory to
restart...any other way to recover this data (manually moving files back in
or something)...otherwise, these queues/messages are orphaned/lost
--
)
at org.apache.activemq.console.Main.runTaskClass(Main.java:262)
at org.apache.activemq.console.Main.main(Main.java:115)
boday wrote
any other thoughts on this? we have seen this several times now when we
restart AMQ (using mkahadb) with messages in the queues. we have had to
archive
in there.
On 12 March 2014 14:52, boday lt;
ben.oday@
gt; wrote:
thanks, I took a look at that issue, but I don't see any truncated
directory
names or warning about this in the logs...any other thoughts?
gtully wrote
I wonder if it is related to truncation. See
https://issues.apache.org/jira
thanks, I took a look at that issue, but I don't see any truncated directory
names or warning about this in the logs...any other thoughts?
gtully wrote
I wonder if it is related to truncation. See
https://issues.apache.org/jira/browse/AMQ-4183
On 11 Mar 2014 23:50, boday lt;
ben.oday@
gt
after bouncing our ActiveMQ 5.9.0 broker, I see these in the logs
INFO | pending local transactions: []
INFO | Corrupt journal records found in
'/usr/local/eda/AMQ_GW/data/kaha/queue#3a#2f#2f/db-1.log' between offsets:
3123034..3123105
INFO | Corrupt journal records found in
at this point, I can't reproduce it on demand, just seeing random locking
occur after hours of uptime...
ceposta wrote
Any chance you can reproduce this?
On Tue, Jul 23, 2013 at 1:03 AM, boday lt;
ben.oday@
gt;wrote:
no errors in the logs, but we see message flow resume after
seeing some thread blocking in our ActiveMQ 5.7 production application (using
VM transport and AMQ connection pool)...anyone know of any
configuration/known bugs that could be contributing to this?
seeing 20 thread like this one, WAITING for a single thread to release a
lock on 659ec0a4
Camel
that connection to block...
On Mon, Jul 22, 2013 at 3:46 PM, boday lt;
ben.oday@
gt;wrote:
seeing some thread blocking in our ActiveMQ 5.7 production application
(using
VM transport and AMQ connection pool)...anyone know of any
configuration/known bugs that could be contributing to this?
seeing
I have 2 AMQ 5.7 brokers, one sends messages to the other via a
JMSTemplate/PooledConnectionFactory/FailoverTransport. It functions fine,
but I see these Successfully connected to... messages in my logs for every
message that is sent...is this expected?
I know I can suppress them with log4j
/PooledConnectionFactory/FailoverTransport.
2 brokers and one sends to the other using JmsTemplate?
On Mon, Dec 10, 2012 at 10:38 AM, boday lt;
ben.oday@
gt;wrote:
String failoverBrokerUrl =
failover:tcp://localhost:61666?randomize=falsetimeout=1;
ActiveMQConnectionFactory factory = new
Kripalani*
Apache Camel Committer
Enterprise Architect, Program Manager, Open Source Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
lt;http://twitter.com/raulvkgt;
On Mon, Dec 10, 2012 at 6:27 PM, boday lt
I tested my ActiveMQ 5.5.0 (fuse version) app in AMQ 5.6.0 and noticed that
our Spring JNDI configured Oracle datasources aren't being found.
The only thing I changed in my applications was the pom.xml versions of
AMQ/Spring (to match the 5.6 versions). Otherwise, I'm using the identical
I found the issue, I added a jndi.properties file under the amq/conf
directory containing the following and it works fine now (didn't need this
under AMQ 5.5, strange)...
java.naming.factory.initial =
org.apache.xbean.spring.jndi.SpringInitialContextFactory
--
View this message in context:
I'm using AMQ message groups with AMQ 5.5.0-fuse-00-27 with Kahadb persistent
messaging and periodically see this WARN in the logs. I don't see any
specific errors that result from this, but am wondering what the side
effects of this are, etc.
My consumer is a Camel (2.7.1-fuse-00-27) route with
amq; every now and again let some
lower priority messages through. It begs lots of questions and it
would be quite complex to achieve :-)
Priority support can be enabled on a per destination basis, so it need
not be respected if you don't want it.
On 31 August 2012 00:41, boday lt;ben.oday
I'm also seeing this message frequently after upgrading from 5.3 to 5.5,
anyone know what causing this? Is it anything significant to worry about?
oscarp wrote
Hi all,
I was testing an application and I saw that one producer couldnt send
messages to the broker. I cant understand why, and
lets say I have a single (slow) consumer from a priority queue and I produce
mostly high priority messages to it...will low priority messages ever get
processed (based on duration in the queue, etc)?
I know there are workarounds (manually promoting, resequencers, using
multiple queues, etc), but
are you using Windows? If so, you might see this bug
https://issues.apache.org/jira/browse/AMQ-3273 AMQ-3273 ...it caused me a
lot of confusion while trying to test this scenario.
Vijay wrote:
I am rephrasing my question for get rid of confusion.
We have a Converter app (Standalone JMS
for your input!
Best regards,
Martin
On Fri, Jul 1, 2011 at 6:21 AM, boday
lt;ben.o...@initekconsulting.comgt; wrote:
Is your issue that certain consumers become too slow? If so, you can
always
set the JMSXGroupSeq header to -1 to force a new consumer (maybe set this
periodically or after
Is your issue that certain consumers become too slow? If so, you can always
set the JMSXGroupSeq header to −1 to force a new consumer (maybe set this
periodically or after a certain number of messages)...
here is a good article that discusses this a bit...
see http://activemq.apache.org/shared-file-system-master-slave.html
In short, consumers should use the following URLs. If the consumers are
embedded in the brokers, then using VM for the transport appears to work
fine. However, if the broker goes down, so does the consumer (generally)...
I'm trying to determine my options for clustering my AMQ 5.3 application that
uses ServiceMix 3.3.1 and Camel 2.1. I'm performing high volume message
processing and I need to cluster for high availability and horizontal
scalability.
Here is basically what my application does (using Apache
how do I set the concurrnetConsumer/maxConcurrentConsumer properties when
using message groups?
For example, if I set the maxConcurrentConsumers to 10 and I send messages
with 100 different JMSXGroupIDs...will the consumers be created/destroyed as
necessary or does a single consumer get reused
what happens when an exception occurs? Is the consumer thread halted while
performing exception handling on the current message or are other messages
processed in parallel? Is there a way to programatically control this?
For example, if a processing exception is thrown and a retry policy is
26 matches
Mail list logo
