Configuring MS SQLServer Datasource in WildFly

In this tutorial we will learn how to configure Microsoft SQLServer Datasource on WildFly application server First of all, you need a JDBC Driver which is fit for your SQLServer version. You can download the JDBC Driver from Microsoft’s site: https://docs.microsoft.com/en-us/sql/connect/jdbc/microsoft-jdbc-driver-for-sql-server Some popular options include: mssql2017: mssql-jdbc-7.4.1.jre8.jar mssql2016: mssql-jdbc-6.4.0.jre8.jar Then, from the jboss-cli.sh connect and … Read more

WildFly basic requirements

In this short tutorial we will learn which are the basic requirements to run WildFly application server. The basic requirements to start WildFly are: A JDK available on your machine The right amount of memory settings for the JDK. Let’s see both requirements. Download the appropriate JDK for your WildFly version Each recent WildFly version … Read more

How to run WildFly on AWS EC2

In this tutorial I’ll show you how you can install Wildfly application server on Amazon EC2 instance. The pre-requesite is that you have already your Amazon account available, so you are ready to launch a new Instance: In the next Window, choose one of the available Images, for example a RHEL 8: You will have … Read more

Getting started with Apache Kafka and WildFly

This tutorial will teach you how to install a Resource Adapter for Apache Kafka on WildFly so that you can Produce and Consume streams of messages on your favourite application server! First of all some basics: what is Apache Kafka? Apache Kafka is a Streaming Platform which provides some key capabilities: Publish and subscribe to … Read more

How to monitor JBoss 5 with snapshots?

This tutorial has been written for an old version of JBoss AS 5. At the bottom of it, you will find how to collect snapshots with JBoss 5 from the JMX-Console. If you are running WildFly or JBoss EAP 7, we recommend the following updated resources: Monitoring Enterprise applications with OpenShift and Prometheus Monitoring WildFly … Read more

Keycloak quickstart example using CLI

In this tutorial we will learn how to create a quickstart Java EE application secured with Keycloak using its command line interface (kcadm). The requirements to run this tutorial are: A Keycloak server A WildFly Application Server with Keycloak plugin installed You can check this tutorial for more details about the set up of Keycloak … Read more

Configuring no-request-timeout in WildFly

The no-request-timeout attribute specifies the length of time in milliseconds that a connection is idle before it is closed. The default value is 60000 milliseconds (1 minute). Here is how you can check its value: /subsystem=undertow/server=default-server/http-listener=default:read-attribute(name=no-request-timeout) { “outcome” => “success”, “result” => 60000 } And conversely you you can increase it: /subsystem=undertow/server=default-server/http-listener=default:write-attribute(name=no-request-timeout, value=70000) Tuning this … Read more

Configuring Ranked Load Balancing in WildFly

One of the new features included in WildFly 18 is the ability to load balance requests using a ranked order of preference. The default session affinity algorithm in a WilFly cluster is set by the “affinity” attribute: /subsystem=undertow/configuration=filter/mod-cluster=load-balancer:read-resource() { “outcome” => “success”, “result” => { “advertise-frequency” => 10000, . . . . “affinity” => {“single” … Read more

From Java EE to Jakarta EE with WildFly

WildFly 18 has been released and one of the most interesting news is the alignment of the project with Jakarta EE 8 API. WildFly 17.0.1 was the first release of the applicaiton server certified as a Jakarta EE 8 compatible implementation. In terms of API do we have anything to change in our configuration ? … Read more

Solving WildFly unable to accept remote connections

If your WildFly server is unable to accept remote connections then keep reading this tutorial, we will help you to solve the issue. For security reasons, WildFly application server uses for its public and management interfaces, as fallback the loopback address: <interfaces> <interface name=”management”> <inet-address value=”${jboss.bind.address.management:127.0.0.1}”/> </interface> <interface name=”public”> <inet-address value=”${jboss.bind.address:127.0.0.1}”/> </interface> </interfaces> This means, … Read more