9 Replies Latest reply: Aug 31, 2005 10:22 AM by song jinlong RSS

ex04_2 deployment problem

song jinlong Newbie

19:12:49,907 WARN [verifier] EJB spec violation:
Bean : CabinEJB
Section: 22.2
Warning: The Bean Provider must specify the fully-qualified name of the Java cla
ss that implements the enterprise bean's business methods in the <ejb-class> ele
ment.
Info : Class not found on 'com.titan.cabin.CabinBean': Unexpected error during
load of: com.titan.cabin.CabinBean, msg=com/titan/cabin/CabinBean (Unsupported
major.minor version 49.0)

19:12:49,917 WARN [verifier] EJB spec violation:
Bean : TravelAgentEJB
Section: 22.2
Warning: The Bean Provider must specify the fully-qualified name of the Java cla
ss that implements the enterprise bean's business methods in the <ejb-class> ele
ment.
Info : Class not found on 'com.titan.travelagent.TravelAgentBean': Unexpected
error during load of: com.titan.travelagent.TravelAgentBean, msg=com/titan/trave
lagent/TravelAgentBean (Unsupported major.minor version 49.0)

19:12:49,917 ERROR [MainDeployer] could not create deployment: file:/E:/jboss-4.
0.2/server/default/deploy/titan.jar
org.jboss.deployment.DeploymentException: Verification of Enterprise Beans faile
d, see above for error messages.
at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:553)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:918)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:774)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:121)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:127)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:325)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:501)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:204)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
bstractDeploymentScanner.java:277)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:272)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:222)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:897)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:418)
at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:121)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:127)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:434)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:315)
at org.jboss.Main.boot(Main.java:195)
at org.jboss.Main$1.run(Main.java:463)
at java.lang.Thread.run(Thread.java:536)
19:12:50,057 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=file:/E
:/jboss-4.0.2/server/default/deploy/jmx-console.war/
19:12:50,327 ERROR [URLDeploymentScanner] Incomplete Deployment

any reply reveice my great graduation!

  • 1. Re:  ex04_2 deployment problem
    Darran Lofthouse Master

    Class not found on 'com.titan.cabin.CabinBean':

    This means that JBoss can not find the class specified, this is usually caused by one of the following: -

    1 - The wrong name is specified.
    2 - The class is missing from the jar.
    3 - The jar has not been packaged correctly and the structure is wrong.

    Execute the command 'jar -tf jarname.jar' against the jar and post the output here.

  • 2. Re:  ex04_2 deployment problem
    song jinlong Newbie

    I am gratful to your help,I don't missing which the jar,I think jboss4 has contain these jar files.my jar file only implement sayHello() method. According to your words ,I excute the command,result as follows:

    D:\>jar -tf titan.jar
    META-INF/
    META-INF/MANIFEST.MF
    com/
    com/titan/
    com/titan/cabin/
    com/titan/cabin/CabinBean.class
    com/titan/cabin/CabinHomeRemote.class
    com/titan/cabin/CabinRemote.class
    com/titan/travelagent/
    com/titan/travelagent/TravelAgentBean.class
    com/titan/travelagent/TravelAgentHomeRemote.class
    com/titan/travelagent/TravelAgentRemote.class
    META-INF/ejb-jar.xml
    META-INF/jboss.xml

    whether the structure is wrong?
    thanks.

  • 3. Re:  ex04_2 deployment problem
    song jinlong Newbie

    Can I ask your question?If I write a jboss Ejb project, which jar files I need? which extra jar files I need copy
    to JBOSS_HOME/server/default/deply/?
    thanks

  • 4. Re:  ex04_2 deployment problem
    Darran Lofthouse Master

    Sorry, just looked back at the original post I missed part of the error.

    Yes the structure of the jar is correct, in general you don't need to copy any other jars to the deploy folder, the only real exception to this is if there are components deployed in other archives that you need.

    Anyway back to the original error message, it looks as though you have compiled your component using Java 5 and your JBoss version appears to be running against an earlier JDK version.

  • 5. Re:  ex04_2 deployment problem
    song jinlong Newbie

    Mr. darranl
    firstly,thanks!
    my jboss vesion is 4.0.2.
    my jdk vesion is jdk.4.1
    have you a email?I can't explain why.I send src code to you.I dont know it influence you.
    thank a lot.

  • 6. Re:  ex04_2 deployment problem
    Darran Lofthouse Master

    Are you sure you have not accidentally compiled your bean using Java 5?

    The part of the error that says (Unsupported
    major.minor version 49.0)
    suggests to me that you have.

    Either compile with the same JDK version you are running JBoss with or change the JAVA_HOME so that JBoss runs with Java 5.

  • 7. Re:  ex04_2 deployment problem
    song jinlong Newbie

    Yes?my eclipse's java jre is set jkd1.5 or jkd1.4.1.
    JAVA_HOME is jdk1.4.1.this question appear.

    if my JAVA_HOME set jdk1.5.0 path regardless of my eclipse jre,it is ok!
    maybe jboss4.0 only support java 5.now quesiton is
    sovled.

    thanks! thanks a lot

  • 8. Re:  ex04_2 deployment problem
    Darran Lofthouse Master

    JBoss does suppot both of the JDK versions, the problem is only if you compile your component using a later JDK version to the version JBoss is using.

  • 9. Re:  ex04_2 deployment problem
    song jinlong Newbie

    thanks!thank a lot!