public static int pid() {
String id = ManagementFactory.getRuntimeMXBean().getName();
String[] ids = id.split(”@”);
return Integer.parseInt(ids[0]);
}

public static void listOpenFiles() throws IOException {
int pid = pid();
Runtime runtime = Runtime.getRuntime();
Process process = runtime.exec(”lsof -p ” + pid);
InputStream is = process.getInputStream();
InputStreamReader isr = new InputStreamReader(is);
BufferedReader br = new BufferedReader(isr);
String line;

while ((line = br.readLine()) != null) {
log.info(line);
}
}

I have this problem, and I tryed to solve it by removing the classpath from the MANIFEST in the external jars (third party jars), but when I packed again the jar file, it does not work. Any sugest? Thanks a lot

But, I still did not understand a thing: when I startup the Jboss Aplication Service this kind of problemns don’t arrive, but when I startup Geronimo Aplication Services the problems arrive.

I am wandering if all of folks that use Geronimo runs in this problem and if all of them visit the manifest of all jar to solve the problem?

Best regards!

But, how can I find which jar has the wrong classpath in the manifest? I use several 3rd party jar. Some of them are: spring, struts2, velocity, activation.jar, quartz, hibernate, and some common libraries from Apache. On your case, which jar caused the problem?

Hemant