Petals SE POJO

Unable to invoke a service asynchronously

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 2.4.1
  • Fix Version/s: 2.5.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    I have written a POJO SU that invoke a sub-service asynchronously (ie. using jbiListener.sendAsync(exchange, context).

    The request to invoke the sub-service is correctly sent. The sub-service receives correctly the request, and sends its reply. But no reply is received by my POJO. The following log traces appears:

    ... FINE [Petals.Container.Components.petals-se-pojo] : Accepting a JBI message with Id : petals:uid:fff6e090-ee07-11e6-8010-024212ca4f1c
    ... FINE [Petals.Container.Components.petals-se-pojo] : Remove AsyncContext (as consumer) for exchange petals:uid:fff6e090-ee07-11e6-8010-024212ca4f1c
    ... FINE [Petals.Container.Components.petals-se-pojo] : Retrieved flow attributes (Flow[instance=fff44880-ee07-11e6-8010-024212ca4f1c, step=fff69270-ee07-11e6-8010-024212ca4f1c]) from async context (petals:uid:fff6e090-ee07-11e6-8010-024212ca4f1c)
    ... FINE [Petals.Container.Components.petals-se-pojo] : Flow attributes for exchange (id petals:uid:fff6e090-ee07-11e6-8010-024212ca4f1c) set to Flow[instance=fff44880-ee07-11e6-8010-024212ca4f1c, step=fff69270-ee07-11e6-8010-024212ca4f1c]
    ... FINE [Petals.Container.Components.petals-se-pojo] : Process an exchange as CONSUMER with id : petals:uid:fff6e090-ee07-11e6-8010-024212ca4f1c
    ... FINE [Petals.Container.Components.petals-se-pojo] : The exchange 'petals:uid:fff6e090-ee07-11e6-8010-024212ca4f1c' refers to an unknown consumer on the component : petals-se-pojo. The listener will not have the consumes and the extensions for this exchange
    ... SEVERE [Petals.Container.Components.petals-se-pojo] : Failed to find the POJO instance matching the endpoint 'edpt-564119a0-edfb-11e6-bfeb-024212ca4f1c'
    Show
    I have written a POJO SU that invoke a sub-service asynchronously (ie. using jbiListener.sendAsync(exchange, context). The request to invoke the sub-service is correctly sent. The sub-service receives correctly the request, and sends its reply. But no reply is received by my POJO. The following log traces appears:
    ... FINE [Petals.Container.Components.petals-se-pojo] : Accepting a JBI message with Id : petals:uid:fff6e090-ee07-11e6-8010-024212ca4f1c
    ... FINE [Petals.Container.Components.petals-se-pojo] : Remove AsyncContext (as consumer) for exchange petals:uid:fff6e090-ee07-11e6-8010-024212ca4f1c
    ... FINE [Petals.Container.Components.petals-se-pojo] : Retrieved flow attributes (Flow[instance=fff44880-ee07-11e6-8010-024212ca4f1c, step=fff69270-ee07-11e6-8010-024212ca4f1c]) from async context (petals:uid:fff6e090-ee07-11e6-8010-024212ca4f1c)
    ... FINE [Petals.Container.Components.petals-se-pojo] : Flow attributes for exchange (id petals:uid:fff6e090-ee07-11e6-8010-024212ca4f1c) set to Flow[instance=fff44880-ee07-11e6-8010-024212ca4f1c, step=fff69270-ee07-11e6-8010-024212ca4f1c]
    ... FINE [Petals.Container.Components.petals-se-pojo] : Process an exchange as CONSUMER with id : petals:uid:fff6e090-ee07-11e6-8010-024212ca4f1c
    ... FINE [Petals.Container.Components.petals-se-pojo] : The exchange 'petals:uid:fff6e090-ee07-11e6-8010-024212ca4f1c' refers to an unknown consumer on the component : petals-se-pojo. The listener will not have the consumes and the extensions for this exchange
    ... SEVERE [Petals.Container.Components.petals-se-pojo] : Failed to find the POJO instance matching the endpoint 'edpt-564119a0-edfb-11e6-bfeb-024212ca4f1c'
  • Environment:
    -

Activity

Christophe DENEUX made changes - Wed, 8 Feb 2017 - 15:09:31 +0100
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Blocker [ 1 ]
Christophe DENEUX made changes - Wed, 8 Feb 2017 - 15:09:36 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Christophe DENEUX added a comment - Wed, 8 Feb 2017 - 17:45:10 +0100

Fixed in trunk

Show
Christophe DENEUX added a comment - Wed, 8 Feb 2017 - 17:45:10 +0100 Fixed in trunk
Christophe DENEUX made changes - Wed, 8 Feb 2017 - 17:45:10 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 2.4.2 [ 10695 ]
Resolution Fixed [ 1 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
14s
1
Christophe DENEUX
Wed, 8 Feb 2017 - 15:09:31 +0100
Open Open In Progress In Progress
5s
1
Christophe DENEUX
Wed, 8 Feb 2017 - 15:09:36 +0100
In Progress In Progress Resolved Resolved
2h 35m
1
Christophe DENEUX
Wed, 8 Feb 2017 - 17:45:10 +0100

People

Dates

  • Created:
    Wed, 8 Feb 2017 - 15:09:17 +0100
    Updated:
    Wed, 8 Feb 2017 - 17:45:10 +0100
    Resolved:
    Wed, 8 Feb 2017 - 17:45:09 +0100