[
https://issues.jboss.org/browse/WFWIP-221?page=com.atlassian.jira.plugin....
]
Jean Francois Denise edited comment on WFWIP-221 at 10/1/19 12:52 PM:
----------------------------------------------------------------------
[~jbliznak] It doesn't occur when running an image built with s2i, you observe the
issue with a run of the builder image. Right?
was (Author: jdenise):
[~jbliznak] It doesn't occur when running an image built with s2i, you observe the
issue with a run of the builder image.
jps can't see server process in Openshift
-----------------------------------------
Key: WFWIP-221
URL:
https://issues.jboss.org/browse/WFWIP-221
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Reporter: Jan Blizňák
Assignee: Jean Francois Denise
Priority: Critical
This is somewhat curious issue.
When pod of app image is deployed (server is started) and switch to terminal in Openshift
GUI, doing `jps -l` does nothing although I can see in logs that server is up and I can
find java process in /proc/*/cmdline (image has no `ps` utility).
This happens only in Openshift environment and it is a regression to what was working
with latest published CD image.
Funnily, when I try to run the image in docker and start the server by
/opt/eap/bin/openshift-launch.sh, then jps can see the java process.
{code:java}
# this works fine
docker run -it
docker-registry.upshift.redhat.com/kwills/eap-cd-openshift-rhel8:18.0-EAP... sh
sh-4.4$ /opt/eap/bin/openshift-launch.sh &
sh-4.4$ jps -l
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)