[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
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)
9 years, 4 months
[JBoss JIRA] (JBIDE-22376) Enable JMX when entering Debug mode
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-22376 at 11/24/16 9:11 AM:
-----------------------------------------------------------------
What has been done there precisely? So i can verify its working as expected. I compared DC of a new application and a deployment config of application in debugging. There is a new port for debug 8787, but what with latest changes to EAP images the jolokia port is 8787 so basically we have 2 same ports with a different name, I don't think it is necessary. Then there are added environment variables:
{code}
{
"name" : "DEBUG_PORT",
"value" : "8787"
},
{
"name" : "DEV_MODE",
"value" : "true"
},
{
"name" : "DEBUG",
"value" : "true"
}
{code}
was (Author: mlabuda):
What has been done there precisely? So i can verify its working as expected. I compared DC of a new application and a deployment config of application in debugging. There is a new port for debug 8787, but what with latest changes to EAP images the jolokia port is 8787 so basically we have 2 same ports with a different name, I don't think it is necessary. Then there are added environment variables:
{code}
{
"name" : "DEBUG_PORT",
"value" : "8787"
},
{
"name" : "DEV_MODE",
"value" : "true"
},
{
"name" : "DEBUG",
"value" : "true"
}
{code}
DEV_MOVE env var was added by mistake probably bcs. of nodejs debugging. It is not required for EAP debugging AFAIK. With DEBUG and DEBUG_PORT env vars. I am not sure, should those be there?
> Enable JMX when entering Debug mode
> -----------------------------------
>
> Key: JBIDE-22376
> URL: https://issues.jboss.org/browse/JBIDE-22376
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jmx, openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Thomas Mäder
> Assignee: Rob Stryker
> Fix For: 4.4.2.Final, 4.4.3.AM1, 4.5.0.AM1
>
>
> We need to update the deployment configuration when entering debug mode. It is not entirely clear how to determine that an Openshift Pod has indeed a wildfly/EAP in it and can be reached with remoting-jmx
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4162) unresolved bundles - slf4j
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4162?page=com.atlassian.jira.plugin.... ]
Lukáš Valach closed JBDS-4162.
------------------------------
Verified, org.slf4j.api 1.7.2 is included.
> unresolved bundles - slf4j
> ---------------------------
>
> Key: JBDS-4162
> URL: https://issues.jboss.org/browse/JBDS-4162
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rhscl, rpm, target-platform
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Fix For: 10.2.0.GA
>
> Attachments: who-uses_ch.qos.logback.slf4j_1.0.7.png, who-uses_slf4j.impl.log4j12_1.7.2.png
>
>
> Vaclav said:
> {quote}
> Just an update on unresolved bundles. I looked at rh-eclipse46-devstudio-10.2-0.20161103.0650.el7.x86_64.rpm and the only ones are:
> ch.qos.logback.slf4j
> org.slf4j.impl.log4j12{quote}
> Both of those bundles declare
> {code}Fragment-Host: org.slf4j.api;bundle-version="[1.7.2,1.7.3)"{code}
> And since we're now using slf4j.api_1.7.4.jar, which has in its MANIFEST.MF:
> {code}
> Export-Package: org.slf4j;version=1.7.4, org.slf4j.spi;version=1.7.4,
> org.slf4j.helpers;version=1.7.4
> Import-Package: org.slf4j.impl;version=1.6.0;resolution:=optional
> Bundle-SymbolicName: slf4j.api
> {code}
> I suspect we need to find newer versions of those that can use slf4j 1.7.4 instead of 1.7.2.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-20906) [portlet] Update parent pom reference to latest TP based on Neon
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20906?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-20906:
-------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.0.Alpha1)
> [portlet] Update parent pom reference to latest TP based on Neon
> ----------------------------------------------------------------
>
> Key: JBIDE-20906
> URL: https://issues.jboss.org/browse/JBIDE-20906
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: portal-gatein
> Affects Versions: 4.4.0.Alpha1
> Reporter: Denis Golovin
> Fix For: 4.4.3.AM1
>
>
> As Max pointed out, there are no changes in code base and in JBoss Tools p2 repository assembly we use latest released portlet version, but we should build it against latest Eclipse Neon in TP to catch at least compilation problems (if any) related to new Eclipse release stream.
> It is required, because portlet is available though JBoss Central in nightly builds from master and we have to be sure it is usable.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months