PM53901: SIP PROXY DOES NOT KEEP MORE THAN 1 HISTORICAL SIPPROXY LOG

Fixes are available

APAR status

Closed as program error.

Error description

When sipproxy.log reaches max specified size, the log rolls
over as expected and creates a date stamped log called


sipproxy_<date>.log and a new sipproxy.log is created. But when
the sipproxy.log reaches it's max specified size, the previous
sipproxy_<date>.log
is overwritten with a new sipproxy_<date>.log

Because of this behavior there is no way to keep more than 1
historical log for the Session Initiation Protocol (SIP) Proxy
Server

Local fix

```
na
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Session Initiation Protocol (SIP)    *
*                  Proxy                                       *
****************************************************************
* PROBLEM DESCRIPTION: SIP Proxy only keeps 1 historical       *
*                      sipproxy log.   There is no way to      *
*                      increase this.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
SIP Proxy only keeps 1 historical sipproxy log.   There is no
way to increase this.

Problem conclusion

We added a custom property for the SIP Proxy to allow  you to
set the maximum number of backup files.  In the administrative
console, go to the
"WebSphere proxy servers > proxy > SIP proxy settings > Custom
properties page.  Add a custom property with name
"maxBackupLogFiles" and set the value to the number of
backup log files.


The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.23 and 8.0.0.3.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM53901
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-12-08
Closed date
2011-12-21
Last modified date
2011-12-21

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R700 PSY
UP
R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

PM53901: SIP PROXY DOES NOT KEEP MORE THAN 1 HISTORICAL SIPPROXY LOG

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

R800 PSY

Document Information

Share your feedback

Need support?