3 Replies Latest reply: Jan 29, 2014 8:11 AM by Chuggans-Oracle RSS

    Error in AIFUtil.callOdiServlet - Error connecting to ODI Servlet

    user13267146

      Hi John & All,

       

      We have EPM 11123 set up on a 2 node Linux cluster using common mount.

       

      The ERPI managed servers in WL domain are as below:

       

      Server A     ErpIntegrator0     6550

       

      Server B     ErpIntegrator1     6551

       

      The oracledi agent is available at

       

      http:// ServerA:6550/ oraclediagent

       

       

       

      Or

       

      http:// ServerB:6551/ oraclediagent

       

      Howver when we run the dataload rule it fails in Export with the below error (In Data management in Workspace) we get the below error:

       

      “CommData.updateWorkflow - END

       

      2014-01-17 12:24:56,438 DEBUG [AIF]: AIFUtil.callOdiServlet - START

       

      2014-01-17 12:24:56,450 FATAL [AIF]: Error in AIFUtil.callOdiServlet - Error connecting to ODI Servlet: url=http://localhost:6551/aif/ODIServlet, class="HPLService", method=loadData, params=[170, u'YXaa0YHQfx8rIJlwC40l9%2BxbO8sEEgKHBWsamkRbZZRoUkatmfYLpfdw2rA%2BI73XtsD9z5AW1vqU9XRlB5WByL03O18g9Yk2TZtc6sgKJG4MzV48jMuIYC7bTiwQ0r6jwWlCRThoPRiy450ScFygchYQG5%2FAHJyZAPzPTDcFlismBoSYiWOl4vk%2Bka5tX45aYjCsHtvVRn8tUvcnsHvRPIBWls2FaHhN3CvY9L0yOhZ8FUFmNNE0ltJ4dgMVh7MyDCVStT8LVBTv5fRIPvOrsWNJhlyvNHNzvyqqN3t677Gw4B%2Fa70TxDJYDb5eb83NZe%2F3GW%2BCKxRsHve6O8JLADO%2B80TIKSrEiLoialbrG%2B6mZApB78sg7h5PwuMZAcFzXxxmnPjDM1KnaK5RRrqddMQXKAxVCg8mhaZtuzFgd3C4AdzsJVGcLM8siaZOLhdjk']”

       

      Traceback”

       

      For some reason it is thinking that ODI is running at localhost:6551.

       

      We tried to manually modify odiagent URL on Data management setup page to one of the two correct URLs as mentioned above. We can check the connection test successful. After this we ran the load, it still looks for "localhost:6551". Then we thought probably after changing the setting we have to restart ErpIntegrator WL managed server. After restart we see the URL defaulting to "http://localhost:6551/oraclediagent".

       

      Not sure how this ODI Servlet URL is getting generated. For sure it is not picking correct server /port combination. Please help on how to resolve this issue.

       

      Regards

       

      vara

        • 1. Re: Error in AIFUtil.callOdiServlet - Error connecting to ODI Servlet
          Chuggans-Oracle

          Hi Vara,

           

          That doesn't look like a problem connecting to the ODI Agent to me at first glance as the context that you're getting in the error is http://localhost:6551/aif not oraclediagent.

           

          Have you got any more information in the context after you see Traceback? Or do you have anything in the logs in user_projects/domains/EPMSystem/servers/ErpIntegrator0/log folder or the user_projects/domains/EPMSystem/servers/ErpIntegrator1/logfolder folder for the other managed server around the same timestamp that you saw the problem? If there are problems I'd usually expect there to be some additional information in the ErpIntegrator0.log or ErpIntegrator1.log in most cases.

           

          Regards

           

          Craig

          • 2. Re: Error in AIFUtil.callOdiServlet - Error connecting to ODI Servlet
            user13267146

            Hi Craig,

            It was actually http://localhost:6551/oraclediagent. The issue got resolved now. In a clustered environment it expects that the ports are same on both the nodes. In our case on one node it was 6550 and on another it was 6551. So in the registry it is updating with the latest port value, that is the port on node2.

             

            Here it is able to interpret localhost to the node that is hosting ErpIntegrator managed server. To test this I kept both the managed servers up (ErpIntegrator0 & ErpIntegrator1), then tried checking the connectivity on Data management page. It didn't succeed. Then stopped ErpIntegrator1, kept ErpIntegrator0 up no luck. Stopped ErpIntegrator0 and Up the ErpIntegrator1. Then with localhost:6551 the ODI agent connectivity works fine.

             

            So I conclude that the port should be same on both nodes. One other finding was if we install a separate standalone ODI agent on the server and try to use that on Data management page it does not work in a clustered env. Where as in a single node setup we can update the host & port of oracledi agent.

             

            Regards

            vara