openjdk team mailing list archive
-
openjdk team
-
Mailing list archive
-
Message #10798
[Bug 1417962] Re: 6b34 regression: jps as root does not show classname anymore but instead 'process information unavailable' for processes running as non-root user
Antonio,Amir:
As another affected user i think downgrade would not be a good idea as it would reopen all the fixed security issues.
But as i wrote in my initial description there is a very easy workaround
which may even make sense to keep.
The problem with jps only happens if
a.) A java program is running as non-root user
b.) you run jps as root and want data about the running process from a.)
Not running jps as root but instead as the same user as the process is
running it is enough to not trigger the bug.
I did not check any of your charms but at least in our app it was very
easy to change our script to not trigger the issue.
Maybe you can incoporate the same change into your scripts/charms also
--
You received this bug notification because you are a member of OpenJDK,
which is subscribed to openjdk-7 in Ubuntu.
https://bugs.launchpad.net/bugs/1417962
Title:
6b34 regression: jps as root does not show classname anymore but
instead 'process information unavailable' for processes running as
non-root user
Status in openjdk-6 package in Ubuntu:
Confirmed
Status in openjdk-7 package in Ubuntu:
Confirmed
Bug description:
I noticed the following behavior change in the jps command line tool when updating from
6b33-1.13.5-1ubuntu0.12.04 -> 6b34-1.13.6-1ubuntu0.12.04.1 on a ubuntu 12.04 64bit system.
Staring point is a java process for apache tomcat running as non-root
user (username openbravo in below example) with pid 1462.
In 6b33 when running jps -l as root it did correctly identify the classname of the running processes as shown here:
luna686:~# jps -l
1462 org.apache.catalina.startup.Bootstrap
11610 sun.tools.jps.Jps
However after updating the same jps call as root-user does now show:
luna686:~# jps -l
12056 sun.tools.jps.Jps
1462 -- process information unavailable
Which break some custom monitoring of us trying to find tomcat process
via its classname.
Note: Problem only occours when running jps as root user and process
in question is running non-root. When running jps as same user as the
tomcat process is running with then both 6b33 + 6b34 work as expected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/1417962/+subscriptions
Follow ups
References