As a work around, you could try using the felix.fileinstall.filter property in the etc/org.apache.felix.fileinstall-deploy.cfg to something like .*\\.jar or any other regexp that would avoid the .svn folder ...
On Mon, Nov 16, 2009 at 15:53, peter lawrey <[email protected]> wrote: > The 'etc' and 'deploy' directories are under subversion control. Karaf sees > the '.svn' in 'deploy' as a bundle and creates a generated module called > '.svn.jar'. When I do an update to 'deploy' the files under 'deploy/.svn' > are changed and the generated bundle gets changed. At this about this time > fileinstall attempts to open the file '.svn.jar' with new JarFile(file) and > sometimes this cause a SIGBUS error in the JVM. > The '.svn.jar' is the only jar file, fileinstall attempt to open and it is on > this line the JVM dies. > > I have logged the follow errors to Sun. But I am trying to put in a work > around as I don't know how long that might take. ;) > > The same bug appears on Solaris x86 and SUSE 10. > > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGBUS (0xa) at pc=0xfe291ce0, pid=23367, tid=67 > # > # JRE version: 6.0_16-b01 > # Java VM: Java HotSpot(TM) Server VM (14.2-b01 mixed mode solaris-x86 ) > # Problematic frame: > # C [libzip.so+0x1ce0] > # > > Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native > code) > C [libzip.so+0x1ce0] > C [libzip.so+0xb1a2] > C [libzip.so+0x25a8] Java_java_util_zip_ZipFile_open+0xb8 > j java.util.zip.ZipFile.open(Ljava/lang/String;IJ)J+0 > j java.util.zip.ZipFile.<init>(Ljava/io/File;I)V+98 > j java.util.jar.JarFile.<init>(Ljava/io/File;ZI)V+3 > j java.util.jar.JarFile.<init>(Ljava/io/File;)V+4 > j > org.apache.felix.fileinstall.internal.BundleTransformer.canHandle(Ljava/io/File;)Z+74 > > > -----Original Message----- > From: Guillaume Nodet [mailto:[email protected]] > Sent: 16 November 2009 13:56 > To: [email protected] > Subject: Re: If you see locking and nothing else... > > On Mon, Nov 16, 2009 at 12:34, peter lawrey <[email protected]> wrote: >> I tried patching the file installer today. It appears that if the file >> installer attempt to open a Jar file while it is being written to it >> kills the JVM (On Solaris x86 and SUSE 10) even with the latest JDK. > > This should not happen, as fileinstall makes sure the content does not > change before actually loading the jar (or it tries to). > Can be a bit more explicit about what you're doing exactly ? > >> >> So I tried patching the file-install so it doesn't open a file, with a >> very recent modification date, and installed file-install to maven. >> However after updating the startup.properties I get the following in the >> logs and nothing else, even with DEBUG enabled. >> >> >> >> 16-Nov-2009 11:14:54 org.apache.felix.karaf.main.SimpleFileLock lock >> >> INFO: locking >> >> >> >> The lock is successfully acquired. Debugging the process, the Main is >> sleeping, waiting for something. >> >> >> >> After trying a number of things, it turned out it couldn't find the >> patched file-install. Reverting startup.properties got the system >> working again. >> >> Next I will try updating the system directory instead. >> >> >> >> Peter. >> >> >> >> >> >> > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
