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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-21857:
---------------------------------------------

Okey, I now grok this issue better and I think it is either expected behavior or due to us handling the restart our self now.

The issue boils down to (variation of [~fbricon] comment):

 1) jvm started and debugger connected (all is good)
 2)  user make a method body change - debugger tells jvm - all is good. no restarts needed.
 3) user make a structural change - debugger tells jvm - jvm does not support it. user is warned. (debugger and jvm is out of sync)
 4) restart just the deployment - change is now visible (debugger and jvm is still out of sync)
 5) do  a method body chance - debugger tells jvm - debugger still out of sync, user asked to restart.

#5 *could* just be our custom code for handling the restart on failed change that is not handling this case properly.

In the past (1+ year ago) we didn't do that.
 
Before we raise this to be a JDK limitation is there a way we can disable that custom logic and see if eclipse plain hotswap failure logic works ? [~rob.stryker] ? 


 

> 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: Max Rydahl Andersen
>            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)