Long Filenames (More Than 101 Characters) Lead to Server Crash (Doc ID 1386574.1)

Last updated on JULY 11, 2016

Applies to:

Oracle Agile Engineering Data Management - Version 6.1.1.0 and later
Information in this document applies to any platform.

Symptoms

On Oracle Agile EDM 6.1.1
Find that checkout of files with long names (more than 101 characters including extension) ends up in a server crash. Additionally, if the file is attached to an office document it cannot be viewed through the office document mask any more - the server is also crashing.
The viewing of the file through the "All documents" mask (or through other document type masks) works correctly, however.

Expected Behavior:
--------------------
The repository allows a file name length of 255 characters (T_FILE_DAT.ORG_NAME). The application should be able to work with that file name length without issues!


The issue can be reproduced at will with the following steps:
-------------------------------------------------------------
1. Create a file that has a file name with more than 101 characters (including extension). Use a file extension that is known in EDM: Manager | External Applications (for example: .doc or .docx)
2. Check in the file with an office document
3. Open that document in the office document mask and select from context menu either File Functions | View or File Functions | Check Out (or the appropriate button)
=> The file is checked out still but then the server crashes (Error message in the Java Client: Connection to host <hostname> lost!)
4. Double checking: Restart the application and load that document into the "All documents" mask
5. Press button "Load document into integrated viewer" => No crash appears and the document can be viewed
6. Open the Files tab and select the file with the long file name
7. Press either the button "Read only copy of file" or "Reserve document and check out file"
=> Again the file is checked out but then the server crashes
8. If the file should be checked in after a restart with button "Update file and unreserve document" it ends up in a server crash, too. However, the file is checked in first.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms