send hangs using vm://

Hello, I have an embedded AMQ with 2 clients using vm:// and tcp:// respectively. The tcp://client mostly used to send lots of messages to the vm:// client. The vm://client periodically sends control massages to tcp:// client. The issue I am facing right now is the send operation from vm:// cl

Queue does not drain completely.

Just installed Active MQ 5.2. Using Stomp, inserted 5000 msgs and try to read the same with while ( my $msg = $stomp->read() ) { $stomp->commit(); print $msg.$/; } It leaves 2 messages in the queue, just reads 4998 and comes out. Any suggestions? -- View this message in context

Re: Unable to send message randomly : Unknown data type: -1

Ok, it was because of the schema I used my old schema and the msg was not in the same format. TEXT instead of IMAGE in 5.2.0 for sybase. Now it seems to work correctly -- View this message in context: http://www.nabble.com/Unable-to-send-message-randomly-%3A-Unknown-data-type%3A--1-tp24293718p

Unable to send message randomly : Unknown data type: -1

Hi, I currently try the version activemq 5.2.0 We use activemq 4.1.1 currently. However with a basic test with a producer and a consumer I always have an issue when I insert. I tried the same test in activemq4 and it works. The test is quite basic: MQProducer remoteProducer = new M

Re: Assistance with redirect using Apache

On Wed, Jul 1, 2009 at 8:32 AM, toby007aud wrote: > > Hi there > > This may not be the correct place to put this message - hopefully someone > can > point me to another group if need be. > > I have a site on a webserver that I want to have setup to redirect to > another > site. > > I have everythin

Assistance with redirect using Apache

Hi there This may not be the correct place to put this message - hopefully someone can point me to another group if need be. I have a site on a webserver that I want to have setup to redirect to another site. I have everything setup but not doing what I want: The current url is: www.cosmeti

Rejecting a failover transport connection on a different embedded Broker

We're using the failover transport for reconnection on network dropouts. We're also using a embedded broker. When the broker gets restarted, we want to force the failover transports to fail reconnection (whereas at the moment it reconnects happily) Is something like this possible? -- View this

ClassCastException having relation to expired messages

While testing ActiveMQ5.2.0, I have a question about expired message. Note that testing messages are Persistent and using a queue, set message expiration time to 10 seconds. configurations are same except destination policy(using a vm queue cursor) as below

Re: When jvm is downed, can the queues and topics(which are automaticlly created in the jvm) be deleted automaticlly

hi, it's depend on your broker.setPersistent(true); and producer.setDeliveryMode(DeliveryMode.PERSISTENT); setting. best, rosen jiang iamjackbob wrote: > > I use activeMQ in java files, and send and receive jms messages by Queue > and Topic, > but when i kill the jvm process, are the Queues a

When jvm is downed, can the queues and topics(which are auto created in the jvm) be deleted automaticlly

I use activeMQ in java files, and send and receive jms messages by Queue and Topic, but when i kill the jvm process, are the Queues and Topics still in JMS server? and is it needed to delete the Queues and Topics mannually? Thanks for all. -- View this message in context: http://www.nabble.com