WildFly 36 standalone-full.xml requires picketbox?

[Davy Koravand]

Hi,

We are updating from WildFly 26 -> 36 and we can not connect to the jboss-cli due to this:

ERROR [org.jboss.as.cli.CommandContext] Cannot start embedded server: WFLYEMB0021: Cannot start embedded process: JBTHR00005: Operation failed: WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. - Server configuration file in use: standalone-full.xml - Minimum feature stability level: community: WFLYCTL0085: Failed to parse configuration: WFLYCTL0083: Failed to load module org.jboss.as.connector: org.jboss.modules.ModuleLoadError: org.picketbox: org.picketbox
Cannot start embedded server: WFLYEMB0021: Cannot start embedded process: JBTHR00005: Operation failed: WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. - Server configuration file in use: standalone-full.xml - Minimum feature stability level: community: WFLYCTL0085: Failed to parse configuration: WFLYCTL0083: Failed to load module org.jboss.as.connector: org.jboss.modules.ModuleLoadError: org.picketbox: org.picketbox

Removing org.jboss.as.connector extension and the subsystems datasources, jca, resource-adapters seems to remove this dependency on picketbox, but we need datasources for our application. Does anyone know why the deprecated org.picketbox is suddenly required for basic subsystems like datasources? On WildFly 26 this worked fine.

[Darran Lofthouse]

Was this reproductibe using the default configuration that shops with WildFly 36 or are you bringing over your configuration from WildFly 26?

[Davy Koravand]

It was the default configuration. We download the default, then apply jboss-cli lines on it for our own changes. But the jboss-cli does not even start due to this unfortunately.

Op vrijdag 1 augustus 2025 om 11:24:24 UTC+2 schreef Darran Lofthouse:

[Darran Lofthouse]

I have just downloaded WildFly 36 and standalone-full.xml boots for me without any errors.

Can you please post the full stack trace of the error that you are seeing and also attach here the failing standalone-full.xml

--
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/wildfly/3b278205-10b6-4e5d-af1f-284a415e44a2n%40googlegroups.com.

[Bartosz Baranowski]

Do you have some env variables set that could point to other directory than WFLY 36 ?

[Davy Koravand]

The issue is resolved.

I checked a fresh wildfly 36 and it worked fine, so env variables were not the cause. I found that we have ironjacamar-jdbc deployed in modules. I updated it to version 3.0.10.Final and removed org.picketbox from its dependencies to resolve the issue.

Thanks all.