Release Notes
November 4, 2009About ULC Load 3.0.2
Release 3.0.2 is a maintenance release for ULC Load release 3.0. It includes the following changes:
Version Notes
- Java Runtime
ULC Load requires the Java Runtime Environment (JRE) 1.4.2 or later. It should run on any platform that supports JRE 1.4.2 or later. - UltraLightClient
ULC Load requires UltraLightClient 6.2.2 or later. ULC Load does not run with earlier versions of UltraLightClient.
This build is based on ULC Load 3.0. Please see the ULC Load 3.0.1 release notes for additional information.
Fixed Bugs
| PR | Description | Comments |
| ULO-654 | Memory leak when stopping a test run. | |
| ULO-671 | Using label.setLabelFor(label)) for a ULCLabel results in stack overflow due to recursion in ULCLoad Recorder. | |
| ULO-675 | Sometime the player and the recorder may not process the proxies in the order they are received from the server thus resulting in a mismatch. | |
| ULO-676 | ULCPlayer does not handle setStructure lazy constraint which results in faulty requests for lazy loading requests while playing a scenario. | |
| ULO-678 | Document the new information about window size, window count, duration and number of users in the User's Guide | |
| ULO-679 | Window count and duration in the graph view are not reset to 0 on clear all. | |
| ULO-680 | Since the window size is 30 sec the time line should start from 30 sec instead of 0 in the graph view. | |
| ULO-684 | The recorder should always create samplers under the latest ULC recording controller. | |
| ULO-673 | ULCLoad does not run on Mac OS X. |
Implemented Feature Requests
| PR | Description | Comments |
| ULO-646 | Provide support for custom Servlet connector when playing a recorder scenario. | |
| ULO-674 | Improve response time / throughput graph. | |
| ULO-683 | It should not be optional to create test plan skeleton in the ULC Recorder panel. |
Known Problems and Limitations
- The ULC application load tested by ULC Load needs to be deployed as a Servlet container. A scenario where the ULC application is deployed as a stateful session bean in an EJB container is currently not supported.