Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1180450

Summary: Cron Syntax in timer boundary events and timer intermediary catch events Causing Parse Error
Product: [Retired] JBoss BPMS Platform 6 Reporter: sfu <sfu>
Component: jBPM CoreAssignee: Alessandro Lazarotti <alazarot>
Status: CLOSED EOL QA Contact: Marek Baluch <mbaluch>
Severity: medium Docs Contact:
Priority: high    
Version: 6.0.3CC: kverlaen, mbaluch
Target Milestone: ER5   
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1195135 (view as bug list) Environment:
Last Closed: 2020-03-27 20:02:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1195135    
Attachments:
Description Flags
reproduce syntax parse error none

Description sfu@redhat.com 2015-01-09 09:19:20 UTC
Created attachment 978072 [details]
reproduce syntax parse error

Description of problem:

In BPMS 6.0.3, Intermediate Timer Events with the “Cron” syntax option selected and a Time Cycle of “0/1 * * * * ?” throw a syntax parse error at build time.

Version-Release number of selected component (if applicable):

How reproducible:

Please import the attachment.

Steps to Reproduce:
1.Create a Intermediate Timer Events

2.Type into a correct cron expression like "0/1 * * * * ?" in the Time Cycle  and select Time Cycle language to cron

3.See the problem console

Actual results:
There is a parse error.

Expected results:
No error.

Additional info:

Attached reproducer , please check.

Comment 2 sfu@redhat.com 2015-01-09 09:53:39 UTC
As a workaround, we assigned the cron string to a process variable “cronStr”, and set the Time Cycle to #{cronStr}.  The build compiles, but throws the same syntax parse error at runtime.So other issue is wrapping cron expression into the process variable is causing runtime failure.

Comment 4 Sona Mala 2015-02-20 13:34:33 UTC
This issue was verified on 6.1.0 ER5.

The attached process was saved without any problems. The process was deployed and started without problems. The 'Send update' human task was generated every minute.

Comment 5 Jiri Svitak 2015-02-24 14:35:20 UTC
The fix has been done only in jbpm core. Changing the component and adding a unit test coverage:
https://gitlab.mw.lab.eng.bos.redhat.com/bxms/brms/commit/5a7cc29718fa89af486309c8fb7519bc930b89b2