Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update METviewer to run with Java 11 and a newer version of Tomcat #530

Open
7 of 23 tasks
jprestop opened this issue May 13, 2024 · 0 comments
Open
7 of 23 tasks

Update METviewer to run with Java 11 and a newer version of Tomcat #530

jprestop opened this issue May 13, 2024 · 0 comments
Assignees
Labels
alert: NEED ACCOUNT KEY Need to assign an account key to this issue component: build process Build process issue priority: medium Medium Priority requestor: METplus Team METplus Development Team type: task An actionable item of work

Comments

@jprestop
Copy link
Contributor

jprestop commented May 13, 2024

Describe the Task

Update METviewer to run with Java 11 and a newer version of Tomcat. From Tatiana: This work will require a sysadmin's help with updating mohawk, dakota, and AWS. It is unlikely that the code will need a lot of updates due to these changes.

This arose from an update to mohawk (below is from Tatiana in an email with the subject "mohawk reboot today?" on April 3, 2024:

The default Java version was changed on mohawk after the reboot from Java 8 to Java 11
vxwww@mohawk:/opt/vxwww/tomcat$ java -version
openjdk version "11.0.22" 2024-01-16
All our apps are still using Java 8
Could you please revert the Java version to 8.

From Tatiana, here are the compatible Tomcat versions with Java 11:

Tomcat 9.0.x and 10.1.x work with Java 11:
https://tomcat.apache.org/whichversion.html
ATEC project uses Tomcat 9.0.80.
I would start testing with the latest version of Tomcat - currently it is 9.0.89 - and require 9.0.x

.

Time Estimate

The developer should estimate this time.

Sub-Issues

Consider breaking the task down into sub-issues.

Beta5

Funding Source

Check in with Tara

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required
  • Select scientist(s) or no scientist required

Labels

  • Select component(s)
  • Select priority
  • Select requestor(s)

Projects and Milestone

  • Select Repository and/or Organization level Project(s) or add alert: NEED CYCLE ASSIGNMENT label
  • Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

Task Checklist

See the METplus Workflow for details.

  • Complete the issue definition above, including the Time Estimate and Funding Source.
  • Fork this repository or create a branch of develop.
    Branch name: feature_<Issue Number>_<Description>
  • Complete the development and test your changes.
  • Add/update log messages for easier debugging.
  • Add/update unit tests.
  • Add/update documentation.
  • Push local changes to GitHub.
  • Submit a pull request to merge into develop.
    Pull request: feature <Issue Number> <Description>
  • Define the pull request metadata, as permissions allow.
    Select: Reviewer(s) and Development issues
    Select: Repository level development cycle Project for the next official release
    Select: Milestone as the next official version
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
alert: NEED ACCOUNT KEY Need to assign an account key to this issue component: build process Build process issue priority: medium Medium Priority requestor: METplus Team METplus Development Team type: task An actionable item of work
Projects
Status: 🟢 Ready
Development

No branches or pull requests

2 participants