karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie goodyear (JIRA)" <j...@apache.org>
Subject [jira] Commented: (KARAF-189) Java endorsed dirs on AIX (IBM JVM)
Date Sat, 11 Sep 2010 20:57:32 GMT

    [ https://issues.apache.org/jira/browse/KARAF-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908366#action_12908366

Jamie goodyear commented on KARAF-189:

Trimming down the issue surface to just a simple HelloWorld class executed with "-Djava.endored.dirs=${KARAF_HOME}/lib/endorsed"
results in a JVM crash only with IBM Java 6. 

Reviewing the snap file the provided exception class appears to be dynamically loaded, so
is the SecurityManagerEx class... more investigation is required.

> Java endorsed dirs on AIX (IBM JVM)
> -----------------------------------
>                 Key: KARAF-189
>                 URL: https://issues.apache.org/jira/browse/KARAF-189
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>         Environment: AIX 5.3, IBM jre 1.6 sr8, power-pc
> Ubuntu linux 10.04, IBM jre sr8, x86
>            Reporter: haedri
>            Assignee: Jamie goodyear
>            Priority: Minor
>             Fix For: 2.1.0
> I have troubles launching karaf 2.0 on AIX, using an IBM jre (1.6 sr8), here are the
relevant lines of the output :
> IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 AIX ppc-32
> jvmap3260sr8-20100401_55940 (JIT enabled, AOT enabled)
> Unhandled exception
> Type=Segmentation error vmState=0x00000000
> (...)
> After trying everything possible (setting LDR_CTRL, LIBPATH, ulimit,...) it appears the
problem is linked to the "-Djava.endorsed.dirs" parameter from the java startup command line,
if I remove the "${KARAF_HOME}/lib/endorsed" entry, then karaf starts successfully.
> I've been able to reproduce the problem on a linux ubuntu on a x86 processor, using the
same IBM jvm version (http://www.ibm.com/developerworks/java/jdk/linux/download.html)
> I think problem comes from IBM jre (because it works on a jre 1.6 sr0), but I din't investigate
enough to be sure

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message