[JBoss JIRA] (JBIDE-24312) Explorer: SSL certificate dialog shows up many many times when using internal test server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24312?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24312:
-------------------------------------
Steps to Reproduce:
# EXEC: launch connection wizard so that you can create a new connection to the internal test server
# ASSERT: connection wizard shows up
# EXEC: fill in the form, using https://*.redhat.com as server, "Basic" as "Protocol", and your kerberos credentialy. Hit "Finish"
# ASSERT: SSL Dialog shows up
# EXEC: Hit "Yes"
# ASSERT: SSL Dialog shows up a 2nd time
# EXEC: hit "Yes"
# ASSERT: Connection shows up in the OpenShift explorer
# EXEC: unfold the connection
# EXEC: create a new project and unfold the connection once it is created
# ASSERT: project shows up as child of the connection
# EXEC: unfold the project
Result:
I have the SSL dialog showing up 17x and I have to confirm all of them. Once finished, a child "glusterfs-cluster" (service) shows up
!create connection paas.mp4|width=1024,height=700!
was:
# EXEC: launch connection wizard so that you can create a new connection to the internal test server
# ASSERT: connection wizard shows up
# EXEC: fill in the form, using https://*.redhat.com as server, "Basic" as "Protocol", and your kerberos credentialy. Hit "Finish"
# ASSERT: SSL Dialog shows up
# EXEC: Hit "Yes"
# ASSERT: SSL Dialog shows up a 2nd time
# EXEC: hit "Yes"
# ASSERT: Connection shows up in the OpenShift explorer
# EXEC: unfold the connection
# EXEC: create a new project and unfold the connection once it is created
# ASSERT: project shows up as child of the connection
# EXEC: unfold the project
Result:
I have the SSL dialog showing up 17x and I have to confirm all of them. Once finished, a child "glusterfs-cluster" (service) shows up
!create connection paas.mp4|width=1024,height=700!
> Explorer: SSL certificate dialog shows up many many times when using internal test server
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-24312
> URL: https://issues.jboss.org/browse/JBIDE-24312
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Environment: MacOS
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.4.4.Final
>
> Attachments: Screencast_04-25-2017_06-56-06+PM.webm, create connection paas.mp4, diff-in-serial.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24291) Improve initial loading of JMX Connection tree
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24291?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-24291:
-----------------------------------------
I tried only with Jolokia for now.
Worth trying with JMX over RMI too.
> Improve initial loading of JMX Connection tree
> ----------------------------------------------
>
> Key: JBIDE-24291
> URL: https://issues.jboss.org/browse/JBIDE-24291
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jmx
> Affects Versions: 4.4.4.AM2
> Reporter: Aurélien Pupier
>
> JMX Navigator is taking quite a long time to load the first level of elements when the connection is targeting a remote server with quite a high latency (such open.paas.redhat.com which is taking around 450ms for each request for me)
> It would be nice to improve the lazy-loading to be able to display the first level of the tree without loading every MBeans and doing one query per MBean Names registered on the server.
> For instance on a FIS project, it is 112 MBean Names * 450ms = 50.4s!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24140) Test Failure(s) in JBIDE 4.4.4.AM2 for jst component - org.jboss.tools.jst.web.test.WebXMLValidationTest
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24140?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24140:
-------------------------------
Fix Version/s: 4.4.4.Final
(was: 4.4.4.AM3)
> Test Failure(s) in JBIDE 4.4.4.AM2 for jst component - org.jboss.tools.jst.web.test.WebXMLValidationTest
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24140
> URL: https://issues.jboss.org/browse/JBIDE-24140
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jst
> Affects Versions: 4.4.4.AM2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: testfailure
> Fix For: 4.4.4.Final
>
>
> *2 Test Failure(s) in JBIDE 4.4.4.AM2 for jst component:*
> http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/d...
> [Search for Test Failure JIRAs in JBIDE 4.4.4.AM2 for jst component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...]
> -----
> {code}
> All Failed Tests
> Test Name
> Duration
> Age
> org.jboss.tools.jst.web.test.WebXMLValidationTest.testPathsInLoginConfig 0.56 sec 5
> org.jboss.tools.jst.web.test.WebXMLValidationTest.testServletClassWithIdenticalComments 15 ms 11
> {code}
> {code}
> Failed
> org.jboss.tools.jst.web.test.WebXMLValidationTest.testServletClassWithIdenticalComments (from org.jboss.tools.jst.web.test.JstWebAllTests)
> Failing for the past 11 builds (Since #69 )
> Took 15 ms.
> add description
> Error Message
> Marker matches the 'servlet-class references to non-existent class "javax.faces.webapp.FacesServlet111"' pattern was found at wrong lines. Expected: 11 but were: 9
> Stacktrace
> junit.framework.AssertionFailedError: Marker matches the 'servlet-class references to non-existent class "javax.faces.webapp.FacesServlet111"' pattern was found at wrong lines. Expected: 11 but were: 9
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsCreated(AbstractResourceMarkerTest.java:200)
> at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsCreated(AbstractResourceMarkerTest.java:413)
> at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsCreated(AbstractResourceMarkerTest.java:409)
> at org.jboss.tools.jst.web.test.WebXMLValidationTest.testServletClassWithIdenticalComments(WebXMLValidationTest.java:55){code}
> {code}
> Failed
> org.jboss.tools.jst.web.test.WebXMLValidationTest.testPathsInLoginConfig (from org.jboss.tools.jst.web.test.JstWebAllTests)
> Failing for the past 5 builds (Since Unstable#75 )
> Took 0.56 sec.
> add description
> Stacktrace
> junit.framework.AssertionFailedError: null
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertTrue(Assert.java:31)
> at junit.framework.TestCase.assertTrue(TestCase.java:201)
> at org.jboss.tools.jst.web.test.WebXMLValidationTest.testPathsInLoginConfig(WebXMLValidationTest.java:103){code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months