[ANNOUNCE] CVE-2019-0222 - Apache ActiveMQ: Corrupt MQTT frame can cause broker shutdown
The following security vulnerability was reported against Apache ActiveMQ 5.15.8 and older versions. Please check the following document and see if you’re affected by the issue. http://activemq.apache.org/security-advisories.data/CVE-2019-0222-announcement.txt Apache ActiveMQ 5.15.9 has been released with appropriate fixes and is available for upgrade.
Re: [VOTE] Apache ActiveMQ Artemis 2.7.0
+1 Regards -- Dejan Bosanac http://sensatic.net/about On Fri, Mar 15, 2019 at 5:00 PM jgenender wrote: > +1 > > Jeff > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html >
Re: [VOTE] Apache ActiveMQ 5.15.9
+1 Regards -- Dejan Bosanac http://sensatic.net/about On Fri, Mar 15, 2019 at 5:08 PM Jamie G. wrote: > +1 (non-binding) > > Cheers, > Jamie > > On Fri, Mar 15, 2019 at 1:28 PM jgenender wrote: > > > > +1 > > > > Jeff > > > > > > > > -- > > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html >
Re: [VOTE] Apache ActiveMQ Artemis 2.5.0
+1 Regards -- Dejan Bosanac http://sensatic.net/about On Wed, Mar 14, 2018 at 12:25 AM, Christopher Shannon < christopher.l.shan...@gmail.com> wrote: > +1 > > On Tue, Mar 13, 2018 at 4:05 PM, Timothy Bish wrote: > > On 03/12/2018 04:40 PM, Clebert Suconic wrote: > >> > >> I would like to propose an Apache ActiveMQ Artemis 2.5.0 release. > >> > >> This is a great release, with 190 tasks completed including bug fixes, > >> improvements, new features and additional tasks. I really appreciate > >> everyone's contribution on making this happening. Thank you so much! > >> > >> > >> I would like to highlight the features introduced on this release: > >> > >> [ARTEMIS-853] - Support for exclusive consumers > >> [ARTEMIS-1030] - Support equivilent ActiveMQ 5.x Virtual Topic Naming > >> Abilities > >> [ARTEMIS-1548] - Support CRL > >> [ARTEMIS-1550] - Support LVQ for OpenWire > >> [ARTEMIS-1600] - Support masked passwords in bootstrap.xm and > login.config > >> [ARTEMIS-1623] - create an ActiveMQServerPlugin for logging various > >> broker events > >> [ARTEMIS-1649] - enable openssl provider for Netty > >> [ARTEMIS-1661] - Enable splitting of broker.xml into multiple files > >> [ARTEMIS-1663] - Add enhanced message count and size metrics for Queues > >> > >> > >> Given the length of this release, please refer to JIRA for the > >> complete report of fixes included on 2.5.0: > >> > >> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa? > projectId=12315920&version=12342127 > >> > >> > >> > >> Source and binary distributions can be found here: > >> https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/2.5.0 > >> > >> > >> The Maven repository is here: > >> https://repository.apache.org/content/repositories/ > orgapacheactivemq-1156 > >> > >> > >> In case you want to give it a try with the maven repo on examples: > >> > >> http://activemq.apache.org/artemis/docs/latest/hacking- > guide/validating-releases.html > >> > >> > >> The source tag: > >> > >> https://git-wip-us.apache.org/repos/asf?p=activemq-artemis. > git;a=tag;h=refs/tags/2.5.0 > >> > >> I will update the website after the vote has passed. > >> > >> > >> > >> [ ] +1 approve the release as Apache Artemis 2.4.0 > >> [ ] +0 no opinion > >> [ ] -1 disapprove (and reason why) > >> > >> Here's my +1 > >> > > > > +1 > > > > * Validated license and notice files > > * Validated signatures and checksums > > * Ran the binary broker and ran some AMQP sample applications against it > > * Built from source and ran some of the tests > > * Ran mvn -P release apache-rat:check to validate source files had > license > > headers > > > > -- > > Tim Bish > > twitter: @tabish121 > > blog: http://timbish.blogspot.com/ > > >
Re: [VOTE] Apache ActiveMQ 5.15.0
+1 Regards -- Dejan Bosanac http://sensatic.net/about On Fri, Jun 30, 2017 at 3:26 PM, Gary Tully wrote: > +1 > > There are some odd stack traces in the source build from bnd tools - looks > like we may need to add some additional excludes or it may be java8 bits > that bnd cannot parse. It is a little ugly need not be a blocker. > > eg: > > [*INFO*] *--- *maven-bundle-plugin:2.3.7:manifest *(bundle-manifest)* @ > activemq-web-demo* ---* > > java.lang.ArrayIndexOutOfBoundsException: 15 > > at aQute.lib.osgi.Clazz.parseClassFile(Clazz.java:448) > > at aQute.lib.osgi.Clazz.parseClassFile(Clazz.java:369) > > at aQute.lib.osgi.Clazz.parseClassFileWithCollector(Clazz.java:359) > > at aQute.lib.osgi.Clazz.parseClassFile(Clazz.java:349) > > at aQute.lib.osgi.Analyzer.analyzeJar(Analyzer.java:1725) > > at aQute.lib.osgi.Analyzer.analyzeBundleClasspath(Analyzer.java:1618) > > at aQute.lib.osgi.Analyzer.analyze(Analyzer.java:124) > > at aQute.lib.osgi.Builder.analyze(Builder.java:306) > > at aQute.lib.osgi.Analyzer.calcManifest(Analyzer.java:301) > > at aQute.lib.osgi.Builder.build(Builder.java:73) > > at > org.apache.felix.bundleplugin.ManifestPlugin.getAnalyzer( > ManifestPlugin.java:201) > > at > org.apache.felix.bundleplugin.ManifestPlugin.getManifest( > ManifestPlugin.java:114) > > at > org.apache.felix.bundleplugin.ManifestPlugin.execute( > ManifestPlugin.java:69) > > at org.apache.felix.bundleplugin.BundlePlugin.execute( > BundlePlugin.java:264) > > at org.apache.felix.bundleplugin.BundlePlugin.execute( > BundlePlugin.java:255) > > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo( > DefaultBuildPluginManager.java:134) > > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute( > MojoExecutor.java:208) > > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute( > MojoExecutor.java:154) > > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute( > MojoExecutor.java:146) > > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject( > LifecycleModuleBuilder.java:117) > > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject( > LifecycleModuleBuilder.java:81) > > at > org.apache.maven.lifecycle.internal.builder.singlethreaded. > SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > > at > org.apache.maven.lifecycle.internal.LifecycleStarter. > execute(LifecycleStarter.java:128) > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309) > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194) > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107) > > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993) > > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345) > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:191) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: > 62) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke( > DelegatingMethodAccessorImpl.java:43) > > at java.lang.reflect.Method.invoke(Method.java:498) > > at > org.codehaus.plexus.classworlds.launcher.Launcher. > launchEnhanced(Launcher.java:289) > > at > org.codehaus.plexus.classworlds.launcher.Launcher. > launch(Launcher.java:229) > > at > org.codehaus.plexus.classworlds.launcher.Launcher. > mainWithExitCode(Launcher.java:415) > > at org.codehaus.plexus.classworlds.launcher.Launcher. > main(Launcher.java:356) > > On Wed, 28 Jun 2017 at 17:01 Timothy Bish wrote: > > > +1 > > > > * Built from source and ran the smoke tests > > * Verified with Apache RAT that the license is present in the source > files > > * Checked the SRC and BIN archives for License and NOTICE files > > * Ran the binary broker and tested the webconsole and ran some sample > > clients against it > > * Validated the signatures and checksums > > > > > > On Tue, Jun 27, 2017 at 1:59 PM, Christopher Shannon < > > christopher.l.shan...@gmail.com> wrote: > > > > > Hi Everyone, > > > > > > I have created the ActiveMQ 5.15.0 release and it's ready for a vote. > > Note > > > that this release bumps the required Java version to Java 8. > > > > > > The list of resolved issues is here: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje > > > ctId=12311210&version=12338054 > > > > > > You can get binary distributions here: > > > https://repository.apache.org/conten
Re: [VOTE] Apache Artemis 2.1.0
+1 Regards -- Dejan Bosanac http://sensatic.net/about On Wed, May 10, 2017 at 9:12 AM, Christian Schneider < ch...@die-schneider.net> wrote: > +1 > > Christian > > > On 09.05.2017 00:25, Clebert Suconic wrote: > >> I'd like to propose an Apache Artemis 2.1.0 release. >> >> >> I would like to highlight these following new features on this release: >> >> - Artemis Plugin Support >> - Support Netty Native Epoll on Linux >> >> >> I would like to also highlight the huge work done around improving >> performance on many protocols, with many benchmarks showing better >> (lower) latency and less GC pauses due to these improvements made. >> >> There was a really extensive work on this last release, showing the >> maturity level of the codebase and the contributions. AMQP has been >> further enhanced even beyond 2.0.0, and I am so happy to see major >> contributions like the Plugin Support recently added, and other major >> contributors being active. >> >> I am really excited about this release and proud to be involved with >> open source development on this... >> >> >> I would appreciate your vote and time on evaluating this release: >> >> >> The release notes can be found here: >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?versi >> on=12339963&styleName=Html&projectId=12315920&Create=Create >> >> >> >> Source and binary distributions can be found here: >> >> https://repository.apache.org/content/repositories/orgapache >> activemq-1133/org/apache/activemq/apache-artemis/2.1.0/ >> >> >> The Maven repository is here: >> >> https://repository.apache.org/content/repositories/orgapacheactivemq-1133 >> >> >> >> In case you want to give it a try with the maven repo: >> >> http://activemq.apache.org/artemis/docs/2.0.0/hacking-guide/ >> validating-releases.html >> >> >> >> The source tag: >> https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.g >> it;a=tag;h=refs/tags/2.1.0 >> >> I will update the website after the vote. >> >> The vote will remain open for 72 hours. >> >> [ ] +1 approve the release as Apache Artemis 2.0.0 >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >> >> Here's my (binding) +1 >> >> Regards >> >> > > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > http://www.talend.com > >
[ANNOUNCE] CVE-2015-7559 - DoS in client via shutdown command
There following security vulnerability was reported against Apache ActiveMQ 5.14.4 and older versions. Please check the following document and see if you’re affected by the issue. http://activemq.apache.org/security-advisories.data/CVE-2015-7559-announcement.txt?version=1&modificationDate=149302471&api=v2 Apache ActiveMQ 5.14.5 with appropriate fixes was released and are available for upgrade. Regards -- Dejan Bosanac http://sensatic.net/about
[ANNOUNCE] Apache ActiveMQ 5.14.5 Released
Hi everyone, The ActiveMQ team is pleased to announce that Apache ActiveMQ 5.14.5 has been released and includes 12 fixes and improvements. A list of issues resolved in this release is available here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12339772 The Wiki page for the release is here: http://activemq.apache.org/activemq-5145-release.html A big thanks to everyone who contributed to this release. Regards -- Dejan Bosanac http://sensatic.net/about
[VOTE] [RESULT] Apache ActiveMQ 5.14.5
This vote passes with 6 +1 votes. I’ll proceed with the release. Regards -- Dejan Bosanac http://sensatic.net/about On Wed, Apr 12, 2017 at 5:39 PM, Timothy Bish wrote: > +1 > > * validated signatures and checksums > * checked using apache-rat for missing license files > * checked for the license and notice files in all the archives > * built from source and ran the sanity check test profile > * ran from the binary and validated using some client samples > * checked that basic web console functions worked > > > > On 04/11/2017 12:27 PM, Dejan Bosanac wrote: > >> Hi Everyone, >> >> I have created the ActiveMQ 5.14.5 release and it's ready for a vote. >> >> The list of resolved issues is here: >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje >> ctId=12311210&version=12339772 >> >> You can get binary distributions here: >> https://repository.apache.org/content/repositories/orgapache >> activemq-1124/org/apache/activemq/apache-activemq/5.14.5/ >> >> Source archives are here: >> https://repository.apache.org/content/repositories/orgapache >> activemq-1124/org/apache/activemq/activemq-parent/5.14.5/ >> >> Maven repository is at: >> https://repository.apache.org/content/repositories/orgapache >> activemq-1124/ >> >> Source tag: >> https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=com >> mit;h=19adb5d840e723631ef1030f689f5492a7163613 >> >> Please vote to approve this release. The vote will remain open for 72 >> hours. >> >> [ ] +1 Release the binary as Apache ActiveMQ 5.14.5 >> [ ] -1 (provide specific comments) >> >> Here's my +1 >> >> Regards >> -- >> Dejan Bosanac >> http://sensatic.net/about >> >> > > -- > Tim Bish > twitter: @tabish121 > blog: http://timbish.blogspot.com/ > >
[VOTE] Apache ActiveMQ 5.14.5
Hi Everyone, I have created the ActiveMQ 5.14.5 release and it's ready for a vote. The list of resolved issues is here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12339772 You can get binary distributions here: https://repository.apache.org/content/repositories/orgapacheactivemq-1124/org/apache/activemq/apache-activemq/5.14.5/ Source archives are here: https://repository.apache.org/content/repositories/orgapacheactivemq-1124/org/apache/activemq/activemq-parent/5.14.5/ Maven repository is at: https://repository.apache.org/content/repositories/orgapacheactivemq-1124/ Source tag: https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=19adb5d840e723631ef1030f689f5492a7163613 Please vote to approve this release. The vote will remain open for 72 hours. [ ] +1 Release the binary as Apache ActiveMQ 5.14.5 [ ] -1 (provide specific comments) Here's my +1 Regards -- Dejan Bosanac http://sensatic.net/about
Re: [VOTE] Apache Artemis 1.5.3 (RC2)
+1 Regards -- Dejan Bosanac http://sensatic.net/about On Tue, Feb 14, 2017 at 8:59 AM, Claus Ibsen wrote: > +1 > > Sorry no time to test, but glad to see patch releases of Artemis being > released regularly. Good job guys. > > On Fri, Feb 10, 2017 at 5:43 PM, Martyn Taylor wrote: > > Hello all, > > > > I'd like to propose an Apache Artemis 1.5.3 release (RC2). > > > > This revision release of Apache Artemis 1.5 contains a number of bug > fixes > > and improvements including: > > > > Bug > > > >- [ARTEMIS-917 <https://issues.apache.org/jira/browse/ARTEMIS-917>] - > >Retained messages from file system contain weird chars > >- [ARTEMIS-931 <https://issues.apache.org/jira/browse/ARTEMIS-931>] - > >Improve HTTP upgrade connection > >- [ARTEMIS-934 <https://issues.apache.org/jira/browse/ARTEMIS-934>] - > >Stomp server keeps pinging client after client stops responding > >- [ARTEMIS-937 <https://issues.apache.org/jira/browse/ARTEMIS-937>] - > >Use Proper disk alignment over libaio instead of 512 hard coded. > >- [ARTEMIS-939 <https://issues.apache.org/jira/browse/ARTEMIS-939>] - > >User list not updated on the broker dynamically > >- [ARTEMIS-951 <https://issues.apache.org/jira/browse/ARTEMIS-951>] - > >MQTT Messages Acks are not auto-committed > >- [ARTEMIS-952 <https://issues.apache.org/jira/browse/ARTEMIS-952>] - > >MQTT Clean session should delete subscription queues > > > > Improvement > > > >- [ARTEMIS-873 <https://issues.apache.org/jira/browse/ARTEMIS-873>] - > >Use K,M,G notations on broker.xml > >- [ARTEMIS-935 <https://issues.apache.org/jira/browse/ARTEMIS-935>] - > >Tool to recalculate disk sync times > >- [ARTEMIS-938 <https://issues.apache.org/jira/browse/ARTEMIS-938>] - > >JDBC persistence-store should use BIGINT type for IDs in database > tables > >- [ARTEMIS-957 <https://issues.apache.org/jira/browse/ARTEMIS-957>] - > >JDBC Store should use setBytes API vs using Concat on BLOB > > > > > > > > The release notes can be found here: > > *https://issues.apache.org/jira/secure/ReleaseNote.jspa? > version=12339575&styleName=Html&projectId=12315920 > > <https://issues.apache.org/jira/secure/ReleaseNote.jspa? > version=12339575&styleName=Html&projectId=12315920>* > > > > The binary distributions can be found here: > > https://repository.apache.org/content/repositories/ > orgapacheactivemq-1117/org/apache/activemq/apache-artemis/1.5.3/ > > > > The source archives can be found here: > > https://repository.apache.org/content/repositories/ > orgapacheactivemq-1117/org/apache/activemq/apache-artemis/1.5.3/ > > > > The Maven repository is here: > > https://repository.apache.org/content/repositories/ > orgapacheactivemq-1117/ > > > > The source tag: > > *https://git-wip-us.apache.org/repos/asf?p=activemq- > artemis.git;a=tag;h=refs/tags/1.5.3 > > <https://git-wip-us.apache.org/repos/asf?p=activemq- > artemis.git;a=tag;h=refs/tags/1.5.3>* > > > > As this is only a revision release, only doc and download links needs to > be > > updated in the website. I will update accordingly after the release. > > > > The vote will remain open for 72 hours. > > > > [ ] +1 approve the release as Apache Artemis 1.5.3 > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > Here's my (binding) +1 > > > > Regards > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
Re: [DISCUSS] distribute binary in .deb and .rpm
Hi Fabio, did you manage to make any progress on this? I’d be interested to help out. Regards -- Dejan Bosanac http://sensatic.net/about On Tue, Dec 20, 2016 at 3:36 PM, Clebert Suconic wrote: > I have asked the apache infra how we could make rpm and .deb releases > (As Robbie pointed out). > > I don't really mind which way we choose. as long it's easier to maintain. > > > It sounds the standard way would be the second option as you suggest. > why don't you start with that? keep the scripts on a directory such > artemis-linux-distros.. and I will wait input from infra on how to > release and sign those.. we can then make more changes. > > On Mon, Dec 19, 2016 at 8:08 PM, Fabio Gomes dos Santos > wrote: > > About the packaging method... > > > > If the second way are chosen, i can contribute with the project. Putting > > the hands-on... > > For the first, all i can do, is write the test for the binary and help > with > > the patterns. > > > > if we want to see Artemis officially on debian or centos, the second one > is > > the best choose. > > > > > > > > 2016-12-12 18:04 GMT-02:00 Robbie Gemmell : > > > >> I know the infra team and some projects have some hosting on bintray > >> (https://bintray.com/apache/), and that can host .deb and .rpm. > >> Whether its used by projects to do that, and what any process around > >> that would be if they do, I'm not sure. Perhaps worth asking infra. > >> > >> On 12 December 2016 at 17:03, Clebert Suconic < > clebert.suco...@gmail.com> > >> wrote: > >> > I couldn't find any information about rpms on apache.org > >> > > >> > Anyone have any information? > >> > > >> > On Thu, Dec 8, 2016 at 8:43 AM, Clebert Suconic > >> > wrote: > >> >> Having a rpm and .deb is a great idea. > >> >> > >> >> > >> >> Anyone knows how the release and distribution process would work for > >> those > >> >> including signing? > >> >> > >> >> > >> >> I will do some research on Apache website later today. > >> >> > >> >> > >> >> > >> >> On Thu, Dec 8, 2016 at 7:16 AM Fabio Gomes dos Santos < > >> supergr...@gmail.com> > >> >> wrote: > >> >>> > >> >>> Hi! > >> >>> > >> >>> > >> >>> > >> >>> We have two ways to do that: > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> 1 - Using a plugin on maven: > >> >>> > >> >>> > >> >>> > >> >>> http://www.mojohaus.org/rpm-maven-plugin/ > >> >>> > >> >>> http://mojo.codehaus.org/deb-maven-plugin > >> >>> > >> >>> > >> >>> > >> >>> 2 - Using the default way of each distribution (using .spec) > >> >>> > >> >>> > >> >>> > >> >>> Fedora/RHEL: https://fedora-java.github.io/howto/latest/ > >> >>> > >> >>> Debian: https://wiki.debian.org/Java/Packaging > >> >>> > >> >>> > >> >>> > >> >>> The packagecloud.io has plans to opensource project, but a simple > s3 > >> can > >> >>> > >> >>> provide a mirror for distribution. > >> >>> > >> >>> > >> >>> > >> >>> what you think about? > >> >>> > >> >>> I think this will provide more visibility to the project > >> >>> > >> >>> > >> >>> > >> >>> -- > >> >>> > >> >>> Fábio Santos > >> >>> > >> >>> supergr...@gmail.com > >> >>> > >> >>> <http://br.linkedin.com/pub/f%C3%A1bio-santos/1b/20/422> > >> >>> > >> >> > >> > > >> > > >> > > >> > -- > >> > Clebert Suconic > >> > > > > > > > > -- > > Fábio Santos > > supergr...@gmail.com > > <http://br.linkedin.com/pub/f%C3%A1bio-santos/1b/20/422> > > > > -- > Clebert Suconic >
Re: [DISCUSS] Web site update
I think the good starting point would be to create a new front page, that explains what’s this all about and have some links to subprojects, downloads, news, blogs and stuff. Then we can migrate existing sites to the new style one by one. Regards -- Dejan Bosanac http://sensatic.net/about On Thu, Dec 15, 2016 at 8:40 PM, Matt Pavlovich wrote: > @tbish Good point. We'll want to bring NMS, CMS, etc along for sure. > > > > On 12/15/16 2:21 PM, Timothy Bish wrote: > >> On 12/15/2016 02:08 PM, Matt Pavlovich wrote: >> >>> @tbish.. haha. Yeah, the Karaf site can be a bit much, but the use of >>> color and pictures is good.. lot of other popular open source projects have >>> similar layouts.. spring.io, etc. >>> >>> @clebert- IMO the plain apache.org is pretty bland. Prolly one step up >>> from openbsd.org level blandness ;-) The current Artemis docs have nice >>> l&f. I agree w/ clean site, but I think we should shoot for better font >>> usage and at least an updated logo. >>> >>> A nice logo that looks good as a laptop sticker, backpacks, t-shirts, >>> etc seems to be attainable. >>> >>> Others to consider: >>> wicket.apache.org >>> spark.apache.org >>> cassandra.apache.org (meh on the font, but clean look, good use of font >>> face and font color) >>> mesos.apache.org >>> couchdb.apache.org (less karaf'sh, simple layout. good font faces and >>> logo) >>> >>> -Matt >>> >> >> Keep in mind that ActiveMQ has several subprojects (multiple brokers, >> multiple clients) so the site design and layout needs to scale along with >> the subprojects >> >> >> >>> On 12/15/16 1:40 PM, Clebert Suconic wrote: >>> >>>> On Thu, Dec 15, 2016 at 12:40 PM, Timothy Bish >>>> wrote: >>>> >>>>> On 12/15/2016 12:11 PM, Matt Pavlovich wrote: >>>>> >>>>>> +1 website needs to be updated and will to assist. >>>>>> >>>>>> I'd also throw out there kafka.apache.org and karaf.apache.org as >>>>>> design >>>>>> concepts to consider as well. >>>>>> >>>>>> The Kafka one isn't bad, the Karaf site make me feel like I need to >>>>> contact >>>>> someone from sales to get a trial license. >>>>> >>>> LOL >>>> >>>> I think Karaf and Kafka have too much of their project's personality >>>> to bring it as a template. >>>> I was looking for a plain template. qpid is very clean. the main >>>> apache.org is also a very good example. >>>> >>> >>> >>> >> >> >
Re: [DISCUSS] LevelDB deprecation
+1 Regards -- Dejan Bosanac http://sensatic.net/about On Wed, Nov 16, 2016 at 8:11 AM, Bennet Schulz wrote: > +1 > > > Am 15.11.2016 um 15:16 schrieb Clebert Suconic < > clebert.suco...@gmail.com>: > > > > +1 > > > > On Tue, Nov 15, 2016 at 9:16 AM, Justin Bertram > wrote: > >> +1 > >> > >> - Original Message - > >> From: "Christopher Shannon" > >> To: dev@activemq.apache.org > >> Sent: Tuesday, November 15, 2016 5:45:41 AM > >> Subject: [DISCUSS] LevelDB deprecation > >> > >> Hi Everyone, > >> > >> I just wanted to ask what people think about officially deprecating > LevelDB > >> in our 5.x broker and update our documentation to say that it is no > longer > >> recommended. We can leave it in the code base for people who are still > >> using it but discourage its use. > >> > >> The main reason is that KahaDB continues to be the main focus where bugs > >> are fixed and not much attention is paid to LevelDB. There seems to be > >> several issues with corruption (especially with replication) so I don't > >> think it should be a recommended store unless the stability is sorted > out. > >> Unfortunately nearly every Jira reported against LevelDB goes ignored. > >> > >> Now that Artemis exists and supports replication I think the focus > should > >> be primarily on making Artemis the focus for users who need a replicated > >> store or to encourage the use of something like a shared file system > >> master/slave setup. > > > > > > > > -- > > Clebert Suconic > >
Re: [VOTE] Apache Artemis 1.4.0
+1 Regards -- Dejan Bosanac http://sensatic.net/about On Wed, Sep 7, 2016 at 8:47 AM, Claus Ibsen wrote: > +1 (binding) > > On Tue, Sep 6, 2016 at 9:59 PM, Clebert Suconic > wrote: > > Hello all, > > > > I would like to propose an Apache Artemis 1.4.0 release. > > > > Since 1.3.0 we've had a lot of fixes and improvements: > > > > * Global Max Size for Paging (Default mode is now is paging) > > * Disk Size monitor > > * Interceptors support added to the MQTT > > * Reload support for the configuration > > * AMQP and Stomp Improvements > > * Many more bug fixes. > > * Specific IDE settings are now removed from the source distribution > > > > The release notes can be found here: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > projectId=12315920&version=12336052 > > > > The binary distributions can be found here: > > https://repository.apache.org/content/repositories/ > orgapacheactivemq-1106/org/apache/activemq/apache-artemis/1.4.0/ > > > > The source archives can be found here: > > https://repository.apache.org/content/repositories/ > orgapacheactivemq-1106/org/apache/activemq/apache-artemis/1.4.0/ > > > > The Maven repository is here: > > https://repository.apache.org/content/repositories/ > orgapacheactivemq-1106/ > > > > The source tag: > > https://git-wip-us.apache.org/repos/asf?p=activemq-artemis. > git;a=tag;h=refs/tags/1.4.0 > > > > The project website for that version has been staged to: > > http://home.apache.org/~clebertsuconic/ > > > > The vote will remain open for 72 hours. > > > > [ ] +1 approve the release as Apache Artemis 1.4.0 > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > Here's my (non-binding) +1 > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
Re: [DISCUSS] CDI Backed Client Library for Artemis
Hi guys, I’m heading out for vacation in an hour, so I won’t be able to take a look at it immediately. I’ll dig into it as soon as I’m back. But, yeah this is a completely new integration, so it won’t affect any of the existing stuff. Regards -- Dejan Bosanac http://sensatic.net/about On Mon, Aug 1, 2016 at 4:24 PM, John D. Ament wrote: > That test looks like its focused on Karaf (OSGi) integration. Definitely > something that should be there. There's one guy I know who does OSGi and > CDI really well, but the market just isn't there. Both leverage JSR-330 > (AtInject) but ultimately are two different service models. > > This being its own JAR shouldn't impact any of that. > > John > > On Mon, Aug 1, 2016 at 10:16 AM Clebert Suconic > > wrote: > > > Looks really nice.. Very well done. > > > > There is a test Dejan wrote for CDI called > > org.apache.activemq.artemis.tests.integration.kara.ArtemisFeatureTest > > > > Can you verify the test still works? > > > > > > And how this would affect that Karaf integration? > > > > > > @Dejan can you take a look given you did a lot of work with this before? > > > > On Sun, Jul 31, 2016 at 11:11 PM, John D. Ament > > wrote: > > > Sorry, meant to link here - > > > https://github.com/johnament/activemq-artemis/tree/cdi-client > > > > > > John > > > > > > On Sun, Jul 31, 2016 at 11:09 PM John D. Ament > > > wrote: > > > > > >> All, > > >> > > >> I wanted to run this POC by you guys to see your thoughts. Obviously > I > > >> have a mixed background at this point, so it kind of makes sense to > > bring > > >> two of my interests together. I started hacking together a CDI backed > > >> client against Artemis Core/JMS. Looking at Artemis and its > > integrations > > >> with Vert.x, Aerogear and Spring, it makes sense to support another > > >> runtime. In addition, the JMS 2 spec mandates support for some > > injection > > >> points via CDI. I wanted to take it a step further. > > >> > > >> - If running locally, bootstrap an embedded server. > > >> - Connect to a locally running server, or a configured remote cluster. > > >> - Provide some injection points to work with said server (e.g. > > >> ConnectionFactory, JMSContext) > > >> > > >> I wouldn't call it complete, but I've created a simple POC that does > > these > > >> things, which you can find at > > >> > > > https://github.com/johnament/activemq-artemis/commit/8430136d9ea648a1f089747da434d945de1d7fa2 > > >> I still want to add some XA support, but even this adds a huge step > > >> forward to be able to connect a simple local process to a remote > server, > > >> without needing full containers to do injection points. > > >> > > >> So what do you guys think? Worth adding to Artemis? > > >> > > >> John > > >> > > > > > > > > -- > > Clebert Suconic > > >
Re: [ANNOUNCE] CVE-2016-3088: ActiveMQ Fileserver web application vulnerabilities
Hi Tim, it’s an omission. The feature will be completely removed with 5.14.0 and it’s been disabled by default since 5.12.0, so 5.13.x broker that haven’t this feature turn on explicitly are not vulnerable. I’ll fix the announcement now to say 5.13.x so it’s future proof in case of new 5.13 branch releases Regards -- Dejan Bosanac about.me/dejanb On Tue, May 24, 2016 at 2:09 PM, Tim Bain wrote: > Does the range of versions specified mean that the issue is already > addressed in 5.13.3, or was its omission from the range an oversight? > > Tim > On May 24, 2016 2:41 AM, "Dejan Bosanac" wrote: > > > There's a security vulnerability reported against Apache > > ActiveMQ 5.13.2 and older versions. > > > > Please check the following document and see if you’re affected by the > > issue. > > > > > > > http://activemq.apache.org/security-advisories.data/CVE-2016-3088-announcement.txt > > > > Vulnerability is similar to the one reported in CVE-2015-1830 ( > > > > > http://activemq.apache.org/security-advisories.data/CVE-2015-1830-announcement.txt > > ). > > The fileserver web application will be removed in 5.14.0 release and > users > > are advised not to use it and disable it in older versions. > > > > Regards > > -- > > Dejan Bosanac > > about.me/dejanb > > >
[ANNOUNCE] CVE-2016-3088: ActiveMQ Fileserver web application vulnerabilities
There's a security vulnerability reported against Apache ActiveMQ 5.13.2 and older versions. Please check the following document and see if you’re affected by the issue. http://activemq.apache.org/security-advisories.data/CVE-2016-3088-announcement.txt Vulnerability is similar to the one reported in CVE-2015-1830 ( http://activemq.apache.org/security-advisories.data/CVE-2015-1830-announcement.txt). The fileserver web application will be removed in 5.14.0 release and users are advised not to use it and disable it in older versions. Regards -- Dejan Bosanac about.me/dejanb
Re: [VOTE] Apache ActiveMQ 5.13.3 #2
+1 Regards -- Dejan Bosanac about.me/dejanb On Thu, Apr 28, 2016 at 9:03 PM, Matt Pavlovich wrote: > +1 > > Compiled and spot checked tests on OSX > > > On 4/28/16 8:16 AM, Christopher Shannon wrote: > >> I have merged in the fix for the failing test and re-cut the release. >> >> The list of resolved issues is here: >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12335045 >> >> You can get binary distributions here: >> >> https://repository.apache.org/content/repositories/orgapacheactivemq-1092/org/apache/activemq/apache-activemq/5.13.3/ >> >> Source archives are here: >> >> https://repository.apache.org/content/repositories/orgapacheactivemq-1092/org/apache/activemq/activemq-parent/5.13.3/ >> >> Maven repository is at: >> https://repository.apache.org/content/repositories/orgapacheactivemq-1092/ >> >> Source tag: >> * >> https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=f2f130b3c878d498cb561f7d4fa4613da56e7761 >> < >> https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=f2f130b3c878d498cb561f7d4fa4613da56e7761 >> >* >> >> Please vote to approve this release. The vote will remain open for 96 >> hours. >> >> [ ] +1 Release the binary as Apache ActiveMQ 5.13.3 >> [ ] -1 (provide specific comments) >> >> Here's my +1 >> >> >
Re: [VOTE] Release ActiveMQ-CPP v3.9.3
+1 Regards -- Dejan Bosanac about.me/dejanb On Mon, Mar 28, 2016 at 9:46 PM, Christopher Shannon < christopher.l.shan...@gmail.com> wrote: > +1 > > On Mon, Mar 28, 2016 at 10:58 AM, Timothy Bish > wrote: > > > New vote open for ActiveMQ-CPP v3.9.3 > > > > This is a new patch release of the ActiveMQ-CPP client with a fix for the > > message producer creation handling that allowed the client to miss > > exceptions sent back from the broker on producer create failure. > > > > The source bundles for this release can be found here: > > https://dist.apache.org/repos/dist/dev/activemq/activemq-cpp/3.9.3/ > > > > The Wiki page for the release is here: > > http://activemq.apache.org/cms/activemq-cpp-393-release.html > > > > The list of issues fixed in this release is available here: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12334243 > > > > Please cast your votes: > > > > [ ] +1 Release the source as Apache ActiveMQ-CPP 3.9.3 > > [ ] -1 (provide specific comments) > > > > Here is my +1 > > > > -- > > Tim Bish > > twitter: @tabish121 > > blog:http://timbish.blogspot.com/ > > > > >
Re: [VOTE] Apache ActiveMQ 5.13.2
+1 Regards -- Dejan Bosanac about.me/dejanb On Fri, Mar 4, 2016 at 8:03 AM, Claus Ibsen wrote: > +1 > > On Tue, Mar 1, 2016 at 6:15 PM, Christopher Shannon > wrote: > > Hi Everyone, > > > > I have created the ActiveMQ 5.13.2 release and it's ready for a vote. > This > > release has 15 bug fixes and improvements. > > > > The list of resolved issues is here: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12334774 > > > > You can get binary distributions here: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1089/org/apache/activemq/apache-activemq/5.13.2/ > > > > Source archives are here: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1089/org/apache/activemq/activemq-parent/5.13.2/ > > > > Maven repository is at: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1089/ > > > > Source tag: > > * > https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=6a2e71f11c72e0419f88cbd31d8bc99c35096abf > > < > https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=6a2e71f11c72e0419f88cbd31d8bc99c35096abf > >* > > > > Please vote to approve this release. The vote will remain open for 72 > > hours. > > > > [ ] +1 Release the binary as Apache ActiveMQ 5.13.2 > > [ ] -1 (provide specific comments) > > > > Here's my +1 > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
Re: [VOTE] Release ActiveMQ-CPP v3.9.2
+1 Regards -- Dejan Bosanac about.me/dejanb On Fri, Feb 5, 2016 at 12:04 PM, Robbie Gemmell wrote: > On 3 February 2016 at 14:57, Timothy Bish wrote: > > New vote open for ActiveMQ-CPP v3.9.2 > > > > This is a new patch release of the ActiveMQ-CPP client with a fix for > > how the STOMP protocol handlers deal with composite destinations. > > > > The source bundles for this release can be found here: > > https://dist.apache.org/repos/dist/dev/activemq/activemq-cpp/3.9.2/< > http://people.apache.org/%7Etabish/cms-3.9.x> > > > > The Wiki page for the release is here: > > http://activemq.apache.org/cms/activemq-cpp-392-release.html< > http://activemq.apache.org/cms/activemq-cpp-391-release.html> > > > > The list of issues fixed in this release is available here: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12334243 > > > > Please cast your votes: > > > > [ ] +1 Release the source as Apache ActiveMQ-CPP 3.9.2 > > [ ] -1 (provide specific comments) > > > > Here is my +1 > > > > -- > > Tim Bish > > twitter: @tabish121 > > blog: http://timbish.blogspot.com/ > > > > > +1 (non-binding) > > I downloaded all the files and verified their sigs, checked they had > licence+notice files, extracted and built using the tar.gz file, and > ran the simple producer+consumer examples. > > Robbie >
Re: [VOTE] Apache ActiveMQ 5.13.1
+1 Regards -- Dejan Bosanac about.me/dejanb On Thu, Feb 4, 2016 at 3:44 PM, Robbie Gemmell wrote: > +1 (non-binding) > > Verified the signature files, ran the source build, ran some of the > tests, used the staged maven artifacts with the Qpid JMS master build > and tests, kicked the tyres on the binary release with the Qpid JMS > HelloWorld example. > > Robbie > > On 2 February 2016 at 18:34, Christopher Shannon > wrote: > > Hello everyone, > > > > I have created the ActiveMQ 5.13.1 release and it's ready for a vote. > This > > release has 43 bug fixes and improvements. > > > > The list of resolved issues is here: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12334251 > > > > You can get binary distributions here: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1086/org/apache/activemq/apache-activemq/5.13.1/ > > > > Source archives are here: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1086/org/apache/activemq/activemq-parent/5.13.1/ > > > > Maven2 repository is at: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1086/ > > > > Source tag: > > * > https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=d60b73402cc11babb53e0a26e4537265f153492b > > < > https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=d60b73402cc11babb53e0a26e4537265f153492b > >* > > > > Please vote to approve this release. The vote will remain open for 72 > > hours. > > > > [ ] +1 Release the binary as Apache ActiveMQ 5.13.1 > > [ ] -1 (provide specific comments) > > > > Here's my +1 >
Re: [VOTE] ActiveMQ 5.11.4/5.12.3
+1 Regards -- Dejan Bosanac about.me/dejanb On Thu, Feb 4, 2016 at 3:50 PM, Jamie G. wrote: > +1 (non-binding) on 5.12.3 > +1 (non-binding) on 5.11.4 > > > On Thu, Feb 4, 2016 at 10:40 AM, Timothy Bish wrote: > > +1 > > > > On 02/03/2016 02:52 PM, Daniel Kulp wrote: > >> Several high importance fixes were back ported from the 5.13.1 release > that we should get into patch releases. > >> > >> > >> Staging Repositories: > >> 5.12.3: > >> > https://repository.apache.org/content/repositories/orgapacheactivemq-1087/ > >> 5.11.4: > >> > https://repository.apache.org/content/repositories/orgapacheactivemq-1088/ > >> > >> Tags: > >> 5.12.3 > >> > https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=231698ac73d6bc2b2e356a941e626ea9a2077c5c > >> 5.11.4 > >> > https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=67ddeb28d85d106dc2a8841cf8e2be7d8e33d0c1 > >> > >> > >> The vote will remain open for 72 hours. Here is my +1 > >> > >> > > > > > > -- > > Tim Bish > > twitter: @tabish121 > > blog: http://timbish.blogspot.com/ > > >
Re: [VOTE] Apache ActiveMQ 5.12.2 #3
+1 Regards -- Dejan Bosanac about.me/dejanb On Fri, Jan 8, 2016 at 4:48 PM, Claus Ibsen wrote: > +1 > > On Fri, Jan 8, 2016 at 3:59 PM, Christopher Shannon > wrote: > > I will leave the vote open for a couple more days as we still need a > couple > > more binding votes for this release to pass. > > > > On Thu, Jan 7, 2016 at 12:06 PM, Christopher Shannon < > > christopher.l.shan...@gmail.com> wrote: > > > >> Yes, AMQ-6077 which is the configuration changes, has been backported to > >> 5.12.2 > >> > >> On Thu, Jan 7, 2016 at 11:54 AM, Claus Ibsen > >> wrote: > >> > >>> Hi > >>> > >>> So this release has the same change as in 5.13.0 about those excluded > >>> package names, which breaks end users applications. > >>> > >>> More here: > >>> http://activemq.apache.org/objectmessage.html > >>> > >>> > >>> Dejan is that latest stuff you did add to master branch also > >>> backported? Or do end users have only the choice of configure this > >>> with JVM system properties? > >>> > >>> If not I would have liked to backport that too, so users on 5.12.x > >>> have a chance to configure this. Its not everyone that is allowed to > >>> configure JVM system properties. Or restart an entire JVM because the > >>> activemq-client can only be configured from JVM system property. > >>> > >>> > >>> > >>> > >>> On Tue, Jan 5, 2016 at 5:18 PM, Christopher Shannon > >>> wrote: > >>> > Hello everyone, > >>> > > >>> > The problem with AMQ-6094 has been fixed I have re-created the > ActiveMQ > >>> > 5.12.2 release and it's ready for a vote. This release has over 25 > bug > >>> > fixes and improvements. > >>> > > >>> > The list of resolved issues is here: > >>> > > >>> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12333874 > >>> > > >>> > You can get binary distributions here: > >>> > > >>> > https://repository.apache.org/content/repositories/orgapacheactivemq-1082/org/apache/activemq/apache-activemq/5.12.2/ > >>> > > >>> > Source archives are here: > >>> > > >>> > https://repository.apache.org/content/repositories/orgapacheactivemq-1082/org/apache/activemq/activemq-parent/5.12.2/ > >>> > > >>> > Maven2 repository is at: > >>> > > >>> > https://repository.apache.org/content/repositories/orgapacheactivemq-1082/ > >>> > > >>> > Source tag: > >>> > * > >>> > https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=6ccbbce23de1d92daf83456accfdb03a4b768238 > >>> > < > >>> > https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=6ccbbce23de1d92daf83456accfdb03a4b768238 > >>> >* > >>> > > >>> > Please vote to approve this release. The vote will remain open for > 72 > >>> > hours. > >>> > > >>> > [ ] +1 Release the binary as Apache ActiveMQ 5.12.2 > >>> > [ ] -1 (provide specific comments) > >>> > > >>> > Here's my +1 (non-binding) > >>> > >>> > >>> > >>> -- > >>> Claus Ibsen > >>> - > >>> http://davsclaus.com @davsclaus > >>> Camel in Action 2: https://www.manning.com/ibsen2 > >>> > >> > >> > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
Re: [VOTE] Apache Artemis 1.2.0 (RC2)
+1 (binding) Regards -- Dejan Bosanac about.me/dejanb On Tue, Jan 5, 2016 at 2:36 PM, Christopher Shannon < christopher.l.shan...@gmail.com> wrote: > +1 (non-binding) > > Built from source and ran the quick tests > Checked LICENSE headers > Deployed and ran the broker from the binary on CentOS > Ran several different examples > > On Mon, Jan 4, 2016 at 8:25 PM, John D. Ament > wrote: > > > +1 non binding. > > > > Source release looks clean, builds fine (even w/ spaces) > > > > For next release: please update copyright dates for 2016 (damn that first > > day after the new year) > > > > John > > > > On Mon, Jan 4, 2016 at 9:19 AM Martyn Taylor wrote: > > > > > Hello all. > > > > > > I'd like to propose an Apache Artemis 1.2.0 release RC2. This RC2 > > > addresses the binary library inclusion in the source distribution and > > > has made progress on addressing the usability issues highlighted in RC1 > > > feedback. > > > > > > Since 1.1.0 we've had some significant improvements to performance, > > > particularly around the persistence layer. In addition new features > > > have been added such as LDAP and OSGi support. There has also been > more > > > improvements to the OpenWire protocol. > > > > > > The release notes can be found here: > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920&version=12333274 > > > > > > > > > The binary distributions can be found here: > > > > > > > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1081/org/apache/activemq/apache-artemis/1.2.0/ > > > > > > > > > The source archives can be found here: > > > > > > > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1081/org/apache/activemq/apache-artemis/1.2.0/ > > > > > > > > > The Maven repository is here: > > > > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1081/ > > > > > > The source tag: > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;a=tag;h=refs/tags/1.2.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.2.0 > > > [ ] +0 no opinion > > > [ ] -1 disapprove (and reason why) > > > > > > Here's my (non-binding) +1 > > > > > > Regards > > > > > >
Re: [VOTE] Apache ActiveMQ 5.12.2 #2
+1 (binding) Looks good Regards -- Dejan Bosanac about.me/dejanb On Thu, Dec 17, 2015 at 1:38 PM, Robbie Gemmell wrote: > On 16 December 2015 at 15:48, Christopher Shannon > wrote: > > Hello everyone, > > > > The problem with the previous release attempt has been fixed I have > > re-created the ActiveMQ 5.12.2 release and it's ready for a vote. This > > release has 20 bug fixes and > > improvements. > > > > The list of resolved issues is here: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12333874 > > > > You can get binary distributions here: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1075/org/apache/activemq/apache-activemq/5.12.2/ > > > > Source archives are here: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1075/org/apache/activemq/activemq-parent/5.12.2/ > > > > Maven2 repository is at: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1075/ > > > > Source tag: > > * > https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=f4a05c45730bbf2b2c531e5d263447e53b7c7ddc > > < > https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=f4a05c45730bbf2b2c531e5d263447e53b7c7ddc > >* > > > > Please vote to approve this release. The vote will remain open for 120 > > hours. (because of the weekend) > > > > [ ] +1 Release the binary as Apache ActiveMQ 5.12.2 > > [ ] -1 (provide specific comments) > > > > Here's my +1 (non-binding) > > > +1 (non-binding) > > Verified the sigs, ran the source build and some of the tests, kicked > the tyres on the binary archive with an AMQP client, used the staged > maven repo with Qpid JMS master build+tests. > > Robbie >
Re: [ANNOUNCE] Apache ActiveMQ 5.13.0 Released
Thanks Claus, here’s some more docs for it http://activemq.apache.org/objectmessage.html#ObjectMessage-Clients I’ll create a proper PR once we have 5.13.1 Regards -- Dejan Bosanac about.me/dejanb On Wed, Dec 16, 2015 at 4:24 PM, Claus Ibsen wrote: > Thanks Dejan > > I logged a ticket at Camel with your instructions > https://issues.apache.org/jira/browse/CAMEL-9429 > > On Mon, Dec 14, 2015 at 2:15 PM, Dejan Bosanac > wrote: > > Hi Claus, > > > > I implemented a fix for this in > > https://issues.apache.org/jira/browse/AMQ-6077. If you can give it a > look > > and see if anything else is missing, it would greatly appreciated. > > > > Here are the proposed changes to the Camel once we have 5.13.1 release > > > https://github.com/dejanb/camel/commit/6c942f4bac18ab84c76411515d1e87caaf7705a4 > > > > BTW. We should change version of the current master to 5.14-SNAPSHOT now > > that 5.13.0 is out. > > > > Regards > > -- > > Dejan Bosanac > > about.me/dejanb > > > > On Mon, Dec 7, 2015 at 2:39 PM, Daniel Kulp wrote: > > > >> > >> > On Dec 7, 2015, at 8:16 AM, Claus Ibsen > wrote: > >> > > >> > Also if the java class name is in a JMS header ( I think there is a > >> > standard for that, JMSType is it not?) maybe the client/server can use > >> > that out of the box to know at least packages from that class is okay > >> > to use. > >> > >> > >> Doesn’t that defeat the purpose though? I could craft a message that > >> contains “MyBadClass” and add that JMS header to say MyBadClass should > be > >> allowed. MyBadClass is loaded and security problem. It really needs > to be > >> something configured, not something part of the message. > >> > >> Dan > >> > >> > >> > > >> > > >> > On Mon, Dec 7, 2015 at 2:15 PM, Claus Ibsen > >> wrote: > >> >> Hi > >> >> > >> >> Thanks. > >> >> > >> >> Yeah this must be easier from client pov. Having to set a JVM system > >> >> property is sometimes hard for people, eg they deploy to an existing > >> >> running app server which they cannot restart. > >> >> > >> >> And then they need to add some code hack to set the system property > >> >> from their java app before AMQ bootstrap. > >> >> > >> >> Looking forward to a 5.13.1 release. Hopefully with a nice and easy > >> >> way for clients, and a speedy release so users can upgrade more > >> >> easily. > >> >> > >> >> > >> >> > >> >> On Mon, Dec 7, 2015 at 1:52 PM, Dejan Bosanac > >> wrote: > >> >>> Hi Claus, > >> >>> > >> >>> here’s the test fix for the current implementation > >> >>> > >> > https://github.com/dejanb/camel/commit/138186ffa40381c8c082d69917cbb29181ab4abc > >> >>> > >> >>> The thing is that the same security issues can occur in the client > >> >>> applications, when folks call getObject() method, so I think it’s > the > >> right > >> >>> approach for people to while-list only the packages they trust. > >> >>> > >> >>> I agree that we can improve user experience by making it easier to > >> >>> configure all this in the client apps. I think it might be good > allow > >> easy > >> >>> configuration on the connection factory and using connection urls. > I’ll > >> >>> raise a new Jira for that and we can deliver this in 5.13.1. If you > >> have > >> >>> any more concerns and ideas on how to improve this, please let me > know. > >> >>> > >> >>> I’ll go ahead next and create more docs around this. > >> >>> > >> >>> > >> >>> Regards > >> >>> -- > >> >>> Dejan Bosanac > >> >>> about.me/dejanb > >> >>> > >> >>> On Mon, Dec 7, 2015 at 11:24 AM, Dejan Bosanac > > >> wrote: > >> >>> > >> >>>> I’ll give it a try now. Thanks! > >> >>>> > >> >>>> Regards > >> >>>> -- > >> >>>> Dejan Bosanac > >> >>>> about.me/dejanb > >> >>>> > >> >>
Re: [ANNOUNCE] Apache ActiveMQ 5.13.0 Released
Sorry Christopher, my mistake. My local branches were messed up. It’s all good. Regards -- Dejan Bosanac about.me/dejanb On Mon, Dec 14, 2015 at 2:24 PM, Christopher Shannon < christopher.l.shan...@gmail.com> wrote: > I updated master to 5.14-SNAPSHOT when i prepared the last release. > > Besides backporting this to the 5.13.x branch we should probably backport > AMQ-6077 to 5.12.x as well so it will be included in 5.12.2. > > On Mon, Dec 14, 2015 at 8:15 AM, Dejan Bosanac > wrote: > > > Hi Claus, > > > > I implemented a fix for this in > > https://issues.apache.org/jira/browse/AMQ-6077. If you can give it a > look > > and see if anything else is missing, it would greatly appreciated. > > > > Here are the proposed changes to the Camel once we have 5.13.1 release > > > > > https://github.com/dejanb/camel/commit/6c942f4bac18ab84c76411515d1e87caaf7705a4 > > > > BTW. We should change version of the current master to 5.14-SNAPSHOT now > > that 5.13.0 is out. > > > > Regards > > -- > > Dejan Bosanac > > about.me/dejanb > > > > On Mon, Dec 7, 2015 at 2:39 PM, Daniel Kulp wrote: > > > > > > > > > On Dec 7, 2015, at 8:16 AM, Claus Ibsen > wrote: > > > > > > > > Also if the java class name is in a JMS header ( I think there is a > > > > standard for that, JMSType is it not?) maybe the client/server can > use > > > > that out of the box to know at least packages from that class is okay > > > > to use. > > > > > > > > > Doesn’t that defeat the purpose though? I could craft a message that > > > contains “MyBadClass” and add that JMS header to say MyBadClass should > be > > > allowed. MyBadClass is loaded and security problem. It really needs > to > > be > > > something configured, not something part of the message. > > > > > > Dan > > > > > > > > > > > > > > > > > > On Mon, Dec 7, 2015 at 2:15 PM, Claus Ibsen > > > wrote: > > > >> Hi > > > >> > > > >> Thanks. > > > >> > > > >> Yeah this must be easier from client pov. Having to set a JVM system > > > >> property is sometimes hard for people, eg they deploy to an existing > > > >> running app server which they cannot restart. > > > >> > > > >> And then they need to add some code hack to set the system property > > > >> from their java app before AMQ bootstrap. > > > >> > > > >> Looking forward to a 5.13.1 release. Hopefully with a nice and easy > > > >> way for clients, and a speedy release so users can upgrade more > > > >> easily. > > > >> > > > >> > > > >> > > > >> On Mon, Dec 7, 2015 at 1:52 PM, Dejan Bosanac > > > wrote: > > > >>> Hi Claus, > > > >>> > > > >>> here’s the test fix for the current implementation > > > >>> > > > > > > https://github.com/dejanb/camel/commit/138186ffa40381c8c082d69917cbb29181ab4abc > > > >>> > > > >>> The thing is that the same security issues can occur in the client > > > >>> applications, when folks call getObject() method, so I think it’s > the > > > right > > > >>> approach for people to while-list only the packages they trust. > > > >>> > > > >>> I agree that we can improve user experience by making it easier to > > > >>> configure all this in the client apps. I think it might be good > allow > > > easy > > > >>> configuration on the connection factory and using connection urls. > > I’ll > > > >>> raise a new Jira for that and we can deliver this in 5.13.1. If you > > > have > > > >>> any more concerns and ideas on how to improve this, please let me > > know. > > > >>> > > > >>> I’ll go ahead next and create more docs around this. > > > >>> > > > >>> > > > >>> Regards > > > >>> -- > > > >>> Dejan Bosanac > > > >>> about.me/dejanb > > > >>> > > > >>> On Mon, Dec 7, 2015 at 11:24 AM, Dejan Bosanac < > de...@nighttale.net> > > > wrote: > > > >>> > > > >>>> I’ll give it a try now. Thanks! > > > >>>> &
Re: [ANNOUNCE] Apache ActiveMQ 5.13.0 Released
Hi Claus, I implemented a fix for this in https://issues.apache.org/jira/browse/AMQ-6077. If you can give it a look and see if anything else is missing, it would greatly appreciated. Here are the proposed changes to the Camel once we have 5.13.1 release https://github.com/dejanb/camel/commit/6c942f4bac18ab84c76411515d1e87caaf7705a4 BTW. We should change version of the current master to 5.14-SNAPSHOT now that 5.13.0 is out. Regards -- Dejan Bosanac about.me/dejanb On Mon, Dec 7, 2015 at 2:39 PM, Daniel Kulp wrote: > > > On Dec 7, 2015, at 8:16 AM, Claus Ibsen wrote: > > > > Also if the java class name is in a JMS header ( I think there is a > > standard for that, JMSType is it not?) maybe the client/server can use > > that out of the box to know at least packages from that class is okay > > to use. > > > Doesn’t that defeat the purpose though? I could craft a message that > contains “MyBadClass” and add that JMS header to say MyBadClass should be > allowed. MyBadClass is loaded and security problem. It really needs to be > something configured, not something part of the message. > > Dan > > > > > > > > On Mon, Dec 7, 2015 at 2:15 PM, Claus Ibsen > wrote: > >> Hi > >> > >> Thanks. > >> > >> Yeah this must be easier from client pov. Having to set a JVM system > >> property is sometimes hard for people, eg they deploy to an existing > >> running app server which they cannot restart. > >> > >> And then they need to add some code hack to set the system property > >> from their java app before AMQ bootstrap. > >> > >> Looking forward to a 5.13.1 release. Hopefully with a nice and easy > >> way for clients, and a speedy release so users can upgrade more > >> easily. > >> > >> > >> > >> On Mon, Dec 7, 2015 at 1:52 PM, Dejan Bosanac > wrote: > >>> Hi Claus, > >>> > >>> here’s the test fix for the current implementation > >>> > https://github.com/dejanb/camel/commit/138186ffa40381c8c082d69917cbb29181ab4abc > >>> > >>> The thing is that the same security issues can occur in the client > >>> applications, when folks call getObject() method, so I think it’s the > right > >>> approach for people to while-list only the packages they trust. > >>> > >>> I agree that we can improve user experience by making it easier to > >>> configure all this in the client apps. I think it might be good allow > easy > >>> configuration on the connection factory and using connection urls. I’ll > >>> raise a new Jira for that and we can deliver this in 5.13.1. If you > have > >>> any more concerns and ideas on how to improve this, please let me know. > >>> > >>> I’ll go ahead next and create more docs around this. > >>> > >>> > >>> Regards > >>> -- > >>> Dejan Bosanac > >>> about.me/dejanb > >>> > >>> On Mon, Dec 7, 2015 at 11:24 AM, Dejan Bosanac > wrote: > >>> > >>>> I’ll give it a try now. Thanks! > >>>> > >>>> Regards > >>>> -- > >>>> Dejan Bosanac > >>>> about.me/dejanb > >>>> > >>>> On Mon, Dec 7, 2015 at 11:16 AM, Claus Ibsen > >>>> wrote: > >>>> > >>>>> Yes a number of test fails in camel-jms, if you test with 5.13.0. You > >>>>> can try yourself by changing the activemq-version in the > >>>>> parent/pom.xml. > >>>>> > >>>>> > >>>>> > >>>>> On Mon, Dec 7, 2015 at 11:04 AM, Dejan Bosanac > >>>>> wrote: > >>>>>> Hi Claus, > >>>>>> > >>>>>> restrictions were necessary for the CVE that was reported. We’re > about > >>>>> to > >>>>>> disclose it fully now after the release. > >>>>>> > >>>>>> AFAIK the change should not affect ObjectMessages in general, just > the > >>>>>> cases where those objects are serialized/unserialized inside of the > >>>>> broker, > >>>>>> like web console or stomp transformations. I’ll create a proper > docs for > >>>>>> the change now and the security aspect of it and we can see later > whet > >>>>> else > >>>>>> we can do to improve the user experience. > >>>>&
[ANNOUNCE] CVE-2015-5254 - Unsafe deserialization in ActiveMQ
A security vulnerabilities is reported against Apache ActiveMQ 5.12.1 and older versions Please check the following document and see if you’re affected http://activemq.apache.org/security-advisories.data/CVE-2015-5254-announcement.txt Apache ActiveMQ 5.13.0 with appropriate fixes is released and available for upgrade. Please take a look at http://activemq.apache.org/objectmessage.html and https://issues.apache.org/jira/browse/AMQ-6013 for more details. Regards -- Dejan Bosanac about.me/dejanb
Re: [ANNOUNCE] Apache ActiveMQ 5.13.0 Released
Hi Claus, here’s the test fix for the current implementation https://github.com/dejanb/camel/commit/138186ffa40381c8c082d69917cbb29181ab4abc The thing is that the same security issues can occur in the client applications, when folks call getObject() method, so I think it’s the right approach for people to while-list only the packages they trust. I agree that we can improve user experience by making it easier to configure all this in the client apps. I think it might be good allow easy configuration on the connection factory and using connection urls. I’ll raise a new Jira for that and we can deliver this in 5.13.1. If you have any more concerns and ideas on how to improve this, please let me know. I’ll go ahead next and create more docs around this. Regards -- Dejan Bosanac about.me/dejanb On Mon, Dec 7, 2015 at 11:24 AM, Dejan Bosanac wrote: > I’ll give it a try now. Thanks! > > Regards > -- > Dejan Bosanac > about.me/dejanb > > On Mon, Dec 7, 2015 at 11:16 AM, Claus Ibsen > wrote: > >> Yes a number of test fails in camel-jms, if you test with 5.13.0. You >> can try yourself by changing the activemq-version in the >> parent/pom.xml. >> >> >> >> On Mon, Dec 7, 2015 at 11:04 AM, Dejan Bosanac >> wrote: >> > Hi Claus, >> > >> > restrictions were necessary for the CVE that was reported. We’re about >> to >> > disclose it fully now after the release. >> > >> > AFAIK the change should not affect ObjectMessages in general, just the >> > cases where those objects are serialized/unserialized inside of the >> broker, >> > like web console or stomp transformations. I’ll create a proper docs for >> > the change now and the security aspect of it and we can see later whet >> else >> > we can do to improve the user experience. >> > >> > Are there any Camel related tests that fails due to this change? I can >> take >> > a look at that as well. >> > >> > >> > Regards >> > -- >> > Dejan Bosanac >> > about.me/dejanb >> > >> > On Sat, Dec 5, 2015 at 11:19 AM, Claus Ibsen >> wrote: >> > >> >> I really think you guys should add something about those object >> >> serialization resitrcitions. Any end users that uses java objects over >> >> JMS is affected. Nothing works anymore. >> >> >> >> Its because of >> >> https://issues.apache.org/jira/browse/AMQ-6013 >> >> >> >> So there should be some text in the release notes, and ideally AMQ >> >> broker / client should have some kind of INFO logging that openwire >> >> with objects is restricted or not. Otherwise its even harder for end >> >> users to spot what is going on. >> >> >> >> >> >> >> >> On Fri, Dec 4, 2015 at 3:57 PM, Timothy Bish >> wrote: >> >> > It's probably a good idea to add a new page in the "New Features" >> section >> >> > on the site to cover the additions in 5.13.0. I know you added the >> >> 'auto' >> >> > transport along with some other work for some additional metrics >> etc, all >> >> > good things that would be nice to advertise a bit. >> >> > >> >> > See: http://activemq.apache.org/new-features.html >> >> > >> >> > On Thu, Dec 3, 2015 at 3:51 PM, Christopher Shannon < >> >> > christopher.l.shan...@gmail.com> wrote: >> >> > >> >> >> Hi everyone, >> >> >> >> >> >> Apache ActiveMQ 5.13.0 has now been released. >> >> >> >> >> >> This release contains a number of resolved issues and new features >> since >> >> >> the 5.12.1 release. >> >> >> >> >> >> A list of issues resolved in this release is available here: >> >> >> >> >> >> >> >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329848 >> >> >> >> >> >> The Wiki page for the release is here: >> >> >> http://activemq.apache.org/activemq-5130-release.html >> >> >> >> >> >> API documentation for 5.12.1 is located here: >> >> >> http://activemq.apache.org/maven/5.13.0/apidocs/index.html >> >> >> >> >> > >> >> > >> >> > >> >> > -- >> >> > -- >> >> > Tim Bish >> >> >> >> >> >> >> >> -- >> >> Claus Ibsen >> >> - >> >> http://davsclaus.com @davsclaus >> >> Camel in Action 2: https://www.manning.com/ibsen2 >> >> >> >> >> >> -- >> Claus Ibsen >> - >> http://davsclaus.com @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 >> > >
Re: [ANNOUNCE] Apache ActiveMQ 5.13.0 Released
I’ll give it a try now. Thanks! Regards -- Dejan Bosanac about.me/dejanb On Mon, Dec 7, 2015 at 11:16 AM, Claus Ibsen wrote: > Yes a number of test fails in camel-jms, if you test with 5.13.0. You > can try yourself by changing the activemq-version in the > parent/pom.xml. > > > > On Mon, Dec 7, 2015 at 11:04 AM, Dejan Bosanac > wrote: > > Hi Claus, > > > > restrictions were necessary for the CVE that was reported. We’re about to > > disclose it fully now after the release. > > > > AFAIK the change should not affect ObjectMessages in general, just the > > cases where those objects are serialized/unserialized inside of the > broker, > > like web console or stomp transformations. I’ll create a proper docs for > > the change now and the security aspect of it and we can see later whet > else > > we can do to improve the user experience. > > > > Are there any Camel related tests that fails due to this change? I can > take > > a look at that as well. > > > > > > Regards > > -- > > Dejan Bosanac > > about.me/dejanb > > > > On Sat, Dec 5, 2015 at 11:19 AM, Claus Ibsen > wrote: > > > >> I really think you guys should add something about those object > >> serialization resitrcitions. Any end users that uses java objects over > >> JMS is affected. Nothing works anymore. > >> > >> Its because of > >> https://issues.apache.org/jira/browse/AMQ-6013 > >> > >> So there should be some text in the release notes, and ideally AMQ > >> broker / client should have some kind of INFO logging that openwire > >> with objects is restricted or not. Otherwise its even harder for end > >> users to spot what is going on. > >> > >> > >> > >> On Fri, Dec 4, 2015 at 3:57 PM, Timothy Bish > wrote: > >> > It's probably a good idea to add a new page in the "New Features" > section > >> > on the site to cover the additions in 5.13.0. I know you added the > >> 'auto' > >> > transport along with some other work for some additional metrics etc, > all > >> > good things that would be nice to advertise a bit. > >> > > >> > See: http://activemq.apache.org/new-features.html > >> > > >> > On Thu, Dec 3, 2015 at 3:51 PM, Christopher Shannon < > >> > christopher.l.shan...@gmail.com> wrote: > >> > > >> >> Hi everyone, > >> >> > >> >> Apache ActiveMQ 5.13.0 has now been released. > >> >> > >> >> This release contains a number of resolved issues and new features > since > >> >> the 5.12.1 release. > >> >> > >> >> A list of issues resolved in this release is available here: > >> >> > >> >> > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329848 > >> >> > >> >> The Wiki page for the release is here: > >> >> http://activemq.apache.org/activemq-5130-release.html > >> >> > >> >> API documentation for 5.12.1 is located here: > >> >> http://activemq.apache.org/maven/5.13.0/apidocs/index.html > >> >> > >> > > >> > > >> > > >> > -- > >> > -- > >> > Tim Bish > >> > >> > >> > >> -- > >> Claus Ibsen > >> - > >> http://davsclaus.com @davsclaus > >> Camel in Action 2: https://www.manning.com/ibsen2 > >> > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
Re: [ANNOUNCE] Apache ActiveMQ 5.13.0 Released
Hi Claus, restrictions were necessary for the CVE that was reported. We’re about to disclose it fully now after the release. AFAIK the change should not affect ObjectMessages in general, just the cases where those objects are serialized/unserialized inside of the broker, like web console or stomp transformations. I’ll create a proper docs for the change now and the security aspect of it and we can see later whet else we can do to improve the user experience. Are there any Camel related tests that fails due to this change? I can take a look at that as well. Regards -- Dejan Bosanac about.me/dejanb On Sat, Dec 5, 2015 at 11:19 AM, Claus Ibsen wrote: > I really think you guys should add something about those object > serialization resitrcitions. Any end users that uses java objects over > JMS is affected. Nothing works anymore. > > Its because of > https://issues.apache.org/jira/browse/AMQ-6013 > > So there should be some text in the release notes, and ideally AMQ > broker / client should have some kind of INFO logging that openwire > with objects is restricted or not. Otherwise its even harder for end > users to spot what is going on. > > > > On Fri, Dec 4, 2015 at 3:57 PM, Timothy Bish wrote: > > It's probably a good idea to add a new page in the "New Features" section > > on the site to cover the additions in 5.13.0. I know you added the > 'auto' > > transport along with some other work for some additional metrics etc, all > > good things that would be nice to advertise a bit. > > > > See: http://activemq.apache.org/new-features.html > > > > On Thu, Dec 3, 2015 at 3:51 PM, Christopher Shannon < > > christopher.l.shan...@gmail.com> wrote: > > > >> Hi everyone, > >> > >> Apache ActiveMQ 5.13.0 has now been released. > >> > >> This release contains a number of resolved issues and new features since > >> the 5.12.1 release. > >> > >> A list of issues resolved in this release is available here: > >> > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329848 > >> > >> The Wiki page for the release is here: > >> http://activemq.apache.org/activemq-5130-release.html > >> > >> API documentation for 5.12.1 is located here: > >> http://activemq.apache.org/maven/5.13.0/apidocs/index.html > >> > > > > > > > > -- > > -- > > Tim Bish > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
Re: [VOTE] Release ActiveMQ-CPP v3.9.1
+1 Regards -- Dejan Bosanac about.me/dejanb On Tue, Dec 1, 2015 at 3:00 PM, Gary Tully wrote: > +1 > > On Tue, 1 Dec 2015 at 12:35 Christopher Shannon < > christopher.l.shan...@gmail.com> wrote: > > > +1 (non-binding) > > > > On Tue, Dec 1, 2015 at 1:43 AM, Claus Ibsen > wrote: > > > > > +1 > > > > > > On Tue, Dec 1, 2015 at 1:47 AM, Timothy Bish > > wrote: > > > > New vote open for ActiveMQ-CPP v3.9.1 > > > > > > > > This is a new bug fix release of the ActiveMQ-CPP client with a fix > for > > > a potential segfault when testing against the latest ActiveMQ Artemis > > > release. A couple other minor fixes are included as well. > > > > > > > > The source bundles for this release can be found here: > > > > http://people.apache.org/~tabish/cms-3.9.x > > > > > > > > The Wiki page for the release is here: > > > > http://activemq.apache.org/cms/activemq-cpp-391-release.html > > > > > > > > The list of issues fixed in this release is available here: > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12333244 > > > > > > > > Please cast your votes: > > > > > > > > [ ] +1 Release the source as Apache ActiveMQ-CPP 3.9.1 > > > > [ ] -1 (provide specific comments) > > > > > > > > Here is my +1 > > > > > > > > -- > > > > Tim Bish > > > > Sr Software Engineer | RedHat Inc. > > > > tim.b...@redhat.com | www.redhat.com > > > > twitter: @tabish121 > > > > blog: http://timbish.blogspot.com/ > > > > > > > > > > > > > > > > -- > > > Claus Ibsen > > > - > > > http://davsclaus.com @davsclaus > > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > >
Re: [VOTE] Apache ActiveMQ 5.13.0
+1 Looks good Regards -- Dejan Bosanac about.me/dejanb On Tue, Dec 1, 2015 at 4:43 PM, Timothy Bish wrote: > +1 > > Built from source and ran sanity tests. > Checked LICENSE and NOTICE files > Ran a rat check for missing license files > Checked all signatures and sums. > Ran the QPid JMS activemq test suite using the maven artifacts > Ran the broker from the binary and checked basic functionality including > web console. > > On 11/30/2015 09:22 AM, Christopher Shannon wrote: > > Hello everyone, > > > > I have cut the ActiveMQ 5.13.0 release and it's ready for a vote. This > > release has over 80 bug fixes and new features. > > > > The list of resolved issues is here: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329848 > > > > You can get binary distributions here: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1071/org/apache/activemq/apache-activemq/5.13.0/ > > > > Source archives are here: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1071/org/apache/activemq/activemq-parent/5.13.0/ > > > > Maven2 repository is at: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1071/ > > > > Source tag: > > > https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=abfe038ddfd6d6c4f7c41e106dabc815041b04c5 > > > > Please vote to approve this release. The vote will remain open for 72 > > hours. > > > > [ ] +1 Release the binary as Apache ActiveMQ 5.13.0 > > [ ] -1 (provide specific comments) > > > > Here's my +1 (non-binding) > > > > > -- > Tim Bish > Sr Software Engineer | RedHat Inc. > tim.b...@redhat.com | www.redhat.com > twitter: @tabish121 > blog: http://timbish.blogspot.com/ > >
Re: [DISCUSS] ActiveMQ 5.13.0 Release Date
+1 Regards -- Dejan Bosanac about.me/dejanb On Wed, Nov 11, 2015 at 4:46 PM, Timothy Bish wrote: > On 11/11/2015 10:17 AM, Christopher Shannon wrote: > > Hi Everyone, > > > > It's been 3 months since 5.12 was released and there has been some > > significant work on new features and many improvements since then. > > > > Here is the current release notes: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329848 > > > > I was thinking about calling a vote for a release in the 2-3 week time > > frame and wanted to see if there were any blockers that would prevent > this. > > > +1 > > There's been several new features added for 5.13.0 so it would be good > to get a release out so folks can try them out and let us know what > needs hardening. > > -- > Tim Bish > Sr Software Engineer | RedHat Inc. > tim.b...@redhat.com | www.redhat.com > twitter: @tabish121 > blog: http://timbish.blogspot.com/ > >
Re: [VOTE] ActiveMQ 5.11.3
+1 Regards -- Dejan Bosanac about.me/dejanb On Sun, Nov 1, 2015 at 11:56 AM, Christian Schneider < ch...@die-schneider.net> wrote: > +1 (non binding) > > Tested in karaf 4.0.2. > > Christian > Am 29.10.2015 5:22 nachm. schrieb "Daniel Kulp" : > > > > > This is a vote to release Apache ActiveMQ 5.11.3 > > > > Staging area: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1070/ > > > > Tag: > > > > > https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=a820bfb4c5489ed842efc6ef5702f0fc21975c41 > > > > Issues resolved: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12333254 > > > > > > This vote will be open till Monday. Here is my +1 > > > > > > -- > > Daniel Kulp > > dk...@apache.org - http://dankulp.com/blog > > Talend Community Coder - http://coders.talend.com > > > > >
Re: [HEADSUP] ActiveMQ 5.12.1 Release Preparation
Great. Thanks! Regards -- Dejan Bosanac about.me/dejanb On Wed, Oct 7, 2015 at 6:48 PM, Christopher Shannon < christopher.l.shan...@gmail.com> wrote: > I went ahead and merged the MQTT changes into the 5.12.x branch. > > On Wed, Oct 7, 2015 at 11:31 AM, Dejan Bosanac > wrote: > > > Yeah, I think those are safe. No major changes, just some hardening. > > > > Regards > > -- > > Dejan Bosanac > > about.me/dejanb > > > > On Wed, Oct 7, 2015 at 5:06 PM, Timothy Bish > wrote: > > > > > On 10/07/2015 11:03 AM, Christopher Shannon wrote: > > > > Claus, I applied your commits to the 5.12.x branch so camel and > jolokia > > > are > > > > now up to date. > > > > > > > > Dejan, no problem, the release can wait until your issue gets fixed. > > > > > > There were a couple recent MQTT fixes that went into master, are those > > > safe to go into 5.12.1? Seems so from a quick glance at the commits. > > > > > > > On Wed, Oct 7, 2015 at 9:19 AM, Claus Ibsen > > > wrote: > > > > > > > >> And jolokia to 1.3.2 > > > >> > > > >> On Wed, Oct 7, 2015 at 3:19 PM, Claus Ibsen > > > wrote: > > > >>> I think we should upgrade camel from 2.15.2 to 2.15.3 so it has the > > > >>> latest bug fixes in this patch release too. > > > >>> > > > >>> On Mon, Oct 5, 2015 at 10:25 PM, Christopher Shannon > > > >>> wrote: > > > >>>> With AMQ-5966 being closed, the only other issue I'm hoping to try > > and > > > >> get > > > >>>> resolved for 5.12.1 is > > https://issues.apache.org/jira/browse/AMQ-5994 > > > . > > > >>>> > > > >>>> Does anyone have any other issues they want to look at resolving > > > before > > > >>>> releasing 5.12.1? > > > >>>> > > > >>>> On Tue, Sep 22, 2015 at 5:21 PM, Christopher Shannon < > > > >>>> christopher.l.shan...@gmail.com> wrote: > > > >>>> > > > >>>>> That is a good point and I agree that issue should be resolved > for > > > >>>>> 5.12.1. However, I am also having a hard time determining if the > > > >> behavior > > > >>>>> change is a bug or not for the same reasons you pointed out. > > > >>>>> > > > >>>>> On Tue, Sep 22, 2015 at 4:47 PM, Daniel Kulp > > > wrote: > > > >>>>> > > > >>>>>>> On Sep 22, 2015, at 4:36 PM, Christopher Shannon < > > > >>>>>> christopher.l.shan...@gmail.com> wrote: > > > >>>>>>> It's been about a month since 5.12.0 was released and there are > > > >> already > > > >>>>>> a > > > >>>>>>> good number of fixes contributed towards 5.12.1 so I'd like to > > > start > > > >>>>>>> working on a 5.12.1 release in a few days. > > > >>>>>>> > > > >>>>>>> If there is anything major that would be a blocker, let me > know. > > > >>>>>>> > > > >>>>>>> Here are the current release notes: > > > >>>>>>> > > > >> > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12333269 > > > >>>>>> Well, I’d like to understand what is going on with > > > >>>>>> https://issues.apache.org/jira/browse/AMQ-5966 a bit first. > > It’s > > > >>>>>> definitely a behavior change (and thus should have been > documented > > > in > > > >>>>>> release notes at the very least).What I’m still struggling > > with > > > is > > > >>>>>> trying to determine if it’s a bug or not. > > > >>>>>> > > > >>>>>> That said, the commit that introduced the change did not > include a > > > >> unit > > > >>>>>> test. The log points at a fuse JIRA that is obviously > completely > > > >>>>>> unrelated. Thus, I have no idea why that change was even put > in. > > > >> I’m > > > >>>>>> tempted to back it out. > > > >>>>>> > > > >>>>>> > > > >>>>>> -- > > > >>>>>> Daniel Kulp > > > >>>>>> dk...@apache.org - http://dankulp.com/blog > > > >>>>>> Talend Community Coder - http://coders.talend.com > > > >>>>>> > > > >>>>>> > > > >>> > > > >>> > > > >>> -- > > > >>> Claus Ibsen > > > >>> - > > > >>> http://davsclaus.com @davsclaus > > > >>> Camel in Action 2nd edition: > > > >>> https://www.manning.com/books/camel-in-action-second-edition > > > >> > > > >> > > > >> -- > > > >> Claus Ibsen > > > >> - > > > >> http://davsclaus.com @davsclaus > > > >> Camel in Action 2nd edition: > > > >> https://www.manning.com/books/camel-in-action-second-edition > > > >> > > > > > > > > > -- > > > Tim Bish > > > Sr Software Engineer | RedHat Inc. > > > tim.b...@redhat.com | www.redhat.com > > > twitter: @tabish121 > > > blog: http://timbish.blogspot.com/ > > > > > > > > >
Re: [HEADSUP] ActiveMQ 5.12.1 Release Preparation
Yeah, I think those are safe. No major changes, just some hardening. Regards -- Dejan Bosanac about.me/dejanb On Wed, Oct 7, 2015 at 5:06 PM, Timothy Bish wrote: > On 10/07/2015 11:03 AM, Christopher Shannon wrote: > > Claus, I applied your commits to the 5.12.x branch so camel and jolokia > are > > now up to date. > > > > Dejan, no problem, the release can wait until your issue gets fixed. > > There were a couple recent MQTT fixes that went into master, are those > safe to go into 5.12.1? Seems so from a quick glance at the commits. > > > On Wed, Oct 7, 2015 at 9:19 AM, Claus Ibsen > wrote: > > > >> And jolokia to 1.3.2 > >> > >> On Wed, Oct 7, 2015 at 3:19 PM, Claus Ibsen > wrote: > >>> I think we should upgrade camel from 2.15.2 to 2.15.3 so it has the > >>> latest bug fixes in this patch release too. > >>> > >>> On Mon, Oct 5, 2015 at 10:25 PM, Christopher Shannon > >>> wrote: > >>>> With AMQ-5966 being closed, the only other issue I'm hoping to try and > >> get > >>>> resolved for 5.12.1 is https://issues.apache.org/jira/browse/AMQ-5994 > . > >>>> > >>>> Does anyone have any other issues they want to look at resolving > before > >>>> releasing 5.12.1? > >>>> > >>>> On Tue, Sep 22, 2015 at 5:21 PM, Christopher Shannon < > >>>> christopher.l.shan...@gmail.com> wrote: > >>>> > >>>>> That is a good point and I agree that issue should be resolved for > >>>>> 5.12.1. However, I am also having a hard time determining if the > >> behavior > >>>>> change is a bug or not for the same reasons you pointed out. > >>>>> > >>>>> On Tue, Sep 22, 2015 at 4:47 PM, Daniel Kulp > wrote: > >>>>> > >>>>>>> On Sep 22, 2015, at 4:36 PM, Christopher Shannon < > >>>>>> christopher.l.shan...@gmail.com> wrote: > >>>>>>> It's been about a month since 5.12.0 was released and there are > >> already > >>>>>> a > >>>>>>> good number of fixes contributed towards 5.12.1 so I'd like to > start > >>>>>>> working on a 5.12.1 release in a few days. > >>>>>>> > >>>>>>> If there is anything major that would be a blocker, let me know. > >>>>>>> > >>>>>>> Here are the current release notes: > >>>>>>> > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12333269 > >>>>>> Well, I’d like to understand what is going on with > >>>>>> https://issues.apache.org/jira/browse/AMQ-5966 a bit first. It’s > >>>>>> definitely a behavior change (and thus should have been documented > in > >>>>>> release notes at the very least).What I’m still struggling with > is > >>>>>> trying to determine if it’s a bug or not. > >>>>>> > >>>>>> That said, the commit that introduced the change did not include a > >> unit > >>>>>> test. The log points at a fuse JIRA that is obviously completely > >>>>>> unrelated. Thus, I have no idea why that change was even put in. > >> I’m > >>>>>> tempted to back it out. > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> Daniel Kulp > >>>>>> dk...@apache.org - http://dankulp.com/blog > >>>>>> Talend Community Coder - http://coders.talend.com > >>>>>> > >>>>>> > >>> > >>> > >>> -- > >>> Claus Ibsen > >>> - > >>> http://davsclaus.com @davsclaus > >>> Camel in Action 2nd edition: > >>> https://www.manning.com/books/camel-in-action-second-edition > >> > >> > >> -- > >> Claus Ibsen > >> - > >> http://davsclaus.com @davsclaus > >> Camel in Action 2nd edition: > >> https://www.manning.com/books/camel-in-action-second-edition > >> > > > -- > Tim Bish > Sr Software Engineer | RedHat Inc. > tim.b...@redhat.com | www.redhat.com > twitter: @tabish121 > blog: http://timbish.blogspot.com/ > >
Re: [HEADSUP] ActiveMQ 5.12.1 Release Preparation
Hi, I’d like to tackle one issue I have on my list in the next few days. It’d be good if you could hold on the release before we have that. Regards -- Dejan Bosanac about.me/dejanb On Mon, Oct 5, 2015 at 10:25 PM, Christopher Shannon < christopher.l.shan...@gmail.com> wrote: > With AMQ-5966 being closed, the only other issue I'm hoping to try and get > resolved for 5.12.1 is https://issues.apache.org/jira/browse/AMQ-5994. > > Does anyone have any other issues they want to look at resolving before > releasing 5.12.1? > > On Tue, Sep 22, 2015 at 5:21 PM, Christopher Shannon < > christopher.l.shan...@gmail.com> wrote: > > > That is a good point and I agree that issue should be resolved for > > 5.12.1. However, I am also having a hard time determining if the > behavior > > change is a bug or not for the same reasons you pointed out. > > > > On Tue, Sep 22, 2015 at 4:47 PM, Daniel Kulp wrote: > > > >> > >> > On Sep 22, 2015, at 4:36 PM, Christopher Shannon < > >> christopher.l.shan...@gmail.com> wrote: > >> > > >> > It's been about a month since 5.12.0 was released and there are > already > >> a > >> > good number of fixes contributed towards 5.12.1 so I'd like to start > >> > working on a 5.12.1 release in a few days. > >> > > >> > If there is anything major that would be a blocker, let me know. > >> > > >> > Here are the current release notes: > >> > > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12333269 > >> > >> Well, I’d like to understand what is going on with > >> https://issues.apache.org/jira/browse/AMQ-5966 a bit first. It’s > >> definitely a behavior change (and thus should have been documented in > >> release notes at the very least).What I’m still struggling with is > >> trying to determine if it’s a bug or not. > >> > >> That said, the commit that introduced the change did not include a unit > >> test. The log points at a fuse JIRA that is obviously completely > >> unrelated. Thus, I have no idea why that change was even put in. I’m > >> tempted to back it out. > >> > >> > >> -- > >> Daniel Kulp > >> dk...@apache.org - http://dankulp.com/blog > >> Talend Community Coder - http://coders.talend.com > >> > >> > > >
Re: {VOTE] Release Apache.NMS.ActiveMQ 1.7.1
+1 Regards -- Dejan Bosanac about.me/dejanb On Mon, Oct 5, 2015 at 1:20 PM, Gary Tully wrote: > +1 > > On Sat, 3 Oct 2015 at 16:46 Timothy Bish wrote: > > > On 09/30/2015 07:04 PM, Jim Gomes wrote: > > > +1 > > > > > > On Wed, Sep 30, 2015, 2:44 PM Timothy Bish > wrote: > > > > > >> Hello > > >> > > >> This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.7.1 > > >> > > >> This is first bugfix release of the Apache.NMS.ActiveMQ v1.7.x line. > > >> This release incorporates many fixes and improvements over the 1.7.0 > > >> release. Several fixes made to the Java OpenWire client were ported > > >> over as well as some fixes for issues in the .NET Distributed > > >> Transaction layer. > > >> > > >> The binaries and source bundles for the Release Candidate can be found > > >> here: > > >> http://people.apache.org/~tabish/nms-1.7.x > > >> <http://people.apache.org/%7Etabish/nms-1.7.x> > > >> > > >> The Wiki Page for this release is here: > > >> http://activemq.apache.org/nms/apachenmsactivemq-v171.html > > >> > > >> The list of issues resolved is here: > > >> > > >> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12329541 > > >> > > >> Please cast your votes (the vote will be open for 72 hrs): > > >> > > >> [ ] +1 Release the source as Apache NMS.ActiveMQ v1.7.1 > > >> [ ] -1 (provide specific comments) > > >> > > >> Here's my +1 > > >> > > >> -- > > >> Tim Bish > > >> Sr Software Engineer | RedHat Inc. > > >> tim.b...@redhat.com | www.redhat.com > > >> twitter: @tabish121 > > >> blog: http://timbish.blogspot.com/ > > >> > > >> > > I'll leave this open for a few more days, hopefully another PMC can take > > a look and cast a vote. > > > > -- > > Tim Bish > > Sr Software Engineer | RedHat Inc. > > tim.b...@redhat.com | www.redhat.com > > twitter: @tabish121 > > blog: http://timbish.blogspot.com/ > > > > >
Re: [VOTE] Apache Artemis (RC4)
+1 (binding) Regards -- Dejan Bosanac about.me/dejanb On Mon, Sep 21, 2015 at 5:04 PM, John D. Ament wrote: > +1 nonbinding > On Sep 18, 2015 10:55, "Martyn Taylor" wrote: > > > Hello all. > > > > I've cut a 4th release candidate of Apache Artemis 1.1.0 addressing. > This > > latest RC fixes the MDB regressions as discussed on the RC3 feedback. > > > > Since 1.0.0 a number of significant improvements have been made, mainly > > around OpenWire protocol support, where a number of bugs have been fixed > > and significant enhancements to performance have been made. The examples > > have also been restructured to make them more user friendly, and lastly, > > MQTT protocol support has been added. > > > > The release notes can be found here: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920&version=12332642 > > > > The binary distributions can be found here: > > > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1068/org/apache/activemq/apache-artemis/1.1.0/ > > > > The source archives can be found here: > > > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1068/org/apache/activemq/apache-artemis/1.1.0/ > > > > The Maven repository is here: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1068/ > > > > The source tag: > > > > > https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;a=tag;h=refs/tags/1.1.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.1.0 > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > Here's my (non-binding) +1 > > > > Regards > > > > Martyn > > >
Re: [VOTE] Apache Artemis 1.1.0 (RC3)
+1 (binding) Regards -- Dejan Bosanac about.me/dejanb On Sat, Sep 12, 2015 at 6:10 PM, Clebert wrote: > I repeated the same procedure I did for Rc2. > > +1 (non binding) > > > > On Sep 12, 2015, at 03:30, Claus Ibsen wrote: > > > > +1 (binding) > > > >> On Fri, Sep 11, 2015 at 10:16 PM, Martyn Taylor > wrote: > >> Hello all. > >> > >> I've cut a 3rd release candidate of Apache Artemis 1.1.0 addressing. > This > >> RC has a fix for the issue raised by Andy Taylor during RC2 feedback. > >> > >> Since 1.0.0 a number of significant improvements have been made, mainly > >> around OpenWire protocol support, where a number of bugs have been > fixed and > >> significant enhancements to performance have been made. The examples > have > >> also been restructured to make them more user friendly, and lastly, MQTT > >> protocol support has been added. > >> > >> The release notes can be found here: > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920&version=12332642 > >> > >> The binary distributions can be found here: > >> > https://repository.apache.org/content/repositories/orgapacheactivemq-1067/org/apache/activemq/apache-artemis/1.1.0/ > >> > >> The source archives can be found here: > >> > https://repository.apache.org/content/repositories/orgapacheactivemq-1067/org/apache/activemq/apache-artemis/1.1.0/ > >> > >> The Maven repository is here: > >> > https://repository.apache.org/content/repositories/orgapacheactivemq-1067/ > >> > >> The source tag: > >> > https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;a=tag;h=refs/tags/1.1.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.1.0 > >> [ ] +0 no opinion > >> [ ] -1 disapprove (and reason why) > >> > >> Here's my (non-binding) +1 > >> > >> Regards > >> > >> Martyn > > > > > > > > -- > > Claus Ibsen > > - > > http://davsclaus.com @davsclaus > > Camel in Action 2nd edition: > > https://www.manning.com/books/camel-in-action-second-edition >
Re: [VOTE] Apache Artemis 1.1.0 (RC2)
+1 (binding) Ran some OpenWire and MQTT examples from 5.x distro. Everything looks good. Regards -- Dejan Bosanac about.me/dejanb On Fri, Sep 11, 2015 at 9:05 AM, Claus Ibsen wrote: > +1 (binding) > > Just checked a bit about the licenses and the JARs. > > Only odd was the jms 2.0 spec JAR is -alpha-2, but it seems that is > the last release. I have no clue why its named alpha when the JMS 2.0 > spec is final. > > > > http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.geronimo.specs%22%20AND%20a%3A%22geronimo-jms_2.0_spec%22 > > > > > On Tue, Sep 8, 2015 at 8:30 PM, Martyn Taylor wrote: > > Hello all. > > > > I've cut a second release candidate of Apache Artemis 1.1.0 addressing > > initial RC feedback. > > > > Since 1.0.0 a number of significant improvements have been made, mainly > > around OpenWire protocol support, where a number of bugs have been fixed > and > > significant enhancements to performance have been made. The examples > have > > also been restructured to make them more user friendly, and lastly, MQTT > > protocol support has been added. > > > > The release notes can be found here: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920&version=12332642 > > > > The binary distributions can be found here: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1066/org/apache/activemq/apache-artemis/1.1.0/ > > > > The source archives can be found here: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1066/org/apache/activemq/apache-artemis/1.1.0/ > > > > The Maven repository is here: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1066/ > > > > The source tag: > > > https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;a=tag;h=refs/tags/1.1.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.1.0 > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > Here's my (non-binding) +1 > > > > Regards > > > > Martyn > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2nd edition: > https://www.manning.com/books/camel-in-action-second-edition >
Re: [VOTE] Release Apache.NMS API 1.7.1
+1 Regards -- Dejan Bosanac about.me/dejanb On Tue, Sep 1, 2015 at 4:49 PM, Jim Gomes wrote: > +1 > > On Tue, Sep 1, 2015, 6:37 AM Timothy Bish wrote: > > > Hello > > > > This is a call for a vote on the release of the Apache.NMS API v1.7.1. > > 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 in the 1.7.x line including Apache.NMS.ActiveMQ. > > > > This is a bug fix version that adds a few minor fixes that are targeted > > at the client libraries that support MS DTC Transactions. > > > > The binaries and source bundles for the Release Candidate can be found > > here: > > [ http://people.apache.org/~tabish/nms-1.7.x > > <http://people.apache.org/%7Etabish/nms-1.7.x> ] > > > > The Wiki Page for this release is here: > > [ http://activemq.apache.org/nms/apachenms-api-v171.html ] > > > > Please cast your votes (the vote will be open for 72 hrs): > > > > [ ] +1 Release the source as Apache NMS API 1.7.1 > > [ ] -1 (provide specific comments) > > > > Here's my +1 > > > > Regards, > > Tim > > > > -- > > Tim Bish > > Sr Software Engineer | RedHat Inc. > > tim.b...@redhat.com | www.redhat.com > > twitter: @tabish121 > > blog: http://timbish.blogspot.com/ > > > > >
Re: [ANNOUNCE] CVE-2015-1830 - Path traversal leading to unauthenticated RCE in ActiveMQ
The vulnerability is fixed with https://issues.apache.org/jira/browse/AMQ-5754 Regards -- Dejan Bosanac about.me/dejanb On Mon, Aug 17, 2015 at 2:29 PM, Dejan Bosanac wrote: > A security vulnerabilities is reported against Apache ActiveMQ 5.11.1 and > older versions > > Please check the following document and see if you’re affected > > > http://activemq.apache.org/security-advisories.data/CVE-2015-1830-announcement.txt > > Apache ActiveMQ 5.12.0 and 5.11.2 with appropriate fixes are released and > available for upgrade. There's also a configuration workaround that > resolves the problem (described in the announcement). > > Regards > -- > Dejan Bosanac > about.me/dejanb >
[ANNOUNCE] CVE-2015-1830 - Path traversal leading to unauthenticated RCE in ActiveMQ
A security vulnerabilities is reported against Apache ActiveMQ 5.11.1 and older versions Please check the following document and see if you’re affected http://activemq.apache.org/security-advisories.data/CVE-2015-1830-announcement.txt Apache ActiveMQ 5.12.0 and 5.11.2 with appropriate fixes are released and available for upgrade. There's also a configuration workaround that resolves the problem (described in the announcement). Regards -- Dejan Bosanac about.me/dejanb
Re: 5.11.2....
Cheers Regards -- Dejan Bosanac about.me/dejanb On Wed, Aug 5, 2015 at 5:35 PM, Daniel Kulp wrote: > > > On Aug 5, 2015, at 9:47 AM, Dejan Bosanac wrote: > > > > Can you add https://issues.apache.org/jira/browse/AMQ-5754 to the list? > > > Yep. Done. Thanks! > > Dan > > > > > > Regards > > -- > > Dejan Bosanac > > about.me/dejanb > > > > On Wed, Aug 5, 2015 at 3:28 PM, Daniel Kulp wrote: > > > >> Thanks for this list. I’ve pulled these back (along with a couple > others > >> needed to get these to compile). The tests all pass. > >> > >> I’ll likely do the 5.11.2 builds tomorrow morning. If anyone has > anything > >> else they need, let me know ASAP! > >> > >> Thanks! > >> Dan > >> > >> > >> > >>> On Aug 3, 2015, at 3:50 PM, Christopher Shannon < > >> christopher.l.shan...@gmail.com> wrote: > >>> > >>> A couple of other bug candidates I thing would be good to include if > not > >>> already on the branch: > >>> > >>> AMQ-5674: 20832f1f1b5bf028d43256a8b2172f2795b0c02d > >>> AMQ-5742: c85fa67e1c65caecb96d3a044fbd5ac835cce3db > >>> AMQ-5787 : e99c8148301c6ff6b6ed529a26ba3337ef20d016 > >>> AMQ-5813: ea03bb1f8cb2bce97fabdaa8fa287f4c9f977a3a > >>> AMQ-5814 : e4af2eb63501251befc33a415abfad2b72d53321 > >>> > >>> > >>> > >>> On Mon, Aug 3, 2015 at 2:47 PM, Daniel Kulp wrote: > >>> > >>>> > >>>>> On Jul 30, 2015, at 11:06 AM, Christopher Shannon < > >>>> christopher.l.shan...@gmail.com> wrote: > >>>>> > >>>>> I checked Jira and there are over 100 bug issues against 5.12.0 that > >> have > >>>>> been resolved. I'm thinking that going forward it might make sense > to > >>>>> backport fixes when the tickets are resolved if it makes sense to do > >> so. > >>>> > >>>> I’d love to see that, but most of the people that have implemented > fixes > >>>> don’t seem to want to spend the time pulling them back to any of the > >> fixes > >>>> branches. :(As long as the people doing the fixes aren’t willing > >> to > >>>> do it, it becomes really tough as it’s more about asking other folks > to > >>>> take a look. That’s something even non-committers could do and help > >> out > >>>> with. In this case, I specifically asked for any fixes or git hashes > >> or > >>>> something to pull back and got exactly one. Not a good sign. > >>>> > >>>>> This won't work for all cases but it would cut down the work at > release > >>>>> time if some of the commits can be merged ahead of time. > >>>> > >>>> In any case, I do plan on doing the build on Wednesday or Thursday. > If > >>>> anyone would like something pulled back, please let me know. > >>>> > >>>> Thanks! > >>>> Dan > >>>> > >>>> > >>>> > >>>>> > >>>>> On Thu, Jul 30, 2015 at 10:56 AM, Daniel Kulp > >> wrote: > >>>>> > >>>>>> > >>>>>>> On Jul 30, 2015, at 10:44 AM, Paul Gale > >> wrote: > >>>>>>> > >>>>>>> If possible can AMQ-5903 be included in 5.11.2? It's only on master > >> at > >>>>>> the > >>>>>>> moment, e.g. destined for 5.12.0. > >>>>>> > >>>>>> Done… can you verify it’s on the branch properly and working? > >>>>>> > >>>>>> Dan > >>>>>> > >>>>>> > >>>>>>> > >>>>>>> Thanks, > >>>>>>> Paul > >>>>>>> > >>>>>>> On Thu, Jul 30, 2015 at 9:10 AM, Daniel Kulp > >> wrote: > >>>>>>> > >>>>>>>> It’s been a while since 5.11.1 so I’d like to get a 5.11.2 release > >> out > >>>>>>>> shortly, probably early/mid next week.There’s not a lot of > fixes > >>>> on > >>>>>> the > >>>>>>>> branch right now, just stuff mostly necessary for OSGi to support > >>>>>> running > >>>>>>>> ActiveMQ in Karaf4. > >>>>>>>> > >>>>>>>> If there are other fixes that people would like to get in, please > >> get > >>>>>> them > >>>>>>>> cherry-picked to the activemq-5.11.x branch or send me the git > >> hashes > >>>>>> and I > >>>>>>>> can take a look and get them merged. > >>>>>>>> > >>>>>>>> Thanks! > >>>>>>>> > >>>>>>>> -- > >>>>>>>> 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 > >>>>>> > >>>>>> > >>>> > >>>> -- > >>>> 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 > >> > >> > > -- > Daniel Kulp > dk...@apache.org - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com > >
Re: 5.11.2....
Can you add https://issues.apache.org/jira/browse/AMQ-5754 to the list? Regards -- Dejan Bosanac about.me/dejanb On Wed, Aug 5, 2015 at 3:28 PM, Daniel Kulp wrote: > Thanks for this list. I’ve pulled these back (along with a couple others > needed to get these to compile). The tests all pass. > > I’ll likely do the 5.11.2 builds tomorrow morning. If anyone has anything > else they need, let me know ASAP! > > Thanks! > Dan > > > > > On Aug 3, 2015, at 3:50 PM, Christopher Shannon < > christopher.l.shan...@gmail.com> wrote: > > > > A couple of other bug candidates I thing would be good to include if not > > already on the branch: > > > > AMQ-5674: 20832f1f1b5bf028d43256a8b2172f2795b0c02d > > AMQ-5742: c85fa67e1c65caecb96d3a044fbd5ac835cce3db > > AMQ-5787 : e99c8148301c6ff6b6ed529a26ba3337ef20d016 > > AMQ-5813: ea03bb1f8cb2bce97fabdaa8fa287f4c9f977a3a > > AMQ-5814 : e4af2eb63501251befc33a415abfad2b72d53321 > > > > > > > > On Mon, Aug 3, 2015 at 2:47 PM, Daniel Kulp wrote: > > > >> > >>> On Jul 30, 2015, at 11:06 AM, Christopher Shannon < > >> christopher.l.shan...@gmail.com> wrote: > >>> > >>> I checked Jira and there are over 100 bug issues against 5.12.0 that > have > >>> been resolved. I'm thinking that going forward it might make sense to > >>> backport fixes when the tickets are resolved if it makes sense to do > so. > >> > >> I’d love to see that, but most of the people that have implemented fixes > >> don’t seem to want to spend the time pulling them back to any of the > fixes > >> branches. :(As long as the people doing the fixes aren’t willing > to > >> do it, it becomes really tough as it’s more about asking other folks to > >> take a look. That’s something even non-committers could do and help > out > >> with. In this case, I specifically asked for any fixes or git hashes > or > >> something to pull back and got exactly one. Not a good sign. > >> > >>> This won't work for all cases but it would cut down the work at release > >>> time if some of the commits can be merged ahead of time. > >> > >> In any case, I do plan on doing the build on Wednesday or Thursday. If > >> anyone would like something pulled back, please let me know. > >> > >> Thanks! > >> Dan > >> > >> > >> > >>> > >>> On Thu, Jul 30, 2015 at 10:56 AM, Daniel Kulp > wrote: > >>> > >>>> > >>>>> On Jul 30, 2015, at 10:44 AM, Paul Gale > wrote: > >>>>> > >>>>> If possible can AMQ-5903 be included in 5.11.2? It's only on master > at > >>>> the > >>>>> moment, e.g. destined for 5.12.0. > >>>> > >>>> Done… can you verify it’s on the branch properly and working? > >>>> > >>>> Dan > >>>> > >>>> > >>>>> > >>>>> Thanks, > >>>>> Paul > >>>>> > >>>>> On Thu, Jul 30, 2015 at 9:10 AM, Daniel Kulp > wrote: > >>>>> > >>>>>> It’s been a while since 5.11.1 so I’d like to get a 5.11.2 release > out > >>>>>> shortly, probably early/mid next week.There’s not a lot of fixes > >> on > >>>> the > >>>>>> branch right now, just stuff mostly necessary for OSGi to support > >>>> running > >>>>>> ActiveMQ in Karaf4. > >>>>>> > >>>>>> If there are other fixes that people would like to get in, please > get > >>>> them > >>>>>> cherry-picked to the activemq-5.11.x branch or send me the git > hashes > >>>> and I > >>>>>> can take a look and get them merged. > >>>>>> > >>>>>> Thanks! > >>>>>> > >>>>>> -- > >>>>>> 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 > >>>> > >>>> > >> > >> -- > >> 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] Artemis Coding Style
+1 for the code style change. I find the code with curly braces on the new line more verbose than necessary and harder to read. Also, most IDEs defaults (IntelliJ for example) are set to in-line code style, so it’s easier to start coding. Regards -- Dejan Bosanac about.me/dejanb On Tue, Aug 4, 2015 at 5:35 PM, Clebert Suconic wrote: > I think I will start with what we have now by just switching the curls > to the same line.. Looking at our checkstyle they are not as strict as > CXF (the one mentioned here). > > We can improve later if needed without any problems. > > On Tue, Aug 4, 2015 at 11:28 AM, Daniel Kulp wrote: > > Lazy consensus is fine.Wait till tomorrow and if no one objects, > just do it. > > > > Dan > > > > > >> On Aug 4, 2015, at 11:24 AM, Clebert Suconic > wrote: > >> > >> Is this a just do it thing, or we need a vote? > >> > >> On Tue, Aug 4, 2015 at 10:07 AM, Timothy Bish > wrote: > >>> On 08/04/2015 07:56 AM, Christopher Shannon wrote: > >>>> So in general I'm not too picky with coding styles but I just started > >>>> looking at the Artemis project a few days ago and something that > stood out > >>>> to me right away was the use of opening curly braces on a new line. > >>>> > >>>> Virtually ever Java code base I've seen is written in the style using > the > >>>> opening brace on the same line. (See > >>>> > http://google.github.io/styleguide/javaguide.html#s4.1.2-blocks-k-r-style) > >>>> I think that in general it would be a good idea to match up to a style > >>>> that most Java developers are used to working with if we want to get > more > >>>> of the community involved. > >>>> > >>>> I was wondering if anyone would have an issue with changing the style > or > >>>> what people's thoughts are about this potential change? > >>>> > >>> +1 > >>> > >>> I think following the javaguide style would make the code much more > >>> approachable. > >>> > >>> -- > >>> Tim Bish > >>> Sr Software Engineer | RedHat Inc. > >>> tim.b...@redhat.com | www.redhat.com > >>> twitter: @tabish121 > >>> blog: http://timbish.blogspot.com/ > >>> > >> > >> > >> > >> -- > >> Clebert Suconic > > > > -- > > Daniel Kulp > > dk...@apache.org - http://dankulp.com/blog > > Talend Community Coder - http://coders.talend.com > > > > > > -- > Clebert Suconic >
Re: Please review: Unix Init Script Improvements - strange options "export" and "create"
Hi Marc, (comments inline) On Sat, Jul 4, 2015 at 8:18 AM, Marc Schöchlin wrote: > Hi Dejan, > > Am 02.07.2015 um 13:14 schrieb Dejan Bosanac: > > Hi Marc, > > > > these commands are not deprecated, they are documented (partially) here > > http://activemq.apache.org/unix-shell-script.html > > > > As far as I can see, export is still work in progress, it should work > like > > > > bin/activemq export --file=archive.tgz > > What is the usecase for this feature? > Is there als a "import" > There’s an import in Apollo broker and I assume we’ll create it for Artemis to ease the migration. > > Works not on my machine: > > $ ./activemq export --file=archive.tgz > INFO: Loading '/home/mschoechlin/myroot/apache-activemq-5.11.1//bin/env' > INFO: Using java '/home/mschoechlin/myroot/java8/bin/java' > Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar > Java Runtime: Oracle Corporation 1.8.0_45 > /home/mschoechlin/myroot/jdk1.8.0_45/jre > Heap sizes: current=62976k free=60999k max=932352k > JVM args: -javaagent:/usr/share/java/jayatanaag.jar -Xms64M -Xmx1G > -Djava.util.logging.config.file=logging.properties > > -Djava.security.auth.login.config=/home/mschoechlin/myroot/apache-activemq-5.11.1//conf/login.config > > -Dactivemq.classpath=/home/mschoechlin/myroot/apache-activemq-5.11.1//conf:/home/mschoechlin/myroot/apache-activemq-5.11.1//../lib/ > -Dactivemq.home=/home/mschoechlin/myroot/apache-activemq-5.11.1/ > -Dactivemq.base=/home/mschoechlin/myroot/apache-activemq-5.11.1/ > -Dactivemq.conf=/home/mschoechlin/myroot/apache-activemq-5.11.1//conf > -Dactivemq.data=/home/mschoechlin/myroot/apache-activemq-5.11.1//data > Extensions classpath: > > > [/home/mschoechlin/myroot/apache-activemq-5.11.1/lib,/home/mschoechlin/myroot/apache-activemq-5.11.1/lib/camel,/home/mschoechlin/myroot/apache-activemq-5.11.1/lib/optional,/home/mschoechlin/myroot/apache-activemq-5.11.1/lib/web,/home/mschoechlin/myroot/apache-activemq-5.11.1/lib/extra] > ACTIVEMQ_HOME: /home/mschoechlin/myroot/apache-activemq-5.11.1 > ACTIVEMQ_BASE: /home/mschoechlin/myroot/apache-activemq-5.11.1 > ACTIVEMQ_CONF: /home/mschoechlin/myroot/apache-activemq-5.11.1/conf > ACTIVEMQ_DATA: /home/mschoechlin/myroot/apache-activemq-5.11.1/data > ERROR | Could not set property file on > org.apache.activemq.console.command.store.StoreExporter@18bf3d14 > java.lang.IllegalArgumentException: Cannot convert from class > java.lang.String to class java.io.File with value archive.tgz > at > > org.apache.activemq.util.IntrospectionSupport.convert(IntrospectionSupport.java:219)[activemq-client-5.11.1.jar:5.11.1] > at > > org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:178)[activemq-client-5.11.1.jar:5.11.1] > at > > org.apache.activemq.console.command.store.amq.CommandLineSupport.setOptions(CommandLineSupport.java:81)[activemq-console-5.11.1.jar:5.11.1] > at > > org.apache.activemq.console.command.StoreExportCommand.execute(StoreExportCommand.java:51)[activemq-console-5.11.1.jar:5.11.1] > at > > org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:150)[activemq-console-5.11.1.jar:5.11.1] > at > > org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57)[activemq-console-5.11.1.jar:5.11.1] > at > > org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:104)[activemq-console-5.11.1.jar:5.11.1] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method)[:1.8.0_45] > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_45] > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_45] > at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_45] > at > > org.apache.activemq.console.Main.runTaskClass(Main.java:262)[activemq.jar:5.11.1] > at > org.apache.activemq.console.Main.main(Main.java:115)[activemq.jar:5.11.1] > ERROR: java.lang.Exception: Unexpected arguments: [--file=archive.tgz] > java.lang.Exception: Unexpected arguments: [--file=archive.tgz] > at > > org.apache.activemq.console.command.StoreExportCommand.execute(StoreExportCommand.java:53) > at > > org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:150) > at > > org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57) > at > > org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > > sun.reflect.NativeMethodAccessorImpl.invoke(Na
Re: Please review: Unix Init Script Improvements - strange options "export" and "create"
Hi Marc, these commands are not deprecated, they are documented (partially) here http://activemq.apache.org/unix-shell-script.html As far as I can see, export is still work in progress, it should work like bin/activemq export --file=archive.tgz Create command is often used and it can be used like bin/activemq create test-broker BTW. While you at it, you might wanna take a peak at this PR https://github.com/apache/activemq/pull/109 and maybe close your original PR for improvements. Regards -- Dejan Bosanac about.me/dejanb On Tue, Jun 30, 2015 at 9:04 AM, Marc Schöchlin wrote: > Hi, > > i had a look for the "export" feature of activemq. > > The documentation and the wiki search does not provide information about > usage of this feature - the only information is : "Exports a stopped > brokers data files to an archive file". > Invoking this functionality raised strage error messages: > > $ ./activemq export > INFO: Loading '/home/mschoechlin/myroot/apache-activemq-5.11.1//bin/env' > INFO: Using java '/home/mschoechlin/myroot/java8/bin/java' > Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar > Java Runtime: Oracle Corporation 1.8.0_45 > /home/mschoechlin/myroot/jdk1.8.0_45/jre > Heap sizes: current=62976k free=60999k max=932352k > JVM args: -javaagent:/usr/share/java/jayatanaag.jar -Xms64M -Xmx1G > -Djava.util.logging.config.file=logging.properties > -Djava.security.auth.login.config=/home/mschoechlin/myroot/apache-activemq-5.11.1//conf/login.config > -Dactivemq.classpath=/home/mschoechlin/myroot/apache-activemq-5.11.1//conf:/home/mschoechlin/myroot/apache-activemq-5.11.1//../lib/ > -Dactivemq.home=/home/mschoechlin/myroot/apache-activemq-5.11.1/ > -Dactivemq.base=/home/mschoechlin/myroot/apache-activemq-5.11.1/ > -Dactivemq.conf=/home/mschoechlin/myroot/apache-activemq-5.11.1//conf > -Dactivemq.data=/home/mschoechlin/myroot/apache-activemq-5.11.1//data > Extensions classpath: > > [/home/mschoechlin/myroot/apache-activemq-5.11.1/lib,/home/mschoechlin/myroot/apache-activemq-5.11.1/lib/camel,/home/mschoechlin/myroot/apache-activemq-5.11.1/lib/optional,/home/mschoechlin/myroot/apache-activemq-5.11.1/lib/web,/home/mschoechlin/myroot/apache-activemq-5.11.1/lib/extra] > ACTIVEMQ_HOME: /home/mschoechlin/myroot/apache-activemq-5.11.1 > ACTIVEMQ_BASE: /home/mschoechlin/myroot/apache-activemq-5.11.1 > ACTIVEMQ_CONF: /home/mschoechlin/myroot/apache-activemq-5.11.1/conf > ACTIVEMQ_DATA: /home/mschoechlin/myroot/apache-activemq-5.11.1/data > ERROR: java.lang.Exception: *required --file option missing* > java.lang.Exception: required --file option missing > at > org.apache.activemq.console.command.store.StoreExporter.execute(StoreExporter.java:80) > at > org.apache.activemq.console.command.StoreExportCommand.execute(StoreExportCommand.java:55) > at > org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:150) > at > org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57) > at > org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.apache.activemq.console.Main.runTaskClass(Main.java:262) > at org.apache.activemq.console.Main.main(Main.java:115) > > $ ./activemq export *--file /tmp/foobar* > INFO: Loading '/home/mschoechlin/myroot/apache-activemq-5.11.1//bin/env' > INFO: Using java '/home/mschoechlin/myroot/java8/bin/java' > Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar > Java Runtime: Oracle Corporation 1.8.0_45 > /home/mschoechlin/myroot/jdk1.8.0_45/jre > Heap sizes: current=62976k free=60999k max=932352k > JVM args: -javaagent:/usr/share/java/jayatanaag.jar -Xms64M -Xmx1G > -Djava.util.logging.config.file=logging.properties > -Djava.security.auth.login.config=/home/mschoechlin/myroot/apache-activemq-5.11.1//conf/login.config > -Dactivemq.classpath=/home/mschoechlin/myroot/apache-activemq-5.11.1//conf:/home/mschoechlin/myroot/apache-activemq-5.11.1//../lib/ > -Dactivemq.home=/home/mschoechlin/myroot/apache-activemq-5.11.1/ > -Dactivemq.base=/home/mschoechlin/myroot/apache-activemq-5.11.1/ > -Dactivemq.conf=/home/mschoechlin/myroot/apache-activemq-5.11.1//conf > -Dactivemq.data=/home/mschoechlin/myroot/apache-activemq-5.11.1//data > Extensions classpath: > > [/home/mschoechlin/myroot/apache-activemq-5.11.1/lib,/home/mschoechlin/myroot/apache-activemq-5.11.1/lib
Re: [VOTE] Apache Artemis 1.0.0 (RC3)
+1 Regards -- Dejan Bosanac -- Red Hat, Inc. dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/ On Fri, May 22, 2015 at 8:28 PM, Timothy Bish wrote: > +1 > > On 05/21/2015 12:38 PM, Martyn Taylor wrote: > > Hello all. > > > > I've cut a third release candidate of Apache Artemis 1.0.0, addressing > > the RC2 feedback from community members. > > > > This is a first release of the Artemis project with protocol support > > for AMQP, STOMP, CORE, HORNETQ and OPENWIRE (alpha). > > > > N.B. The OpenWire implementation is at alpha with support for ActiveMQ > > JMS clients and basic transport. More advanced features will be added > > progressively over the next series of releases. > > > > > > The release notes can be found here: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920&version=12328953 > > > > > > The binary distributions can be found here: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1060/org/apache/activemq/apache-artemis/1.0.0/ > > > > > > The source archives can be found here: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1060/org/apache/activemq/apache-artemis/1.0.0/ > > > > > > The Maven repository is here: > > > https://repository.apache.org/content/repositories/orgapacheactivemq-1060/ > > > > > > 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 > > > > > -- > Tim Bish > Sr Software Engineer | RedHat Inc. > tim.b...@redhat.com | www.redhat.com > twitter: @tabish121 > blog: http://timbish.blogspot.com/ > >
[jira] [Resolved] (AMQ-5744) Password encryption is broken in OSGi
[ https://issues.apache.org/jira/browse/AMQ-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-5744. Resolution: Fixed Fixed with http://git-wip-us.apache.org/repos/asf/activemq/commit/b8698953 I incidentally upgraded jasypt-spring3 to jasypt-spring31 for the standalone distribution as well > Password encryption is broken in OSGi > - > > Key: AMQ-5744 > URL: https://issues.apache.org/jira/browse/AMQ-5744 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.11.0 > Reporter: Dejan Bosanac > Assignee: Dejan Bosanac > Fix For: 5.12.0 > > > We're missing jasypt-spring31 bundle in the feature definition. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMQ-5744) Password encryption is broken in OSGi
Dejan Bosanac created AMQ-5744: -- Summary: Password encryption is broken in OSGi Key: AMQ-5744 URL: https://issues.apache.org/jira/browse/AMQ-5744 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.11.0 Reporter: Dejan Bosanac Assignee: Dejan Bosanac Fix For: 5.12.0 We're missing jasypt-spring31 bundle in the feature definition. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMQ-5734) Support MQTT 3.1 silent subscription fail
[ https://issues.apache.org/jira/browse/AMQ-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-5734. Resolution: Fixed Fixed with http://git-wip-us.apache.org/repos/asf/activemq/commit/a4fbe708 > Support MQTT 3.1 silent subscription fail > - > > Key: AMQ-5734 > URL: https://issues.apache.org/jira/browse/AMQ-5734 > Project: ActiveMQ > Issue Type: Improvement > Components: MQTT >Affects Versions: 5.11.0 > Reporter: Dejan Bosanac > Assignee: Dejan Bosanac > Fix For: 5.12.0 > > > There's a difference in what 3.1 and 3.1.1 specs say should happen when an > unauthorised subscribe happens. In 3.1, the broker don't informs the client > so it just silently ignores the problem. In 3.1.1 it sends special QoS back. > We currently only implement the later. We need to implement also 3.1 > behaviour for older clients. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMQ-5734) Support MQTT 3.1 silent subscription fail
Dejan Bosanac created AMQ-5734: -- Summary: Support MQTT 3.1 silent subscription fail Key: AMQ-5734 URL: https://issues.apache.org/jira/browse/AMQ-5734 Project: ActiveMQ Issue Type: Improvement Components: MQTT Affects Versions: 5.11.0 Reporter: Dejan Bosanac Assignee: Dejan Bosanac Fix For: 5.12.0 There's a difference in what 3.1 and 3.1.1 specs say should happen when an unauthorised subscribe happens. In 3.1, the broker don't informs the client so it just silently ignores the problem. In 3.1.1 it sends special QoS back. We currently only implement the later. We need to implement also 3.1 behaviour for older clients. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMQ-5721) Update AMQ to commons-pool2
[ https://issues.apache.org/jira/browse/AMQ-5721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-5721. Resolution: Fixed Assignee: Dejan Bosanac Pull request merged. Thanks I triggered a new build of https://builds.apache.org/job/ActiveMQ-Java7/ which should definitely give us an answer if there are any regressions (local build was fine). Can you close PR, as I merged your remote, so there's no commit that will close it automatically? > Update AMQ to commons-pool2 > --- > > Key: AMQ-5721 > URL: https://issues.apache.org/jira/browse/AMQ-5721 > Project: ActiveMQ > Issue Type: Bug >Reporter: Jeff Genender > Assignee: Dejan Bosanac > Fix For: 5.12.0 > > > Update ActiveMQ to use commons-pool2 instead of commons-pool. AMQ-5636 will > need it. The JMS pool and other components should use it as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMQ-5724) Query command don't filter properly
[ https://issues.apache.org/jira/browse/AMQ-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-5724. Resolution: Fixed Fixed with http://git-wip-us.apache.org/repos/asf/activemq/commit/eece06b3 > Query command don't filter properly > > > Key: AMQ-5724 > URL: https://issues.apache.org/jira/browse/AMQ-5724 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.11.0 > Reporter: Dejan Bosanac >Assignee: Dejan Bosanac > Fix For: 5.12.0 > > > --xobjname parameter is not taken into account and --view parameter doesn't > show attributes in any meaningful order -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMQ-5724) Query command don't filter properly
Dejan Bosanac created AMQ-5724: -- Summary: Query command don't filter properly Key: AMQ-5724 URL: https://issues.apache.org/jira/browse/AMQ-5724 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.11.0 Reporter: Dejan Bosanac Assignee: Dejan Bosanac Fix For: 5.12.0 --xobjname parameter is not taken into account and --view parameter doesn't show attributes in any meaningful order -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Pick a code name for the HornetQ code donation
+1 [c] ActiveMQ Reactive Regards -- Dejan Bosanac -- Red Hat, Inc. dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/ On Wed, Apr 15, 2015 at 11:10 AM, Martyn Taylor wrote: > +1 [c] ActiveMQ Reactive > > On 14/04/15 16:42, Hiram Chirino 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 >> >> >
[jira] [Resolved] (AMQ-4929) remove old and unused org.apache.activemq.broker.BrokerService#setSupportFailOver
[ https://issues.apache.org/jira/browse/AMQ-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-4929. Resolution: Fixed Assignee: Dejan Bosanac This is now fixed with http://git-wip-us.apache.org/repos/asf/activemq/commit/2852a8bd The property should have been moved when we removed pure master-slave functionality https://issues.apache.org/jira/browse/AMQ-4165 > remove old and unused > org.apache.activemq.broker.BrokerService#setSupportFailOver > - > > Key: AMQ-4929 > URL: https://issues.apache.org/jira/browse/AMQ-4929 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.9.0 >Reporter: Gary Tully >Assignee: Dejan Bosanac > Fix For: 5.12.0 > > > there is a bunch of duplicate detection in transactionbroker that is disabled > by default and not tested that duplicates work done elsewhere - store and > producerAutit. It should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMQ-5718) Prevent adding a message to topic subscriber while we're discarding a message
[ https://issues.apache.org/jira/browse/AMQ-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-5718. Resolution: Fixed Fixed with http://git-wip-us.apache.org/repos/asf/activemq/commit/2562cf21 > Prevent adding a message to topic subscriber while we're discarding a message > - > > Key: AMQ-5718 > URL: https://issues.apache.org/jira/browse/AMQ-5718 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.11.0 > Reporter: Dejan Bosanac >Assignee: Dejan Bosanac > Fix For: 5.12.0 > > > These additional messages can only be advisories generated in the process, > which can cause more messages to get discarded and generate a recursive loop > with StackOverflow exception as the end result. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMQ-5718) Prevent adding a message to topic subscriber while we're discarding a message
Dejan Bosanac created AMQ-5718: -- Summary: Prevent adding a message to topic subscriber while we're discarding a message Key: AMQ-5718 URL: https://issues.apache.org/jira/browse/AMQ-5718 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.11.0 Reporter: Dejan Bosanac Assignee: Dejan Bosanac Fix For: 5.12.0 These additional messages can only be advisories generated in the process, which can cause more messages to get discarded and generate a recursive loop with StackOverflow exception as the end result. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMQ-5665) memory store is broken in 5.11.0 for advisories (and probably other issues as well)
[
https://issues.apache.org/jira/browse/AMQ-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac resolved AMQ-5665.
Resolution: Fixed
Fix Version/s: 5.12.0
Assignee: Dejan Bosanac
I ran into this writing a test for advisories
http://git-wip-us.apache.org/repos/asf/activemq/commit/69767a2f fixes it
The test for another issue I'm working on will be used to verify and guard the
fix
> memory store is broken in 5.11.0 for advisories (and probably other issues as
> well)
> ---
>
> Key: AMQ-5665
> URL: https://issues.apache.org/jira/browse/AMQ-5665
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.11.0
>Reporter: Kevin Burton
>Assignee: Dejan Bosanac
> Fix For: 5.12.0
>
>
> We're running 5.10.2 and don't encounter this issue. We're running a
> non-persistent broker in production and testing so that's why we found this
> issue.
> It looks like 5.11.0 introduced this issue.
> Essentially Advisories fail to fire.
> It looks like it’s a bug with MemoryTransactionStore. Switching to persistent
> brokers fixes the problem.
> It’s because addMessage calls:
> } else {
> destination.addMessage(null, message);
> }
> .. with an explicit null.
> the message given is:
> 2015-03-16 12:54:17,538 WARN [ActiveMQ Transport:
> tcp:///127.0.0.1:56468@16161] org.apache.activemq.advisory.AdvisoryBroker
> Failed to fire delivered advisory, reason: java.lang.NullPointerException
> … and I saw this when I was running mvn test in the main ActiveMQ test suite
> (or at least pretty sure I did) so this is happening not just in my code.
> The full exception , which I captured by setting a break point is below.
> java.lang.NullPointerException
> at
> org.apache.activemq.advisory.AdvisoryBroker.fireAdvisory(AdvisoryBroker.java:626)
> at
> org.apache.activemq.advisory.AdvisoryBroker.messageDelivered(AdvisoryBroker.java:397)
> at
> org.apache.activemq.broker.BrokerFilter.messageDelivered(BrokerFilter.java:349)
> at
> org.apache.activemq.broker.BrokerFilter.messageDelivered(BrokerFilter.java:349)
> at
> org.apache.activemq.broker.MutableBrokerFilter.messageDelivered(MutableBrokerFilter.java:360)
> at
> org.apache.activemq.broker.MutableBrokerFilter.messageDelivered(MutableBrokerFilter.java:360)
> at
> org.apache.activemq.broker.region.BaseDestination.messageDelivered(BaseDestination.java:518)
> at org.apache.activemq.broker.region.Queue.messageSent(Queue.java:1806)
> at
> org.apache.activemq.broker.region.Queue.doPendingCursorAdditions(Queue.java:794)
> at
> org.apache.activemq.broker.region.Queue.orderedCursorAdd(Queue.java:875)
> at org.apache.activemq.broker.region.Queue.doMessageSend(Queue.java:854)
> at org.apache.activemq.broker.region.Queue.send(Queue.java:733)
> at
> org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:419)
> at
> org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:468)
> at
> org.apache.activemq.broker.jmx.ManagedRegionBroker.send(ManagedRegionBroker.java:297)
> at org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:152)
> at
> org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:96)
> at
> org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:307)
> at
> org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:157)
> at
> org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:157)
> at
> org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:541)
> at
> org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:768)
> at
> org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:334)
> at
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:188)
> at
> org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
> at
> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
> at
> org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:270)
> at
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
> at
> org.apache.activemq.transport.tcp.TcpTransport.doR
Re: [DISCUSS] dev mailing list is cluttered
+1 for separate lists
Regards
--
Dejan Bosanac
--
Red Hat, Inc.
dbosa...@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/
On Tue, Apr 7, 2015 at 11:56 PM, Jim Gomes wrote:
> +1 for lazy consensus.
>
> On Tue, Apr 7, 2015, 1:44 PM James Carman
> 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
> > 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
> > 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 > >>> >>> > 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
> > 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\@4VYY9&5R\"F)R=6-E+G-N>61E > "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\@4VYY9&5R\"F)R=6-E+G-N>61E > );'
> > >>
> > >> 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
> >
>
[jira] [Resolved] (AMQ-5710) ActiveMQConnection cleanup should not close the connection on the broker
[ https://issues.apache.org/jira/browse/AMQ-5710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-5710. Resolution: Fixed Fixed with http://git-wip-us.apache.org/repos/asf/activemq/commit/c705523c > ActiveMQConnection cleanup should not close the connection on the broker > > > Key: AMQ-5710 > URL: https://issues.apache.org/jira/browse/AMQ-5710 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.11.0 > Reporter: Dejan Bosanac > Assignee: Dejan Bosanac > Fix For: 5.12.0 > > > As the spec says > http://docs.oracle.com/javaee/6/api/javax/resource/spi/ManagedConnection.html#cleanup() > "The cleanup of ManagedConnection instance resets its client specific state > and prepares the connection to be put back in to a connection pool. The > cleanup method should not cause resource adapter to close the physical pipe > and reclaim system resources associated with the physical connection." > We should not send RemoveInfo on cleanup, but just clean client side state. > The result of "closing" a connection on cleanup is that connection will not > be cached when using XA transactions, causing high CPU usage on the broker. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMQ-5710) ActiveMQConnection cleanup should not close the connection on the broker
Dejan Bosanac created AMQ-5710: -- Summary: ActiveMQConnection cleanup should not close the connection on the broker Key: AMQ-5710 URL: https://issues.apache.org/jira/browse/AMQ-5710 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.11.0 Reporter: Dejan Bosanac Assignee: Dejan Bosanac Fix For: 5.12.0 As the spec says http://docs.oracle.com/javaee/6/api/javax/resource/spi/ManagedConnection.html#cleanup() "The cleanup of ManagedConnection instance resets its client specific state and prepares the connection to be put back in to a connection pool. The cleanup method should not cause resource adapter to close the physical pipe and reclaim system resources associated with the physical connection." We should not send RemoveInfo on cleanup, but just clean client side state. The result of "closing" a connection on cleanup is that connection will not be cached when using XA transactions, causing high CPU usage on the broker. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMQ-5697) Authorization map doesn't handle composite destinations properly
[
https://issues.apache.org/jira/browse/AMQ-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac resolved AMQ-5697.
Resolution: Fixed
Fixed with http://git-wip-us.apache.org/repos/asf/activemq/commit/8bb58036
> Authorization map doesn't handle composite destinations properly
>
>
> Key: AMQ-5697
> URL: https://issues.apache.org/jira/browse/AMQ-5697
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.11.0
> Reporter: Dejan Bosanac
>Assignee: Dejan Bosanac
> Fix For: 5.12.0
>
>
> If two destinations are specified explicitly in the authorization map, like
> {code}admin="admins"/>
> admin="admins"/> {code}
> trying to connect to the composite destination "QUEUEA,QUEUEB" will fail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMQ-5697) Authorization map doesn't handle composite destinations properly
Dejan Bosanac created AMQ-5697:
--
Summary: Authorization map doesn't handle composite destinations
properly
Key: AMQ-5697
URL: https://issues.apache.org/jira/browse/AMQ-5697
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.11.0
Reporter: Dejan Bosanac
Assignee: Dejan Bosanac
Fix For: 5.12.0
If two destinations are specified explicitly in the authorization map, like
{code}
{code}
trying to connect to the composite destination "QUEUEA,QUEUEB" will fail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMQ-5008) Support for certificate revocation checking (with patch)
[
https://issues.apache.org/jira/browse/AMQ-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac resolved AMQ-5008.
Resolution: Fixed
Fix Version/s: 5.12.0
Assignee: Dejan Bosanac
This is now fixed with
http://git-wip-us.apache.org/repos/asf/activemq/commit/0fd174b9
More docs available at:
http://activemq.apache.org/how-do-i-use-ssl.html#HowdoIuseSSL-Certificaterevocation
> Support for certificate revocation checking (with patch)
>
>
> Key: AMQ-5008
> URL: https://issues.apache.org/jira/browse/AMQ-5008
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Connector
>Reporter: Michal Růžička
> Assignee: Dejan Bosanac
>Priority: Minor
> Fix For: 5.12.0
>
> Attachments: CRL_checking.patch
>
>
> Currently it's possible to require client authentication during SSL/TLS
> handshake by adding {{needClientAuth=true}} query string to the respective
> connector URI. But it is not possible to configure revocation checking of the
> certificate submitted by the client.
> The attached patch adds the capability by introducing a new attribute -
> {{crl}} - of the {{org.apache.activemq.spring.SpringSslContext}} class and
> updating the
> {{org.apache.activemq.spring.SpringSslContext.createTrustManagers()}} method
> to make use of the value specified for the attribute in the corresponding
> {{}} tag as appropriate.
> The code is inspired by a similar code in jetty webserver:
> https://github.com/eclipse/jetty.project/blob/release-9/jetty-util/src/main/java/org/eclipse/jetty/util/ssl/SslContextFactory.java#L927-L965
> Please consider it for merging.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMQ-5558) Make activemq-client jar executable and able to send/receive messages
[
https://issues.apache.org/jira/browse/AMQ-5558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac updated AMQ-5558:
---
Fix Version/s: 5.12.0
> Make activemq-client jar executable and able to send/receive messages
> -
>
> Key: AMQ-5558
> URL: https://issues.apache.org/jira/browse/AMQ-5558
> Project: ActiveMQ
> Issue Type: New Feature
>Affects Versions: 5.11.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.12.0
>
>
> It would be nice to have basic verification/example tool builded directly in
> activemq-client.jar, so that folks can do something like
> {code}java -jar lib/activemq-client-xxx.jar producer
> java -jar lib/activemq-client-xxx.jar consumer{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMQ-5558) Make activemq-client jar executable and able to send/receive messages
[
https://issues.apache.org/jira/browse/AMQ-5558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac resolved AMQ-5558.
Resolution: Fixed
All the features are now in and the usage has been documented here
http://activemq.apache.org/version-5-examples.html
The old examples are just deprecated for now (I added a line into readme) and I
opened an issue to remove them in the future version
(https://issues.apache.org/jira/browse/AMQ-5687)
> Make activemq-client jar executable and able to send/receive messages
> -
>
> Key: AMQ-5558
> URL: https://issues.apache.org/jira/browse/AMQ-5558
> Project: ActiveMQ
> Issue Type: New Feature
>Affects Versions: 5.11.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
>
> It would be nice to have basic verification/example tool builded directly in
> activemq-client.jar, so that folks can do something like
> {code}java -jar lib/activemq-client-xxx.jar producer
> java -jar lib/activemq-client-xxx.jar consumer{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMQ-5687) Remove old ant-based examples
Dejan Bosanac created AMQ-5687: -- Summary: Remove old ant-based examples Key: AMQ-5687 URL: https://issues.apache.org/jira/browse/AMQ-5687 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.12.0 Reporter: Dejan Bosanac Assignee: Dejan Bosanac Fix For: 5.13.0 With the work on https://issues.apache.org/jira/browse/AMQ-5558, we provided better alternative and deprecated the old examples for 5.12. So, in 5.13 we can remove them from the code base. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Apache ActiveMQ 6.0.0 (RC3)
Even after 6.0 is released (using any of these development paths), 5.x and 6.x will continue to coexists for a long while as many folks wouldn’t want to move for one reason or another. And that’s normal thing in this kind of projects. For example take a look at Tomcat, where at this moment you can download 6.x, 7.x and 8.x (and 9.x is coming), all active. The main thing to do is to document all this properly, so users can make informed decisions on what they want/need. Regards -- Dejan Bosanac -- Red Hat, Inc. dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/ On Fri, Mar 20, 2015 at 4:34 PM, Timothy Bish wrote: > On 03/20/2015 11:17 AM, Daniel Kulp wrote: > >> How is this any different than say CXF 2.7.x to CXF 3.0.x? Both >> versions use the same maven coordinates.Or Karaf 2.x -> 3.x -> 4.x? >> > +1 was wondering the same thing > > My opinion is that if this is intended to eventually be a “6.0” of >> ActiveMQ, then lets keep going that direction. That said, if it’s not >> ready to be a full replacement, then give it a slightly different naming, >> like “6.0.0-M1” for milestone 1 or similar. I guess that would be my >> preference. Until we have all the migration issues hammered out and and >> feature replacements in place, (and OSGi support) I’m kind uncomfortable >> calling it 6.0. However, a "release milestone” along that path is still a >> good idea to get people working on it. >> >> Dan >> > +1 milestone releases would seem to make it clear where it's going > > >> On Mar 19, 2015, at 8:57 PM, artnaseef wrote: >>> >>> I will continue to look at this as I can find time. >>> >>> One question I'm seeing now - the artifact naming is using activemq- for >>> the >>> prefix, and a greater concern is the overlap of the artifacts like the >>> followin: >>> >>> * activemq-ra >>> * activemq-web >>> >>> I'm concerned that Maven central will have two sets of artifacts with the >>> activemq name, which will lead to confusion for users. And, I'm >>> especially >>> concerned that two totally different artifacts with the same name will >>> be in >>> maven central. >>> >>> Until HornetQ becomes a replacement for ActiveMQ and we decide to stop >>> maintaining ActiveMQ, I'm concerned that we need to avoid this type of >>> confusion. >>> >>> >>> >>> -- >>> View this message in context: http://activemq.2283324.n4. >>> nabble.com/VOTE-Apache-ActiveMQ-6-0-0-tp4692911p4693512.html >>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >>> >> > > -- > Tim Bish > Sr Software Engineer | RedHat Inc. > tim.b...@redhat.com | www.redhat.com > skype: tabish121 | twitter: @tabish121 > blog: http://timbish.blogspot.com/ > >
Re: ActiveMQ 6.0.0 required Java 8?
Hi Kevin, 5.x is not dead. HornetQ JMS engine has a good architecture and performances and was donated to ActiveMQ project so we can join efforts in creating a next generation broker that will be faster and more stable. It is not a drop-in replacement for the current 5.x. So the development of 6.x and 5.x will continue in parallel for a long while. There has been work already done on 6.x compatibility with the current ActiveMQ clients, but that’s just a start. We should document all this and lay the roadmap for future development soon after the release. Regards -- Dejan Bosanac -- Red Hat, Inc. dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/ On Thu, Mar 19, 2015 at 5:35 AM, Kevin Burton wrote: > Why call it ActiveMQ 6.0 and not HornetMQ (or another name)? > > Is hornetq a fork of ActiveMQ ? > > We’re still having issues with ActiveMQ and the idea of migrating to > another projects sounds like a nightmare for us. > > There are people using the current code base of ActiveMQ and this means > that 5.x is dead. > > Unless I’m missing something. Which I hope I am :) > > I’ll try to do a lot more reading on the subject and ActiveMQ 6.0.. maybe > it will solve all my problems :) > > On Wed, Mar 18, 2015 at 8:05 PM, Clebert Suconic < > clebert.suco...@gmail.com> > wrote: > > > as we said on the vote thread, activemq6 is This is a first release of > > the HornetQ code donation with support for AMQP, STOMP, CORE and > > OPENWIRE. > > > > It's a new dev effort and it's from a different repo: > > https://github.com/apache/activemq-6/ > > > > So I don't think the issue you mentioned would affect the new repo / > > codebase. > > > > We are being quite active on moving forward with this codebase and we > > are striving and working hard here. So any issues please let us know. > > > > On Wed, Mar 18, 2015 at 10:18 PM, Kevin Burton > wrote: > > > Yes. Sort of. There was a regression for persistent=false which > breaks > > it > > > for advisories. > > > > > > https://issues.apache.org/jira/browse/AMQ-5665 > > > > > > I was *hoping* it fixed the issue. > > > > > > If it doesn’t I was going to write a test and then git bisect to find > > where > > > it broke. > > > > > > One other problem I ran into: > > > > > > https://github.com/apache/activemq > > > > > > Does not have the source for 6.0.0 (unless I’m missing something.) > > > > > > master is 5.11 snapshot and there are no 6.0.0 branches.. > > > > > > The other issue I had, was that a lot of the modules changed. So I was > > > trying to track down the source to figure out which modules have been > > > renamed but of course I can’t find the source :-P > > > > > > We’re still trying to deploy a pretty large ActiveMQ install. Right > now > > > it’s on 8 servers and has about 80GB of messages. 5.10.x has had a > > number > > > of issues for us. I fixed two significant ones but they weren’t merged > > for > > > 6.0.0. The pull request was for 5.10.x and 5.11.x but it seems to have > > > been left behind? It was about 2 days worth of work and fixes a pretty > > > major scalability issue for ActiveMQ with a large number of queues. > > > > > > I’m also pretty convinced I’ve found another bug whereby the entire > queue > > > serves messages at about 1/100th the correct speed and queues grow very > > > large with nothing being served. I was going to try to get on 5.11 or > > > 6.0.0 but I can’t with the above bug in advisories. > > > > > > I don’t mind stepping in and fixing these issues btw. But I need to > > figure > > > out the right way to contribute so my pull requests don’t go into > > > purgatory. Not pointing figures.. I just need to figure out a way to > > avoid > > > having my work left behind. > > > > > > Maybe officially rejecting the pull request with a reason would help? > > > > > > Purgatory and lost work seems to be a far worst situation than a ‘no, > > we’re > > > not going to merge that because of X’ because I can fix this situation! > > :) > > > > > > If I know how to resolve these I’ll take my patches out of the > graveyard > > > and port them to 6.0.0 and then get the AMQ-5665 fixed and get a pull > > > request for that as well. > > > > > > Kevin > > > > > > > > > > > &
[jira] [Resolved] (AMQ-5674) initialRedeliveryDelay not respected
[ https://issues.apache.org/jira/browse/AMQ-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-5674. Resolution: Fixed Fixed with http://git-wip-us.apache.org/repos/asf/activemq/commit/20832f1f > initialRedeliveryDelay not respected > > > Key: AMQ-5674 > URL: https://issues.apache.org/jira/browse/AMQ-5674 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.11.0 > Reporter: Dejan Bosanac > Assignee: Dejan Bosanac > Fix For: 5.12.0 > > > Setting initialRedeliveryDelay on redelivery policy is not used in some use > cases. In case of a session rollback, the delay is wrongly calculated as > redelivery counter is incremented before. Also, according to the docs > redeliveryDelay should only be used if initialRedeliveryDelay = 0, which is > not the case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMQ-5674) initialRedeliveryDelay not respected
Dejan Bosanac created AMQ-5674: -- Summary: initialRedeliveryDelay not respected Key: AMQ-5674 URL: https://issues.apache.org/jira/browse/AMQ-5674 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.11.0 Reporter: Dejan Bosanac Assignee: Dejan Bosanac Fix For: 5.12.0 Setting initialRedeliveryDelay on redelivery policy is not used in some use cases. In case of a session rollback, the delay is wrongly calculated as redelivery counter is incremented before. Also, according to the docs redeliveryDelay should only be used if initialRedeliveryDelay = 0, which is not the case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Apache ActiveMQ 6.0.0 (RC3)
Hi, I’ve checked release candidate: - Checked the signature - Built the source release - Checked dependencies - Ran the broker - Ran 5.x client against it - Checked JMX, Jolokia APIs - Ran couple of examples - Checked docs, web site, Javadocs It all looks good from here. Great work. +1 Regards -- Dejan Bosanac -- Red Hat, Inc. dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/ On Tue, Mar 17, 2015 at 10:26 AM, Martyn Taylor wrote: > Hello all. > > I've cut a third release candidate of Apache ActiveMQ 6.0.0, addressing > the RC2 feedback from community members. > > This is a first release of the HornetQ code donation with support for > AMQP, STOMP, CORE and OPENWIRE. > > The release notes can be found here: > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > projectId=12315920&version=12328953 > > The binary distributions can be found here: > https://repository.apache.org/content/repositories/ > orgapacheactivemq-1038/org/apache/activemq/apache-activemq/6.0.0/ > > The source archives can be found here: > https://repository.apache.org/content/repositories/ > orgapacheactivemq-1038/org/apache/activemq/apache-activemq/6.0.0/ > > The Maven repository is here: > https://repository.apache.org/content/repositories/orgapacheactivemq-1038/ > > The source tag: > https://git-wip-us.apache.org/repos/asf?p=activemq-6.git;a= > tag;h=refs/tags/6.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 ActiveMQ 6.0.0 > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Here's my (non-binding) +1 > > Regards > > Martyn >
Re: ActiveMQ DSLs
Yup, Jira + pull request is a good start
Regards
--
Dejan Bosanac
--
Red Hat, Inc.
dbosa...@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/
On Tue, Mar 17, 2015 at 11:59 AM, Jakub Korab
wrote:
> Just taking a look through the source tree, given that all the tests are
> in activemq-unit-tests, it doesn't make a structural difference. Keeping it
> external might make sense as it would be an optional extra.
>
> I also have a test DSL as a sub-project of my source tree that uses JUnit
> 4.11 (same version as used by ActiveMQ) @Rule annotations, which get the
> test runner to manage the lifecycle of the DSL-defined broker (as opposed
> to writing the same setUp() and tearDown() methods all the time). It allows
> lookups of transport connector URIs for easy ConnectionFactory
> instantiation, and also does transparent network proxying via a SocketProxy.
>
> |public class MyEmbeddedBrokerTest {
> @Rule
> public ProxiedBrokerResource broker = new BrokerResource(
> ActiveMQBrokers.broker("embeddedBroker").useJmx(false)
> .persistent(false)
> .transportConnectors()
> .transportConnector("openwire", "tcp://0.0.0.0:61616
> ").end()
> .transportConnector("stomp", "stomp://0.0.0.0:61618
> ").end()
> .end())
> .withProxied("openwire").port(1); // port to be proxied
> is looked up by name
> // you can define multiple proxies for the one broker!
>
> @Test
> public void testNetworkOutages() {
> ConnectionFactory cf =
> new ActiveMQConnectionFactory(
> "failover:(" + broker.getTcpConnectionUri("openwire") +
> ")"); // returns proxied port 1
> // ...
> SocketProxy socketProxy = broker.getProxy("openwire");
> socketProxy.close(); // network goes down
> // ...
> socketProxy.reopen(); // network comes back up
> }
> }|
>
>
> I would like to drop it in to an activemq-test-dsl project - that would
> allow its use in unit tests, as well as by anyone external who would like
> to make use of it. Does that sound good?
>
> I think that the general consensus is to go ahead. How do I go about doing
> this? Should I log in in Jira, and issue a pull request from a git branch?
>
> Jakub
>
>
> On 17/03/15 10:30, Dejan Bosanac wrote:
>
>> That’s fine by me as well. It’s just that I don’t see it as much of a
>> burden on activemq-broker. It really is just a couple of classes in it’s
>> own package which can be used to configure and run the broker from Java.
>> If
>> it’s a separate module, than we need to make sure we include it
>> activemq-all, activemq-osgi, etc, and add it as a dependency to all
>> modules
>> that want to use it for testing. So in the end it will be more
>> complicated.
>> But whatever folks prefer is fine by me.
>>
>> Regards
>> --
>> Dejan Bosanac
>> --
>> Red Hat, Inc.
>> dbosa...@redhat.com
>> Twitter: @dejanb
>> Blog: http://sensatic.net
>> ActiveMQ in Action: http://www.manning.com/snyder/
>>
>> On Tue, Mar 17, 2015 at 11:17 AM, Hadrian Zbarcea
>> wrote:
>>
>> How about a separate jar that could be used in conjunction with
>>> activemq-broker? In time start moving 'nice to have' things from
>>> activemq-broker into this other jar?
>>>
>>> Hadrian
>>>
>>>
>>> On 03/17/2015 05:57 AM, Dejan Bosanac wrote:
>>>
>>> IMHO it should be enough to just put these classes in the new package
>>>> (something like org.apache.activemq.broker.dsl) inside the
>>>> activemq-broker
>>>> module.
>>>>
>>>> Regards
>>>> --
>>>> Dejan Bosanac
>>>> --
>>>> Red Hat, Inc.
>>>> dbosa...@redhat.com
>>>> Twitter: @dejanb
>>>> Blog: http://sensatic.net
>>>> ActiveMQ in Action: http://www.manning.com/snyder/
>>>>
>>>> On Tue, Mar 17, 2015 at 12:26 AM, artnaseef wrote:
>>>>
>>>> That's an interesting use-case, and I see the value there.
>>>>
>>>>> Would this be a new, separate artifact or a change to an existing one?
>>>>>
>>>>> Art
>>>>>
>>>>> P.S. apologies for confusion on my earlier post - using nabble's "raw"
>>>>> content did indeed cause the content of the post to get stripped in
>>>>> email
>>>>> somehow.
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://activemq.2283324.n4.nabble.com/ActiveMQ-DSLs-
>>>>> tp4693171p4693332.html
>>>>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>>
>
Re: ActiveMQ DSLs
That’s fine by me as well. It’s just that I don’t see it as much of a burden on activemq-broker. It really is just a couple of classes in it’s own package which can be used to configure and run the broker from Java. If it’s a separate module, than we need to make sure we include it activemq-all, activemq-osgi, etc, and add it as a dependency to all modules that want to use it for testing. So in the end it will be more complicated. But whatever folks prefer is fine by me. Regards -- Dejan Bosanac -- Red Hat, Inc. dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/ On Tue, Mar 17, 2015 at 11:17 AM, Hadrian Zbarcea wrote: > How about a separate jar that could be used in conjunction with > activemq-broker? In time start moving 'nice to have' things from > activemq-broker into this other jar? > > Hadrian > > > On 03/17/2015 05:57 AM, Dejan Bosanac wrote: > >> IMHO it should be enough to just put these classes in the new package >> (something like org.apache.activemq.broker.dsl) inside the >> activemq-broker >> module. >> >> Regards >> -- >> Dejan Bosanac >> -- >> Red Hat, Inc. >> dbosa...@redhat.com >> Twitter: @dejanb >> Blog: http://sensatic.net >> ActiveMQ in Action: http://www.manning.com/snyder/ >> >> On Tue, Mar 17, 2015 at 12:26 AM, artnaseef wrote: >> >> That's an interesting use-case, and I see the value there. >>> >>> Would this be a new, separate artifact or a change to an existing one? >>> >>> Art >>> >>> P.S. apologies for confusion on my earlier post - using nabble's "raw" >>> content did indeed cause the content of the post to get stripped in email >>> somehow. >>> >>> >>> >>> -- >>> View this message in context: >>> http://activemq.2283324.n4.nabble.com/ActiveMQ-DSLs- >>> tp4693171p4693332.html >>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >>> >>> >>
Re: ActiveMQ DSLs
IMHO it should be enough to just put these classes in the new package (something like org.apache.activemq.broker.dsl) inside the activemq-broker module. Regards -- Dejan Bosanac -- Red Hat, Inc. dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/ On Tue, Mar 17, 2015 at 12:26 AM, artnaseef wrote: > That's an interesting use-case, and I see the value there. > > Would this be a new, separate artifact or a change to an existing one? > > Art > > P.S. apologies for confusion on my earlier post - using nabble's "raw" > content did indeed cause the content of the post to get stripped in email > somehow. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-DSLs-tp4693171p4693332.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >
Re: ActiveMQ DSLs
I like this approach of configuring the brokers. I see it as as very
powerful tool for writing complex unit tests, which can make our lives
easier. On the other hand, I don’t see any reason why wouldn’t we include
it in the code base. It doesn’t affect the core, so it’s not a
stability/performance risk, nor it is a big maintenance burden.
Regards
--
Dejan Bosanac
--
Red Hat, Inc.
dbosa...@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/
On Sat, Mar 14, 2015 at 1:44 PM, Jakub Korab
wrote:
> The end() idiom was just something I put in to make it clear when an
> element was closing (there's no way to easily express the difference
> between an attribute and a subelement of a config node, or when an element
> is finishing). I'm not married to any particular syntax here, and it
> definitely has room for improvement.
>
> Just to refer back to my previous reply to Hadrian, imagine this sort of
> thing, and you get a much better idea as to where my thinking is heading
> with regard to the power of a DSL.
>
> String[] destinationsToReplicate = new String[] {"a", "b", "c", "d",
> "e"...};
>
> List virtualDestinations = new
> ArrayList()<>;
> for (String destination : destinationsToReplicate} {
> virtualDestinations.add(
> compositeQueue(destination) // statically included method
> .forwardOnly(true)
> .forwardTo()
> .queue("toNY." + destination)
> .queue("toLN." + destination)
> .topic("audit." + destination));
> }
>
> ActiveMQBrokers.broker("TY.orderRouter")
> .destinationInterceptors()
> .virtualDestinationInterception()
> .withVirtualDestinations(virtualDestinations)
> .networkConnectors()
> .networkConnector("TY-NY", "tcp...")
> .staticallyIncludedDestinations("toNY.>")
> .networkConnector("TY-LN", "tcp...")
> .staticallyIncludedDestinations("toLN.>");
>
> Tiny amount of code, lots of work being performed, easy to comprehend and
> maintain.
>
> If you had multiple brokers in different geographical locations, you could
> inject all the string values from some config into a template broker
> definition, and have a standard deployed process that uses this DSL spin up
> a uniformly configured broker specific to that location. That's something
> you can't do with ease right now.
>
> Jakub
>
>
> On 13/03/15 22:18, David Jencks wrote:
>
>> Unfortunately your sample didn't show up on the mailing list…. I had to
>> resort to looking at nabble.
>>
>> I think your example is too simple to see the benefits of a fluent api.
>> For instance, you haven't added an object that itself needs configuration
>> to a collection (e.g. transport connector). My experience is that they
>> make configuring anything reasonably complicated 10x simpler and more
>> pleasant :-)
>>
>> That being said….. I'm not familiar with the ".end()" idiom. Is this
>> common? "standard"? I'd think it would be less confusing if they were
>> .endTransportConnectors() etc so it was clear what you were ending.
>>
>> thanks
>> david jencks
>>
>>
>> On Mar 13, 2015, at 5:32 PM, artnaseef wrote:
>>
>> I see "fluent is easier" as a valid argument to maintaining the project,
>>> but
>>> not necessarily as a reason to pull it into the ActiveMQ main code base.
>>>
>>> Still, I am 50/50 on this myself. I personally don't have a need for
>>> simpler configuration of embedded brokers. Also, the syntax of fluent
>>> builders doesn't appeal to me personally, so that makes it harder for me
>>> to
>>> buy-in. For example:
>>>
>>> Seems simpler to understand than (I'm making this one up - not using the
>>> posted language):
>>>
>>> With that said - I acknowledge this is my opinion and welcome some
>>> discussion of the benefit of including the code inside of ActiveMQ itself
>>> (beyond the well-understood "it will then be maintained with the core
>>> code").
>>>
>>> Art
>>>
>>>
>>>
>>> --
>>> View this message in context: http://activemq.2283324.n4.
>>> nabble.com/ActiveMQ-DSLs-tp4693171p4693202.html
>>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>>>
>>
>
[jira] [Resolved] (AMQ-5644) Autorization map doesn't handle wildcard subscriptions properly
[ https://issues.apache.org/jira/browse/AMQ-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-5644. Resolution: Fixed New fix in http://git-wip-us.apache.org/repos/asf/activemq/commit/3b39d2cc > Autorization map doesn't handle wildcard subscriptions properly > --- > > Key: AMQ-5644 > URL: https://issues.apache.org/jira/browse/AMQ-5644 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.11.0 > Reporter: Dejan Bosanac >Assignee: Dejan Bosanac > Fix For: 5.12.0 > > > Wildcard destination subscriptions are matched against all matching map > entries. Instead, we should only return those entries that explicitly matches > subscription wildcard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMQ-5644) Autorization map doesn't handle wildcard subscriptions properly
[ https://issues.apache.org/jira/browse/AMQ-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac reopened AMQ-5644: Reverted a commit temporarily as it break some tests. I need to investigate it further. > Autorization map doesn't handle wildcard subscriptions properly > --- > > Key: AMQ-5644 > URL: https://issues.apache.org/jira/browse/AMQ-5644 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.11.0 > Reporter: Dejan Bosanac >Assignee: Dejan Bosanac > Fix For: 5.12.0 > > > Wildcard destination subscriptions are matched against all matching map > entries. Instead, we should only return those entries that explicitly matches > subscription wildcard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMQ-5644) Autorization map doesn't handle wildcard subscriptions properly
[ https://issues.apache.org/jira/browse/AMQ-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-5644. Resolution: Fixed Fixed with http://git-wip-us.apache.org/repos/asf/activemq/commit/744d > Autorization map doesn't handle wildcard subscriptions properly > --- > > Key: AMQ-5644 > URL: https://issues.apache.org/jira/browse/AMQ-5644 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.11.0 > Reporter: Dejan Bosanac >Assignee: Dejan Bosanac > Fix For: 5.12.0 > > > Wildcard destination subscriptions are matched against all matching map > entries. Instead, we should only return those entries that explicitly matches > subscription wildcard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMQ-5644) Autorization map doesn't handle wildcard subscriptions properly
Dejan Bosanac created AMQ-5644: -- Summary: Autorization map doesn't handle wildcard subscriptions properly Key: AMQ-5644 URL: https://issues.apache.org/jira/browse/AMQ-5644 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.11.0 Reporter: Dejan Bosanac Assignee: Dejan Bosanac Fix For: 5.12.0 Wildcard destination subscriptions are matched against all matching map entries. Instead, we should only return those entries that explicitly matches subscription wildcard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-5585) Messages not reachable after moving
[ https://issues.apache.org/jira/browse/AMQ-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327239#comment-14327239 ] Dejan Bosanac commented on AMQ-5585: It's probably a different issue as this is only when you move messages using JMX. It'd be good if you could write a test case that reproduces the issue against the current master branch. > Messages not reachable after moving > --- > > Key: AMQ-5585 > URL: https://issues.apache.org/jira/browse/AMQ-5585 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.11.0 >Reporter: Dejan Bosanac >Assignee: Dejan Bosanac > Fix For: 5.12.0 > > > When you move messages that are added when memory limit was hit, they will be > unreachable until the broker restart -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMQ-5594) Virtual topic wildcard consumers don't receive some messages
[ https://issues.apache.org/jira/browse/AMQ-5594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-5594. Resolution: Fixed This is now fixed with http://git-wip-us.apache.org/repos/asf/activemq/commit/05c31124 We need to treat virtual topic wildcard subscriptions differently as they need to be represented by a dedicated queue. The subscription to that queue should not subscribe to other child queues (as in the normal case) or we'll get duplicates. > Virtual topic wildcard consumers don't receive some messages > > > Key: AMQ-5594 > URL: https://issues.apache.org/jira/browse/AMQ-5594 > Project: ActiveMQ > Issue Type: Bug > Components: MQTT >Affects Versions: 5.11.0 >Reporter: Dejan Bosanac >Assignee: Dejan Bosanac > Fix For: 5.12.0 > > > When using mqtt with virtual topic subscription strategy, it shows some > failures when dealing with wildcard subscriptions. The problems are related > to how we deal with wildcards in virtual topic consumer, leading to messages > sent to child topics are not forwarded properly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMQ-5594) Virtual topic wildcard consumers don't receive some messages
Dejan Bosanac created AMQ-5594: -- Summary: Virtual topic wildcard consumers don't receive some messages Key: AMQ-5594 URL: https://issues.apache.org/jira/browse/AMQ-5594 Project: ActiveMQ Issue Type: Bug Components: MQTT Affects Versions: 5.11.0 Reporter: Dejan Bosanac Assignee: Dejan Bosanac Fix For: 5.12.0 When using mqtt with virtual topic subscription strategy, it shows some failures when dealing with wildcard subscriptions. The problems are related to how we deal with wildcards in virtual topic consumer, leading to messages sent to child topics are not forwarded properly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMQ-5585) Messages not reachable after moving
[ https://issues.apache.org/jira/browse/AMQ-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-5585. Resolution: Fixed This is now fixed on master with http://git-wip-us.apache.org/repos/asf/activemq/commit/1cab7138 > Messages not reachable after moving > --- > > Key: AMQ-5585 > URL: https://issues.apache.org/jira/browse/AMQ-5585 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.11.0 > Reporter: Dejan Bosanac > Assignee: Dejan Bosanac > Fix For: 5.12.0 > > > When you move messages that are added when memory limit was hit, they will be > unreachable until the broker restart -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMQ-5585) Messages not reachable after moving
Dejan Bosanac created AMQ-5585: -- Summary: Messages not reachable after moving Key: AMQ-5585 URL: https://issues.apache.org/jira/browse/AMQ-5585 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.11.0 Reporter: Dejan Bosanac Assignee: Dejan Bosanac Fix For: 5.12.0 When you move messages that are added when memory limit was hit, they will be unreachable until the broker restart -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [DISCUSS] 5.10.2 release
Hi Art, please include the following commit in the 5.10.2 release https://git1-us-west.apache.org/repos/asf?p=activemq.git;a=commit;h=00921f22ff9a8792d7663ef8fadd4823402a6324 Regards -- Dejan Bosanac -- Red Hat, Inc. dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/ On Wed, Feb 11, 2015 at 7:35 PM, artnaseef wrote: > Here's the jira list of tickets for 5.10.2: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20fixVersion%20%3D%205.10.2 > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/DISCUSS-5-10-2-release-tp4691398p4691400.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >
[jira] [Commented] (AMQ-5558) Make activemq-client jar executable and able to send/receive messages
[
https://issues.apache.org/jira/browse/AMQ-5558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317982#comment-14317982
]
Dejan Bosanac commented on AMQ-5558:
This now works in Karaf as well, you can do
{code}activemq:producer
activemq:consumer{code}
Also, I made activemq-all jar executable, so you can do things like
{code}java -jar target/activemq-all-5.12-SNAPSHOT.jar start
java -jar target/activemq-all-5.12-SNAPSHOT.jar producer
java -jar target/activemq-all-5.12-SNAPSHOT.jar consumer
java -jar target/activemq-all-5.12-SNAPSHOT.jar stop{code}
Next, I need to implement a couple more features that are missing so we can
remove old ant examples and document all this.
> Make activemq-client jar executable and able to send/receive messages
> -
>
> Key: AMQ-5558
> URL: https://issues.apache.org/jira/browse/AMQ-5558
> Project: ActiveMQ
> Issue Type: New Feature
>Affects Versions: 5.11.0
>Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
>
> It would be nice to have basic verification/example tool builded directly in
> activemq-client.jar, so that folks can do something like
> {code}java -jar lib/activemq-client-xxx.jar producer
> java -jar lib/activemq-client-xxx.jar consumer{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMQ-5033) webconsole url and html encoding missing
[ https://issues.apache.org/jira/browse/AMQ-5033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308977#comment-14308977 ] Dejan Bosanac commented on AMQ-5033: This issue is related to CVE-2014-8110 The vulnerability was introduced with https://fisheye6.atlassian.com/changelog/activemq-git?cs=0c4790bb946127ebb9a153c1fba1e3140917aad6 It's fixed with http://git-wip-us.apache.org/repos/asf/activemq/commit/994d9b26 More information is available at http://activemq.apache.org/security-advisories.html > webconsole url and html encoding missing > > > Key: AMQ-5033 > URL: https://issues.apache.org/jira/browse/AMQ-5033 > Project: ActiveMQ > Issue Type: Bug > Components: webconsole >Affects Versions: 5.9.0 >Reporter: Arthur Naseef >Assignee: Arthur Naseef > Fix For: 5.9.1, 5.10.0 > > > While working on AMQ-4813, many cases of passing text through to HTML without > proper HTML and URL encoding. > I believe this can cause security risks, failed operations, or a misformatted > UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-5345) Improve LDAP communication
[ https://issues.apache.org/jira/browse/AMQ-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308968#comment-14308968 ] Dejan Bosanac commented on AMQ-5345: This issue fixes CVE-2014-3612. Take a look at http://activemq.apache.org/security-advisories.html for more details. > Improve LDAP communication > -- > > Key: AMQ-5345 > URL: https://issues.apache.org/jira/browse/AMQ-5345 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.10.0 >Reporter: Dejan Bosanac > Assignee: Dejan Bosanac > Fix For: 5.10.1, 5.11.0 > > > Various improvement in how we communicate with LDAP -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-5333) XPath selector - make xml parser features configurable
[ https://issues.apache.org/jira/browse/AMQ-5333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308965#comment-14308965 ] Dejan Bosanac commented on AMQ-5333: This issue fixes CVE-2014-3600. take a look at http://activemq.apache.org/security-advisories.html for more details. > XPath selector - make xml parser features configurable > --- > > Key: AMQ-5333 > URL: https://issues.apache.org/jira/browse/AMQ-5333 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.10.0 >Reporter: Dejan Bosanac > Assignee: Dejan Bosanac > Fix For: 5.11.0 > > > We need to be able to set xml parser features configurable using system > properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[ANNOUNCE] CVE-2014-3579 - ActiveMQ Apollo vulnerability
A security vulnerability has been reported agains ActiveMQ Apollo 1.7 and older versions. Please check the following document and see if you’re affected http://activemq.apache.org/security-advisories.data/CVE-2014-3579-announcement.txt ActiveMQ Apollo 1.7.1 with appropriate fixes is released and available for upgrade Regards -- Dejan Bosanac -- Red Hat, Inc. dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/
[ANNOUNCE] CVE-2014-3600, CVE-2014-3612 and CVE-2014-8110 - Apache ActiveMQ vulnerabilities
There have been a several security vulnerabilities reported against Apache ActiveMQ 5.10.0 and older versions. Please check the following documents and see if you’re affected by them http://activemq.apache.org/security-advisories.data/CVE-2014-3600-announcement.txt http://activemq.apache.org/security-advisories.data/CVE-2014-3612-announcement.txt http://activemq.apache.org/security-advisories.data/CVE-2014-8110-announcement.txt Apache ActiveMQ 5.10.1 and 5.11.0 with appropriate fixes are released and available for upgrade Regards -- Dejan Bosanac -- Red Hat, Inc. dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/
