Unable to login into WebSphere Application server of RTC
We are using RTC 4.0 version and when i try to login into Websphere application server of RTC, getting the below error.
Please help me to locate the issue.
com.ibm.ws.sm.workspace.WorkSpaceException: WKSP0011E Unable to create existing session id file /opt/IBM/WebSphere/AppServer/profiles/Dmgr/wstemp/-791806762/workspace/.workspace_6c7fAl1qnZdJzG8gwO1lp79 --java.io.IOException: No such file or directory
3 answers
Hello Fazal,
I am assuming you are not able to log into the WebSphere administrative console. The first thing I would attempt is the following:
1. Stop WebSphere
2. Clear out the following temp directories
<WebSphere_Install_Root>\profiles\(profile_name)\wstemp
<WebSphere_Install_Root>\profiles\(profile_name)\temp
<WebSphere_Install_Root>\profiles\(profile_name)\config\temp
3. Clear out the RTC and WebSphere logs located at
<WebSphere_Install_Root>\profiles\(profile_name)\logs
In this directory there will be two sub directories \ffdc and \(server_name) ... either remove or rename these directories. During startup WebSphere will recreate.
Also the jts.log, ccm.log ext are located in this directory. May be a good idea to remove these as well so that we have a clean set of logs when restarting WebSphere
4. Restart WebSphere
5. IF the issue persists, open a PMR against WebSphere and upload the WebSphere logs to the PMR. This way the WebSPhere admin team can look into this issue.
I am assuming you are not able to log into the WebSphere administrative console. The first thing I would attempt is the following:
1. Stop WebSphere
2. Clear out the following temp directories
<WebSphere_Install_Root>\profiles\(profile_name)\wstemp
<WebSphere_Install_Root>\profiles\(profile_name)\temp
<WebSphere_Install_Root>\profiles\(profile_name)\config\temp
3. Clear out the RTC and WebSphere logs located at
<WebSphere_Install_Root>\profiles\(profile_name)\logs
In this directory there will be two sub directories \ffdc and \(server_name) ... either remove or rename these directories. During startup WebSphere will recreate.
Also the jts.log, ccm.log ext are located in this directory. May be a good idea to remove these as well so that we have a clean set of logs when restarting WebSphere
4. Restart WebSphere
5. IF the issue persists, open a PMR against WebSphere and upload the WebSphere logs to the PMR. This way the WebSPhere admin team can look into this issue.