[
https://issues.apache.org/jira/browse/TRINIDAD-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved TRINIDAD-294.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 1.2.9-core
1.0.9-core
> file upload: UPLOAD_MAX_MEMORY limit
> ------------------------------------
>
> Key: TRINIDAD-294
> URL: https://issues.apache.org/jira/browse/TRINIDAD-294
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.0.1-incubating-core-SNAPSHOT
> Reporter: Jim Graf
> Assignee: Matthias Weßendorf
> Priority: Minor
> Fix For: 1.0.9-core, 1.2.9-core
>
>
> I stumbled across this issue when I changed UPLOAD_MAX_MEMORY to 3G:
> org/apache/myfaces/trinidadinternal/webapp/UploadedFileProcessorImpl.java:
> private long _maxDiskSpace = -1;
> but
> _maxDiskSpace = Integer.parseInt(maxDiskSpace);
> I think this makes more sense:
> _maxDiskSpace = Long.parseLong(maxDiskSpace);
> Occasionally we do need to allow a customer to upload a file greater then the
> 2G limit that the above code implies. I haven't (successfully) converted this
> app over to Trinidad yet and I'm unlikely to get any help from Oracle as I
> don't use jdeveloper and I don't have a contract.
> thanks,
> jim
> ps. obviously _maxMemory should be treated the same way.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
