Profile Photo
Hi,   I have a Gradle project that I'm using WildFly-CLI java lib to deploy applications.   compile group: 'org.wildfly.core', name: 'wildfly-cli', version: '4.0.0.Final'  Everything works fine however I would like to disable the CLI logs on console. When I deploy an application the CLI logs something like: WARN: can't find jboss-cli.xml. Using… (Show more)
in WildFly
Profile Photo
Click to view larger imageI recently updated to WildFly 18.0.0.Final/HAL 3.2.1.Final from WildFly 16.0.0.Final/HAL 3.1.2.Final and noticed the following:   Selecting Runtime > MicroProfile Health item will show a DOWN outcome when no health checks are present. The http://$host:$http.management.port/health endpoint returns an UP outcome with an empty list of checks.   In… (Show more)
in WildFly
Profile Photo
Used WildFly: 17.0.1.Final   1. Steps to reproduce: Start WildFly 2. Deploy simple WAR with an Entity (in my case"MyEntity"), a web.xml and persistence.xml. 3. Access metrics using *hostname*:9990/metrics   Used dependencies: <dependency>… (Show more)
in WildFly
Profile Photo
I am currently migrating from JBoss AS 4.2.2 to WildFly 9.0.2. Some applications have MBeans that access EJB 2.x components in a stop() lifecycle method like this: … (Show more)
in WildFly
Profile Photo
I recently upgraded from WildFly 9.0.2.Final to WildFly 16.0.0.Final.   I have been using the jboss-client.jar in standalone client apps, but am in the process of switching to using the wildfly-ejb-client-bom and wildfly-jms-client-bom dependencies.   One of the main reasons for this is I discovered some classpath conflicts due to the… (Show more)
in WildFly