[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ] Brian Stansberry edited comment on JBIDE-19641 at 6/3/15 8:48 AM: ------------------------------------------------------------------ Just an FYI, I mentioned on the mail thread that the code path for the CLI and what JBIDE is using is the same once it reaches the point where the bits are being pushed to the server (which is where things are stuck.) But it turns out that's not the case; the management op the CLI uses is different. The CLI actually reads the entire file into memory, Base64 encodes it and sends it to server as a param to the management op. That's really not ideal, as the memory requirements on the client and the server can be really high. The ServerDeploymentManager stuff JBIDE is using results in sending the bytes out of band to the server. That's a better approach but there may be a problem there. But to say more I'll need to try out the versions your using. was (Author: brian.stansberry): Just an FYI, I mentioned on the mail thread that the code path for the CLI and what JBIDE is using is the same once it reaches the point where the bits are being pushed to the server (which is where things are stuck.) But it turns out that's not the case; the management op the CLI uses is different. -- This message was sent by Atlassian JIRA (v6.3.15#6346)