Very large meaning how large ? > 2tb ?
What os are the appserver and client ?
About 50GB and App Server sits on RHEL 6x and Client is Windows 7.
X86? X64 ?
Why do you have a 50gb package ?
x64 and this package is from a BSA User. I didn't build it. I was just Exporting/Importing for them. Looks like they are packaging some BPM Process Center software from IBM.
it would be helpful to get the full stack trace of the error message and if there are any messages on the appserver side. something could have cut off the connection during the upload or there could be some issue handling a file that large. imo though if you have a 50gb package you are doing it wrong
Bill Robinson wrote:
imo though if you have a 50gb package you are doing it wrong
Haha, "go big or go home" doesn't always apply in the IT world.
we are also getting this error, but we are trying to add oracle 11g R2 in depot which is approx 2 GB.
is there any limit for the depot objects to add?
can we configure the size limit for depot objects?
Hi Bill Sorry for this delayed reply. Customer and I never got back on this particular package to move it over. I believe they put this one to the side for now. I will see if i can get some additional logs for further details. By the way I agree 50GB is pretty big for a BLPackage. I'll keep this thread alive for Aryan.
I'm back on this export/import I'm working with customer again and still getting same error.
Only thing in the logs on the app server is that basically outputs the same error.
[03 Jun 2014 09:23:45,250] [Client-Connections-Thread-8] [DEBUG] [E003114@dt.inc:BLAdmins:192.168.9.51] [Client] java.io.EOFException: Unexpected end of ZLIB input stream
com.bladelogic.om.infra.mfw.util.BlException: java.io.EOFException: Unexpected end of ZLIB input stream
Caused by: java.io.EOFException: Unexpected end of ZLIB input stream
The software customer is packaging up is BPM process Center DE.
Does the Zipper.java have a size limit ?
Best practice to package up something on this size level?
Any additional assistance is appreciated.
Thanks.....I went back to the customer and just explained we'll just need to find a different approach to this particular BLPackage.
Typically on very large files my customers will run a get command or something similar first, which copies the binary from some repository to the target. Then a follow up command to do the installation.
Although this is somewhat older - the cause seems to be related to this one:
(I just came over this during export/import in an 8.2 environment - exactly 8.2.02.321, which has Java version 1.6.0_24-B07)