My Oracle Support Banner

DIH Connectors Screen Fail to Load / Open with 'java.lang.NullPointerException: null' (Doc ID 2647069.1)

Last updated on MARCH 16, 2020

Applies to:

Oracle Financial Services Data Integration Hub - Version 8.0.6 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)

Symptoms

In Oracle Financial Services Data Integration Hub (DIH) 8.0.x, for an environment with Weblogic, the Connectors screen is not opening.  It shows the progress bar continuously.  Also, the connectors are not listed on the Publish/Unpublish screen.

The following error exists in the web layer DIH.log:

[20-02-20 09:38:47 AM] ~ INFO ~ DIHLOGGER ~ [SummaryDAO][getObjectFromDb]Fetching Summary Data
[20-02-20 09:38:47 AM] ~ ERROR ~ DIHLOGGER ~ [SummaryDAO][getObjectFromDb]null
java.lang.NullPointerException: null
       at com.ofss.fsgbu.dihapp.dao.SummaryDAO.getConnectorSummary(SummaryDAO.java:123) [dih-app.jar:8.0.6.0.0_10150147718792]
       at com.ofss.fsgbu.dihapp.dao.SummaryDAO.getObjectFromDb(SummaryDAO.java:45) [dih-app.jar:8.0.6.0.0_10150147718792]
       at com.ofss.fsgbu.dihapp.client.SummaryServiceClient.getObject(SummaryServiceClient.java:34) [dih-app.jar:8.0.6.0.0_10150147718792]
       at com.ofss.fsgbu.dihapp.servlet.DIHServletHelper.invokeActions(DIHServletHelper.java:51) [dih-app.jar:8.0.6.0.0_10150147718792]
       at com.ofss.fsgbu.dihapp.servlet.DIHServlet.doGet(DIHServlet.java:19) [dih-app.jar:8.0.6.0.0_10150147718792]
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) [javax.servlet.javax.servlet-api.jar:3.1.0]
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [javax.servlet.javax.servlet-api.jar:3.1.0]
       etc.

Also, the following error exists in the web layer FUSIONSUBSYSTEMSService.log:

[20-02-20 09:43:25,405 GMT AM] [ERROR] [WEB] [AMHM] [NA] [CONNECTIONS]
javax.naming.NameNotFoundException: Unable to resolve 'jdbc.<INFODOM>'. Resolved 'jdbc'; remaining name '<INFODOM>'
       at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1292)
       at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:354)
       at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:222)
       at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
       at weblogic.jndi.internal.ServerNamingNode.lookup(ServerNamingNode.java:521)
       at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:228)
       at weblogic.jndi.internal.ServerNamingNode.lookup(ServerNamingNode.java:521)
       at weblogic.jndi.internal.RootNamingNode.lookup(RootNamingNode.java:84)
       at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:307)
       at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:434)
       at javax.naming.InitialContext.lookup(InitialContext.java:417)
       etc.

As a result of this issue, you cannot access the connectors to transfer data.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.