[JBoss JIRA] (JBDS-3953) JBoss Studio Developer crash at startup on Fedora 24
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3953?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3953:
--------------------------------------
cc: [~akurtako]
> JBoss Studio Developer crash at startup on Fedora 24
> ----------------------------------------------------
>
> Key: JBDS-3953
> URL: https://issues.jboss.org/browse/JBDS-3953
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 9.1.0.GA
> Environment: Fedora 24
> openjdk full version "1.8.0_92-b14"
> Reporter: Donato Marrazzo
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 10.x
>
> Attachments: hs_err_pid12689.log, hs_err_pid3836.log.zip
>
>
> After installation, as I launch JBS, it just display the eclipse workbench for few second that it crash.
> Despite the console message, no core dump is generated.
> This is the cmd line output:
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in [bundleresource://1072.fwk923366543:1/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in [bundleresource://1072.fwk923366543:2/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
> SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
> 14:09:55.604 [Worker-2] DEBUG o.e.m.c.i.p.r.ProjectRegistryRefreshJob - Queued refresh request: [/RemoteSystemsTempFiles/pom.xml]
> openjdk version "1.8.0_92"
> OpenJDK Runtime Environment (build 1.8.0_92-b14)
> OpenJDK 64-Bit Server VM (build 25.92-b14, mixed mode)
> 14:09:57.115 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository
> 14:09:57.142 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository
> 14:09:57.143 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshing: [L/RemoteSystemsTempFiles/pom.xml]
> 14:09:57.156 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshed: [L/RemoteSystemsTempFiles/pom.xml]
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007f521a6d7bfe, pid=12689, tid=0x00007f52cf5a3700
> #
> # JRE version: OpenJDK Runtime Environment (8.0_92-b14) (build 1.8.0_92-b14)
> # Java VM: OpenJDK 64-Bit Server VM (25.92-b14 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [libjavascriptcoregtk-3.0.so.0+0x4d4bfe] JSC::VM::throwException(JSC::ExecState*, JSC::JSValue)+0x236e
> #
> # Core dump written. Default location: /home/donato/core or core.12689
> #
> # An error report file with more information is saved as:
> # /home/donato/hs_err_pid12689.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3847) Need new screenshot for DevStudio 10 update site page
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3847?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov edited comment on JBDS-3847 at 6/16/16 12:15 PM:
----------------------------------------------------------------
Attached a new screenshot - !devstudio.png|thumbnail!
was (Author: akazakov):
Attached a new screenshot - !devstudio.png!
> Need new screenshot for DevStudio 10 update site page
> -----------------------------------------------------
>
> Key: JBDS-3847
> URL: https://issues.jboss.org/browse/JBDS-3847
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: documentation, updatesite
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.0.0.GA
>
> Attachments: devstudio.png, devstudio10-screenshot-full.png, devstudio10-screenshot-thumb.png
>
>
> https://devstudio.redhat.com/10.0/staging/updates/ contains two screenshots, both showing "JBoss Central".
> Since we're now calling that Red Hat Central, we need new screenshots for that page.
> We could also backport this to the /9.0/ pages if anyone cares.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22473) Environment Var Wizard: Cannot remove env vars
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22473?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-22473:
-----------------------------------------------
[~adietish], all changes in the wizard are revertible, so all changes are displayed. User can select the deleted item and push 'Reset' thus restoring it back. If it were hidden, then how user can view all the changes and how else can he restore the item? There is option 'Reset All' but it will revert all changes. When var's value is edited, it does not matter if item was deleted or not because user said ok to have the item with the just entered value. When var's name is changed, it cannot be treated other than creating new var, if the 'renamed' var was persistent, it must be shown as deleted. That may look a bit strange equally with both deleted and active items. But the only way to get rid of the strangeness is to forbid editing var's name, because for persistent items it equals 'add new'+'delete old.
> Environment Var Wizard: Cannot remove env vars
> ----------------------------------------------
>
> Key: JBIDE-22473
> URL: https://issues.jboss.org/browse/JBIDE-22473
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Viacheslav Kabanovich
> Labels: env_var_wizard, openshift_v3
> Fix For: 4.4.1.Alpha1
>
> Attachments: deleted-env-var.png
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22603:
------------------------------------------
The fix in JBIDE-21828 could affect what you experience in this issue.
> Sometimes multiple OpenShift watch managers are periodically created and finished
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22603
> URL: https://issues.jboss.org/browse/JBIDE-22603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Priority: Critical
> Labels: explorer, openshift_v3
> Attachments: watchers.png
>
>
> Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template.
> !watchers.png!
> It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3953) JBoss Studio Developer crash at startup on Fedora 24
by Donato Marrazzo (JIRA)
[ https://issues.jboss.org/browse/JBDS-3953?page=com.atlassian.jira.plugin.... ]
Donato Marrazzo commented on JBDS-3953:
---------------------------------------
In the second test, I applied all suggestion even tuning GTK3.
Then, I was running GTK2.
Thank you for the prompt response.
> JBoss Studio Developer crash at startup on Fedora 24
> ----------------------------------------------------
>
> Key: JBDS-3953
> URL: https://issues.jboss.org/browse/JBDS-3953
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 9.1.0.GA
> Environment: Fedora 24
> openjdk full version "1.8.0_92-b14"
> Reporter: Donato Marrazzo
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 10.x
>
> Attachments: hs_err_pid12689.log, hs_err_pid3836.log.zip
>
>
> After installation, as I launch JBS, it just display the eclipse workbench for few second that it crash.
> Despite the console message, no core dump is generated.
> This is the cmd line output:
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in [bundleresource://1072.fwk923366543:1/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in [bundleresource://1072.fwk923366543:2/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
> SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
> 14:09:55.604 [Worker-2] DEBUG o.e.m.c.i.p.r.ProjectRegistryRefreshJob - Queued refresh request: [/RemoteSystemsTempFiles/pom.xml]
> openjdk version "1.8.0_92"
> OpenJDK Runtime Environment (build 1.8.0_92-b14)
> OpenJDK 64-Bit Server VM (build 25.92-b14, mixed mode)
> 14:09:57.115 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository
> 14:09:57.142 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository
> 14:09:57.143 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshing: [L/RemoteSystemsTempFiles/pom.xml]
> 14:09:57.156 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshed: [L/RemoteSystemsTempFiles/pom.xml]
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007f521a6d7bfe, pid=12689, tid=0x00007f52cf5a3700
> #
> # JRE version: OpenJDK Runtime Environment (8.0_92-b14) (build 1.8.0_92-b14)
> # Java VM: OpenJDK 64-Bit Server VM (25.92-b14 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [libjavascriptcoregtk-3.0.so.0+0x4d4bfe] JSC::VM::throwException(JSC::ExecState*, JSC::JSValue)+0x236e
> #
> # Core dump written. Default location: /home/donato/core or core.12689
> #
> # An error report file with more information is saved as:
> # /home/donato/hs_err_pid12689.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22609) Provided wrong credentials, CDK server adapter says "started" even though it is not.
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22609?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22609:
-----------------------------------
Fix Version/s: 4.4.x
> Provided wrong credentials, CDK server adapter says "started" even though it is not.
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-22609
> URL: https://issues.jboss.org/browse/JBIDE-22609
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.0.Final
> Environment: Devstudio 10.0.0.GA (B33), CDK 2.1.RC4, Windows 10
> Reporter: Radim Hopp
> Priority: Critical
> Fix For: 4.4.x
>
>
> When CDK startup fails when it is provided wrong credentials (it fails on vagrant-registration), CDK server adapter sets its state to "started" and OS3 connection is created (even though OS3 is not running in vagrant) with some weird IP (10.0.2.15). Also error pops up saying "The CDK VM is up and running, but OpenShift is unreachable at url https://10.0.2.15:8443/healthz/ready". I really don't know where this IP comes from. I was able to reproduce it on Fedora using libvirt box and the IP was something like (192.168.x.x)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months