[JBoss JIRA] (JBIDE-23487) Server adapter: Publishing fails when server adapter is created out of eap app running on openshift (in cdk)
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23487?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-23487:
---------------------------------------
So far I have not experience such kind of issue. At least not on staged AM3 build. I will update this issue once I will perform full regression test run on final build.
> Server adapter: Publishing fails when server adapter is created out of eap app running on openshift (in cdk)
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23487
> URL: https://issues.jboss.org/browse/JBIDE-23487
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Martin Malina
> Labels: openshift_v3, rsync, server_adapter
> Fix For: 4.4.2.Final
>
>
> While testing Rob's jolokia stuff from JBIDE-23429 I did this:
> 1. Start CDK (2.3.cr1)
> 2. Create eap64-basic-s2i app
> 3. Wait till the app is built and the pod is running
> 4. Right-click the eap-app in OpenShift explorer and create a server adapter
> 5. Now the server adapter is publishing and this will fail:
> {code}
> Could not sync /Users/rasp/jbossqa/JBDS/10.0.0/workspace-neon-1a/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy to all pods running the service eap-app
> Syncing com.openshift.restclient.capability.resources.IRSyncable$LocalPeer@41249d31 to com.openshift.restclient.capability.resources.IRSyncable$PodPeer@27c8ba3a failed: Unable to connect to the server: net/http: TLS handshake timeout
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2]
> error: exit status 12
> {code}
> This is on macOS Sierra with JBoss Tools from master with Rob's patches, but he says his patches have nothing to do with publishing. I may try out a normal build of devstudio or JBT later.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23488) NullPointerException in WizardDialogHelper.openWizard
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23488?page=com.atlassian.jira.plugi... ]
George Gastaldi reassigned JBIDE-23488:
---------------------------------------
Assignee: George Gastaldi
> NullPointerException in WizardDialogHelper.openWizard
> -----------------------------------------------------
>
> Key: JBIDE-23488
> URL: https://issues.jboss.org/browse/JBIDE-23488
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: Automated Error Reporting Bot
> Assignee: George Gastaldi
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> java.lang.NullPointerException: null
> at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:103)
> at org.jboss.tools.forge.ui.internal.ext.handlers.RunForgeCommandHandler.openWizard(RunForgeCommandHandler.java:85)
> at org.jboss.tools.forge.ui.internal.ext.handlers.RunForgeCommandHandler.execute(RunForgeCommandHandler.java:72)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> Bundles:
> | org.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.6.0.v20160319-0612 |
> | org.eclipse.swt | 3.105.0.v20160519-0649 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.jboss.tools.forge.ui.ext | 2.0.2.Final-v20160331-1851-B95 | 2.0.101.v20160607-1332 |
> Operating Systems:
> | Linux | 4.4.0 | 4.4.0 |
> | MacOSX | 10.11.5 | 10.11.5 |
> | Windows | 6.1.0 | 6.3.0 |
> The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/57a34e1fe4b084ea943... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23488) NullPointerException in WizardDialogHelper.openWizard
by Automated Error Reporting Bot (JIRA)
Automated Error Reporting Bot created JBIDE-23488:
-----------------------------------------------------
Summary: NullPointerException in WizardDialogHelper.openWizard
Key: JBIDE-23488
URL: https://issues.jboss.org/browse/JBIDE-23488
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Reporter: Automated Error Reporting Bot
The following problem was reported via the automated error reporting:
Message: HIDDEN
java.lang.NullPointerException: null
at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:103)
at org.jboss.tools.forge.ui.internal.ext.handlers.RunForgeCommandHandler.openWizard(RunForgeCommandHandler.java:85)
at org.jboss.tools.forge.ui.internal.ext.handlers.RunForgeCommandHandler.execute(RunForgeCommandHandler.java:72)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
Bundles:
| org.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.6.0.v20160319-0612 |
| org.eclipse.swt | 3.105.0.v20160519-0649 | 3.105.0.v20160603-0902 |
| org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
| org.jboss.tools.forge.ui.ext | 2.0.2.Final-v20160331-1851-B95 | 2.0.101.v20160607-1332 |
Operating Systems:
| Linux | 4.4.0 | 4.4.0 |
| MacOSX | 10.11.5 | 10.11.5 |
| Windows | 6.1.0 | 6.3.0 |
The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/57a34e1fe4b084ea943... for the latest data.
Thank you for your assistance.
Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22810:
-------------------------------------
Labels: explorer openshift_v3 windows (was: )
> OpenShift Explorer: empty at start
> ----------------------------------
>
> Key: JBIDE-22810
> URL: https://issues.jboss.org/browse/JBIDE-22810
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: explorer, openshift_v3, windows
> Fix For: 4.4.2.Final
>
> Attachments: EmptyViewAtStart.png
>
>
> When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections.
> I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22810:
-------------------------------------
Environment: windows
> OpenShift Explorer: empty at start
> ----------------------------------
>
> Key: JBIDE-22810
> URL: https://issues.jboss.org/browse/JBIDE-22810
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Environment: windows
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: explorer, openshift_v3, windows
> Fix For: 4.4.2.Final
>
> Attachments: EmptyViewAtStart.png
>
>
> When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections.
> I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22810:
------------------------------------------
I can still reproduce this using 4.4.2.AM3 (in my virtualbox). [~jeffmaury] Could you please take care of this one since you're running Windows? Developing in Virtualbox is a pain.
> OpenShift Explorer: empty at start
> ----------------------------------
>
> Key: JBIDE-22810
> URL: https://issues.jboss.org/browse/JBIDE-22810
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.2.Final
>
> Attachments: EmptyViewAtStart.png
>
>
> When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections.
> I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4175) RPM version: NPE after install from Red Hat Central
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-4175:
------------------------------------
Assignee: Václav Kadlčík
> RPM version: NPE after install from Red Hat Central
> ---------------------------------------------------
>
> Key: JBDS-4175
> URL: https://issues.jboss.org/browse/JBDS-4175
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Environment: RHEL 7.2 with RHSCL repositories available:
> * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....)
> * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...)
> Reporter: Václav Kadlčík
> Assignee: Václav Kadlčík
> Fix For: 10.2.0.GA
>
> Attachments: sw_to_install.txt, workspace.log
>
>
> I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
> I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
> Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4175) RPM version: NPE after install from Red Hat Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4175:
----------------------------------
It's also useful to start eclipse with ./eclipse -console -consolelog -debug | tee log.text
Then you can use the OSGi console to see what bundles are active or ignored.
You can also use the -clean flag, which might solve the NPE.
Or re-enable the reconciler and see of it complains about a conflict.
> RPM version: NPE after install from Red Hat Central
> ---------------------------------------------------
>
> Key: JBDS-4175
> URL: https://issues.jboss.org/browse/JBDS-4175
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Environment: RHEL 7.2 with RHSCL repositories available:
> * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....)
> * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...)
> Reporter: Václav Kadlčík
> Fix For: 10.2.0.GA
>
> Attachments: sw_to_install.txt, workspace.log
>
>
> I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
> I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
> Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4174) Install Vagrant and Virtual box for macOS out of Apple DIsk Image
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4174?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-4174:
-------------------------------------
Mounting dmg file:
{code}hdiutil attach -mountpoint /Volumes/$\{unique-name\} $\{path.to.dmg.file\}{code}
Run installer for package in mounted folder
{code}installer -pkg /Volumes/*\{unique-name\}/package.pkg -target /{code}
Then two commands above should be wrapped with
{code}osascript -e "do shell script \"$\{shell.script\}\" with administrator privileges"{code}
> Install Vagrant and Virtual box for macOS out of Apple DIsk Image
> -----------------------------------------------------------------
>
> Key: JBDS-4174
> URL: https://issues.jboss.org/browse/JBDS-4174
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.2.0.AM3
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.2.0.GA
>
>
> Installation can be done in two commands:
> 1. mounting dmg file as a folder
> 2. running macOS installer with pkg file name for corresponding application
> To trigger privilege lifting both commands should be wrapped with osascript command that require administartive account.
> Consequences are there are going o be two requests for administrator credentials.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4176) Useless-provides detected by RPMlint
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4176?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-4176:
------------------------------------
Assignee: Nick Boldt
> Useless-provides detected by RPMlint
> ------------------------------------
>
> Key: JBDS-4176
> URL: https://issues.jboss.org/browse/JBDS-4176
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.2.0.AM3
> Environment: RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.2.0.GA
>
>
> The rpmlint detects some problems in rpm package:
> {code}
> rpmlint -f ./rpmlint.conf ./rh-eclipse46-devstudio-10.2-0.20161111.1151.el7.x86_64.rpm
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(com.google.guava)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(com.google.inject)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(javax.wsdl)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.collections)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.io)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.lang3)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.logging)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.api)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.connector.basic)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.impl)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.spi)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.util)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(com.fasterxml.classmate)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.jboss.logging.jboss-logging)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.yaml.snakeyaml)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(slf4j.api)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.objectweb.asm)
> 1 packages and 0 specfiles checked; 17 errors, 0 warnings.
> {code}
> There are only important problems in the list above, another errors/warnings were suppressed according to discussion with [~vkadlcik].
> There is configuration of rpmlint filter:
> {code}
> addFilter("W: ") # Warnings can be suppressed
> addFilter("E: dir-or-file-in-opt") # False positive
> addFilter("E: devel-dependency") # False positive
> addFilter("E: explicit-lib-dependency") # May be improved but is not important for now
> addFilter("E: non-executable-script") # 99% of these errors are false positive comming from upstream, there is a very small chance to get relevant error
> addFilter("E: wrong-script-interpreter") # The same as above
> addFilter("E: zero-length") # The same as above
> {code}
> [~vkadlcik] please correct me if I'm wrong.
> RPMlint test has been automated, you can find it in [jenkins|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months