Release Notes

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Gatekeeper 4.0 Known and Resolved Issues

 


Known Issues in Gatekeeper 4.0

.

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
 
CR372834
The MLP Simulator in Platfor Test Environment will parse longitude/latitude incorrectly when the locale is not English.
Switch locale to English
4.0
 
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
 
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:
  1. If you are using the MyISAM engine, set the character type to latin1
  2. or

  3. Use the InnoDB engine with UTF-8 or latin1 character set
4.0
 
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
 
CR372233
Warnings are thrown even when the silent installer is run successfully.
These warnings have no impact on functionality.
4.0
 
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
 
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
 
CR372847
The Statistics Service createWeeklyReport operation fails to retrieve a value which the report requires, which causes the operation to fail.
4.0
 
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
 
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
 

 


Resolved Issues in Gatekeeper 4.0

CR341661
Installing WLNG defaults to a development mode installation instead of production mode.
3.0
4.0
CR330939
There is no OAM method to enable trace for Access Tier servers
3.0
4.0
CR329979
Changing buffer size property for Trace service erases the trace files content.
3.0
4.0
CR311065
If you make changes in WS-Security options using the Admin Console, the Console offers to let you store plan.xml in the directory of your choice. But WLS itself only looks for the plan.xml in the default location, so a file saved to other than the default location has no impact on WLS behavior. .
3.0
4.0
CR327407
When SLAs are updated, only the server where the SLA is updated gets the current settings immediately. The budget service does not push budget configuration changes to slaves on update, so other Network Tier servers keep the old budget settings until the budget service polls for configuration changes.
3.0
4.0
CR326236/ CR328083/ CR328439/CR306501
In some cases of NT failover while running MMS, WAP Push with Delivery Notifications, or Terminal Location traffic, there may be a brief period during which throughput falls to zero and some messages are lost.
3.0
4.0
CR327200
If you are using the backwards compatible version of the SMS traffic path with SMPP, and you have multiple plug-ins, each of which is set to different limits in the Node SLA, node policy enforcement will not work correctly.

Note: This communication service is no longer supported

3.0
4.0
CR319714
When there are multiple address fields in a StartCallNotification message, only the SIP URL in the first address field is checked for format.
3.0
4.0
CR319715
Trying to stop CallNotification with an invalid correlator produces an SVC001 exception instead of the correct SVC002.
3.0
4.0
CR317967
If an application calls StopSmsNotification with an invalid correlator, an incorrect error message is produced. An SVC0002 exception is thrown, but the variables field in the response message contains the value of the correlator, not the text "Correlator"
3.0
4.0
CR318556
If an application calls EndCall with an incorrectly formatted identifier, an incorrect error message is produced. An SVC0001 exception is thrown, with error code SIP000003 instead of an SVC002.
3.0
4.0
CR318555
If an application calls EndCall with an invalid identifier, no error message is produced. An SVC002 should be thrown.
3.0
4.0
CR318552
If an application calls MakeCall with a charging part defined and the ThirdPartyCall plug-in for SIP has ChargingAllowed set to false, no error message is produced. A POL0008 exception should be thrown.
3.0
4.0
CR319755
If an application calls StartCallDirectionNotification more than once for a single SIP address, an incorrect error message is produced. An SVC0001 exception is thrown with the error code CN-000001. The correct value would be an SVC0002 exception with a variable field that indicates the SIP address.

Note: The decision was that the current implementation is more useful for end user. Marked Works as Designed.

3.0
4.0
CR327292
Both SP and Global node SLA contracts are enforced even if the use period falls outside of specified start and end dates.
3.0
4.0
CR329959
If there are overlapping <override> tags in the SLA, enforcement may choose either tag value.
3.0
4.0
CR327429
Node/Global policy enforcement throws service exceptions instead of policy exceptions
3.0
4.0
CR330699
In the Extension Toolkit the Turn On Plug-in Debug option cannot be selected.
3.0
4.0
CR305817
There is no mechanism for unregistering interfaces for a ManagedPlugin instance. New objects that are registered are simply appended to the existing list.
3.0
4.0
CR329497
The alarm page of the Management Console does not limit the number of alarms displayed. In a situation where many alarms are being emitted, this may cause significant lag times as the page is being rendered.
3.0
4.0
CR326557
The management operation PolicyArrow symbolreloadServiceProviderXmlDriver does not reload the XSD for the Service Provider SLAs.
3.0
4.0
CR305375
Management operation SLEEArrow symbolgetFreeDiskSpace does not return the correct value. A NumberFormatException Exception is thrown.
3.0
4.0
CR327896
Application sessions expire one minute early. If LoginTicket Lifetime (session) check is enabled, the time-out value expires one minute earlier than expected.
3.0
4.0
CR329465
In the SMPP plug-in for SMS, the methods getReceivedSms and getSmsDeliveryStatus produce events, but these are not described in the edr.xml file. This means that the event will not be classified, and will appear to listeners as "Unknown." As a result, it is impossible to have these events trigger CDRs.
3.0
4.0
CR326808
Network Gatekeeper cannot process MMSes without attachments, as, for example, an MMS that is sent with a subject but no content. If a SOAP attachment is NULL, SVC0001 is thrown to the application and NullPointerExceptions are logged in Network Gatekeeper
3.0
4.0
CR306833
If an application calls SendSms with no destination address specified, an incorrect error message is produced. An SVC0001 exception is thrown, but the variables field in the response message reads: "No plug-in available for type: interface com.bea.wlcp.wlng.px21.plugin.SendSmsPlugin".
3.0
4.0
CR311849
Service Level Agreements fail to load if there are space characters prior to the <?xml> tag.
3.0
4.0
CR327194/CR327314
Alarms are not generated in certain circumstances: for Node/Global policy enforcement, when Node SLA limit for application-initiated traffic is reached
3.0
4.0
CR318142
If you use the Eclipse plug-in to generate a communication serviceskeleton, the GUI does not give you the option of naming the Administration Server anything but AdminServer. Also using the plug-in GUI you cannot specify t3 as the protocol for the WLS administration URL.
3.0
4.0


  Back to Top       Previous  Next