This content has been marked as final.
Show 8 replies
-
1. Re: Deployment exception...
jaikiran Nov 8, 2007 9:53 AM (in response to manwithoutface)Which version of Java did you use to compile your application? Looks like you used a higher version of Java (maybe Java6?) to compile the application and you are deploying it on JBoss which is using a lower version (Java5). Compiling the application using Java5 should solve the issue.
-
2. Re: Deployment exception...
manwithoutface Nov 8, 2007 9:59 AM (in response to manwithoutface)For building I'm using JDK5 (jdk1.5.0_11).
-
3. Re: Deployment exception...
jaikiran Nov 8, 2007 10:09 AM (in response to manwithoutface)Can you post the logs that you see on the console from the point when you start JBoss till you see this exception?
-
4. Re: Deployment exception...
manwithoutface Nov 8, 2007 10:19 AM (in response to manwithoutface)===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\jboss-4.2.2.GA
JAVA: V:\jdk1.5.0_11\\bin\java
JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
CLASSPATH: V:\jdk1.5.0_11\\lib\tools.jar;C:\jboss-4.2.2.GA\bin\run.jar
===============================================================================
18:14:23,948 INFO [Server] Starting JBoss (MX MicroKernel)...
18:14:23,948 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)
18:14:23,948 INFO [Server] Home Dir: C:\jboss-4.2.2.GA
18:14:23,948 INFO [Server] Home URL: file:/C:/jboss-4.2.2.GA/
18:14:23,948 INFO [Server] Patch URL: null
18:14:23,948 INFO [Server] Server Name: default
18:14:23,948 INFO [Server] Server Home Dir: C:\jboss-4.2.2.GA\server\default
18:14:23,948 INFO [Server] Server Home URL: file:/C:/jboss-4.2.2.GA/server/default/
18:14:23,948 INFO [Server] Server Log Dir: C:\jboss-4.2.2.GA\server\default\log
18:14:23,948 INFO [Server] Server Temp Dir: C:\jboss-4.2.2.GA\server\default\tmp
18:14:23,948 INFO [Server] Root Deployment Filename: jboss-service.xml
18:14:24,213 INFO [ServerInfo] Java version: 1.5.0_11,Sun Microsystems Inc.
18:14:24,213 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_11-b03,Sun Microsystems Inc.
18:14:24,213 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
18:14:24,664 INFO [Server] Core system initialized
18:14:27,916 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
18:14:27,916 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
18:14:28,476 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
18:14:28,476 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
18:14:28,725 INFO [TransactionManagerService] Starting recovery manager
18:14:28,881 INFO [TransactionManagerService] Recovery manager started
18:14:28,881 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
18:14:32,009 INFO [EJB3Deployer] Starting java:comp multiplexer
18:14:32,335 INFO [STDOUT] no object for null
18:14:32,351 INFO [STDOUT] no object for null
18:14:32,367 INFO [STDOUT] no object for null
18:14:32,382 INFO [STDOUT] no object for {urn:jboss:bean-deployer}supplyType
18:14:32,398 INFO [STDOUT] no object for {urn:jboss:bean-deployer}dependsType
18:14:34,374 INFO [NativeServerConfig] JBoss Web Services - Native
18:14:34,374 INFO [NativeServerConfig] jbossws-native-2.0.1.SP2 (build=200710210837)
18:14:35,463 INFO [Embedded] Catalina naming disabled
18:14:35,588 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: V:\jdk1.5.0_11\bin;.;C:\WINXP\system32;C:\WINXP;C:\WINXP\system32;C:\WINXP;C:\WINXP\System32\Wbem;C:\Program Files\Intel\DMIX;V:\jdk1.5.0_11\bin;D:\svn\bin\;C:\Program Files\GTK\2.0\bin
18:14:35,961 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
18:14:35,961 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
18:14:35,961 INFO [Catalina] Initialization processed in 512 ms
18:14:35,961 INFO [StandardService] Starting service jboss.web
18:14:35,977 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
18:14:36,023 INFO [Catalina] Server startup in 54 ms
18:14:36,319 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
18:14:36,895 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
18:14:37,190 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/jbossws.sar/jbossws-context.war/
18:14:37,626 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
18:14:38,747 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
18:14:39,416 INFO [MailService] Mail Service bound to java:/Mail
18:14:39,556 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
18:14:39,587 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
18:14:39,649 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
18:14:39,711 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
18:14:39,758 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
18:14:39,805 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
18:14:39,836 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
18:14:39,851 INFO [QuartzResourceAdapter] start quartz!!!
18:14:39,929 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
18:14:39,960 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
18:14:39,960 INFO [RAMJobStore] RAMJobStore initialized.
18:14:39,960 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
18:14:39,960 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
18:14:39,960 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
18:14:40,645 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
18:14:40,878 INFO [A] Bound to JNDI name: queue/A
18:14:40,878 INFO [B] Bound to JNDI name: queue/B
18:14:40,894 INFO [C] Bound to JNDI name: queue/C
18:14:40,894 INFO [D] Bound to JNDI name: queue/D
18:14:40,894 INFO [ex] Bound to JNDI name: queue/ex
18:14:40,910 INFO [testTopic] Bound to JNDI name: topic/testTopic
18:14:40,910 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
18:14:40,910 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
18:14:40,910 INFO [testQueue] Bound to JNDI name: queue/testQueue
18:14:40,956 INFO [UILServerILService] JBossMQ UIL service available at : /127.0.0.1:8093
18:14:40,987 INFO [DLQ] Bound to JNDI name: queue/DLQ
18:14:41,112 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
18:14:41,174 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
18:14:41,563 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
18:14:41,579 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
18:14:41,594 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 17s:646ms
18:16:21,666 ERROR [MainDeployer] Could not create deployment: file:/C:/jboss-4.2.2.GA/server/default/deploy/Migo.war
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 java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.jboss.wsf.container.jboss42.JAXWSDeployerHookPreJSE.getRelevantServlets(JAXWSDeployerHookPreJSE.java:128)
at org.jboss.wsf.container.jboss42.JAXWSDeployerHookPreJSE.isWebServiceDeployment(JAXWSDeployerHookPreJSE.java:101)
at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:87)
at org.jboss.wsf.container.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:79)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy45.create(Unknown Source)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) -
5. Re: Deployment exception...
jaikiran Nov 8, 2007 10:31 AM (in response to manwithoutface)18:14:24,213 INFO [ServerInfo] Java version: 1.5.0_11,Sun Microsystems Inc.
18:14:24,213 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_11-b03,Sun Microsystems Inc.
The server logs looks fine to me. The server is definitely using Java5, just wanted to make sure about this.
How do you compile your application? Do you use an IDE or Ant? From the place where you compile your application what's the output of the following:java -version
-
6. Re: Deployment exception...
manwithoutface Nov 8, 2007 10:40 AM (in response to manwithoutface)C:\Documents and Settings\*top secret username*>java -version
java version "1.5.0_11"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode)
I'm using Ant in IDE Eclipse Europe. -
7. Re: Deployment exception...
jaikiran Nov 8, 2007 10:56 AM (in response to manwithoutface)"ManWithoutFace" wrote:
I'm using Ant in IDE Eclipse Europe.
Are you sure Eclipse/Ant is not using a different JDK version for compiling your classes? The output you posted looks fine to me as long as the same version of java is being used by Eclipse/Ant to compile your classes. I suspect Eclipse might be using a different version.
I dont have Eclipse open in front of me right now, but if i remember correctly, the Project -> Java Compiler -> Compiler Compliance level gives you an option of specifying the version of Java you want your compiled files to be compliant with. Set it to Java version 5. I believe Ant uses these properties along with the JDK set in Eclipse Workspace->Preference settings to compile the classes.
Let us know how it goes. -
8. Re: Deployment exception...
manwithoutface Nov 8, 2007 12:42 PM (in response to manwithoutface)In all settings of Eclipse set Java version 5.0...
----------------------------------------------------------
You are don't believe me, but I'm make restart of PC and deployment complete. All good!
Thanks from Russia! :)