Configure Connection Attributes and Recieve java.lang.NullPointerException Error
(Doc ID 1489513.1)
Last updated on JUNE 05, 2023
Applies to:
Oracle Communications MetaSolv Solution - Version 6.2.1 and laterInformation in this document applies to any platform.
Symptoms
After the 6.2.1 upgrade for all VPN orders created before the upgrade where there is no circuit id yet, going into Configure Product and accessing any Connection Attributes page and trying to click Next Connection or Done causes a null pointer exception error. This appears to be because in 6.0.15 the serv_item_desc column in the serv_item table was null until a circuit id was generated for an item. In 6.2.1 a value is populated there from serv item creation. If no value is found there when going into Connection Attributes it throws a null pointer exception.
java.lang.NullPointerException at
com.mslv.core.api.internal.PSR.importData.ConnectionServiceItem.getSiDescript
ion(ConnectionServiceItem.java:1885) at
com.mslv.core.api.internal.PSR.importData.ServiceItem.update(ServiceItem.java
:1030) at
com.mslv.core.api.internal.PSR.importData.ConnectionServiceItem.update(Connec
tionServiceItem.java:903) at
com.mslv.ejb.PSR.modifier.UpdateConnectionServItemModifier.initiateModificati
on(UpdateConnectionServItemModifier.java:60) at
com.mslv.ejb.MSLVSessionBean.initiateModification(MSLVSessionBean.java:773)
at
com.mslv.ejb.PSR.NgnOrderingBean.updateConnectionOnOrder(NgnOrderingBean.java
:801) at
com.mslv.ejb.PSR.NgnOrdering_d0fbgw_EOImpl.updateConnectionOnOrder(NgnOrderin
g_d0fbgw_EOImpl.java:4033) at
com.mslv.ejb.PSR.NgnOrdering_d0fbgw_EOImpl_CBV.updateConnectionOnOrder(Unknow
n Source) at
com.mslv.ejb.PSR.NgnOrderingHandler.updateConnectionOnOrder(NgnOrderingHandle
r.java:738) at
com.mslv.webapp.psr.data.ConnectionAttributesData.updateConnectionOnOrder(Con
nectionAttributesData.java:119) at
com.mslv.webapp.psr.action.PostConnectionAttributes.execute(PostConnectionAtt
ributes.java:163) at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcess
or.java:484) at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSec
urityHelper.java:227) at
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper
.java:125) at
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(We
bAppServletContext.java:3504) at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject
.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown
Source) at
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletCo
ntext.java:2186) at
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.j
ava:2092) at
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406
) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at
weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
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 |
| References |