• 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:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

weblogic.ejbc - EJB Deployment

 
Ranch Hand
Posts: 50
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The problem is-
when I am creating the Ejb.jar through using the weblogic.ejbc and deploying this jar into the weblogic6.1 server, I am getting the error - "Assertion Failed".
I will recompile this Ejb.jar , then it will deploy this Ejb jar.
When I extracted these jar, I found the defference in these jar files.
What could be the reason for this Error during the Deployment of the EJB jar ???
[ December 29, 2002: Message edited by: Vikalp Singh ]
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
As far as I can tell, this has nothing to do with Web Services -- I'm moving this to the WebLogic forum.
Kyle
 
Ranch Hand
Posts: 2713
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Typically you should never see an Assertion Error.
Can you show the full error? It usually says:

Check to make sure there are no "stale" versions of your class on the classpath when compiling or deploying your EJB. This could cause an Assertion Error in some cases.
You mentioned that there are differences between the two generated jars... what are those differences?
I am leaning towards the "stale" class theory but other than that, I can't help unless I know more about the problem.
 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
i encountered this before and it's because the particular EJB that causes assertion error is not declared in the weblogic-ejb-jar.xml. Try checking the file.
 
Vikalp Singh
Ranch Hand
Posts: 50
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for Response

This is the Full Error
--------------------------------------------------
####<Jan 30, 2003 5:07:15 PM GMT> <Error> <J2EE> <ukebouasw01> <camuServer> <main> <system> <> <160001> <Error deploying application TaxOpsAuthBeanOut:
Unable to deploy EJB: TaxOpsAuthEJB from TaxOpsAuthBeanOut.jar:
java.lang.ClassNotFoundException: com.iflex.camu.securities.taxopsauth.TaxOpsAuthBean_8v3o8e_HomeImpl
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:180)
at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:304)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.getHomeClass(ClientDrivenBeanInfoImpl.java:352)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:793)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
at weblogic.j2ee.Application.addComponent(Application.java:170)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy0.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
-------------------------------------------------
One More thing i am getting this error only in case of when i am compiling the jar's with all other jars of the application.
 
Vikalp Singh
Ranch Hand
Posts: 50
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
can any body give the proper reason for this.
and how to solve this problem.. this is urgent for me.
-
Vikalp
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
try deleting the contents of the dir

C:\domains\<app name>\<node>\.wlnotdelete\EJBCompilerCache

could be there are non compatible classes here that are not recompiled.

this can be a problem when switching ejb-compilers
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic