Nagra CAS Cartridge NE Connection Not Closed On Error (Doc ID 1109964.1)

Last updated on JUNE 14, 2010

Applies to:

Oracle Communications ASAP Cartridges - Version: 1.0.0 and later   [Release: 1.0.0 and later ]
Information in this document applies to any platform.

Symptoms

The Nagra CAS (DTV) cartridge does not seem to recognize NE errors and stays connected in case of an issue with the SMS interface (Nagra RTM). The received exceptions on the asynchronous channel are ignored and the connection stays up. Once the NE becomes fully available again, the cartridge spawns a new NE connection which gets refused by the Nagra NE as the original connection was not closed yet. The desired solution would be that the cartridge recognizes connection issues, shuts down all open connections and re-establishes a new connection.

The work around is to restart the related NEP.

The WL domain log shows the following exception in case of the error:
####<Jun 30, 2009 4:42:45 AM MEST> <Error> <NAGRA_CAS_2_7_6>
<xxxxxxxxxx> <IEpbserver> <Thread-44> <> <>
<000000> <ResponseHandler
::IOEXCEPTION
java.net.SocketException: Socket closed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.DataInputStream.read(DataInputStream.java:224)
at
com.metasolv.cartridge.oss.nagra_cas_2_7_6.prov.ResponseHandler.run(ResponseHandler.java:99)
at java.lang.Thread.run(Thread.java:534)

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