Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Thu, 16 Feb 2012 00:52:59 +0000 (UTC)
From: "Kathey Marsden (Updated) (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1512378452.44155.1329353579592.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <698878097.4237.1316735246146.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DERBY-5429) With mixed jar versions the error
 java.lang.NoSuchMethodError:
 org/apache/derby/iapi/services/info/JVMInfo.javaDump()  can occur because
 JVMInfo is in both derby.jar and derbyclient.jar
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-5429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden updated DERBY-5429:
----------------------------------

    Affects Version/s: 10.8.2.2
    
> With mixed jar versions the error java.lang.NoSuchMethodError: org/apache/derby/iapi/services/info/JVMInfo.javaDump()  can occur because JVMInfo is in both derby.jar and derbyclient.jar
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5429
>                 URL: https://issues.apache.org/jira/browse/DERBY-5429
>             Project: Derby
>          Issue Type: Bug
>          Components: Services
>    Affects Versions: 10.8.2.2
>            Reporter: Kathey Marsden
>
> The class org.apache.derby.iapi.services.info.JVMInfo is in both derbyclient.jar and derby.jar.  This means that if an older version of derbyclient.jar  is  in the classpath before  derby.jar the following error can occur when a javaDump is triggered.
>  java.lang.NoSuchMethodError: org/apache/derby/iapi/services/info/JVMInfo.javaDump()V
> 	at org.apache.derby.iapi.services.context.ContextManager.cleanupOnError(Unknown Source)
> 	at org.apache.derby.impl.jdbc.TransactionResourceImpl.cleanupOnError(Unknown Source)
> 	at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
> 	at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source)
> 	at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
> 	at org.apache.derby.jdbc.EmbeddedDriver.connect(Unknown Source)
> 	at org.apache.derby.impl.drda.Database.makeConnection(Unknown Source)
> 	at org.apache.derby.impl.drda.DRDAConnThread.getConnFromDatabaseName(Unknown Source)
> 	at org.apache.derby.impl.drda.DRDAConnThread.verifyUserIdPassword(Unknown Source)
> 	at org.apache.derby.impl.drda.DRDAConnThread.parseSECCHK(Unknown Source)
> 	at org.apache.derby.impl.drda.DRDAConnThread.parseDRDAConnection(Unknown Source)
> 	at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown Source)
> 	at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
> This was discovered running a 10.5.3.2 - (1171883) client (derbclient.jar and derbyTesting.jar)  against a  10.8.2.1 - (1170221) server (derby.jar and derbynet.jar) with the derbyclient.jar first in the classpath.
> The test that failed was testConnectShutdownAuthentication, but 
>  but this should be reproducible by reducing  derby.stream.error.extendedDiagSeverityLevel=0 and generating any error. Probably client needs its own separate JVMInfo class. I am not sure where it is used. Maybe it s

--
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