Hudson build is back to stable: ActiveMQ #210

See

Hudson build is back to stable: ActiveMQ » ActiveMQ :: Core #210

See

[jira] Closed: (AMQNET-222) Commands.Message RedeliveryCounter not preserved when creating a new message

[ https://issues.apache.org/activemq/browse/AMQNET-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQNET-222. --- Resolution: Working as Designed This as well as the other properties in the Message Commands are

[jira] Created: (AMQNET-222) Commands.Message RedeliveryCounter not preserved when creating a new message

Commands.Message RedeliveryCounter not preserved when creating a new message Key: AMQNET-222 URL: https://issues.apache.org/activemq/browse/AMQNET-222 Project: ActiveMQ .Net

[jira] Updated: (AMQNET-220) Should retry 15 times in between sessions

[ https://issues.apache.org/activemq/browse/AMQNET-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQNET-220: Fix Version/s: 1.2.0 I've been able to produce some redelivery errors with a Unit test this mor

[jira] Assigned: (AMQNET-220) Should retry 15 times in between sessions

[ https://issues.apache.org/activemq/browse/AMQNET-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reassigned AMQNET-220: --- Assignee: Timothy Bish (was: Jim Gomes) > Should retry 15 times in between sessions > --

[jira] Closed: (AMQNET-217) AcknowledgementMode.Transactional Broken (Apache.NMS.NMSException: Invliad State: Not Currently in a Transaction)

[ https://issues.apache.org/activemq/browse/AMQNET-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQNET-217. --- Resolution: Working as Designed Closing as the Commit errors are expected. If there are errors i

Re: Apache NMS 1.2.0 RC1 now ready for download.

K. This makes sense. Thanks for the explanation/clarification Tim. Timothy Bish wrote: > > On Fri, 2009-12-11 at 10:09 -0800, magellings wrote: >> So when assigning a delegate (e.g. OnMessage) to the Listener event on >> the >> message consumer, the framework can't pull for another message af

[jira] Commented: (AMQNET-221) Should be able to max out retries on a message and then sent to dead letter queue

[ https://issues.apache.org/activemq/browse/AMQNET-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56401#action_56401 ] Timothy Bish commented on AMQNET-221: - The properties and bodies of received messages are

[jira] Updated: (AMQNET-220) Should retry 15 times in between sessions

[ https://issues.apache.org/activemq/browse/AMQNET-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Gellings updated AMQNET-220: - Attachment: NativeNMSConsumerAndProducer.zip I also noticed the RedeliveryCounter comes throu

[jira] Issue Comment Edited: (AMQNET-220) Should retry 15 times in between sessions

[ https://issues.apache.org/activemq/browse/AMQNET-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56400#action_56400 ] Mark Gellings edited comment on AMQNET-220 at 12/11/09 12:21 PM: --

[jira] Commented: (AMQNET-221) Should be able to max out retries on a message and then sent to dead letter queue

[ https://issues.apache.org/activemq/browse/AMQNET-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56399#action_56399 ] Mark Gellings commented on AMQNET-221: -- I've done some more troubleshooting and the issu

Re: Apache NMS 1.2.0 RC1 now ready for download.

On Fri, 2009-12-11 at 10:09 -0800, magellings wrote: > So when assigning a delegate (e.g. OnMessage) to the Listener event on the > message consumer, the framework can't pull for another message after the > scope of the delegate ends? Is this how the java implementation behaves? > This isn't a bi

Re: Apache NMS 1.2.0 RC1 now ready for download.

So when assigning a delegate (e.g. OnMessage) to the Listener event on the message consumer, the framework can't pull for another message after the scope of the delegate ends? Is this how the java implementation behaves? This isn't a big deal, we already were defaulting to doing pulls manually w

Re: Apache NMS 1.2.0 RC1 now ready for download.

On Fri, 2009-12-11 at 08:38 -0800, magellings wrote: > Hey Tim. Could you explain this a bit more? How come this isn't possible. > Seems like it should be. Thanks :-) > > Quad.NMS.Integration.Test.PrefetchZeroPullTest.Should_be_able_to_set_prefetch_to_zero_and_nms_activemq_enables_pull_mode >

Re: Apache NMS 1.2.0 RC1 now ready for download.

Hey Tim. Could you explain this a bit more? How come this isn't possible. Seems like it should be. Thanks :-) Quad.NMS.Integration.Test.PrefetchZeroPullTest.Should_be_able_to_set_prefetch_to_zero_and_nms_activemq_enables_pull_mode : Apache.NMS.NMSException : Cannot set Asynchronous Listener o

[jira] Commented: (AMQ-2480) Stomp Transport Dispatcher Fails on NPE

[ https://issues.apache.org/activemq/browse/AMQ-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56397#action_56397 ] Adam Walczak commented on AMQ-2480: --- Thats another issue with ActiveMQ I have that sometimes

[jira] Created: (AMQ-2529) Browsing Queues over network can cause a message delivered twice

Browsing Queues over network can cause a message delivered twice Key: AMQ-2529 URL: https://issues.apache.org/activemq/browse/AMQ-2529 Project: ActiveMQ Issue Type: Bug

[jira] Resolved: (AMQ-2518) QueueBrowser cause duplicate message delivery on network broker after restart

[ https://issues.apache.org/activemq/browse/AMQ-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-2518. Resolution: Duplicate Fix Version/s: 5.4.0 5.3.1 Fixed with https://iss

[jira] Commented: (AMQ-2480) Stomp Transport Dispatcher Fails on NPE

[ https://issues.apache.org/activemq/browse/AMQ-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56395#action_56395 ] Ben commented on AMQ-2480: -- This is a result of a null message being sent from a JMS producer. To sto

[jira] Commented: (AMQ-2148) ActiveMQ 5.2.0 time to live > 0 problem

[ https://issues.apache.org/activemq/browse/AMQ-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56394#action_56394 ] Adam Walczak commented on AMQ-2148: --- I've added a suggestion on how we could make ActiveMQ in

[jira] Commented: (AMQ-2480) Stomp Transport Dispatcher Fails on NPE

[ https://issues.apache.org/activemq/browse/AMQ-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56393#action_56393 ] Adam Walczak commented on AMQ-2480: --- I have a similar problem. I use the PHP Stomp librart fr

[jira] Commented: (AMQ-1605) 5.0.0: applet fails to initialize with default log4j.properties.

[ https://issues.apache.org/activemq/browse/AMQ-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56390#action_56390 ] Adam Walczak commented on AMQ-1605: --- '@ Manuel Garcia: Thats right. I'm using ActiveMQ 5.3 i

[jira] Commented: (AMQ-2473) Async error occurred: java.lang.NullPointerException

[ https://issues.apache.org/activemq/browse/AMQ-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56387#action_56387 ] Dejan Bosanac commented on AMQ-2473: We found in our testing that this might be related to

[jira] Commented: (AMQ-2501) Modify Apache Camel version of the pom

[ https://issues.apache.org/activemq/browse/AMQ-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56385#action_56385 ] Willem Jiang commented on AMQ-2501: --- @Vincent, Thanks for you confirmation. If you have time

[jira] Commented: (AMQ-2501) Modify Apache Camel version of the pom

[ https://issues.apache.org/activemq/browse/AMQ-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56384#action_56384 ] Vincent Girard-Reydet commented on AMQ-2501: I was in fact using a messed up versio