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

[Thomas Mäder (JIRA)]

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

Thomas Mäder commented on JBIDE-21857:
--------------------------------------

Did some experimenting:
# The jolokia agent in the eap image used in cdk uses ssh with credentials specific to OpenShift. I haven't been able to connect to that instance
# I have succeeded to start a second jolokia agent by adding a "-javaagent:jolokia.jar..." to the JAVA_OPTS_PREPEND. I was able to connect to the agent with a local browser after forwarding the proper port.
This would make it possible to start a jolokia connection when setting up the container for debug (we already add environment variables & forward ports when we start debugging). What's not yet clear is how or if we can access the jolokia connection when only having a debug target and an IServer in hand.

> 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
>            Priority: Blocker
>             Fix For: 4.4.0.Alpha1
>
>         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
(v6.4.11#64026)