[JBoss JIRA] (JBIDE-26445) Remote server cannot start on windows when connected via local remote system type
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26445?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-26445:
------------------------------------------
[~rob.stryker] I believe that this issue is critical given that latest EAPs are affected. Is there really nothing we can do about it?
> Remote server cannot start on windows when connected via local remote system type
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-26445
> URL: https://issues.jboss.org/browse/JBIDE-26445
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.9.0.Final, 4.11.0.AM1
> Environment: windows
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.12.x
>
>
> I got this in Console when trying to start remote EAP 7.x server adapter:
> {code}
> 'cmd' is not recognized as an internal or external command, operable program or batch file.
> {code}
> And server is still starting until timeout is reached.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-20014) Explorer: "New" context menu not showing up at times (Linux only, GTK2 and GTK3)
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-20014?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-20014:
------------------------------------------
This issue was resolved in platform a long time ago. Resolving.
> Explorer: "New" context menu not showing up at times (Linux only, GTK2 and GTK3)
> --------------------------------------------------------------------------------
>
> Key: JBIDE-20014
> URL: https://issues.jboss.org/browse/JBIDE-20014
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.3.0.Beta1
> Environment: Linux GTK2, GTK3
> Reporter: André Dietisheim
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 4.3.x, 4.12.0.Final
>
> Attachments: new-submenu-not-visible.png, new-submenu-visible.png
>
>
> It is quite frequent that the "New" (and "Show in" for v3) submenu wont show up. This happens even if the submenu is first visible but then, on a 2nd context menu invocation, disappears
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-20014) Explorer: "New" context menu not showing up at times (Linux only, GTK2 and GTK3)
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-20014?page=com.atlassian.jira.plugi... ]
André Dietisheim resolved JBIDE-20014.
--------------------------------------
Fix Version/s: 4.12.0.Final
Resolution: Done
> Explorer: "New" context menu not showing up at times (Linux only, GTK2 and GTK3)
> --------------------------------------------------------------------------------
>
> Key: JBIDE-20014
> URL: https://issues.jboss.org/browse/JBIDE-20014
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.3.0.Beta1
> Environment: Linux GTK2, GTK3
> Reporter: André Dietisheim
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 4.12.0.Final, 4.3.x
>
> Attachments: new-submenu-not-visible.png, new-submenu-visible.png
>
>
> It is quite frequent that the "New" (and "Show in" for v3) submenu wont show up. This happens even if the submenu is first visible but then, on a 2nd context menu invocation, disappears
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-11338) JBoss AS 7.0.2 do not start when Java Agent is run and throws log error with JVM 6 update 15 and above
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-11338?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-11338:
------------------------------------------
[~jeffmaury] jdk 6 is EOF and the bug is 3y+ old. Shouldnt we resolve this?
> JBoss AS 7.0.2 do not start when Java Agent is run and throws log error with JVM 6 update 15 and above
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11338
> URL: https://issues.jboss.org/browse/JBIDE-11338
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: profiler
> Affects Versions: LATER
> Reporter: Ramesh Pa
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: JBoss
> Fix For: LATER
>
>
> Workaround as below is also not working.
> set JAVA_OPTS= %JAVA_OPTS% -Xbootclasspath/p:C:\jboss-6.1.0.Final\lib\jboss-logmanager.jar -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger .pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl
> No issues with JVM 6 update 14 and earlier.
> Error message
> INFO: 801. Dummy Java Agent:: Transformer to Transform Class: java/lang/ExceptionInInitializerError
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at org.jboss.as.server.Main.main(Main.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.modules.Module.run(Module.java:272)
> at org.jboss.modules.Main.main(Main.java:313)
> Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system proper
> ty to "org.jboss.logmanager.LogManager")
> at org.jboss.logmanager.Logger.getLogger(Logger.java:60)
> at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42)
> ... 7 more
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-25696) Deadlock when running JBoss Tools Project Validator on startup
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-25696?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-25696:
------------------------------------------
[~jeffmaury] No updates for this for more than a year. I think that we should resolve this as CANNOT_REPRODUCE or INCOMPLETE.
> Deadlock when running JBoss Tools Project Validator on startup
> --------------------------------------------------------------
>
> Key: JBIDE-25696
> URL: https://issues.jboss.org/browse/JBIDE-25696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, common, jst
> Environment: JBoss Developer Studio 11.2.0.GA, Windows 10
> Reporter: Vsevolod Golovanov
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 4.12.x
>
> Attachments: lockedup.png, threaddump-1518088511239.tdump
>
>
> The workspace is one EAR project, a couple dozen EJBs, 2 WARs, a couple dozen JAR webfragments (deployed inside the WARs), some misc projects - 67 projects alltogether.
> When opening it sometimes locks up completely - UI is not responding, process CPU is at 0%.
> Here's what it looks like: !lockedup.png|thumbnail!
> This time I just opened the Problems view and clicked Markers, which never opened. But I don't think this isn't necessary, pretty sure it sometimes hangs without clicking anything at all.
> It always shows JBoss Tools Project Validator in the Progress view when this happens.
> VisualVM reports a deadlock, seems to be JBoss Tools Validator related: [^threaddump-1518088511239.tdump]
> I think this used to happen with JBDS10 too, but I don't know for sure, because I don't have the threaddumps.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months