Java, Java, Java, Java, Java, Java .....

Java, Java, Java, Java, Java, Java .....

Post by Hans H. Hagber » Fri, 22 Sep 2000 04:00:00

In the systems being developed here, everything is coded in Java. There
are about 100 Java applications each running its own virtual machine.

I'm supposed to work with test and performance analysis of these systems
and I'm using tools that log system behaviour on process level.

The problem is that all I see is 100 processes named Java with some
small variations in command line parameters.

Is there a safe way to alter the process names either at startup or at
runtime ?
What could be the consequences of doing such a thing ?

//Hans Hagberg


1. java/50729: java/jdk14: broken calls

Synopsis: java/jdk14: broken calls (SIOCGIFCONF)

Responsible-Changed-From-To: freebsd-java->phantom
Responsible-Changed-By: phantom
Responsible-Changed-When: Sat Jun 14 03:41:59 PDT 2003
My area.  My victim

2. Teesside Linuxers Take Note!

3. Help. XFree86 and Mach64

4. java/47447: linux-sun-jdk1.4.1: java command can't find java.lang.Object


6. Java with HotSpot on FreeBSD (Was: Re: A Call to Action for freebsd-java)

7. Sound card for music editing etc

8. java/jdk14 broken (SIOCGIFCONF)

9. Java applet and Java plug-in

10. SSRT3582 Potential Sec. Vulnerability in Java VM (J2SE) and the Java Plugin

11. java/44380: patch for java-commapi-freebsd

12. Java Workshop and Java Studio