Re: [VOTE] Release Apache.NMS.ActiveMQ 1.2.0 #3
Got your changes. They matched mine. - Jim -Original Message- From: Timothy Bish tabish...@gmail.com Date: Tue, 02 Feb 2010 17:28:39 To: dev@activemq.apache.org Subject: Re: [VOTE] Release Apache.NMS.ActiveMQ 1.2.0 #3 On Tue, 2010-02-02 at 14:20 -0800, Jim Gomes wrote: I searched the code for other areas where Thread.ResetAbort() was called (three locations found), and I have made some changes on my local machine. I am reconfiguring my application to use these custom versions so I can test the changes. I'll report back after I have been able to verify the fix. I see that you reopened AMQNET-218. I'll go add my comments there so we can track the issue. I made a few small changes in the code, make sure you grab the latest. On Tue, Feb 2, 2010 at 1:53 PM, Timothy Bish tabish...@gmail.com wrote: On Tue, 2010-02-02 at 13:41 -0800, Jim Gomes wrote: -1 The recent change made for AMQNET-218 seems to have introduced a problem. In general, I am uneasy about having this type of threading-related code change made right before a release. It would be better to let this kind of change cook for a while. Specifically, in CompositeTaskRunner.cs, line 160, the call to Thread.ResetAbort() in the exception handler is causing an exception, because this function should only be called in response to a ThreadAbortException. It is causing a ThreadStateException because no abort was requested. This catch handler should be re-written so that the Thread.ResetAbort() call is made in a specific exception handler for ThreadAbortException, rather than in the general exception handler. Ok, then lets consider the vote canceled and until such time as someone can come up with a solution that makes everyone happy we will put 1.2.0 on hold. Regards Tim.
Re: [VOTE] Release Apache.NMS.ActiveMQ 1.2.0 #4
+1 On Mon, Feb 8, 2010 at 7:07 AM, Timothy Bish tabish...@gmail.com wrote: The issue found during the last voting cycle have all been resolved so its time to try another vote. Now that we've fixed the issue the Voting is open once again on the Apache.NMS.ActiveMQ 1.2.0 release. This release is based on the Apache.NMS API v1.2.0 and runs on .NET frameworks 2.0+ and Mono 2.0+ Changes in this version include * Support for ConnectionMeteData in the Connection API. * Supports the new Individual Acknowledge Mode. * New IStreamMessage support * New IRedeliveryPolicy interface and PrefecthPolicy support. * Expanded IByteMessage interface to read/write primitive types. * Message's adhere to the JMS Read only and Write only rules. * Many new Unit Tests added to the Test Suite. * Support for Message Body Compression. * Connection Inactivity Monitor. * Optional Asynchronous Reconnects in the Failover Transport. * Optional Timeouts for Dispose and Close of Sessions. * Many more bugfixes and improvements as well. The new binary and source bundles for the release candidate can be found here: http://people.apache.org/~tabish/nms.activemq-1.2.0/http://people.apache.org/%7Etabish/nms.activemq-1.2.0/ The Wiki Page for this release is here: http://activemq.apache.org/nms/activemq-net-120-release.html The vote will remain open for 72 hours. Please cast your votes: [ ] +1 Release the source as Apache.NMS.ActiveMQ 1.2.0 [ ] -1 Veto the release (provide specific comments) Here's my +1 Regards, Tim
Re: [VOTE] Apache ActiveMQ 5.3.1 RC1
+1 On Thu, Mar 18, 2010 at 8:04 AM, Dejan Bosanac de...@nighttale.net wrote: Hi, I've just cut a first release candidate for 5.3.1 Could you review the release artifacts and vote? The list of resolved issues is here https://issues.apache.org/activemq/secure/IssueNavigator.jspa?reset=truepid=10520fixfor=12183status=5sorter/field=issuekeysorter/order=DESC You can get binary distributions here: https://repository.apache.org/content/repositories/orgapacheactivemq-004/org/apache/activemq/apache-activemq/5.3.1/ Source archives are here: https://repository.apache.org/content/repositories/orgapacheactivemq-004/org/apache/activemq/activemq-parent/5.3.1/ Maven2 repository is at: https://repository.apache.org/content/repositories/orgapacheactivemq-004/ Source SVN tag: http://svn.apache.org/viewvc/activemq/tags/activemq-5.3.1 The maven site and release notes will be done after the vote. Please vote to approve this release [ ] +1 Release the binary as Apache ActiveMQ 5.3.1 [ ] -1 Veto the release (provide specific comments) Here's my +1 Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net
Re: [VOTE] Apache ActiveMQ 5.3.2
+1 - Jim -Original Message- From: David Jencks david_jen...@yahoo.com Date: Mon, 26 Apr 2010 16:04:39 To: dev@activemq.apache.org Cc: Geronimo Dev List \(JIRA\)d...@geronimo.apache.org Subject: [VOTE] Apache ActiveMQ 5.3.2 Hi, I've staged a release candidate for ActiveMQ 5.3.2. The main driver for this is to get the osgi version range fixes into a release usable by the upcoming geronimo 3.0 milestone. The changes since the recent 5.3.1: merging 881433 - jaxb plugin problem changing activemq.version to match project version AMQ-2501 Modify version range for camel imports AMQ-2637 port osgi version range fixes from trunk AMQ-2700 - code disclosure vunl AMQ-2675 - web console topic form The staging repo is here: https://repository.apache.org/content/repositories/orgapacheactivemq-022/ The svn tag is here: https://svn.apache.org/repos/asf/activemq/tags/activemq-parent-5.3.2 This seems to be a different name format than the other tags. If people want me to redo the release to fix this I will probably want to update the build a little more such as using apache 7 parent pom and making the release plugin defaults work. Please vote +1 Promote staging repo as amq 5.3.2 -1 Drop staging repo and tag, try again (please provide specific comments) Many thanks david jencks
Re: [VOTE] Release Apache.NMS.ActiveMQ 1.3.0
+1 On Mon, May 17, 2010 at 2:50 PM, Timothy Bish tabish...@gmail.com wrote: Hello This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.3.0. This version provides some much requested new feature like SSL support and support for the QueueBrowser. Changes in this version include: * Fully implemented QueueBrowser functionality. * Ability to specify the socket binding on the URI * SSL Transport to provide secure connections. * Other bug fixes for issues found since v1.2.0 The binaries and source bundles for the Release Candidate can be found here: http://people.apache.org/~tabish/nms-1.3.0-RC1/ The Wiki Page for this release is here: http://activemq.apache.org/nms/activemq-net-130-release.html Please cast your votes (the vote will be open for 72 hrs): [ ] +1 Release the source as Apache NMS.ActiveMQ 1.3.0 [ ] -1 Veto the release (provide specific comments) Here's my +1 Regards, Tim
Re: [VOTE] Release Apache.NMS.Stomp 1.3.0
+1 On Mon, May 24, 2010 at 3:23 PM, Timothy Bish tabish...@gmail.com wrote: Hello This is a call for a vote on the release of Apache.NMS.Stomp v1.3.0. This version provides some much requested new feature like SSL support and several bug fixes. Changes in this version include: * SSL Transport to provide secure connections. * Many other bug fixes for issues found since v1.2.0 The binaries and source bundles for the Release Candidate can be found here: http://people.apache.org/~tabish/nms-1.3.0-RC1/ The Wiki Page for this release is here: http://activemq.apache.org/nms/activemq-net-130-release.html Please cast your votes (the vote will be open for 72 hrs): [ ] +1 Release the source as Apache NMS.Stomp 1.3.0 [ ] -1 Veto the release (provide specific comments) Here's my +1 Regards, Tim
Re: [VOTE] Apache ActiveMQ 5.4.0
+1 On Tue, Aug 10, 2010 at 12:37 PM, Hadrian Zbarcea hzbar...@gmail.comwrote: A new release activemq-5.4.0 is out with approximately 281 issues resolved. Please find the staging repo here: https://repository.apache.org/content/repositories/orgapacheactivemq-092/ The binary distribution is here: https://repository.apache.org/content/repositories/orgapacheactivemq-092/org/apache/activemq/activemq-all/5.4.0/ The source distribution is here: https://repository.apache.org/content/repositories/orgapacheactivemq-092/org/apache/activemq/activemq-parent/5.4.0/ The repository tag is here: https://svn.apache.org/repos/asf/activemq/tags/activemq-5.4.0/ The list of resolved issues is here: https://issues.apache.org/activemq/browse/AMQ/fixforversion/12110 Please review and vote to approve this release binary. Your vote counts! [ ] +1 Release the binary as Apache ActiveMQ 5.4.0 [ ] -1 Veto the release (provide specific comments) Vote is open for 72 hours. Here's my +1 Hadrian
Re: [VOTE] Apache ActiveMQ 5.4.0
Changing my vote to -1. I have found what I believe to be a show-stopper issue. It would be good if someone else could confirm this. I can consistently reproduce it on my machine using sources that I have built myself from the 5.4.0 tag. *Problem:* If ActiveMQ in installed into a folder whose complete path has a space in it, then all of the web apps will fail to start. *Scenario:* Install ActiveMQ into a folder named *C:\MyTest\ActiveMQ * (no spaces), and everything works fine. Shutdown ActiveMQ, and rename* C:\MyTest* to *C:\My Test *(add a space between the two words), and then re-launch the broker. A series of java.net.URISyntaxException errors will be thrown complaining about an Illegal character in path at index xx. It appears when webapps/admin, webapps/camel, webapps/demo, and webapps/fileserver and launching. The broker then reports that it has started and appears to be running. *Environment:* Windows Server 2003 R2 (32-bit) Java JRE 1.6.0_21 I consider this a severe problem, as it is common to install applications under the C:\Program Files folder in windows, which has a space in the name. Would someone else try to reproduce this problem? On Tue, Aug 10, 2010 at 4:22 PM, Jim Gomes e.se...@gmail.com wrote: +1 On Tue, Aug 10, 2010 at 12:37 PM, Hadrian Zbarcea hzbar...@gmail.comwrote: A new release activemq-5.4.0 is out with approximately 281 issues resolved. Please find the staging repo here: https://repository.apache.org/content/repositories/orgapacheactivemq-092/ The binary distribution is here: https://repository.apache.org/content/repositories/orgapacheactivemq-092/org/apache/activemq/activemq-all/5.4.0/ The source distribution is here: https://repository.apache.org/content/repositories/orgapacheactivemq-092/org/apache/activemq/activemq-parent/5.4.0/ The repository tag is here: https://svn.apache.org/repos/asf/activemq/tags/activemq-5.4.0/ The list of resolved issues is here: https://issues.apache.org/activemq/browse/AMQ/fixforversion/12110 Please review and vote to approve this release binary. Your vote counts! [ ] +1 Release the binary as Apache ActiveMQ 5.4.0 [ ] -1 Veto the release (provide specific comments) Vote is open for 72 hours. Here's my +1 Hadrian
Re: [VOTE] Apache ActiveMQ 5.4.0
+1 On Fri, Aug 13, 2010 at 6:17 PM, Hadrian Zbarcea hzbar...@gmail.com wrote: A new release activemq-5.4.0 is out with approximately 283 issues resolved. Please find the staging repo here: https://repository.apache.org/content/repositories/orgapacheactivemq-104/ The binary distribution is here: https://repository.apache.org/content/repositories/orgapacheactivemq-104/org/apache/activemq/activemq-all/5.4.0/ The source distribution is here: https://repository.apache.org/content/repositories/orgapacheactivemq-104/org/apache/activemq/activemq-parent/5.4.0/ The repository tag is here: https://svn.apache.org/repos/asf/activemq/tags/activemq-5.4.0/ The list of resolved issues is here: https://issues.apache.org/activemq/browse/AMQ/fixforversion/12110 Please review and vote to approve this release binary. Your vote counts! [ ] +1 Release the binary as Apache ActiveMQ 5.4.0 [ ] -1 Veto the release (provide specific comments) Vote is open for 72 hours. Here's my +1 Hadrian
Re: [VOTE] Release Apache.NMS API v1.4.0
+1 - Jim -Original Message- From: Timothy Bish tabish...@gmail.com Date: Tue, 07 Sep 2010 13:53:48 To: ActiveMQ-Developersdev@activemq.apache.org Reply-To: dev@activemq.apache.org Subject: [VOTE] Release Apache.NMS API v1.4.0 Hello This is a call for a vote on the release of the Apache.NMS API v1.4.0. This package contains the API for the various Apache.NMS clients along with utility classes and unit test cases against the abstract NMS API. This version of the API will be the basis for the next set of NMS client releases including Apache.NMS.ActiveMQ and Apache.NMS.Stomp. Changes in this version include: * Updates to the IMapMessage API * Addition of an API to register Message Transformers on both IMessageProducer's and IMessageConsumers * Improvements to the NMS URI parsing code. * Additional test cases added for better coverage. * Other minor bugfixes to the NMS support classes. The binaries and source bundles for the Release Candidate can be found here: http://people.apache.org/~tabish/nms-1.4.0 The Wiki Page for this release is here: http://activemq.apache.org/nms/activemq-net-140-release.html Please cast your votes (the vote will be open for 72 hrs): [ ] +1 Release the source as Apache NMS API 1.4.0 [ ] -1 Veto the release (provide specific comments) Here's my +1 Regards, -- Tim Bish Open Source Integration: http://fusesource.com ActiveMQ in Action: http://www.manning.com/snyder/ Follow me on Twitter: http://twitter.com/tabish121 My Blog: http://timbish.blogspot.com/
Re: NMS The world of Silverlight
I have not tried this, but the compiler seems reasonable. My understanding is that the Silverlight runtime is not the same as the CLR 2.0. You would need to need to compile them to target the Silverlight target runtime. Let me know what you are able to come up with, and I can possibly look into adding it as a compile option. Or if you can modify the NAnt build scripts and submit a patch, that would be great. -Jim On Tue, Jul 8, 2008 at 12:46 PM, Richard Gillingham [EMAIL PROTECTED] wrote: Hello all I've been thinking about Silverlight and decided tonight to try my NMS client assemblies in a Silverlight 2 Beta project. The IDE complains that the assemblies were not built against the Silverlight runtime. Has anyone tried this before?? If not, I'll go ahead and report back :) kind regards Richard -- View this message in context: http://www.nabble.com/NMS-The-world-of-Silverlight-tp18347501p18347501.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: NMS The world of Silverlight
I have removed the references to System.Data, so that should help out a bit. I'll take a look at the StringDictionary next. From what you mention, we may want to look for a temporary work-around until Microsoft ships a newer Silverlight since they are planning to support StringDictionary eventually. On 7/12/08, Richard Gillingham [EMAIL PROTECTED] wrote: Hello Jim The Silverlight runtime is a subset of CLR - it's only 4.5Mb downloadable. I've looked at the NMS assembly so far. References to system.data (which aren't used anyway and are only there because VS adds them by default) need to be removed because that is not supported in SL. After that point there are just two functions that won't compile in the Utils.URI because they uses System.Collection.Specialized.StringDictionary which again is not in the SL runtime. According to some doc StringDictionary is meant to be there in Beta 2 but it's not :) I might roll my own StringDictionary to close this off. Then I'm hoping ActiveMQ.dll will be as painless - which would be great. kind regards Richard semog wrote: I have not tried this, but the compiler seems reasonable. My understanding is that the Silverlight runtime is not the same as the CLR 2.0. You would need to need to compile them to target the Silverlight target runtime. Let me know what you are able to come up with, and I can possibly look into adding it as a compile option. Or if you can modify the NAnt build scripts and submit a patch, that would be great. -Jim On Tue, Jul 8, 2008 at 12:46 PM, Richard Gillingham [EMAIL PROTECTED] wrote: Hello all I've been thinking about Silverlight and decided tonight to try my NMS client assemblies in a Silverlight 2 Beta project. The IDE complains that the assemblies were not built against the Silverlight runtime. Has anyone tried this before?? If not, I'll go ahead and report back :) kind regards Richard -- View this message in context: http://www.nabble.com/NMS-The-world-of-Silverlight-tp18347501p18347501.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/NMS-The-world-of-Silverlight-tp18347501p18420542.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: NMS API design question regarding AckMode
Hi Mark,
I have been playing around with this for a while, and here are my findings
for further discussion.
It is possible to change the IConnection interface to use the following
generic types:
ISession CreateSession(System.Enum acknowledgementMode);
System.Enum AcknowledgementMode { get; set; }
This would allow for passing in a generic enumeration. However, I think
that it will force more code to be written using explicit casting in order
to deal with the AcknowledgementMode property in the most general cases.
Since using provider specific acknowledgment modes is the outlyer case, I
think using casting to show specific intent to deviate from standard modes
is preferred. The C# enum type system is robust enough to support the
following using the existing interface definition without reverting to
generic System.Enum:
interface IConnection// SNIPPET
{
ISession CreateSession(AcknowledgementMode acknowledgementMode);
AcknowledgementMode AcknowledgementMode { get; set; }
}
enum MyAckModes
{
IgnoreDups,
Transactional,
Explicit
}
IConnection connection = GetConnection();
// Set the default ack mode
connection.AcknowledgementMode = (AcknowledgementMode)
MyAckModes.IgnoreDups;
// Set session-specific ack mode
ISession session = connection.CreateSession((AcknowledgementMode)
MyAckModes.Explicit);
As can be seen from this snippet of code, the existing code base allows the
use of provider specific enumerations while providing type-safety and
non-casting for the general case. When a user of NMS wants to have
low-level access to a provider's unique acknowledgment modes, then they can
do so and the C# enum system will carry their values through, even if that
acknowledgment mode value is outside the range of the original
AcknowledgmentMode enumeration. I have created a sample C# app that
demonstrates basic casting of enumerations to show that provider specific
enumeration values can be carried inside the existing AcknowledgementMode
enumeration. Since these values only make sense to the individual
providers, they will be the ones who will cast when setting/getting the
AcknowledgementMode property.
using System;
public class EnumTest
{
enum MyEnum{ First, Second, Third }
enum ProviderEnum { Fourth, Fifth }
static void ShowEnum(System.Enum baseEnum)
{
Console.WriteLine(base = {0}, baseEnum);
ProviderEnum derived = (ProviderEnum) baseEnum;
Console.WriteLine(derived = {0}, derived);
}
static void Main()
{
ShowEnum(MyEnum.Second);
ShowEnum(MyEnum.Third);
}
}
I hope that this addresses the concerns about using provider specific
extensions to the acknowledgment mode enumeration. Let me know if I didn't
explain anything clearly. I am interested in your comments on this
proposal.
- Jim
On Mon, Jun 9, 2008 at 12:27 PM, Mark Pollack [EMAIL PROTECTED]
wrote:
Hi,
Just a ping to see if we can get closure on an approach...
Mark
-Original Message-
From: Mark Pollack [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 29, 2008 10:09 AM
To: 'dev@activemq.apache.org'
Subject: RE: NMS API design question regarding AckMode
Hi,
My suggestion is to have the base enumeration class, System.Enum, be used.
I suspect that all .NET messaging providers have used enums for ack modes
and if they didn't, the NMS implementation for that provider could supply
one.
In the case of the EMS binding, this would read
connection.CreateSession(SessionMode.NoAcknowledge)
This seems more natural than using a literal string. All the general
arguments of enum vs. string apply here.
I used this approach with System.Data.DbType, the base enum for data types
in ADO.NET. All ADO.NET providers have their own custom enum (for
'advanced' data types like xml, arrays etc.) This has seemed to work out
well, at least no complaints.
Cheers,
Mark
-Original Message-
From: Rob Davies [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 29, 2008 2:32 AM
To: dev@activemq.apache.org
Subject: Re: NMS API design question regarding AckMode
+1 on Strings
On 29 May 2008, at 05:47, Jim Gomes wrote:
Hi Mark,
I like the idea of having providers extend the session modes to what
makes
sense for them. For instance, MSMQ may ignore transactional, but
have some
additional acknowledgment mode. However, what do you propose as a
solution
such that provider's individual extensions to the acknowledgment
mode do not
pollute the global API space? I like your suggestion of having a
loose
and flexible API, and I would think that an acknowledgement mode as a
string, versus an enumeration, would be the loosest. But that may
not be
the best way to go.
Changing to a string might work. The current enumeration could be
changed
to readonly strings. This way providers would be free to support
custom
Re: NMS does not support BLOB messages
Hi Mark, I think this message is referring to BLOB messages which are out-of-band payload messages. The normal object messages are in-band, which means their payload actually moves through the broker. See this link for more info: http://activemq.apache.org/blob-messages.html I also responded to Marko's cross-posting of this message on the User's mailing list with another potential stop-gap solution, but I haven't seen a reply as to whether that might work for him. - Jim On 8/14/08, Mark Pollack [EMAIL PROTECTED] wrote: Hi, ISession has the methods CreateObjectMessage, for serializing objects, and CreateBytesMessage for byte[]. That would seem to meet your needs. Cheers, Mark -Original Message- From: Marko111 [mailto:[EMAIL PROTECTED] Sent: Thursday, August 14, 2008 9:21 AM To: dev@activemq.apache.org Subject: NMS does not support BLOB messages Currently NMS does not support BLOB messages. Is there a plan to change this. -- View this message in context: http://www.nabble.com/NMS-does-not-support-BLOB-messages-tp18981388p18981388 .html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: NMS ssl support
Hi Janek, There hasn't been any plan for implementing SSL into NMS, since there hasn't been a JIRA logged so we could schedule it into the releases. Right now, we are working on shipping 1.0 and would not want to make such a big change that could destabilize the code. As you mention, it would be good to come up with a clean solution that integrates well into the existing code. If you like, please enter a JIRA and we can schedule it for a future release of NMS. Also, if you have some potential code that you could share, that would be very welcome. Thanks, Jim On Tue, Aug 19, 2008 at 2:31 AM, benetnash [EMAIL PROTECTED] wrote: Hi! I see, that there is no ssl support in NMS. Is there any plan for implementing that in near future? I made small library vith Mono.Security providing SslConnectionFactory using copy-paste from ConnectionFactory, TcpTransportFactory and TcpTransport but it's very messy solution (any change in one of above classes must be also done in my classes). It would be easier to implement that if some developer change in Apache.NMS.AcitveMQ following methods to virtual: ConnectionFactory.CreateConnection(), TcpTransport.Start() and TcpTransportFactory.CreateTransport(). With that my ssl transport may inherit from tcp transport classes and only override that methods. Is there any possibility to do so in several days? Best regards and sorry for my poor english. Janek -- View this message in context: http://www.nabble.com/NMS-ssl-support-tp19047073p19047073.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: aqctivemq-dotnet releases
I am in the process of creating a 1.0 release right now. On 8/22/08, kingpin_rcs [EMAIL PROTECTED] wrote: Looking at the activemq-dotnet source repository I see no tags or branches. I want to use a stable release but it appears that there is not one yet. What exactly is the status of this project? Thanks -- View this message in context: http://www.nabble.com/aqctivemq-dotnet-releases-tp19115875p19115875.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: Broken Build - ActiveMQ 5.2 SNAPSHOT
Yay! I can finally build again as of today. On 8/26/08, semog [EMAIL PROTECTED] wrote: The trunk ActiveMQ 5.2 SNAPSHOT build is not working due to recent changes. When I compile, I get the following warning: [INFO] [INFO] Building ActiveMQ :: Core [INFO]task-segment: [install] [INFO] [WARNING] While downloading javacc:javacc:3.2 This artifact has been relocated to net.java.dev.javacc:javacc:3.2. And then I get the following errors: [INFO] Compiling 492 source files to C:\Projects\GVDev\3rdParty\ActiveMQ\trunk\activemq-core\target\classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure C:\Projects\GVDev\3rdParty\ActiveMQ\trunk\activemq-core\src\main\java\org\apache\activemq\broker\jmx\CompositeDataHelper.java:[45,65] incompatible types found : java.util.Collectioncapture#872 of ? required: java.util.Collectionjavax.management.openmbean.CompositeData -- View this message in context: http://www.nabble.com/Broken-Build---ActiveMQ-5.2-SNAPSHOT-tp19168510p19168510.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: ActiveMQ release process - two queries
Hi Gary, I don't know anything about the ActiveMQ release process, but I will chime-in on the version numbering. I think the three-digit numbering should be kept. It makes things very consistent. I am not a fan of long strings of version numbers, but I think the three digits are the minimum necessary to convey all of the import information about the build. If we know that there might be minor rev numbers (i.e., the third digit), then that number should always be present for easier sorting/comparison either by a human or a computer. That's my $0.02.0 cents. :) - Jim On Tue, Sep 9, 2008 at 2:32 AM, Gary Tully [EMAIL PROTECTED] wrote: Hi, In cutting a first release candidate of AMQ 5.2 two small issues arise that mean a re-cut. 1) I accepted the maven release default version numbers, and based of the parent pom the svn tag is activemq-parent-5.2. I guess I should have inserted a different value at the prompt during release to make it activemq-5.2 , but is a little error prone. I am wondering if the parent pom changed its name to activemq, how damaging would that be? From a release perspective, it means that we just hit return (accept defaults) during the release execution. Maven activemq dependencies are typically on activemq-core. Would anyone notice a change to the name of the parent pom? 2) the number of digits in the version number, why the extra 0? I see 4.1, then 5.1.0, but in the poms, we have 5.2. Has this been discussed and what is the outcome? I like the idea of keeping the version digits at a minimum. 5.1, 5.1.0, 5.1.1 etc. but not 5.1.0. FWIW, the current candidate is at: http://people.apache.org/~gtully/staging-repos/activemq-5.2/org/apache/activemq/apache-activemq/5.2 Thanks, Gary.
Re: Apache.NMS.ActiveMQ trunk is broken
Hi Daniel, Thanks for investigating this. The trunk definitely seems to be in a bad state. Now that I am back from vacation, I will be addressing these problems directly. - Jim On Wed, Nov 5, 2008 at 2:56 PM, Daniel Ellis [EMAIL PROTECTED] wrote: I have noticed the latest in trunk is hanging when creating a session. I have worked my way back through the revisions and it seems it hasn't been passing the unit tests since revision 707506. These are my results of the unit tests with ActiveMQ version 5.1.0:- 707506 - OK 707747 - Fails OpenWire/BooleanStreamTest 707803 - Fails most tests - KeyNotFoundException 708307 - Fails OpenWire/BooleanStreamTest 708312 - Fails most tests - BrokerException Unknown data type 708627 - (Didn't test) 708628 - (Didn't test) 708735 - (Didn't test) 708738 - Wire format negotiation timeout 708739 - Hangs/Deadlock 708741 - (Didn't test) 709284 - (Didn't test) 709310 - (Didn't test) 709510 - (Didn't test) 709539/head - Hangs/Deadlock -- View this message in context: http://www.nabble.com/Apache.NMS.ActiveMQ-trunk-is-broken-tp20351840p20351840.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: Patch for NMS ConnectionFactory problem with ASP.NET
Yeah, I'm not able to access it either. I am getting a 410 error: file has been deleted. Adding it to a JIRA issue would be great. On Wed, Nov 19, 2008 at 7:24 AM, Hiram Chirino [EMAIL PROTECTED]wrote: Hi Dan, Looks like the URL to the patch in your emails is not loading up for me. Perhaps you should just attach it to a JIRA issue at: http://issues.apache.org/activemq/browse/AMQNET Regards, Hiram On Tue, Nov 18, 2008 at 11:30 AM, Daniel Ellis [EMAIL PROTECTED] wrote: Hello, Good to see the NMS trunk is back up to speed and passing the unit tests. This morning I had a problem getting the connection factory to work within ASP.NET and believe it may not be possible with the current implementation. Currently the function 'LookupConnectionFactoryInfo' obtains the path to the nmsprovider.config file by looking in the directory of the currently executing assembly. However ASP.NET does not run the assembly where the DLL is located. Instead the DLL is copied to a path deep within the ASP.NET temporary files folder. The attached patch now checks three folders:- * Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location); * AppDomain.CurrentDomain.BaseDirectory; * AppDomain.CurrentDomain.RelativeSearchPath; I have tested this and it now works with both a service and an asp.net webapp. I have done my best not to break the compact framework build, but have not managed to build that yet. Is this a suitable implementation? http://www.nabble.com/file/p20563084/NMSConnectionFactory-aspnet.patch NMSConnectionFactory-aspnet.patch Regards, Dan -- View this message in context: http://www.nabble.com/Patch-for-NMS-ConnectionFactory-problem-with-ASP.NET-tp20563084p20563084.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
Re: Patch for NMS ConnectionFactory problem with ASP.NET
Scratch that last message. I was able to retrieve the patch by going to the Nabble website. I couldn't link to it from the e-mail message. I'll add it in later today. - Jim On Wed, Nov 19, 2008 at 8:24 AM, Jim Gomes [EMAIL PROTECTED] wrote: Yeah, I'm not able to access it either. I am getting a 410 error: file has been deleted. Adding it to a JIRA issue would be great. On Wed, Nov 19, 2008 at 7:24 AM, Hiram Chirino [EMAIL PROTECTED]wrote: Hi Dan, Looks like the URL to the patch in your emails is not loading up for me. Perhaps you should just attach it to a JIRA issue at: http://issues.apache.org/activemq/browse/AMQNET Regards, Hiram On Tue, Nov 18, 2008 at 11:30 AM, Daniel Ellis [EMAIL PROTECTED] wrote: Hello, Good to see the NMS trunk is back up to speed and passing the unit tests. This morning I had a problem getting the connection factory to work within ASP.NET and believe it may not be possible with the current implementation. Currently the function 'LookupConnectionFactoryInfo' obtains the path to the nmsprovider.config file by looking in the directory of the currently executing assembly. However ASP.NET does not run the assembly where the DLL is located. Instead the DLL is copied to a path deep within the ASP.NET temporary files folder. The attached patch now checks three folders:- * Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location); * AppDomain.CurrentDomain.BaseDirectory; * AppDomain.CurrentDomain.RelativeSearchPath; I have tested this and it now works with both a service and an asp.net webapp. I have done my best not to break the compact framework build, but have not managed to build that yet. Is this a suitable implementation? http://www.nabble.com/file/p20563084/NMSConnectionFactory-aspnet.patch NMSConnectionFactory-aspnet.patch Regards, Dan -- View this message in context: http://www.nabble.com/Patch-for-NMS-ConnectionFactory-problem-with-ASP.NET-tp20563084p20563084.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
Re: Apache.NMS.ActiveMQ trunk is broken
By way of semi-official announcement, trunk is back to normal. There may still be bugs, but it should be usable. On 11/10/08, Jim Gomes [EMAIL PROTECTED] wrote: Hi Daniel, Thanks for investigating this. The trunk definitely seems to be in a bad state. Now that I am back from vacation, I will be addressing these problems directly. - Jim On Wed, Nov 5, 2008 at 2:56 PM, Daniel Ellis [EMAIL PROTECTED] wrote: I have noticed the latest in trunk is hanging when creating a session. I have worked my way back through the revisions and it seems it hasn't been passing the unit tests since revision 707506. These are my results of the unit tests with ActiveMQ version 5.1.0:- 707506 - OK 707747 - Fails OpenWire/BooleanStreamTest 707803 - Fails most tests - KeyNotFoundException 708307 - Fails OpenWire/BooleanStreamTest 708312 - Fails most tests - BrokerException Unknown data type 708627 - (Didn't test) 708628 - (Didn't test) 708735 - (Didn't test) 708738 - Wire format negotiation timeout 708739 - Hangs/Deadlock 708741 - (Didn't test) 709284 - (Didn't test) 709310 - (Didn't test) 709510 - (Didn't test) 709539/head - Hangs/Deadlock -- View this message in context: http://www.nabble.com/Apache.NMS.ActiveMQ-trunk-is-broken-tp20351840p20351840.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: NMS on the compact framework
Hi Matthew, I updated the wiki so that page you referenced will get generated the next tiime it runs. Until then, you just need to change down one more folder level into the 'trunk' folder before running nant. Be sure to build the Apache.NMS module first, and then build the Apache.NMS.ActiveMQ module. If you have VS2005 installed, nant will generate CF assemblies. -Jim On 12/12/08, Powers, Matthew mpow...@systems.textron.com wrote: Tim, I am still having problems. Maybe you can help. I checked out all the source like it says here: http://activemq.apache.org/nms/source.html so my directory structure looks like this... C:\activemq-dotnet\Apache.NMS C:\activemq-dotnet\Apache.NMS.ActiveMQ C:\activemq-dotnet\Apache.NMS.EMS C:\activemq-dotnet\Apache.NMS.MSMQ C:\activemq-dotnet\Apache.NMS.WCF Building with nant referenced here: http://activemq.apache.org/nms/building.html tells me to run nant from c:\activemq-dotnet\ but that does not work...I have my nant.bat file in c:\activemq-dotnet\ which references the directory of my nant install. Am I missing something? Sorry - kinda a newbie -Original Message- From: Timothy Bish [mailto:tabish...@gmail.com] Sent: 2008-12-12 10:58 AM To: dev@activemq.apache.org Subject: RE: NMS on the compact framework That's probably the better way to go unless you are dead set on using VS to build. Regards Tim. On Fri, 2008-12-12 at 10:38 -0500, Powers, Matthew wrote: Thanks I am guessing that I could just use nant to build the entire thing too and change the target framework instead of doing it through visual studio -- Tim Bish http://fusesource.com http://timbish.blogspot.com/
Re: Where can i download the latest verstion of Apache.NMS.ActiveMQ.dll
Hello, There isn't a final package yet, as NMS 1.1 has not been released yet. However, you should be able to get the latest compiled version from the deploy sub-directory out of Subversion. I am working towards a more standard release location that packages the assemblies together for ease of downloading and distribution. Best, Jim On Tue, Jan 20, 2009 at 4:59 PM, sbs1982 satyajit.sa...@sac.com wrote: I have the version 1.1.0.0 with me. Where can i get the latest version if there has been a release? -- View this message in context: http://www.nabble.com/Where-can-i-download-the-latest-verstion-of-Apache.NMS.ActiveMQ.dll-tp21575158p21575158.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: Is Apache.NMS.ISession thread safe?
There are currently a couple of JIRA issues related to threading issues. I have not verified these, nor have I run across them in my own usage patterns. However, they may be related to whatever issues you may be experiencing. Take at look at them and see if they might help you diagnose your issues: https://issues.apache.org/activemq/browse/AMQNET-136 https://issues.apache.org/activemq/browse/AMQNET-132 https://issues.apache.org/activemq/browse/AMQNET-113 Best, Jim On Wed, Jan 21, 2009 at 9:41 AM, sbs1982 satyajit.sa...@sac.com wrote: If one thread in my app is trying to create a temporary topic and I already have a few consumers(listening on other temp topics processesing incoming messages on their respective call back methods i.e listeners) open. Now trying to call the close method of one of these consumers causes my app to go into deadlock. is there some know issue of close method of consumers locking? I looked at the code in the MessageConsumer..the first statement is lock(this). Some articles are out there saying that locking on this is unsafe? -- View this message in context: http://www.nabble.com/Is-Apache.NMS.ISession-thread-safe--tp21588244p21588244.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: Discuss: AMQNET-93
Well, I think this issue needs to be resolved. The informal vote and preference is for List One, so I'll adjust the code to match that style. - Jim On Fri, Feb 27, 2009 at 2:53 PM, ybronsht ybron...@progress.com wrote: Jim, I understand your point about Oracle. First of all, we can tell that Oracle is also ignorant of the framework guidelines from their naming of OracleXMLSQLException. I've actually seen this come up in a more general case in Microsoft's own products: There's a ServiceDescription class (represents a WSDL document) in the System.Web.Services.Description in a .Net 2.0 assembly, and a System.ServiceModel.ServiceDescription class in a WCF (.Net 3.0) assembly. Having worked on a WCF product for the past year or so, I've seen them collide on many occasions. What is done (including in many Microsoft code samples) is just a namespace alias: using WSDL = System.Web.Services.Description; ... var wsdl = new WSDL.ServiceDescription(); The compiler will force the user to keep the naming unambiguous - that's not our job. And if the user wants to type those extra three letters for visual clarity, he can do that too - again, not our job. Let's let the user decide when those letters need to be there and when they can be done without. -- View this message in context: http://www.nabble.com/Discuss%3A-AMQNET-93-tp22255094p22256029.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: Performance comparison between OpenWire and Stomp
My rule of thumb is always use openwire unless forced to use stomp. Openwire is more compact than stomp. --Original Message-- From: Garfield071 To: ActiveMQ Dev ReplyTo: ActiveMQ Dev Subject: Performance comparison between OpenWire and Stomp Sent: Mar 5, 2009 9:37 AM Hi, I wondering if there's a rule of thumb to evalute impacts on bandwith of choosing OpenWire vs Stomp. This issue nay be a major trigger in my decision. Thank you. -- View this message in context: http://www.nabble.com/Performance-comparison-between-OpenWire-and-Stomp-tp22356562p22356562.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. - Jim
Re: NMS 1.1 Breaking API Change
There are 2 outstanding bugs logged against the 1.1 version as of this morning. Once those are resolved a release candidate will be cut. - Jim -Original Message- From: Bruce Snyder bruce.sny...@gmail.com Date: Thu, 28 May 2009 12:26:22 To: dev@activemq.apache.org Subject: Re: NMS 1.1 Breaking API Change On Fri, May 22, 2009 at 4:58 PM, semog e.se...@gmail.com wrote: This is a heads-up message for users of the NMS 1.1 library. Two fixes were made to the product that will break compilation of existing code. When you update to the latest version, you will need to update references to a couple of fields and parameters. On the positive side, these breaking changes are obvious and will generate compiler errors. They are not subtle changes that are hard to find in your code. Please see the following JIRA issues for more information: See https://issues.apache.org/activemq/browse/AMQNET-105 See https://issues.apache.org/activemq/browse/AMQNET-101 The basic change is that the NMSPersistent field is no longer a boolean value. It has been renamed to NMSDeliveryMode and the type is the new MsgDeliveryMode enumeration. The NMSPriority field has been changed from a simple byte type to the MsgPriority enumeration. The Send() function parameters now use these new enumeration types. Jim, any idea when the next release of NMS will take place? Bruce -- perl -e 'print unpack(u30,D0G)u8...@4vyy95R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' ActiveMQ in Action: http://bit.ly/2je6cQ Blog: http://bruceblog.org/ Twitter: http://twitter.com/brucesnyder
Re: ActiveMQ 6 Codename?
Sticking with the mythology theme: +1 Charon Charon was the ferryman and was the implicit flow control for entry into hell. - Jim -Original Message- From: Colin MacNaughton colin.macnaugh...@gmail.com Date: Thu, 11 Jun 2009 08:34:06 To: dev@activemq.apache.org Subject: RE: ActiveMQ 6 Codename? +1 apollo for me. -Original Message- From: Bruce Snyder [mailto:bruce.sny...@gmail.com] Sent: Thursday, June 11, 2009 7:28 AM To: dev@activemq.apache.org Subject: Re: ActiveMQ 6 Codename? On Thu, Jun 11, 2009 at 7:42 AM, Rob Daviesrajdav...@gmail.com wrote: puma gets my vote +1 for puma. Bruce -- perl -e 'print unpack(u30,D0G)u8...@4vyy95R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' ActiveMQ in Action: http://bit.ly/2je6cQ Blog: http://bruceblog.org/ Twitter: http://twitter.com/brucesnyder
NMS 1.1.0 RC1 Available
* ANNOUNCEMENT * The Apache NMS 1.1.0 Release Candidate 1 is now available at the following location: http://people.apache.org/~jgomes/nms_1.1.0 The following projects are included: Apache.NMS Apache.NMS.ActiveMQ Apache.NMS.EMS Apache.NMS.MSMQ Apache.NMS.WCF There are release binaries and debug binaries (with PDBs) provided. The binary ZIP files include pre-built assemblies for all of the platforms that are supported by each project (e.g., .NET 2.0, Mono, .NET 3.5, etc). Not all projects support all platforms. Please note that in order to use the Apache.NMS.EMS project files, you will need to provide your own copy of the TIBCO.EMS.dll, as this is a licensed 3rd Party application. Please report any issues or problems you have with these files. Best, Jim Gomes
Re: NMS 1.1.0 RC1 Available
Just to clarify, this isn't a call for a vote yet. Just merely an announcement for preview. A vote will be called shortly. On Mon, Jun 15, 2009 at 7:15 AM, Jim Gomes e.se...@gmail.com wrote: * ANNOUNCEMENT * The Apache NMS 1.1.0 Release Candidate 1 is now available at the following location: http://people.apache.org/~jgomes/nms_1.1.0http://people.apache.org/%7Ejgomes/nms_1.1.0 The following projects are included: Apache.NMS Apache.NMS.ActiveMQ Apache.NMS.EMS Apache.NMS.MSMQ Apache.NMS.WCF There are release binaries and debug binaries (with PDBs) provided. The binary ZIP files include pre-built assemblies for all of the platforms that are supported by each project (e.g., .NET 2.0, Mono, .NET 3.5, etc). Not all projects support all platforms. Please note that in order to use the Apache.NMS.EMS project files, you will need to provide your own copy of the TIBCO.EMS.dll, as this is a licensed 3rd Party application. Please report any issues or problems you have with these files. Best, Jim Gomes
Re: NMS 1.1.0 RC1 Available
Thanks for the great feedback. I have incorporated the following changes:
1. The package files are now down to two files: a bin and a src ZIP file
(along with the attending .asc files).
2. I added a modified version of the script proposed by Mark. Using the
strategy of embedding the framework version quickly over-ran the allowable
range for the revision number. I instead adopted the use of the number of
days since inception strategy. This will give a unique daily build number,
which should be sufficient.
I will place the new build files out tomorrow. It may be late in the day,
since I need my work build machine to generate the build, but I can't access
the remote server from work. I am having to split my efforts between two
locations, which is cumbersome. I hope to streamline this. I will send out
another announcement when it's done.
Please feel free to offer more comments and suggestions.
- Jim
On Mon, Jun 15, 2009 at 7:59 PM, Mark Pollack mark.poll...@springsource.com
wrote:
Hi,
Another suggestion, the RC1 as well as the dlls that I've used from svn all
have the identical assembly version, 1.1.0.0. Can the assembly revision be
unique for each build/release. This makes it hard to identify version
issue, both with what .NET framework is in use and what exact version is
being used, svn snapshot vs. RC1, vs. GA release.
There are several strategies here. Sometimes people coerce the svn version
number into the assembly - though there is less range available in the
assembly numbers.
I've used the following scheme in spring.net which you may find useful
Major.minor.patch - as you would normally, for example 1.1.1
And the assembly revision is calculated according to the scheme:
RRXXX where RR = framework number (1.0=10; 1.1=11; 2.0=20, 3.0=30, 3.5=35,
etc.) and
XXX is the number of days from the year the project 'started', property
project.year.
The following snippit in from NAnt will do this for you...
target name=generate-build-number
script language=C#
imports
import namespace=System.Globalization /
import namespace=System.Threading /
/imports
code
!-- format for assembly revision is RRXXX where RR = framework
number (1.0=10; 1.1=11; 2.0=20, 3.0=30, 3.5=35, etc.) and
XXX is the number of days from the year the project 'started',
property project.year. --
![CDATA[
public static void ScriptMain(Project project) {
string frameworkRevisionNumber =
project.Properties[nant.settings.currentframework.revisionnumber];
int startYear =
Convert.ToInt32(project.Properties[project.year]);
DateTime start = new DateTime(startYear, 1, 1);
TimeSpan ts = DateTime.Now - start;
int days = ts.Days;
string version =
project.Properties[package.version].ToString() + . +
frameworkRevisionNumber + days.ToString();
project.Properties[project.version.numeric] =
version.ToString();
}
]]
/code
/script
/target
Mark
-Original Message-
From: Timothy Bish [mailto:tabish...@gmail.com]
Sent: Monday, June 15, 2009 10:53 AM
To: dev@activemq.apache.org
Subject: Re: NMS 1.1.0 RC1 Available
On Mon, 2009-06-15 at 07:15 -0700, Jim Gomes wrote:
* ANNOUNCEMENT *
The Apache NMS 1.1.0 Release Candidate 1 is now available at the
following
location:
http://people.apache.org/~jgomes/nms_1.1.0http://people.apache.org/%7Ejgomes/nms_1.1.0
The following projects are included:
Apache.NMS
Apache.NMS.ActiveMQ
Apache.NMS.EMS
Apache.NMS.MSMQ
Apache.NMS.WCF
There are release binaries and debug binaries (with PDBs) provided. The
binary ZIP files include pre-built assemblies for all of the platforms
that
are supported by each project (e.g., .NET 2.0, Mono, .NET 3.5, etc). Not
all projects support all platforms. Please note that in order to use the
Apache.NMS.EMS project files, you will need to provide your own copy of
the
TIBCO.EMS.dll, as this is a licensed 3rd Party application.
Please report any issues or problems you have with these files.
Best,
Jim Gomes
Nice work Jim.
There certainly are a lot of Zip files, do you think perhaps it would
make sense to package all this as one archive for each of the projects,
or a source and binary for each?
I took a look at the log4net project and it looks like there they just
package everything into one file.
See:
http://logging.apache.org/log4net/download.html
Regards
Tim.
__ Information from ESET NOD32 Antivirus, version of virus
signature database 4155 (20090615) __
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
__ Information from ESET NOD32 Antivirus, version of virus
signature database 4156 (20090615
NMS 1.1.0 RC2 Available
* ANNOUNCEMENT * The Apache NMS 1.1.0 Release Candidate 2 is now available at the following location: http://people.apache.org/~jgomes/nms_1.1.0http://people.apache.org/%7Ejgomes/nms_1.1.0 The following projects are included: Apache.NMS 1.1.0.1629 Apache.NMS.ActiveMQ 1.1.0.1629 Apache.NMS.EMS 1.1.0.1629 Apache.NMS.MSMQ 1.1.0.1629 Apache.NMS.WCF 1.1.0.1629 There are release binaries and debug binaries (with PDBs) provided. The binary ZIP files include pre-built assemblies for all of the platforms that are supported by each project (e.g., .NET 2.0, Mono, .NET 3.5, etc). Not all projects support all platforms. Please note that in order to use the Apache.NMS.EMS project files, you will need to provide your own copy of the TIBCO.EMS.dll, as this is a licensed 3rd Party application. Changes from RC1 include the following: - Fewer number of ZIP files. There is now only a bin and src ZIP file for each project. - Revision number is now embedded and automatically generated as part of the NAnt build. - Removed assembly info marking of SNAPSHOT and changed to GA. Please report any issues or problems you have with these files. A vote will be taken later on whether this should be the final release. Best, Jim Gomes
Re: NMS 1.1.0 RC2 Available
Thanks, Tim. Can you verify the PGP signature I generated on those files to make sure I did it correctly? Also, do I need to generate an MD5 hash file for any of the other files, or is that optional? On Thu, Jun 18, 2009 at 8:37 AM, Timothy Bish tabish...@gmail.com wrote: On Thu, 2009-06-18 at 07:59 -0700, Jim Gomes wrote: * ANNOUNCEMENT * The Apache NMS 1.1.0 Release Candidate 2 is now available at the following location: http://people.apache.org/~jgomes/nms_1.1.0http://people.apache.org/%7Ejgomes/nms_1.1.0 http://people.apache.org/%7Ejgomes/nms_1.1.0 The following projects are included: Apache.NMS 1.1.0.1629 Apache.NMS.ActiveMQ 1.1.0.1629 Apache.NMS.EMS 1.1.0.1629 Apache.NMS.MSMQ 1.1.0.1629 Apache.NMS.WCF 1.1.0.1629 There are release binaries and debug binaries (with PDBs) provided. The binary ZIP files include pre-built assemblies for all of the platforms that are supported by each project (e.g., .NET 2.0, Mono, .NET 3.5, etc). Not all projects support all platforms. Please note that in order to use the Apache.NMS.EMS project files, you will need to provide your own copy of the TIBCO.EMS.dll, as this is a licensed 3rd Party application. Changes from RC1 include the following: - Fewer number of ZIP files. There is now only a bin and src ZIP file for each project. - Revision number is now embedded and automatically generated as part of the NAnt build. - Removed assembly info marking of SNAPSHOT and changed to GA. Please report any issues or problems you have with these files. A vote will be taken later on whether this should be the final release. Best, Jim Gomes Very nice, seems much more manageable than before. Great Job Jim. Regards Tim. -- Tim Bish http://fusesource.com http://timbish.blogspot.com/
Re: NMS 1.1.0 RC2 Available
The KEYS file is in the root of the project. Look in https://svn.apache.org/repos/asf/activemq/activemq-dotnet I thought a central location made more sense than having it spread into 12 different locations. - Jim -Original Message- From: Timothy Bish tabish...@gmail.com Date: Fri, 19 Jun 2009 10:57:33 To: dev@activemq.apache.org Subject: Re: NMS 1.1.0 RC2 Available On Fri, 2009-06-19 at 07:36 -0700, Jim Gomes wrote: Thanks, Tim. Can you verify the PGP signature I generated on those files to make sure I did it correctly? Also, do I need to generate an MD5 hash file for any of the other files, or is that optional? The MD5 checksun isn't a requirement no, signing with detached signature should be sufficient. I noticed last night that the KEYS file isn't present in any of the NMS projects so we need to add that so that myself and others can import your public key in order to verify the signature. Regards Tim. On Thu, Jun 18, 2009 at 8:37 AM, Timothy Bish tabish...@gmail.com wrote: On Thu, 2009-06-18 at 07:59 -0700, Jim Gomes wrote: * ANNOUNCEMENT * The Apache NMS 1.1.0 Release Candidate 2 is now available at the following location: http://people.apache.org/~jgomes/nms_1.1.0http://people.apache.org/%7Ejgomes/nms_1.1.0 http://people.apache.org/%7Ejgomes/nms_1.1.0 The following projects are included: Apache.NMS 1.1.0.1629 Apache.NMS.ActiveMQ 1.1.0.1629 Apache.NMS.EMS 1.1.0.1629 Apache.NMS.MSMQ 1.1.0.1629 Apache.NMS.WCF 1.1.0.1629 There are release binaries and debug binaries (with PDBs) provided. The binary ZIP files include pre-built assemblies for all of the platforms that are supported by each project (e.g., .NET 2.0, Mono, .NET 3.5, etc). Not all projects support all platforms. Please note that in order to use the Apache.NMS.EMS project files, you will need to provide your own copy of the TIBCO.EMS.dll, as this is a licensed 3rd Party application. Changes from RC1 include the following: - Fewer number of ZIP files. There is now only a bin and src ZIP file for each project. - Revision number is now embedded and automatically generated as part of the NAnt build. - Removed assembly info marking of SNAPSHOT and changed to GA. Please report any issues or problems you have with these files. A vote will be taken later on whether this should be the final release. Best, Jim Gomes Very nice, seems much more manageable than before. Great Job Jim. Regards Tim. -- Tim Bish http://fusesource.com http://timbish.blogspot.com/
Re: Using NMS to connect to OpenMQ via stomp
I think the fix sounds right. Without having looked at the code yet, would it make sense to name the constant NULL_BYTE so it is clear how it should be used? --Original Message-- From: matt walsh To: ActiveMQ Dev ReplyTo: ActiveMQ Dev Subject: Using NMS to connect to OpenMQ via stomp Sent: Jun 24, 2009 9:29 PM Hi All, I have had a problem connecting to OpenMQ via stomp using Apache NMS. It seems the NMS code terminates stomp frames using a 'NULL' character (as per the stomp spec), which is defined in the class StompFrameStream as follows public const char NULL = (char) 0; OpenMQ was giving me errors because it seems from my investigations that this 'NULL' is infact a double byte character and is therefore sending 2 zeros at the end of a frame. This leaves an extra NULL lying around in the stream that OpenMQ is unhappy with, breaking further commands sent for a session. I have patched the NMS source to define NULL as a byte, ie public const byte NULL = (byte) 0; This makes the problem go away for OpenMQ. I would like some advice on this. Is it acceptable for a Stomp frame to have additional NULL characters lying around as NMS seems to be doing (and thus is this a problem that should be dealt with by OpenMQ) or should NMS be patched in a way similar to what I have done here? I have attached my patched version of the 1.0 version of StompFrameStream. http://www.nabble.com/file/p24196808/StompFrameStream.cs StompFrameStream.cs -- View this message in context: http://www.nabble.com/Using-NMS-to-connect-to-OpenMQ-via-stomp-tp24196808p24196808.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. - Jim
Re: NMS 1.1.0 RC2 Available
Hi Mark, Thanks for the idea. I'm not sure what might change for next time, but I definitely want to improve upon the automated tools I have currently. I have been working on creating a toolset that makes things easier to generate builds and deploy them out. Best, Jim On Thu, Jun 25, 2009 at 8:36 AM, Mark Pollack mark.poll...@springsource.com wrote: Hi, Can you put RC1, RC2, etc., in the filenames going forward or for next time? Mark
[VOTE RESULT] Release Apache ActiveMQ .NET 1.1.0
After bringing the release of Apache ActiveMQ .NET 1.1.0 to a vote, here are the results for the individual projects: +1 -1 0 Module Name --- --- --- - 3 0 0 Apache.NMS 3 0 0 Apache.NMS.ActiveMQ 3 0 0 Apache.NMS.EMS 3 0 0 Apache.NMS.MSMQ 3 0 0 Apache.NMS.WCF With a total of +3 votes for each project, and no negatives, the product will move to a shipping status. The code has been copied out to the distribution servers, and is being updated to the download mirror sites. The WIKI page links have been updated, and will be published on its normal update schedule. An announcement to the developer and user lists will be made after the updates have been published. - Jim Gomes
Re: WIKI Problems
Hi Bruce, Thanks for doing that. I think I figured out what the problem is. There seems to be an extra file out on the website. I'm not sure where this file came from. The bogus file is here: http://activemq.apache.org/nms.html This file shouldn't be there. The proper file is http://activemq.apache.org/nms/index.html. If you look at those two pages, they are identical, but the first one's links are all incorrect. I checked the main ActiveMQ webpage to make sure that they don't link to the bogus webpage, and everything that I checked appears to link to the correct webpage. This bogus webpage has all of the latest changes to it, so I think it was generated from the WIKI. I wonder if it were deleted, would it reappear at the next generation? Should it just be removed, or should an auto-forwarding page be put in its place that would forward to the correct webpage? - Jim On Wed, Jul 22, 2009 at 8:54 AM, Bruce Snyder bruce.sny...@gmail.comwrote: On Tue, Jul 21, 2009 at 8:50 AM, Jim Gomese.se...@gmail.com wrote: The NMS WIKI pages are not being generated correctly. I checked the WIKI sources for the NMS project pages, and they are all correct with no missing pages. However, some of the generated pages are missing, and some have incorrect links to other pages. Is there anyone available to help diagnose the generation problems? I've just manually exported the NMS space, did that resolve it? Bruce -- perl -e 'print unpack(u30,D0G)u8...@4vyy95R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' ActiveMQ in Action: http://bit.ly/2je6cQ Blog: http://bruceblog.org/ Twitter: http://twitter.com/brucesnyder
Re: WIKI Problems
OK. I deleted the bogus webpage, so we can see if it reappears. None of the other webpages were in added to the root directory, so I think it may have been an isolated fluke of having that file placed there. On Wed, Jul 22, 2009 at 11:48 AM, Bruce Snyder bruce.sny...@gmail.comwrote: On Wed, Jul 22, 2009 at 12:30 PM, Jim Gomese.se...@gmail.com wrote: Hi Bruce, Thanks for doing that. I think I figured out what the problem is. There seems to be an extra file out on the website. I'm not sure where this file came from. The bogus file is here: http://activemq.apache.org/nms.html This file shouldn't be there. The proper file is http://activemq.apache.org/nms/index.html. If you look at those two pages, they are identical, but the first one's links are all incorrect. I checked the main ActiveMQ webpage to make sure that they don't link to the bogus webpage, and everything that I checked appears to link to the correct webpage. This bogus webpage has all of the latest changes to it, so I think it was generated from the WIKI. I wonder if it were deleted, would it reappear at the next generation? Should it just be removed, or should an auto-forwarding page be put in its place that would forward to the correct webpage? In a static HTML scenario, I would usually add a meta-refresh header element to automatically push to the correct page. But since these pages are automatically generated, that's not really an option. It would probably be best if we removed that page and check to see if it is automatically regenerated. Bruce -- perl -e 'print unpack(u30,D0G)u8...@4vyy95R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' ActiveMQ in Action: http://bit.ly/2je6cQ Blog: http://bruceblog.org/ Twitter: http://twitter.com/brucesnyder
Re: WIKI Problems
I saw that Anonymous owned item named NMS, but it is actually an attachment. It says that it is 7Kb, but I can't seem to delete it or even view it. If I browse the space and list all of the pages alphabetically, there is only one page named NMS. I don't know how to clean up that attachment. There were some obsolete pages in the ActiveMQ WIKI, so I cleaned those up and fixed the link references to the current pages. Perhaps those old pages were causing a generation problem. On Wed, Jul 22, 2009 at 5:47 PM, Bruce Snyder bruce.sny...@gmail.comwrote: On Wed, Jul 22, 2009 at 6:29 PM, Jim Gomese.se...@gmail.com wrote: Yep. It's back. In browsing the pages in the wiki, I actually see two named NMS. One if owned by you and one is owned by Anonymous. Bruce -- perl -e 'print unpack(u30,D0G)u8...@4vyy95R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' ActiveMQ in Action: http://bit.ly/2je6cQ Blog: http://bruceblog.org/ Twitter: http://twitter.com/brucesnyder
Re: WIKI Problems
Found it. I took a closer look at the two HTML files, and discovered that the clean up I did on the ActiveMQ WIKI will fix the problem. The nms.html webpage was actually just including the index.html page, which is why they looked identical. The next time the website is generated, I think it will be better. On Wed, Jul 22, 2009 at 7:58 PM, Jim Gomes e.se...@gmail.com wrote: I saw that Anonymous owned item named NMS, but it is actually an attachment. It says that it is 7Kb, but I can't seem to delete it or even view it. If I browse the space and list all of the pages alphabetically, there is only one page named NMS. I don't know how to clean up that attachment. There were some obsolete pages in the ActiveMQ WIKI, so I cleaned those up and fixed the link references to the current pages. Perhaps those old pages were causing a generation problem. On Wed, Jul 22, 2009 at 5:47 PM, Bruce Snyder bruce.sny...@gmail.comwrote: On Wed, Jul 22, 2009 at 6:29 PM, Jim Gomese.se...@gmail.com wrote: Yep. It's back. In browsing the pages in the wiki, I actually see two named NMS. One if owned by you and one is owned by Anonymous. Bruce -- perl -e 'print unpack(u30,D0G)u8...@4vyy95R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' ActiveMQ in Action: http://bit.ly/2je6cQ Blog: http://bruceblog.org/ Twitter: http://twitter.com/brucesnyder
Re: [VOTE] Release Apache Apollo 1.0 Beta 4
+1 On Wed, Jun 29, 2011 at 3:10 PM, Hiram Chirino hi...@hiramchirino.comwrote: Hi Everyone, It's been several weeks since the last Apollo beta release. Since then several new and noteworthy features have been implementing including: * APLO-17 - Support message expiration * APLO-39 - Apply configuration updates to a broker without needing a restart * APLO-40 - Web interface should support editing all the apollo configuration files (log4j, jaas, etc.) * APLO-41 - Expose JVM Status/Metrics via REST API * APLO-43 - Create an XSD to validate the apollo.xml configuration file. * APLO-45 - Support auto deleting idle queues and topics * APLO-47 - Add connection_counter, consumer_counter, and producer_counter metrics to the management interface * APLO-50 - Support pre-creating durable subscriptions via the broker config file * APLO-55 - Add an option to enable strict validation of the configuration XML * APLO-57 - Track desired service state so you can stop a service which is still starting * APLO-60 - Support regular expressions in destination wildcards. * APLO-42 - File based JAAS login modules should cache file contents until changed. * APLO-44 - Eagerly create destinations which are explicitly defined in the server configuration file. * APLO-46 - Include current/total page info when the REST interface returns a paged result set You can find the release notes at https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12316522styleName=TextprojectId=12311310Create=Create The new release candidate has been staged to nexus under: https://repository.apache.org/content/repositories/orgapacheactivemq-007/ Binary distros can be found at: https://repository.apache.org/content/repositories/orgapacheactivemq-007/org/apache/activemq/apache-apollo/1.0-beta4/ Source code distros can be found at: https://repository.apache.org/content/repositories/orgapacheactivemq-007/org/apache/activemq/apollo-project/1.0-beta4/ The build was tagged at: http://svn.apache.org/repos/asf/activemq/activemq-apollo/tags/apollo-project-1.0-beta4/ The project website for that version has been staged to: http://activemq.apache.org/apollo/versions/1.0-beta4/website/index.html Please vote to approve this release [ ] +1 Release Apache ActiveMQ Apollo 1.0 Beta 4 [ ] -1 Veto the release (provide specific comments) Here's my +1 Regards, Hiram FuseSource Web: http://fusesource.com/
Re: Website Branding Checklist
Thanks, Hiram. Do we have a list of our project's brands and their proper usage to use as a standard? On Wed, Jul 6, 2011 at 12:07 PM, Hiram Chirino hi...@hiramchirino.comwrote: Hi Folks, The Apache Board is expecting that the ActiveMQ project be compliant with the following branding checklist by this next board report that's due. http://www.apache.org/foundation/marks/pmcs#checklist I've gone through and fixed up most of the items that we were out of compliance with. I've just kicked off an export of the wiki so all the changes should be live within an hour. Hoping some of you good folks could double check the work. Regards, Hiram FuseSource Web: http://fusesource.com/
Re: Possible NMS Transaction bug Transaction GUID not Unique
Thanks for the info on this issue. Would you be able to enter a JIRA item
for this, along with any unit test code that exposes the problem? Having
unit tests helps us ensure we have fixed the problem and guards against any
future regressions.
Best,
Jim
On Wed, Aug 10, 2011 at 10:50 PM, spenceee spenc...@gmail.com wrote:
G'day, first time poster, apologies if I'm in the wrong forum.
I think I have found a defect in the NMS 1.5.0 API regarding the allocation
of a Resource Manager GUID in the NetTxConnection class. This is sent to
the MS DTC as a unique identifier for the resource manager. I've read the
source code for this class and it is derived from the BrokerInfo.BrokerID
from the connection. According to MSDN the ID needs to be:
resourceManagerIdentifier
A unique identifier for a resource manager, which should persist across
resource manager failure or reboot.
If I understand correctly, each new connection to the broker will get a new
value for BrokerID. Therefore I can see little value in deriving the GUID
from the broker info. I think it would make more sense for
NetTxConnection.ResourceManagerGUID to set the value internally to
Guid.NewGuid(); and then return this value.
internal resourceManagerGuid = Guid.NewGuid; //Guaranteed* unique
and threadsafe.
internal Guid ResourceManagerGuid
{
get
{
return resourceManagerGuid;
}
}
The only reason I can see for receiving this error is if somehow the same
brokerID is returned. I am using 4 threads to make connections with to the
broker concurrently on 4 separate Active MQ connection objects.
I've santised the error I've received if it's helpful.
Error : 2011/19/12 04:19:44 xxx: Source: System.Transactions
Message: A resource manager with the same identifier is already registered
with the specified transaction coordinator. (Exception from HRESULT:
0x8004D102)Stack:at
System.Transactions.Oletx.IDtcProxyShimFactory.CreateResourceManager(Guid
resourceManagerIdentifier, IntPtr managedIdentifier, IResourceManagerShim
resourceManagerShim)
at
System.Transactions.Oletx.OletxResourceManager.get_ResourceManagerShim()
at System.Transactions.Oletx.OletxResourceManager.Reenlist(Int32
prepareInfoLength, Byte[] prepareInfo, IEnlistmentNotificationInternal
enlistmentNotification)
at
System.Transactions.Oletx.OletxTransactionManager.ReenlistTransaction(Guid
resourceManagerIdentifier, Byte[] recoveryInformation,
IEnlistmentNotificationInternal enlistmentNotification)
at System.Transactions.TransactionManager.Reenlist(Guid
resourceManagerIdentifier, Byte[] recoveryInformation,
IEnlistmentNotification enlistmentNotification)
at Apache.NMS.ActiveMQ.TransactionContext.InitializeDtcTxContext()
at
Apache.NMS.ActiveMQ.NetTxConnection.CreateAtiveMQSession(AcknowledgementMode
ackMode)
at Apache.NMS.ActiveMQ.Connection.CreateSession(AcknowledgementMode
sessionAcknowledgementMode)
at xxx.TimeoutRead(Int32 timeOut, Boolean commit)
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Possible-NMS-Transaction-bug-Transaction-GUID-not-Unique-tp3735015p3735015.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: C# NMS: After close a connection a couple of handles will not be cleaned up
Thanks for the report. It looks like we are at least leaking threads on the
InactivityMonitor. I've taken the sample provided and used it as a base to
reproduce the problem. I can reproduce a thread leak for every connection
that should have been cleaned up via Dispose(). I'll take a closer look at
it tomorrow and see if I can narrow it down and come up with a fix.
If you have any additional info on what is being leaked, that would be
helpful to have.
Thanks.
-Jim
On Sat, Sep 10, 2011 at 9:23 AM, Shine activ...@club.webhop.org wrote:
Hi,
i use the latest binaries from
http://activemq.apache.org/nms/activemq-downloads.html (1.5.1.2341)
and i tried the source code from subversion.
am Freitag, 9. September 2011 um 21:53 schrieben Sie:
On Fri, 2011-09-09 at 12:44 -0700, Shine wrote:
hi,
if you connect to the message broker and close/dispose everything, few
handles still alive.
expample:
Apache.NMS.IConnectionFactory factory = new
Apache.NMS.NMSConnectionFactory(@tcp://
messagebroker.xabcd.org:61616?wireFormat.maxInactivityDuration=0);
using (Apache.NMS.IConnection connection =
factory.CreateConnection(NotForYourEyes, NotForYourEyes))
{
using (Apache.NMS.ISession session = connection.CreateSession())
{
Apache.NMS.IDestination destination = new
Apache.NMS.ActiveMQ.Commands.ActiveMQTopic({12345678-288C-4787-A9C9-123456789012}/11023);
using (Apache.NMS.IMessageConsumer consumer =
session.CreateConsumer(destination))
{
connection.Start();
}
}
}
About 35 handles will not be cleaned up. If you do some reconnects you
get
an OutOfMemory Exception after a while.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/C-NMS-After-close-a-connection-a-couple-of-handles-will-not-be-cleaned-up-tp3802609p3802609.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Usually helpful to let us know what version you are using, there were
some things like this fixed in past releases, if not on v1.5.1 then I'd
suggest giving that a try.
Regards
--
Mit freundlichen Grüßen
activ...@club.webhop.org
mailto:activ...@club.webhop.org
--
View this message in context:
http://activemq.2283324.n4.nabble.com/C-NMS-After-close-a-connection-a-couple-of-handles-will-not-be-cleaned-up-tp3802609p3804031.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: C# NMS: After close a connection a couple of handles will not be cleaned up
The problem is only reproducible with the
wireFormat.maxInactivityDuration=0parameter. If this parameter is
removed, then the thread is cleaned up
correctly. Knowing that, I think the fix should be pretty straightforward.
In the meantime, as a work-around, I would suggest not adding that
parameter.
On Mon, Sep 12, 2011 at 6:06 PM, Jim Gomes e.se...@gmail.com wrote:
Thanks for the report. It looks like we are at least leaking threads on
the InactivityMonitor. I've taken the sample provided and used it as a base
to reproduce the problem. I can reproduce a thread leak for every
connection that should have been cleaned up via Dispose(). I'll take a
closer look at it tomorrow and see if I can narrow it down and come up with
a fix.
If you have any additional info on what is being leaked, that would be
helpful to have.
Thanks.
-Jim
On Sat, Sep 10, 2011 at 9:23 AM, Shine activ...@club.webhop.org wrote:
Hi,
i use the latest binaries from
http://activemq.apache.org/nms/activemq-downloads.html (1.5.1.2341)
and i tried the source code from subversion.
am Freitag, 9. September 2011 um 21:53 schrieben Sie:
On Fri, 2011-09-09 at 12:44 -0700, Shine wrote:
hi,
if you connect to the message broker and close/dispose everything, few
handles still alive.
expample:
Apache.NMS.IConnectionFactory factory = new
Apache.NMS.NMSConnectionFactory(@tcp://
messagebroker.xabcd.org:61616?wireFormat.maxInactivityDuration=0);
using (Apache.NMS.IConnection connection =
factory.CreateConnection(NotForYourEyes, NotForYourEyes))
{
using (Apache.NMS.ISession session = connection.CreateSession())
{
Apache.NMS.IDestination destination = new
Apache.NMS.ActiveMQ.Commands.ActiveMQTopic({12345678-288C-4787-A9C9-123456789012}/11023);
using (Apache.NMS.IMessageConsumer consumer =
session.CreateConsumer(destination))
{
connection.Start();
}
}
}
About 35 handles will not be cleaned up. If you do some reconnects you
get
an OutOfMemory Exception after a while.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/C-NMS-After-close-a-connection-a-couple-of-handles-will-not-be-cleaned-up-tp3802609p3802609.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Usually helpful to let us know what version you are using, there were
some things like this fixed in past releases, if not on v1.5.1 then I'd
suggest giving that a try.
Regards
--
Mit freundlichen Grüßen
activ...@club.webhop.org
mailto:activ...@club.webhop.org
--
View this message in context:
http://activemq.2283324.n4.nabble.com/C-NMS-After-close-a-connection-a-couple-of-handles-will-not-be-cleaned-up-tp3802609p3804031.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: [VOTE] Apache ActiveMQ 5.5.1
+1 On Wed, Oct 12, 2011 at 5:32 AM, Hiram Chirino hi...@hiramchirino.comwrote: Hi all,I've just cut a release candidate for the 5.5.1 release.This release is identical to the the 5.5.0 except that it fixes issue AMQ-3491 by removing the the camel console to avoid including a LGPL dependency in our distribution. Could you review the artifacts and vote? You can get binary distributions here: https://repository.apache.org/content/repositories/orgapacheactivemq-056/org/apache/activemq/apache-activemq/5.5.1/ Source archives are here: https://repository.apache.org/content/repositories/orgapacheactivemq-056/org/apache/activemq/activemq-parent/5.5.1/ Maven2 repository is at: https://repository.apache.org/content/repositories/orgapacheactivemq-056/ Source SVN tag:http://svn.apache.org/viewvc/activemq/tags/activemq-5.5.1 Please vote to approve this release [ ] +1 Release the binary as Apache ActiveMQ 5.5.1[ ] -1 Veto the release (provide specific comments) Here's my +1 Regards, Hiram FuseSource Web: http://fusesource.com/
Re: [VOTE] Apache ActiveMQ 5.4.3
+1 On Wed, Oct 12, 2011 at 7:18 AM, Hiram Chirino hi...@hiramchirino.comwrote: Hi all,I've just cut a release candidate for the 5.4.3 release.Thisrelease is identical to the the 5.4.2 except that it fixes issueAMQ-3491 by removing the the camel console to avoid including a LGPLdependency in our distribution. Could you review the artifacts and vote? You can get binary distributions here: https://repository.apache.org/content/repositories/orgapacheactivemq-059/org/apache/activemq/apache-activemq/5.4.3/ Source archives are here: https://repository.apache.org/content/repositories/orgapacheactivemq-059/org/apache/activemq/activemq-parent/5.4.3/ Maven2 repository is at: https://repository.apache.org/content/repositories/orgapacheactivemq-059/ Source SVN tag:http://svn.apache.org/viewvc/activemq/tags/activemq-5.4.3 Please vote to approve this release[ ] +1 Release the binary as Apache ActiveMQ 5.4.3[ ] -1 Veto the release (provide specific comments) Here's my +1 Regards, Hiram FuseSource Web: http://fusesource.com/
Re: {VOTE] Release Apache.NMS.ActiveMQ 1.5.2
+1 On Mon, Nov 14, 2011 at 7:56 AM, Timothy Bish tabish...@gmail.com wrote: Hello This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.5.2. New in this release: * This release focuses on stability and performance fixes for the NMS ActiveMQ client, no new features were added in this release. The binaries and source bundles for the Release Candidate can be found here: http://people.apache.org/~tabish/nms-1.5.0/ The Wiki Page for this release is here: http://activemq.apache.org/nms/apachenmsactivemq-v152.html The list of issues resolved is here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201styleName=Htmlversion=12316156 Please cast your votes (the vote will be open for 72 hrs): [ ] +1 Release the source as Apache NMS.ActiveMQ v1.5.2 [ ] -1 Veto the release (provide specific comments) Here's my +1 Regards -- Tim Bish FuseSource Email: tim.b...@fusesource.com Web: http://fusesource.com Twitter: tabish121 Blog: http://timbish.blogspot.com/
Re: {VOTE] Release Apache.NMS.Stomp 1.5.2
+1 On Tue, Nov 15, 2011 at 12:44 PM, Timothy Bish tabish...@gmail.com wrote: Hello This is a call for a vote on the release of Apache.NMS.Stomp v1.5.2. New in this release: * This release focuses on stability and performance fixes for the NMS Stomp client, the main fix in the release addresses an issue found in interoperability with Stomp v1.1 brokers. The binaries and source bundles for the Release Candidate can be found here: http://people.apache.org/~tabish/nms-1.5.0/ The Wiki Page for this release is here: http://activemq.apache.org/nms/apachenmsstomp-v152.html The list of issues resolved is here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201styleName=Htmlversion=12316156 Please cast your votes (the vote will be open for 72 hrs): [ ] +1 Release the source as Apache NMS.Stomp v1.5.2 [ ] -1 Veto the release (provide specific comments) Here's my +1 Regards -- Tim Bish FuseSource Email: tim.b...@fusesource.com Web: http://fusesource.com Twitter: tabish121 Blog: http://timbish.blogspot.com/
Re: C# - NMS.ActiveMQ (Trunk) - Windows-Service with admin-user account
This is interesting. With your work-around in place, it will eventually
connect and everything works correctly after that?
On Mon, Nov 21, 2011 at 8:59 AM, Shine activ...@club.webhop.org wrote:
hi,
I am using the latest version of NMS to connect to an ActiveMQ Server
(version 5.5).
If you use this snippet in a windows service runs with a local admin
credential, you get an EndOfStreamException at this.connection.Start();.
That snippet works fine in a normal windows application or if the service
runs with local system.
Snippet
try
{
Apache.NMS.IConnectionFactory connectionFactory = new
Apache.NMS.ActiveMQ.ConnectionFactory(ssl://x);
System.Diagnostics.Trace.WriteLine(Verbindung wird
erstellt.);
this.connection =
connectionFactory.CreateConnection(MessageBrokerUsername,
MessageBrokerPassword);
this.connection.ExceptionListener += new
Apache.NMS.ExceptionListener(connection_ExceptionListener);
// this.connection.ClientId =
System.Environment.TickCount.ToString();
System.Diagnostics.Trace.WriteLine(Verbindung wird
aufgebaut.);
// Here occures the exception
this.connection.Start();
this.session = connection.CreateSession();
System.Diagnostics.Trace.WriteLine(Queue wird erstellt.);
Apache.NMS.IDestination destination = new
Apache.NMS.ActiveMQ.Commands.ActiveMQQueue(test);
System.Diagnostics.Trace.WriteLine(Consumer wird
erstellt.);
this.consumer = session.CreateConsumer(destination);
this.consumer.Listener += new
Apache.NMS.MessageListener(consumer_Listener);
}
catch (System.Exception ex)
{
System.Diagnostics.Trace.WriteLine(ex.ToString());
}
Workaround: Call CreateConnection and Start again.
Replace: this.connection.Start();
To:
bool connected = false;
int connectionCounter = 0;
while (!connected)
{
try
{
connectionCounter++;
this.connection.Start();
connected = this.connection.IsStarted;
}
catch (System.Exception ex)
{
this.connection.Dispose();
System.Diagnostics.Trace.WriteLine(ex.ToString());
System.Diagnostics.Trace.WriteLine(Tries to
connect: + connectionCounter.ToString());
System.Threading.Thread.Sleep(3000);
this.connection =
connectionFactory.CreateConnection(MessageBrokerUsername,
MessageBrokerPassword);
}
}
Anyone knows a other solution for my problem?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/C-NMS-ActiveMQ-Trunk-Windows-Service-with-admin-user-account-tp4092212p4092212.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: C# - NMS.ActiveMQ (Trunk) - Windows-Service with admin-user account
I wouldn't have expected that sort of behavior. Very odd. Would you mind
entering this as a JIRA issue so that we can track it and get it fixed in a
future release? Here's the link: https://issues.apache.org/jira
Thanks for your help. Also, if you have a patch that fixes it, feel free
to contribute it with the report. Be sure to mark the Grant ASF License
for it.
Best,
Jim
On Tue, Nov 22, 2011 at 12:14 PM, Shine activ...@club.webhop.org wrote:
Hi jgomes,
yes .. everything works fine after the reconnect and it takes never
more than one reconnect.
best regards
Marc
am Montag, 21. November 2011 um 20:49 schrieben Sie:
This is interesting. With your work-around in place, it will eventually
connect and everything works correctly after that?
On Mon, Nov 21, 2011 at 8:59 AM, Shine activ...@club.webhop.org wrote:
hi,
I am using the latest version of NMS to connect to an ActiveMQ Server
(version 5.5).
If you use this snippet in a windows service runs with a local admin
credential, you get an EndOfStreamException at
this.connection.Start();.
That snippet works fine in a normal windows application or if the
service
runs with local system.
Snippet
try
{
Apache.NMS.IConnectionFactory connectionFactory = new
Apache.NMS.ActiveMQ.ConnectionFactory(ssl://x);
System.Diagnostics.Trace.WriteLine(Verbindung wird
erstellt.);
this.connection =
connectionFactory.CreateConnection(MessageBrokerUsername,
MessageBrokerPassword);
this.connection.ExceptionListener += new
Apache.NMS.ExceptionListener(connection_ExceptionListener);
// this.connection.ClientId =
System.Environment.TickCount.ToString();
System.Diagnostics.Trace.WriteLine(Verbindung wird
aufgebaut.);
// Here occures the exception
this.connection.Start();
this.session = connection.CreateSession();
System.Diagnostics.Trace.WriteLine(Queue wird
erstellt.);
Apache.NMS.IDestination destination = new
Apache.NMS.ActiveMQ.Commands.ActiveMQQueue(test);
System.Diagnostics.Trace.WriteLine(Consumer wird
erstellt.);
this.consumer = session.CreateConsumer(destination);
this.consumer.Listener += new
Apache.NMS.MessageListener(consumer_Listener);
}
catch (System.Exception ex)
{
System.Diagnostics.Trace.WriteLine(ex.ToString());
}
Workaround: Call CreateConnection and Start again.
Replace: this.connection.Start();
To:
bool connected = false;
int connectionCounter = 0;
while (!connected)
{
try
{
connectionCounter++;
this.connection.Start();
connected = this.connection.IsStarted;
}
catch (System.Exception ex)
{
this.connection.Dispose();
System.Diagnostics.Trace.WriteLine(ex.ToString());
System.Diagnostics.Trace.WriteLine(Tries to
connect: + connectionCounter.ToString());
System.Threading.Thread.Sleep(3000);
this.connection =
connectionFactory.CreateConnection(MessageBrokerUsername,
MessageBrokerPassword);
}
}
Anyone knows a other solution for my problem?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/C-NMS-ActiveMQ-Trunk-Windows-Service-with-admin-user-account-tp4092212p4092212.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
___
If you reply to this email, your message will be added to the discussion
below:
http://activemq.2283324.n4.nabble.com/C-NMS-ActiveMQ-Trunk-Windows-Service-with-admin-user-account-tp4092212p4092872.html
To unsubscribe from C# - NMS.ActiveMQ (Trunk) - Windows-Service
with admin-user account, visit
http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=4092212code=YWN0aXZlbXFAY2x1Yi53ZWJob3Aub3JnfDQwOTIyMTJ8MTE4Nzc0MjAzMQ==
--
Mit freundlichen Grüßen
activ...@club.webhop.org
mailto:activ...@club.webhop.org
--
View this message in context:
http://activemq.2283324.n4.nabble.com/C-NMS-ActiveMQ-Trunk-Windows-Service-with-admin-user-account-tp4092212p4097126.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Apollo 1.0 Beta 6
+1 On Thu, Dec 8, 2011 at 11:35 AM, Hiram Chirino hi...@hiramchirino.comwrote: Hi Everyone, I thought it would be a great time to put out another Apollo beta release since it's picked up quite a few new features and a ton of bug fixes. You can find the release notes at https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12319157styleName=TextprojectId=12311310Create=Create The new release candidate has been staged to nexus under: https://repository.apache.org/content/repositories/orgapacheactivemq-299/ Binary distros can be found at: https://repository.apache.org/content/repositories/orgapacheactivemq-299/org/apache/activemq/apache-apollo/1.0-beta6/ Source code distros can be found at: https://repository.apache.org/content/repositories/orgapacheactivemq-299/org/apache/activemq/apollo-project/1.0-beta6/ The build was tagged at: http://svn.apache.org/repos/asf/activemq/activemq-apollo/tags/apollo-project-1.0-beta6/ The project website for that version has been staged to: http://activemq.apache.org/apollo/versions/1.0-beta6/website/index.html Please vote to approve this release [ ] +1 Release Apache ActiveMQ Apollo 1.0 Beta 6 [ ] -1 Veto the release (provide specific comments) Here's my +1 Regards, Hiram FuseSource Web: http://fusesource.com/
Re: {VOTE] Release Apache.NMS.ActiveMQ 1.5.3
+1 There's a minor typo on the release page. The link text to the source zip still shows 1.5.2. The rest looks good. On Mon, Jan 23, 2012 at 5:29 PM, Timothy Bish tabish...@gmail.com wrote: Hello This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.5.3. New in this release: * This release focuses on stability fixes for the NMS ActiveMQ client, no new features were added in this release. The binaries and source bundles for the Release Candidate can be found here: http://people.apache.org/~tabish/nms-1.5.0/ The Wiki Page for this release is here: http://activemq.apache.org/nms/apachenmsactivemq-v153.html The list of issues resolved is here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201styleName=Htmlversion=12319084 Please cast your votes (the vote will be open for 72 hrs): [ ] +1 Release the source as Apache NMS.ActiveMQ v1.5.3 [ ] -1 Veto the release (provide specific comments) Here's my +1 Regards
Re: [VOTE] Release Apache Apollo 1.1
+1 On Wed, Feb 29, 2012 at 9:24 AM, Hiram Chirino hi...@hiramchirino.comwrote: Hi Everyone, It's been a month since the Apollo 1.0 release. I'd like to do a new 1.1 release to pickup a couple of bug fixes and features. You can find the release notes at https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12316477styleName=TextprojectId=12311310Create=Create The new release candidate has been staged to nexus under: https://repository.apache.org/content/repositories/orgapacheactivemq-092/ Source code distros can be found at: https://repository.apache.org/content/repositories/orgapacheactivemq-092/org/apache/activemq/apollo-project/1.1/ Binary distros can be found at: https://repository.apache.org/content/repositories/orgapacheactivemq-092/org/apache/activemq/apache-apollo/1.1/ The build was tagged at: http://svn.apache.org/repos/asf/activemq/activemq-apollo/tags/apollo-project-1.1/ The project website for that version has been staged to: http://activemq.apache.org/apollo/versions/1.1/website/index.html Please vote to approve this release [ ] +1 Release Apache Apollo 1.1 [ ] -1 Veto the release (provide specific comments) As usual, the vote will be open for at least 72 hours. Here's my +1 -- ** *Hiram Chirino* *Software Fellow | FuseSource Corp.* *chir...@fusesource.com | fusesource.com* *skype: hiramchirino | twitter: @hiramchirino http://twitter.com/hiramchirino * *blog: Hiram Chirino's Bit Mojo http://hiramchirino.com/blog/* * * * *
Re: {VOTE] Release Apache.NMS.ActiveMQ 1.5.4
+1 On Mon, Apr 9, 2012 at 8:49 AM, Timothy Bish tabish...@gmail.com wrote: Hello This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.5.4. New in this release: * This release focuses on stability fixes for the NMS ActiveMQ client, no new features were added in this release. The binaries and source bundles for the Release Candidate can be found here: http://people.apache.org/~tabish/nms-1.5.0/ The Wiki Page for this release is here: http://activemq.apache.org/nms/apachenmsactivemq-v154.html The list of issues resolved is here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201styleName=Htmlversion=12319545 Please cast your votes (the vote will be open for 72 hrs): [ ] +1 Release the source as Apache NMS.ActiveMQ v1.5.4 [ ] -1 Veto the release (provide specific comments) Here's my +1 -- Tim Bish Sr Software Engineer | FuseSource Corp tim.b...@fusesource.com | www.fusesource.com skype: tabish121 | twitter: @tabish121 blog: http://timbish.blogspot.com/
Re: [VOTE] Release Apache Apollo 1.2
+1 On Fri, Apr 13, 2012 at 6:53 AM, Hiram Chirino hi...@hiramchirino.comwrote: Hi Everyone, Lots of fixes and improvement have found their way into Apollo since the 1.1 release. I've deployed a 1.2 release candidate to pickup those fixes and improvements. You can find the release notes at https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12319854styleName=TextprojectId=12311310Create=Create The new release candidate has been staged to nexus under: https://repository.apache.org/content/repositories/orgapacheactivemq-042/ Source code distros can be found at: https://repository.apache.org/content/repositories/orgapacheactivemq-042/org/apache/activemq/apollo-project/1.2/ Binary distros can be found at: https://repository.apache.org/content/repositories/orgapacheactivemq-042/org/apache/activemq/apache-apollo/1.2/ The build was tagged at: http://svn.apache.org/repos/asf/activemq/activemq-apollo/tags/apollo-project-1.2/ The project website for that version has been staged to: http://activemq.apache.org/apollo/versions/1.2/website/index.html Please vote to approve this release [ ] +1 Release Apache Apollo 1.2 [ ] -1 Veto the release (provide specific comments) As usual, the vote will be open for at least 72 hours. Here's my +1 -- ** *Hiram Chirino* *Software Fellow | FuseSource Corp.* *chir...@fusesource.com | fusesource.com* *skype: hiramchirino | twitter: @hiramchirino http://twitter.com/hiramchirino * *blog: Hiram Chirino's Bit Mojo http://hiramchirino.com/blog/* * * * *
Re: [VOTE] Release ActiveIO 3.1.4
+1 On Thu, Apr 19, 2012 at 8:50 AM, Dejan Bosanac de...@nighttale.net wrote: Hi, 5.6.0 ActiveMQ release is getting closer. The build is stable and tests look good. However we need to release activeio before it as it contains a fix for two issues: https://issues.apache.org/jira/browse/AMQ-3679 https://issues.apache.org/jira/browse/AMQ-3587 I created a release candidate for 3.1.4 ActiveIO release that contains these fixes. Staging repo is at https://repository.apache.org/content/repositories/orgapacheactivemq-073/ Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be open for 72 hours. Here's my +1 Regards -- Dejan Bosanac Senior Software Engineer | FuseSource Corp. dej...@fusesource.com | fusesource.com skype: dejan.bosanac | twitter: @dejanb blog: http://www.nighttale.net ActiveMQ in Action: http://www.manning.com/snyder/
Re: [VOTE] Apache ActiveMQ 5.6.0
+1 On Wed, Apr 25, 2012 at 3:39 AM, Dejan Bosanac de...@nighttale.net wrote: Hi all, I've just cut a release candidate for the 5.6.0 release. This is a long-waited release with some 400 bug fixes and improvements. It also contains a lot of new features which are summarized here: https://cwiki.apache.org/confluence/display/ACTIVEMQ/New+Features+in+5.6 Could you review the artifacts and vote? The list of resolved issues is here (430 issues fixed) https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+AMQ+AND+fixVersion+%3D+12317974+AND+status+in+%28Resolved%2C+Closed%29+ORDER+BY+priority+DESC A bit better (release note) view: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210version=12317974 You can get binary distributions here: https://repository.apache.org/content/repositories/orgapacheactivemq-099/org/apache/activemq/apache-activemq/5.6.0/ Source archives are here: https://repository.apache.org/content/repositories/orgapacheactivemq-099/org/apache/activemq/activemq-parent/5.6.0/ Maven2 repository is at: https://repository.apache.org/content/repositories/orgapacheactivemq-099/ Source SVN tag: https://svn.apache.org/repos/asf/activemq/tags/activemq-5.6.0/ Please vote to approve this release [ ] +1 Release the binary as Apache ActiveMQ 5.6.0 [ ] -1 Veto the release (provide specific comments) Here's my +1 Regards -- Dejan Bosanac Senior Software Engineer | FuseSource Corp. dej...@fusesource.com | fusesource.com skype: dejan.bosanac | twitter: @dejanb blog: http://www.nighttale.net ActiveMQ in Action: http://www.manning.com/snyder/
Re: [VOTE] Release Apache.NMS.ActiveMQ 1.5.5
+1 On Mon, Apr 30, 2012 at 8:53 AM, Timothy Bish tabish...@gmail.com wrote: Hello This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.5.5. New in this release: * Sending to non-existent temp queue causes consumer to shutdown * Consumers frequently fail to reconnect after broker outage/failover. * FailoverTransport doesn't trigger a reconnect on send of a Tracked Command. * ActiveMQ.NMS hangs sometimes due to concurrency problems while accessing static IDictionary * Apache.NMS.ActiveMQ discovery protocol throwing ArgumentOutOfRangeException The binaries and source bundles for the Release Candidate can be found here: http://people.apache.org/~tabish/nms-1.5.0/ The Wiki Page for this release is here: http://activemq.apache.org/nms/apachenmsactivemq-v155.html The list of issues resolved is here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201styleName=Htmlversion=12320740 Please cast your votes (the vote will be open for 72 hrs): [ ] +1 Release the source as Apache NMS.ActiveMQ v1.5.5 [ ] -1 Veto the release (provide specific comments) Here's my +1 -- Tim Bish Sr Software Engineer | FuseSource Corp tim.b...@fusesource.com | www.fusesource.com skype: tabish121 | twitter: @tabish121 blog: http://timbish.blogspot.com/
Re: [VOTE] Release Apache Apollo 1.3
+1 On Thu, May 3, 2012 at 11:34 AM, Hiram Chirino hi...@hiramchirino.comwrote: Hi Everyone, I've deployed a 1.3 release candidate to pickup fixes since the 1.2 release. This release candidate fixes the following issues: * [APLO-160] - Reduce memory overhead of connections. * [APLO-188] - Add Access-Control-Allow-Methods and Access-Control-Allow-Headers to CORS requests * [APLO-192] - java.lang.AssertionError: Dispatch queue 'virtual-host' was not executing occurs when queue or dsub is deleted via web admin * [APLO-198] - Apollo sometimes does not send all the messages in a queue * [APLO-193] - Support filtering outgoing messages * [APLO-196] - Allow protocol filters to drop a messages The release candidate has been staged to nexus under: https://repository.apache.org/content/repositories/orgapacheactivemq-029/ Source code distros can be found at: https://repository.apache.org/content/repositories/orgapacheactivemq-029/org/apache/activemq/apollo-project/1.3/ Binary distros can be found at: https://repository.apache.org/content/repositories/orgapacheactivemq-029/org/apache/activemq/apache-apollo/1.3/ The build was tagged at: http://svn.apache.org/repos/asf/activemq/activemq-apollo/tags/apollo-project-1.3/ The project website for that version has been staged to: http://activemq.apache.org/apollo/versions/1.3/website/index.html Please vote to approve this release [ ] +1 Release Apache Apollo 1.3 [ ] -1 Veto the release (provide specific comments) As usual, the vote will be open for at least 72 hours. Here's my +1 -- ** *Hiram Chirino* *Software Fellow | FuseSource Corp.* *chir...@fusesource.com | fusesource.com* *skype: hiramchirino | twitter: @hiramchirino http://twitter.com/hiramchirino * *blog: Hiram Chirino's Bit Mojo http://hiramchirino.com/blog/* * * * *
Re: [VOTE] Release Apache.NMS API v1.5.1
+1 On Mon, Jul 2, 2012 at 2:52 PM, Timothy Bish tabish...@gmail.com wrote: Hello This is a call for a vote on the release of the Apache.NMS API v1.5.1. This package contains the API for the various Apache.NMS clients along with utility classes and unit test cases against the abstract NMS API. Changes in this version include: * Fix a marshaling bug in the Message properties class that caused the marshaled properties to be much larger than necessary due to padding of the buffer. The binaries and source bundles for the Release Candidate can be found here: http://people.apache.org/~tabish/nms-1.5.0/ The Wiki Page for this release is here: http://activemq.apache.org/nms/apachenms-api-v151.html Please cast your votes (the vote will be open for 72 hrs): [ ] +1 Release the source as Apache NMS API 1.5.1 [ ] -1 Veto the release (provide specific comments) Here's my +1 Regards, -- Tim Bish Sr Software Engineer | FuseSource Corp tim.b...@fusesource.com | www.fusesource.com skype: tabish121 | twitter: @tabish121 blog: http://timbish.blogspot.com/
Re: Moving slow tests into a build profile.
+1 for 402. On Thu, Jul 26, 2012 at 12:10 AM, Rob Davies rajdav...@gmail.com wrote: Sounds good to me - would also prefer more test methods run too (402) On 26 Jul 2012, at 04:57, Hiram Chirino hi...@hiramchirino.com wrote: Hi folks, I don't know about you guys but I'd rather have the default developer build finish in some sort of reasonable time. I took the build output of one of CI builds and figured out how much time is spent on running the tests. It came out to 8.03 hours. Then sorted all the tests and tried to figure out how many tests I would need to disable to spend at most 30 min. These are my results: If you sort by total test time, then you only have to disable 263 of the test classes and it ends up running 1824 test methods. If you sort by 'test time/test methods' then you have to disable 402 test classes but it ends up running 3026 test methods out of a total of 4777 methods. I would like to move the 'slow' tests off to it's own builds profile. The question is which tests do I pick to disable. Should I disable the 263 or the 402. I'm leaning towards the 402 since you end up running more test methods. Once we do have the slow list checked into a pom, perhaps folks can try to optimize those test so that we can bring them back to the standard build. WDYT? -- ** *Hiram Chirino* *Software Fellow | FuseSource Corp.* *chir...@fusesource.com | fusesource.com* *skype: hiramchirino | twitter: @hiramchirino http://twitter.com/hiramchirino * *blog: Hiram Chirino's Bit Mojo http://hiramchirino.com/blog/* * * * *
Re: [VOTE] Release Apache.NMS.Stomp 1.5.3
+1 On Mon, Aug 27, 2012 at 1:05 PM, Timothy Bish tabish...@gmail.com wrote: Hello This is a call for a vote on the release of Apache.NMS.Stomp v1.5.3. New in this release: * This release focuses on stability fixes for issues found since the v1.5.2 release. The release should work much better with the Apollo broker. The binaries and source bundles for the Release Candidate can be found here: http://people.apache.org/~tabish/nms-1.5.0/ The Wiki Page for this release is here: http://activemq.apache.org/nms/apachenmsstomp-v153.html The list of issues resolved is here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201styleName=Htmlversion=12319084 Please cast your votes (the vote will be open for 72 hrs): [ ] +1 Release the source as Apache NMS.Stomp v1.5.3 [ ] -1 Veto the release (provide specific comments) Here's my +1 Regards -- Tim Bish Sr Software Engineer | FuseSource Corp tim.b...@fusesource.com | www.fusesource.com skype: tabish121 | twitter: @tabish121 blog: http://timbish.blogspot.com/
Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2
+1 On Thu, Jun 5, 2014 at 7:08 AM, Dejan Bosanac de...@nighttale.net wrote: Hi folks, I've just cut a second release candidate for the 5.10.0 release. This release has 232 bug fixes and improvements. Could you review the artifacts and vote? The list of resolved issues is here: https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20fixVersion%20%3D%205.10.0%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC You can get binary distributions here: https://repository.apache.org/content/repositories/orgapacheactivemq-1007/org/apache/activemq/apache-activemq/5.10.0/ Source archives are here: https://repository.apache.org/content/repositories/orgapacheactivemq-1007/org/apache/activemq/activemq-parent/5.10.0/ Maven2 repository is at: https://repository.apache.org/content/repositories/orgapacheactivemq-1007/ Source tag: https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=58dd93e42e7405768fd89154ff94b45ac71f151f Please vote to approve this release [ ] +1 Release the binary as Apache ActiveMQ 5.10.0 [ ] -1 Veto the release (provide specific comments) Here's my +1 Regards -- Dejan Bosanac -- Red Hat, Inc. FuseSource is now part of Red Hat dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/
Re: {VOTE] Release Apache.NMS.ActiveMQ 1.6.3
+1 On Wed, Jul 16, 2014 at 3:34 PM, Timothy Bish tabish...@gmail.com wrote: Hello This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.6.3 This is a bug fix only release focusing on some issues with Consumers in local transacted sessions and an update to the ZLib library to fix some error when uncompressing messages of a certain size. The binaries and source bundles for the Release Candidate can be found here: http://people.apache.org/~tabish/nms-1.6.0 The Wiki Page for this release is here: http://activemq.apache.org/nms/apachenmsactivemq-v163.html The list of issues resolved is here: https://issues.apache.org/jira/secure/ReleaseNote.jspa? projectId=12311201version=12325840 Please cast your votes (the vote will be open for 72 hrs): [ ] +1 Release the source as Apache NMS.ActiveMQ v1.6.3 [ ] -1 Veto the release (provide specific comments) Here's my +1 Regards -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.redhat.com skype: tabish121 | twitter: @tabish121 blog: http://timbish.blogspot.com/
Re: {VOTE] Release Apache.NMS.ActiveMQ 1.6.4
+1 On Mon, Sep 8, 2014 at 7:43 AM, Timothy Bish tabish...@gmail.com wrote: Hello This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.6.4 This is a bug fix only release focusing on some issues with Consumers in local transacted sessions where messages were getting marked as duplicates in error after failover and some other edge cases that could lead to a missed redelivery. The binaries and source bundles for the Release Candidate can be found here: http://people.apache.org/~tabish/nms-1.6.0 The Wiki Page for this release is here: http://activemq.apache.org/nms/apachenmsactivemq-v164.html The list of issues resolved is here: https://issues.apache.org/jira/secure/ReleaseNote.jspa? projectId=12311201version=12327446 Please cast your votes (the vote will be open for 72 hrs): [ ] +1 Release the source as Apache NMS.ActiveMQ v1.6.4 [ ] -1 Veto the release (provide specific comments) Here's my +1 Regards -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.redhat.com skype: tabish121 | twitter: @tabish121 blog: http://timbish.blogspot.com/
Re: [VOTE] Accept hornetq code grant and active committers
+1 On Wed, Sep 24, 2014 at 8:44 AM, Gary Tully gary.tu...@gmail.com wrote: we need to formally vote to: 1) accept the code grant from RedHat for hornetq[1] 2) invite the active core committers (Clebert Suconic, Andy Taylor, Justin Bertram, Youg Hao Gao, Martyn Taylor) from hornetq to become activemq committers. For background, the dev thread with the original discussion is at [2] Please vote, adoption by lazy consensus is acceptable but not recommended. [ ] +1 - Accept hornetq code grant and new active committers [ ] -1 - Don't accept the code grant and/or new activemq committers because This vote will be open for 72 hours. here is my +1 Thank you, Gary. [1] http://incubator.apache.org/ip-clearance/hornetq.html [2] http://mail-archives.apache.org/mod_mbox/activemq-dev/201407.mbox/% 3ccakf+bsovr7hvn-rmykb3pf6hogjx7nujwzt_nh8myc4usrb...@mail.gmail.com%3E
Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)
+1 On Mon, Feb 2, 2015, 8:11 AM Hadrian Zbarcea hzbar...@gmail.com wrote: +1 (binding) * Sigs ok * Legal ok (almost) - a bunch of Copyright notices pointing to 2014 or 2013 (need to cleanup) * Builds from source ok (almost) There is one consistent failure in activemq-karaf-itest, however test does pass when ran individually. No product defect, but should be addressed. ActiveMQAMQPBrokerFeatureTestActiveMQBrokerFeatureTest.test:66- AbstractJmsFeatureTest.produceMessage:67-getConnection:53 » ClassNotFound All in all, quite impressive. Very solid release, awesome work. Thanks Gary, Hadrian On 01/30/2015 09:00 AM, Gary Tully wrote: Hi folks, I've just cut a third release candidate for the long-awaited 5.11.0 release. This release has more than 120 bug fixes and improvements. -note- this candidate includes the fix for the 'reliably' broken test case from rc2 however there can be no expectation of a 'reliable' full test run from mvn install. I have raised https://issues.apache.org/jira/browse/AMQ-5552 to address that. I think a resolution to that issue would address all of the disapproving commentary on the rc2 vote. If you voted -1 last time round, please chime in on AMQ-5552. -end note- Could you please review the artifacts and vote? The list of resolved issues is here: https://issues.apache.org/jira/secure/ReleaseNote.jspa? projectId=12311210version=12324951 You can get binary distributions here: https://repository.apache.org/content/repositories/ orgapacheactivemq-1016/org/apache/activemq/apache-activemq/5.11.0/ Source archives are here: https://repository.apache.org/content/repositories/ orgapacheactivemq-1016/org/apache/activemq/activemq-parent/5.11.0/ Maven2 repository is at: https://repository.apache.org/content/repositories/ orgapacheactivemq-1016/ Source tag: https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h= 66bd5da9405765ddbc950b4f1c5a6ef6195207e5 The vote will remain open for 72 hours. [ ] +1 approve the release as Apache ActiveMQ 5.11.0 [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards, Gary.
Re: {VOTE] Release Apache.NMS.ActiveMQ 1.6.5
+1 On Mon, Feb 2, 2015, 8:33 AM Timothy Bish tabish...@gmail.com wrote: Hello This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.6.5 This is a small bugfix release that addresses an issue in the OpenWire support around tight marshalling of data. Also a fix for message consumers that can wrongly mark messages as redelivered was added. The binaries and source bundles for the Release Candidate can be found here: http://people.apache.org/~tabish/nms-1.6.0 The Wiki Page for this release is here: http://activemq.apache.org/nms/apachenmsactivemq-v165.html The list of issues resolved is here: https://issues.apache.org/jira/secure/ReleaseNote.jspa? projectId=12311201version=12329150 Please cast your votes (the vote will be open for 72 hrs): [ ] +1 Release the source as Apache NMS.ActiveMQ v1.6.5 [ ] -1 (provide specific comments) Here's my +1 -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.redhat.com skype: tabish121 | twitter: @tabish121 blog: http://timbish.blogspot.com/
Re: [VOTE] Release Apache ActiveMQ 5.10.1 (3rd attempt)
+1 On Thu, Jan 15, 2015, 11:04 PM Claus Ibsen claus.ib...@gmail.com wrote: Hi I gave the RC a test spin with latest Camel source code. And the spring XSD schema 5.10.1 is included. +1 On Thu, Jan 15, 2015 at 6:10 PM, artnaseef a...@artnaseef.com wrote: The release candidate for the activemq 5.10.1 release is now built and ready for a vote. This release comes with 34 fixes and 1 administrative jira entry. Please see the list of jira entries here: https://issues.apache.org/jira/issues/?jql=fixVersion% 20%3D%205.10.1%20AND%20project%20%3D%20AMQ You can get binary distributions here: https://repository.apache.org/content/repositories/ orgapacheactivemq-1013/org/apache/activemq/apache-activemq/5.10.1/ Source archives are here: https://repository.apache.org/content/repositories/ orgapacheactivemq-1013/org/apache/activemq/activemq-parent/5.10.1/ Maven2 repository is here: https://repository.apache.org/content/repositories/ orgapacheactivemq-1013/ Source tag: https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h= 8938d14d434447193b02ba635606aa0fb7a80353 NOTE: I used Hadrian's prior thread as a template (thank you Hadrian). -- View this message in context: http://activemq.2283324.n4. nabble.com/VOTE-Release-Apache-ActiveMQ-5-10-1-3rd-attempt-tp4689959.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8 http://hawt.io/fabric8: http://fabric8.io/
Re: [DISCUSS] Have every committer on the PMC by default
I don't think every committer should be on the PMC by default. Not all may want that responsibility, and may not be ready for it, either. Lowering the bar to entry may be useful, but this seems too low. On Thu, Jan 29, 2015, 7:36 AM Hadrian Zbarcea hzbar...@gmail.com wrote: They can indicate the same by doing whatever they want to do, nobody stops them to self elect and do whatever they like, scratch an itch. They prove that they understand the ASF values and they get voted in. I am not ok with providing blanket binding votes in this community where proper mentorship has been a problem. I do encourage however any committer to be proactive and do all the management he's interested in. I encourage any contributor to keep contributing, improve their skills, and *their* project (activemq) and become, if they want, committers (speaking of which, doesn't necessarily need to be only code, I got a lot of complaints lately about documentation). They all got my full support. -1 (binding) Hadrian On 01/29/2015 08:42 AM, Gary Tully wrote: In that way, committers that are interested in project management duties can indicate same with their votes. Effectively self elect to step up to the task. What is the down side?
Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)
+1 On Fri, Jan 30, 2015, 10:34 PM Claus Ibsen claus.ib...@gmail.com wrote: Hi +1 Tested against Camel in Action source code also. On Fri, Jan 30, 2015 at 3:00 PM, Gary Tully gary.tu...@gmail.com wrote: Hi folks, I've just cut a third release candidate for the long-awaited 5.11.0 release. This release has more than 120 bug fixes and improvements. -note- this candidate includes the fix for the 'reliably' broken test case from rc2 however there can be no expectation of a 'reliable' full test run from mvn install. I have raised https://issues.apache.org/jira/browse/AMQ-5552 to address that. I think a resolution to that issue would address all of the disapproving commentary on the rc2 vote. If you voted -1 last time round, please chime in on AMQ-5552. -end note- Could you please review the artifacts and vote? The list of resolved issues is here: https://issues.apache.org/jira/secure/ReleaseNote.jspa? projectId=12311210version=12324951 You can get binary distributions here: https://repository.apache.org/content/repositories/ orgapacheactivemq-1016/org/apache/activemq/apache-activemq/5.11.0/ Source archives are here: https://repository.apache.org/content/repositories/ orgapacheactivemq-1016/org/apache/activemq/activemq-parent/5.11.0/ Maven2 repository is at: https://repository.apache.org/content/repositories/ orgapacheactivemq-1016/ Source tag: https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h= 66bd5da9405765ddbc950b4f1c5a6ef6195207e5 The vote will remain open for 72 hours. [ ] +1 approve the release as Apache ActiveMQ 5.11.0 [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards, Gary. -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8 http://hawt.io/fabric8: http://fabric8.io/
Re: [VOTE] Apache ActiveMQ 5.11.0
+1 On Mon, Jan 26, 2015, 1:03 PM Gary Tully gary.tu...@gmail.com wrote: Hi folks, I've just cut a second release candidate for the long-awaited 5.11.0 release. This release has more than 120 bug fixes and improvements. Could you review the artifacts and vote? Especially, it would be great if you could test the unix shell script and make sure there's no any regressions on the platform you're using. The list of resolved issues is here: https://issues.apache.org/jira/secure/ReleaseNote.jspa? projectId=12311210version=12324951 You can get binary distributions here: https://repository.apache.org/content/repositories/ orgapacheactivemq-1014/org/apache/activemq/apache-activemq/5.11.0/ Source archives are here: https://repository.apache.org/content/repositories/ orgapacheactivemq-1014/org/apache/activemq/activemq-parent/5.11.0/ Maven2 repository is at: https://repository.apache.org/content/repositories/orgapacheactivemq-1014/ Source tag: https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h= f6eb86ee31640427d0f953847f38fcf81a71f9e1 The vote will remain open for 72 hours. [ ] +1 Release the binary as Apache ActiveMQ 5.11.0 [ ] -1 Veto the release (provide specific comments) Here's my +1 Regards Gary
Re: [DISCUSS] Renaming trunk to master
I don't really know the conventions of git, but are the branches still called branches, or are they servants? Trunk/branches is a consistent metaphor. Master/branches is mixing metaphors. On Mon, Jan 5, 2015, 1:52 PM Timothy Bish tabish...@gmail.com wrote: +1 On 01/05/2015 01:27 PM, Hadrian Zbarcea wrote: It's a bit confusing, a leftover from the svn days. I think the rename was supposed to happen but it was somehow overlooked. Any objection to rename? Hadrian -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.redhat.com skype: tabish121 | twitter: @tabish121 blog: http://timbish.blogspot.com/
Re: {VOTE] Release Apache.NMS.ActiveMQ 1.7.0
+1 On Mon, Jan 12, 2015, 6:47 AM Timothy Bish tabish...@gmail.com wrote: Hello This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.7.0 This is first release of the Apache.NMS.ActiveMQ v1.7.x line. This release incorporates many fixes and improvements along with updates to the .NET compression library used to resolve some edge cases that can occur if a message compresses to a specific size and compliance with the v1.7.0 NMS API has been added. The binaries and source bundles for the Release Candidate can be found here: http://people.apache.org/~tabish/nms-1.7.x The Wiki Page for this release is here: http://activemq.apache.org/nms/apachenmsactivemq-v170.html The list of issues resolved is here: https://issues.apache.org/jira/secure/ReleaseNote.jspa? projectId=12311201version=12325350 Please cast your votes (the vote will be open for 72 hrs): [ ] +1 Release the source as Apache NMS.ActiveMQ v1.7.0 [ ] -1 (provide specific comments) Here's my +1 -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.redhat.com skype: tabish121 | twitter: @tabish121 blog: http://timbish.blogspot.com/
Re: [VOTE] Release Apache.NMS API 1.7.0
+1 On Mon, Jan 5, 2015, 7:00 AM Timothy Bish tabish...@gmail.com wrote: Hello This is a call for a vote on the release of the Apache.NMS API v1.7.0. This package contains the API for the various Apache.NMS client along with utility classes and unit test cases against the abstract NMS API. This version of the API will be the basis for the next set of NMS client releases including Apache.NMS.ActiveMQ and Apache.NMS.Stomp etc. Changes in this version include: * Added IDisposable as a base of IDestination. * Added some improvements to the Unit tests framework. * Added some new provider names (AMQP and MQTT) to allow for future clients. The binaries and source bundles for the Release Candidate can be found here: [ http://people.apache.org/~tabish/nms-1.7.x ] The Wiki Page for this release is here: [ http://activemq.apache.org/nms/apachenms-api-v170.html ] Please cast your votes (the vote will be open for 72 hrs): [ ] +1 Release the source as Apache NMS API 1.7.0 [ ] -1 (provide specific comments) Here's my +1 Regards, Tim -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.redhat.com skype: tabish121 | twitter: @tabish121 blog: http://timbish.blogspot.com/
Re: [VOTE] Apache Artemis 1.0.0 (RC2)
Another reason for not releasing this build: the destinations are not automatically created. Server throws *ActiveMQNonExistentQueueException *when trying to create a destination. Is this a configurable feature? If so, it should be set to the standard ActiveMQ behavior by default (i.e., auto-create destinations). Here's the exception that gets thrown: ERROR [org.apache.activemq.artemis.core.server] error decoding: ActiveMQNonExistentQueueException[errorType=QUEUE_DOES_NOT_EXIST message=AMQ119017: Queue jms.queue.TEST.AsyncConsumeTest.2df14c0d-4e0c-4d74-91ab-8abbd3ba02ea does not exist] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.destroyQueue(ActiveMQServerImpl.java:1401) [artemis-server-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.destroyQueue(ActiveMQServerImpl.java:1390) [artemis-server-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.destroyQueue(ActiveMQServerImpl.java:1380) [artemis-server-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.protocol.openwire.OpenWireProtocolManager.deleteQueue(OpenWireProtocolManager.java:689) [artemis-openwire-protocol-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.protocol.openwire.OpenWireConnection.processRemoveDestination(OpenWireConnection.java:1641) [artemis-openwire-protocol-1.0.0.jar:1.0.0] at org.apache.activemq.command.DestinationInfo.visit(DestinationInfo.java:124) [activemq-client-5.10.0.jar:5.10.0] at org.apache.activemq.artemis.core.protocol.openwire.OpenWireConnection.bufferReceived(OpenWireConnection.java:271) [artemis-openwire-protocol-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:694) [artemis-server-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:73) [artemis-core-client-1.0.0.jar:1.0.0] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:332) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:318) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:787) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:125) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:507) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:464) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:378) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:350) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116) [netty-all-4.0.20.Final.jar:4.0.20.Final] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_20] On Thu, May 14, 2015 at 8:05 AM, Jim Gomes e.se...@gmail.com wrote: -1 Two reasons: 1. The default configuration of localhost for the broker does not allow connections from off-machine. For some reason, socket connections are refused from non-local clients. I had to change the broker.xml config to use the machine's actual IP address, and then non-local clients could connect. 2. The basic NMS OpenWire client fails to connect at all. It is getting unknown response IDs from the broker. I don't think the OpenWire protocol is being negotiated correctly. I am running with the latest NMS trunk version (1.8.0). On Wed, May 13, 2015 at 10:12 AM, Martyn Taylor mtay...@redhat.com wrote: Hello all. I've cut a second release candidate of Apache Artemis 1.0.0 addressing the initial RC feedback from community members. This is a first release of the Artemis project with protocol support for AMQP, STOMP, CORE, HORNETQ and OPENWIRE. The release notes can be found here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920version=12328953 The binary distributions can be found here: https://repository.apache.org/content/repositories/orgapacheactivemq-1051/org/apache/activemq/apache-artemis/1.0.0/ The source archives can be found here: https://repository.apache.org/content/repositories/orgapacheactivemq-1051/org/apache/activemq/apache-artemis/1.0.0/ The Maven repository is here: https://repository.apache.org/content/repositories/orgapacheactivemq-1051/ The source tag: https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;a=tag;h=refs/tags/1.0.0 The project website for that version has been staged to: http
Re: [VOTE] Apache Artemis 1.0.0 (RC2)
The resource clean up code for dead clients doesn't seem to work reliably. Probably not a show-stopper for a beta release, but definitely needs to be cleaned up for production. Basically, when Artemis detected a dead client (it stopped responding because I hit a breakpoint in my debugger), it tried to clean it up, but failed. The result is that I can no longer connect a new client from that client machine, because the broker thinks I already have a connection. This is after I killed my client app and restarted it. I'll log a bug for this one, but here's the server log: WARN [org.apache.activemq.artemis.core.server] AMQ222067: Connection failure has been detected: AMQ119014: Did not receive data from /xxx.xxx.xxx.xxx:53516. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] WARN [org.apache.activemq.artemis.core.server] AMQ222061: Client connection failed, clearing up resources for session ID:testmachine-63273-635671999039695375-1:0:-1 WARN [org.apache.activemq.artemis.core.server] AMQ222107: Cleared up resources for session ID:testmachine-63273-635671999039695375-1:0:-1 WARN [org.apache.activemq.artemis.core.server] AMQ222061: Client connection failed, clearing up resources for session ID:testmachine-63273-635671999039695375-1:0:1 WARN [org.apache.activemq.artemis.core.server] AMQ222107: Cleared up resources for session ID:testmachine-63273-635671999039695375-1:0:1 *INFO [org.apache.activemq.artemis.core.server] AMQ221021: failed to remove connection* Attempting to run a fresh client gets the following return exception on the client: Apache.NMS.Test.AsyncConsumeTest.TestAsynchronousConsume(Persistent): Apache.NMS.InvalidClientIDException : Broker: mybroker - Client: ID:AsyncConsumeTest:1:2 already connected from /xxx.xxx.xxx.xxx:53516 On Thu, May 14, 2015 at 11:37 AM, Jim Gomes e.se...@gmail.com wrote: Another reason for not releasing this build: the destinations are not automatically created. Server throws *ActiveMQNonExistentQueueException *when trying to create a destination. Is this a configurable feature? If so, it should be set to the standard ActiveMQ behavior by default (i.e., auto-create destinations). Here's the exception that gets thrown: ERROR [org.apache.activemq.artemis.core.server] error decoding: ActiveMQNonExistentQueueException[errorType=QUEUE_DOES_NOT_EXIST message=AMQ119017: Queue jms.queue.TEST.AsyncConsumeTest.2df14c0d-4e0c-4d74-91ab-8abbd3ba02ea does not exist] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.destroyQueue(ActiveMQServerImpl.java:1401) [artemis-server-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.destroyQueue(ActiveMQServerImpl.java:1390) [artemis-server-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.destroyQueue(ActiveMQServerImpl.java:1380) [artemis-server-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.protocol.openwire.OpenWireProtocolManager.deleteQueue(OpenWireProtocolManager.java:689) [artemis-openwire-protocol-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.protocol.openwire.OpenWireConnection.processRemoveDestination(OpenWireConnection.java:1641) [artemis-openwire-protocol-1.0.0.jar:1.0.0] at org.apache.activemq.command.DestinationInfo.visit(DestinationInfo.java:124) [activemq-client-5.10.0.jar:5.10.0] at org.apache.activemq.artemis.core.protocol.openwire.OpenWireConnection.bufferReceived(OpenWireConnection.java:271) [artemis-openwire-protocol-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:694) [artemis-server-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:73) [artemis-core-client-1.0.0.jar:1.0.0] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:332) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:318) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:787) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:125) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:507) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized
Re: [VOTE] Apache Artemis 1.0.0 (RC2)
If it was done on purpose for security reasons, that's cool. However, it is
doubtful this is the way any broker will ever be run for real. The whole
purpose of a broker is to integrate disparate systems. It's like having a
web server start up without the ability to server web pages by default.
Kind of silly.
Anyway, I will log the bug with the NMS clients, and I do think the release
should be held up because of this problem. It's a show-stopper for NMS
clients. Here's the server exception being thrown:
ERROR [org.apache.activemq.artemis.core.server] error decoding:
java.lang.IllegalStateException: Cannot handle command: ConsumerControl
{commandId = 0, responseRequired = false, consumerId =
ID:testmachine-58728-635671869132994591-1:0:44:1, close = false, stop =
false, start = false, flush = false, prefetch = 32766, destination =
topic://UnitTest.Status}
at
org.apache.activemq.artemis.core.protocol.openwire.OpenWireProtocolManager.handleCommand(OpenWireProtocolManager.java:236)
[artemis-openwire-protocol-1.0.0.jar:1.0.0]
at
org.apache.activemq.artemis.core.protocol.openwire.OpenWireConnection.bufferReceived(OpenWireConnection.java:315)
[artemis-openwire-protocol-1.0.0.jar:1.0.0]
at
org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:694)
[artemis-server-1.0.0.jar:1.0.0]
at
org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:73)
[artemis-core-client-1.0.0.jar:1.0.0]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:332)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:318)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:787)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:125)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:507)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:464)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:378)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:350)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_20]
On Thu, May 14, 2015 at 8:20 AM, Justin Bertram jbert...@apache.com wrote:
IMO the broker correctly binds to localhost only and does not, by default,
allow connections from remote machines. This is a simple security/sanity
measure to prevent access to default (i.e. unsecured) instances.
The merit of this configuration is obviously up for debate, but it's worth
noting it was done on purpose.
Justin
- Original Message -
From: Jim Gomes e.se...@gmail.com
To: ActiveMQ Dev dev@activemq.apache.org
Sent: Thursday, May 14, 2015 10:05:55 AM
Subject: Re: [VOTE] Apache Artemis 1.0.0 (RC2)
-1
Two reasons:
1. The default configuration of localhost for the broker does not allow
connections from off-machine. For some reason, socket connections are
refused from non-local clients. I had to change the broker.xml config to
use the machine's actual IP address, and then non-local clients could
connect.
2. The basic NMS OpenWire client fails to connect at all. It is getting
unknown response IDs from the broker. I don't think the OpenWire protocol
is being negotiated correctly. I am running with the latest NMS trunk
version (1.8.0).
On Wed, May 13, 2015 at 10:12 AM, Martyn Taylor mtay...@redhat.com
wrote:
Hello all.
I've cut a second release candidate of Apache Artemis 1.0.0 addressing
the
initial RC feedback from community members.
This is a first release of the Artemis project with protocol support for
AMQP, STOMP, CORE, HORNETQ and OPENWIRE.
The release notes can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920version=12328953
The binary distributions can be found here:
https://repository.apache.org/content/repositories/orgapacheactivemq-1051/org/apache/activemq/apache-artemis/1.0.0/
The source archives can be found here:
https://repository.apache.org/content/repositories/orgapacheactivemq-1051/org/apache/activemq/apache-artemis/1.0.0/
The Maven repository is here:
https://repository.apache.org/content/repositories/orgapacheactivemq-1051/
The source tag:
https://git-wip-us.apache.org/repos/asf
Re: [VOTE] Apache Artemis 1.0.0 (RC2)
Thanks, Clebert!
And thanks for the quick update on the default bindings.
On Thu, May 14, 2015 at 8:59 AM, Clebert Suconic clebert.suco...@gmail.com
wrote:
here is the JIRA with the current progress on the renames:
https://issues.apache.org/jira/browse/INFRA-9543
On Thu, May 14, 2015 at 11:41 AM, Jim Gomes e.se...@gmail.com wrote:
Logged bug ACTIVEMQ6-106.
And at the risk of opening a big can of worms, do we need to have
Infrastructure rename the JIRA database from ACTIVEMQ6 to AMQARTEMIS or
something? I was very hesitant to enter a bug there, and had to
double-check that it was indeed the Artemis bug tracker.
On Thu, May 14, 2015 at 8:28 AM, Jim Gomes e.se...@gmail.com wrote:
If it was done on purpose for security reasons, that's cool. However, it
is doubtful this is the way any broker will ever be run for real. The
whole
purpose of a broker is to integrate disparate systems. It's like having
a
web server start up without the ability to server web pages by default.
Kind of silly.
Anyway, I will log the bug with the NMS clients, and I do think the
release should be held up because of this problem. It's a show-stopper
for
NMS clients. Here's the server exception being thrown:
ERROR [org.apache.activemq.artemis.core.server] error decoding:
java.lang.IllegalStateException: Cannot handle command: ConsumerControl
{commandId = 0, responseRequired = false, consumerId =
ID:testmachine-58728-635671869132994591-1:0:44:1, close = false, stop =
false, start = false, flush = false, prefetch = 32766, destination =
topic://UnitTest.Status}
at
org.apache.activemq.artemis.core.protocol.openwire.OpenWireProtocolManager.handleCommand(OpenWireProtocolManager.java:236)
[artemis-openwire-protocol-1.0.0.jar:1.0.0]
at
org.apache.activemq.artemis.core.protocol.openwire.OpenWireConnection.bufferReceived(OpenWireConnection.java:315)
[artemis-openwire-protocol-1.0.0.jar:1.0.0]
at
org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:694)
[artemis-server-1.0.0.jar:1.0.0]
at
org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:73)
[artemis-core-client-1.0.0.jar:1.0.0]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:332)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:318)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:787)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:125)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:507)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:464)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:378)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:350)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_20]
On Thu, May 14, 2015 at 8:20 AM, Justin Bertram jbert...@apache.com
wrote:
IMO the broker correctly binds to localhost only and does not, by
default, allow connections from remote machines. This is a simple
security/sanity measure to prevent access to default (i.e. unsecured)
instances.
The merit of this configuration is obviously up for debate, but it's
worth noting it was done on purpose.
Justin
- Original Message -
From: Jim Gomes e.se...@gmail.com
To: ActiveMQ Dev dev@activemq.apache.org
Sent: Thursday, May 14, 2015 10:05:55 AM
Subject: Re: [VOTE] Apache Artemis 1.0.0 (RC2)
-1
Two reasons:
1. The default configuration of localhost for the broker does not allow
connections from off-machine. For some reason, socket connections are
refused from non-local clients. I had to change the broker.xml config
to
use the machine's actual IP address, and then non-local clients could
connect.
2. The basic NMS OpenWire client fails to connect at all. It is getting
unknown response IDs from the broker. I don't think the OpenWire
protocol
is being negotiated correctly. I am running with the latest NMS trunk
version (1.8.0).
On Wed, May 13, 2015 at 10:12 AM, Martyn Taylor mtay...@redhat.com
wrote:
Hello all
Re: [VOTE] Apache Artemis 1.0.0 (RC2)
-1 Two reasons: 1. The default configuration of localhost for the broker does not allow connections from off-machine. For some reason, socket connections are refused from non-local clients. I had to change the broker.xml config to use the machine's actual IP address, and then non-local clients could connect. 2. The basic NMS OpenWire client fails to connect at all. It is getting unknown response IDs from the broker. I don't think the OpenWire protocol is being negotiated correctly. I am running with the latest NMS trunk version (1.8.0). On Wed, May 13, 2015 at 10:12 AM, Martyn Taylor mtay...@redhat.com wrote: Hello all. I've cut a second release candidate of Apache Artemis 1.0.0 addressing the initial RC feedback from community members. This is a first release of the Artemis project with protocol support for AMQP, STOMP, CORE, HORNETQ and OPENWIRE. The release notes can be found here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920version=12328953 The binary distributions can be found here: https://repository.apache.org/content/repositories/orgapacheactivemq-1051/org/apache/activemq/apache-artemis/1.0.0/ The source archives can be found here: https://repository.apache.org/content/repositories/orgapacheactivemq-1051/org/apache/activemq/apache-artemis/1.0.0/ The Maven repository is here: https://repository.apache.org/content/repositories/orgapacheactivemq-1051/ The source tag: https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;a=tag;h=refs/tags/1.0.0 The project website for that version has been staged to: http://people.apache.org/~martyntaylor/ The vote will remain open for 72 hours. [ ] +1 approve the release as Apache Artemis 1.0.0 [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my (non-binding) +1 Regards Martyn
Re: [VOTE] Apache Artemis 1.0.0 (RC2)
Logged bug ACTIVEMQ6-106.
And at the risk of opening a big can of worms, do we need to have
Infrastructure rename the JIRA database from ACTIVEMQ6 to AMQARTEMIS or
something? I was very hesitant to enter a bug there, and had to
double-check that it was indeed the Artemis bug tracker.
On Thu, May 14, 2015 at 8:28 AM, Jim Gomes e.se...@gmail.com wrote:
If it was done on purpose for security reasons, that's cool. However, it
is doubtful this is the way any broker will ever be run for real. The whole
purpose of a broker is to integrate disparate systems. It's like having a
web server start up without the ability to server web pages by default.
Kind of silly.
Anyway, I will log the bug with the NMS clients, and I do think the
release should be held up because of this problem. It's a show-stopper for
NMS clients. Here's the server exception being thrown:
ERROR [org.apache.activemq.artemis.core.server] error decoding:
java.lang.IllegalStateException: Cannot handle command: ConsumerControl
{commandId = 0, responseRequired = false, consumerId =
ID:testmachine-58728-635671869132994591-1:0:44:1, close = false, stop =
false, start = false, flush = false, prefetch = 32766, destination =
topic://UnitTest.Status}
at
org.apache.activemq.artemis.core.protocol.openwire.OpenWireProtocolManager.handleCommand(OpenWireProtocolManager.java:236)
[artemis-openwire-protocol-1.0.0.jar:1.0.0]
at
org.apache.activemq.artemis.core.protocol.openwire.OpenWireConnection.bufferReceived(OpenWireConnection.java:315)
[artemis-openwire-protocol-1.0.0.jar:1.0.0]
at
org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:694)
[artemis-server-1.0.0.jar:1.0.0]
at
org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:73)
[artemis-core-client-1.0.0.jar:1.0.0]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:332)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:318)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:787)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:125)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:507)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:464)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:378)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:350)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
[netty-all-4.0.20.Final.jar:4.0.20.Final]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_20]
On Thu, May 14, 2015 at 8:20 AM, Justin Bertram jbert...@apache.com
wrote:
IMO the broker correctly binds to localhost only and does not, by
default, allow connections from remote machines. This is a simple
security/sanity measure to prevent access to default (i.e. unsecured)
instances.
The merit of this configuration is obviously up for debate, but it's
worth noting it was done on purpose.
Justin
- Original Message -
From: Jim Gomes e.se...@gmail.com
To: ActiveMQ Dev dev@activemq.apache.org
Sent: Thursday, May 14, 2015 10:05:55 AM
Subject: Re: [VOTE] Apache Artemis 1.0.0 (RC2)
-1
Two reasons:
1. The default configuration of localhost for the broker does not allow
connections from off-machine. For some reason, socket connections are
refused from non-local clients. I had to change the broker.xml config to
use the machine's actual IP address, and then non-local clients could
connect.
2. The basic NMS OpenWire client fails to connect at all. It is getting
unknown response IDs from the broker. I don't think the OpenWire protocol
is being negotiated correctly. I am running with the latest NMS trunk
version (1.8.0).
On Wed, May 13, 2015 at 10:12 AM, Martyn Taylor mtay...@redhat.com
wrote:
Hello all.
I've cut a second release candidate of Apache Artemis 1.0.0 addressing
the
initial RC feedback from community members.
This is a first release of the Artemis project with protocol support for
AMQP, STOMP, CORE, HORNETQ and OPENWIRE.
The release notes can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920version=12328953
The binary distributions can be found here:
https://repository.apache.org/content
Re: [VOTE] Apache Artemis 1.0.0 (RC2)
It's impossible to run any of the NMS unit tests with destination autocreate set to false. If Artemis is meant to be a drop-in replacement (as much as possible) for ActiveMQ, then we should match feature defaults, unless there is an definite problem that is being solved by changing the defaults. On Thu, May 14, 2015 at 11:55 AM, Andy Taylor andy.tayl...@gmail.com wrote: I think it's fine to release with auto create set to false. Remember 1.0.0 is just a starting point. We can discuss what needs changing after the release in a separate discussion. I'm sure there will be lots of differences like this but we shouldn't let them block this first release. Great job on kicking Artemis's tyres by the way Jim. On 14 May 2015 19:37, Jim Gomes e.se...@gmail.com wrote: Another reason for not releasing this build: the destinations are not automatically created. Server throws *ActiveMQNonExistentQueueException *when trying to create a destination. Is this a configurable feature? If so, it should be set to the standard ActiveMQ behavior by default (i.e., auto-create destinations). Here's the exception that gets thrown: ERROR [org.apache.activemq.artemis.core.server] error decoding: ActiveMQNonExistentQueueException[errorType=QUEUE_DOES_NOT_EXIST message=AMQ119017: Queue jms.queue.TEST.AsyncConsumeTest.2df14c0d-4e0c-4d74-91ab-8abbd3ba02ea does not exist] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.destroyQueue(ActiveMQServerImpl.java:1401) [artemis-server-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.destroyQueue(ActiveMQServerImpl.java:1390) [artemis-server-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.destroyQueue(ActiveMQServerImpl.java:1380) [artemis-server-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.protocol.openwire.OpenWireProtocolManager.deleteQueue(OpenWireProtocolManager.java:689) [artemis-openwire-protocol-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.protocol.openwire.OpenWireConnection.processRemoveDestination(OpenWireConnection.java:1641) [artemis-openwire-protocol-1.0.0.jar:1.0.0] at org.apache.activemq.command.DestinationInfo.visit(DestinationInfo.java:124) [activemq-client-5.10.0.jar:5.10.0] at org.apache.activemq.artemis.core.protocol.openwire.OpenWireConnection.bufferReceived(OpenWireConnection.java:271) [artemis-openwire-protocol-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:694) [artemis-server-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:73) [artemis-core-client-1.0.0.jar:1.0.0] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:332) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:318) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:787) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:125) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:507) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:464) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:378) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:350) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116) [netty-all-4.0.20.Final.jar:4.0.20.Final] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_20] On Thu, May 14, 2015 at 8:05 AM, Jim Gomes e.se...@gmail.com wrote: -1 Two reasons: 1. The default configuration of localhost for the broker does not allow connections from off-machine. For some reason, socket connections are refused from non-local clients. I had to change the broker.xml config to use the machine's actual IP address, and then non-local clients could connect. 2. The basic NMS OpenWire client fails to connect at all. It is getting unknown response IDs from the broker. I don't think the OpenWire protocol is being negotiated correctly. I am running with the latest NMS trunk version (1.8.0). On Wed, May 13, 2015 at 10:12 AM, Martyn Taylor mtay...@redhat.com
Re: [VOTE] Apache Artemis 1.0.0 (RC2)
Yeah, we don't have to have everything fixed, however, ACTIVEMQ6-106 is a showstopper, because consumers are getting kicked off even when the are sending KeepAlive and even when they are active. I attached a sample application to the JIRA that can reproduce the item. As far as I can tell, the destinations are getting created (at least I could send/receive messages), but it's throwing a server side exception. That can be put off as a fix for next release. On Thu, May 14, 2015 at 12:52 PM, Clebert Suconic clebert.suco...@gmail.com wrote: This is going to be the first release... and even the first with OpenWire... there certainly going to be other issues. I Think of this like a Beta... people will then have time to kick it out and raise issues... then this should be released very frequently... On Thu, May 14, 2015 at 3:29 PM, Clebert Suconic clebert.suco...@gmail.com wrote: Is that what it is? just setting auto-create to true will fix it? if that's the case... it's an easy fix? On Thu, May 14, 2015 at 3:06 PM, Andy Taylor andy.tayl...@gmail.com wrote: Agreed. But there are lots of them. Let's get 1.0.0 out and then come up with a migration path for all of them. On 14 May 2015 20:04, Jim Gomes e.se...@gmail.com wrote: It's impossible to run any of the NMS unit tests with destination autocreate set to false. If Artemis is meant to be a drop-in replacement (as much as possible) for ActiveMQ, then we should match feature defaults, unless there is an definite problem that is being solved by changing the defaults. On Thu, May 14, 2015 at 11:55 AM, Andy Taylor andy.tayl...@gmail.com wrote: I think it's fine to release with auto create set to false. Remember 1.0.0 is just a starting point. We can discuss what needs changing after the release in a separate discussion. I'm sure there will be lots of differences like this but we shouldn't let them block this first release. Great job on kicking Artemis's tyres by the way Jim. On 14 May 2015 19:37, Jim Gomes e.se...@gmail.com wrote: Another reason for not releasing this build: the destinations are not automatically created. Server throws *ActiveMQNonExistentQueueException *when trying to create a destination. Is this a configurable feature? If so, it should be set to the standard ActiveMQ behavior by default (i.e., auto-create destinations). Here's the exception that gets thrown: ERROR [org.apache.activemq.artemis.core.server] error decoding: ActiveMQNonExistentQueueException[errorType=QUEUE_DOES_NOT_EXIST message=AMQ119017: Queue jms.queue.TEST.AsyncConsumeTest.2df14c0d-4e0c-4d74-91ab-8abbd3ba02ea does not exist] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.destroyQueue(ActiveMQServerImpl.java:1401) [artemis-server-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.destroyQueue(ActiveMQServerImpl.java:1390) [artemis-server-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.destroyQueue(ActiveMQServerImpl.java:1380) [artemis-server-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.protocol.openwire.OpenWireProtocolManager.deleteQueue(OpenWireProtocolManager.java:689) [artemis-openwire-protocol-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.protocol.openwire.OpenWireConnection.processRemoveDestination(OpenWireConnection.java:1641) [artemis-openwire-protocol-1.0.0.jar:1.0.0] at org.apache.activemq.command.DestinationInfo.visit(DestinationInfo.java:124) [activemq-client-5.10.0.jar:5.10.0] at org.apache.activemq.artemis.core.protocol.openwire.OpenWireConnection.bufferReceived(OpenWireConnection.java:271) [artemis-openwire-protocol-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:694) [artemis-server-1.0.0.jar:1.0.0] at org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:73) [artemis-core-client-1.0.0.jar:1.0.0] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:332) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:318) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:787) [netty-all-4.0.20.Final.jar:4.0.20.Final] at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:125) [netty
Re: [VOTE] Pick a code name for the HornetQ code donation
+0 Have no preference for any of them, but recommend going with the fewest syllables. On Apr 14, 2015 8:43 AM, Hiram Chirino hi...@hiramchirino.com wrote: Now that we have chosen to give the HornetQ code donation a code name, it's time to pick what that code name will be. Please select from one of the following options: [a] ActiveMQ Artemis [b] ActiveMQ Luna [c] ActiveMQ Reactive Vote will be open for 72 hours. The option with the most votes will win. Regards, Hiram -- Hiram Chirino Engineering | Red Hat, Inc. hchir...@redhat.com | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino
Re: [DISCUSS] Should ActiveMQ {CodeName} Support Backward Compatibility with HornetQ...
There's a difference between should and can. Is this a short term support
via deprecated and planned obsolescence, or is it long term first class
support? I don't really know much about what the HornetQ support entails.
On Wed, Apr 15, 2015, 9:18 AM Clebert Suconic clebert.suco...@gmail.com
wrote:
I think it doesn't hurt to do it. it's only beneficial.
The concern probably started from this Pull Request:
https://github.com/apache/activemq-6/pull/205
Which we will merge it.. I will just extend the change to coupe with
old clients.
On Wed, Apr 15, 2015 at 10:53 AM, Hiram Chirino hi...@hiramchirino.com
wrote:
Yep. I think supporting old HornetQ clients should be a goal too. If
it's not too much effort will open our projects to more users which I
think is a good thing.
On Wed, Apr 15, 2015 at 11:43 AM, James Carman
ja...@carmanconsulting.com wrote:
It has come to light that some folks feel that ActiveMQ {CodeName}
should support backward compatibility with HornetQ. I don't think
this has been discussed specifically within the community yet, so I
thought I'd bring it up.
James
--
Hiram Chirino
Engineering | Red Hat, Inc.
hchir...@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino
--
Clebert Suconic
http://community.jboss.org/people/clebert.suco...@jboss.com
http://clebertsuconic.blogspot.com
Re: [DISCUSS] ActiveMQ {CodeName} Must-Have Features...
Must have:
Support for the Timestamp plugin, or (better) built-in equivalent. My usage
requires the ability to override timestamps on submitted messages to
correct for out of synch clocks between clients and server.
On Wed, Apr 15, 2015, 8:58 AM James Carman ja...@carmanconsulting.com
wrote:
In order for ActiveMQ {CodeName} to take over as the next generation
of ActiveMQ, it obviously must have some level of feature parity with
the existing ActiveMQ 5.x (or 6.x if it's released before that
transition) offering. We should come up with some level of a roadmap
together about which features are required. Thus far, the only
big-ticket items that have been addressed are:
1. The OpenWire protocol is supported
2. Auto-creation of destinations (mostly complete).
This is obviously not all of what the existing ActiveMQ is all about.
What other features are folks wanting to see in the next generation
ActiveMQ?
James
Re: [DISCUSS] Should ActiveMQ {CodeName} Support Backward Compatibility with HornetQ...
Then I would say yes, we should support them through a transition plan. It
might be helpful to lay out a time line of which version this support will
be removed. That gives fair notice to everyone involved.
From what I've seen in other messages, it seems like this support is there,
or almost there, already. Is that correct?
On Apr 15, 2015 11:20 AM, Clebert Suconic clebert.suco...@gmail.com
wrote:
I would say it's a short term for older clients being able to connect
via deprecated.
On Wed, Apr 15, 2015 at 12:37 PM, Jim Gomes jgo...@apache.org wrote:
There's a difference between should and can. Is this a short term support
via deprecated and planned obsolescence, or is it long term first class
support? I don't really know much about what the HornetQ support entails.
On Wed, Apr 15, 2015, 9:18 AM Clebert Suconic clebert.suco...@gmail.com
wrote:
I think it doesn't hurt to do it. it's only beneficial.
The concern probably started from this Pull Request:
https://github.com/apache/activemq-6/pull/205
Which we will merge it.. I will just extend the change to coupe with
old clients.
On Wed, Apr 15, 2015 at 10:53 AM, Hiram Chirino hi...@hiramchirino.com
wrote:
Yep. I think supporting old HornetQ clients should be a goal too. If
it's not too much effort will open our projects to more users which I
think is a good thing.
On Wed, Apr 15, 2015 at 11:43 AM, James Carman
ja...@carmanconsulting.com wrote:
It has come to light that some folks feel that ActiveMQ {CodeName}
should support backward compatibility with HornetQ. I don't think
this has been discussed specifically within the community yet, so I
thought I'd bring it up.
James
--
Hiram Chirino
Engineering | Red Hat, Inc.
hchir...@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino
--
Clebert Suconic
http://community.jboss.org/people/clebert.suco...@jboss.com
http://clebertsuconic.blogspot.com
--
Clebert Suconic
http://community.jboss.org/people/clebert.suco...@jboss.com
http://clebertsuconic.blogspot.com
Re: [DISCUSS] Should ActiveMQ {CodeName} Support Backward Compatibility with HornetQ...
Sounds good. Thanks for the update, Clebert! On Wed, Apr 15, 2015, 1:36 PM Clebert Suconic clebert.suco...@gmail.com wrote: It's hard to come up with a time.. it only depends on users. We need to make proper announcements at the hornetq community first and talk to users there about that. So far we are in wait mode for the first release. From what I've seen in other messages, it seems like this support is there, or almost there, already. Is that correct? There are a few places like internal properties where this would cause semantic issues, so we left those untouched. (which was the PR sent). That PR sent will break compatibility but I will follow up with something preserving compatibility without offending new clients.
Re: [DISCUSS] dev mailing list is cluttered
I'm OK with moving JIRA notices to a separate list. On Tue, Apr 7, 2015, 1:22 PM Hiram Chirino hi...@hiramchirino.com wrote: Do we need an official vote thread for these kinds of changes? Perhaps this discussion thread is good enough? On Tue, Apr 7, 2015 at 3:14 PM, James Carman ja...@carmanconsulting.com wrote: I think we need to have Hiram request this since he is the chair of the PMC. On Tuesday, April 7, 2015, James Carman ja...@carmanconsulting.com wrote: Actually the mailing lists are different https://infra.apache.org/officers/mlreq On Tuesday, April 7, 2015, Bruce Snyder bruce.sny...@gmail.com javascript:_e(%7B%7D,'cvml','bruce.sny...@gmail.com'); wrote: Anything that requires assistance from the Infra team is accomplished by creating a JIRA issue. Just create a new issue in JIRA ( https://issues.apache.org/jira/secure/Dashboard.jspa) and select the Infrastructure project. Bruce On Tue, Apr 7, 2015 at 12:36 PM, artnaseef a...@artnaseef.com wrote: Hey Bruce - I would like to learn the process here. Can you help me? Was the request made simply by creating a Jira entry? -- View this message in context: http://activemq.2283324.n4.nabble.com/DISCUSS-dev- mailing-list-is-cluttered-tp4694420p4694448.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- perl -e 'print unpack(u30,D0G)U8V4\@4VYY95R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' ActiveMQ in Action: http://bit.ly/2je6cQ Blog: http://bruceblog.org/ Twitter: http://twitter.com/brucesnyder -- Hiram Chirino Engineering | Red Hat, Inc. hchir...@redhat.com | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino
Re: [DISCUSS] dev mailing list is cluttered
+1 for lazy consensus. On Tue, Apr 7, 2015, 1:44 PM James Carman ja...@carmanconsulting.com wrote: Sounds good. There's no reason to rush this by any stretch of the imagination. Lazy consensus is just fine for this sort of thing, I'd think. On Tue, Apr 7, 2015 at 4:36 PM, Hiram Chirino hi...@hiramchirino.com wrote: How about this.. Lets request the change 72 hours after this thread was started. So 3 days - 5 hours :) That way, we lets folks in different time zones get a chance to object if they want. After that we can call it lazy consensus and be done with it. On Tue, Apr 7, 2015 at 4:30 PM, Bruce Snyder bruce.sny...@gmail.com wrote: I don't think we need a vote, but I won't stand in the way of one. Bruce On Tue, Apr 7, 2015 at 2:26 PM, James Carman ja...@carmanconsulting.com wrote: Unless anyone objects, I don't think we need an official VOTE. Thus far, it appears we have consensus. Anyone? Anyone? Bueller? On Tue, Apr 7, 2015 at 4:21 PM, Hiram Chirino hi...@hiramchirino.com wrote: Do we need an official vote thread for these kinds of changes? Perhaps this discussion thread is good enough? On Tue, Apr 7, 2015 at 3:14 PM, James Carman ja...@carmanconsulting.com wrote: I think we need to have Hiram request this since he is the chair of the PMC. On Tuesday, April 7, 2015, James Carman ja...@carmanconsulting.com wrote: Actually the mailing lists are different https://infra.apache.org/officers/mlreq On Tuesday, April 7, 2015, Bruce Snyder bruce.sny...@gmail.com javascript:_e(%7B%7D,'cvml','bruce.sny...@gmail.com'); wrote: Anything that requires assistance from the Infra team is accomplished by creating a JIRA issue. Just create a new issue in JIRA ( https://issues.apache.org/jira/secure/Dashboard.jspa) and select the Infrastructure project. Bruce On Tue, Apr 7, 2015 at 12:36 PM, artnaseef a...@artnaseef.com wrote: Hey Bruce - I would like to learn the process here. Can you help me? Was the request made simply by creating a Jira entry? -- View this message in context: http://activemq.2283324.n4.nabble.com/DISCUSS-dev- mailing-list-is-cluttered-tp4694420p4694448.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- perl -e 'print unpack(u30,D0G)U8V4\@4VYY95R\F)R=6-E+G-N61ED\!G;6%I;\ YC;VT* );' ActiveMQ in Action: http://bit.ly/2je6cQ Blog: http://bruceblog.org/ Twitter: http://twitter.com/brucesnyder -- Hiram Chirino Engineering | Red Hat, Inc. hchir...@redhat.com | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino -- perl -e 'print unpack(u30,D0G)U8V4\@4VYY95R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' ActiveMQ in Action: http://bit.ly/2je6cQ Blog: http://bruceblog.org/ Twitter: http://twitter.com/brucesnyder -- Hiram Chirino Engineering | Red Hat, Inc. hchir...@redhat.com | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino
Re: [PROPOSAL] Pluggable Brokers...
I'm with Guillaume on this. From the NMS perspective, the broker already is a plugin implementation. I don't understand why it would need to go any deeper than that. NMS can talk to TIBCO or ActiveMQ brokers via one common API. The idea of pluggable brokers already exists. On Mon, Mar 30, 2015, 8:32 AM Guillaume Nodet gno...@apache.org wrote: Fwiw, the whole broker implementation looks like an implementation detail from a user point of view that uses the JMS spec... ;-) 2015-03-30 17:12 GMT+02:00 Hadrian Zbarcea hzbar...@gmail.com: +1. The blocking today it merely an implementation detail than can be addressed. Hadrian On 03/30/2015 09:23 AM, James Carman wrote: All, With all the talk over the last week or so regarding the Broker Wars, especially after reading Rob Davies' email about how the broker has been tweaked through the years to emphasize different aspects (long-term storage for instance), it occurred to me that we might be able to move past all this craziness by providing an abstraction layer above the broker and try to make them pluggable. If there really are situations where the broker needs to focus on one particular aspect of message delivery, that sounds to me like the strategy pattern. If a broker can be written in such a way that it is allowed to focus on certain aspects and maybe ignore or completely forego others, then it would seem to me that the code could be made much more straight-forward, because it doesn't have to try to be the swiss army knife, solving everyone's problems at one time. Of course, this may be just a pipe dream and there's no way to do it (admittedly I'm not terribly familiar with the code), but I thought I'd throw it out there as a possible approach. I mean, we do this sort of thing already with the persistence providers, so maybe there's an opportunity here as well. Thoughts? James
Re: [PROPOSAL] Pluggable Brokers...
I guess if this would help the ActiveMQ developer by reducing code debt and making maintenance simpler, it's a Good Thing. Pluggable architectures have a certain amount of overhead, though. I don't want to discourage interesting and new areas of architecture. The original message said the pluggable interface would be above the broker, not within it. That's what didn't make a lot of sense to me. If it's above it, then the obvious plugin interface would be the existing wire protocols: JMS via OpenWire or STOMP. If it's within the broker, where are the plugin interface points? Is that what would need to be rearchitected, and is this a significant amount of effort? I don't know enough of ActiveMQ's internals to know where the boundaries are for clean separation. On Wed, Apr 8, 2015, 12:15 AM James Carman ja...@carmanconsulting.com wrote: Pluggable *within* ActiveMQ. That is what doesn't exist. The idea is that the underlying engine could be optimized on a case-by-case basis. For instance, you may be able to streamline the implementation of a broker that doesn't require persistence at all. Right now, we have one implementation that tries to be the end-all-be-all solution for everything. On Wednesday, April 8, 2015, Jim Gomes jgo...@apache.org wrote: I'm with Guillaume on this. From the NMS perspective, the broker already is a plugin implementation. I don't understand why it would need to go any deeper than that. NMS can talk to TIBCO or ActiveMQ brokers via one common API. The idea of pluggable brokers already exists. On Mon, Mar 30, 2015, 8:32 AM Guillaume Nodet gno...@apache.org javascript:; wrote: Fwiw, the whole broker implementation looks like an implementation detail from a user point of view that uses the JMS spec... ;-) 2015-03-30 17:12 GMT+02:00 Hadrian Zbarcea hzbar...@gmail.com javascript:;: +1. The blocking today it merely an implementation detail than can be addressed. Hadrian On 03/30/2015 09:23 AM, James Carman wrote: All, With all the talk over the last week or so regarding the Broker Wars, especially after reading Rob Davies' email about how the broker has been tweaked through the years to emphasize different aspects (long-term storage for instance), it occurred to me that we might be able to move past all this craziness by providing an abstraction layer above the broker and try to make them pluggable. If there really are situations where the broker needs to focus on one particular aspect of message delivery, that sounds to me like the strategy pattern. If a broker can be written in such a way that it is allowed to focus on certain aspects and maybe ignore or completely forego others, then it would seem to me that the code could be made much more straight-forward, because it doesn't have to try to be the swiss army knife, solving everyone's problems at one time. Of course, this may be just a pipe dream and there's no way to do it (admittedly I'm not terribly familiar with the code), but I thought I'd throw it out there as a possible approach. I mean, we do this sort of thing already with the persistence providers, so maybe there's an opportunity here as well. Thoughts? James
Re: [DISCUSS] Fix Sorting of Board Reports
Thanks for the explanation. That helps. So, I guess we could discuss the merits of keeping the Board Reports on our wiki, as it does seem somewhat redundant. As long as they exist on the wiki, it would be helpful to have a better indexing system. Perhaps Hiram can offer background as to the purpose and intent of the Board Reports being published on the wiki? Best, Jim On Thu, Apr 9, 2015 at 10:27 AM, Daniel Kulp dk...@apache.org wrote: On Apr 9, 2015, at 1:02 PM, Jim Gomes jgo...@apache.org wrote: Thanks for the link, Dan. I didn't know those were there. I think the main difference here is that link is to the Board Minutes, whereas the ActiveMQ wiki has the Board Report. They seem to be identical, but will they always be? Possibly not, but it would NORMALLY be because the board has decided something should be private (like names of people being voted on or something) in which case it should likely not have been in our public version as well. Doesn't happen too often. Also, they would remove any wiki formatting type things that wouldn't look right in the text form they use. And even if they are identical, do we still need to have the redundancy for trace-ability? For instance, if the Board, for whatever reason, claims they didn't receive the report, we have documentation on the wiki showing the Report was produced. I don't really think the board would care if one was produced or not. It's the chair's job to make sure the board gets the report. If they don't get it, they ask the chair to report again next month. If the chair consistently has issues, they'd likely replace the chair.Another thing to keep in mind: it's the Chairs job to create the report that reflects the state of the community. The chair MAY include the wider community in creating that report, but that's not a requirement. Thus, saying the community produced one, the chair didn't submit it really wouldn't matter at all. Dan That's me just trying to understand the reason for the Board Report page's existence. -Jim On Thu, Apr 9, 2015 at 9:53 AM, Daniel Kulp dk...@apache.org wrote: No objection, but why don't we just delete the page and point at the official records: https://whimsy.apache.org/board/minutes/ActiveMQ.html Dan On Apr 9, 2015, at 12:35 PM, Jim Gomes jgo...@apache.org wrote: I recently went out to look at previous Board Reports ( http://activemq.apache.org/apache-activemq-board-reports.html) and found the current sorting method difficult to deal with. Unless we are required to use the page naming format, I would like to change it to the following format: Apache ActiveMQ Board Report - 2009.01 January Apache ActiveMQ Board Report - 2009.04 April Apache ActiveMQ Board Report - 2009.07 July . . . I would then set it to sort in reverse order so the most recent report is automatically at the top, and they descend in chronological order. The current sorting puts the most recent board report (2015/02) in the middle of the pack, making it difficult to find. Good luck trying to find the report directly prior to that. I will make the changes, unless anyone has other suggestions. Best, Jim -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
Re: [DISCUSS] Fix Sorting of Board Reports
Thanks, Tim. That is a clear and compelling reason to keep them there. With that clarified, does anyone have any comments on the renaming of the pages to improve the indexing? Best, Jim On Thu, Apr 9, 2015 at 11:16 AM, Timothy Bish tabish...@gmail.com wrote: On 04/09/2015 02:13 PM, Jim Gomes wrote: Thanks for the explanation. That helps. So, I guess we could discuss the merits of keeping the Board Reports on our wiki, as it does seem somewhat redundant. As long as they exist on the wiki, it would be helpful to have a better indexing system. Perhaps Hiram can offer background as to the purpose and intent of the Board Reports being published on the wiki? Best, Jim On Thu, Apr 9, 2015 at 10:27 AM, Daniel Kulp dk...@apache.org wrote: On Apr 9, 2015, at 1:02 PM, Jim Gomes jgo...@apache.org wrote: Thanks for the link, Dan. I didn't know those were there. I think the main difference here is that link is to the Board Minutes, whereas the ActiveMQ wiki has the Board Report. They seem to be identical, but will they always be? Possibly not, but it would NORMALLY be because the board has decided something should be private (like names of people being voted on or something) in which case it should likely not have been in our public version as well. Doesn't happen too often. Also, they would remove any wiki formatting type things that wouldn't look right in the text form they use. And even if they are identical, do we still need to have the redundancy for trace-ability? For instance, if the Board, for whatever reason, claims they didn't receive the report, we have documentation on the wiki showing the Report was produced. I don't really think the board would care if one was produced or not. It's the chair's job to make sure the board gets the report. If they don't get it, they ask the chair to report again next month. If the chair consistently has issues, they'd likely replace the chair.Another thing to keep in mind: it's the Chairs job to create the report that reflects the state of the community. The chair MAY include the wider community in creating that report, but that's not a requirement. Thus, saying the community produced one, the chair didn't submit it really wouldn't matter at all. Dan That's me just trying to understand the reason for the Board Report page's existence. -Jim On Thu, Apr 9, 2015 at 9:53 AM, Daniel Kulp dk...@apache.org wrote: No objection, but why don't we just delete the page and point at the official records: https://whimsy.apache.org/board/minutes/ActiveMQ.html Dan On Apr 9, 2015, at 12:35 PM, Jim Gomes jgo...@apache.org wrote: I recently went out to look at previous Board Reports ( http://activemq.apache.org/apache-activemq-board-reports.html) and found the current sorting method difficult to deal with. Unless we are required to use the page naming format, I would like to change it to the following format: Apache ActiveMQ Board Report - 2009.01 January Apache ActiveMQ Board Report - 2009.04 April Apache ActiveMQ Board Report - 2009.07 July . . . I would then set it to sort in reverse order so the most recent report is automatically at the top, and they descend in chronological order. The current sorting puts the most recent board report (2015/02) in the middle of the pack, making it difficult to find. Good luck trying to find the report directly prior to that. I will make the changes, unless anyone has other suggestions. Best, Jim -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com I believe that he does this as a place to create and edit them and allow for other members to contribute if they so desire before he submits them. I've edited a couple in the past prior to submission to add CMS or NMS release notes. -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.redhat.com twitter: @tabish121 blog: http://timbish.blogspot.com/
[DISCUSS] Fix Sorting of Board Reports
I recently went out to look at previous Board Reports ( http://activemq.apache.org/apache-activemq-board-reports.html) and found the current sorting method difficult to deal with. Unless we are required to use the page naming format, I would like to change it to the following format: Apache ActiveMQ Board Report - 2009.01 January Apache ActiveMQ Board Report - 2009.04 April Apache ActiveMQ Board Report - 2009.07 July . . . I would then set it to sort in reverse order so the most recent report is automatically at the top, and they descend in chronological order. The current sorting puts the most recent board report (2015/02) in the middle of the pack, making it difficult to find. Good luck trying to find the report directly prior to that. I will make the changes, unless anyone has other suggestions. Best, Jim
Re: [DISCUSS] Fix Sorting of Board Reports
Thanks for the feedback, everyone. It looks like there's no technical reason for the current naming scheme. I just wanted to make sure I wasn't breaking some kind of formatting requirement from the Board. I'll get them fixed up shortly. Best, Jim On Thu, Apr 9, 2015 at 12:12 PM, Gary Tully gary.tu...@gmail.com wrote: renaming makes sense to me. On 9 Apr 2015 19:44, Jim Gomes e.se...@gmail.com wrote: Thanks, Tim. That is a clear and compelling reason to keep them there. With that clarified, does anyone have any comments on the renaming of the pages to improve the indexing? Best, Jim On Thu, Apr 9, 2015 at 11:16 AM, Timothy Bish tabish...@gmail.com wrote: On 04/09/2015 02:13 PM, Jim Gomes wrote: Thanks for the explanation. That helps. So, I guess we could discuss the merits of keeping the Board Reports on our wiki, as it does seem somewhat redundant. As long as they exist on the wiki, it would be helpful to have a better indexing system. Perhaps Hiram can offer background as to the purpose and intent of the Board Reports being published on the wiki? Best, Jim On Thu, Apr 9, 2015 at 10:27 AM, Daniel Kulp dk...@apache.org wrote: On Apr 9, 2015, at 1:02 PM, Jim Gomes jgo...@apache.org wrote: Thanks for the link, Dan. I didn't know those were there. I think the main difference here is that link is to the Board Minutes, whereas the ActiveMQ wiki has the Board Report. They seem to be identical, but will they always be? Possibly not, but it would NORMALLY be because the board has decided something should be private (like names of people being voted on or something) in which case it should likely not have been in our public version as well. Doesn't happen too often. Also, they would remove any wiki formatting type things that wouldn't look right in the text form they use. And even if they are identical, do we still need to have the redundancy for trace-ability? For instance, if the Board, for whatever reason, claims they didn't receive the report, we have documentation on the wiki showing the Report was produced. I don't really think the board would care if one was produced or not. It's the chair's job to make sure the board gets the report. If they don't get it, they ask the chair to report again next month. If the chair consistently has issues, they'd likely replace the chair.Another thing to keep in mind: it's the Chairs job to create the report that reflects the state of the community. The chair MAY include the wider community in creating that report, but that's not a requirement. Thus, saying the community produced one, the chair didn't submit it really wouldn't matter at all. Dan That's me just trying to understand the reason for the Board Report page's existence. -Jim On Thu, Apr 9, 2015 at 9:53 AM, Daniel Kulp dk...@apache.org wrote: No objection, but why don't we just delete the page and point at the official records: https://whimsy.apache.org/board/minutes/ActiveMQ.html Dan On Apr 9, 2015, at 12:35 PM, Jim Gomes jgo...@apache.org wrote: I recently went out to look at previous Board Reports ( http://activemq.apache.org/apache-activemq-board-reports.html) and found the current sorting method difficult to deal with. Unless we are required to use the page naming format, I would like to change it to the following format: Apache ActiveMQ Board Report - 2009.01 January Apache ActiveMQ Board Report - 2009.04 April Apache ActiveMQ Board Report - 2009.07 July . . . I would then set it to sort in reverse order so the most recent report is automatically at the top, and they descend in chronological order. The current sorting puts the most recent board report (2015/02) in the middle of the pack, making it difficult to find. Good luck trying to find the report directly prior to that. I will make the changes, unless anyone has other suggestions. Best, Jim -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com I believe that he does this as a place to create and edit them and allow for other members to contribute if they so desire before he submits them. I've edited a couple in the past prior to submission to add CMS or NMS release notes. -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.redhat.com twitter: @tabish121 blog: http://timbish.blogspot.com/
Re: [DISCUSS] Fix Sorting of Board Reports
Thanks for the link, Dan. I didn't know those were there. I think the main difference here is that link is to the Board Minutes, whereas the ActiveMQ wiki has the Board Report. They seem to be identical, but will they always be? And even if they are identical, do we still need to have the redundancy for trace-ability? For instance, if the Board, for whatever reason, claims they didn't receive the report, we have documentation on the wiki showing the Report was produced. That's me just trying to understand the reason for the Board Report page's existence. -Jim On Thu, Apr 9, 2015 at 9:53 AM, Daniel Kulp dk...@apache.org wrote: No objection, but why don't we just delete the page and point at the official records: https://whimsy.apache.org/board/minutes/ActiveMQ.html Dan On Apr 9, 2015, at 12:35 PM, Jim Gomes jgo...@apache.org wrote: I recently went out to look at previous Board Reports ( http://activemq.apache.org/apache-activemq-board-reports.html) and found the current sorting method difficult to deal with. Unless we are required to use the page naming format, I would like to change it to the following format: Apache ActiveMQ Board Report - 2009.01 January Apache ActiveMQ Board Report - 2009.04 April Apache ActiveMQ Board Report - 2009.07 July . . . I would then set it to sort in reverse order so the most recent report is automatically at the top, and they descend in chronological order. The current sorting puts the most recent board report (2015/02) in the middle of the pack, making it difficult to find. Good luck trying to find the report directly prior to that. I will make the changes, unless anyone has other suggestions. Best, Jim -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
