[ 
https://issues.apache.org/jira/browse/TRINIDAD-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420916#comment-13420916
 ] 

Blake Sullivan commented on TRINIDAD-2293:
------------------------------------------

In the HA case you describe, your solution is forcing the HA system to 
replicate file A to the failover server just-in-case.  This is a huge expense 
for a very rare case.  In this case, the user can simply reupload the file.  In 
addition, it isn't clear how the current code doesn't suffer from race 
conditions.

If we are worried about the file A, file B case you describe, the solution is 
to run the lifecycle on file A as soon as it completes.  This also, 
conveniently reduces the resource requirements on the server.

How does this code handle the case where the user starts an upload from more 
than one multifile upload in the same page or separate multifile uploads on 
multiple pages.  It seems like we would get clashes on the session keys.

Also, does the code correctly handle the case where the server crashed while 
writing a temp file to disk?
                
> multi file upload does not get replicated in a High Availability environment
> ----------------------------------------------------------------------------
>
>                 Key: TRINIDAD-2293
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-2293
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions: 2.0.2-core
>         Environment: linux x86
>            Reporter: Kentaro Kinebuchi
>         Attachments: Trinidad-2293.patch
>
>
> In multi file upload, the uploaded files are stored in the user's session 
> before submit. In a HA environment, the session context which is replicated 
> does not contain this file information so if the server goes down then the 
> file data is lost in the replicated server.
> There are two specific issues which need to be handled in the code:
> 1. In WebLogic, unless the setAttribute() method is called on the session 
> context, that attribute is not automatically replicated. Hence, all 
> attributes which are updated during multi file upload and we want replicated 
> have to specifically call that method.
> 2. WebLogic does not replicate all File objects stored in the context. Hence, 
> the path to the temporary file created for each uploaded file needs to be 
> saved in a String in the context so it is replicated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to