Red Hat jBoss Reviews

My experience with JBoss EAP is fascinating - specifically EAP 7.1, where they provided a graphical management console and an out of the box support for mod_cluster and load balancing, which made my life a lot easier. It's really open and supports everything I needed - either out of the box or with a simple tweak.

Not a big thing - but the error messages aren't that helpful, and sometimes the community itself gets confused by the error.

To go with the latest version, as the changes made between each release and the next is HUGE.

JBoss EAP is an application platform mainly used as an application server, but also provides other modules/subsystems which makes it provide the functionality of a messaging queue, a load balancer, a gateway, or even a firewall.

And, yes... Jboss/wildfly should be default web server for java web applications. Is an open source Java EE application server implemented in pure Java, specifically the Java EE specification. Being Java-based, JBoss can be used on any operating system for which the Java virtual machine is available. WildFly is free and open source software, subject to the requirements of the GNU Lesser General Public License.

Wel, it is not perfect. All you can see es lines and lines of code, errors, warnings, information, all is text in a console. It need a configuration that is not for beginners, at least not alone beginners, without an expert helper. If yo need to apply styles, be patient, consult the web and go ahead with this arduous (and hard, if you use faces) task.

If you need to run web applications developed with java, do not hesitate and use jboss / wildfly, the initial configuration is puco ruda at the beginning then you get used to it and finally it is routine. It does not need servers of great magnitude and you can always count on your console to control your log. Besides, it has its web interface, where you can configure many things, like datasource, drivers, deploys, etc. IT'S FREE.

Five years ago, when i start to development in java web applications i needed ans erver that can run those, and find jboos. This along with the help of communities on the web, allowed my applications to come to life and be used by my clients.

What I like most is the stability it provides, it supports large loads of requests from multiple users and rarely gets out of line, has a great capacity to balance the loads.

What I do not like very much is that I think it can improve by increasing the documentation to facilitate the problems of continuous integration to the developers.

I would highly recommend this server to the development community.

It is highly stable and reliable and above all easy to use. it's great.

Use Jboss for the first time to develop a logistics system based on Java technology, jsf and restfull web services. and I really liked the performance of the server throughout the project.

jBoss offers a ton of flexibility in its application platform. It is easy to get up and running and there is plenty of documentation and forums on the internet to help figure things out. jBoss is also very stable and easy to upgrade as well. So far we have been very impressed with this product.

There is not much to dislike about jBoss. The only thing that I can say is that there are so many plugins, both third party and Red Hat built, that it can be a bit overwhelming when you are first getting jBoss up and running. You also need to be very proficient in Linux in order to administer this product - so you will definitely need to have a savvy RHEL administrator on staff.

jBoss has brought a lot of stability to our application development platform. Our developers are able to collaborate on new projects easier and we get new enhancements turned around faster so our business users are happy.

Jboss is a complete package for develop, test and deploy applications. It has great integration with openshift which saves lots of our time. You can connect your OSE projects in this tool itself and can view logs as well. You can use git close right in this tool. Lots of useful features and very fast tool.

Jboss have all good features we need, I dont see any issues with this tool.

I am using this to develop our Apis in openshift environment.

Maybe there's a lot of things that jBoss is doing great--in general, it does the job serving the needs of our application. But because of the terrible things that I experienced myself with using JBoss, it all boils down to those

Developers point of view--JBoss is not very easy to use upfront. It has complications and is not very user friendly. It takes a lot of things to get it up and running. Not very lightweight. Full iteration takes so much time and effort because of need to restart the server. "Hot deploy" almost always don't work.

There are a lot of reasons not to use jBoss. It is not simple to set up and even more on development time. I wouldn't say jBoss is very reliable in serving up the needs of an application. Therefore, It adds up to developers burden.

We need aJ2EE application server that is scalable AND offers ease of use for developers as well.

JBoss is much faster, cheaper and more solid and innovative then the IBM or Oracle's alternatives. JBoss in the free version works and the pay one adds a few more features and support.

JBoss always works perfect on Linux and is very scalable. I really like that it doesn't require too much configuration. Really a few settings for your apps and for a database.

Undertow the HTTP engine is really fast and works great. This is a nice choice to use for running jars instead of Jetty. This is worth the price of admissions and is really fast. You have to love Redhat and Jboss for all the work they do for Java and JEE. They are the only independent voice pro enterprise java these days.

They keep the open source version a little behind the EAP pay version. Also sometimes there's issues with data connection pooling and i've had some crashing. Logging to check things can get ridiculous and if you send that too splunk it could cost you a ton of money as the megabytes of log files can build up in seconds.

Download it and try it. Try it for a local project, good replacement for tomcat or jetty.

Running ecommerce applications for a large book store. And it worked. Just as good as brand DB and brand Blue.

It is a pleasure to develop with jboss, you can run it local or on a server or through eclipse.

JBoss is an Application Server java-based designed that offers the same features as others proprietary servers for less than a thenth of the cost with excellent support for common enterprise practices and specifications.

Probably, one of the worst thing is the documentations ,is not good and sometimes difficult to find.

In our enterprise we have solved all production deployment, it is fast, easy to maintain, escale and configurable.

It's very easy to deploy to it without restarting, most of the time.

It's slow, takes forever to start, uses a lot of memory, it's possible to get it to crash, sometimes it doesn't find dependencies in the jar files, sometimes just deploying war files doesn't work and it needs to be restarted. Its configuration is quite complex.

Think twice if you really need this mammoth in your stack.

Deploying business solution. The primary benefit is that it makes PM feel confident due to its solid track record of powering large enterprises. Can't say the same about developers.

jboss is secure, works well in a clustered environment

it's slow, takes a long time to start up, has a major footprint

I would strongly consider moving to a more lightweight server infrastructure if you can. jboss is ok for what it is, but most of it seems for big monolithic applications in a world where we're moving towards light weight web apps. look at cloud foundry with spring boot, etc.

we use jboss as our primary app server technology for our application in the automotive industry. we connect to apache web servers and mysql databases.

My experience with the Red Hat JBoss revolves around the web server software that they provide. I love that it is an open-source, free software solution. It has allowed myself and the rest of my development team to stand up a web server that we can use for development purposes. It is easily deployed on a local machine or a server on the local network.

Configuration can be a bit confusing, especially for newer users. There are some settings that can cause issues on various platforms, such as OSX. I've also experienced some issues when upgrading JBoss versions (even minor ones) that usually relate to configuration.

As with almost all other open source software, take advantage of the community support for any problems or questions that you have with JBoss.

Allowing our development team to stand up a local web server for testing and continued development.

We had a developer team who immediately started to be productive with JBoss. Seems very easy to start with the prodcut.

Honestly, I don't have any bad point at all with JBoss, unless you dislike Java ;)

We have developed an entire intranet with some advanced features including SSO

Its opensource and allows a lot of configuration and you can install even more plugins if you like

Mostly any configuration must be done through XML files because Admin console is very limited

Web Services and internet base applications solutions implementations and deployment for different customers in public sector, banking and insurance

CLI is very system admin style

configuration file is very convinient

It starts really fast.

Easy to be added in application installation script

Creating a new server by simply copying the default instance

You can't have two different versions of JBoss on the same OS

If you use RPMs, Jboss is exploded all over the place, it follows the Unix conventions for deploying applications, but you end up looking everywhere for jboss

Having JBoss installed from RH repositories the app admin is dependent on unix admins for updates

A good application server to have which is comparatively easier to deploy and not complex to manage.

I am running financial software with jboss. The benefit I am getting is to use the Jboss Installation script with my application installation files to avoid complications to the customers.

The fast configuration and the configuration itself led to you

nothing at all, it's a good and reliable component when dealing with the deployment of software.

Just try it for a period of 2 months and then you can make your own criteria for choosing this software ahead the others you use.

the production deployment of applications

- Quality of Final Solution;

- Quantity of Tools available to help the developer

- Community interaction.

- Too slow to evolve. Nowadays Spring is leading the development in Java.

Web Applications in general.

Jboss is relatively light and easy to install and configure

Java applications at scale can sometimes be hard to manage

Running java applications on Unix-based systems

It just works. It solve our business requirement without issue. It is fast and stable.

It may bit a bit complicated to setup compared to other application server solutions out there.

One of the most battle-tested technology.

It is for hosting Java backend. It is proven technology.