Failed to activate session in OSB: java.io.IOException: Permission denied

Question

I was able to successfully import my sbconfig jar. But while activating the session, the error below appeared.
Error message:
<Error> <ConfigFwk> <BEA-390101> <Activation of session weblogic failed: java.io.IOException: Permission denied (errno:13)
java.io.IOException: Permission denied (errno:13)
at java.io.UnixFileSystem.createFileExclusively(Native Method)
at java.io.File.createNewFile(File.java:903)
at com.bea.wli.sb.resources.archive.ArchiveResourceRuntimeManager$ArchiveResourceLifecycleListener.createJarClassLoader(ArchiveResourceRuntimeManager.java:103)
at com.bea.wli.sb.resources.archive.ArchiveResourceRuntimeManager$ArchiveResourceLifecycleListener.onCreate(ArchiveResourceRuntimeManager.java:171)
at com.bea.wli.config.impl.ResourceListenerNotifier.sendChangeNotification(ResourceListenerNotifier.java:456)
Truncated. see log file for complete stacktrace
We assume that the error was with the creation of the new file. We need to check if its filesystem has proper permissions. Please advise on the fix for the permission error and also any inputs on where this file is created.

Answer 1

This can also occur if your $DOMAIN_HOME/osb/config/core/_binary/_jars path and the files it contains are owned by root, which can happen if you have accidentally started the server as root once.
The easiest way however to find the root cause (on Linux) is:
cd $DOMAIN_HOME
find . -user root > /tmp/ownedByRoot
And then check the file /tmp/ownedByRoot for any hits. Finally change the file permissions using the chown command, so they get owned by the user running WebLogic.
My experience is that you don't need to restart the OSB server after this change. Activating the OSB import worked immediately after I chown'ed that dir.
Edited by: 925121 on Apr 3, 2012 1:26 AM