I'm using Ubuntu 12.10 (with Oracle JDK 1.7.0_09 being used - though I have seen the SIGSEGV issue on 1.6.x as well, and others have seen the issue on Fedora too).
As for Karaf/OSGi/Felix - we're using a Maven dependency to include those in our project. Tim On Wed, Dec 19, 2012 at 3:44 PM, jgoodyear [via Karaf] < [email protected]> wrote: > Hi, > > Can you provide which specific Linux distro you are using? > > Karaf 2.2.9 comes with Felix 3.2.2 > ( > http://karaf.apache.org/index/documentation/karaf-dependencies/karaf-deps-2.2.x.html), > > are you using a custom distribution? > > Cheers, > Jamie > > On Wed, Dec 19, 2012 at 7:45 PM, thully <[hidden > email]<http://user/SendEmail.jtp?type=node&node=4027103&i=0>> > wrote: > > > Hi, > > > > Our project (Cytoscape) utilizes Karaf/Felix/OSGi to for its application > > bundles (the application as a whole is built as a set of OSGi bundles). > > Anyway, we've noticed a strange problem when running on Linux systems > (using > > multiple different JVMs - including the latest Oracle 1.6 and 1.7.x > > releases). Frequently, after we install a new bundle (using the > > functionality that does so within our application or by just copying it > to > > the apprpriate place), we're finding that we get a JVM SIGSEGV crash in > the > > middle of bundle loading the next time we try to start up Cytoscape (and > > hence Karaf). It looks something like the following: > > > > # A fatal error has been detected by the Java Runtime Environment: > > # > > # SIGSEGV (0xb) at pc=0x00007f5ebd3fc54e, pid=23273, > tid=140044176189184 > > # > > # JRE version: 7.0_09-b05 > > # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.5-b02 mixed mode > > linux-amd64 compressed oops) > > # Problematic frame: > > # C [libc.so.6+0x8054e][thread 140044020991744 also had an error] > > > > Anyway, to get this error to go away, we frequently have to restart > Karaf > > multiple times and/or clear the cache - at which point everything > (including > > the new bundle) starts up fine. Does anyone have an idea as to what may > be > > the issue? This only happens on Linux systems - Windows and Mac don't > > experience the same issue. Our project is using Karaf 2.2.9, Felix > 3.0.1, > > and OSGi 4.2.0. > > > > Also, if upgrading our project to the latest versions of > Karaf/Felix/OSGi > > may help, I'd like to give it a try - though my attempt to do so by > changing > > the version numbers for those projects in our Maven pom.xml file and > > rebuliding resulted in a slew of BundleExceptions complaining about > "missing > > requirements". Any idea as to what I need to upgrade our project? > > > > Let me know if you have any suggestions regarding this issue... > > > > Tim > > > > > > > > -- > > View this message in context: > http://karaf.922171.n3.nabble.com/SIGSEGV-crash-issues-with-Karaf-OSGi-on-Linux-tp4027102.html > > Sent from the Karaf - User mailing list archive at Nabble.com. > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://karaf.922171.n3.nabble.com/SIGSEGV-crash-issues-with-Karaf-OSGi-on-Linux-tp4027102p4027103.html > To unsubscribe from SIGSEGV crash issues with Karaf/OSGi on Linux, click > here<http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4027102&code=dG1odWxsQGVuZy51Y3NkLmVkdXw0MDI3MTAyfC0xMzI0MDI2MjYx> > . > NAML<http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://karaf.922171.n3.nabble.com/SIGSEGV-crash-issues-with-Karaf-OSGi-on-Linux-tp4027102p4027104.html Sent from the Karaf - User mailing list archive at Nabble.com.
