Win a copy of Rust Web Development this week in the Other Languages 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:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Liutauras Vilda
  • Jeanne Boyarsky
Sheriffs:
  • Junilu Lacar
  • Rob Spoor
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Tim Moores
  • Jesse Silverman
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Piet Souris
  • Frits Walraven

UnmarshalException

 
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
I am attempting to have a Stateless Session EJB running on a Weblogic 6.1 managed server call a method on a Stateless Session EJB running on a Weblogic 6.1 Admin server (I know we probably should not run code there but that is a story for another post.) Both beans are deployed in EAR files. The managed EJB EAR contains the remote and home interfaces for the admin EJB in its JAR file.
Everything works fine until an application exception is thrown by the admin EJB at which point I get the following exception on the managed server:
----------------------------------------------------------
Exception in <method_name> is java.rmi.UnmarshalException: Problem finding error class;
nested exception is:
java.lang.ClassNotFoundException: S3Exception: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that cluster
----------------------------------------------------------
The class is question (S3Exception) is contained in the managed EJB jar file and therefore should be loaded in the EJB classloader. I have noticed if I place the class in question (S3Exception) in the managed servers system classpath then this problem disappears however that is not an acceptable solution.
Any ideas as to how I fix this would be greatly appreciated.
Thanks...
Steve
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic