[MGNLDATA-86] unable to activate items of given type when no workflow/versioning is used Created: 10/Nov/09  Updated: 15/Sep/15  Resolved: 10/Nov/09

Status: Closed
Project: Magnolia Data Module (closed)
Component/s: None
Affects Version/s: 1.3.2
Fix Version/s: 1.4

Type: Bug Priority: Major
Reporter: Zdenek Skodik Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Any activation after activating types fails with exception like:

      2009-11-10 12:21:52,201 ERROR a.module.admininterface.commands.ActivationCommand: can't activate
      javax.jcr.ItemNotFoundException: 6fb2ac75-1fd3-4ce2-a4c1-9bdcb57cd5eb
      	at org.apache.jackrabbit.core.ItemManager.getItemData(ItemManager.java:306)
      	at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:250)
      	at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:515)
      	at org.apache.jackrabbit.core.SessionImpl.getNodeById(SessionImpl.java:575)
      	at org.apache.jackrabbit.core.SessionImpl.getNodeByUUID(SessionImpl.java:544)
      	at org.apache.jackrabbit.core.SessionImpl.getNodeByUUID(SessionImpl.java:855)
      	at info.magnolia.cms.core.DefaultHierarchyManager.getContentByUUID(DefaultHierarchyManager.java:465)
      	at info.magnolia.module.admininterface.commands.BaseRepositoryCommand.getNode(BaseRepositoryCommand.java:57)
      	at info.magnolia.module.admininterface.commands.ActivationCommand.execute(ActivationCommand.java:83)
      	at info.magnolia.commands.MgnlCommand.executePooledOrSynchronized(MgnlCommand.java:173)
      	at info.magnolia.commands.MgnlCommand.execute(MgnlCommand.java:160)
      	...

The problem is caused by Type activation command not releasing resources properly.



 Comments   
Comment by Zdenek Skodik [ 10/Nov/09 ]

all the mentioned above was tested using simple activation. With XA it's much better, all goes fine, only the last bullet above is valid then.

Comment by Zdenek Skodik [ 10/Nov/09 ]

and the issue described in last bullet disappeared for me only with full 4.2-beta EE - with workflow, versioning and transactional activation.

Comment by Jan Haderka [ 10/Nov/09 ]

That was just a luck since more then one instance of the command have been in the command instance pool. I've managed to reproduce the issue even with the XA activation.

Comment by Michael Mühlebach [ 15/Sep/15 ]

This ticket was closed because former resolved tickets are deemed to be closed now. If this assumption is untrue in this particular case please feel free to reopen the ticket again.

Generated at Mon Feb 12 05:11:13 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.