Re: Activemq 5.1 or 5.0.1 release ?

On 9 Apr 2008, at 23:30, realSri wrote: Hi, When do you expect the next release (5.1 or 5.0.1 ?) to come out (which has the inactivity monitor fix) ? If we have 5.0 clients and broker does upgrading broker suffice ? (assuming the fix is on the broker side). Thanks, - Sri -- View this m

"Duplex" problems

I have two brokers (call them A and B), where A establishes a connection to B with the options: duplex="true" networkTTL="3" dynamicOnly="true" I have two clients connecting to broker A, and one to B. One of the clients on A is subscribing to a queue, the other is publishing to it. The client o

BrokerFilter.acknowledge implementation

could someone please suggest a way to implement acknowledge which would be used to get notification about receiving a message. method signature: public void acknowledge(ConnectionContext context, MessageAck ack) thanks -- View this message in context: http://www.nabble.com/BrokerFilter.acknowl

Activemq 5.1 or 5.0.1 release ?

Hi, When do you expect the next release (5.1 or 5.0.1 ?) to come out (which has the inactivity monitor fix) ? If we have 5.0 clients and broker does upgrading broker suffice ? (assuming the fix is on the broker side). Thanks, - Sri -- View this message in context: http://www.nabble.com/Activem

ActiveMQ message is not consumed

This is my Spring configuration and I have ActiveMQ integrated with JBoss. I am able to add messages to the queue but they never seem to get picked up. I understand that the connection needs to be started. Where should this be done? And is it possible to make it the default behavior? I tried to st

Re: Persistence From Redo Log Only?

When i stopped using jms transactions, and started using client acknowledgements, all these problems went away, and AMQ 5.1-snapshot is now very stable and working just as expected. So my personal recommendation - do not use transactions. Use client acknoledgements instead (acknowledge instead of

how to find wether a message is consumed or not

i have been working on jmx and have found a way to know wether a message has been consumed and that would be to invoke the getMessage method on the queue mbean with the message id. is there a better, simpler or more efficient way to know the status of a message? thanks -- View this message in c

Re: completely disabling Kaha Store

Ah. Okay, thanks. rajdavies wrote: > > Unfortunately you need to set any persistence parameters before adding > a connector ... > > > > On 9 Apr 2008, at 00:44, yg_cvg wrote: > >> >> Oddly enough, doing >> >> m_broker = BrokerFactory.createBroker("broker:()? >> persistent=false"); >

Re: Messages hang in Queue even when consumers are present after failover

Okay, I think I found the problem. There is a race condition between the time the message is set with the broker sequence number (RegionBroker.java in send method), and the time it is actually put in the database (DefaultJDBCAdapter.java in doAddMessage method). I have seen that sometimes messa

Re: wrong exception thrown?

thx - fix just committed On 9 Apr 2008, at 15:25, jackrabbit wrote: FYI: the issue number is AMQ-1651. -- View this message in context: http://www.nabble.com/wrong-exception-thrown--tp16560154s2354p16586193.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: wrong exception thrown?

FYI: the issue number is AMQ-1651. -- View this message in context: http://www.nabble.com/wrong-exception-thrown--tp16560154s2354p16586193.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Web console for broker with a name

Hi, you can take a look at this article http://www.nighttale.net/onjava/integrating-activemq-web-console.html it might help Cheers -- Dejan Bosanac www.scriptinginjava.net On Wed, Apr 9, 2008 at 1:09 PM, Dil <[EMAIL PROTECTED]> wrote: > > I have created a broker programatically in java code w

Re: Building 32-bit

On a 64bit OS install all the system libraries, or at least a large majority are going to built as 64 bit libraries. So the obvious question is do you even have 32 bit versions installed to link a 32 bit ActiveMQ CPP library against? You may want to look at the GNU Libtool documentation to see wh

Web console for broker with a name

I have created a broker programatically in java code with name fred. i.e, vm:fred producer consumer seem to be working fine, how do i configure webconsole to observe queues for this broker. here is some code of broker: public class ProdConnection { public static final ActiveMQConnectionFa

Re: Sending message from EJB3: poor performances after a while

See http://activemq.apache.org/how-do-i-use-jms-efficiently.html On 09/04/2008, James Strachan <[EMAIL PROTECTED]> wrote: > You are not using your J2EE providers JMS proxy to cache things; you > are using vanilla JMS. > > So try using the PooledConnectionFactory from ActiveMQ instead. > > > > O

Re: Sending message from EJB3: poor performances after a while

You are not using your J2EE providers JMS proxy to cache things; you are using vanilla JMS. So try using the PooledConnectionFactory from ActiveMQ instead. On 09/04/2008, paoletto <[EMAIL PROTECTED]> wrote: > > i wrote the following Stateless Session Bean, and ran in a j2ee application > on jb

Sending message from EJB3: poor performances after a while

i wrote the following Stateless Session Bean, and ran in a j2ee application on jbossAS. With the following implementation i have the problem that, if for example i put the send in a for to send 1000 messages (invocations) in a row, after about 200-250 the sender start to slow down and at about 30

Re: ActiveMQConnection:1653 - Async exception with no exception listener: java.net.SocketException: socket closed

Noted Dhurba! (High Five dude!!!) Thanks for the prompt reply. I ll be highlighting more issues as I 'll be strangling activemq until the end of this month for production readiness. :-D Regards Hatta Dhruba Bandopadhyay-2 wrote: > > Yeah I faced this problem as well. > > It was some time ba

Re: ActiveMQConnection:1653 - Async exception with no exception listener: java.net.SocketException: socket closed

Yeah I faced this problem as well. It was some time back but from what I can remember I believe the solution was to have two jars available. 1. spring-2.5.3.jar 2. spring-webmvc-2.5.3.jar The reason is that now, post 2.5, the DispatcherServlet is in the second jar. This would be preferable to m