APAR status
Closed as program error.
Error description
On windows machine on V5.0.2 and V5.1 attempts to change the
location of the IBM Service log (acticity.log) fails. The Admin
Console shows the error "File name is not a valid entry."
-
These are the steps that show the problem:
1. Bring up Administrative Console.
2. Click on Servers > Application Severs
3. Select server-name
4. Under section "additional property"
- Select Logging and Tracing
- Select IBM Service Logs
5. The default log file is: $(LOG_ROOT)/activity.log
Changed to following path
D:/logs/activity.log
6. Click OK
7. Popup message is seen:
"File name is not a valid entry."
-
Early analyse shows the problem is occurring because of the
validation being done
======
Work Around:
Two possible work-arounds are available
1. Use the format /logs/activity.log. This will put the file
in the directory where WebSphere is installed.
or
2. From admin console
- click Environment > Manage WebSphere Variables
- set up desired scope
- Click new
- Add variable name and the directory for the log
such as log-keeper and D:/logs
- Save
- From the IBM Service Logs panel change the log file to
$(log-keeper)/activity.log
- Save
Local fix
Work Around:
Two possible work-arounds are available
1. Use the format /logs/activity.log. This will put the file
in the directory where WebSphere is installed.
or
2. From admin console
- click Environment > Manage WebSphere Variables
- set up desired scope
- Click new
- Add variable name and the directory for the log
such as log-keeper and D:/logs
- Save
- From the IBM Service Logs panel change the log file to
$(log-keeper)/activity.log
- Save
Problem summary
****************************************************************
* USERS AFFECTED: Administrative console users using Windows *
* operating systems who try to change the path *
* of activity.log *
****************************************************************
* PROBLEM DESCRIPTION: Change activity.log path from GUI *
* using these steps *
* 1. Open v 5.0 GUI *
* 2. Click on Servers *
* 3. Select Application Servers *
* 4. Select Server1 *
* Under section "additional property" *
* - Select Logging and Tracing *
* - Then Select IBM Service Logs *
* 5. The default log file is: *
* $(LOG_ROOT)/activity.log *
* Change to path , for example *
* d:/logs/UAT1/east/activity.log *
* *
* *
* on clicking "OK", it comes up with *
* following popup msg. *
* "File name is not a valid entry." *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The problem is occuring because of the restrictions occuring
in validation.xml. If the filepath contained a ':' character,
it was considered invalid . This validation error was corrected
as part of the fix.
Problem conclusion
A validation check was added which handles valid file paths of
both unix and windows operating systems and the problem was
resolved
Temporary fix Comments
APAR information |
APAR number |
PQ92478 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-08-05 |
Closed date |
2004-09-21 |
Last modified date |
2004-09-21 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R00W PSY |
UP |
R10W PSY |
UP |
|