[JBoss JIRA] (JBDS-4728) Jboss Developer Studio Hangs on Step 8 of 10
by Susmit Dey (JIRA)
Susmit Dey created JBDS-4728:
--------------------------------
Summary: Jboss Developer Studio Hangs on Step 8 of 10
Key: JBDS-4728
URL: https://issues.jboss.org/browse/JBDS-4728
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Feature Request
Affects Versions: 12.0.0.GA
Environment: Windows 7 (Enterprise) 64bit
Reporter: Susmit Dey
Attachments: JBDS_Hung.jpg
devstudio-12.0.0.GA-installer-standalone installer hangs on step 8 of 10
installation progress stuck at 1/3
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (JBIDE-26311) EAP 7.1 fails to stop when connected over ssh
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26311?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-26311:
-------------------------------------
So I found I was doing some things differently.
1) I was not downloading the runtime, but using a local one.
2) I was not using my IP address, but rather the ssh host named "localhost"
I did not expect 1) would change anything. I thought maybe fixing 2) would cause me to replicate it.
Unfortunately I still cannot replicate. Would you be able to trace through this? You'll want to set a breakpoint in RSEJBossCommandLineShutdownController.stopImpl(etc). You'll also want to trace into the superclass calls, especially the eventual call to gracefulStop().
The gracefulStop() method should be trying to execute a command like as follows:
/home/rob/apps/jboss/unzipped/jboss-eap-7.1.0.zip.expanded/bin/jboss-cli.sh --connect command=:shutdown
As for the exceptions in your log, I've discovered their cause. While your server is configured to use command-line / filesystem operations only, and not management, we never converted our deployment scanner utility to have a command-line implementation. The server adapter is still trying to customize the deployment scanners via management, but mgmt is not exposed.
> EAP 7.1 fails to stop when connected over ssh
> ---------------------------------------------
>
> Key: JBIDE-26311
> URL: https://issues.jboss.org/browse/JBIDE-26311
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.9.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: regression
> Attachments: JBIDE-26311.local.ogv
>
>
> I have an EAP 7.1 setup up over ssh. It's running on my localhost, so it's the most basic test of an ssh server. When I click the stop button on the server, it says:
> Server Red Hat JBoss EAP 7.1 ssh failed to stop.
> An exception stack trace is not available.
> It will stop on second attempt. On a local server this would mean killing the server java process. I'm not sure exactly what happens on a remote server, but it works.
> I'm pretty sure this worked last time (previous milestone).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (JBIDE-26148) CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected a broken link)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26148?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-26148 at 9/6/18 4:56 AM:
------------------------------------------------------------------
[~rob.stryker] If some kind of a trigger in preferences (like a button, a link, etc.) where the user can force a renewed search is what you're suggesting, then I'm all +1.
Thinking this issue through again made me believe that the edge case that we can fix here makes this a non-critical, non-urgent issue.
was (Author: adietish):
[~rob.stryker] If some kind of a trigger in preferences (like a button, a link, etc.) where the user can force a renewed search is what you're suggesting, then I'm all +1.
Thinking this issue through again made me think that the edge case that we can fix makes this a non-critical, non-urgent issue.
> CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected a broken link)
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26148
> URL: https://issues.jboss.org/browse/JBIDE-26148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.9.x
>
>
> [CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command (on the $PATH, etc.). But it'll only do so once:
> {code:title=CommandLocationBinary}
> public String findLocation(int timeout) {
> if (foundLoc != null || searchFailed)
> return foundLoc;
> String searched = CommandLocationLookupStrategy.get().search(this, timeout);
> if (searched == null) {
> searchFailed = true;
> }
> foundLoc = searched;
> return searched;
> }
> {code}
> Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
> What if I update my ex. correct a broken link to oc while I keep Eclipse running?
> I'd think that one should be able to repeat the lookup if it fails since the user could modify it's system while he keeps Eclipse running. Afaics the current impl forces me to restart Eclipse.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (JBIDE-26148) CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected a broken link)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26148?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26148:
------------------------------------------
[~rob.stryker] If some kind of a trigger in preferences (like a button, a link, etc.) where the user can force a renewed search is what you're suggesting, then I'm all +1.
Thinking this issue through again made me think that the edge case that we can fix makes this a non-critical, non-urgent issue.
> CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected a broken link)
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26148
> URL: https://issues.jboss.org/browse/JBIDE-26148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.9.x
>
>
> [CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command (on the $PATH, etc.). But it'll only do so once:
> {code:title=CommandLocationBinary}
> public String findLocation(int timeout) {
> if (foundLoc != null || searchFailed)
> return foundLoc;
> String searched = CommandLocationLookupStrategy.get().search(this, timeout);
> if (searched == null) {
> searchFailed = true;
> }
> foundLoc = searched;
> return searched;
> }
> {code}
> Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
> What if I update my ex. correct a broken link to oc while I keep Eclipse running?
> I'd think that one should be able to repeat the lookup if it fails since the user could modify it's system while he keeps Eclipse running. Afaics the current impl forces me to restart Eclipse.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (JBIDE-26148) CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected a broken link)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26148?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26148:
-------------------------------------
Fix Version/s: 4.9.x
> CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected a broken link)
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26148
> URL: https://issues.jboss.org/browse/JBIDE-26148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.9.x
>
>
> [CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command (on the $PATH, etc.). But it'll only do so once:
> {code:title=CommandLocationBinary}
> public String findLocation(int timeout) {
> if (foundLoc != null || searchFailed)
> return foundLoc;
> String searched = CommandLocationLookupStrategy.get().search(this, timeout);
> if (searched == null) {
> searchFailed = true;
> }
> foundLoc = searched;
> return searched;
> }
> {code}
> Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
> What if I update my ex. correct a broken link to oc while I keep Eclipse running?
> I'd think that one should be able to repeat the lookup if it fails since the user could modify it's system while he keeps Eclipse running. Afaics the current impl forces me to restart Eclipse.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (JBIDE-26336) Upgrade jacoco version to 0.8.2+ to be compatible with Java 11
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26336?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26336:
-------------------------------
Component/s: build
> Upgrade jacoco version to 0.8.2+ to be compatible with Java 11
> --------------------------------------------------------------
>
> Key: JBIDE-26336
> URL: https://issues.jboss.org/browse/JBIDE-26336
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.9.0.AM3
> Reporter: Aurélien Pupier
> Fix For: 4.9.0.Final
>
>
> https://github.com/jacoco/jacoco/releases/tag/v0.8.2
> {quote}Experimental support for Java 11 and Java 12 class files, including JEP 12 "preview features" (GitHub #719, #738, #743).{quote}
> for now for SAp Tooling, I got
> {noformat}
> 09:37:54 Exception in thread "main" java.lang.reflect.InvocationTargetException
> 09:37:54 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 09:37:54 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 09:37:54 at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 09:37:54 at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> 09:37:54 at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513)
> 09:37:54 at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525)
> 09:37:54 Caused by: java.lang.RuntimeException: Class java/lang/UnknownError could not be instrumented.
> 09:37:54 at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:140)
> 09:37:54 at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:101)
> 09:37:54 at org.jacoco.agent.rt.internal_c13123e.PreMain.createRuntime(PreMain.java:55)
> 09:37:54 at org.jacoco.agent.rt.internal_c13123e.PreMain.premain(PreMain.java:47)
> 09:37:54 ... 6 more
> 09:37:54 Caused by: java.lang.NoSuchFieldException: $jacocoAccess
> 09:37:54 at java.base/java.lang.Class.getField(Class.java:2000)
> 09:37:54 at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:138)
> 09:37:54 ... 9 more
> 09:37:54 FATAL ERROR in native method: processing of -javaagent failed
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (JBIDE-26336) Upgrade jacoco version to 0.8.2+ to be compatible with Java 11
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26336?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26336:
-------------------------------
Affects Version/s: 4.9.0.AM3
> Upgrade jacoco version to 0.8.2+ to be compatible with Java 11
> --------------------------------------------------------------
>
> Key: JBIDE-26336
> URL: https://issues.jboss.org/browse/JBIDE-26336
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Affects Versions: 4.9.0.AM3
> Reporter: Aurélien Pupier
> Fix For: 4.9.0.Final
>
>
> https://github.com/jacoco/jacoco/releases/tag/v0.8.2
> {quote}Experimental support for Java 11 and Java 12 class files, including JEP 12 "preview features" (GitHub #719, #738, #743).{quote}
> for now for SAp Tooling, I got
> {noformat}
> 09:37:54 Exception in thread "main" java.lang.reflect.InvocationTargetException
> 09:37:54 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 09:37:54 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 09:37:54 at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 09:37:54 at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> 09:37:54 at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513)
> 09:37:54 at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525)
> 09:37:54 Caused by: java.lang.RuntimeException: Class java/lang/UnknownError could not be instrumented.
> 09:37:54 at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:140)
> 09:37:54 at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:101)
> 09:37:54 at org.jacoco.agent.rt.internal_c13123e.PreMain.createRuntime(PreMain.java:55)
> 09:37:54 at org.jacoco.agent.rt.internal_c13123e.PreMain.premain(PreMain.java:47)
> 09:37:54 ... 6 more
> 09:37:54 Caused by: java.lang.NoSuchFieldException: $jacocoAccess
> 09:37:54 at java.base/java.lang.Class.getField(Class.java:2000)
> 09:37:54 at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:138)
> 09:37:54 ... 9 more
> 09:37:54 FATAL ERROR in native method: processing of -javaagent failed
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (JBIDE-26336) Upgrade jacoco version to 0.8.2+ to be compatible with Java 11
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26336?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26336:
-------------------------------
Fix Version/s: 4.9.0.Final
> Upgrade jacoco version to 0.8.2+ to be compatible with Java 11
> --------------------------------------------------------------
>
> Key: JBIDE-26336
> URL: https://issues.jboss.org/browse/JBIDE-26336
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Affects Versions: 4.9.0.AM3
> Reporter: Aurélien Pupier
> Fix For: 4.9.0.Final
>
>
> https://github.com/jacoco/jacoco/releases/tag/v0.8.2
> {quote}Experimental support for Java 11 and Java 12 class files, including JEP 12 "preview features" (GitHub #719, #738, #743).{quote}
> for now for SAp Tooling, I got
> {noformat}
> 09:37:54 Exception in thread "main" java.lang.reflect.InvocationTargetException
> 09:37:54 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 09:37:54 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 09:37:54 at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 09:37:54 at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> 09:37:54 at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513)
> 09:37:54 at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525)
> 09:37:54 Caused by: java.lang.RuntimeException: Class java/lang/UnknownError could not be instrumented.
> 09:37:54 at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:140)
> 09:37:54 at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:101)
> 09:37:54 at org.jacoco.agent.rt.internal_c13123e.PreMain.createRuntime(PreMain.java:55)
> 09:37:54 at org.jacoco.agent.rt.internal_c13123e.PreMain.premain(PreMain.java:47)
> 09:37:54 ... 6 more
> 09:37:54 Caused by: java.lang.NoSuchFieldException: $jacocoAccess
> 09:37:54 at java.base/java.lang.Class.getField(Class.java:2000)
> 09:37:54 at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:138)
> 09:37:54 ... 9 more
> 09:37:54 FATAL ERROR in native method: processing of -javaagent failed
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months