Re: uses virtual topic and ClientAcknowledge to submit themessageoccured probem

I tested on the latest 5.3 snapshot (-5.3-20090620.174423-1-bin) and the same exception occurs. I don't know if this is related to NMS or not. Maybe you could try to replicate it? Can you run your unit test and look at the broker log to see if the error is logged? magellings wrote: > > I ca

Re: uses virtual topic and ClientAcknowledge to submit themessageoccured probem

I can give 5.3 a shot. But there is an issue created for 5.4 right now. https://issues.apache.org/activemq/browse/AMQ-1763 This is why I was wondering if it is related to NMS or the broker. The original poster mentions VT work fine with java code. I'm currently using 5.2 and 1.1 of NMS.

Re: uses virtual topic and ClientAcknowledge to submit themessageoccured probem

Thanks for the offer of help. I am not sure where the problem is. I have seen broker problems with virtual topics if queue mirroring is turned on, so it is possible the error is in the broker. It would be good to test against the latest ActiveMQ 5.3 snapshot. - Jim -Original Message- F

Re: uses virtual topic and ClientAcknowledge to submit themessage occured probem

Are you using the latest trunk code, or is this a version that you've had for awhile? Regards Tim. On Mon, 2009-06-29 at 11:56 -0700, magellings wrote: > Hey Jim thanks for the response. > > I took a look at your test. > > I too can receive messages just fine with a transactional session. >

Re: uses virtual topic and ClientAcknowledge to submit themessage occured probem

Hey Jim thanks for the response. I took a look at your test. I too can receive messages just fine with a transactional session. The problem is that the message does not get removed from the queue when you commit the session. Instead the broker writes to the log an error like the following and

Re: Does The ActiveMQ treat the same clientID consumer on different broker as different consumer?

Pre-configuration to set up network: broker A localhost:61616 http://www.nabble.com/file/p24259347/activemq_61616.xml activemq_61616.xml broker B localhost:51616 http://www.nabble.com/file/p24259347/activemq_51616.xml activemq_51616.xml For localhost:61616 I change the netw

Does The ActiveMQ treat the same clientID consumer on different broker as different consumer?

Broker A and broker B build up a network of brokers. Assuming in this case a client registered on broker A with clientID "client1" and somehow he lost the connection, at that time some messages came, next time when the "client1" resume the connection on broker B, he supposed to receive the messag

Re: I can not start activemq on Red hat Linux 64 bits computer, looks like can not found log4j......

Ok so this is pretty interesting. IT was definitely conflicting with something else. I have a feeling it's the log4j jar that's in my eclipse plugins directory. Anyway, when I delete log4j from the activemq lib/optional directory, it works. bsnyder wrote: > > On Mon, Jun 29, 2009 at 9:44 AM

Re: uses virtual topic and ClientAcknowledge to submit themessage occured probem

I created some virtual topic tests for NMS awhile ago, and they are all working. You can view the tests in VirtualTopicTest.cs in the Apache.NMS.ActiveMQ project. Regarding this particular problem, I would have to do further investigation to find the ultimate source of the problem. - Jim --

Re: uses virtual topic and ClientAcknowledge to submit the message occured probem

Is this an NMS specific problem or with the actual broker? I see the link below but the user is saying everything works with java code. Does anyone know what version of ActiveMQ Virtual Topics did work? http://activemq.apache.org/virtual-destinations.html pclovec wrote: > > i try to test

Re: I can not start activemq on Red hat Linux 64 bits computer, looks like can not found log4j......

On Mon, Jun 29, 2009 at 9:44 AM, zfbrad wrote: > > Did you figure out what was going on here?  I'm running OSX and I have the > same exception. Seems to not be able to find log4j even though it's in the > activemq directory. I develop and run ActiveMQ on MacOS X all the time without this issue. Ho

Re: I can not start activemq on Red hat Linux 64 bits computer, looks like can not found log4j......

No, I didn't. sorry. I switched to 32 bits linux zfbrad wrote: > > Did you figure out what was going on here? I'm running OSX and I have the > same exception. Seems to not be able to find log4j even though it's in the > activemq directory. > > > Websphere and ActiveMQ wrote: >> >> Yes. lo

Re: I can not start activemq on Red hat Linux 64 bits computer, looks like can not found log4j......

Did you figure out what was going on here? I'm running OSX and I have the same exception. Seems to not be able to find log4j even though it's in the activemq directory. Websphere and ActiveMQ wrote: > > Yes. log4j jar file is there. > > > bsnyder wrote: >> >> On Tue, May 12, 2009 at 2:42

Re: JDBC Master Slave Question

You have got to ask the JDBC driver or database documentation. I imagine there is a lock expiry option that can be tweaked. 2009/6/29 colonelx > > Hi, > > I have 2 brokers setup in a JDBC Master Slave Configuration. > > Each broker is on a different machine. BoxA and BoxB > The database is also

ZipException on Ubuntu server

Hi When I start AMQ on my MacBook it works fine but when I run the same code on a Ubuntu hosted server I get the attached exception. The result is that I can not browse the queues with the admin web app. I notice there is a similar issue noted with regard to an rpm distribution: Jira AMQ-2105. se

Re: JDBC Master Slave Question

I know that I could test this by plugging in and out the physical network connections, but I'm not really in a position to do this on any of the above boxes. If you are on Windows you can use TCPView to kill connections without having to physically disconnect the network:

JDBC Master Slave Question

Hi, I have 2 brokers setup in a JDBC Master Slave Configuration. Each broker is on a different machine. BoxA and BoxB The database is also on a different machine BoxC. (mysql 5.1) The failover is working fine when I manually kill any instance of ActiveMQ on BoxA or BoxB. (Ctrl-C) However, can