Re: 4.0.1 Release

+1. I'd like to get a 4.0.1 out ASAP as there's a few urgent bug fixes in there. On 6/14/06, Hiram Chirino [EMAIL PROTECTED] wrote: I'd like ActiveMQ to have follow the release early and release often mantra. So what do you guys think about getting a 4.0.1 release done by early next week? We

[jira] Updated: (AMQ-567) Time in queue statistics handy

[ https://issues.apache.org/activemq/browse/AMQ-567?page=all ] james strachan updated AMQ-567: --- Fix Version: 4.1 (was: 4.0) moved to 4.1 Time in queue statistics handy -- Key: AMQ-567

[jira] Updated: (AMQ-122) add support for priority message ordering

[ https://issues.apache.org/activemq/browse/AMQ-122?page=all ] james strachan updated AMQ-122: --- Fix Version: 4.2 (was: 3.2.5) add support for priority message ordering - Key:

[jira] Commented: (AMQ-745) in message selector does not match messages

[ https://issues.apache.org/activemq/browse/AMQ-745?page=comments#action_36392 ] Adrian Co commented on AMQ-745: --- Hi, I tried to reproduce the issue, but the in selector seems to work using the browse command. Im using the default out-of-the-box

[jira] Closed: (AMQ-745) in message selector does not match messages

[ https://issues.apache.org/activemq/browse/AMQ-745?page=all ] Jeff Martin closed AMQ-745: --- Resolution: Cannot Reproduce I've tried to reproduce this myself and I now think that there was something odd going on at the time. But it's not a problem with

[jira] Commented: (AMQ-608) Change logging level of some DemandForwardingBridge log messages.

[ https://issues.apache.org/activemq/browse/AMQ-608?page=comments#action_36400 ] Hiram Chirino commented on AMQ-608: --- 4.0 is officially released. 4.0.1 should be out in a few weeks. Change logging level of some DemandForwardingBridge log messages.

[jira] Commented: (AMQ-752) fix the uberjar to tidy up the notice/license files to make it absolutely clear whats going on

[ https://issues.apache.org/activemq/browse/AMQ-752?page=comments#action_36402 ] Hiram Chirino commented on AMQ-752: --- I updated the project name to apache-incubator-activemq so that distributions include the apache in it. Fixing the issues with the

[jira] Resolved: (AMQ-752) fix the uberjar to tidy up the notice/license files to make it absolutely clear whats going on

[ https://issues.apache.org/activemq/browse/AMQ-752?page=all ] Hiram Chirino resolved AMQ-752: --- Resolution: Fixed Applied changes to 4.1 and partially to 4.0... I think changing the module name on a big fix release would be in bad form. fix the

[jira] Resolved: (AMQ-749) ConnectionDotFileInterceptor not thread safe.

[ https://issues.apache.org/activemq/browse/AMQ-749?page=all ] Hiram Chirino resolved AMQ-749: --- Resolution: Fixed Assign To: Hiram Chirino Added synchronization to make thread safe. ConnectionDotFileInterceptor not thread safe.

[jira] Commented: (AMQ-725) Messages Sent by JMS that contain header properties cause error when STOMP client registers a Subscriber

[ https://issues.apache.org/activemq/browse/AMQ-725?page=comments#action_36405 ] Hiram Chirino commented on AMQ-725: --- Added test to the StompTest that looks like : public void testSubscribeWithMessageSentWithProperties() throws Exception {

Re: 4.0.1 Release

Hiram Chirino wrote: I'd like ActiveMQ to have follow the release early and release often mantra. So what do you guys think about getting a 4.0.1 release done by early next week? We have already done quite a few bug fixes in the 4.0 branch and I don't think we should hold those back any longer

Re: Graduation

Hiram Chirino wrote: Hi Folks, especially you ActiveMQ Mentors out there... I feel that ActiveMQ is ready if incubator graduation. For the looks of the Status report and the health of our community I think we are overdue! Mentors, do you think we are ready to petition the incubator for

Re: Graduation

I think so. There are lots of TLPs that do not have multiple subprojects like geronimo or ws have (log4j, xmlbeans, ant ..). So, i' m +1 for ActiveMQ to graduate as a TLP. Cheers, Guillaume Nodet Alan D. Cabrera wrote: Hiram Chirino wrote: Hi Folks, especially you ActiveMQ Mentors out

[jira] Commented: (AMQ-696) Client: XXX already connected exception when connection started after consumers added

[ https://issues.apache.org/activemq/browse/AMQ-696?page=comments#action_36414 ] Sanjiv Jivan commented on AMQ-696: -- oops, looks like I spoke too soon. With Active MQ 4.0 RC3, I used to get this exception as soon as the brokers were started. However with