Java libraries wrong ... 3.3
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
Describe the bug
A clear and concise description of what the bug is.
The start up shell scripts have code like
/u/tmp/zowec33/../zowep33/components/zaas/bin/start.sh
LIBPATH="$LIBPATH":"/usr/lib"
LIBPATH="$LIBPATH":"${JAVA_HOME}"/bin
LIBPATH="$LIBPATH":"${JAVA_HOME}"/bin/classic
LIBPATH="$LIBPATH":"${JAVA_HOME}"/bin/j9vm
LIBPATH="$LIBPATH":"${JAVA_HOME}"/lib/s390/classic
LIBPATH="$LIBPATH":"${JAVA_HOME}"/lib/s390/default
LIBPATH="$LIBPATH":"${JAVA_HOME}"/lib/s390/j9vm
LIBPATH="$LIBPATH":"${LIBRARY_PATH}"
The s390 libraries do not exist in Semeru 11 and above.
classic is not found
eg
find /usr/lpp/java/J21.0_64/lib/ -name j9vm
/usr/lpp/java/J21.0_64/lib/j9vm
See
https://www.ibm.com/docs/en/js-and-srozu?topic=SSJ2RXU/comparison_table.htm
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the startup shell scripts corresponding to the example path, such as components/zaas/bin/start.sh, and inspect how LIBPATH is assembled for Java on s390. Compare the referenced paths with Semeru 11 and later layouts, including the j9vm location shown in the issue. Done means startup scripts no longer reference libraries absent from supported Java versions and start successfully on s390.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, shell
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100