With more recent versions of WildFly (11), we're seeing the following warning in server.log:

11:41:44,124 WARN [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-43) RESTEASY002142: Multiple resource methods match request "GET /jobexecutions/running". Selecting one. Matching methods: [public org.jberet.rest.entity.JobExecutionEntity[] org.jberet.rest.resource.JobExecutionResource.getRunningExecutions(java.lang.String,javax.ws.rs.core.UriInfo), public org.jberet.rest.entity.JobExecutionEntity org.jberet.rest.resource.JobExecutionResource.getJobExecution(long,javax.ws.rs.core.UriInfo)]

RESTEASY002142: Multiple resource methods match request "GET /schedules/features". Selecting one. Matching methods: [public java.lang.String[] org.jberet.rest.resource.JobScheduleResource.getFeatures(), public org.jberet.schedule.JobSchedule org.jberet.rest.resource.JobScheduleResource.getJobSchedule(java.lang.String)]

This may have been caused by more recent version of RESTEasy, which seems to be more strict in matching request path.

See related discussion:
https://stackoverflow.com/questions/39635174/can-resteasy-look-into-parameters-type-for-jax-rs-methods

This issue is also reflected in JBeret REST API docs, with the following warning:

This rest interface (partially) hides another rest interface

/jobexecutions/running/

method: org.jberet.rest.resource.JobExecutionResource.getRunningExecutions

Overlaps with: /jobexecutions/{jobExecutionId}