karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Luo (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KARAF-2624) Karaf script for AIX should use JVM option: -Xdump:heap instead of IBM_JAVA_HEAPDUMP_TEXT to control production heapdumps
Date Wed, 11 Dec 2013 10:20:07 GMT

     [ https://issues.apache.org/jira/browse/KARAF-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Joe Luo updated KARAF-2624:
---------------------------

    Description: 
When we start Karaf with the karaf script on AIX we get the following error:

{quote}
user@host:/apps/user/pache-karaf-2.3.1/bin> ./karaf
MAXDATA=0xB0000000@DSA
karaf: JAVA_HOME not set; results may vary
IBM J9 VM (build 2.6, JRE 1.7.0 AIX ppc64-64 20120322_106209 (JIT enabled, AOT enabled)
** ASSERTION FAILED ** j9prt.748 at common/j9memtag.c:145 Trc_Assert_PRT_memory_corruption_detected((memoryCorruptionDetected))
Please wait while JBoss Fuse is loading...
{quote}

When we checked on the IBM site we found this article: 
http://www-01.ibm.com/support/docview.wss?uid=swg1IV29784

If we look in the startup script we find:
{code}
    # For AIX, set an environment variable
    if $aix; then
         export LDR_CNTRL=MAXDATA=0xB0000000@DSA
         export IBM_JAVA_HEAPDUMP_TEXT=true
         echo $LDR_CNTRL
    fi
{code}

And the IBM article states that you should avoid using IBM_JAVA_HEAPDUMP_TEXT variable to
not have that error message we've seen. The preferred mechanism for controlling the production
of
Heapdumps is the JVM option: -Xdump:heap.

  was:
When we start Karaf with the karaf script on AIX we get the following error:

{quote}
user@host:/apps/user/pache-karaf-2.3.1/bin> ./karaf
MAXDATA=0xB0000000@DSA
karaf: JAVA_HOME not set; results may vary
IBM J9 VM (build 2.6, JRE 1.7.0 AIX ppc64-64 20120322_106209 (JIT enabled, AOT enabled)
** ASSERTION FAILED ** j9prt.748 at common/j9memtag.c:145 Trc_Assert_PRT_memory_corruption_detected((memoryCorruptionDetected))
Please wait while JBoss Fuse is loading...
{quote}

When we checked on the IBM site we found this article: 
http://www-01.ibm.com/support/docview.wss?uid=swg1IV29784

If we look in the startup script we find:
    # For AIX, set an environment variable
    if $aix; then
         export LDR_CNTRL=MAXDATA=0xB0000000@DSA
         export IBM_JAVA_HEAPDUMP_TEXT=true
         echo $LDR_CNTRL
    fi

And the IBM article states that you should avoid using IBM_JAVA_HEAPDUMP_TEXT variable to
not have that error message we've seen. The preferred mechanism for controlling the production
of
Heapdumps is the JVM option: -Xdump:heap.


> Karaf script for AIX should use JVM option: -Xdump:heap instead of IBM_JAVA_HEAPDUMP_TEXT
to control production heapdumps
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KARAF-2624
>                 URL: https://issues.apache.org/jira/browse/KARAF-2624
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 2.3.1
>            Reporter: Joe Luo
>            Assignee: Jean-Baptiste Onofré
>
> When we start Karaf with the karaf script on AIX we get the following error:
> {quote}
> user@host:/apps/user/pache-karaf-2.3.1/bin> ./karaf
> MAXDATA=0xB0000000@DSA
> karaf: JAVA_HOME not set; results may vary
> IBM J9 VM (build 2.6, JRE 1.7.0 AIX ppc64-64 20120322_106209 (JIT enabled, AOT enabled)
> ** ASSERTION FAILED ** j9prt.748 at common/j9memtag.c:145 Trc_Assert_PRT_memory_corruption_detected((memoryCorruptionDetected))
> Please wait while JBoss Fuse is loading...
> {quote}
> When we checked on the IBM site we found this article: 
> http://www-01.ibm.com/support/docview.wss?uid=swg1IV29784
> If we look in the startup script we find:
> {code}
>     # For AIX, set an environment variable
>     if $aix; then
>          export LDR_CNTRL=MAXDATA=0xB0000000@DSA
>          export IBM_JAVA_HEAPDUMP_TEXT=true
>          echo $LDR_CNTRL
>     fi
> {code}
> And the IBM article states that you should avoid using IBM_JAVA_HEAPDUMP_TEXT variable
to not have that error message we've seen. The preferred mechanism for controlling the production
of
> Heapdumps is the JVM option: -Xdump:heap.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message