[英]Is it worth upgrading to JBoss 7.1 from JBoss 5.1
Currently our production environment runs JBoss 5.1 and we have been debating whether or not its worth migrating to JBoss 7.1. 目前我们的生产环境运行JBoss 5.1,我们一直在争论它是否值得迁移到JBoss 7.1。 If it was a simple server upgrade, then it wouldn't be a problem.
如果它是一个简单的服务器升级,那么它不会是一个问题。 But, unfortunately, we would have to change configurations and that would take some effort.
但是,不幸的是,我们必须改变配置,这需要付出一些努力。 Also, our server runs in a cluster and I read that JBoss 7.1 has more cluster support.
此外,我们的服务器在一个集群中运行,我读到JBoss 7.1有更多的集群支持。
So is it worth it or not? 它值得与否?
Thanks 谢谢
We're currently in the same situation. 我们目前处于相同的情况。
There seem to aa lot of things on the positive side: 积极方面似乎有很多事情:
Things that we still need to look into: 我们仍需要研究的事情:
We don't run in a cluster so I can't comment on that. 我们不在群集中运行,因此我无法对此发表评论。
What will probably be the biggest effort for us is migrating all the shell scripts (installation, integration tests, …) that interact in one way or another with JBoss. 对我们来说最大的努力可能是迁移所有与JBoss以某种方式交互的shell脚本(安装,集成测试......)。
Update 更新
We have migrated and it was definitely worth it. 我们已经迁移,绝对值得。 Some updates to the points above:
以上几点的一些更新:
Update 2 更新2
Is everything working on JBoss 5.1.0 for you? 一切都在为JBoss 5.1.0工作吗? Is your performance something you can live with?
你的表现是否可以与你一起生活?
I'm currently in the middle of upgrading from JBoss 5.1.0GA to JBoss 7.1.1 and it has not been easy at all. 我目前正处于从JBoss 5.1.0GA升级到JBoss 7.1.1的过程中,并不容易。 You're basically upgrading to a new application server.
您基本上是升级到新的应用程序服务器。 You will need to budget a lot of dollars for this effort I'm guessing.
你需要为这项努力预算很多钱。
Having said that JBoss 7.1.1 is VERY fast compared to 5.1.0 (start up times at least). 虽然说JBoss 7.1.1与5.1.0相比非常快(至少启动时间)。 I think in the next 6 months (or so) most of the "hard" migration and transition issues will be fleshed out in the jboss forums or through bug fixes.
我认为在接下来的6个月(或左右)中,大多数“硬”迁移和过渡问题将在jboss论坛或通过错误修复中充实。 At that point you and your team can reevaluate if you want to do the migration.
此时,如果您想进行迁移,您和您的团队可以重新评估。
Good luck! 祝好运!
If you are using SSL, one advantage to upgrading is that JBoss 7.1.1 runs on jdk 1.7, which has support for TLS 1.1 & 1.2, while jdk 1.6 only supports up to TLS 1.0. 如果您使用SSL,升级的一个优点是JBoss 7.1.1在jdk 1.7上运行,它支持TLS 1.1和1.2,而jdk 1.6仅支持TLS 1.0。 JBoss 5 will not run on java 1.7 so you are susceptible to a BEAST attack.
JBoss 5不能在java 1.7上运行,因此您容易受到BEAST攻击。
Regardless, I'd wait a bit. 无论如何,我等一下。
AS 5 is a EE5 server, AS 7.1 is a EE6 server (and EE6 spec came out in 2009). AS 5是EE5服务器,AS 7.1是EE6服务器(EE6规范于2009年发布)。 So that's alot of work for an excellent new runtime environment, but it won't give you any hot architectural possibilities.
这对于一个出色的新运行时环境来说有很多工作,但它不会给你任何热门的架构可能性。
The WildFly 8.0.0.CR1 is already due and that's EE7 server bringing you a bunch of new interesting developing possibilitites, like WebSockets and JAX-RS 2.0 ( http://www.slideshare.net/dandreadis/2013-11devoxxwild-flybof ). WildFly 8.0.0.CR1已经到期,而EE7服务器为您带来了一堆新的有趣的开发可能性,如WebSockets和JAX-RS 2.0( http://www.slideshare.net/dandreadis/2013-11devoxxwild-flybof ) 。 New admin features like Single Instance Patching.
新的管理功能,如单实例修补。 And it's not sure that AS7-to-WildFly8 will be a super-easy migration since som major new stuff is introduced, like Undertow instead of JBossWeb/Tomcat.
并且不确定AS7-to-WildFly8将是一个超级简单的迁移,因为引入了主要的新东西,如Undertow而不是JBossWeb / Tomcat。
If you gotta go, you gotta go - and if U wind down the dead 7.x path, don't forget to get your hands on the much improved 7.2.0.Final tag (several hundred issues better that 7.1.1). 如果你必须离开,你必须离开 - 如果你绕过死亡的7.x路径,不要忘记接受改进的7.2.0.Final标签(比7.1.1好几百个问题)。 But if you think you can start developing/migrating now using Beta/CR releases and wait some months for a nice production-stable WildFly 8.xx release, you might be able to sit tight longer before next major update.
但是如果你认为你现在可以开始使用Beta / CR版本开发/迁移并等待几个月来制作一个生产稳定的WildFly 8.xx版本,那么你可以在下次重大更新之前保持更长时间。
br, Jens br,Jens
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.