| Asset ID: |
1-71-2227421.1 |
| Update Date: | 2017-01-31 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
2227421.1
:
Logs Files Forming With Huge Size
| Related Items |
- Oracle Communications Policy Management
|
| Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Broadband Network Solutions>SN-SND: Tekelec Policy
|
In this Document
Created from <SR 3-14064209921>
Applies to:
Oracle Communications Policy Management - Version POLICY 12.1.2 and later
Information in this document applies to any platform.
Goal
On : POLICY 12.1.2 version, Wireless (Production)
Logs files forming with huge size
On MPE servers we found lot of log files are forming with size of GBs and are not getting terminated after certain size in MB.
Rather that creating multiple files with small size , system is creating single files with very large size.
Solution
ISSUE:
rc_output_log file size in GB and keeps growing.
ROOTCAUSE:
This is a known issue. rc_output_log file has too many exceptions (200K +) for below messages, these messages need not be written into this file
java.lang.NumberFormatException: For input string: "6.3"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:580)
at java.lang.Integer.parseInt(Integer.java:615)
at camiant.diameter.apps.nasreq.af.objects.MediaDescription$FMTP.parse(MediaDescription.java:793)
at camiant.diameter.apps.nasreq.af.objects.MediaDescription$FMTP.(MediaDescription.java:760)
at camiant.diameter.apps.nasreq.af.objects.MediaDescription$Attribute.parse(MediaDescription.java:531)
at camiant.diameter.apps.nasreq.af.objects.MediaDescription.(MediaDescription.java:162)
at camiant.diameter.apps.nasreq.af.objects.MediaData.parse(MediaData.java:124)
at camiant.diameter.apps.nasreq.af.rx.objects.CodecData.parse(CodecData.java:83)
at camiant.diameter.apps.nasreq.af.objects.MediaData.parse(MediaData.java:114)
at camiant.diameter.apps.nasreq.af.objects.MediaData.(MediaData.java:51)
at camiant.diameter.apps.nasreq.af.rx.objects.CodecData.(CodecData.java:65)
at camiant.diameter.apps.nasreq.af.rx.objects.CodecDataAVP.getMediaDataImpl(CodecDataAVP.java:50)
at camiant.diameter.apps.nasreq.af.objects.MediaDataAVP.parse(MediaDataAVP.java:58)
at camiant.diameter.apps.nasreq.af.objects.MediaDataAVP.getMediaDataValue(MediaDataAVP.java:71)
at camiant.diameter.apps.nasreq.af.rx.objects.CodecDataAVP.getCodecDataValue(CodecDataAVP.java:46)
at camiant.diameter.apps.nasreq.af.rx.objects.RxMediaCompDesc.setNewMediaDataAVPs(RxMediaCompDesc.java:152)
From the stack above, we can see this exception was raised when PCRF parse the CodecData AVP in Rx message. Seems some invalid parameters are filled in this AVP
WORKAROUND:
whenever the file size grows, use the below command to empty the file (Do not delete this file)
" > rc_output.log "
FIX:
As part of the fix, these exceptions would be written in rc.log, which gets rotated. This issue is fixed in 12.2, 12.2 is currently available.
References
<BUG:22824999> - BROOKLYN_COMMON: LOGGER STATEMENTS SHOULD BE USED INSTEAD OF PRINTING THROWABLE
Attachments
This solution has no attachment
