Solved
Forum Discussion
AJaensson
Staff
Hi,
This has been fixed in the maintenance builds of Ready! API (available here). Using that build, the -Dsoapui.mock.connector.headerBufferSize=<my new value> option is available again.
We do have plans to upgrade jetty, but it is a pretty big change and it has to be prioritized against other tasks.
Regards,
Anders
Ready! API developer
psy
9 years agoOccasional Contributor
Ready! API nightly build 1.4.1 contained the fix and now the version 1.5.0 is released, but no (sub) release note is mentioning this fix. http://readyapi.smartbear.com/about/release_notes/start As an improvement, it would be helpful to see all changes in release note. We have already enough fixes and features as submarine in our business applications. A tool for testing should be better. ;-)
- psy9 years agoOccasional ContributorVersion 1.6 is out, but the fix is never mentioned up to now in any change log. But the page for "Java Virtual Machine Parameters" contains the property. Issue is solved at all :-) http://readyapi.smartbear.com/soapui/working/environment_settings/jvm_options
Related Content
- 6 years agodrwohlers