當application的jdk版本與服務器的jdk版本不一致下,常會出現bad version number異常消息。而這個問題的避免,咱們能夠在網上搜羅信息,能夠經過IDE設置complie level,來保證編譯class的級別。這裏很少說。 java
今天,我遇到的問題,也是bad version number的錯誤。可是我已經設置好了complie level,卻依舊出現這樣的問題。這個問題,並非在服務器啓動時出現,而是由於我訪問某個類的時候,出現如此問題。那麼,如此證實了問題也不是我自身代碼編譯的問題(由於有能運行class)。 web
因而,我找到了代碼的錯誤日誌信息,發現如此:
apache
20131105 17:08:20 com.pdager.enavi.wap.web.impl.RedirectExceptionResolver - server error! java.lang.UnsupportedClassVersionError: Bad version number in .class file at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1876) at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:889) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1353) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1232) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:164) at org.hibernate.connection.C3P0ConnectionProvider.configure(C3P0ConnectionProvider.java:92) at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:124) at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:56) at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:410) at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:62) at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2009) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1292) at com.autonavi.data.persister.PersistenceFacade.<clinit>(PersistenceFacade.java:26) at com.autonavi.data.dao.LuckyHistoryDao.queryByCodeAndMdn(LuckyHistoryDao.java:36) at com.pdager.enavi.wap.servlet.DefaultQueryServlet.handlePost(DefaultQueryServlet.java:46) at com.pdager.enavi.wap.web.impl.ActiveHandler.handle(ActiveHandler.java:30) at com.pdager.enavi.wap.web.DispatcherServlet.service(DispatcherServlet.java:155) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:875) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at java.lang.Thread.run(Thread.java:595)
後來,通過查看Hibernate.jar和c3p0.jar的編譯版本,均沒有問題。但是,在我查看jdbc-driver.jar的時候,發現了問題,它的編譯級別爲1.6。至此,問題解決。 tomcat
注:
1. bad number version的錯誤緣由:在低版本的jdk下,運行高版本的jdk編譯class
2. 不要懷疑本身,應該根據程序的提示,順藤摸瓜,由於程序不說謊! 服務器