Configuring JBoss 5.1 with latest versions of JMS, EJB, Remoting, etc

[michaill]

Hello,

When you configure JBoss 5.1 for production, do you use the 5/2009 release as is, or do you install the latest versions of whatever services you use.

For example, there is JBoss EJB3 Plugin 1.0.19, jboss-messaging-1.4.5, JBossRemoting.

There have been no bug fix releases of JBoss since that 2009 release, so do you keep the server up to date by using the latest versions of individual pieces? If you do, what else is there besides the three that I mentioned? What about the server kernel itself? Are all the updates independent of each other? For example, if I install the latest JBossRemoting, might that break some EJB component?

Just curious,

Mike

[jaikiran]

Michael Vershub wrote:

When you configure JBoss 5.1 for production, do you use the 5/2009 release as is, or do you install the latest versions of whatever services you use.

For example, there is JBoss EJB3 Plugin 1.0.19, jboss-messaging-1.4.5, JBossRemoting.

There have been no bug fix releases of JBoss since that 2009 release, so do you keep the server up to date by using the latest versions of individual pieces?

Why not use the latest stable JBoss AS 6.0.0.Final?

[michaill]

1. Our apps may have to be deployed on other (JEE 5) app servers, so they must be JEE5. 

2. HornetQ has broken SSL, so we can't use it, and it seemed it would be a bit silly to use JBoss 6 with JBMessaging, if that's even possible (JMS is a major part of our project). 

3. I had serious trouble finding JBoss 6 documentation, while there were several JBoss 5 books and official docs were an order of magnitude better.

4. There was a general feeling (totally subjective, but based in part on ## 2 and 3) that the 6 might still be a bit raw. We may go with Enterprise in the future, but for now we only have Community, and it seemed safer to go with something that's been around for a couple of years.

So I was wondering about JBoss policy for releasing bug fixes.

Mike