[JBoss JIRA] (JBIDE-24240) Include newer version of wtp in JBT/devstudio Neon.3 target platform (4.63.x)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24240?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24240:
-------------------------------
Attachment: patched-in-devstudio.png
install-jbt-abridged-including-patch-feature.png
> Include newer version of wtp in JBT/devstudio Neon.3 target platform (4.63.x)
> -----------------------------------------------------------------------------
>
> Key: JBIDE-24240
> URL: https://issues.jboss.org/browse/JBIDE-24240
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.4.4.AM2
> Reporter: Aurélien Pupier
> Assignee: Nick Boldt
> Fix For: 4.4.4.AM3
>
> Attachments: install-jbt-abridged-including-patch-feature.png, patched-in-devstudio.png, wtp383-cannot-be-installed-in-EclipseNeon3JavaEE_EPP.png, wtp383plugin-only-cannot-be-installed-in-EclipseNeon3JavaEE_EPP.png
>
>
> the neon.3 contains a regression which is impacting a lot of m2e users and prevents Fuse Tooling to migrate to Neon.3 safely
> I provided a patch to fix it and hope to have a new version of the plugin available soon, see
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=511793#c9
> We will need to include this new version in the TP for JBoss Tools 4.4.4
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24285) Java coredump when starting jboss server from Eclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24285?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24285:
-------------------------------
Component/s: server
> 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
> 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
> Fix For: 4.5.0.AM1
>
> 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.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24285) Java coredump when starting jboss server from Eclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24285?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24285:
-------------------------------
Fix Version/s: 4.5.0.AM1
(was: LATER)
> 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
> 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
> Fix For: 4.5.0.AM1
>
> 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.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24285) Java coredump when starting jboss server from Eclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24285?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-24285:
----------------------------------
Assignee: Rob Stryker
> 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
> 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.5.0.AM1
>
> 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.2.3#72005)
8 years, 11 months