We are working on upgrading the JBOSS application server because of end of support for the current version. The current version of JBOSS application server we are using is EAP 4. Can somebody tell me which version would be recommended to upgrade to whose support will be available at least for 2 more years. Also, it should be supportive on Linux RHEL 7.
Also, it would be great to know the Java version that would be supported by the recommended JBOSS application server version.
The latest version of JBoss is version 7, so wouldn't it make sense to upgrade to that version? Then after that it may be worth including a more regular upgrade cycle into your project plans so you don't fall into this trap again?
Tim Driven Development
posted 1 year ago
Thanks. But is it a stable version? And till when would it be in support? For next 2 years atleast?
It's a full release, not a beta, so it's as stable as any other JBoss release. I have also just learned something new myself today. JBoss is not called JBoss anymore. It's called WildFly. So while the most recent version of JBoss is version 7, development and releases have continued under the different name with the latest version being WildFly 11.
As for the support period: Given that you say support for JBoss 4 is only just coming to an end, for a product that was released 13 years ago, I'd say you'll be alright for support if you chose to use WildFly 11. If you want to be sure it'd be worth checking with RedHat themselves.
Tim Cooke wrote:JBoss is not called JBoss anymore. It's called WildFly. So while the most recent version of JBoss is version 7, development and releases have continued under the different name with the latest version being WildFly 11.
Technically JBoss EAP and WildFly are not the same. EAP is definitely based on WildFly, but it lags a bit behind to keep it more stable. You can consider JBoss EAP as an LTS release, and WildFly the branch that gets more regular releases and the latest features.
About JBoss EAP, I would actually try to stay away from any first release, and wait for the first patch to be delivered (which you have to pay for with EAP...). I've seen enough issues with fresh releases that required a patch before we could properly work with it.
Tim Cooke wrote:I'd say you'll be alright for support if you chose to use WildFly 11. If you want to be sure it'd be worth checking with RedHat themselves.
If you want official support, you definitely need to stay away from WildFly. The only support you'll get there is whatever the community behind WildFly (of which RedHat itself is also a member) is willing and capable of doing. For official support from RedHat you need to use EAP. That support is actually pretty good as well. At work we've had quite some experience with the support team actively helping us out. Not just anonymous support, they really work for you (or your company), running your code if needed, etc.
Of course you have to pay yearly for it, but as a company that's often worth it.