JBoss Reviews

We used JBoss as our application server on the recommendation of the lead developer. JBoss's compatibility with Java EE, modularity, and support for clustering met the diverse needs of our applications. The management console and developer-friendly features simplify configuration and maintenance. JBoss provided a reliable and efficient runtime environment for our Java-based applications.

The most valuable thing about JBoss is how easy it is to install and manage it on-premise, making the process simple. The application setup is neat and easy to follow. Although we used to manually check log files, integrating a monitoring tool later on improved efficiency. Overall, JBoss is user-friendly and adapts well to changing monitoring requirements.

The version of JBoss we used, which was quite old (version 4), lacked a user-friendly web console or portal for easy server management. It would be beneficial to have a console for configuration to simplify the administrator's tasks. In terms of monitoring, the old version was somewhat limited in flexibility, lacking the ability to easily adjust configurations.

I used JBoss for a previous project at my company.

JBoss stability depends on the administrator's familiarity with adjusting Java's memory settings. If you're not familiar with it, the application might not be very stable. But once you understand how to allocate the necessary memory, JBoss runs reliably.

JBoss is scalable. It supports configuring both load-balanced and clustered architectures, enabling scalability for the applications it hosts. Approximately 5,000 people used it at our company.

It takes less than an hour to deploy JBoss. Deploying it was a bit manual. We downloaded JAR files from the JBoss community edition website, ran a script on Linux, and manually copied and configured the Java application using the provided templates. It worked, but the process could have been smoother, especially compared to modern containerized deployment methods. Three lead engineers were responsible for setting up and maintaining the application servers.

We didn't pay for a license because we used the JBoss community edition, which is free.

I would recommend JBoss to others. Overall, I would rate it as a nine out of ten.

I use the solution in my company since we have developed an application that runs on the application server, JBoss, and another application server, such as Oracle WebLogic Server or WebSphere. In my company, we developed an application for the bank, and we deployed it under JBoss, WebSphere, or Oracle WebLogic Server.

The most valuable feature of the solution for me stems from the fact that our company can develop applications on JBoss, and we didn't see anything like it compared to WebLogic and WebSphere. The facility to install and handle JBoss is much lighter than the other application servers.

My company had faced some issues where our questions were not answered, and we did not receive proper solutions the way we wanted. The technical support of the product can be improved. Response time for support could be a bit better.

The price of the product is an area of concern where improvements are required. The product could be made cheaper.

I have been using JBoss for eight years. My company has a partnership with Red Hat.

Stability-wise, I rate the solution an eight out of ten.

My company did not face any issues related to scalability. Scalability-wise, I rate the solution a seven out of ten.

My company works with banks of both small and big sizes.

I rate the technical support a seven out of ten.

Neutral

In comparison with the other products I have used in the past, I like JBoss's simplicity, lightness, and cost. Considering what my company used to use both solutions for, JBoss was better than WebLogic.

The product's initial setup phase is easy.

For the product's deployment and maintenance, our company has a system engineer who maintains both our instances associated with JBoss and supports the bank engineers.

The product offers a good return on investment.

I rate the product price as eight on a scale, where one means it is a very cheap solution, and ten points mean that it is a very expensive tool.

In terms of how JBoss supports enterprise Java standards and positively impacts our company's project, I can say that we use it, and we didn't have any issues. In our company, we have been able to do a posting of the application on the other application servers.

My company has not faced issues with the integration of the product with other software tools or infrastructures.

The product fits our company's requirements.

I recommend the product to others.

I rate the tool an eight out of ten.

JBoss is a middleware product. The customers use it to make connections between front-end applications and databases.

Red Hat provides the product and the support. We get good support from the support team. It is one of the benefits.

The product could be cheaper. The solution recently increased the prices.

I have been working with the product for 6 months to a year.

The tool is stable. The customers are buying the product.

The tool is scalable. We can install additional servers. We can extend our cluster horizontally.

The support is fast and reliable. It is very good. If we raise a support ticket, the support team will solve the problem somehow.

The deployment is not that complex. It is easy.

We pay a yearly subscription fee. There are no additional costs associated with the product.

I recommend the tool to others. Overall, I rate the solution an 8 out of 10.

I use JBoss for our websites and multiple products.

The greatest benefit of JBoss is that it was procured by IBM, thereby offering exceptional support for our banking operations.

The stability of the solution could improve with Microsoft Windows.

I have been using JBoss for approximately 10 years.

The stability of JBoss. However, if we are using Linux it is more stable than if we are using Microsoft Windows.

JBoss is capable of scaling, and it supports clustering for scalability. However, if clustering is not supported, we would need to use a load balancer to achieve scalability.

We have our own team that handles the support. I have not contacted the vendor for support.

We are using the web application server from IBM.

The setup of JBoss was straightforward.

We have a Red Hat professional partner who helps us with the implementation of the solution.

The number of people needed for the implementation depends on the build. If the setup is basic then one person can handle it.

The return on investment from JBoss depends on the specific solutions being used. In our case, based on the solutions we are running, I don't believe we are getting a good ROI. If we were running a large-scale solution such as a channel, then it would make sense. However, if we are using a small free solution, such as a back-office solution, and investing in expensive licenses, it may not be very cost-effective.

Despite the price increase after being acquired by IBM, JBoss still maintains its competitiveness. The package provided is more geared towards cloud-based deployments, whereas our setup is more traditional, which makes it slightly more expensive for us. As most vendors are transitioning towards cloud-centric solutions, companies like ours need to adapt accordingly.

The license from JBoss. There is a CAPX cost and an annual cost.

All the solutions we use are on-premise because we are a bank institution. However, we use some SaaS solutions but they are not connected to the on-premise systems.

I would recommend JBoss to others.

I rate JBoss a nine out of ten.

We use JBoss exclusively for API integration and do not use it for other purposes. Our focus is solely on providing services and configuring ACLs.

Certain works are being done very well with JBoss due to its peer configuration. The various styles of services offered by JBoss are very useful for our company and other companies as it becomes difficult for businesses to afford too many services running on different computers. In short, JBoss is a good product. We use several instances, such as Java instances, and also install numerous services within the solution.

Logging-related issues in JBoss require improvement. Also, another problem in the solution is that once the developer finishes coding, minor changes are often required when deploying Red Hat Fuse. Though the developer already knows these changes, there may be some dependency problems and the need to install JAAS. The other issue in JBoss is related to instances being stuck.

I have been working with the solution for four years.

For our company, JBoss is a stable tool. However, I won't be able to speak for other people.

JBoss is a scalable tool.

Regarding the setup of JBoss, it is a standalone setup, which is straightforward. So, we are not using a domain setup. The solution's deployment was done four years ago. Additionally, the solution's setup is done on Openshift, which is a cloud-based platform.

Since the solution is freeware, our customers don't need to pay any licensing fees. The only element that requires payment is RHEL.

We use Git as a version controller, with the help of which the developers do coding and then commit their changes for a game. We have been using Git for four years.

I recommend JBoss to people who want to start using the solution. It is not a complicated tool to use. We are deploying different services over different instances. So, we reduce the cost over the one server, which we use to provide more than 600 services. Overall, I rate this solution a ten out of ten.

For our application to deploy, we used to set up different platforms. We are certifying JBoss support as well for the deployment.

JBoss's configuration is straightforward and easy. It is easy to edit one standalone dot XML file with all the configurations.

The solution sometimes crashed and had some compatibility issues with the DevOps JAR file.

JBoss's next release should include a one-click solution for clustering or straightforward installation.

I have been using JBoss for three to four years.

I rate JBoss a seven out of ten for stability.

JBoss is a scalable product and 100 people were using it in our company.

The initial setup of JBoss is easy. However, the clustering part was a little bit complex.

I recommend people to use JBoss because it is easy to set up and install.

Overall, I rate JBoss an eight to nine out of ten.

The use cases include online webshops and any organization doing online business can use JBoss.

It is fast. You can quickly migrate applications to JBoss and create things like webshops.

I have experience with this product. I've worked with JBoss before but without Red Hat. But now, it comes with Red Hat's JBoss.

I would rate the stability a ten out of ten. 

I would rate the scalability a ten out of ten. It is very scalable. 

We have contacted the technical support team now and then. 

The initial setup is straightforward and quick. You can deploy it standalone or with the Red Hat runtime, which bundles JBoss.

Licensing costs are always debatable. While there are free, open-source alternatives like Java EE and WildFly, they lack the support and reliability of a paid, certified product like JBoss. 

With JBoss, you get the peace of mind of premium support and avoid potential issues in production environments. 

So, for production environments, I recommend certified products with support. For testing, free, open-source options are fine.

Overall, I would rate the solution a ten out of ten. 

JBoss is an on-premises solution we use in a banking setting.  It is used to manage servers and applications. There are two modes: domain and development. We can monitor and control all types of deployments in JBoss.

We have around 20,000 to 30,000 users on the same application and everything is going via the JBoss. We were using JBoss 1.0 when I first installed it, but they've probably included some more security patches in the latest version. 

We can deploy the applications on the JBoss server, so it is easy to manage. It's also easy to add new certificates to the config.

The documentation could be better. When we have questions, we need to check multiple websites. There isn't one place listing a set of common problems and how to fix them. 

I've been using JBoss since I joined the company three years ago. 

I haven't had any complaints in production, but in development and UAT, I've noticed that some of the applications are not deployed properly, and errors need to be fixed.

I used Tomcat when I worked for a cement manufacturer in India. They were a small-scale company, so we preferred Tomcat server. When I started working in finance, the bank suggested we go with JBoss. JBoss is easier to handle, and it can take on a much larger load compared to Tomcat.

Setting up JBoss is more complex relative to Tomcat. We need to follow the set of steps because it's not like we are installing a single system. Several separate systems need to be connected using the common prompt. There will be a common for that. After generating, we need to connect with the other ID with the main deployment controller.

There is one deployment controller, and we need to connect the separate server nodes using that. I use a trial-and-error process for the JBoss installations for the development. We follow the steps and document everything. After we do it once, it's not complex the second time because we know all the steps we need to follow. 

We don't use outside consultants. It's open source, so we do some R&D and a process of trial and error in the development environment. There is no help JBoss or a consultant. The banking team works with the development team to get it done.

I rate JBoss seven out of 10. I would recommend Tomcat for a small-scale use case. It's easy to maintain and deploy, and the UA interface is simple. JBoss is more appropriate for large industries. Though it is complex to maintain, JBoss is well balanced and can handle larger loads.