NullPointerException when Redeploying Application (Doc ID 1390640.1)

Last updated on MARCH 23, 2012

Applies to:

Oracle Communications Converged Application Server - Version: 5.0.0 and later   [Release: 5.0 and later ]
Information in this document applies to any platform.

Symptoms


Following exception is received when redeploying the application:


<Error> <WLSS.Engine> <BUSCO000LKVB19C>
 <AdminServer> <[ACTIVE] ExecuteThread: '16' for queue:
 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1309450306172>
 <BEA-330001> <Unexpected exception
 com.bea.wcp.sip.engine.server.SetupException: [WLSS.Engine:330027]Failed to
 initialize "Ticket" servlet class com.vz.sc.test.unittest.ticket.SCSipServlet
 java.lang.NullPointerException: the input id should not be null
 at
 com.bea.wcp.sip.engine.AdapterUtils.checkParameterNotNull(AdapterUtils.java:198)
 at
 com.bea.wcp.sip.engine.SipSessionsUtilAdapter.getApplicationSessionById(SipSes
 sionsUtilAdapter.java:129)
 at
 com.vendor.dialogic.javax.media.mscontrol.DlgcProxy.getProxySAS(DlgcProxy.java :88)
 at
 com.vendor.dialogic.javax.media.mscontrol.DlgcMediaSessionProxy.createMediaGroup(DlgcMediaSessionProxy.java:97)
 at
com.vendor.dialogic.javax.media.mscontrol.DlgcMediaSessionProxy.createMediaGroup(DlgcMediaSessionProxy.java:85)
 at com.vz.sc.test.unittest.ticket.SCSipServlet.init(SCSipServlet.java:32) at javax.servlet.GenericServlet.init(GenericServlet.java:241)
 at
 com.bea.wcp.sip.engine.server.CanaryServlet$PrivilegedInitAction.run(CanaryServlet.java:853)
Truncated. See log file for complete stack trace.

Dialogic's JSR309 media server connector is used in the example. Overall flow is:


1. The application after getting the factory calls createMediaSession method.

2. Inside the createMediaSession, a DlgcMediaSession is created;however, for serialization purposes   a unique application session is created for the given session. To do that,  the WorkManager is used to schedule a task. Inside the task an application session is created and the application proxyId is saved in the DlgcMediaSession.

3. This proxyId is later used during creation of other “Proxy” JSR309 components etc.


Following are the steps to reproduce the problem:


1) Start the OCCAS container.
2) Send in a call to the app.
3) Hangup the call ( the app does not send 200 okay, so call doesn't complete successfuly)
4) Redeploy app by going into admin console and updating the deployment.
5) Send in a 2nd call. You should get the exception thrown in the logs.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms