IBM Support

Application Server does not start - OSGi permission issue

Technote (troubleshooting)


You attempt to start an application server (ie: server1), but it does not start and the systemout.log is not updated when using IBM WebSphere Application Server.


The native_stdout.log shows:

deleteEclipseInstanceArea shutdown hook: deleting /app/wasprofile/profile1/temp/osgi_instance_location/wasadm/9697023

Under the folder there is a file called nnnnnnnnnnnnn.log (where nnnnnnnnnnnnn is a random number). The content of that file shows:

!ENTRY org.eclipse.osgi 4 0 2012-01-17 10:00:31.414

!MESSAGE Error reading configuration: Unable to create lock manager.

!STACK 0 Unable to create lock manager.

at org.eclipse.osgi.internal.baseadaptor.BaseStorage.initFileManager(
at org.eclipse.osgi.internal.baseadaptor.BaseStorage.initialize(
at org.eclipse.osgi.baseadaptor.BaseAdaptor.initializeStorage(
at org.eclipse.osgi.framework.internal.core.Framework.initialize(
at org.eclipse.osgi.framework.internal.core.Framework.<init>(
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at org.eclipse.core.launcher.Main.invokeFramework(
at org.eclipse.core.launcher.Main.basicRun(


The problem is caused by a permission problem with the folders under the <profile_home>/servers/<servername>/configuration folder. The WebSphere Application Server was not able to read/write to the folders. The folders have the wrong permissions because the command was ran as the root user but WebSphere Application Server is being run as a non-root user.


This is only seen in WebSphere Application Server Version 8.

Diagnosing the problem

The errors in the nnnnnnnnnnnnn.log indicate that files could not be created in the <profile_home>/servers/<servername>/configuration subfolders.

Resolving the problem

Remove or rename the <profile_home>/servers/<servername>/configuration folder and re-running the command as the correct user. This will create a new <profile_home>/servers/<servername>/configuration folder with the correct permissions.

Document information

More support for: WebSphere Application Server
System Management/Repository

Software version: 8.0, 8.5, 8.5.5

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows

Reference #: 1578438

Modified date: 17 January 2012