This content has been marked as final. Show 4 replies
it could be that you have installed OSB as root, so there are certains directories in the /tmp folder that your unix user cannot access in write mode. The directory is /tmp/alsbTempDir or something along that line.
Thanks for the inputs. I am sure that I did not install OSB using root access. The user I used for the installation is the same user I am using for the import and activation. I only saw /var/tmp/alsbTempJars. There's is no alsbTemp directory in /tmp. Please advise.
sure, your mileage can vary, it depends of which TEMP directory you are using to write temporary files.
anyway just make sure that your Unix user has write access to that ALSBtempJar directory, as well as to the domain directory and all its subdirectories.
Incidentally, are you starting the WL server directly or through a Node Manager? The issue could be that if you run through the Node Manager the unix user associated is different from the one you used to install the domain and/or the binaries.
It would be so much easier if the log was telling you which file it was trying to create....I don't think it would be asking the moon...
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:
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