in the project of incubator-activemq-cpp-1.0-src.zip , all code like this :
string t1 = "11";
string t2 = "11";
t1 = t2 ; // throw exception here!
if i create a new project, there is no problems!
--
View this message in context:
http://www.nabble.com/string-problem-about-incubator-a
Nevermind guys - I've realized that the Queue doesn't get populated upon
failover but only after a Producer or Consumer also fail to the new broker.
Cheers!
spiderman2 wrote:
>
> When failing over to a slave, should the unconsumed messages of the broker
> be entered in the queue of the slave?
>
Hi Juan,
The c/c++ client with the most active development is activemq-cpp (
http://activemq.apache.org/activemq-c-clients.html). Version 1.1 has just
been released (although we haven't yet updated the links on the download
page) http://activemq.apache.org/activemq-cpp-11-release.html
For exampl
Hi all!
Anyone have seen this exception in 4.1.0? I only use Java clients to
commincate with AMQ. Any ideas?
I get a lot of "org.apache.activemq.transport.InactivityIOException: Channel
was inactive for too long" messages before and after the ClassCastException.
java.lang.ClassCastException: or
When failing over to a slave, should the unconsumed messages of the broker be
entered in the queue of the slave?
I'm not seeing this happen. I'm following the example of
http://activemq.apache.org/jdbc-master-slave.html JDBC Master Slave and I'm
using JConsole to see the number of messages in t
Another way to solve your problem is to use the "failover://" URI.
http://activemq.apache.org/failover-transport-reference.html See
http://activemq.apache.org/failover-transport-reference.html
for an example on how a consumer can fail from a master to a slave.
Matías Cobiella wrote:
>
> Hi,
PooledSession does not appear to use the Topic supplied to the
createPublisher(topic) method, at least when obtained from
PooledConnectionFactory.
When the publish(Message) method is called on the returned
TopicPublisher instance, an UnsupportedOperationException is thrown ("A
destination must
Thanks, I know the failover URI's, but I need the behavior that I've
mentioned.
spiderman2 wrote:
>
> Another way to solve your problem is to use the "failover://" URI.
>
> http://activemq.apache.org/failover-transport-reference.html See
> http://activemq.apache.org/failover-transport-refer
Hi,
Is there some way that one Client connects to a SLAVE with the same hostname
and port of the MASTER host?
I mean. The Client connect to the MASTER (tcp://150.0.0.1:61616), when the
MASTER goes down, the SLAVE becomes MASTER but with the same url
(tcp://150.0.0.1:61616) and the Client failove
Hi, I'm new to the list and to ActiveMQ. I'm starting a project where
several C and Java distributed processes will have to communicate
among themselves and I wanted to use ActiveMQ for it.
I've seen there are several C/C++ interfaces and I wanted to know
which one is the recommended one. One of
Unfortunately this is looking suspiciously like an inter-version
interop problem - its looking like the Client's ConnectionInfo does
not appear to have a ConnectionId when the broker reads it.
Unfortunately it looks from this log like 4.0.1 and 4.1 do not
interoperate :(
On 2/12/07, Thomas Swind
Appologies if this has already been recorded in a defect somewhere.
I am running an ActiveMQ 4.1 broker. Another team have developed a client
based upon ActiveMQ 4.0.1. They are running it within Tomcat and were having
probems with their service starting as it was failing to connect to my
broker.
That's not really enough information to go on. Could you provide a snippet
of your program and indicate on which line it fails?
On 2/11/07, penny_hu <[EMAIL PROTECTED]> wrote:
i download the incubator-activemq-cpp-1.0-src.zip from the amq website.
but
everytime when i run it , it will throw
On 2/12/07, Steven Marcus <[EMAIL PROTECTED]> wrote:
Hello all!
In the late January 4.2 snapshot the commons-collections had been
upgraded to 3.1
I notice in the Feb9 4.2 snapshot the commons-collections has reverted to 2.1.
Hmm, I'm not quite sure how that happened. BTW you just mean the jar
On 2/8/07, MqUser <[EMAIL PROTECTED]> wrote:
I need to set up many fast and lossless clients (producers) on different
computers.
Each has to be able to create message quickly, not lose them, and move on to
the next operation.
That would mean each has to have an embedded broker with persistent
The jgroups transport was never ported across to Apache since jgroups
is LGPL and Apache code is not allowed to link to LGPL libraries. So
currently Apache ActiveMQ does not support jgroups.
On 2/10/07, Sampangi Apparao <[EMAIL PROTECTED]> wrote:
Hi,
I am facing a problem, while jgroups transp
16 matches
Mail list logo
