Petals SE EIP

Dispatcher pattern uncoherent behavior in Integration test case

Details

  • Type: Bug Bug
  • Status: New New
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.5
  • Fix Version/s: None
  • Component/s: Dispatcher
  • Security Level: Public
  • Description:
    Hide

    An DONE for ACKNOLEDGMENT was returned during integration test case instead ERROR,for Test 8 RobustInOnly dispatcher with a fault and faultToException.

    This integration test case with Dispatcher pattern expect an ERROR because a exception must be returned by the EIP dispatcher pattern with "faultToException" policy.

    In this test the RMIComponentContext_EIP_1 running Test8 send message with IN_ONLY mep. The EIP Component dispatches the incoming IN message toward the configured 'sub-services' in Consumes sections (here RMIComponentContext_EIP_2 and RMIComponentContext_EIP_3).

    The RMIComponentContext_EIP_2 receive from the dispatcher the exchange of Test 8 with RobustInOnly mep and return DONE
    The RMIComponentContext_EIP_2 wait the incoming message of Test 9.

    An integration exception was generated because expected ACK is ERROR and the ACK recovered was DONE ...

    After that the RMIComponentContext_EIP_3 receive from the dispatcher the exchange of Test 8 with mep RobustInOnly
    and wait the incoming message of Test 9

    I think a timeout can be reached or another cause occurred, before the RMIComponentContext_EIP_3 receive the dispatched message and the expected Fault wasn't set, the EIP Component can't generate the Exception from a Fault because status was setted to DONE by the RMIComponentContext_EIP_2.

    Show
    An DONE for ACKNOLEDGMENT was returned during integration test case instead ERROR,for Test 8 RobustInOnly dispatcher with a fault and faultToException. This integration test case with Dispatcher pattern expect an ERROR because a exception must be returned by the EIP dispatcher pattern with "faultToException" policy. In this test the RMIComponentContext_EIP_1 running Test8 send message with IN_ONLY mep. The EIP Component dispatches the incoming IN message toward the configured 'sub-services' in Consumes sections (here RMIComponentContext_EIP_2 and RMIComponentContext_EIP_3). The RMIComponentContext_EIP_2 receive from the dispatcher the exchange of Test 8 with RobustInOnly mep and return DONE The RMIComponentContext_EIP_2 wait the incoming message of Test 9. An integration exception was generated because expected ACK is ERROR and the ACK recovered was DONE ... After that the RMIComponentContext_EIP_3 receive from the dispatcher the exchange of Test 8 with mep RobustInOnly and wait the incoming message of Test 9 I think a timeout can be reached or another cause occurred, before the RMIComponentContext_EIP_3 receive the dispatched message and the expected Fault wasn't set, the EIP Component can't generate the Exception from a Fault because status was setted to DONE by the RMIComponentContext_EIP_2.
  • Environment:
    Hide
    The environment where the bug can be reproduce is the petals-se-eip project in petals-integration, get the attachments file in order to install the best environment to reproduce the problem. The test 8 is replicate several times in integration1.xml integration2.xml integration3.xml

    RMI client log can be read in petals-se-eip-integration-out.txt, and petals container log can be read in petals.log file.
    The study of the test case, suppositions, description test case, conclusion ... can be view in test-case-study.pdf attached file.
    I also provide a RMIClient for integration and an EIP component with more log
    Show
    The environment where the bug can be reproduce is the petals-se-eip project in petals-integration, get the attachments file in order to install the best environment to reproduce the problem. The test 8 is replicate several times in integration1.xml integration2.xml integration3.xml RMI client log can be read in petals-se-eip-integration-out.txt, and petals container log can be read in petals.log file. The study of the test case, suppositions, description test case, conclusion ... can be view in test-case-study.pdf attached file. I also provide a RMIClient for integration and an EIP component with more log
  1. build.xml
    (19 kB)
    Adrien Ruffie
    Wed, 13 Apr 2011 - 14:39:01 +0200
  2. integration1.xml
    (39 kB)
    Adrien Ruffie
    Wed, 13 Apr 2011 - 14:34:50 +0200
  3. integration2.xml
    (34 kB)
    Adrien Ruffie
    Wed, 13 Apr 2011 - 14:34:50 +0200
  4. integration3.xml
    (26 kB)
    Adrien Ruffie
    Wed, 13 Apr 2011 - 14:34:50 +0200
  5. petals-se-eip-2.6-SNAPSHOT.zip
    (6.70 MB)
    Adrien Ruffie
    Wed, 13 Apr 2011 - 14:39:01 +0200
  6. petals-se-eip-integration-out.txt
    (67 kB)
    Adrien Ruffie
    Wed, 13 Apr 2011 - 14:34:13 +0200
  7. petals.log
    (528 kB)
    Adrien Ruffie
    Wed, 13 Apr 2011 - 14:34:13 +0200
  8. RMIClient.java
    (46 kB)
    Adrien Ruffie
    Wed, 13 Apr 2011 - 14:39:01 +0200
  9. test-case-study.PDF
    (158 kB)
    Adrien Ruffie
    Wed, 13 Apr 2011 - 14:34:13 +0200
  10. wait.patch
    (3 kB)
    Christophe DENEUX
    Fri, 15 Apr 2011 - 14:12:25 +0200

Activity

People

Dates

  • Created:
    Wed, 13 Apr 2011 - 14:33:22 +0200
    Updated:
    Thu, 31 Jan 2019 - 10:55:26 +0100