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

[Marián Labuda (JIRA)]

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

Marián Labuda commented on JBIDE-21857:
---------------------------------------

How does it work or what are the steps to reproduce? I tried eap64-basis-s2i template with changed CONTEXT_DIR to helloworld. I have a server adapter in debugging mode. I have even activated JMX on the server adapter (JMX tree item is placed under an OS 3 server adapter but it is disconnected by default on server adapter in debug mode, required double click or selection of context menu item Connect... 

First scenario I was trying for hot code replacement by changing method signature in HelloService class. It failed and resulted into out of sync. 
Second scenario I was trying was adding another method to the HelloService class. It failed and resulted into out of sync.

> 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: Rob Stryker
>             Fix For: 4.4.2.Final, 4.4.3.AM1, 4.5.0.AM1
>
>         Attachments: HCRFailure.zip
>
>
> 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
(v7.2.3#72005)