karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-5632) dev:create-dump creates invalid dump file
Date Wed, 21 Feb 2018 12:08:00 GMT

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

ASF GitHub Bot commented on KARAF-5632:
---------------------------------------

rhierlmeier opened a new pull request #464: #KARAF-5632: Reuse in HeapDumpProvider now the
copy function of LogDu…
URL: https://github.com/apache/karaf/pull/464
 
 
   Fixed the copy of the dumpfile in the HeapDumpProvider 
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> dev:create-dump creates invalid dump file
> -----------------------------------------
>
>                 Key: KARAF-5632
>                 URL: https://issues.apache.org/jira/browse/KARAF-5632
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 3.0.8
>         Environment: karaf 3.0.8, windows 10
>            Reporter: Richard Hierlmeier
>            Priority: Major
>         Attachments: screenshot-1.png
>
>
> When creating with the {{dev:create-dump}} command an heap dump, this dump can not be
opened with eclipse memory analyser I  get the following error:
> {noformat}
> The HPROF parser encountered a violation of the HPROF specification that it could not
safely handle. This could be due to file truncation or a bug in the JVM. Please consider filing
a bug at eclipse.org. To continue parsing the dump anyway, you can use -DhprofStrictnessWarning=true
or set the strictness mode under Preferences > HPROF Parser > Parser Strictness. See
the inner exception for details.
> The HPROF parser encountered a violation of the HPROF specification that it could not
safely handle. This could be due to file truncation or a bug in the JVM. Please consider filing
a bug at eclipse.org. To continue parsing the dump anyway, you can use -DhprofStrictnessWarning=true
or set the strictness mode under Preferences > HPROF Parser > Parser Strictness. See
the inner exception for details.
> (Possibly) Invalid HPROF file: Expected to read another 83.886.080 bytes, but only 1.500
bytes are available.
> (Possibly) Invalid HPROF file: Expected to read another 83.886.080 bytes, but only 1.500
bytes are available.
> {noformat}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message