![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
5.1 |
|
Assignee:
|
Unassigned |
|
Created:
|
06/Jan/14 1:08 PM
|
|
Description:
|
In info.magnolia.module.exchangesimple.BaseSyndicatorImpl.transportActivatedData(ActivationContent, URLConnection, String), a timestamp of current author time is gathered, and later on sent to public instances together with the activation request. The activation request is then refused by the public instance if the public's current time diverges from this author timestamp by more than 30s, presumably in order to verify author and public clocks are in sync.
Unfortunately, the timestamp on author is created before the temporary file with activation data is created in Transporter.transport(). Given a recursive activation with huge amounts of binary data (multiple GB) plus some load on author and public, these 30s can too easily be exceeded.
The timestamp on author should be created as shortly as possible before the actual sending of the activation HTTP request. Otherwise, the clock sync check will fail when creating the temp file takes longer than 30s, which probably isn't desired.
|
|
Fix Versions:
|
5.2.x |
|
Project:
|
Magnolia Activation Module
|
|
Labels:
|
maintenance
support
|
|
Priority:
|
![Neutral]() Neutral
|
|
Reporter:
|
Joerg von Frantzius
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <
[email protected]>
----------------------------------------------------------------
