Re: configuring redelivery with NMS

On Wed, 2009-01-28 at 14:13 -0800, mkeenan wrote: > > The NMS client does not implement the RedeliveryPolicy features > > discussed in that documentation, that applies to the Java code. > > Tim, > > Thanks for that information. Does that imply there is no way to specify > redelivery policy (an

Using the NIO transport causes issues

Anyone know why I would be seeing the following exception when using the NIO transport connector. I do not see this with TCP. [java] javax.jms.JMSException: Wire format negotiation timeout: peer did not send his wire format. [java] at org.apache.activemq.util.JMSExceptionSupport.cre

Re: configuring redelivery with NMS

> The NMS client does not implement the RedeliveryPolicy features > discussed in that documentation, that applies to the Java code. Tim, Thanks for that information. Does that imply there is no way to specify redelivery policy (anywhere) when using NMS? I am under the impression that it is n

Re: configuring redelivery with NMS

On Wed, 2009-01-28 at 12:58 -0800, mkeenan wrote: > I have read all of the relevant messages in this mailing list (and JIRA > entries) and I am still confused about configuring the redelivery policy. > > I am using NMS trunk and ActiveMQ 5.2 > > Where can I set the redelivery policy properties?

Re: Transacted Messages Not Committed

Just FYI for any forum users, Gary has correctly identified the issue as being one with my code. I have an abstract class that the single threaded consumers subclass and which handles the creation of the connection and the session. In this class I had static variables for the connection and sess

configuring redelivery with NMS

I have read all of the relevant messages in this mailing list (and JIRA entries) and I am still confused about configuring the redelivery policy. I am using NMS trunk and ActiveMQ 5.2 Where can I set the redelivery policy properties? I tried to put a element in the XML file but the broker woul

Re: Transacted Messages Not Committed

Hi Gary, I've entered this in JIRA under Test Cases. The title is "Transacted Messages not Committed". Thanks, -Frank Gary Tully wrote: > > Hi Frank, > it is great to have a test case. Could you create a jira issue[1] for > this and attach your tests case with the ASF license grant. In tha

Re: Update Broker Bridging while running?

2009/1/28 project2501 : > > Hi, > Is there a way to inform ActiveMQ to bridge to a new static tcp: broker > address after it is running? > I need to dynamically update the snf bridges, but won't have multicast > ability. > > Can I do this without modifying the config and restarting it? Maybe via A

Update Broker Bridging while running?

Hi, Is there a way to inform ActiveMQ to bridge to a new static tcp: broker address after it is running? I need to dynamically update the snf bridges, but won't have multicast ability. Can I do this without modifying the config and restarting it? Maybe via API or REST interface? thanks, Darre

Re: Webconsole and Tomcat

Hi, take a look at this article for starters http://activemq.apache.org/web-console.html#WebConsole-StartingtheWebConsoleinaseperateVM/inaWebContainer Regards -- Dejan Bosanac Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.

Re: ActiveMQ invalid response

This error indicates that we did not receive a WireFormat response from the Broker when we connected, which could mean that the broker is in a bad state and is unable to respond to us. This could be related to an out of memory situation. On Wed, 2009-01-28 at 06:40 -0800, Sebastien SOILEN wrote:

Re: ActiveMQ invalid response

it seems coherent, as we don't use producer flow control. We'll see if longer delay helps. There is another exception we get sometimes when trying to open connection with the broker.We can't really understand its meaning... and how it affects the connection. May it be caused by a possible lack of

Re: ActiveMQ invalid response

Things like this can also happen if you disable producer flow control on the client or the Broker is running out of memory. The default timeout that we used prior to adding the option to set it on the connection was 15 seconds, one second just seems a bit to brief to me to allow for other proces

Re: ActiveMQ invalid response

Thanks for your quick answer. We are trying with a 5s timeout, but we aren't under heavy load, the clients are all local and few (<50). -- View this message in context: http://www.nabble.com/ActiveMQ-invalid-response-tp21703873p21706383.html Sent from the ActiveMQ - User mailing list ar

Webconsole and Tomcat

Hi All Sorry if this is a really basic question, I'm wondering if anyone can help me out, I am trying to understand deploying the activemq web console to tomcat. A couple of questions to start of 1) When you deploy the web console to tomcat, is this supposed to link to broker instances that are

Re: AMQ Patching and Updating

Dejan, What is AMQ's standard in releasing patches, fixes and updates? If a patch or fix comes along, lets say hypothetically for version 5.2, does AMQ release version 5.3 with the updates and fixes? In other words how are AMQ releases maintained? How are users affected by it (do they upgrade or

Re: ActiveMQ invalid response

By setting the send timeout you are making the client more susceptible to failing because the broker is using flow control. Also a one second timeout is pretty short depending on how many client are using your broker and what the overall network load is, I'd recommend something a good deal higher,

Re: AMQ Patching and Updating

Hi Shaffin, the best way is get the source (http://activemq.apache.org/source.html) and provide your patch to the Jira ( https://issues.apache.org/activemq/browse/AMQ) along with the bug report. As for the Jetty, take a look at their site (http://www.mortbay.org/jetty/) for the source code and Ji

ActiveMQ invalid response

Hello, We are at the moment using ActiveMQ 5.2.0 with amq-cpp 2.2.3 through pyactivemq. The connection to the broker is done with these parameters: tcp://127.0.0.1:61616?connection.closeTimeout=1000&connection.sendTimeout=1000 After a few hours working, we get this exception in some of our proce

Re: Restricting queues

2009/1/28 dwout : > > Hi, > > Is it possible to keep producers from sending messages to a queue that > hasn't been defined in the activemq.xml config? Yes, just use security to restrict admin access (to be able to create new queues or topics) http://activemq.apache.org/security.html I was surpris

Restricting queues

Hi, Is it possible to keep producers from sending messages to a queue that hasn't been defined in the activemq.xml config? Thanks -- View this message in context: http://www.nabble.com/Restricting-queues-tp21702981p21702981.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.