[JBoss JIRA] (JBTIS-1103) SAP tests are failing due to installation timeout
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-1103:
----------------------------------------
Summary: SAP tests are failing due to installation timeout
Key: JBTIS-1103
URL: https://issues.jboss.org/browse/JBTIS-1103
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: Fuse IDE, QE
Affects Versions: 4.4.3.CR1
Reporter: Andrej Podhradsky
Assignee: Andrej Podhradsky
Fix For: 4.4.3.CR1
SAP tests are failing due to installation timeout.
There is an issue with the new Eclipse where all installations take toooo long. See JBDS-4343
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4343) Installation hangs on 'Configuring toolingorg.eclipse.equinox.launcher.*'
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBDS-4343?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky commented on JBDS-4343:
-----------------------------------------
This is not only related to Devstudio installation. This affects all installations :(
Is it already reported in Eclipse bugzilla?
> Installation hangs on 'Configuring toolingorg.eclipse.equinox.launcher.*'
> -------------------------------------------------------------------------
>
> Key: JBDS-4343
> URL: https://issues.jboss.org/browse/JBDS-4343
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.4.0.AM2
> Environment: devstudio-10.4.0.AM2-v20170330-1543-B348-installer-standalone.jar
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 11.0.0.GA
>
> Attachments: install.png
>
>
> The installer spends several minutes in this state:
> !install.png|thumbnail!
> Just for comparison
> - AM1 installation takes total of about 2 minutes 15 seconds
> - AM2 takes 5 minutes 40 seconds
> There is no shortage of memory or disk I/O availability, the CPU is not topped off (even though AM2 eats up more CPU itself during this time).
> DTRACE=true reveals nothing interesting really, this is what it says in the particular moment (notice how much time the operation takes):
> {noformat}
> Configuring toolingorg.eclipse.equinox.launcher.gtk.linux.x86_64
> Preparing to commit the provisioning operation.
> Committing the provisioning operation.
> Operation completed in 289855 ms.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-23869:
-----------------------------------------
{quote}Don't think we can do more as the request is rejected by OpenShift for authentication reason. You need to setup your OpenShift credentials on the JMX connection (HTTP header){quote}
Do you mean that the OpenShift server is providing the "Invalid status type java.lang.String('Failure') recevived".
I'm very sceptical on that.
With this error the user has no idea that it is due to some authentication issue, so 2 possibilities:
- OpenShift server is providing a bad response --> this need to be improved on OpenShift server side
- the OpenShift server response is ate by Jolokia or JBoss Tools --> this need to be fixed in Jolokia or JBoss Tools
> ClassCastException with Jolokia connection
> ------------------------------------------
>
> Key: JBIDE-23869
> URL: https://issues.jboss.org/browse/JBIDE-23869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, openshift
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: jmx, jolokia, openshift
> Fix For: 4.4.4.Final
>
> Attachments: failure.png, image-2017-02-06-13-54-27-708.png
>
>
> !image-2017-02-06-13-54-27-708.png|thumbnail!
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767
> !MESSAGE An internal error occurred during: "Connect Job".
> !STACK 0
> java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-23869:
------------------------------------
Don't think we can do more as the request is rejected by OpenShift for authentication reason. You need to setup your OpenShift credentials on the JMX connection (HTTP header)
> ClassCastException with Jolokia connection
> ------------------------------------------
>
> Key: JBIDE-23869
> URL: https://issues.jboss.org/browse/JBIDE-23869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, openshift
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: jmx, jolokia, openshift
> Fix For: 4.4.4.Final
>
> Attachments: failure.png, image-2017-02-06-13-54-27-708.png
>
>
> !image-2017-02-06-13-54-27-708.png|thumbnail!
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767
> !MESSAGE An internal error occurred during: "Connect Job".
> !STACK 0
> java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months