Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9EADF10852 for ; Tue, 20 Aug 2013 16:21:00 +0000 (UTC) Received: (qmail 46004 invoked by uid 500); 20 Aug 2013 16:20:59 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 45919 invoked by uid 500); 20 Aug 2013 16:20:54 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 45895 invoked by uid 99); 20 Aug 2013 16:20:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Aug 2013 16:20:52 +0000 Date: Tue, 20 Aug 2013 16:20:51 +0000 (UTC) From: "Kevin Sutter (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (OPENJPA-2399) Oracle JDK 1.7 seems to be causing an issue with OpenJPA MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745096#comment-13745096 ] Kevin Sutter commented on OPENJPA-2399: --------------------------------------- This issue continues to be discussed via the OpenJPA mailing list: The latest post from Garpinc describes the problem, the proper solution, and a workaround... Turns out adding jvm option -XX:+AlwaysLockClassLoader appears to resolve issue. >From http://docs.oracle.com/javase/7/docs/technotes/guides/lang/cl-mt.html It says: Troubleshooting If your product ships and appears to have problems due to incomplete handling of critical sections, you can use a new VM flag -XX:+AlwaysLockClassLoader. This flag reverts to locking the class loader lock before invoking your custom class loader's findClass() or loadClass() method, even for class loaders that register as parallel capable. The correct fix however would be to follow the guidelines in that post. > Oracle JDK 1.7 seems to be causing an issue with OpenJPA > -------------------------------------------------------- > > Key: OPENJPA-2399 > URL: https://issues.apache.org/jira/browse/OPENJPA-2399 > Project: OpenJPA > Issue Type: Bug > Affects Versions: 2.2.0, 2.3.0, 2.2.2 > Reporter: garpinc > > I recently had to upgrade to JDK 1.7 and I'm having > java.lang.LinkageError: loader (instance of sun/misc/Launcher$AppClassLoader): attempted duplicate class definition for name: "org/apache/openjpa/jdbc/identifier/DBIdentifier$DBIdentifierType" > I previously reported this sometime ago here: > http://openjpa.208410.n2.nabble.com/JDK-1-7-seems-to-be-causing-an-issue-with-latest-snapshot-td7581417.html#a7583248 > seems there has been no resolution. I've tried 2.2.0, 2.2.1 and 2.3.0-SNAPSHOT and all have same issue on Oracle JDK 1.7. Can someone please advise? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira