JavaService - Release History

Latest Release

Version 2.0.8 - 6th January 2006

New Features

No new features included in this release - internal changes only.

Bug Fixes

304292 Incorrect error message if -Djava.class.path= not supplied
An incorrect error message was reported if an install command did not explictly define the classpath. This stated that the mandatory -start parameter was not present, even though it was included in the command.
The error is reported when a class path option is not present, but the local environment included a definition for the CLASSPATH variable. This value is picked up and used for the service configuration, but a bug in the code meant that parameter counting and placement was not handled correctly.
The software now handles this condition correctly. It also outputs an informational message whenever the CLASSPATH value is used.

Known Problems

No further known problems with this release.

Compatibility

Backwards-compatible with V2.0 and V1.2 releases of JavaService.

Preceding Releases

Version 2.0.7 - 3rd November 2005

This release of JavaService is based on the new Version 2 code base.
V2.0.7 can now be viewed as stable and is suitable for use in production software environments.

New Features

No new features included in this release - internal changes only.

Bug Fixes

304209 StopServiceThread fails
An error would occur if the stop method was specified, if the start method would return after invocation. The code has now been changed to prevent this run-time error.

Known Problems

No further known problems with this release.

Compatibility

Backwards-compatible with V2.0 and V1.2 releases of JavaService.

Version 2.0.6 - 29th September 2005

New Features

No new features included in this release - internal changes only.

Bug Fixes

303998 Overlapped I/O operation in progress
This problem arose when a service was installed without specifying a shutdown class in the configuration. Code changes have been incorporated to treat this correctly as an optional parameter. Improvements have also been made to error detection and handling in this area of code.

Known Problems

No further known problems with this release.
If no new reports are received, the Version 2 codebase will be moved to 'stable release' status.

Compatibility

Backwards-compatible with V2.0 and V1.2 releases of JavaService.

Version 2.0.5 - 30th August 2005

New Features

No new features included in this release - internal changes only.

Bug Fixes

Error Message Output
A problem was detected (not reported) with output of error messages when failing to install a service. This release fixes this problem so that the correct error message text is displayed on any failure.

Overlapped I/O operation in progress
Some minor code changes have been incorporated towards finding and resolving the cause of this intermittent problem.

Known Problems

There has been a single report of a 'Overlapped I/O operation in progress' error message when attempting to install the CruiseControl service. This does not appear in testing with the SampleService code and is being investigated further. Some changes have been included in this release to work towards a fix.

Compatibility

Backwards-compatible with V2.0.4 and V1.2.12 (and earlier) releases of JavaService.

Version 2.0.4 - 21st August 2005

This version of JavaService is the first official release to be based on the new Version 2 code base.
Hence it should initially be viewed as 'release candidate' status and not used for production software environment until suitable testing and verification has been performed.

New Features

This version incorporates refactored code and additional commands, whilst maintaining complete backwards compatibility with V1.2 commands and configuration entries. The benefits of the new code base are aimed to support easier enhancements with new functionality. There is also a reduction of code duplication, which should in turn reduce the possibilities for errors and improve the maintainability of the application software.

The following new commands are included in this release:-

-queryconfig servicename
To view the configuration entries for the named Java service
-status servicename
To display the current execution status of the named Java service
-license
To output the LGPL licensing text from JavaService
-help command
Displaying further help details for the specified command

The software has been tested using the SampleService code and has undergone debug testing to verify internal operation. The interface at the Windows Service level has been improved, whilst maintaining the same Registry and Java JNI interfaces as used by previous releases of JavaService.

Additionally, using the JavaServiceDebug executable will generated debug-type output to a log file for fault investigation. At present, this filename is fixed internally as C:\javaservice.log

Bug Fixes

There are no specific bug fixes included within this release.

Known Problems

There are no specific bug fixes included within this release.

Compatibility

Backwards-compatible with V1.2.12 (and earlier) releases of JavaService.

Previous Stable Release

Version 1.2.12 - 1st August 2005

This is the final planned release of the JavaService utility from the Version 1.x code base.

It can be viewed as a 'stable' release, with the code having been used in essentially the same form for a number of years, with limited internal changes at each release level.

Refer to V1.x documentation for release notes and prior change history.

Version Numbering

Releases of the JavaService product code are given a three-part version number, which is incorporated in the binary image of the program as well as being used in the source control system. There is a fourth part to the version number, used for internal build release tracking only.

The meaning of each part of the version number is explained below, using V2.0.4.0 as an example:

Version PartDescription
First (2)Major version number indicating codebase of the software
Second (0)Minor version number for directly-compatible releases
Third (4)Incremental version number for patch releases of software
Fourth (0)Build tracking number, may be used for custom builds

Compatibility will be maintained between releases of software with the same major version numbers, unless there is a particular problem identified and resolved in the later release. Software releases with the same major and minor release numbers shall be compatible in all cases (accepting that additional functionality may be included in the later release).