• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Ejbs exception while invocation on Websphere

 
Sunny Jigyasu
Greenhorn
Posts: 2
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
posted Today 15:31:50
Hi,

Websphere throws following exception while invoking ejbs although the deployment is correct and could be seen in the jndi tree with the proper jndi name.
The same thing works when I manually deploy the ear through admin console which should have happened automatically during server startup. Why is this manual intervention needed ?Am I missing something?
at com.ibm.ws.naming.jndicos.CNContextImpl.mapINV_OBJREF(CNContextImpl.java:4594) ~[com.ibm.ws.runtime.jar:na]
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1835) ~[com.ibm.ws.runtime.jar:na]
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1776) ~[com.ibm.ws.runtime.jar:na]
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1433) ~[com.ibm.ws.runtime.jar:na]
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:615) ~[com.ibm.ws.runtime.jar:na]
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:165) ~[com.ibm.ws.runtime.jar:na]
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179) ~[com.ibm.ws.runtime.jar:na]
at org.apache.aries.jndi.DelegateContext.lookup(DelegateContext.java:161) ~[na:na]
at javax.naming.InitialContext.lookup(InitialContext.java:422) ~[na:1.7.0]
at com.amdocs.aif.j2ee.AbstractJ2eeConnector$GenericCreateEjbHome.run(AbstractJ2eeConnector.java:155) ~[AmdocsAif-9.0.0.ed04_hf02.jar:na]
... 44 common frames omitted
Caused by: org.omg.CORBA.INV_OBJREF:
>> SERVER (id=3e57aca3, host=illin580) TRACE START:
>> org.omg.CORBA.INV_OBJREF: Could not resolve IOR string. vmcid: 0x0 minor code: 0 completed: No
>> at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.resolveUnresolvedBinding(WsnOptimizedNamingImpl.java:2007)
>> at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.resolve_binding(WsnOptimizedNamingImpl.java:1663)
>> at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.do_resolve_complete_info(WsnOptimizedNamingImpl.java:603)
>> at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete_info(WsnOptimizedNamingImplBase.java:2169)
>> at com.ibm.WsnOptimizedNaming._NamingContextImplBase._invoke(_NamingContextImplBase.java:286)
>> at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:669)
>> at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:523)
>> at com.ibm.rmi.iiop.ORB.process(ORB.java:523)
>> at com.ibm.CORBA.iiop.ORB.process(ORB.java:1575)
>> at com.ibm.rmi.iiop.Connection.doRequestWork(Connection.java:2992)
>> at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2875)
>> at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:64)
>> at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)
>> at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1783)
>> SERVER (id=3e57aca3, host=illin580) TRACE END.
 
Mamnun Ahmed
Greenhorn
Posts: 1
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Try changing EJB module version to 2.1 through project facets. Somewhere your java version and EJB version is mismatching.
 
Don't get me started about those stupid light bulbs.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic