[MGNLACTIVATION-138] Activation fails with nodes with very long names (above 200 chars) Created: 21/Jul/16  Updated: 28/Nov/16  Resolved: 25/Nov/16

Status: Closed
Project: Activation
Component/s: None
Affects Version/s: None
Fix Version/s: 5.4.5, 5.5.1

Type: Bug Priority: Major
Reporter: Edwin Guilbert Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OSX El Capitan 10.11.5 using HFS (journaled) as filesystem
java version "1.7.0_67"


Attachments: Text File FilenameTooLong.log    
Issue Links:
Relates
relates to MAGNOLIA-2695 Activation fails for nodes with long ... Closed
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:
Sprint: Kromeriz 72
Story Points: 3

 Description   

Trying to activate a page with a name longer than 225 (on my current system) throws the following exception:

info.magnolia.cms.exchange.ExchangeException: java.io.IOException: File name too long

Caused by:

java.io.File.createTempFile(File.java:2040)
at info.magnolia.module.activation.ResourceCollector.exportAndParse(ResourceCollector.java:218)

Full stack trace attached (magnolia 5.3.15).



 Comments   
Comment by Edwin Guilbert [ 21/Jul/16 ]

This issue was once fixed but reverted back years ago.

Generated at Sun Feb 11 23:00:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.