[jbosstools-issues] [JBoss JIRA] (JBIDE-21857) Hot code replacement 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=13332021#comment-13332021 ] 

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

[~adietish] well, although server adapter in Servers view shows Synchronized, check Debug view and Remote debugger of the application. It says, on the debugged thread, "out of synch" (it makes me bit dizzy seeing "synch" instead of "sync", but that would be for another issue. It does not look nice). So server adapter can be synchronized, but debugger isn't. 

Also, my JMX is disconected, until I connect it manually.

And I wouldn't close this one, because those further HCR compatible changes you perform, show HCR Failed dialog, as you confirmed, but if you do not restart module (just push button Continue - it is not necessary to restart module with HCR compatible changes), your changes will not be applied (server will still use old code).

> Hot code replacement 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, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png
>
>
> 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)