[JBoss JIRA] (JBIDE-19820) Batch feature makes wildfly import way slower
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19820?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-19820:
-----------------------------------------------
I did two new PR, to encapsulate Jandex use inside common. Our API has two query methods.
> Batch feature makes wildfly import way slower
> ---------------------------------------------
>
> Key: JBIDE-19820
> URL: https://issues.jboss.org/browse/JBIDE-19820
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.3.0.Alpha2
> Reporter: Rastislav Wagner
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
>
> I made a comparison between Eclipse M6 and Eclipse M6 with batch feature installed while importing wildfly. WF is imported as maven project, maven is set to offline mode and local repository contains all needed dependencies.
> I did a 4 runs with following results:
> M6 was able to import WF 628,575,577,612 (in seconds) = average 598s
> M6 with batch feature: 843,832,924,877 (in seconds) = average 869s
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19641:
-------------------------------------
[~brian.stansberry] Sorry for the delay:
Jars JBT is using to communicate with 7.x servers:
jboss-as-controller-client-7.2.0.Final-redhat-4.jar
jboss-as-protocol-7.2.0.Final-redhat-4.jar
jboss-dmr-1.1.6.Final-redhat-1.jar
jboss-logging-3.1.2.GA-redhat-1.jar
jboss-marshalling-1.3.16.GA-redhat-1.jar
jboss-marshalling-river-1.3.16.GA-redhat-1.jar
jboss-remoting-3.2.16.GA.jar
jboss-sasl-1.0.3.Final-redhat-1.jar
jboss-threads-2.1.0.Final-redhat-1.jar
xnio-api-3.0.7.GA-redhat-1.jar
xnio-nio-3.0.7.GA-redhat-1.jar
---
EAP 6.4 using:
jboss-as-controller-client-7.5.0.Final-redhat-21.jar
jboss-as-protocol-7.5.0.Final-redhat-21.jar
jboss-dmr-1.2.2.Final-redhat-1.jar
jboss-logging-3.1.4.GA-redhat-2.jar
jboss-marshalling-1.4.10.Final-redhat-1.jar
jboss-marshalling-river-1.4.10.Final-redhat-1.jar
jboss-marshalling-river-1.4.10.Final-redhat-1.jar
jboss-remoting-3.3.4.Final-redhat-1.jar
jboss-sasl-1.0.5.Final-redhat-1.jar
jboss-threads-2.1.2.Final-redhat-1.jar
xnio-api-3.0.13.GA-redhat-1.jar
xnio-nio-3.0.13.GA-redhat-1.jar
So obviously there's a bit of a disconnect here. Do you think it's a good idea to update to the jars from eap 6.4? Would they still be able to communicate with all 7.x servers? Or has that not been substantially tested?
> Big war deployment via management API gets stuck
> ------------------------------------------------
>
> Key: JBIDE-19641
> URL: https://issues.jboss.org/browse/JBIDE-19641
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
> Attachments: stuck-deploy-eap-jstack-osx.log, stuck-deploy-eap-jstack-rhel.log, stuck-deploy-jstack-osx.log, stuck-deploy-jstack-rhel.log
>
>
> When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through.
> This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ]
Rob Stryker edited comment on JBIDE-19641 at 6/2/15 2:41 PM:
-------------------------------------------------------------
[~brian.stansberry] Sorry for the delay:
Jars JBT is using to communicate with JBoss 7.x / EAP 6.x servers:
jboss-as-controller-client-7.2.0.Final-redhat-4.jar
jboss-as-protocol-7.2.0.Final-redhat-4.jar
jboss-dmr-1.1.6.Final-redhat-1.jar
jboss-logging-3.1.2.GA-redhat-1.jar
jboss-marshalling-1.3.16.GA-redhat-1.jar
jboss-marshalling-river-1.3.16.GA-redhat-1.jar
jboss-remoting-3.2.16.GA.jar
jboss-sasl-1.0.3.Final-redhat-1.jar
jboss-threads-2.1.0.Final-redhat-1.jar
xnio-api-3.0.7.GA-redhat-1.jar
xnio-nio-3.0.7.GA-redhat-1.jar
---
EAP 6.4 using:
jboss-as-controller-client-7.5.0.Final-redhat-21.jar
jboss-as-protocol-7.5.0.Final-redhat-21.jar
jboss-dmr-1.2.2.Final-redhat-1.jar
jboss-logging-3.1.4.GA-redhat-2.jar
jboss-marshalling-1.4.10.Final-redhat-1.jar
jboss-marshalling-river-1.4.10.Final-redhat-1.jar
jboss-marshalling-river-1.4.10.Final-redhat-1.jar
jboss-remoting-3.3.4.Final-redhat-1.jar
jboss-sasl-1.0.5.Final-redhat-1.jar
jboss-threads-2.1.2.Final-redhat-1.jar
xnio-api-3.0.13.GA-redhat-1.jar
xnio-nio-3.0.13.GA-redhat-1.jar
So obviously there's a bit of a disconnect here. Do you think it's a good idea to update to the jars from eap 6.4? Would they still be able to communicate with all 7.x servers? Or has that not been substantially tested?
was (Author: rob.stryker):
[~brian.stansberry] Sorry for the delay:
Jars JBT is using to communicate with 7.x servers:
jboss-as-controller-client-7.2.0.Final-redhat-4.jar
jboss-as-protocol-7.2.0.Final-redhat-4.jar
jboss-dmr-1.1.6.Final-redhat-1.jar
jboss-logging-3.1.2.GA-redhat-1.jar
jboss-marshalling-1.3.16.GA-redhat-1.jar
jboss-marshalling-river-1.3.16.GA-redhat-1.jar
jboss-remoting-3.2.16.GA.jar
jboss-sasl-1.0.3.Final-redhat-1.jar
jboss-threads-2.1.0.Final-redhat-1.jar
xnio-api-3.0.7.GA-redhat-1.jar
xnio-nio-3.0.7.GA-redhat-1.jar
---
EAP 6.4 using:
jboss-as-controller-client-7.5.0.Final-redhat-21.jar
jboss-as-protocol-7.5.0.Final-redhat-21.jar
jboss-dmr-1.2.2.Final-redhat-1.jar
jboss-logging-3.1.4.GA-redhat-2.jar
jboss-marshalling-1.4.10.Final-redhat-1.jar
jboss-marshalling-river-1.4.10.Final-redhat-1.jar
jboss-marshalling-river-1.4.10.Final-redhat-1.jar
jboss-remoting-3.3.4.Final-redhat-1.jar
jboss-sasl-1.0.5.Final-redhat-1.jar
jboss-threads-2.1.2.Final-redhat-1.jar
xnio-api-3.0.13.GA-redhat-1.jar
xnio-nio-3.0.13.GA-redhat-1.jar
So obviously there's a bit of a disconnect here. Do you think it's a good idea to update to the jars from eap 6.4? Would they still be able to communicate with all 7.x servers? Or has that not been substantially tested?
> Big war deployment via management API gets stuck
> ------------------------------------------------
>
> Key: JBIDE-19641
> URL: https://issues.jboss.org/browse/JBIDE-19641
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
> Attachments: stuck-deploy-eap-jstack-osx.log, stuck-deploy-eap-jstack-rhel.log, stuck-deploy-jstack-osx.log, stuck-deploy-jstack-rhel.log
>
>
> When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through.
> This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19903) Build/test timeout after 5 hours
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19903?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-19903:
--------------------------------------
Assignee: Alexey Kazakov
> Build/test timeout after 5 hours
> --------------------------------
>
> Key: JBIDE-19903
> URL: https://issues.jboss.org/browse/JBIDE-19903
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, cdi-extensions, seam2
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
>
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> {code}
> 03:33:03 Failed tests:
> 03:33:03 ELReferencesQueryParticipantTest.testELReferencesQueryParticipantForType:29 Match not found (file - /numberguess/web/giveup.jspx name - numberGuess)
> 03:33:03 ELReferencesQueryParticipantTest.testELReferencesQueryParticipantForMethod1:44 Match not found (file - /numberguess/web/giveup.jspx name - remainingGuesses)
> 03:33:03 ELReferencesQueryParticipantTest.testELReferencesQueryParticipantForMethod2:59 Match not found (file - /numberguess/web/giveup.jspx name - possibilities)
> 03:33:03
> 03:33:03 Tests run: 86, Failures: 3, Errors: 0, Skipped: 0
> 03:33:03
> 03:33:08 [ERROR] There are test failures.
> {code}
> {code}
> 04:39:42 Running org.jboss.tools.seam.core.test.project.facet.Seam20XFacetTestSuite230
> 04:40:10 Jun 02, 2015 4:40:10 AM org.hibernate.eclipse.HibernatePlugin start
> 04:40:10 INFO: HibernatePlugin Started
> 04:40:55 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:40:55 WARNING: core.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:40:55 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/earNoLibPrj-ejb
> 04:40:56 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/earNoLibPrj
> 04:41:25 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:41:25 WARNING: core.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:41:26 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/earTemplLibPrj-ejb
> 04:41:27 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/earTemplLibPrj
> 04:41:58 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:41:58 WARNING: core.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:41:58 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/earLibPrj-ejb
> 04:41:59 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/earLibPrj
> 04:42:03 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:03 WARNING: openid4java-consumer.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:07 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:07 WARNING: openid4java-consumer.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:07 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/warNoTemplLibPrj
> 04:42:11 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:11 WARNING: openid4java-consumer.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:14 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/warNoLibPrj
> 04:42:26 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:26 WARNING: openid4java-consumer.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:26 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/warTemplLibPrj
> 04:42:53 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:53 WARNING: openid4java-consumer.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:53 Deleting resource /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/work/data/warLibPrj
> 04:42:57 WARNING: commons-digester.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib
> 04:42:57 WARNING: core.jar jar is mentioned in deploy-*.list file but does not exist in /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seam230.core.test/target/requirements/jboss-seam-2.3.0/jboss-seam-2.3.0.Final/lib{code}
> {code}
> 05:02:54 [INFO] --- tycho-pack200b-plugin:0.22.0:pack (pack200-pack) @ org.jboss.tools.seamfp.ui.test ---
> 05:02:54 [INFO] Pack200 packing jar /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/seam/tests/org.jboss.tools.seamfp.ui.test/target/org.jboss.tools.seamfp.ui.test-3.7.0-SNAPSHOT.jar
> 05:02:54 [INFO]
> 05:02:54 [INFO] --- tycho-p2-plugin:0.22.0:p2-metadata (attached-p2-metadata) @ org.jboss.tools.seamfp.ui.test ---
> 05:02:54 [INFO]
> 05:02:54 [INFO] --- tycho-p2-plugin:0.22.0:p2-metadata (p2-metadata) @ org.jboss.tools.seamfp.ui.test ---
> 05:02:54 [INFO]
> 05:02:54 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap) @ org.jboss.tools.seamfp.ui.test ---
> 05:02:56 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-noauth-4.3.0.GA_CP03.zip
> 05:02:56 Build timed out (after 300 minutes). Marking the build as aborted.
> 05:02:56 Terminating xvnc.
> 05:02:57 $ vncserver -kill :43
> 05:03:07 Killing Xvnc process ID 13038
> 05:03:09 Xvnc seems to be deadlocked. Kill the process manually and then re-run
> 05:03:09 /usr/bin/vncserver -kill :43
> 05:03:09 to clean up the socket files.
> 05:03:09 Build was aborted
> 05:03:09 Archiving artifacts
> 05:03:58 Recording test results
> 05:04:15 Description set:
> 05:04:15 Build was marked for publishing on https://hudson.jboss.org/hudson/
> 05:04:16 Notifying upstream projects of job completion
> 05:04:16 Finished: ABORTED
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years