Check-in of large file (more than 2GB) in RTC
Hi,
I am trying to check-in large files in RTC. Each file is more than 2GB. Everytime I get the error while check-in and deliver and it fails at 26%.
Following is the error
Error during upload
Failed to upload File /ModelException/Data Imports/ESG/3 - ESG Main.a.igy
CRJAZ1247I The request to the server failed. The server returned the http error 500 with error text "Internal Server Error". Examine any further details here or look in the server log files for more information on how to resolve the issue.
To fix this I did increase the "Jazz Repository Connection timeout" to 9999 seconds (That's the maximum). Also I added preferences.properties files in ~\.jazz-scm folder and have setup repository.timeout to 60000 sec.
But it's still failing. Any idea if I need to change any other settings?
Thanks,
Vaijayanti
I am trying to check-in large files in RTC. Each file is more than 2GB. Everytime I get the error while check-in and deliver and it fails at 26%.
Following is the error
Error during upload
Failed to upload File /ModelException/Data Imports/ESG/3 - ESG Main.a.igy
CRJAZ1247I The request to the server failed. The server returned the http error 500 with error text "Internal Server Error". Examine any further details here or look in the server log files for more information on how to resolve the issue.
To fix this I did increase the "Jazz Repository Connection timeout" to 9999 seconds (That's the maximum). Also I added preferences.properties files in ~\.jazz-scm folder and have setup repository.timeout to 60000 sec.
But it's still failing. Any idea if I need to change any other settings?
Thanks,
Vaijayanti
3 answers
AND if you are running Websphere as the front server, make sure to configure it into Synchronous transport mode, else you can get cases where large files will overwhelm the JVM heap, and crash the app server.
our users are over remote links from the server.. rtc->websphere is 1gig speed, websphere to user is <1meg speed.
we crashed the server once a month for about 6 months randomly til IBM found all this data in a heap dump.
do NOT put large binaries into the source control system. put them in Asset Manager or Artifactory or ANY PLACE outside the source system.
our users are over remote links from the server.. rtc->websphere is 1gig speed, websphere to user is <1meg speed.
we crashed the server once a month for about 6 months randomly til IBM found all this data in a heap dump.
do NOT put large binaries into the source control system. put them in Asset Manager or Artifactory or ANY PLACE outside the source system.
There's also the case that there were space issues on the server itself. We had this happen yesterday on a server whose scm temporary location was in the "root" directory and that file system became full while a delivery was being made. We created a separate file system for the temporary files.
I agree with not putting large binaries in SCM (of any type), what we may disagree upon is the precise definition of "large" :-D
Kevin
I agree with not putting large binaries in SCM (of any type), what we may disagree upon is the precise definition of "large" :-D
Kevin
Comments
