|
| Re: [CDO] Not Active: Transaction # [message #757945 is a reply to message #757944] |
Wed, 16 November 2011 07:04   |
|
Am 15.11.2011 21:17, schrieb Christophe Bouhier:
> Hi,
>
> What makes a transaction lifecycle go inactive, like in the exception below? In my case, I keep transactions open for
> UI views. When activating the viewpart, the selection is used to update commands etc.. Here an object parent is
> retrieved resulting in this exception.
>
> Is this a timeout of the transaction, or is this because of something else?
No, neither transactions nor views or sessions have timeouts. They can be actively deactivated with the close() methods
or passively if the network IConnector, the IChannel or IProtocol get deactivated. To find out why/when they get
deactivated you can add a LifecycleEventAdater to any of these concepts (ideally your transaction) and set a breakpoint
in onDeactivated() or onAboutToDeactivate().
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
>
> thx Christophe
>
> !ENTRY org.eclipse.ui.workbench 4 0 2011-11-15 21:05:29.017
> !MESSAGE Not active: Transaction 26
> !STACK 0
> java.lang.IllegalStateException: Not active: Transaction 26
> at org.eclipse.net4j.util.lifecycle.LifecycleUtil.checkActive(LifecycleUtil.java:72)
> at org.eclipse.net4j.util.lifecycle.Lifecycle.checkActive(Lifecycle.java:190)
> at org.eclipse.emf.internal.cdo.view.AbstractCDOView.getStore(AbstractCDOView.java:176)
> at org.eclipse.emf.internal.cdo.CDOObjectImpl.cdoStore(CDOObjectImpl.java:1022)
> at org.eclipse.emf.internal.cdo.CDOObjectImpl.eInternalContainer(CDOObjectImpl.java:584)
> at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eContainer(BasicEObjectImpl.java:771)
> at org.eclipse.emf.edit.provider.ItemProviderAdapter.getParent(ItemProviderAdapter.java:636)
> at org.eclipse.emf.edit.domain.AdapterFactoryEditingDomain.getParent(AdapterFactoryEditingDomain.java:624)
> at org.eclipse.emf.edit.domain.AdapterFactoryEditingDomain.createCommand(AdapterFactoryEditingDomain.java:491)
> at
> com.netxforge.netxstudio.screens.editing.ScreensAdapterFactoryEditingDomain.createCommand(ScreensAdapterFactoryEditingDomain.java:84)
> at org.eclipse.emf.edit.command.RemoveCommand.create(RemoveCommand.java:99)
> at org.eclipse.emf.edit.command.RemoveCommand.create(RemoveCommand.java:91)
> at com.netxforge.netxstudio.screens.editing.actions.WarningDeleteCommand.prepareCommand(WarningDeleteCommand.java:91)
> at com.netxforge.netxstudio.screens.editing.actions.WarningDeleteCommand.prepare(WarningDeleteCommand.java:86)
> at org.eclipse.emf.common.command.AbstractCommand.canExecute(AbstractCommand.java:114)
> at org.eclipse.emf.edit.ui.action.CommandActionHandler.updateSelection(CommandActionHandler.java:105)
> at com.netxforge.netxstudio.screens.editing.actions.EditingActionsHandler.update(EditingActionsHandler.java:277)
> at
> com.netxforge.netxstudio.screens.editing.actions.EditingActionsHandler.propertyChanged(EditingActionsHandler.java:320)
> at org.eclipse.ui.part.WorkbenchPart.firePropertyChange(WorkbenchPart.java:129)
> at com.netxforge.netxstudio.screens.editing.AbstractScreensViewPart.access$0(AbstractScreensViewPart.java:1)
> at com.netxforge.netxstudio.screens.editing.AbstractScreensViewPart$1$1.run(AbstractScreensViewPart.java:351)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
| Re: [CDO] Not Active: Transaction # [message #757946 is a reply to message #757945] |
Wed, 16 November 2011 08:44 |
 Christophe Bouhier
Messages: 937
Registered: July 2009 |
Senior Member |
|
|
Many thanks Eike, I will do as you advise.
rgds Christophe
On 16-11-11 08:04, Eike Stepper wrote:
> Am 15.11.2011 21:17, schrieb Christophe Bouhier:
>> Hi,
>>
>> What makes a transaction lifecycle go inactive, like in the exception
>> below? In my case, I keep transactions open for UI views. When
>> activating the viewpart, the selection is used to update commands
>> etc.. Here an object parent is retrieved resulting in this exception.
>>
>> Is this a timeout of the transaction, or is this because of something
>> else?
> No, neither transactions nor views or sessions have timeouts. They can
> be actively deactivated with the close() methods or passively if the
> network IConnector, the IChannel or IProtocol get deactivated. To find
> out why/when they get deactivated you can add a LifecycleEventAdater to
> any of these concepts (ideally your transaction) and set a breakpoint in
> onDeactivated() or onAboutToDeactivate().
>
> Cheers
> /Eike
>
> ----
> http://www.esc-net.de
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
>
>
>>
>> thx Christophe
>>
>> !ENTRY org.eclipse.ui.workbench 4 0 2011-11-15 21:05:29.017
>> !MESSAGE Not active: Transaction 26
>> !STACK 0
>> java.lang.IllegalStateException: Not active: Transaction 26
>> at
>> org.eclipse.net4j.util.lifecycle.LifecycleUtil.checkActive(LifecycleUtil.java:72)
>>
>> at
>> org.eclipse.net4j.util.lifecycle.Lifecycle.checkActive(Lifecycle.java:190)
>>
>> at
>> org.eclipse.emf.internal.cdo.view.AbstractCDOView.getStore(AbstractCDOView.java:176)
>>
>> at
>> org.eclipse.emf.internal.cdo.CDOObjectImpl.cdoStore(CDOObjectImpl.java:1022)
>>
>> at
>> org.eclipse.emf.internal.cdo.CDOObjectImpl.eInternalContainer(CDOObjectImpl.java:584)
>>
>> at
>> org.eclipse.emf.ecore.impl.BasicEObjectImpl.eContainer(BasicEObjectImpl.java:771)
>>
>> at
>> org.eclipse.emf.edit.provider.ItemProviderAdapter.getParent(ItemProviderAdapter.java:636)
>>
>> at
>> org.eclipse.emf.edit.domain.AdapterFactoryEditingDomain.getParent(AdapterFactoryEditingDomain.java:624)
>>
>> at
>> org.eclipse.emf.edit.domain.AdapterFactoryEditingDomain.createCommand(AdapterFactoryEditingDomain.java:491)
>>
>> at
>> com.netxforge.netxstudio.screens.editing.ScreensAdapterFactoryEditingDomain.createCommand(ScreensAdapterFactoryEditingDomain.java:84)
>>
>> at
>> org.eclipse.emf.edit.command.RemoveCommand.create(RemoveCommand.java:99)
>> at
>> org.eclipse.emf.edit.command.RemoveCommand.create(RemoveCommand.java:91)
>> at
>> com.netxforge.netxstudio.screens.editing.actions.WarningDeleteCommand.prepareCommand(WarningDeleteCommand.java:91)
>>
>> at
>> com.netxforge.netxstudio.screens.editing.actions.WarningDeleteCommand.prepare(WarningDeleteCommand.java:86)
>>
>> at
>> org.eclipse.emf.common.command.AbstractCommand.canExecute(AbstractCommand.java:114)
>>
>> at
>> org.eclipse.emf.edit.ui.action.CommandActionHandler.updateSelection(CommandActionHandler.java:105)
>>
>> at
>> com.netxforge.netxstudio.screens.editing.actions.EditingActionsHandler.update(EditingActionsHandler.java:277)
>>
>> at
>> com.netxforge.netxstudio.screens.editing.actions.EditingActionsHandler.propertyChanged(EditingActionsHandler.java:320)
>>
>> at
>> org.eclipse.ui.part.WorkbenchPart.firePropertyChange(WorkbenchPart.java:129)
>>
>> at
>> com.netxforge.netxstudio.screens.editing.AbstractScreensViewPart.access$0(AbstractScreensViewPart.java:1)
>>
>> at
>> com.netxforge.netxstudio.screens.editing.AbstractScreensViewPart$1$1.run(AbstractScreensViewPart.java:351)
>>
>> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
>> at
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
>>
|
|
|
Powered by
FUDForum. Page generated in 0.01858 seconds
] 
Search
Help
Register
Login
Home
