Win a copy of Microservices Testing (Live Project) this week in the Spring forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

problem with jboss-4.0.3SP1 version

 
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

i've deployed an application successfully with jboss-4.0.3 version.
My client wants to update the jboss version with latest which is
jboss-4.0.3SP1. But deploying of the same ear on jboss-4.0.3SP1 version
is failing. and it is throwing the following application.
But everywhere i made it propertly. Though i commented the cleanupOrders() method in the entire application and again try to deploy that by deleting the ear and tmp,work directories still it's getting the same exception.
Any one of you Please provide the solution for this and i would be thankful to you

it's working absolutely fine on jboss-4.0.3 version.
please find the exception below:
16:27:30,793 INFO [EARDeployer] Init J2EE application: file:/D:/jboss-4.0.3SP1/server/default/deploy/CSL.ear
16:27:46,210 WARN [verifier] EJB spec violation:
Bean : OrderManager
Method : public abstract void cleanupOrders() throws CAppException, RemoteException
Section: 7.11.5
Warning: The methods defined in the remote interface must have a matching method in the bean's class with the same name and same number and types of arguments.

16:27:46,866 ERROR [MainDeployer] Could not create deployment: file:/D:/jboss-4.0.3SP1/server/default/tmp/deploy/tmp42571CSL.ear-contents/CSLEJB.jar
org.jboss.deployment.DeploymentException: Verification of Enterprise Beans failed, see above for error messages.
at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:575)
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:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy24.create(Unknown Source)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:935)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:925)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:789)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
at sun.reflect.GeneratedMethodAccessor49.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:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:319)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:489)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:192)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:203)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:182)


Thanks in advance,
Vasavi.
 
Ranch Hand
Posts: 100
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
check this statement:

Warning: The methods defined in the remote interface must have a matching method in the bean's class with the same name and same number and types of arguments.


when you deploy you new commented out module,make sure you component interface and bean's implemented method is same,commented out in remote interface,then comment bean's same method too,vice versa,or keep both.
and stop the server,deploy and the restart the server.
 
vicky john
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes, I did in all the possible ways. But still it's not working.
If there is any problem in the code, how come it can work on Jboss-4.0.3 and not able to work on jboss-4.0.3SP1.
I commented out the entire method wherever it is applicable.
But still it's showing the same method. I don't know why..
 
Bartender
Posts: 3778
40
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by vasavi vasireddy:
Yes, I did in all the possible ways. But still it's not working.
If there is any problem in the code, how come it can work on Jboss-4.0.3 and not able to work on jboss-4.0.3SP1.
I commented out the entire method wherever it is applicable.
But still it's showing the same method. I don't know why..



Maybe you need to delete some cached files/or undeploy existing application.
 
vicky john
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Atlast we could resolve the problem... ..
the problem is that :
we removed the CSLScheduler.jar and order-ejb-client.jar from lib folder of
jboss4.0.3SP1. In order-ejb-client.jar, the remote and home interface for
OrderManager bean was defined. In EAR also, the remote and home interfaces are defined. JBoss server first lookup in EAR for classpath, then lib folder of the JBoss for any application to deploy. But for Jboss4.0.3SP1, it was picking up the interfaces from the lib folder first, rather than the one defined in the EAR itself. That was reason it was failing and giving the verification of enterprise beans failed error.

The above two jars are related to scheduler and are no longer in use, Since the scheduler is packed into EAR itself. Hence deleted them and application works fine.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic