Hi Gary
Yes, it helps me. Thank you.
I understand that, if I have a Java reference of the embedded brokerService
object, and use brokerService.stop(), I will gracefully quit the network of
broker . Good ! It's the main part of my question.
You told me that I can continue to use my URI syntax.
This looks suspiciously related to a problem that we have been encountering,
but have been unable to narrow down. I don't know if there is an existing
JIRA for this, but if there is, I'd vote for it. Top priority.
Thanks for reporting your insights on this issue.
On Thu, Feb 19, 2009 at 2:57 AM
I'll look at the source and see if I can make it do what I want, and
submit a patch. Currently the failover transport blocks on sending a
connection info message to the remote broker as part of startup, and I
think already has a mechanism to do that on reconnect.
Uwe
On Thu, 2009-02-19 at 07:42
hey dejan,
after thinking about the stomp ack described on the wiki page i have some
points to mention. As far is i understand the behaviour of jms transacted
sessions, the big advantage is the use of the message broker for delayed
delivery.
for me this was understood as a message broker support
INFO: Journal is locked... waiting 10 seconds for the journal to be
unlocked.
Feb 19, 2009 11:21:58 AM
org.apache.activemq.store.journal.JournalPersistenceAdapterFactory
createJournal
This is exception i am seeing continuously in my logs and queue is not
functional any more.
I tried restartin
The following is the exception in our production logs.
Feb 17, 2009 10:03:01 PM
org.apache.activemq.store.journal.JournalPersistenceAdapter doCheckpoint
SEVERE: Failed to mark the Journal:
org.apache.activeio.journal.InvalidRecordLocationException: The location is
less than the last mark.
org.apa
On Thu, 2009-02-19 at 19:06 +0100, Eduardo Montoya wrote:
> Hello,
>
> I have some problems when reading a cms::BytesMessage.
>
> first of all, my client code looks like:
>
> void MyMessageListener::onMessage( const Message* message )
> {
> const BytesMessage* b = dynamic_cast( message );
>
Hi all. I'm getting an unexpected error when working with messages in a DLQ
using the jetty Web Console. After resolving the issue client side that
caused a message to be placed into a DLQ, we'd like to move the message back
to the originating Queue for normal processing.
The error I'm seeing i
I'm using a large number of consumers (>20) for a single queue in my
application, and at times of high volume it appears somehow that the number
of pending messages count goes negative, and the messages received number is
higher than the messages sent number. Which obviously explains the negative
Hello,
I have some problems when reading a cms::BytesMessage.
first of all, my client code looks like:
void MyMessageListener::onMessage( const Message* message )
{
const BytesMessage* b = dynamic_cast( message );
if (b != NULL)
{
std::size_t len = b->getBodyLength(); // thi
Check out http://activemq.apache.org/failover-transport-reference.html
If it is attempting to establish a connection it will block.
With the timeouts and such you might be able to get around start() blocking
and do your own queuing of messages because if there isn't a valid
connection the send(
ActiveMQ version: 5.2, 5.1, 4.1.1
Eclipse Equinox OSGi Version: 3.4
JVM: 1.6.0_11
When attempting to connect to an ActiveMQ server while running within a
simple Equinox OSGi (Eclipse) plugin the connection fails half the time with
a timeout, while the other half it takes over 30 seconds to establ
thanks for the verification. I think the analysis in AMQ-2102 is spot
on, for a slave, the ack validation logic needs to be able to cope
with an ack for a different consumer as the actual dispatch logic is
not in sync between the master and the slave. In essence, to accept
the ack, the slave will n
Hi Hans,
this is not supported yet. I just filed an enhancement request
https://issues.apache.org/activemq/browse/AMQ-2127
Cheers
--
Dejan Bosanac
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Thu, Feb 19
I tried 5.3-SNAPSHOT and got exactly the same problems.
Gary Tully wrote:
>
> could you try your scenario against a 5.3-SNAPSHOT[1], there is a
> known issue but it occurs with multiple consumers only. see:
> https://issues.apache.org/activemq/browse/AMQ-2102
>
> [1]
> http://people.apache.org
Hi Eirc,
If you want to access the broker service you should use the
org.apache.activemq.broker.BrokerFactory to create it and return a
reference. The create takes the same uri syntax as a
connectionFactory.
The details can be found at:
http://activemq.apache.org/how-do-i-embed-a-broker-inside-a-c
Hi,
seems like its still a problem in 5.2.0 (fuse 5.2.0.2).
The problem is quite easy to reproduce:
1.Limit the memoryUsage in activemq.xml to -say- 50MB.
2.set producer flow control=false and disable saving messages to disk.
2.Start one producer publishing non-persistent messages with TTL=5sec
Hi Jörg,
I did some analysis of the per message allocations from your email. It
is clear that each store write allocates a bunch of objects, however,
from code inspection, I cannot see a point where they are leaked
through a reference.
There are two relevant points that may make static analysis a l
18 matches
Mail list logo
