aspose file tools*
The moose likes JBoss/WildFly and the fly likes Jboss Deployment Error - Verification of Enterprise Beans failed Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "Jboss Deployment Error - Verification of Enterprise Beans failed" Watch "Jboss Deployment Error - Verification of Enterprise Beans failed" New topic
Author

Jboss Deployment Error - Verification of Enterprise Beans failed

Derek Joyce
Greenhorn

Joined: May 12, 2009
Posts: 4
We are trying to migrate an application from WebLogic 8.1 to jBoss 4.0.5. with no previous jBoss experience. We have replaced the weblogic-ejb-jar.xml with jboss.xml and replaced all references to weblogic.jar with jboss-j2ee.jar. The application is built successfully with Ant but we receive the following single error message when we deploy the ear file to jBoss:

2009-05-12 15:13:07,169 ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/C:/jboss-4.0.5.GA/server/default/tmp/deploy/tmp27313DMSApplication.ear-contents/DMSAggregationBatch.jar
org.jboss.deployment.DeploymentException: Verification of Enterprise Beans failed, see above for error messages.
at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:610)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
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.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:74)
at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
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 $Proxy26.create(Unknown Source)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
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 $Proxy8.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.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
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 $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
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 $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:490)
at java.lang.Thread.run(Thread.java:534)

Could anyone point us in the right direction with regard to this error message? It appears quite frequently on internet websites but none of the suggestions have worked.

The following is an example of the jboss.xml that we are using:

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss_2_4.dtd">

<jboss>
<enterprise-beans>
<session>
<ejb-name>AggregationBatch</ejb-name>
<stateless-session-descriptor>
<pool>
<max-beans-in-free-pool>10</max-beans-in-free-pool>
<initial-beans-in-free-pool>2</initial-beans-in-free-pool>
</pool>
</stateless-session-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>AGGREGATION_BATCH_REMOTE</jndi-name>
<local-jndi-name>AGGREGATION_BATCH_LOCAL</local-jndi-name>
</session>
</enterprise-beans>
</jboss>
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10288
    
168

see above for error messages.


What does the console show above this exception stacktrace?

While posting logs or xml content or code, please remember to wrap it in a code block by using the Code button in the message editor window. Please use the Preview button to ensure that your post is correctly formatted.


[My Blog] [JavaRanch Journal]
Derek Joyce
Greenhorn

Joined: May 12, 2009
Posts: 4
The following warning is displayed just above the exception:

2009-05-12 16:37:12,684 DEBUG [org.jboss.ejb.EJBDeployer] create, DMSAggregationBatch.jar
2009-05-12 16:37:12,809 DEBUG [org.jboss.ejb.EJBDeployer] Verifying file:/C:/jboss-4.0.5.GA/server/default/tmp/deploy/tmp38875DMSApplication.ear-contents/DMSAggregationBatch.jar
2009-05-12 16:37:12,856 WARN [org.jboss.ejb.EJBDeployer.verifier] EJB spec violation:
Bean : AggregationBatch
Method : public abstract void runAggregationBatch(BatchProcessDTO) throws DMSAggregationException, RemoteException, Exception
Section: 7.10.7
Warning: The methods in the local interface must not include java.rmi.RemoteException in their throws clause.

This warning originally said that the local interface must include java.rmi.RemoteException in their throws clause so we added 'import java.rmi.RemoteExceptionl;' to the code. This resulted in the above warning. The way the application was built has prevented us from resolving this warning without extensive code changes throughout the application. However as it was a warning we hoped that it was not a fatal stumbling point and could not see a relationship with the error that followed.
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10288
    
168

Derek Joyce wrote:

This warning originally said that the local interface must include java.rmi.RemoteException in their throws clause so we added 'import java.rmi.RemoteException;' to the code.

Are you sure it asked you to add the throws clause for a local interface and not the remote interface?

Derek Joyce wrote:
However as it was a warning we hoped that it was not a fatal stumbling point and could not see a relationship with the error that followed.


You can disable these verifications. In %JBOSS_HOME%/server/< serverName>/deploy/ejb-deployer.xml you can set the StrictVerifier to false:

Derek Joyce
Greenhorn

Joined: May 12, 2009
Posts: 4
Thank you for your response.

My apologies, the warning was about the remote interface:

2009-04-29 12:22:45,240 WARN [org.jboss.ejb.EJBDeployer.verifier] EJB spec violation:
Bean : AggregationBatch
Method : public abstract void runAggregationBatch(BatchProcessDTO) throws DMSAggregationException, Exception
Section: 7.10.5
Warning: The methods in the remote interface must include java.rmi.RemoteException in their throws clause.

I have done as you suggested and the error is no longer appearing, although I do now have numerous individual warnings about ejb spec violations on the remote interface (which hopefully can be ignored ..at least for now!).

Thank you very much for your assistance.
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5845
    
    7

sandy moh,
Your post was moved to a new topic.


JBoss In Action
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Jboss Deployment Error - Verification of Enterprise Beans failed