You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2012/11/15 22:28:48 UTC

[Bug 54153] New: SampleSender should take into account SaveService configuration to remove data not persisted by SaveService

https://issues.apache.org/bugzilla/show_bug.cgi?id=54153

          Priority: P2
            Bug ID: 54153
          Assignee: issues@jmeter.apache.org
           Summary: SampleSender should take into account SaveService
                    configuration to remove data not persisted by
                    SaveService
          Severity: enhancement
    Classification: Unclassified
                OS: All
          Reporter: p.mouawad@ubik-ingenierie.com
          Hardware: All
            Status: NEW
           Version: 2.8
         Component: Main
           Product: JMeter

Today SampleSender does not take into account SaveService configuration in
remote sampling.
This leads SampleSender to send data to controller that is not persisted by
SaveService. 
This should be changed by maybe sending SaveService Configuration summary of
Controller to servers so that they can remove non persisted fields

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 54153] SampleSender should take into account SaveService configuration to remove data not persisted by SaveService

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=54153

--- Comment #2 from Sebb <se...@apache.org> ---
Since the entire test plan is sent to the server (some classes are modified
slightly), I would expect the configuration to be already present on the
server.

It's just a question of finding the correct place plug the code in.

Warning: a single sample may be processed by several different listeners, each
of which may have different configuration setttings, so the original sample
result must be preserved.

This means that a copy of the sample has to be created.
Might be sensible to provide a copy method that filters based on the
SaveService configuration (rather than doing a full copy and adjusting it
later).

It will of course be more work to create the copy, however it should allow the
amount of transmitted data to be reduced.

Given that it may place an extra load on the server, I think the behaviour
should be optional.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 54153] SampleSender should take into account SaveService configuration to remove data not persisted by SaveService

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=54153

Philippe Mouawad <p....@ubik-ingenierie.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |p.mouawad@ubik-ingenierie.c
                   |                            |om

--- Comment #1 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
At start of test, we could send a simple bean 
representing what has been configured in CSVSaveService or SaveService,
And we could implement a new SampleSender using that config.

-- 
You are receiving this mail because:
You are the assignee for the bug.