[jbosstools-issues] [JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift

Thomas Mäder (JIRA) issues at jboss.org
Fri Mar 18 06:27:00 EDT 2016


    [ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178876#comment-13178876 ] 

Thomas Mäder edited comment on JBIDE-21857 at 3/18/16 6:26 AM:
---------------------------------------------------------------

I looked at the wildfly VM in a profiler and was able to see that there are at least two class loaders where MemberRegistration is loaded.
When looking at the JNI global references, there seems to be one instance retained per attempted class reload or restart modules (not sure which).
There really should not be a JNIGlobal referencing this class. I suspect that the failed HCR leaks this reference somehow. Difficult to tell whether this is a JDI/JDT problem or VM.


was (Author: tmader):
I looked at the wildfly VM in a profiler and was able to see that there are at least two class loaders where MemberRegistration is loaded.

> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
>                 Key: JBIDE-21857
>                 URL: https://issues.jboss.org/browse/JBIDE-21857
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.3.1.Beta2
>            Reporter: Fred Bricon
>            Assignee: Thomas Mäder
>            Priority: Blocker
>             Fix For: 4.3.1.CR1
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)



More information about the jbosstools-issues mailing list