Julian Scheid wrote:
I have a durable topic distributed over two broker nodes and it's
working just fine, however messages get lost when I artificially
disconnect and later reconnect one of the brokers.
This could be related to http://issues.apache.org/activemq/browse/AMQ-1076
Using ActiveMQ 4.1
I have a producer that does the following -
1. main thread creates a Connectionfactory using tcp
2. creates a few threads - say 5
3. each thread creates a new Connection and a new Session using the
connectionfactory created in the main thread. Session is created with
auto-ack
to further respond to my own posts,
just tried to get mysql masterslave going and ran into this bug:
http://www.nabble.com/Master-Slave-locking-with-MYSQL-is-not-working-with-4.1.1-tf3399897s2354.html#a9475786
is there any way to get redundancy working with 4.1.1??
jdemic wrote:
>
> To furt
To further complicate this, I just tested failover and the following
happened:
- i kill -9'd activemq on the master server.
- on the slave server, activemq was still spinning on the filesystem lock as
per my last email.
- when i started up the master again, it started spinning on the filesystem
l
Hey All,
I'm attempting to setup activemq in a master/slave configuration as follows:
http://activemq.apache.org/shared-file-system-master-slave.html
I'm setting this up ontop of redhat es3 using the shared journal on an NFS
mount. When i start the slave, the following occurs:
faultPersistenc
On 9/5/07, budcurtis <[EMAIL PROTECTED]> wrote:
>
> Thank you for that explanation. =) That is what I didn't understand, the
> embedded Jetty is not until ActiveMQ 5.0.
No worries, our bad - we don't always document exactly when each
feature is released etc.
So can you switch from SONIC now? :)
Thank you for that explanation. =) That is what I didn't understand, the
embedded Jetty is not until ActiveMQ 5.0.
Can you explain what the ACTIVEMQ_CLASSPATH attribute is suppose to contain.
For example, is it intended to contain the jars in the lib/optional or are
those automatically added to
Hi again,
my experiments have also showed that having Session with
CLIENT_ACKNOWLEDGE mode instead of transacted session and issuing
message.acknowledge() after each consumed persistent message also
gives huge performance grow comparing to Session.commit(). Now I can
consume more than 3000 msg / s
Hi,
resolving TCP_NODELAY issue made Session.commit() fast after each
non-persistent message consumption when broker is running Linux.
However, commit is no longer fast when consuming persistent messages.
Performance running broker both on Windows and Linux is no more than
10 msg / sec.
I suppos
tabish121 wrote:
>
> Sounds like it could be a bug.
>
> The best thing to do is to create an issue in Jira:
> http://issues.apache.org/activemq/browse/AMQCPP
>
> Describe the problem and the expected behavior. Same sample code that
> demonstrates the problem is appreciated along with as much
Sounds like it could be a bug.
The best thing to do is to create an issue in Jira:
http://issues.apache.org/activemq/browse/AMQCPP
Describe the problem and the expected behavior. Same sample code that
demonstrates the problem is appreciated along with as much information
on reproducing it as pos
Does anyone have any advice on how to cleanly close a session when comms to a
broker is broken?
After the comms have been broken (shutting down the broker is an easy way to
reproduce) and the producer attempts to send a message a Transport IO
exception is raised but after this point the session c
Hi All!!
I am new to apache ActiveMQ. Can someone tell me what is new in ActiveMQ
4.1 as compared to the previous version?
Thanks in advance
regards
Ashish
Dear all,
I am trying to use the PooledConnectionFactory with Spring on a producer
connected to a network of brokers (B1 and B2).
The scenario is the following : I start B1 and B2 and send 100 messages to
the network with the brokerURL : failover:(tcp://myip:61616,
tcp://myip:62626) .
Then I
On 9/5/07, jgunz <[EMAIL PROTECTED]> wrote:
> I realized after I sent my original message that I didn't specify what type
> of clustering I was referring to. I think I understand how the routing rules
> would work in a master/slave setup but I'm still a little foggy on how they
> would function in
I realized after I sent my original message that I didn't specify what type
of clustering I was referring to. I think I understand how the routing rules
would work in a master/slave setup but I'm still a little foggy on how they
would function in a store and forward network of brokers. My goal in
Ooops, my-bad. The delivery mode is set to PERSISTENT. I was not using the
producer's setDeliveryMode method :o)
Joe
James.Strachan wrote:
>
> On 9/5/07, ttmdev <[EMAIL PROTECTED]> wrote:
>>
>> I am doing the following:
>>
>> 1. I start a broker with persitent="false" and no destinations def
Hi,
I have a durable topic distributed over two broker nodes and it's
working just fine, however messages get lost when I artificially
disconnect and later reconnect one of the brokers. To elaborate:
I've set up two broker nodes on two different hosts, broker B1 on host
H1 and broker B2 on h
Just wondering whether anyone has seen this error before. I am using the
ttl facility on some messages in my system. Is it a known bug?
2007-09-04 16:41:57,394 [VMTransport] WARN - Failed to pass expired
message to dead letter queue
java.lang.NullPointerException
at org.apache.acti
Ah my mistake - that only works on the client side - not on the broker side.
On 9/5/07, James Strachan <[EMAIL PROTECTED]> wrote:
> As described on AMQ_1156, why not use
>
> ?socket.tcpNoDelay=true
>
>
> On 9/5/07, Dziugas Baltrunas <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I hope tcpNoDelay flag
As described on AMQ_1156, why not use
?socket.tcpNoDelay=true
On 9/5/07, Dziugas Baltrunas <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I hope tcpNoDelay flag will be updated in next release of ActiveMQ.
> For those using 4.1.1 version there are two workarounds:
>
> 1. Modify the source code as describe
Thanks this was of great help also - I was wondering if their is a way to
set round robin load balancing policy on the client producers of a queue.
On 9/4/07, corcorda <[EMAIL PROTECTED]> wrote:
>
>
> You were completely right. Sorry, I managed to read the prefetch article
> and
> still miss it.
>
Hi,
I hope tcpNoDelay flag will be updated in next release of ActiveMQ.
For those using 4.1.1 version there are two workarounds:
1. Modify the source code as described in AMQ-1156.
2. In lib/activemq-core-4.1.1.jar edit
META-INF/services/org/apache/activemq/transport/tcp and change
class=org.apa
Hi,
I am using apache-activemq-5.0-20070826.220436-61 on windowsXP Pro SP2 and
Java version "1.6.0_02". I am using below xml file for configuration. With
this configuration ActiveMQ starts and samples work fine.
http://www.nabble.com/file/p12493391/activemq.xml activemq.xml
When I change conf
24 matches
Mail list logo