[JBoss JIRA] (JBIDE-24594) $0 subscription download doesn't work - Read timed out
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24594?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24594:
---------------------------------------
I wanted to see if I can still reproduce this. So I tried with a brand new installation of eclipse oxygen jee. Then I installed jbt 4.5.0.AM2 from market place (previously I installed abridged jbt from the update site, so it's not 100% the same, but hopefully that's not the issue). And eap 7.0 download works fine for me there. So I'm afraid I'm gonna have to close this JIRA for now.
> $0 subscription download doesn't work - Read timed out
> ------------------------------------------------------
>
> Key: JBIDE-24594
> URL: https://issues.jboss.org/browse/JBIDE-24594
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.5.0.AM1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM2
>
>
> When I try to download EAP 7.0 using Preferences -> Runtime Detection and Download, I get an error when it validates my redhat.com credentials.
> {code}
> Read timed out
> java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
> at java.net.SocketInputStream.read(SocketInputStream.java:171)
> at java.net.SocketInputStream.read(SocketInputStream.java:141)
> at sun.security.ssl.InputRecord.readFully(InputRecord.java:465)
> at sun.security.ssl.InputRecord.read(InputRecord.java:503)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
> at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930)
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735)
> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
> at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerWorkflowUtility.headerOnlyStatusCode(DownloadManagerWorkflowUtility.java:65)
> at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerWorkflowUtility.getWorkflowStatus(DownloadManagerWorkflowUtility.java:47)
> at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment.validateCredentials(DownloadManagerCredentialsFragment.java:205)
> at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment.access$1(DownloadManagerCredentialsFragment.java:203)
> at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment$3.run(DownloadManagerCredentialsFragment.java:168)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> {code}
> What I did: I was trying to verify JBIDE-24582, so I installed Eclipse Oxygen. Then JBoss Tools abridged (4.5.0.AM1). And then built the PR from that JIRA and installed it. I doubt it could cause this. Then I went to Preferences -> Runtime Detection and Download, selected eap 7.0, then added my account, but selected "always ask for password". Then I entered password and clicked Next. Now it failed with the above error. I tried several times.
> I tried the same in devstudio 11.0.0.AM1 and it works fine for me there, so that's odd - I was suspecting some server-side outage. I tried again in Eclipse and it still fails.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24584) Rename cdk adapter to cdk 2
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24584?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24584:
---------------------------------------
It turns out there is another place in the ui where this needs fixing - the runtime detectors in Preferences -> JBoss Tools -> JBoss Runtime Detection. I created a new jira for that: JBIDE-24749
> Rename cdk adapter to cdk 2
> ---------------------------
>
> Key: JBIDE-24584
> URL: https://issues.jboss.org/browse/JBIDE-24584
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.5.0.AM1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM2
>
>
> I just noticed that in the New Server wizard we have these two adapter types:
> Red Hat Container Development Kit
> Red Hat Container Development Kit 3
> Obviously I know the first one is 2.x, but if I didn't know there's no indication anywhere. So I think it's a good idea to rename it to reflect this.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24749) Rename cdk runtime detector to cdk 2
by Martin Malina (JIRA)
Martin Malina created JBIDE-24749:
-------------------------------------
Summary: Rename cdk runtime detector to cdk 2
Key: JBIDE-24749
URL: https://issues.jboss.org/browse/JBIDE-24749
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime-detection
Affects Versions: 4.5.0.AM2
Reporter: Martin Malina
Assignee: Rob Stryker
In JBIDE-24584 I requested that cdk server adapter be renamed to cdk 2 which is now done. But today I noticed that we missed the runtime detector:
Go to Preferences -> JBoss Tools -> JBoss Runtime Detection
On that page, there is a table called Available runtime detectors which, among others, includes:
Container Development Environment 3
Container Development Environment
So the latter should be renamed to include "2" or "2.x" - probably the latter to be consistent with the server adapter name.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBTIS-1144) Cannot install SwitchYard Tooling with a standalone installer nor from update site
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1144?page=com.atlassian.jira.plugin... ]
Paul Leacu reassigned JBTIS-1144:
---------------------------------
Assignee: Paul Leacu
> Cannot install SwitchYard Tooling with a standalone installer nor from update site
> ----------------------------------------------------------------------------------
>
> Key: JBTIS-1144
> URL: https://issues.jboss.org/browse/JBTIS-1144
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 11.0.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Blocker
> Fix For: 11.0.0.GA
>
> Attachments: 1500536110156.log, devstudiois-error.txt
>
>
> Cannot install SwitchYard Tooling with a standalone installer.
> {code}
> Missing requirement: SwitchYard 2.4.0.CR1-v20170717-1303-B16 (org.switchyard.tools.feature.feature.group 2.4.0.CR1-v20170717-1303-B16) requires 'org.jboss.ide.eclipse.freemarker.feature.feature.group 1.2.0' but it could not be found
> {code}
> Please see the attachments for full error messages.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4447) JBoss Tools Fuse not listed on Summary screen
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4447?page=com.atlassian.jira.plugin.... ]
Lukáš Valach commented on JBDS-4447:
------------------------------------
Thanks for correcting me [~nickboldt]. Fuse is now listed on Summary screen. Do we want to correct Fuse name also at "Select Additional Features to Install" screen?
Compare !Select_Additional_Features_to_Install.png|thumbnail! and !Summary_Information.png|thumbnail!
Possible PR: https://github.com/jbdevstudio/jbdevstudio-product/pull/465/files
> JBoss Tools Fuse not listed on Summary screen
> ---------------------------------------------
>
> Key: JBDS-4447
> URL: https://issues.jboss.org/browse/JBDS-4447
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 11.0.0.AM1
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Priority: Minor
> Fix For: 11.0.0.GA
>
> Attachments: Select_Additional_Features_to_Install.png, Summary_Information.png
>
>
> The JBoss Tools Fuse isn't listed on Summary screen though I have checked it on Features screen.
> There is summary I got:
> {code}
> Installation path:
> /home/lvalach/JBDS/test4
> Java VM path:
> default
> Components to install:
> Red Hat JBoss Developer Studio 11.0.0.AM1
> Disk Space:
> Available Disk Space: 65.28 GB
> Required Disk Space: 753.83 MB
> {code}
> I think that problem is here \[1\]. Fuse is no longer in integration-stack.fuse package but in com.jboss.devstudio.fuse package.
> https://github.com/jbdevstudio/jbdevstudio-product/blob/3a0300cb7f849b121...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4447) JBoss Tools Fuse not listed on Summary screen
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4447?page=com.atlassian.jira.plugin.... ]
Lukáš Valach updated JBDS-4447:
-------------------------------
Attachment: Select_Additional_Features_to_Install.png
> JBoss Tools Fuse not listed on Summary screen
> ---------------------------------------------
>
> Key: JBDS-4447
> URL: https://issues.jboss.org/browse/JBDS-4447
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 11.0.0.AM1
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Priority: Minor
> Fix For: 11.0.0.GA
>
> Attachments: Select_Additional_Features_to_Install.png, Summary_Information.png
>
>
> The JBoss Tools Fuse isn't listed on Summary screen though I have checked it on Features screen.
> There is summary I got:
> {code}
> Installation path:
> /home/lvalach/JBDS/test4
> Java VM path:
> default
> Components to install:
> Red Hat JBoss Developer Studio 11.0.0.AM1
> Disk Space:
> Available Disk Space: 65.28 GB
> Required Disk Space: 753.83 MB
> {code}
> I think that problem is here \[1\]. Fuse is no longer in integration-stack.fuse package but in com.jboss.devstudio.fuse package.
> https://github.com/jbdevstudio/jbdevstudio-product/blob/3a0300cb7f849b121...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4447) JBoss Tools Fuse not listed on Summary screen
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4447?page=com.atlassian.jira.plugin.... ]
Lukáš Valach updated JBDS-4447:
-------------------------------
Attachment: Summary_Information.png
> JBoss Tools Fuse not listed on Summary screen
> ---------------------------------------------
>
> Key: JBDS-4447
> URL: https://issues.jboss.org/browse/JBDS-4447
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 11.0.0.AM1
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Priority: Minor
> Fix For: 11.0.0.GA
>
> Attachments: Select_Additional_Features_to_Install.png, Summary_Information.png
>
>
> The JBoss Tools Fuse isn't listed on Summary screen though I have checked it on Features screen.
> There is summary I got:
> {code}
> Installation path:
> /home/lvalach/JBDS/test4
> Java VM path:
> default
> Components to install:
> Red Hat JBoss Developer Studio 11.0.0.AM1
> Disk Space:
> Available Disk Space: 65.28 GB
> Required Disk Space: 753.83 MB
> {code}
> I think that problem is here \[1\]. Fuse is no longer in integration-stack.fuse package but in com.jboss.devstudio.fuse package.
> https://github.com/jbdevstudio/jbdevstudio-product/blob/3a0300cb7f849b121...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4475) BundleException: Could not resolve module: *genericeditor*
by Lukáš Valach (JIRA)
Lukáš Valach created JBDS-4475:
----------------------------------
Summary: BundleException: Could not resolve module: *genericeditor*
Key: JBDS-4475
URL: https://issues.jboss.org/browse/JBDS-4475
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: rpm
Affects Versions: 11.0.0.GA
Environment: RHEL7
RHSCL: http://brewweb.engineering.redhat.com/brewroot/repos/devtools-1.0-rh-ecli...
Devstudio: 11.0-0.20170720.0620.el7
Reporter: Lukáš Valach
Assignee: Nick Boldt
Fix For: 11.0.0.GA
Attachments: rh-eclipse47-devstudio11.0-0.20170720.0620.el7.log.20170720-0858-clean_start_strict.txt, rh-eclipse47.log.20170720-0834-without_devstudio_strict.txt
After start of Devstudio installed from RPM I found these exceptions in the log:
{code}
!ENTRY org.eclipse.pde.genericeditor.extension 4 0 2017-07-20 09:00:15.704
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.pde.genericeditor.extension [1433]
Another singleton bundle selected: osgi.identity; osgi.identity="org.eclipse.pde.genericeditor.extension"; type="osgi.bundle"; version:Version="1.0.0.v20170703-2151"; singleton:="true"
at org.eclipse.osgi.container.Module.start(Module.java:444)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1628)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1607)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1579)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1522)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
!ENTRY org.eclipse.ui.genericeditor 4 0 2017-07-20 09:00:15.737
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.ui.genericeditor [1476]
Another singleton bundle selected: osgi.identity; osgi.identity="org.eclipse.ui.genericeditor"; type="osgi.bundle"; version:Version="1.0.0.v20170703-2151"; singleton:="true"
at org.eclipse.osgi.container.Module.start(Module.java:444)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1628)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1607)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1579)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1522)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
{code}
I also tried to install and run eclipse47 without devstudio and there wasn't this problem, so I guess that this issue is related only to devstudio.
It seems that there are installed multiple archives of genericeditor.
{code}
cd /opt/rh/rh-eclipse47/
find -iname "*org.eclipse.pde.genericeditor.extension*"
./root/usr/share/eclipse/droplets/eclipse-pde/eclipse/plugins/org.eclipse.pde.genericeditor.extension_1.0.0.v20170703-2151.jar
./root/usr/share/eclipse/droplets/eclipse-sdk/eclipse/plugins/org.eclipse.pde.genericeditor.extension.source_1.0.0.v20170703-2151.jar
./root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.eclipse.pde.genericeditor.extension_1.0.0.v20170315-0955.jar
find -iname "*org.eclipse.ui.genericeditor*"
./root/usr/share/eclipse/droplets/eclipse-sdk/eclipse/plugins/org.eclipse.ui.genericeditor.source_1.0.0.v20170703-2151.jar
./root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.eclipse.ui.genericeditor_1.0.0.v20170516-0821.jar
./root/usr/lib/eclipse/plugins/org.eclipse.ui.genericeditor_1.0.0.v20170703-2151.jar
cd ~/.eclipse/
find -iname "*org.eclipse.pde.genericeditor.extension*"
<nothing>
find -iname "*org.eclipse.ui.genericeditor*"
<nothing>
{code}
I don't see any impact to the user, Java, HTML and XML editor works fine.
Eclipse without Devstudio log: [^rh-eclipse47.log.20170720-0834-without_devstudio_strict.txt]
Eclipse with Devstudio log: [^rh-eclipse47-devstudio11.0-0.20170720.0620.el7.log.20170720-0858-clean_start_strict.txt]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months