Java CLC fails to extract large files v10_1_0_1128

[rzsmith@nhbc.co.uk]

We are getting failed extraction runs from the Java CLC and seek assistance in overcoming this.

Our methodology is to prepare a release directory in SGV then to do a 'getr' on that directory. However we are finding that larger files are failing on extraction and truncated. We have not ascertained the exact size threshold for this but today's release successfully copied out a 2097152 byte module but failed with the largest one at 4861952 bytes. Multiple attempts at extraction with the java CLC all failed and just extracted 2440866 bytes before failure - does this imply the threshold is somewhere between 2440866 and 2097152?

Manual extraction using the windows SGV client for the larger file consistently worked without problems.

An example failing command:

Code: Select all

/app/sgv10/vaultJavaCLC/vault GET -makewritable -merge automatic -verbose -host SVR-SGV01 -user reluser -password *redacted*  -repository "NHBC IT Source Control"  -nonworkingfolder "/tmp/steve/" "$/fusion/Implementation/Releases/fusion REGR/CHG0046059.0/"

Code: Select all

The error message:
log4j:WARN No appenders could be found for logger (com.cdesg.jni.natives.NativeLoader).
log4j:WARN Please initialize the log4j system properly.
<vault>
  <error>
    <exception>java.lang.ArrayIndexOutOfBoundsException: -1
        at system.ClrUInt8Array.getValue(ClrUInt8Array.jvm.cs:24)
        at system.Text.UTF8Encoding.Fallback(UTF8Encoding.cs:994)
        at system.Text.UTF8Encoding.InternalGetChars(UTF8Encoding.cs:1252)
        at system.Text.UTF8Encoding$UTF8Decoder.GetChars(UTF8Encoding.cs:1463)
        at system.IO.StreamReader.ReadBuffer(StreamReader.cs:358)
        at system.IO.StreamReader.Read(StreamReader.cs:402)
        at system.IO.TextReader.ReadBlock(TextReader.cs:100)
        at VaultClientOperationsLib.OperationsMisc.FileCopyChangeEOL(Unknown Source)
        at VaultClientOperationsLib.ClientInstance.ProcessFile_NonWorkingFolder(Unknown Source)
        at VaultClientOperationsLib.ClientInstance.ProcessGetFileRequests(Unknown Source)
        at VaultClientOperationsLib.ClientInstance.GetToNonWorkingFolder(Unknown Source)
        at VaultClientOperationsLib.ClientInstance.GetToNonWorkingFolder(Unknown Source)
        at VaultClientIntegrationLib.GetOperations.ProcessCommandGetToLocationOutsideWorkingFolder(GetOperations.cs:333)
        at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Unknown Source)
        at VaultCmdLineClient.VaultCmdLineClient.$Main$(Unknown Source)
        at VaultCmdLineClient.VaultCmdLineClient.main(Unknown Source)
</exception>
  </error>
  <result>
    <success>False</success>
  </result>

[Tonya]

Hello,

Would you mind to send over your Vault Server server log from %windir%\temp\sgvault\sgvault.log to "support at sourcegear.com" with a link to this forum thread?

Perhaps the log file will provide us with additional details.

Thanks,

Tonya

[rzsmith@nhbc.co.uk]

Server log mailed to support as requested.

For info the relevant lines are *only* those for the "reluser" connections as all othere will be from Windows clients not the CLC automation. This line in that log looks suspicious to me ...

"---04/01/2022 15:36:27 reluser--ovmdba01.nhbc.ad(10.137.0.78)--SSL Disabled Login
----04/01/2022 15:36:37 reluser--ovmdba01.nhbc.ad(10.137.0.78)--SSL Disabled Logout
----04/01/2022 15:36:38 reluser--ovmdba01.nhbc.ad(10.137.0.78)--SSL Disabled System.Web.HttpException (0x800703E3): The remote host closed the connection. The error code is 0x800703E3.
at VaultServiceSQL.VaultSqlSCC.GetDeltaChainForFullFile(VaultSqlConn conn, Int64 nObjVerID, Int32 nBufSize, String strFileToken, Stream stream, ListDictionary ldDataStreams, RunningCRC32 crc, UInt32& nCRC) at VaultServiceSQL.VaultSqlSCC.GetDeltaChainForFullFile(VaultSqlConn conn, Int64 nObjVerID, Int32 nBufSize, String strFileToken, Stream stream, ListDictionary ldDataStreams, RunningCRC32 crc, UInt32& nCRC)
"

[Tonya]

Thank you for the Vault Server log. I replied in the support ticket (#258177).

Tonya