WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  NamingContext exception while ORB resolve in Websphere

    Posted Tue March 31, 2015 09:52 AM
    Hi,

           I have deployed my application ABC in websphere 8.5.5 and trying to connect data server using CORBA but getting the below exception.

    org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0

        My application ABC is initial implemented in Jboss and using jacorb , i am able to connect, resolve the namecomponent and fetching the data.

       But now i am migrating the same to WebSphere where i am missing something which is giving the below exeption.

       Could anyone please let me know what configuration i am missing in WebSphere.

    Application ABC+Jacorb+Jboss = Working Fine

    Application ABC+IBMORB+Webpshere8.5.5 = some Configuration is missing somewhere and not able to figure it out


    Error :

    Could not resolve name Dataservers 11.22.33.44_A_POA org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0

    **orb.props to websphere:**
    org.omg.CORBA.ORBClass=com.ibm.CORBA.iiop.ORB org.omg.CORBA.ORBSingletonClass=com.ibm.rmi.corba.ORBSingleton jacorb.implname StandardNS  (Suspecting)
    ORBInitRef.NameService corbaloc:iiop:DATASERVER:14888/NameService


    I suspect, no connection is established to dataserver using ORBInitRef.NameService. So, i am getting the above error. I just want to know how to connect the dataserver from Websphere. Let me know if anyone wants more inforamtion


  • 2.  NamingContext exception while ORB resolve in Websphere

    Posted Tue March 31, 2015 10:02 AM
    This is turning me a huge blockage for further deveopment. Please let me know if any body want more data for analaysis..

    General Flow:

    Application ABC --> Javacode (SOAP webservice) --> Business Login --> CORBA layer --> Connect to Dataserver in c++ --> get Dataserver Stub --> Fetch the data.


  • 3.  NamingContext exception while ORB resolve in Websphere

    Posted Tue March 31, 2015 12:25 PM

    This issue occurs only when the port number is incorrect.

    Pls confirm the CORBA port matches with the BOOTSTRAP_ADDRESS of the server.


  • 4.  NamingContext exception while ORB resolve in Websphere

    Posted Wed April 01, 2015 03:52 AM
    Hi Kishore,

    thanks buddy for ur response. Please find the ports in websphere 8.5.5 and suspected debug paramerters in below screesnhot.. I suspect , Websphere is connecting to NameService of its localhost(WAS) and not to the server i have specified like corbaloc:iiop:11.22.33.44:14888/NameService.

    I just want to know, any configuration settings need to be done at websphere to connect to that server and then i can able to lookup that oject as like datasource lookups....

     



  • 5.  NamingContext exception while ORB resolve in Websphere

    Posted Wed April 01, 2015 06:40 PM
    No additional configuration is required on the server

    Pls try by providing the below URL from the code.

    corbaloc:iiop:localhost:2809/NameService 

    Thanks,
    Kishore Kumar Ingersal 


  • 6.  NamingContext exception while ORB resolve in Websphere

    Posted Thu April 02, 2015 01:09 AM

    Hi Kishore,


       Just a doubt. If i try to connect corbaloc:iiop:localhost:2809/NameService , it will connect to locahost of WAS. If i use localhost, i wont get the dataserverstub and finally i cant access the data exists.


        But my context is to connect dataserver located in other machine 11.22.33.44.  i.e.., corbaloc:iiop:11.22.33.44:14888/NameService.


         My main problem is why WAS is not looking outside of its conext for dataserver stub. It seems like , it is ignoring my corbaloc location of dataserver i am passing to WAS. Really trying hard to find the configuration or approach to make WAS look for dataserver corbaloc.


     



  • 7.  NamingContext exception while ORB resolve in Websphere

    Posted Thu April 02, 2015 01:12 AM

    Hi, 


     I have printed the stacktrace and here is below....Last bold letters are part of log and there are inputs to orb.properties file.


    Error in Sysout.log


    Unable to perform operation on method 'login' of webservice 'AAAServices' due to the following reason: Remote exception caught.[00000010004] Details: Could not resolve name IDAservers 11.22.33.44_oohoncho_poa.


    ErrorLog:


    org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0


    at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:95)

    at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve(_NamingContextStub.java:1556)

    at com.ida.services.IdaRepImpl.getObject(IdaRepImpl.java:677)

    at com.ida.services.IdaRepImpl.getRemoteObject(IdaRepImpl.java:727)

    at com.ida.services.IdaRepImpl.getPOAinfo(IdaRepImpl.java:331)

    at com.ida.services.IdaRepImpl.doRemoteMethod(IdaRepImpl.java:554)

    at com.ida.services.IdaRepImpl.getIdmTicket(IdaRepImpl.java:1197)

    at com.ida.services.IdaRepImpl.login(IdaRepImpl.java:841)

    at com.ida.services.IdaRepImpl.(IdaRepImpl.java:146)

    at com.ida.server.impl.SysServicesImpl.login(SysServicesImpl.java:226)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)

    at java.lang.reflect.Method.invoke(Method.java:611)

    at org.apache.axis2.jaxws.server.dispatcher.JavaDispatcher.invokeTargetOperation(JavaDispatcher.java:120)

    at org.apache.axis2.jaxws.server.dispatcher.JavaBeanDispatcher.invoke(JavaBeanDispatcher.java:118)

    at org.apache.axis2.jaxws.server.EndpointController.invoke(EndpointController.java:111)

    at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessageReceiver.java:161)

    at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:212)

    at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)

    at com.ibm.ws.websvcs.transport.http.WASAxis2Servlet.doPost(WASAxis2Servlet.java:1583)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

    at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1230)

    at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:779)

    at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)

    at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)

    at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1071)

    at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:87)

    at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:914)

    at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662)

    at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200)

    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:459)

    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:526)

    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:312)

    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:283)

    at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)

    at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)

    at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)

    at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)

    at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)

    at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)

    at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)

    at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)

    at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)

    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1864)

    org.omg.CORBA.ORBClass=com.ibm.CORBA.iiop.ORB

    org.omg.CORBA.ORBSingletonClass=com.ibm.rmi.corba.ORBSingleton

    ORBInitRef.NameService=corbaloc:iiop:11.22.33.44:14888/NameService

    jacorb.implname=StandardNS


  • 8.  NamingContext exception while ORB resolve in Websphere

    Posted Fri May 15, 2015 05:03 AM
    Hi All,

    Issue got resolved. I have created a new namespace binding using WAS admin console.

    Environment > Naming > Name space bindings >NEW -> CORBA.
     

    Provide the input and lookup from your code as

    InitialContext context = new InitialContext();


    org.omg.CosNaming.NamingContext rootContext = (NamingContext)context.lookup("");

    you will get a context and can use the same for furthur transactions.

    Thank you very much for your responses and feedback.