Petals BC Quartz

Unable to deploy 2 jobs as service consumers of the same service provider invoking different operations

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.7.0
  • Fix Version/s: 1.7.1
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    The Quartz job name is computed from interface name, service name and endpoint name.

    So, potential problem can occurs if we want to create jobs to call different operations of a same service provider with a named endpoint: one job name identifying two jobs

    <jbi:consumes interface-name="mvt:Mouvement" service-name="mvt:MouvementService" endpoint-name="edpMouvement">
    <petalsCDK:operation>mvt:desactiver</petalsCDK:operation>
    ...
    <quartz:cron-expression>${mouvement.desactivation.cron}</quartz:cron-expression>
    ...
</jbi:consumes>

<jbi:consumes interface-name="mvt:Mouvement" service-name="mvt:MouvementService" endpoint-name="edpMouvement">
    <petalsCDK:operation>mvt:suspend</petalsCDK:operation>
    ...
    <quartz:cron-expression>${mouvement.suspend.cron}</quartz:cron-expression>
    ...
</jbi:consumes>

    So please add the operation name to compute the QUartz job name

    Show
    The Quartz job name is computed from interface name, service name and endpoint name. So, potential problem can occurs if we want to create jobs to call different operations of a same service provider with a named endpoint: one job name identifying two jobs 
    <jbi:consumes interface-name="mvt:Mouvement" service-name="mvt:MouvementService" endpoint-name="edpMouvement">
    <petalsCDK:operation>mvt:desactiver</petalsCDK:operation>
    ...
    <quartz:cron-expression>${mouvement.desactivation.cron}</quartz:cron-expression>
    ...
</jbi:consumes>

<jbi:consumes interface-name="mvt:Mouvement" service-name="mvt:MouvementService" endpoint-name="edpMouvement">
    <petalsCDK:operation>mvt:suspend</petalsCDK:operation>
    ...
    <quartz:cron-expression>${mouvement.suspend.cron}</quartz:cron-expression>
    ...
</jbi:consumes>
    So please add the operation name to compute the QUartz job name
  • Environment:
    -

Activity

Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
2m 54s
1
Christophe DENEUX
Fri, 24 Jun 2022 - 12:13:29 +0200
Open Open In Progress In Progress
1s
1
Christophe DENEUX
Fri, 24 Jun 2022 - 12:13:30 +0200
In Progress In Progress Resolved Resolved
24m 8s
1
Christophe DENEUX
Fri, 24 Jun 2022 - 12:37:38 +0200
Resolved Resolved Open Open
21s
1
Christophe DENEUX
Fri, 24 Jun 2022 - 12:37:59 +0200
Open Open In Progress In Progress
1s
1
Christophe DENEUX
Fri, 24 Jun 2022 - 12:38:00 +0200
In Progress In Progress Resolved Resolved
6m 56s
1
Christophe DENEUX
Fri, 24 Jun 2022 - 12:44:56 +0200

People

Dates

  • Created:
    Fri, 24 Jun 2022 - 12:10:35 +0200
    Updated:
    Fri, 24 Jun 2022 - 12:44:56 +0200
    Resolved:
    Fri, 24 Jun 2022 - 12:44:56 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.