Hi,
I've verified the bug with the Table Log component, this will be fixed in the final release. The documentation should be updated as well. When in distributed mode, the checkbox enables the display (disabled by default, since it can require sending a lot of network traffic), but writing to the log file should always be enabled when the component is configured to do so. As a workaround until the final version is released, you can use the attached updated TableLog component.
Regarding the HTTP Sessions, it should work as you describe you want it to. Are you saying that the initial request from the 'logon' runner, directly triggered by a Generator component, seems to have some HTTP state already set? This shouldn't be the case, so that sounds like a bug. How is this session kept? As a cookie? If you could perhaps share your projects (both the loadUI project as well as any soapUI projects used by it) we can take a look at it and see if we can figure out what's going on. You can either attach the files to this forum thread or send them via email to smartbear-sweden-support *AT* smartbear _DOT_ com.
Lastly, there won't be anything in loadUI 2.0 to help you with ramping up a Fixed Load component, but it's very likely that we'll add something in the next version after that. Currently your best bet is to create a custom component which does what you want, using the FixedLoad Component as a base. There're some developer documentation available on the subject
here.
Regards,
Dain
SmartBear Software
