Has anyone experienced performance degradation when upgrading from HornetQ to Active Artemis? I'm working on a system that upgraded from HornetQ 2.4.5.Final to Artemis 2.10.0 and am seeing a performance degradation. Beginning investigation, but so far it appears the configuration/setup is similar between the two.
There have been lots of performance enhancements made to ActiveMQ Artemis since the donation of the HornetQ code-base to Apache so if anything I would expect it to be faster. However, there's certainly a chance that a particular use-case could be slower, and there's always the possibility of bugs.
It's worth noting that HornetQ 2.4.5.Final was tagged in October 2014 (the same month & year as the donation to Apache) and ActiveMQ Artemis 2.10.0 was tagged in August 2019 which is about 5 years difference. That's a significant gap in the life of an active software project. There have been over 7,000 commits to the ActiveMQ Artemis code-base during that time.
You would really need to describe your use-case in detail and quantify the performance degradation for any real investigation to be done.
Related
I wanted to get started with kafka ( i had little experience with kafka 0.10 , and now, it seems there are "major" changes happened)
I am going through release changes of kafk. However, I am stuck with which version I should choose in terms of stability , community support . I am little reluctant to use the latest version 2.5
Please suggest me a version which didn't get a lot of "major" changes . I heard kafka 2.1 is good start as it had some breaking changes from previous version .
If you're making the leap from 0.10, I don't see any point in stopping part-way with 2.1.
In terms of releases, the latest stable release is 2.5.0. If you prefer, 2.4 was released in December 2019 and has had a dot release since (2.4.1).
Check out this excellent talk which addresses why you should upgrade.
I didn't find a lot of material about 2.5
The majority of material is version agnostic (unless it's based on super-old versions, like 0.10 etc). If you want to see breaking changes specifically, look at the download page which notes major changes and links to the release notes for each version which lists every single change.
I am seeing 2 versions (9.0.1 vs 8.2.1) of wildfly which were released on the same day. What is the difference between two versions and why there are 2 versions exist in parallel? I couldn't find it over the internet.
Wildfly ships on a very fast development cycle. Each major release 8.x, 9.x, 10.x contains major changes from the previous version. All current major work is being done on the 10.x beta versions.
The minor versions are for bugfixes related to that particular release. Since there are now people in production with both 8.x and 9.x, any critical bugs or security patches go into one of these releases. It is very possible a security issue could exist and be fixed in both 8.x.1 and 9.x.1.
JBoss EAP, which is based on WildFly, deliberately has a slower release schedule. For each major version they release they offer paid support for 4 years, so they change major versions much slower.
There is a good slide of the lifecycle of WildFly/JBoss on page 9 of this slide-deck from the RedHat Summit in June:
http://videos.cdn.redhat.com/summit2015/presentations/12186_red-hat-jboss-enterprise-application-platform-7-roadmap-new-features.pdf
Here is the official announcement for the pair of releases: -
http://wildfly.org/news/2015/07/23/WildFly-901-and-821/
We are using JBoss 4.2 GA, and need use a newest version in some new project.
I heard that JBoss 5.0 encounter such bugs... is this correct?
If not, which exact version of 5.0 to use?? and what about 6.0??
Thanks.
JBoss AS 5.1 is perfectly fine. Every app server has bugs, they're big, complex applications in themselves, but 5.1 is solid.
JBoss AS 6 hasn't been released yet, it's still in beta.
Jboss Application Server 7 is released, and up to a beta version of 7.1.0. You can download a copy here, and find the Getting Started Guides here.
As with any major revision of an application server, there are significant changes that might impact upon your business and will need to be considered in the context of your use case. Being an open source project, the early praise and early bugs are in the public arena, so it is easy to research for yourself.
Working on a documentation project involving AS7 I have seen some of the great work that the team has undertaken, and I couldn't imagine going back to a previous version now I've enjoyed the fast boot-up times, the ease of application deployment, custom configuration and the powerful Management CLI.
These kinds of improvements and features, not just constrained to JBoss Application Server or JBoss Enterprize Application Platform, speak volumes about the speed, stability and usability that will be increasing exponentially in this field for all competitors over the coming years. I'd urge you to check out the current generation of application servers if your experience is largely with JBoss AS 4.2.
I'm currently testing Memcached in a Windows machine and we are planning to use it in production while Microsoft Velocity is still in CTP. It is running well so I believe that Memcached for Windows will do well when our site is already in production. I'm reading some blogs pertaining to this issue and some of them just mentioned that it must not yet be used in production.
If there are issues, please tell why? And please, if you have any links about this matter, just post it here. Thanks.
There is no official release of memcached on Windows. We're working on it right now, but unless you're pulling from a dev branch or you've downloaded a pre-release, you've definitely got an unsupported version with a large number of bugs and missing features from the last couple of years.
I've been using memcached in production for several years now (since early 2008). We're currently using a 12-instance cluster and it absolutely hums. I would recommend memcached any day of the week.
As far as i know the EAP editions of JBoss Application Server (AS) are just a bunch of community edition JBoss projects with some sugar.
So, what is the community edition of the JBoss Application Server that JBoss EAP 4.3.0 corresponds to?
This response is really late but I came across the unanswered question in a Google search and I wanted to make sure there's a correct response. I work for JBoss support so you can consider this a qualified answer.
JBoss EAP is the only commercially supported version of JBoss. It contains JBoss AS and JBoss Seam. EAP diverged (in terms of the svn branch it's built off) from JBoss AS around version 4.2.1 (not exactly, but close enough). EAP has a 5-year lifetime and is tested and certified rigorously. EAP has paid commercial support and patches (called CPs or cumulative patches) that are designed to maintain ABI/API stability over time while allowing for security issues and bugs to be fixed. It is actually against policy to introduce a feature in a CP, but it happens on occasion.
If you're familiar with how Red Hat Enterprise Linux differs from Fedora, you can consider the difference to be quite similar. The JBoss project/product split is much newer, though, so the differences are smaller. Here's the official page describing what I've said.
http://www.jboss.com/products/community-enterprise
Cheers,
Chris
According to JBoss Enterprise Application Platform Component Details, JBoss EAP 4.3 is based on:
JBoss Application Server 4.2.1 with various updates, component upgrades, and bug fixes
The primary difference between EAP and the community release is that EAP is the officially supported configuration of the community edition, with fixed versions of the various components. RedHat was finding it too difficult to support the different component versions used by man+dog, and nailed it down to one set.
As for versioning, the EAP version numbers roughly track the community releases, but with differences:
EAP 4.2 is based on JBossAS 4.2
EAP 4.3 is also based on JBossAS 4.2.1, but with JBossMQ replaced by JBossMessaging, and Java6 support
EAP 5.0 is based on JBossAS 5.1
EAP 5.1 also seems to be based on JBossAS 5.1, with some cumulative patches
Edit:
EAP 6.x is based on JBoss Application Server 7.x
I've been digging into JBoss version information to try and find an answer to a more specific question i'm dealing with, and i thought i'd share my observations. You can get a picture of the names and dates of releases from JBoss's JIRA bug tracker: you can check out the info for the Community and Enterprise editions.
I was interested in the 4.2 branch rather than 4.3. If you hunt back a few years, you'll find that the Community release 4.2.0.GA came out on the 14th of May 2007, and was followed six weeks later by the Enterprise release 4.2.0.GA on the 3rd of July 2007. After that, the numbering diverged: the Community edition shipped point upgrades - 4.2.1.GA, 4.2.2.GA and 4.2.3.GA - every few months after that. The Enterprise edition instead shipped a series of 'cumulated patch' releases based on 4.2.0, starting with 4.2.0.GA_CP01 and hitting 4.2.0.GA_CP06 a few months ago. How do these releases relate to each other? I'm still not sure about this, but i think the theory is that the Enterprise edition doesn't gain any new features (within that branch), only bugfixes, but that those bugfixes are applied to both the Enterprise and Community editions. In fact, i suspect that in the case of my bug10, the fix was developed against the Community edition, and then crossported to the Enterprise edition, although i'm far from sure about that.
Turning back to your actual question, things are less clear. The Enterprise 4.3.0.GA came out on the 7th of January 2008, after the Community 4.2.2.GA, but before 4.2.3.GA. There is no Community 4.3.0, nor is there an Enterprise 4.2.x for any x > 0. Chris says that the Enterprise and Community versions "diverged", and i assume that what he means by that is that the Enterprise version is no longer based on just bugfixing a Community version, but rather is now an entirely separate development stream - presumably taking code drops from the Community edition where that's appropriate.
So, the answer to your question is some combination of: 4.2.2.GA (but only distantly), 4.2.0.GA (plus years of separate development), and mu.
While JBoss AS / Wildfly is really the basis for JBoss EAP, it's definitely not just "some sugar" what is added.
EAP is what went through an extensive testing and many many bug and security issues are fixed.
More, EAP is usually also faster after going though a period of performance tests, soak testing, and code analysis.
Also, EAP artefacts (jars) are all built by Red Hat, i.e. Red Hat is responsible for whatever is in them - i.e. you don't get whatever anyone puts in the central repo or whichever other repo you may have configured in your settings.xml (in case you build your own AS). Many of these third-party libraries are changed - CVE's fixed, performance issues addressed etc.
And lastly, EAP is way better in terms of features. For example, last 7.x release of JBoss AS is 7.1.1, year-and-something old, while EAP 6.1 is about a month old, and is way better in regards of manageability, stability, configurability etc. There is a several hundreds of commits difference between those two.
So, stating that "JBoss EAP X is based on JBoss AS Y" may be true, but at the same time misleading.
Check the EAP 6.1.