Skip to main content
summaryrefslogtreecommitdiffstats
blob: fcf9d2c0a748e7727d109bbe6eb4912814a8c222 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
/*
 * Copyright (c) 2004-2013 Eike Stepper (Berlin, Germany) and others.
 * All rights reserved. This program and the accompanying materials
 * are made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at
 * http://www.eclipse.org/legal/epl-v10.html
 *
 * Contributors:
 *    Eike Stepper - initial API and implementation
 */
package org.eclipse.emf.cdo.util;

import org.eclipse.emf.cdo.CDOObject;
import org.eclipse.emf.cdo.transaction.CDOAutoLocker;

/**
 * A {@link ConcurrentAccessException concurrent access exception} that indicates that the repository can not acquire optimistic locks for some of the locally modified objects.
 * <p>
 * It's usually possible and adequate to attempt to commit the transaction again (optimistic strategy).
 * Pessimistic {@link CDOObject#cdoWriteLock() locks} can help to avoid the problematic situation (see also {@link CDOAutoLocker}) at commit time.
 * <p>
 * The optimistic locking timeout can be configured on the server side:
 *
 * <pre>
    &lt;property name="optimisticLockingTimeout" value="10000"/>
 * </pre>
 *
 * @author Eike Stepper
 * @since 4.2
 * @noextend This interface is not intended to be extended by clients.
 * @noinstantiate This class is not intended to be instantiated by clients.
 */
public class OptimisticLockingException extends ConcurrentAccessException
{
  private static final long serialVersionUID = 1L;

  public OptimisticLockingException(String message)
  {
    super(message);
  }
}

Back to the top