-
1. Re: Why are there so many critical bugs in every jboss as 7.x.x???
wdfink Oct 18, 2013 5:43 AM (in response to ybxiang.china)1 of 1 people found this helpfulWhat you call 'critical bugs'?
Lot of issues are fixed in 7.2, you might use the latest 7.2 from github (before the development change to WildFly) if you need to fix issues.
The next community version will be WildFly 8, the 8.0.0.Beta1 will be available since a few days.
The EAP6 downloads are only for development and you will have a 0$ subscription (therefore the notice) to be able to test and develop with that version.
But if you decide to go with the community version in production you will not have support and patches for it, for fixes you need to try the next version.
Other option is to use the github repository and create your own version.
I think there are many people using the community version in production like you.
-
2. Re: Why are there so many critical bugs in every jboss as 7.x.x???
jaikiran Oct 18, 2013 6:11 AM (in response to ybxiang.china)xiang yingbing wrote:
Why are there so many critical bugs in every jboss as 7.1.x, 7.2.x ???
Among jboss as community versions, JBoss AS 7 serials' quality is too bad when compared with JBoss AS 5.1.0.
I know every version has had bugs and even AS7 versions have bugs but having used and seen forum posts about AS5, I am very sure that the quality of AS7 is vastly better than AS5.
xiang yingbing wrote:
Are you on purpose???
What purpose would that be?
xiang yingbing wrote:
When I download jboss eas 6.1, I am told:
Please, keep in mind, that you have agreed with our terms and conditions on July 9, 2013. You will be notified again in 264 days after your subscription ends.
I really dislike it!
Like with any product, don't use the product (EAP in this case) if the terms and conditions governing it don't suit your needs.
All community versions of WildFly are free for even production use, so that's one option for you.
-
3. Re: Why are there so many critical bugs in every jboss as 7.x.x???
ybxiang.china Oct 18, 2013 7:26 AM (in response to jaikiran)I apologize for my impolite words "Are you on purpose???"
I take back it.
I spent many many days on JBoss AS 7 and persuade friends to use it. And persuade myself to forget Glassfish3.
I spent many hours to migrate my product from jboss-as-7.1.3/jboss-as-7.2.0.Alpha1.to JBoss AS 7.2.0.
There are still new bugs in JBoss AS 7.2.0, which does NOT exist in previous version jboss-as-7.2.0.Alpha1.
I must google it and patch it(or return back to jboss-as-7.2.0.Alpha1 or 7.1.3).
Wildfly is still beta version, if I use it and find more bugs which does NOT exist in jboss as 7.2.0, then how shoud I do?
I agree that "there are always bugs in any software".
I just expect too much on JBoss AS.
-
4. Re: Why are there so many critical bugs in every jboss as 7.x.x???
dlofthouse Oct 18, 2013 7:38 AM (in response to ybxiang.china)Are the bugs you are talking about reported? If we know which bugs are affecting user migrations it can help us focus on what really is impacting users out there.
-
5. Re: Why are there so many critical bugs in every jboss as 7.x.x???
ybxiang.china Oct 18, 2013 10:52 AM (in response to dlofthouse)Yes. It had been reported: https://issues.jboss.org/browse/HORNETQ-408, it fixed in HornetQ 2.3.0 Final. Affects Version/s: 2.3.0.CR1
JBoss AS 7.2.0-alpha uses 2.2.18.Final.
JBoss AS 7.2.0 and EAP 6.1 uses the Affected Version 2.3.0.CR1, so both of them has this problem.
I am wondering why EAP 6.1 uses the CR1 version instead of final version???
I don't know if I will meet more such bugs when I use wildfily.So I will not use it as my production environment.
But I will learn it those days and become one of your WHITE MICE.
Correction
Sorry, I used the EAP 6.1 Alpha version.
I should download final version from JBoss Application Server Downloads - JBoss Community.
I checked it just now, EAP 6.1 final does use hornetq 2.3.1.final.
:
-
6. Re: Why are there so many critical bugs in every jboss as 7.x.x???
jaikiran Oct 18, 2013 8:31 AM (in response to ybxiang.china)I think in this specific case (i.e. the HornetQ bug) it should be easy to upgrade in your local instance. You'll just have to upgrade the module jar and module.xml in HornetQ module to use 2.3.0.Final instead of the CR version. I'm basing that on what I see here https://github.com/wildfly/wildfly/pull/4428/files
-
7. Re: Why are there so many critical bugs in every jboss as 7.x.x???
ybxiang.china Oct 18, 2013 9:17 AM (in response to ybxiang.china)I will return back to jboss as 7.2.0-alpha.
After Wildfly final version is released, I will migrate my app to wildfly directly.
Thank you all for your warm hearts.
-
8. Re: Why are there so many critical bugs in every jboss as 7.x.x???
jbertram Oct 18, 2013 9:45 AM (in response to ybxiang.china)FYI - JBoss EAP 6.1 does not use HornetQ 2.3.0.CR1; it uses HornetQ 2.3.1.Final.
-
9. Re: Why are there so many critical bugs in every jboss as 7.x.x???
ybxiang.china Oct 18, 2013 10:51 AM (in response to jbertram)Sorry, I used the EAP 6.1 Alpha version.
I should download final version from JBoss Application Server Downloads - JBoss Community.
I checked it just now, EAP 6.1 final does use hornetq 2.3.1.final.