Troubleshooting
Problem
FileNotFoundException occurs for derby.log if creating a profile with non-root user and configuring datasource of Derby.
Symptom
A FileNotFoundException occurs for derby.log when configuring a datasource of Derby using a profile of a non-root user ownership during the start up of the server process. The following message is written in the SystemErr.log file, reporting permission denied to derby.log with non-root user:
| [5/19/09 10:37:59:801 JST] 00000009 SystemErr R 2009-05-19 01:37:59 .798 GMT Thread[server.startup : 0,5,main] java.io.FileNotFoundException: /usr/IBM/WebSphere/AppServer/derby/derby.log (The file access permis sions do not allow the specified action.) |
Cause
The start-up user should have write permission for the derby.log file, but the information center topic, Assigning profile ownership to a non-root user, does not describe the permission for the following file:
| install_root/derby/derby.log |
Resolving The Problem
Change the path of the derby.log file to a new location within the directory that the non-root user has permission.
For example, modify the path of the derby.log file to the following directory:
| install_root/profile/profile_name/derby/derby.log |
- Set derby.stream.error.file as a JVM custom property
- In the administrative console, expand Servers > Application servers > server_name > Process definition > Java Virtual Machine > Custom properties.
- Click New.
- Specify the following Custom property and click Apply.
Name:
derby.stream.error.file
Value:
install_root/profile/profile_name/derby/derby.log
- Set derby.stream.error.file in derby.properties:
- Edit the derby.properties file located in the following directory:
- Add the following line in the derby.properties file:
| install_root/derby/derby.properties |
| derby.stream.error.file=install_root/profile/profile_name/derby/derby.log |
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21389419