Re: VM transport

On Fri, Aug 12, 2011 at 11:32 PM, Martin C. wrote: > Hi, > > On Fri, Aug 12, 2011 at 9:35 PM, Mohit Anchlia wrote: >> Thanks! Slightly different question. Is there any reason why one >> shouldn't use vm transport? > > Often it is sensible to have the broker as an external running > application, s

Re: VM transport

Hi, On Fri, Aug 12, 2011 at 9:35 PM, Mohit Anchlia wrote: > Thanks! Slightly different question. Is there any reason why one > shouldn't use vm transport? Often it is sensible to have the broker as an external running application, so it is available for procuders / consumers in other processes e

Re: VM transport

Thanks! Slightly different question. Is there any reason why one shouldn't use vm transport? On Fri, Aug 12, 2011 at 12:28 PM, Hervé BARRAULT wrote: > Hi, > you can activate the persistence by using the KahaDB persistence adapter ( > http://activemq.apache.org/kahadb.html). > > > 2011/8/12 Mohit

Re: VM transport

Hi, you can activate the persistence by using the KahaDB persistence adapter ( http://activemq.apache.org/kahadb.html). 2011/8/12 Mohit Anchlia > I am looking at using ActiveMQ. When using vm transport is data > persisted on the disk or is it always in memory? For eg: if I send > message and wa

Re: VM transport not using pass-by-reference

I traced through some code. It looks like ActiveMQSession.send() does honor copyMessageOnSend as noted. But this only explains why you see 2001, not 2002 messages. Message consumption on a topic happens in a two step process: 1) During dispatch, a MessageDispatch object is enqueued to consumer's

Re: VM transport not using pass-by-reference

Ryan Stewart wrote: > > I'm trying to use an embedded ActiveMQ instance for some lightweight > message handling... > *bump* again. Is there no answer to this? -- View this message in context: http://www.nabble.com/VM-transport-not-using-pass-by-reference-tp17442075s2354p17648713.html Sent f

Re: VM transport not using pass-by-reference

ttmdev wrote: > > FYI - copyMessageOnSend is being used within the ActiveMQSession.send() > method. > > ... > if (connection.isCopyMessageOnSend()) { >msg = (ActiveMQMessage)msg.copy(); > } > ... > > Joe > Cool. Thanks for pointing that out. -- View this message in context: http://www

Re: VM transport not using pass-by-reference

FYI - copyMessageOnSend is being used within the ActiveMQSession.send() method. ... if (connection.isCopyMessageOnSend()) { msg = (ActiveMQMessage)msg.copy(); } ... Joe Ryan Stewart wrote: > > I'm trying to use an embedded ActiveMQ instance for some lightweight > message handling. Accordi

Re: VM transport not using pass-by-reference

Hi Rob. I call connection.setCopyMessageOnSend(false) on the producer and consumer connection objects, and yes, the producer and consumers all use the vm transport. See my second post in this thread for sample code demonstrating the problem. (Actually, I just noticed that in that code I have "cop

Re: VM transport not using pass-by-reference

Hi Ryan, how are you setting copyMessageOnSend - and are the consumers using vm://transport too ? cheers, Rob http://open.iona.com/products/enterprise-activemq http://rajdavies.blogspot.com/ On 23 May 2008, at 23:32, Ryan Stewart wrote: I'm trying to use an embedded ActiveMQ instance

Re: VM transport not using pass-by-reference

Ryan Stewart wrote: > > I'm trying to use an embedded ActiveMQ instance for some lightweight > message handling... > *bump* Anyone? -- View this message in context: http://www.nabble.com/VM-transport-not-using-pass-by-reference-tp17442075s2354p17520875.html Sent from the ActiveMQ - User mai

Re: VM transport not using pass-by-reference

Ryan Stewart wrote: > > I'm trying to use an embedded ActiveMQ instance for some lightweight > message handling... > Here is a simple test case that exhibits the problem. Unfortunately you'll need some sort of profiler to see the actual problem. When I run this test, I get 2001 ActiveMQTextMes

Re: VM Transport problem when closing connections

No i am not using Spring and YES, I have also tried it without "failover". The result is the same. TOPPER_HARLEY wrote: > > Hi, > Are you using Spring? Can you use an > org.apache.activemq.xbean.BrokerFactoryBean? > > This will create and start the broker and just leave it there in the VM. >

Re: VM Transport problem when closing connections

Since you're connecting to an embedded broker, there is no need to use the 'failover' transport. Are you reusing Connection objects? zouzounos wrote: > > Hi, > I'm using activemq4.1.1 under tomcat 6. I am using the next entry in the > Context.xml: > type="org.apache.activemq.ActiveMQConnect

Re: VM Transport problem when closing connections

Hi, Are you using Spring? Can you use an org.apache.activemq.xbean.BrokerFactoryBean? This will create and start the broker and just leave it there in the VM. You can create a connection and then close it as you want but it will not shutdown the broker. (Broker stays alive until VM dies or until