mod-cluster main page specifies JBoss AS 5 as a minimum requirement for mod_cluster.
But at the same time on mod-cluster documentation page we can read how to configure JBoss AS 4.3
Is it some kind of documentation mistake? Anyone runs JBoss AS 4.3 with mod_cluster on it?
JBoss AS 5 is the oldest JBoss AS with which one could get mod_cluster working without any additional development effort.
mod_cluster is added as a *.sar; suggested version is the latest in mod_cluster 1.0.x branch.
Lemme add that using software as old as this is discouraged; you should move to Wildfly and mod_cluster 1.3.x.
Related
I would have added this to another thread, but I am unable to comment on other's posts. And what I read did not answer my question. I just installed EAP 7.2.0.GA. In the console log, it says:
JBoss EAP 7.2.0.GA (WildFly Core 6.0.11.Final-redhat-00001)
However, others think it is around version 13. And when I look at the releases of wildfly ( http://wildfly.org/downloads/ ) a version 6 is so old it does not even show up and would have been prior to 2014...
So, how can it be 6.0.11.Final?
WildFly core is just a component in WildFly application server.
As such is also used in JBoss EAP which is a downstream product based on WildFly AS.
WildFly core is standalone project which provides most of core capabilities (management, cli, administration, subsystem infrastructure...) of the application server without any Java EE support, that is added to it by WildFly project.
you can see the sources for both at
https://github.com/wildfly/wildfly-core/
https://github.com/wildfly/wildfly/
as for your confusion.
WildFly core 6.0.x is used in EAP 7.1 as well as in WildFly 14
which you an see also in the sources https://github.com/wildfly/wildfly/blob/14.0.0.Final/pom.xml#L375
micro version is not always exactly the same, as in the process of building downstream product of EAP, extra patches can be added.
WildFly Core is a component in JBoss Enterprise Application Platform 7 (EAP 7). So, this log means:
JBoss EAP 7.2 - JBoss EAP in version 7.2
GA - General availability
WildFly Core 6.0.11.Final - component WildFly Core in version 6.0.11.Final.
See also:
JBoss Enterprise Application Platform Component Details
Software release life cycle
I am running JBoss 6.1.0.Final with embedded HornetQ.
I want to upgrade HornetQ but keep the JBoss.
Is that possible, and how? What would the latest compatible HornetQ version that can still work with JBoss 6.1.0Final?
Looking at this thread: How to upgrade HornetQ version in JBoss 6?
I tried the following:
1- Download HornetQ 2.4.0, but wasn't sure what copy from the pack?
2- Download the latest JBoss AS 6.1.1Final and copies some jars, but not sure what version I deployed.
I need at least version 2.3.0 or HornetQ, and I have no idea which version of HornetQ is deployed with the latest 6.1.1.Final !
With JBoss EAP I would post your question to RedHat support. EAP 6.1 comes with HornetQ 2.3.1.Final, as you can see here. 6.1.1 comes with 3.6.6. And you can see the version simply by looking at the log messages or inside the manifest.
I'm about to start working on a project to be deployed later this year and would like to use JDK8. We use JBoss EAP for production but the latest JBoss EAP, 6.2 (based on JBoss AS 7.3) does not yet support it.
From a compatibility perspective, is it ok to start deploying in Wildfly8 now (which supports JDK8) with the expectation that later this year the corresponding EAP will come out?
It all depends on your application to be fair.
WildFly 8 support EE7 and EAP6 EE6, so it is up to you to decide what level of Java EE you need/want.
In future WildFly will be base for EAP7, which version of WildFly will depend on what is available at the time when "productivization" will begin.
As for Java 8 support goes, EAP 6.3 runs on Java 8, currently it is at Beta release which you can grab from http://jbossas.jboss.org/downloads/ with GA release coming soon.
I need to migrate from Jboss 5.1.0 GA to any other that supports jdk 1.7.
I'm currently using jboss 5.1 with seam 2, jdk 1.6 and sqlserver 2008 r2.
What community version of Jboss is recommended for jdk 1.7 and why?
Thanks in advance!
You can actually get JBoss AS 5.1.0 GA to run on JDK 7, see JBAS-6981. All of the following options will work with JDK 7:
JBoss AS 5.1.0 (plus the fix for JBAS-6981)
JBoss AS 6.1.0
JBoss AS 7.1.1
JBoss EAP 6.2
WildFly AS 8 CR 1
The right solution depends on your situation:
The simplest solution with the least risk is to stay with JBoss AS 5.1.0 and fix JBAS-6981 yourself. We did that and ran with it for over a year and it worked fine. Note however that JBoss AS 5.1.0 is end of life, eg. there aren't any security patches available.
If you don't want to fix JBAS-6981 yourself you can go with JBoss AS 6.1.0. This should be quite a simple migration because it builds on the same architecture and has the same disk layout. Note however that it is Java EE 6 which means among other things standardized JNDI names. Depending on your application this can have quite a bit impact — or none at all. Note however that JBoss AS 6.1.0 is end of life, eg. there aren't any security patches available.
The next "stable" community version is JBoss AS 7.1.1 with brings a whole new architecture. Depending on your application that can be quite a large migration — or a really simple one. However I would recommend against JBoss AS 7.1.1 as it's buggy as hell. Note there won't be any future releases for JBoss AS 7.1.1 as well.
JBoss EAP 6.2 builds on JBoss AS 7.1.1 (AS 7.3 actually) and contains many bug fixes (and some features). You either need to build it from source or get a license from Red Hat. There will be patches for EAP 6.2.
The current in development community version is WildFly AS 8 CR1. As you can see from the version name there isn't a stable release yet. And it contains a whole new servlet engine, which makes a whole lot of people nervous. I would only use it if you have really good integration tests.
I don't know what the situation regarding Seam is for any of them.
Note that sooner or later you'll have to migrate to a newer version of JBoss AS anyway. To judge how hard the migration will be you first need to know what dependencies on JBoss AS you have in your code.
I am new to JBoss application server. when I go for download the application server in the website. I am seeing the below servers list in the top
EAP built from AS 7.3.
EAP 6.2 Maven Repository.
EAP 6.2 Quickstarts.
kindly help me. Which is the best one. otherwise, shall I go for any other open source application server.
Thanks
I don't want to make any comment about these things you mentioned. But I can share my experience with you.
Jboss 5.1: It was good.
Jboss 7.1: I faced a problem with log4j issue. Its very complicated.
EAP 6.2: Its much stable than 7.1. my log4j problem is solved with this version.
So, it totally depends upon how deep you want to use jboss.