OPENJPA-366 - Add message text to InternalException.

git-svn-id: https://svn.apache.org/repos/asf/openjpa/branches/1.0.x@581609 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Albert Lee 2007-10-03 14:11:27 +00:00
parent cc2b032223
commit 89744de0b9
2 changed files with 6 additions and 2 deletions

View File

@ -1733,7 +1733,7 @@ public class BrokerImpl
detachAllInternal(null); detachAllInternal(null);
} }
if (_operationCount < 1) if (_operationCount < 1)
throw new InternalException(); throw new InternalException(_loc.get("multi-threaded-access"));
return _operationCount == 1; return _operationCount == 1;
} catch (OpenJPAException ke) { } catch (OpenJPAException ke) {
throw ke; throw ke;

View File

@ -374,4 +374,8 @@ provided via an initializer or by calling the setter method. You either need \
to remove the @GeneratedValue annotation or modify the code to remove the \ to remove the @GeneratedValue annotation or modify the code to remove the \
initializer processing. initializer processing.
invalid-tran-status: The transaction was not in a valid state ({0}) to \ invalid-tran-status: The transaction was not in a valid state ({0}) to \
accept the "{1}" method invocation. Processing will continue. accept the "{1}" method invocation. Processing will continue.
multi-threaded-access: Multiple concurrent threads attempted to access a \
single broker. By default brokers are not thread safe, if you require \
and/or intent a broker to be accessed by more then one thread, set the \
openjpa.Multithreaded property to true to override the default behavior.