Re: Redelivery policy in resource adapter

Sorry, works only *MaximumRedeliveries* parameter! -- View this message in context: http://activemq.2283324.n4.nabble.com/Redelivery-policy-in-resource-adapter-tp4712787p4712797.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Redelivery policy in resource adapter

Hi all, i need some help! I use glassfish 3, and i have running external activemq. I deployed resource adapter( post ), create connection pool(XA! with name "activemq/connectionFactory") and i create JNDI name(jms/activem

Re: failover protocol not reconnecting to single boker

Ah, so the thread that come with failover protocol to reconnecting to the broker is non-daemon. So I need to come up with a logic to keep the JVM open. Got it! Thanks! -- View this message in context: http://activemq.2283324.n4.nabble.com/failover-protocol-not-reconnecting-to-single-boker-t

Re: failover protocol not reconnecting to single boker

On 06/08/2016 10:45 AM, pompanoSlayer wrote: >From what I read, I would only need to add failover:(tcp://localhost:61616) as the connection url for the broker and activeMQ does all the reconnecting for me. However I can't seem to get this right. The program waits for the broker to go online and i

failover protocol not reconnecting to single boker

>From what I read, I would only need to add failover:(tcp://localhost:61616) as the connection url for the broker and activeMQ does all the reconnecting for me. However I can't seem to get this right. The program waits for the broker to go online and is able to read messages out of the queue when t

Re: nio buffer memory problem

Yes, the buffer was changed to a direct byte buffer for performance reasons. This was done in https://issues.apache.org/jira/browse/AMQ-6184 I think the best thing you can do for now is to keep increasing the size and see if it stabilizes. You mentioned that you could see it using 10g under vers

Re: Problems with UTF-8 encoding.

Hi Raul, Mayank is not the only one with the problem. For example I use JMS native client to send a message and then consume it via the REST API. I post object messages like so: /ObjectMessage message = session.createObjectMessage(new String(mystring.getBytes("UTF-8")));/ /producer.send(messag