[JBoss JIRA] (JBTIS-1155) Consider downgrade to Apache HTTP Client to avoid proxy/update and access problems
by Sopot Cela (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1155?page=com.atlassian.jira.plugin... ]
Sopot Cela edited comment on JBTIS-1155 at 9/12/17 9:15 AM:
------------------------------------------------------------
Hello Rick,
We've been looking at this from the Eclipse side of things. The main issue we are facing now it's that we are not able to reproduce the issue.
As far as I can see, in the ticket the setup looks like this:
Teiid -> cntlm -> Forefront TMG (which uses NTLM v2 auth) -> web
The Forefront TMG is a software which we don't have access to in order to reproduce. This product was discontinued as far as its website goes http://www.microsoft.com/tmg in favor of another major Security solution. However we will try to reproduce it now with other proxy solutions and hope that we can hit the issue.
The client was supposed to try to reproduce it with Squid. Do you know if managed to?
was (Author: scela):
Hello Rick,
We've been looking at this from the Eclipse side of things. The main issue we are facing now it's that we are not able to reproduce the issue.
As far as I can see, in the ticket the setup looks like this:
Teiid -> cntlm -> Forefront TMG (which uses NTLM v2 auth) -> web
The Forefront TMG is a software which we don't have access to in order to reproduce. This product was discontinued as far as its website goes http://www.microsoft.com/tmg in favor of another major Security solution. However we will try to reproduce it now with other proxy solutions and hope that we can hit the issue.
The client was supposed to try to reproduce it with Squid. Do you know if managed to reproduce?
Also it was mentioned that they would try with Squid. Did he get back to you on whether he is able to reproduce that?
> Consider downgrade to Apache HTTP Client to avoid proxy/update and access problems
> ----------------------------------------------------------------------------------
>
> Key: JBTIS-1155
> URL: https://issues.jboss.org/browse/JBTIS-1155
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: teiid
> Environment: JBoss Data Virt IDE (Teiid Designer)
> Reporter: Rick Wagner
>
> Users behind proxy report a problem with access to REST services and update problems.
> Research suggests this problem might be related to recent versions of Apache HTTPClient.
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=422665
> [2] http://sonarqube-archive.15.x6.nabble.com/sonar-dev-SonarQube-Plugin-3-3-...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24938) server.it.weekly jenkins job runs out of disk space on Windows
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24938?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24938:
---------------------------------------
I wanted to check this on a mac slave and there is a problem there with the static build env settings - HUDSON_STATIC_ENV is not defined on windows or mac. The consequence (at least on mac, but likely same for windows) is that the variable won't get substituted for anything and a directory like this will be created:
./itests/org.jboss.tools.as.itests/${HUDSON_STATIC_ENV}
./itests/org.jboss.tools.as.management.itests/${HUDSON_STATIC_ENV}
./itests/org.jboss.tools.as.ui.bot.itests/${HUDSON_STATIC_ENV}
Each at 1.4 GB. This happened even before Nick's fix, so it's still much improved.
The problem with HUDSON_STATIC_ENV is actually reported in JBIDE-24964. So I want to fix it at least for mac so I can verify that the footprint is now much smaller.
> server.it.weekly jenkins job runs out of disk space on Windows
> --------------------------------------------------------------
>
> Key: JBIDE-24938
> URL: https://issues.jboss.org/browse/JBIDE-24938
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.1.AM2
> Reporter: Martin Malina
> Assignee: Martin Malina
> Fix For: 4.5.1.AM2
>
>
> This job is failing on Windows:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i...
> It's because it runs out of disk space.
> The windows instances have (I believe) 30GB of disk space. This is set up in our openstack instance by eng-ops:
> https://ci-rhos.centralci.eng.rdu2.redhat.com/dashboard/
> If we wanted more space, we would need to ask eng ops to change this. But it's probably the same for all other users, so I don't think they would change it easily. And in any case, it should be enough.
> The main thing is that we need to reduce the space the tests are using.
> They download all the runtimes via the itests pom:
> https://github.com/jbosstools/jbosstools-server/blob/master/as/itests/pom...
> The main problem is that this happens 4 times:
> 3.5G ./org.jboss.tools.as.management.itests/target/requirements
> 3.5G ./org.jboss.tools.as.itests/target/requirements
> 3.5G ./target/requirements
> 3.5G ./org.jboss.tools.as.ui.bot.itests/target/requirements
> Fortunately this doesn't mean that all the servers are really downloaded 4 times - they are downloaded once and stored in the local maven download cache. But then the zips are copied over for each of the modules and unzipped.
> So, there are several options:
> a) Get rid of the zips once they're unzipped - that would save half the space. Unfortunately the download plugin does not support this:
> https://github.com/maven-download-plugin/maven-download-plugin
> b) Delete the requirements dir for each module at the end of the maven module lifecycle. This might be doable, needs investigating.
> c) Change the overall setup so that only one download is needed for all the tests - i.e. the child modules don't inherit the download plugin call, but instead use the downloaded runtimes from the higher pom (itests)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBTIS-1155) Consider downgrade to Apache HTTP Client to avoid proxy/update and access problems
by Sopot Cela (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1155?page=com.atlassian.jira.plugin... ]
Sopot Cela edited comment on JBTIS-1155 at 9/12/17 9:06 AM:
------------------------------------------------------------
Hello Rick,
We've been looking at this from the Eclipse side of things. The main issue we are facing now it's that we are not able to reproduce the issue.
As far as I can see, in the ticket the setup looks like this:
Teiid -> cntlm -> Forefront TMG (which uses NTLM v2 auth) -> web
The Forefront TMG is a software which we don't have access to in order to reproduce. This product was discontinued as far as its website goes http://www.microsoft.com/tmg in favor of another major Security solution. However we will try to reproduce it now with other proxy solutions and hope that we can hit the issue.
The client was supposed to try to reproduce it with Squid. Do you know if managed to reproduce?
Also it was mentioned that they would try with Squid. Did he get back to you on whether he is able to reproduce that?
was (Author: scela):
Hello Rick,
We've been looking at this from the Eclipse side of things. The main issue we are facing now it's that we are not able to reproduce the issue.
As far as I can see, in the ticket the setup looks like this:
Teiid -> cntlm -> Forefront TMG (which uses NTLM v2 auth) -> web
The Forefront TMG is a software which we don't have access to in order to reproduce. This product was discontinued as far as its website goes http://www.microsoft.com/tmg in favor of another major Security solution. However we will try to reproduce it now with other proxy solutions and hope that we can hit the issue.
The client was supposed to try to reproduce it with Squid. Do you know if managed to reproduce?
The client mentioned they would try with Squid. Did he get back to you on whether he is able to reproduce that?
> Consider downgrade to Apache HTTP Client to avoid proxy/update and access problems
> ----------------------------------------------------------------------------------
>
> Key: JBTIS-1155
> URL: https://issues.jboss.org/browse/JBTIS-1155
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: teiid
> Environment: JBoss Data Virt IDE (Teiid Designer)
> Reporter: Rick Wagner
>
> Users behind proxy report a problem with access to REST services and update problems.
> Research suggests this problem might be related to recent versions of Apache HTTPClient.
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=422665
> [2] http://sonarqube-archive.15.x6.nabble.com/sonar-dev-SonarQube-Plugin-3-3-...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24763) Some server itests are failing on Jenkins
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24763?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24763:
---------------------------------------
Current status: all green!
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i...
(As of build #49/#50)
> Some server itests are failing on Jenkins
> -----------------------------------------
>
> Key: JBIDE-24763
> URL: https://issues.jboss.org/browse/JBIDE-24763
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
> Attachments: server-itests.png
>
>
> Here's the job:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Currently we got around 30 failures:
> {code}
> All Failed Tests
> Test Name
> Duration
> Age
> org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[1] 5.3 sec 1
> org.jboss.tools.as.management.itests.AS7ManagerIntegrationTest.canGetServerState[7] 76 ms 1
> org.jboss.tools.as.ui.bot.itests.parametized.server.RuntimeDetectionDuplicatesTest.duplicateRuntimes default [0] 17 sec 1
> org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[4] 1.7 sec 2
> org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[4] 5.3 sec 2
> org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[1] 2.3 sec 3
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[0] 4.4 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[1] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[2] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[3] 2.2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[4] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[5] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[6] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[7] 2.3 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[8] 2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[9] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[10] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[11] 2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[12] 2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[13] 2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[14] 2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[15] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[16] 2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[17] 2 sec 6
> org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[0] 1.7 sec 6
> org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [0] 1 min 49 sec 6
> org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [1] 1 min 43 sec 6
> org.jboss.tools.wtp.runtimes.tomcat.itests.ServerUtilTest.testUniqueServerName 2.6 sec 6
> org.jboss.tools.wtp.runtimes.tomcat.itests.TomcatDetectionTest.testTomcatDetection 0.13 sec 6
> org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[2] 1.7 sec 7
> {code}
> Nick already shared some details in JBIDE-22799
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-25009) Migrate Installer and RPM tests to RedDeer 2
by Lukáš Valach (JIRA)
Lukáš Valach created JBIDE-25009:
------------------------------------
Summary: Migrate Installer and RPM tests to RedDeer 2
Key: JBIDE-25009
URL: https://issues.jboss.org/browse/JBIDE-25009
Project: Tools (JBoss Tools)
Issue Type: Task
Components: integration-tests
Affects Versions: 4.5.1.AM2
Reporter: Lukáš Valach
Assignee: Lukáš Valach
Fix For: 4.5.1.AM3
We have to migrate Installer, BYOE, Central and RPM the tests to RD2.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months