Can you raise a jira issue to track this, it points to a problem with
the query parsing, it is typically called with the query string minus
the leading '?' but is attempting to jump to the last '?' which is
causing it to pick up the wrong parameter.
from a cursory look, the fix is:
Index:
I use ActiveMQ-cpp to make a connection with an AcitveMQ server. The
CMSConnection is started with:
// Create a ConnectionFactory
auto_ptrConnectionFactory connectionFactory(
ConnectionFactory::createCMSConnectionFactory( brokerURI ) );
// Create a
There is no easy answer, the a new bridge is created after each
failure, so there is no resume, just a new start.
The corresponding mbeans come and go as the bridges start and
disappear so JMX could give you a handle to active bridges and
possibly a notification on mbean registration.
Another
On Wed, 2010-12-08 at 05:17 -0800, joost wrote:
I use ActiveMQ-cpp to make a connection with an AcitveMQ server. The
CMSConnection is started with:
// Create a ConnectionFactory
auto_ptrConnectionFactory connectionFactory(
Just switched to kahadb on my amq 5.4.1 (fuse) and the log is filling
with this:
2010-12-08 14:26:12,668 | WARN | KahaDB PageFile flush: 3 queued writes, latch
wait took 119 | org.apache.kahadb.page.PageFile | ActiveMQ Journal Checkpoint
Worker
2010-12-08 14:28:03,769 | WARN | KahaDB
Changing the failover settings (or just disabling failover) solved the
problem.
Thanks!
Joost
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-cpp-Check-if-ActiveMQ-server-is-running-tp3078173p3078288.html
Sent from the ActiveMQ - User mailing list archive at
In the main, it is not important, that should be at debug or trace
level logging or removed altogether, it is just an indication of the
pagefile sync to disk latency and the amount of concurrent writes that
are pending at the time, an remnant of some performance tuning work
that was done for
In the startup script, add
-Dorg.apache.activemq.store.kahadb.LOG_SLOW_ACCESS_TIME=0
to SUNJMX to turn off this logging.
At least this works with 5.3.0.
Peter P
-Original Message-
From: Gary Tully [mailto:gary.tu...@gmail.com]
Sent: Wednesday, December 08, 2010 10:24 AM
To:
[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor31]
Exception in thread BrokerService[SUPALARM-tterdp31v] Task
java.lang.ArrayIndexOutOfBoundsException: -32768
at
org.apache.activemq.openwire.BooleanStream.writeBoolean(BooleanStream.java:54)
at
The producer could handle this by listening to consumer advisories for
its topic,
the first subscription to the consumer advisory topic will get all of
the connected consumers and it can decrement on each consumer remove
command etc.
http://activemq.apache.org/advisory-message.html
Having the
That looks like some concurrent access to the brokerInfos. Can you
open a jira issue and attach as much relevant info about your setup as
possible.
I think the problem is in the
org.apache.activemq.command.BrokerInfo#copy() method, it does not deep
copy the brokerInfo array.
On 8 December 2010
Hello there, i have mounted HDFS using FUSE and I want to use ActiveMQ with
amqPersistenceAdapter the directory of ythe mounted HDFS filesystem. However
there seems to occurs some problems. Looking at the logs one can see the
following (when starting the broker)
20 10-12-08 21:02:59,643 |
Gary, thanks for the answer. I'll see what I can figure out.
Brett
On Wed, Dec 8, 2010 at 10:19 PM, Gary Tully gary.tu...@gmail.com wrote:
There is no easy answer, the a new bridge is created after each
failure, so there is no resume, just a new start.
The corresponding mbeans come and go
I have been banging my head against this for several days.
I have a case of durable/retroactive message recovery that is very long and
involves a lot of messages. It is done with a custom
SubscriptionRecoveryPolicy that gets the messages from a special store.
This can involve literally hours
I posted to the ActiveMQ - Dev forum, but the post has not yet been sent to
the maillist. I am having trouble subscribing. Since the addressee email
address is too long, I did what the email instructed and sent email to
dev-allow-requ...@activemq.apache.org with the subject of
On Wed, Dec 8, 2010 at 9:14 PM, Steve.V. stephen.vinc...@sas.com wrote:
I posted to the ActiveMQ - Dev forum, but the post has not yet been sent to
the maillist. I am having trouble subscribing. Since the addressee email
address is too long, I did what the email instructed and sent email to
Yes, that just causes a confirmation email message to be sent to me. I can't
simply reply to it since the address is too long, and as I mentioned in the
original post, my attempts at sending email to the other suggested addresses
gets me nowhere.
I had no problem subscribing to the ActiveMQ -
17 matches
Mail list logo
