Environment: 

• RHPAM 7.11.1
• deployed one-off for RHPAM-4192 (RHPAM-4211);
• The process is deployed using "PER_REQUEST" runtime strategy;
• Executed GET timers REST API 

When GET timers REST API is executed, for the process deployed using "PER_REQUEST" runtime strategy the timer is returned with all null(s) and 0(s)... for instance:
**************************
curl -X GET "
http://localhost:8080/kie-server/services/rest/server/admin/containers/QuartzTimerProject_2.0.0-SNAPSHOT/processes/instances/15/timers
" -H "accept: application/json"
**************************

and returned result:

**************************

{ "timer-instance": [

{ "name": null, "id": 0, "timer-id": 0, "activation-time": null, "last-fire-time": null, "next-fire-time": null, "delay": 0, "period": 0, "repeat-limit": 0, "process-instance-id": 0, "session-id": 0 }

]
}

**************************

If the same project is deployed using "PER_PROCESS_INSTANCE", the above GET timers REST API will return:

**************************
{
"timer-instance": [
{
"name": "",
"id": 1,
"timer-id": 0,
"activation-time":

{ "java.util.Date": 1698924549602 }

,
"last-fire-time": null,
"next-fire-time":

{ "java.util.Date": 1698928149602 }

,
"delay": 3600000,
"period": 0,
"repeat-limit": -1,
"process-instance-id": 16,
"session-id": 37
}
]
}
**************************
 

The purpose of this Jira is to have an equivalent outcome when using "PER_REQUEST" runtime strategy as that is the case with "PER_PROCESS_INSTANCE". The attached reproducer can be used to see the problem.