What's new in the WSS (Change Log)

Added by Rich Karstens over 7 years ago

Version 0.9.2

Digest Authentication Real for Tomcat Configuration

Due to differences between the names of authentication realms used at different facilities, the digest realm name (nominally 'FDSN') is now configured in the Tomcat startup scripts. Here is a section of code that sets the correctly named system property wss.digest.realmname.

Without this setting, no Realm Name would be set and Tomcat Digest Authentication would not work with authenticated services. Also the default realm name would be reported as ${wss.digest.realmname} and therefore in any browser authentication dialog box.

# This is the name of the REALM used for digest authentication

Client Disconnection Triggers Handler Termination

The WSS will now terminate any running handler if it detects a disconnection from the client. Prior to this release it was necessary for the client to detect this (typically via an IO write error) and exit cleanly. Or not, and that would lead to zombie processes. Hence, this change. :)

Version 0.9.3

Fix for SEED logging

The WSS was dropping the final few blocks of SEED data from its logging procedure. This would result in a summary log message which could be possibly greater than the sum of the individual log messages sent for each network/station/location/channel.

NB: this did not affect actual transmission of SEED data; only the logging of such.

Version 0.9.4

Addition of Counts handler.

In addition to the existing handlers, catalogs and contributors, the WSS now handles an new URI, counts. Note that all three default to XML output. The configurations for each are catalogsHandlerProgram, contributorsHandlerProgram and countsHandlerProgram, respectively.

Change of output type SEED to MSEED

The SEED output type has been changed to MSEED. This requires a change to all configuration files which specify the output format. Also, the actual MIME type reported by the WSS in the response is now changed to miniSEED rather than full seed. Finally, the format sent to a command line handler program via the '--format' parameter is now also 'mseed'.

Version 1.0.1

New Configuraiton 'allowCors'

Enables CORS headers to be appended for all responses.

Version 1.0.2

New configuration: wadlPath

A URI can now be specified (rather than a file) for the WADL.

Version 1.0.3

Minor Logging Issues

  • WSS was failing to log the start and end time logging parameters for mSEED type requests running as a process. This has been corrected.
  • Logging sent to the Usage Logger now sets the logging level to 'ERROR' when logging errors for Log4J logging. All standard usage log messages are logged as INFO.
    • Note that all responses that don't return an HTTP status of 200 will generate an ERROR type message. This includes 204 and obviously, 400, 404, 500

Version 1.0.4

Query Parameter Control of output format (MIME Type)

The WSS was erroneously changed the output format permanently via the '?output=FORMAT' query parameter. This would overwrite the configured outputType from the service.cfg file until the service is restarted. This has been corrected and now the query parameter override will only affect the current request

The WSS was honoring both 'output' and the vestigial 'format' query parameter for this purpose. Support for 'format' is removed.

Version 1.0.5

Query Parameter Control of output format (MIME Type)

Support of the query parameter 'format' is reinstated due to popular demand.

Version 1.0.6

Jersey resource checking limited to Wss package

The init-param, is now set to the package edu.iris.wss. This prevents possible conflicts by Jersey when looking for URL mapping resource when included JARs and other classes might conflict

Version 1.1.0

Added ZIP output type.

As it becomes necessary to accomodate handler programs which need to return multiple file objects, unless we require all handler programs to create ZIP streams, we need a method to handle multiple named file responses from a handler program.

The WSS provides a method for doing this via the creation of an output directory where the handler program can place output files and a new method of monitoring stdin which allows the handler program to tell the WSS line by line that new files have been created and are ready for inclusion in the ZIP stream.


A new output type is added. When this output type is selected via the service configuration file, the WSS will automatically append the special command line parameter --outputdir DIRNAME. DIRNAME is a randomly generated directory name under the WSS instance's working directly (as set in elsewhere in the configuration). When the WSS is done handling the response, the contents of this directory and the directory itself are deleted.

STDIN handling

The WSS still monitors stdin for data, but instead of expecting the data stream to be coming from the handler program on stdin, the WSS will expect fully qualified filenames (i.e. full paths) to be sent from the handler program, one per line. Upon receipt of a line, the WSS will read the file, create a new ZIP entry and write the file's contents to the ZIP stream and finally delete the file.