[
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)