Forum Discussion
omatzura
17 years agoSuper Contributor
Hi Magnus,
thanks for you post.. currently MockResponse steps are synchronized during loadtests.. so the one that "listens first", gets the first request. Unfortunately I don't really know how we could achieve this with the current implementation.
Your idea with different ports is good.. also we could have some configurable identifier in the incoming request that is used to "select" the corresponding loadtest-thread via a property or something.. (for exmple a session-id).. does that sound viable?
any other ideas are very welcome!
regards!
/Ole
eviware.com
thanks for you post.. currently MockResponse steps are synchronized during loadtests.. so the one that "listens first", gets the first request. Unfortunately I don't really know how we could achieve this with the current implementation.
Your idea with different ports is good.. also we could have some configurable identifier in the incoming request that is used to "select" the corresponding loadtest-thread via a property or something.. (for exmple a session-id).. does that sound viable?
any other ideas are very welcome!
regards!
/Ole
eviware.com