You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (Resolved) (JIRA)" <ji...@apache.org> on 2012/04/18 19:54:39 UTC
[jira] [Resolved] (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
[ https://issues.apache.org/jira/browse/DERBY-5429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden resolved DERBY-5429.
-----------------------------------
Resolution: Fixed
Fix Version/s: 10.8.2.2
10.9.0.0
This is resolved with the Fix for DERBY-1046. Note moving forward , the community decided not to continue to support mixed jar versions in the same class loader context.
> 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
> Fix For: 10.9.0.0, 10.8.2.2
>
>
> 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