[MAGNOLIA-2695] Activation fails for nodes with long names when name is longer then max filename length of underlying file system Created: 21/Apr/09 Updated: 21/Jul/16 Resolved: 27/Apr/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation |
| Affects Version/s: | 4.0.1, 3.6.5 |
| Fix Version/s: | 4.1, 3.6.6, 4.0.2 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Manfred Stock | Assignee: | Jan Haderka |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OpenJDK 1.6.0 on CentOS 5.3 64bit with ext3 filesystem, Magnolia OnAir 4.0.1 |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
We've got a case where we automatically generate node names that can become longer than about 220 characters. This seems to be no problem in the author instance, but the activation of such a node fails with the exception shown in attached stacktrace. One can reproduce the issue in the JCR browser of the author instance by creating e.g. a datafolder with a name that is at least 221 characters long. A subsequent activation will fail. The problem seems to be that some temporary file names that get created in BaseSyndicatorImpl contain the node name, but there is no check which ensures that the complete filename is shorter than the maximum of 255 characters supported by most filesystems. |
| Comments |
| Comment by Jan Haderka [ 27/Apr/09 ] |
|
Done as of r24531 on trunk and as of r24534 on 3.6 branch and as of r24535 on 4.0 branch. |