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

Andre Dietisheim (JIRA) issues at jboss.org
Thu Jan 12 13:01:00 EST 2017


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

Andre Dietisheim edited comment on JBIDE-21857 at 1/12/17 1:00 PM:
-------------------------------------------------------------------

[~tmader] as discussed above, the  "Hot Code Replace Failed" dialog always shows up, after there was a 1st "not code replaceable" change. Do you know how to prevent this (aka only show the "Hot Code Replace Failed" if there really is a change that's not "hot code replaceable" - not always as it is now)? 


was (Author: adietish):
[~tmader] as discussed above, the  "Hot Code Replace Failed" dialog always shows up, as soon as it once popped up. Do you know how to prevent this (aka only show the "Hot Code Replace Failed" if there really is a change that's not "hot code replaceable" - not always as it is now)? 

> 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: Andre Dietisheim
>             Fix For: 4.4.3.AM2
>
>         Attachments: HCRFailure.zip, code-out-of-sync.png, 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)


More information about the jbosstools-issues mailing list