Project

General

Profile

Feature #1031

Environment variable exposing port or logging path

Added by Nick Falco over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Target version:
Start date:
06/20/2019
Due date:
% Done:

100%

Estimated time:
Resolution:
Fixed

Description

Web Service Shell handlers that are not writing in Java currently have no way to dynamically determine the appropriate web service logging path on their server. Having this path would be handy for writing additional debug logs directly from the handler and not through Tomcat.

Tomcat by defaults writes to the logs/ directory in its local instance . For example, ~/server8084/logs/. This logs directory is a symlink to a directory in /wslogs on the server (i.e. ~/server8084/logs -> /wslogs/wsbeta1/server8084/).

The Web Service Shell is already exposing a number of environment variables defined in the following document:

https://seiscode.iris.washington.edu/projects/webserviceshell/wiki/Working_with_Handlers#Environment-Variables-Set-by-the-WSS

During our meeting, we determined that it would be useful to add PORT number to this list, as well as, LOGGING_DIRECTORY which would be the absolute path to the appropriate ~/server####/logs directory for the given instance.

Whiteboard notes

IMG_0441.jpg (712 KB) IMG_0441.jpg Whiteboard notes Nick Falco, 06/20/2019 09:49 AM

History

#1 Updated by Mick Van Fossen over 2 years ago

In progress.

Hoping these 2 variable names will do? PORT && TOMCATLOGDIR

#2 Updated by Nick Falco over 2 years ago

This worked perfectly Mick. Thanks for making the update. I've deployed the change in ph5wsbeta and will deploy it to production once a new web service shell release is published.

#3 Updated by Mick Van Fossen over 2 years ago

  • Resolution set to Fixed
  • % Done changed from 0 to 100
  • Target version set to 2.4.10
  • Assignee set to Mick Van Fossen
  • Status changed from New to Resolved

Done. Deployed as 2.4.10

Also available in: Atom PDF