[JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ]
Kabir Khan commented on JBIDE-19641:
------------------------------------
The problem is a combination of the client heap size and the copies done by the ByteArrayOutputStream when growing and (with a larger heap) when calling toByteArray() in InputStreamEntry.InMemoryEntry.
{code}
@Override
public synchronized int initialize() throws IOException {
final ByteArrayOutputStream os = new ByteArrayOutputStream();
try {
StreamUtils.copyStream(original, os);
} finally {
if(autoClose) {
StreamUtils.safeClose(original);
}
}
data = os.toByteArray();
return data.length;
}
{code}
The simplest fix is to increase the heap size on the client. When I increase the heap to 4GB my 1GB deployment uploads fine. With a heap of 3GB it fails in the toByteArray() method, with a heap of 2GB it fails earlier in the method, when writing to it and it needs to grow. But that probably isn't the best way.
There is also an alternative and unused implementation InputStreamEntry.CachingStreamEntry, which caches the input stream in a temporary file. The protocol seems to need the size, which is why we are doing these initial steps. Switching to that for everything is easy. Switching to it for somethings would require an extra field on InputStreamAttachements or something like that.
Alternatively, if the operation attachment InputStreams are passed in as something implementing both InputStream and InputStreamEntry, AbstractModelControllerClient/createStreamEntries() will not create an additional InputStreamEntry. Thus an implementation for File, which uses the FileInputStream directly and gets the size from the File (removing the need to copy/cache the whole thing) should do the job. So perhaps a factory method for one of those would be nice to have somewhere?
> 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.Beta2
>
> 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)
10 years, 10 months
[JBoss JIRA] (JBIDE-20078) [launchbar] installing into workspace with pre-existing servers yields no matching o.e.remote connection
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-20078:
-----------------------------------
Summary: [launchbar] installing into workspace with pre-existing servers yields no matching o.e.remote connection
Key: JBIDE-20078
URL: https://issues.jboss.org/browse/JBIDE-20078
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.3.0.Beta1
Reporter: Rob Stryker
Steps to reproduce:
1) Create a workspace with 1 (or more) server adapters (of any type)
2) Install jbt launchbar
3) restart workbench
4) Verify server exists
5) Window -> Preferences -> Remote Development/Remote Connections page
6) Expand combo, select Server Adapter
7) Verify some matching o.e.remote exist that match existing server adapters in server view [FAIL]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20077) All the Quickstarts from JBoss Central should be available offline
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-20077:
-----------------------------------
Summary: All the Quickstarts from JBoss Central should be available offline
Key: JBIDE-20077
URL: https://issues.jboss.org/browse/JBIDE-20077
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: project-examples
Affects Versions: 4.3.0.Beta1
Reporter: Fred Bricon
The offline script doesn't currently support the examples returned in JBoss Central (~200+ projects).
It will most likely make the offline script execution time explode, but you gotta do what you gotta do ...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3068) Installer fails to recognize java versions without underscores
by Robert Heise (JIRA)
[ https://issues.jboss.org/browse/JBDS-3068?page=com.atlassian.jira.plugin.... ]
Robert Heise commented on JBDS-3068:
------------------------------------
This is still happening with jboss-devstudio-8.1.0.GA-installer-eap.jar.
> Installer fails to recognize java versions without underscores
> --------------------------------------------------------------
>
> Key: JBDS-3068
> URL: https://issues.jboss.org/browse/JBDS-3068
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 8.0.0.Beta2
> Environment: JBDS 8.0.0.Beta2b B121
> Oracle JDK 1.8.0
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Labels: respin-c
> Fix For: 8.0.0.Beta2
>
> Attachments: java-1.8.0.png
>
>
> This was spotted by Fred: When he tried to install JBDS and selected Oracle JDK 1.8.0, he got: "JBoss Developer Studio does not work with selected version of java."
> !java-1.8.0.png!
> It was on Windows and I managed to reproduced it there, but it is probably not limited to Windows. It works fine with Oracle JDK 1.8.0_05. So the key here is that this is the original 1.8.0 release.
> Fred suspects that this commit broke this:
> https://github.com/jbdevstudio/jbdevstudio-product/commit/080b102d893b801...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months