On 14 February 2011 12:17, Mathieu Baudier mbaudier@argeo.org wrote:
When I package a "Runnable JAR" using the Eclipse Export wizard, in the manifest file, the main-class is given as org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader, which I presume is a little bit of code to redirect the main method to the main method of my actual application. This is the "extra layer" I was referring to.
Ok, if I well understand, Eclipse packages a big jar containing all your code and jar dependencies, and then uses its own classloader to access them.
As you suggested this is an interesting trail to follow. I already had issues with "exotic" classloaders using OpenJdk on CentOS.
Try indeed to do a "pure" java deployment (java -cp myjar1,myjar2,... com.example.MyAppWithMainMethod) and see if the issue still happens.
What was the result of your tests with Sun JRE (cf. your post from Feb 11th)? Do you have the issue with Sun JRE as well? _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Hi All,
I've been running our apps as purely as I can (java -cp /path/to/libs/* path.to.the.App) and they're still being send SIGHUP signals for reasons I can't understand.
I've added timestamps to my strace output and it seems to come out of the blue:
19:49:07.438591 futex(0x40d889d0, FUTEX_WAIT, 29119, NULL) = -1 EINTR (Interrupted system call) 01:45:14.275055 --- SIGHUP (Hangup) @ 0 (0) --- 01:45:14.275106 futex(0x2b3f32c7a000, FUTEX_WAKE_PRIVATE, 1) = 1 01:45:14.275417 rt_sigreturn(0x2b3f32c7a000) = -1 EINTR (Interrupted system call) 01:45:14.275461 futex(0x40d889d0, FUTEX_WAIT, 29119, NULL <unfinished ... exit status 129>
Does anyone know why this signal would be sent?
Martin