DWR

Wrong collection returned when same function name called consecutively

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Trivial Trivial
  • Resolution: Cannot Reproduce
  • Affects Version/s: None
  • Fix Version/s: 3.0.RC2
  • Component/s: Core
  • Description:
    Hide
    When calling the same function 4 times consecutively passing a different
    paramter the same result is always returned. While debugging on the server side
    (jboss), I have noted that the result passed back (a collection) is different.
    However, DWR appears to be getting confused and always returns the same result
    for each call.

    I have noticed that if I put each call between a begin/endbatch that the correct
    result is returned.

    This is only for 1.1. 1.0 does not have this issue.

    LabBean.getMaterials(displayMaterialJewels, 1);
    LabBean.getMaterials(displayMaterialReversedItems, 2);
    LabBean.getMaterials(displayMaterialReversedJewels, 1);
    LabBean.getMaterials(displayMaterialItems, 2);

    Was: https://dwr.dev.java.net/issues/show_bug.cgi?id=100
    Show
    When calling the same function 4 times consecutively passing a different paramter the same result is always returned. While debugging on the server side (jboss), I have noted that the result passed back (a collection) is different. However, DWR appears to be getting confused and always returns the same result for each call. I have noticed that if I put each call between a begin/endbatch that the correct result is returned. This is only for 1.1. 1.0 does not have this issue. LabBean.getMaterials(displayMaterialJewels, 1); LabBean.getMaterials(displayMaterialReversedItems, 2); LabBean.getMaterials(displayMaterialReversedJewels, 1); LabBean.getMaterials(displayMaterialItems, 2); Was: https://dwr.dev.java.net/issues/show_bug.cgi?id=100

Activity

Hide
David Marginian added a comment - 06/Aug/10 9:37 PM

This is so old I am sure it does not apply. But let's add a test for it and resolve it for RC2.

Show
David Marginian added a comment - 06/Aug/10 9:37 PM This is so old I am sure it does not apply. But let's add a test for it and resolve it for RC2.
Hide
David Marginian added a comment - 11/Aug/10 8:54 PM

It seems we have numerous tests in our suite that would catch this problem. I have added another test that calls 5 remote methods consecutively and verifies that the data passed in is returned correctly. This issue is so old my guess this issue was resolved a long time ago.

Show
David Marginian added a comment - 11/Aug/10 8:54 PM It seems we have numerous tests in our suite that would catch this problem. I have added another test that calls 5 remote methods consecutively and verifies that the data passed in is returned correctly. This issue is so old my guess this issue was resolved a long time ago.

People

Dates

  • Created:
    23/Feb/07 3:22 AM
    Updated:
    11/Aug/10 8:54 PM
    Resolved:
    11/Aug/10 8:54 PM