[jbosstools-issues] [JBoss JIRA] (JBIDE-24285) Java coredump when starting jboss server from Eclipse

Jeff MAURY (JIRA) issues at jboss.org
Wed Apr 18 12:13:11 EDT 2018


     [ https://issues.jboss.org/browse/JBIDE-24285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff MAURY updated JBIDE-24285:
-------------------------------
    Fix Version/s: 4.6.x
                       (was: 4.5.x)


> Java coredump when starting jboss server from Eclipse
> -----------------------------------------------------
>
>                 Key: JBIDE-24285
>                 URL: https://issues.jboss.org/browse/JBIDE-24285
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server, upstream
>         Environment: Windows 7
> System memory 24GB - memory checked and no issues found.
> JDK 1.8.0_121 x64
> JBoss EAP 6.4
> Eclipse Neon.3 with JBoss server support installed (Not full JBoss Developer Studio)
>            Reporter: Beirti O'Nunain
>            Assignee: Rob Stryker
>             Fix For: 4.6.x
>
>         Attachments: hs_err_pid53068.log, hs_err_pid58832.log
>
>
> Intermittently, when starting a JBoss server from the "servers" view in Debug mode, the process coredumps shortly after starting the application. (3rd party application provided by Calypso) I've not seen this with non-jboss processes yet.
> Problematic frame always points to jvm.dll (same frame 0x68637). Logs attached.
> I've started the JBoss process with -Xcheck:jni  but unfortunately the console is full of noise from 
>     WARNING: JNI local refs: zu, exceeds capacity: zu
> which causes the process to timeout on startup due to massively slowing down the startup. You can add this flag locally to see full logs
> Have also tried bumping Xmx/Xms from 1g to 4g but still getting the same issue. This issue does not occur if I start the server in 'run' mode instead of 'debug'.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jbosstools-issues mailing list