We are using tree cache in jboss 4.2.x, we are planning to switch to jboss6.x, will jboss 6.x supports tree cache?
From the JBoss Wiki:
As of version 6.0.0.CR1, Infinispan replaced JBoss Cache as the distributed caching technology upon which JBoss AS clustering services are built.
Now, it's possible that you may be able to package a downloaded copy of JBossCache 1.4 (which is the version that comes with JBossAS 4.2) inside your application and deploy it on JBossAS 6.x, but I suspect this is unlikely to work - JBossCache 1.4 relies on some very old shared JBoss libraries.
I think you're going to have to refactor your code to work with Infinispan rather than JBossCache, if you want to migrate from AS 4.2 to 6.x.
Related
I understand previous JBoss versions used DBCP, but I don't find a specific reference to which library and version use JBoss EAP 6.4.
Edit: I found references of uses of ironjacamar as mentioned by #ehsavoi here. But I saw this disclaimer:
"This feature should only be used for development. It is not
recommended for production environments because it is not supported by
the JBoss administrative and management tools. This feature is
deprecated in JBoss EAP 6.4 and will not be supported in the next
major release of the product."
So my concern is if this disclaimer is related only to datasource deployment (*.ds files) or to ironjacamar as well.
It is using ironjacamar. The version depends on the effective version of EAp 6.4 you are using.
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
right now my app use 4.2 jboss with java 1.5.
I manage to build my app (EJB, jsf, hibernate, seam) with java 1.8, but i get some problems with running jboss 4.2 with java 1.8.
So I wonder, whether it is even possible or it will be better to switch to another version of jboss(with will be also complicate)?
Thank you for clarification.
So another question appear, if I use new jboss and java8 , Am I need to change hibernate (eg. I use hibernate-ejb 3.3.2ga), jsf, etc. to newer version? Application was build with java 8 with success.
You can't run JBoss EAP 4.2 on Java 1.8 (Or any other java newer than 1.6)
Use new version of JBoss EAP instead. This will give you better performance some cool new features and server will be easier to monitor and maintain.
Here is the link
I am going to start a new enterprise application. Which version I wanted to use?
Is it EAP 6.2.0 GA(EAP built from AS 7.3) or JBoss AS 7.1.0.Final or Wildfly 8.1.0.Final? I am very confused about these versions. when do i have to download EAP 6.2.0?
Also, why wildfly is not avaialbe on http://jbossas.jboss.org/downloads/? why?
I was having the impression that wildfly and jboss8 as are same. If both are same,
why it is not avalible in the downloads of above link?
the community version of JBoss has been renamed to Wildfly and can be found here: http://wildfly.org/downloads/. EAP 6.2 is the commercial version of JBoss provided by RedHat for which you get professional support by them.
Which version you choose depends on your requirements and whether you are willing to spend money for it ;) But if you are going with the community version, it wouldn't make sense to start with JBoss AS 7 since Wildfly 8 provides Java EE 7 support, JBoss AS 7 not. I've recently migrated a huge industry-strength project to Wildfly and am very surprised by the new application server. Nevertheless, with my current experience, I would recommend to go with EAP and professional support for large projects that utilize the whole Java EE stack. The only drawback there is that EAP 6 doesn't support Java EE 7 yet.
Jboss EAP is Red Hat product while wildfly is community version. Latest EAP version available currently is EAP 7.1.2, you will have to buy Red Hat subscription to use the same. Wildfly is opensource community version for the same, which you download and use freely.
Which version to be used will depend completely on your project requirement and budget. EAP would be more stable and tested product which can be used for critical production applications, also Red Hat will provide complete support if you purchase the subscription.
But if you have budget constraints and want to use free application server wildfly can be used.
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.