• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Callback Servlet from EJB

 
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
I'm using iPlanet Webserver 6.0 and Weblogic Application Server 6.1. My servlet
(on iPlanet) registers an object with an EJB (on Weblogic)
for callback. Using RMI (java.rmi at all places), the following code works fine
from an application client.

The callback is done successfully when using application client but, when the
same code is used in a servlet and deployed on iPlanet, the weblogic server
prints exception (stack trace attached) and callback doesn't happen. I would
like know how an EJB can callback a servlet other than using JNDI bind and
lookup. Is there a way at all?
I've been trying to solve this problem for a long time now. Any help(or
appropriate material) on this would be appreciated.
Thanks in advance,
CA
===========================================================================
Start server side stack trace:
java.lang.ClassCastException: MyObject
at com.hss.gmlcp.lcshandler.CallbackHandler_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at
weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:133)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy75.handleLocationResponse(Unknown Source)
at
com.hss.gmlcp.lcshandler.test.TestLCSRequestHandlerImpl.submitLocationRequest(TestLCSRequ
estHandlerImpl.java:81)
at
com.hss.gmlcp.lcshandler.test.TestLCSRequestHandlerImpl_exqj34_EOImpl.submitLocationReque
st(TestLCSRequestHandlerImpl_exqj34_EOImpl.java:37)
at
com.hss.gmlcp.lcshandler.test.TestLCSRequestHandlerImpl_exqj34_EOImpl_WLSkel.invoke(Unkno
wn Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic