Win a copy of Murach's Python Programming this week in the Jython/Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

nested javax.naming.NamingException: Failed to unmarshal proxy  RSS feed

 
Ram Pra
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello All,
I have coded two new entity beans for an already existing application and deployed them on to JRun3.1 server. But when I try to access it I get the following exception.But i am able to access the other entity beans from the same client pgm.
com.ltcg.resol.util.ResolException: **Error Failed to unmarshal proxy
----> nested com.ltcg.framework.exception.EJBFactoryException: Failed to unmarshal proxy
----> nested javax.naming.NamingException: Failed to unmarshal proxy [Root exception is java.lang.ClassNotFoundException: com.ltcg.resol.dataaccess.genoffer.resolicited_product_offerHomeObject_Stub (no security manager: RMI class loader disabled)]
at com.ltcg.resol.util.EJBTest.testEntityBeans(EJBTest.java:125)
at com.ltcg.resol.util.EJBTest.main(EJBTest.java:50)
java.lang.RuntimeException: **Error Failed to unmarshal proxy
at com.ltcg.resol.util.EJBTest.testEntityBeans(EJBTest.java:136)
at com.ltcg.resol.util.EJBTest.main(EJBTest.java:50)
Exception in thread "main"

I have no idea why this exception is thrown when the deployment went thru fine and alos i can see the entity bean deployed onto the server. I have verified the deployment descriptor over 100 times. Still I am not able to crack this problem.
If anyone of you are aware of this please reply back asap.
Thanks,
Prashanth pramesh@ltcg.com
 
Ruilin Yang
Ranch Hand
Posts: 150
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You can debug this problem by deploying two beans separately (one bean a time)to see why one works and the other does not.
 
Ram Pra
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't face any problem while deployment. Its only when I access the bean by a sample client program, it throws the exception.
 
Ruilin Yang
Ranch Hand
Posts: 150
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You got error when you tried to access the bean. If you had deployed your bean correctly you would have accessed it with no problem.
In order to debug the problem I suggest you redeploy your beans one bean a time to try to find the problem.
 
Ram Pra
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sorry Yang....The solution you gave did not solve my problem, if you want i can post the deloyment descriptor and the client code, so that you can have a look at it. The exception says that it didn't find the home object stub, but actually when i checked the jars in the deploy directory of the server I did find the home object stubs.
Prashanth
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!