openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Curtis <curti...@gmail.com>
Subject Re: [jira] [Commented] (OPENJPA-2139) OpenJPA fails to recover from a broken database on startup
Date Mon, 27 Feb 2012 16:24:40 GMT
I was referring to the exception that resulted in this message :
"openjpa.Runtime: Warn: An error occurred while registering a
ClassTransformer with..... "

On Mon, Feb 27, 2012 at 9:24 AM, Albert Lee <allee8285@gmail.com> wrote:

> Exception data: <openjpa-1.2.3-SNAPSHOT-r422266:1053401 nonfatal user
> error> org.apache.openjpa.persistence.ArgumentException: An error occurred
> while parsing the query filter "SELECT b from AuditLogon b WHERE
> b.sessionId = :sessionId". Error message: The name "AuditLogon" is not a
> recognized entity or identifier. Known entity names: []
>         at
>
> org.apache.openjpa.kernel.exps.AbstractExpressionBuilder.parseException(AbstractExpressionBuilder.java:118)
>        at
>
> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getClassMetaData(JPQLExpressionBuilder.java:180)
>        at
>
> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.resolveClassMetaData(JPQLExpressionBuilder.java:150)
>        at
>
> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getCandidateMetaData(JPQLExpressionBuilder.java:225)
>        at
>
> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getCandidateMetaData(JPQLExpressionBuilder.java:195)
>        at
>
> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getCandidateType(JPQLExpressionBuilder.java:188)
>        at
>
> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.access$600(JPQLExpressionBuilder.java:69)
>        at
>
> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder$ParsedJPQL.populate(JPQLExpressionBuilder.java:1756)
>        at
> org.apache.openjpa.kernel.jpql.JPQLParser.populate(JPQLParser.java:56)
>        at
>
> org.apache.openjpa.kernel.ExpressionStoreQuery.populateFromCompilation(ExpressionStoreQuery.java:156)
>        at
> org.apache.openjpa.kernel.QueryImpl.newCompilation(QueryImpl.java:658)
>        at
>
> org.apache.openjpa.kernel.QueryImpl.compilationFromCache(QueryImpl.java:639)
>        at
>
> org.apache.openjpa.kernel.QueryImpl.compileForCompilation(QueryImpl.java:605)
>        at
> org.apache.openjpa.kernel.QueryImpl.compileForExecutor(QueryImpl.java:667)
>        at org.apache.openjpa.kernel.QueryImpl.compile(QueryImpl.java:574)
>  ....
>
>
> On Mon, Feb 27, 2012 at 8:14 AM, Rick Curtis (Commented) (JIRA) <
> jira@apache.org> wrote:
>
> >
> >    [
> >
> https://issues.apache.org/jira/browse/OPENJPA-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217198#comment-13217198
> ]
> >
> > Rick Curtis commented on OPENJPA-2139:
> > --------------------------------------
> >
> > Albert -
> >
> > In the case that you mentioned, do you know what/where the exception is
> > that we encounter?
> >
> > > OpenJPA fails to recover from a broken database on startup
> > > ----------------------------------------------------------
> > >
> > >                 Key: OPENJPA-2139
> > >                 URL:
> https://issues.apache.org/jira/browse/OPENJPA-2139
> > >             Project: OpenJPA
> > >          Issue Type: Bug
> > >    Affects Versions: 2.2.0
> > >            Reporter: Mark Struberg
> > >            Assignee: Mark Struberg
> > >            Priority: Critical
> > >             Fix For: 2.3.0
> > >
> > >         Attachments: OPENJPA-2139.mdr.patch, OPENJPA-2139.patch
> > >
> > >
> > > The following scenario:
> > > 1.) turn off the database
> > > 2.) perform a query against the database
> > > 3.) turn on the database
> > > 4.) try to re-run the query from 2.)
> > > In 4.) you will get the following Exception:
> > > openjpa-2.2.0-r422266:1244990 nonfatal user error>
> > org.apache.openjpa.persistence.ArgumentException: An error occurred while
> > parsing the query filter "SELECT k FROM DbEnumKey AS k where k.type=:typ
> > ORDER BY k.ordinal". Error message: The name "DbEnumKey" is not a
> > recognized entity or identifier. Known entity names: []
> > > Basically the whole app is stale afterwards!
> > > Solution: caching the entities might only be done if a connection can
> be
> > established.
> >
> > --
> > This message is automatically generated by JIRA.
> > If you think it was sent incorrectly, please contact your JIRA
> > administrators:
> > https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> > For more information on JIRA, see:
> http://www.atlassian.com/software/jira
> >
> >
> >
>
>
> --
> Albert Lee.
>



-- 
*Rick Curtis*

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message