[JBoss JIRA] (JBDS-4772) port offset does not work
by Bin Hu (Jira)
Bin Hu created JBDS-4772:
----------------------------
Summary: port offset does not work
Key: JBDS-4772
URL: https://issues.jboss.org/browse/JBDS-4772
Project: Red Hat CodeReady Studio (devstudio)
Issue Type: Bug
Affects Versions: 12.9.0.GA
Reporter: Bin Hu
Attachments: port-offset.jpg, version.jpg
the port offset checkbox does not work
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (JBDS-4771) port offset does not work
by Bin Hu (Jira)
Bin Hu created JBDS-4771:
----------------------------
Summary: port offset does not work
Key: JBDS-4771
URL: https://issues.jboss.org/browse/JBDS-4771
Project: Red Hat CodeReady Studio (devstudio)
Issue Type: Bug
Components: runtime-detection
Affects Versions: 12.9.0.GA
Reporter: Bin Hu
Assignee: Jeff MAURY
Attachments: port-offset.jpg, version.jpg
When testing the local server, I found the port offset checkbox does not work.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (JBIDE-26627) Provide full-fledged GNOME on linux images
by Tomáš Sedmík (Jira)
[ https://issues.jboss.org/browse/JBIDE-26627?page=com.atlassian.jira.plugi... ]
Tomáš Sedmík updated JBIDE-26627:
---------------------------------
Description:
If I try to provision a linux machine (Fedora, RHEL), the instance has not full-fledged GNOME environment configured. Therefore, I'm unable to perform manual testing on this machine.
Could you please reconfigure the images to provide full-fledged GNOME enabled by default?
It is needed for testing CRC.
was:
If I try to provision _rhel7-16gb_ machine, the instance has not full-fledged GNOME environment configured. Therefore, I'm unable to perform manual testing on this machine.
Could you please reconfigure the image to provide full-fledged GNOME?
I need it for testing CRC.
> Provide full-fledged GNOME on linux images
> ------------------------------------------
>
> Key: JBIDE-26627
> URL: https://issues.jboss.org/browse/JBIDE-26627
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Reporter: Tomáš Sedmík
> Priority: Major
> Fix For: 4.12.0.AM1
>
> Attachments: Screenshot from 2019-04-23 10-54-37.png
>
>
> If I try to provision a linux machine (Fedora, RHEL), the instance has not full-fledged GNOME environment configured. Therefore, I'm unable to perform manual testing on this machine.
> Could you please reconfigure the images to provide full-fledged GNOME enabled by default?
> It is needed for testing CRC.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (JBIDE-26627) Provide full-fledged GNOME on linux images
by Tomáš Sedmík (Jira)
[ https://issues.jboss.org/browse/JBIDE-26627?page=com.atlassian.jira.plugi... ]
Tomáš Sedmík updated JBIDE-26627:
---------------------------------
Fix Version/s: 4.12.0.AM1
> Provide full-fledged GNOME on linux images
> ------------------------------------------
>
> Key: JBIDE-26627
> URL: https://issues.jboss.org/browse/JBIDE-26627
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Reporter: Tomáš Sedmík
> Priority: Major
> Fix For: 4.12.0.AM1
>
> Attachments: Screenshot from 2019-04-23 10-54-37.png
>
>
> If I try to provision a linux machine (Fedora, RHEL), the instance has not full-fledged GNOME environment configured. Therefore, I'm unable to perform manual testing on this machine.
> Could you please reconfigure the images to provide full-fledged GNOME enabled by default?
> It is needed for testing CRC.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (JBIDE-26627) Provide full-fledged GNOME on linux images
by Tomáš Sedmík (Jira)
[ https://issues.jboss.org/browse/JBIDE-26627?page=com.atlassian.jira.plugi... ]
Tomáš Sedmík updated JBIDE-26627:
---------------------------------
Summary: Provide full-fledged GNOME on linux images (was: Provide full-fledged GNOME on RHEL 7 images)
> Provide full-fledged GNOME on linux images
> ------------------------------------------
>
> Key: JBIDE-26627
> URL: https://issues.jboss.org/browse/JBIDE-26627
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Reporter: Tomáš Sedmík
> Priority: Major
> Attachments: Screenshot from 2019-04-23 10-54-37.png
>
>
> If I try to provision _rhel7-16gb_ machine, the instance has not full-fledged GNOME environment configured. Therefore, I'm unable to perform manual testing on this machine.
> Could you please reconfigure the image to provide full-fledged GNOME?
> I need it for testing CRC.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (ERT-727) [GTK] vm crash when scrolling StyledText [EBZ#546274]
by Friendly Jira Robot (Jira)
Friendly Jira Robot created ERT-727:
---------------------------------------
Summary: [GTK] vm crash when scrolling StyledText [EBZ#546274]
Key: ERT-727
URL: https://issues.jboss.org/browse/ERT-727
Project: Eclipse Release Train
Issue Type: Task
Components: Platform
Reporter: Friendly Jira Robot
I suspect this is caused by 'Canvas.cachedCairo' becoming stale, which was introduced by Bug 540674. Will try to prepare a test snippet.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (JBIDE-26200) Server adapter wizard: Imported project is not filled into "Eclipse Project"
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26200?page=com.atlassian.jira.plugi... ]
Josef Kopriva commented on JBIDE-26200:
---------------------------------------
[~adietish] are you able to replicate this? It seems to me it is fixed now.
> Server adapter wizard: Imported project is not filled into "Eclipse Project"
> ----------------------------------------------------------------------------
>
> Key: JBIDE-26200
> URL: https://issues.jboss.org/browse/JBIDE-26200
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Final
> Reporter: André Dietisheim
> Assignee: Josef Kopriva
> Priority: Major
> Labels: import_wizard, server_adapter_wizard
> Fix For: 4.12.x
>
> Attachments: image-2018-07-16-14-26-26-327.png, screenshot-1.png
>
>
> steps:
> # ASSERT: make sure you have a service running on your server but it's *NOT* present in your Eclipse workspace (ex. created via the nodejs-mongo-persistent template)
> # EXEC: in Explorer: select the service of your application (ex. nodejs-mongo-persisten service) and pick "Server Adapter..." in it's context menu
> # ASSERT: server adapter wizard shows up with "Eclipse Project" empty and marked with an error
> !image-2018-07-16-14-26-26-327.png!
> # EXEC: hit "Import" to the right of the "Eclipse Project" text field
> # ASSERT: "Select Build Config" wizard shows up listing a build config to import (ex. nodejs-mongo-persistent)
> # EXEC: select the build config and finish the wizard
> # ASSERT: "Select Build Config" wizard disappears, you're back in the "Server Adapter" wizard & the project is imported to your worksapce in the background and eventually shows up in the workspace
> Result:
> "Eclipse Project" is not filled out (even though I just imported it), text field is therefore still decorated with an error
> !screenshot-1.png!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (JBIDE-26604) Cannot connect to JMX server connection with EAP 7.1 remote local system on Java 8
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26604?page=com.atlassian.jira.plugi... ]
Jeff MAURY resolved JBIDE-26604.
--------------------------------
Resolution: Won't Fix
> Cannot connect to JMX server connection with EAP 7.1 remote local system on Java 8
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-26604
> URL: https://issues.jboss.org/browse/JBIDE-26604
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, server
> Affects Versions: 4.11.0.Final
> Environment: Fedora 29, openjdk 1.8.0-201
> Reporter: Ondrej Dockal
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.12.0.AM1
>
> Attachments: EAP7.1-JMX_error.gif
>
>
> Problem is with default system java. This happens when system java or java on path is in version 11 and differs with the java we want the server to start with (Java 8).
> {code}
> eclipse.buildId=12.11.0.GA-v20190329-0120-B4247
> java.version=1.8.0_201
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/odockal/workspace-12110GA-Respin-Java8-JMX/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.ide.eclipse.as.core
> Error
> Fri Mar 29 16:42:53 CET 2019
> Error connecting to remote JMX. Please ensure your server is properly configured for JMX access.
> org.jboss.tools.jmx.core.JMXException: Error connecting to remote JMX. Please ensure your server is properly configured for JMX access.
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:228)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:161)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:136)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:131)
> at org.jboss.tools.jmx.core.tree.NodeUtils.createObjectNameTree(NodeUtils.java:54)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.loadRoot(JBossServerConnection.java:113)
> at org.jboss.tools.jmx.ui.internal.views.navigator.MBeanExplorerContentProvider$1.run(MBeanExplorerContentProvider.java:211)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> Caused by: java.io.EOFException: Read past end of file
> at org.jboss.marshalling.SimpleDataInput.eofOnRead(SimpleDataInput.java:151)
> at org.jboss.marshalling.SimpleDataInput.readUnsignedByteDirect(SimpleDataInput.java:294)
> at org.jboss.marshalling.SimpleDataInput.readUnsignedByte(SimpleDataInput.java:249)
> at org.jboss.marshalling.river.RiverUnmarshaller.start(RiverUnmarshaller.java:1346)
> at org.jboss.remotingjmx.protocol.v2.Common.prepareForUnMarshalling(Common.java:140)
> at org.jboss.remotingjmx.protocol.v2.Common.prepareForUnMarshalling(Common.java:110)
> at org.jboss.remotingjmx.protocol.v2.ClientCommon$BaseResponseHandler.handle(ClientCommon.java:184)
> at org.jboss.remotingjmx.protocol.v2.ClientCommon$MessageReceiver$1.run(ClientCommon.java:123)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> console log:
> {code}
> 16:42:53,240 WARN [org.jboss.remotingjmx.protocol.v2.ServerCommon] (pool-2-thread-1) Unexpected internal error: java.lang.ExceptionInInitializerError
> at org.jboss.marshalling.river//org.jboss.marshalling.river.ClassDescriptors.<clinit>(ClassDescriptors.java:99)
> at org.jboss.marshalling.river//org.jboss.marshalling.river.RiverUnmarshaller.doReadClassDescriptor(RiverUnmarshaller.java:1241)
> at org.jboss.marshalling.river//org.jboss.marshalling.river.RiverUnmarshaller.doReadClassDescriptor(RiverUnmarshaller.java:1040)
> at org.jboss.marshalling.river//org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1354)
> at org.jboss.marshalling.river//org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:275)
> at org.jboss.marshalling.river//org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:208)
> at org.jboss.marshalling//org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:76)
> at org.jboss.remoting-jmx//org.jboss.remotingjmx.protocol.v2.ServerProxy$QueryNamesHandler.handle(ServerProxy.java:1102)
> at org.jboss.remoting-jmx//org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153)
> at org.jboss.as.jmx//org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:71)
> at org.jboss.as.jmx//org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:66)
> at org.wildfly.security.elytron-private//org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287)
> at org.wildfly.security.elytron-private//org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244)
> at org.jboss.as.controller//org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
> at org.jboss.as.controller//org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
> at org.jboss.as.jmx//org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:66)
> at org.jboss.remoting-jmx//org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149)
> at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator!
> at org.jboss.marshalling.river//org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287)
> ... 20 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months