# Release Notes

# Gatekeeper 4.1 Known and Resolved Issues

## Resolved Issues in Gatekeeper 4.1

.

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR372355 | Non-ASCII values for sendName in SMS and Binary SMS sendSMS result in garbled data. Values for this parameter must be ASCII per the SMPP standard. | 4.0 | 4.1
CR372834 | The MLP Simulator in Platform Test Environment will parse longitude/latitude incorrectly when the locale is not English. Switch locale to English | 4.0 | 4.1
CR365666 | Installing the Windows version using the installer does not work if the installer file is in the root directory of the disk. Remove the installer file from root and place in a sub-folder. | 4.0 | Closed
CR366737 | Some Gatekeeper DB tables specify primary keys and/or indexes that exceed the maximum key length for MySQL with MyISAM table type and UTF-8 character type. Either: If you are using the MyISAM engine, set the character type to latin1 or Use the InnoDB engine with UTF-8 or latin1 character set | 4.0 | 4.1
CR370718 | Return values from methods on the Store are not size limited. This can cause out-of-memory errors if the dataset is very large. Make sure your queries don’t fetch the entire key/entry/value set from stores | 4.0 | 4.1
CR372233 | Warnings are thrown even when the silent installer is run successfully. These warnings have no impact on functionality. | 4.0 | 4.1
CR372323 | An IllegalArgumentException can be thrown when retrieving MMS message details in the Platform Test Environment. This usually does not affect the outcome of the operation. | 4.0 | 4.1
CR372242 | Gatekeeper can create new connections to the database when all the connections in the pool are in use. This can cause lock contention. Make sure that the database is configured with an adequate value for `MaximumCapacity`. | 4.0 | 4.1
CR372847 | The Statistics Service createWeeklyReport operation fails to retrieve a value which the report requires, which causes the operation to fail. | 4.0 | 4.1
CR346962 | If the address of the MLP server is changed using OAM, the plug-in does not try to connect to the new server immediately. Instead it waits for the heartbeat interval before trying to connect. | 3.0MP1 | 4.1
CR310647 | During startup, there is a warning that no appenders can be found for loggers. The messages occur in the brief period of time when classes try to log messages before log4j has been initialized. They do not indicate a problem. | 3.0 | Closed

## Known Issues in Gatekeeper 4.1

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
CR384334 | If you stop one AT server and one NT server in a multi-cluster domain and then restart only the AT server, application-initiated requests sent to that server may result in the following error with the message: “Failed to invoke end component <component name>”. In the reverse case, network-triggered requests may fail. Dependent on Oracle WebLogic Server CR384639. Make sure you start both servers. Contact Oracle support for a patch on this issue. | 4.1 |
CR384442 | On the first start-up after domain configuration, if 2 or more NT servers are started at the same time, the servers may throw LDAP exception. An equivalent failure may occur on deploying applications. Restart the servers. If the problem persists, start one server first, and then the others Retry deploying the application. If the problem persists, redeploy the application when the servers are not running. | 4.1 |
CR384688 | Before geo-redundancy is set up, you may sometimes get null pointer exception in geo-storage module. This is benign and may be ignored. | 4.1 |
CR384693 | Setting `StatisticsServiceMbean::StoreInterval` to 0 can produce negative data in the transactions field of the `slee_statistics_data` table. Don’t set StoreInterval to 0 | 4.1 |
CR384696 | When OCSG is first used, the database is initialized. If two NT servers are started up at the same time, they may both try to initialize the database, causing a Service Deployment Exception and one server failing to start up. Make sure the servers are started one at a time. Restart the failed server. | 4.1 |
CR384729 | Some Diameter requests may be dropped during patching, redeployment, or upgrade of the CDR to Diameter module. Check the database for the time period during which the transition took place. All CDRs are stored in the database. | 4.1 |
CR384771 | If the credit control interceptor fails to connect to the Diameter server, the `isConnected` attribute will show incorrect state. Run traffic to check whether the interceptor is connected. | 4.1 |
CR384818 | The Native SMPP Communication Service does not support hitless upgrades. Upgrades cannot be performed without traffic service interruption. Perform a rolling upgrade instead. | 4.1 |
CR384822 | The Parlay X 2.1Short Messaging/SMPP plug-in does not support in-production upgrade after upgrading from 4.0. Before you do a rolling upgrade to the servers, undeploy the EAR file for this communication service. After all upgrades are complete, redeploy the EAR. This does not affect fresh installations of 4.1.
Note: | A mandatory patch will be released to correct this error. Please contact your Oracle service representative about acquiring this patch when it comes out.
| 4.1 |
CR384839 | The Plug-in Manager reports that plugin_sms_smpp state is connected even when it is not. Use the ActiveStatus attribute of the SMPP MBean to check connection status | 4.1 |
CR384863 | When running the Legacy SMPP communication service, you may receive the following exception from your NT servers. `ERROR com.bea.wlcp.wlng.legacy.smpp.connector.SmppChannelProcessor - Could not find request for received response` This exception can be ignored. | 4.1 |
CR384497 | Due to incompatible class changes to the stored blob data, old application data (notifications, etc.) in SIP call notification and presence plug-ins will NOT be usable after the upgrade. Exceptions will be thrown during the upgrade when the old application data is accessed. Contact Oracle support for migration scripts. | 4.1 |
CR384759 | There is an error in the data migration scripts that causes the old SP SLA not to be changed. Necessary script updates can be found in “Upgrading Oracle Communications Services Gatekeeper” in Installation Guide, a separate document in this set. | 4.1 |
CR371114 | PRM service provider users and operator users can not be given access to a restricted set of JMX interfaces exposed by Oracle Communications Services Gatekeeper. Dependent on Oracle WebLogic Server CR 382906. | 4.1 |
CR380863 | The SOAP to SOAP generation does not support all WSDLs. The WSDL defining the application-facing interface must adhere to the following: Attribute name in <wsdl:service> must include the suffix Service. Attribute name in <wsdl:port> must be the same as the name attribute in <wsdl:service>, excluding the suffix Service. Dependent on Oracle WebLogic Server CR 384278. | 4.1 |
CR382790 | The Native SMPP communication service does not actively disconnect applications if the SMSC connection is down. The communication service sends an OK response to enqure link requests in this case. | 4.1 |