Return-Path: X-Original-To: apmail-openjpa-users-archive@minotaur.apache.org Delivered-To: apmail-openjpa-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BC5BD17496 for ; Tue, 24 Feb 2015 15:26:39 +0000 (UTC) Received: (qmail 37425 invoked by uid 500); 24 Feb 2015 15:26:39 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 37390 invoked by uid 500); 24 Feb 2015 15:26:39 -0000 Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@openjpa.apache.org Delivered-To: mailing list users@openjpa.apache.org Received: (qmail 37378 invoked by uid 99); 24 Feb 2015 15:26:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Feb 2015 15:26:39 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of l6459852@gmail.com designates 209.85.214.181 as permitted sender) Received: from [209.85.214.181] (HELO mail-ob0-f181.google.com) (209.85.214.181) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Feb 2015 15:26:13 +0000 Received: by mail-ob0-f181.google.com with SMTP id vb8so43840391obc.12 for ; Tue, 24 Feb 2015 07:26:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=FU+awidmmGE/XDXlc6oxAJ2rJXNFevsRI489/V8Fcjg=; b=qY+1+t907pIdLxsph+rjP2P/RykXrpS8Wlw32iUd0BF6FBkKHqMSDk0GJI7pBJ5CbZ uztyZqFBx7hLxbA+3hH/XPlqXzde5A/d2Lu4tlaCcNzPMSNjLPbp9zKc29vWGDNS9Uax Nf+zYwqb/SUKOLtWtZUWg88ZWGp/v2GFWP2lNRhWh42KPEl1Wz9VTYAQD3ZmrPliD8CS XF81fU3Sl8RbhztRtO5EdOwq3nmyi848wyCCvlRjiuNUYvLvUNQ72FNDeECHC1tooWa6 +8MKVsB7s6q4oavsdlY4oz8vJfotl4MoSpc8HOU/fpaC6DbGX9urSFlNRvtEAs0FSbBP EOkw== MIME-Version: 1.0 X-Received: by 10.60.58.65 with SMTP id o1mr11664127oeq.50.1424791571385; Tue, 24 Feb 2015 07:26:11 -0800 (PST) Received: by 10.76.154.74 with HTTP; Tue, 24 Feb 2015 07:26:11 -0800 (PST) In-Reply-To: References: Date: Tue, 24 Feb 2015 12:26:11 -0300 Message-ID: Subject: Re: JPA metadata errors while starting TomEE From: leo ks To: users@openjpa.apache.org Content-Type: multipart/alternative; boundary=089e013d095a7dd39a050fd72361 X-Virus-Checked: Checked by ClamAV on apache.org --089e013d095a7dd39a050fd72361 Content-Type: text/plain; charset=UTF-8 I haven't tried the javaagent instead, I've enhanced them before starting tomee 2015-02-24 11:37 GMT-03:00 Rick Curtis : > and configuring the javaagent fix everything? > > On Mon, Feb 23, 2015 at 7:51 PM, leo ks wrote: > > > I was having strange and random errors complaining of entity mapping > > between entities or unrecognized mapping between entity attributes and > the > > columns in the DB > > > > 2015-02-23 22:42 GMT-03:00 Rick Curtis : > > > > > Can you expand a bit? Were you having problems with > > > openjpa.RuntimeUnenhancedClasses? > > > > > > On Mon, Feb 23, 2015 at 5:52 PM, leo ks wrote: > > > > > > > the enhancer seems to have fixed it :-) > > > > > > > > 2015-02-23 19:17 GMT-03:00 Rick Curtis : > > > > > > > > > What sort of errors are you seeing? > > > > > > > > > > On Mon, Feb 23, 2015 at 1:07 PM, leo ks > wrote: > > > > > > > > > > > ---------- Forwarded message ---------- > > > > > > From: leo ks > > > > > > Date: 2015-02-23 16:05 GMT-03:00 > > > > > > Subject: JPA metadata errors while starting TomEE > > > > > > To: users@tomee.apache.org > > > > > > > > > > > > > > > > > > Hi > > > > > > > > > > > > I am using tomee 1.6.0 and I'm experiencing some strange errors > > > during > > > > > > startup. > > > > > > > > > > > > Sometimes, I get errors from JPA trying to resolve metadata > > > > > > (MetaDataException), sometimes it just starts without any problem > > and > > > > it > > > > > > works OK. > > > > > > > > > > > > I wonder if any process is starting before others (such as MDBs > > > > > processing > > > > > > persistent messages for example). > > > > > > > > > > > > What's the best practice in this situation? > > > > > > > > > > > > Cheers > > > > > > > > > > > > K. > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > *Rick Curtis* > > > > > > > > > > > > > > > > > > > > > -- > > > *Rick Curtis* > > > > > > > > > -- > *Rick Curtis* > --089e013d095a7dd39a050fd72361--