[MGNLUI-1702] Stacktrace when uploading asset to root Created: 18/Jun/13  Updated: 18/Jun/13  Resolved: 18/Jun/13

Status: Closed
Project: Magnolia UI
Component/s: app framework
Affects Version/s: 5.0
Fix Version/s: 5.0

Type: Bug Priority: Neutral
Reporter: Mikaël Geljić Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: detail-sub-app, upload
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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: RC 2

 Description   
2013-06-17 17:11:54,460 WARN  info.magnolia.ui.contentapp.detail.DetailSubApp : Could not determine if parent node still exists
javax.jcr.RepositoryException: Invalid path:
        at org.apache.jackrabbit.core.session.Session...Operation.perform(SessionItemOperation.java:194)
        at org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
        at org.apache.jackrabbit.core.SessionImpl.perform(SessionImpl.java:361)
        at org.apache.jackrabbit.core.SessionImpl.nodeExists(SessionImpl.java:1138)
        at info.magnolia.jcr.wrapper.DelegateSessionWrapper.nodeExists(DelegateSessionWrapper.java:274)
        at info.magnolia.jcr.wrapper.DelegateSessionWrapper.nodeExists(DelegateSessionWrapper.java:274)
        at info.magnolia.jcr.wrapper.DelegateSessionWrapper.nodeExists(DelegateSessionWrapper.java:274)
        at info.magnolia.jcr.decoration...onWrapper.nodeExists(ContentDecoratorSessionWrapper.java:115)
        at info.magnolia.ui.contentapp.detail.DetailSubApp$1.onContentChanged(DetailSubApp.java:173)


 Comments   
Comment by Jozef Chocholacek [ 18/Jun/13 ]

The asset is uploaded and it is possible to work with it, so the issue is just that log message.

Generated at Mon Feb 12 08:49:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.