|
This document applies only to the following language
version(s):
US English |
|
Problem(Abstract) |
Trying to login to administrative console throws error 500
with java.lang.NullPointerException. |
|
Symptom |
After running out of disk space, trying to login to the
administrative console failed with error 500 and following Exception in
SystemOut.log:
java.lang.NullPointerException
at org.apache.jsp._console._jspService(_console.java:172)
at com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase.
java:89)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.cache.servlet.ServletWrapper.serviceProxied
(ServletWrapper.java:266)
Also in the stderr.log:
com.ibm.ws.util.prefs.InvalidPreferencesFormatException:
org.xml.sax.SAXParseException Premature end of file.
at
com.ibm.ws.util.prefs.XmlHelper.importPreferences(XmlHelper.java:126)
at
com.ibm.ws.util.prefs.BasePreferencesImpl.importPreferences(BasePreferencesImpl.java:449)
at
com.ibm.ws.console.core.bean.UserPreferenceBean.init(UserPreferenceBean.java:58)
at
com.ibm.ws.console.core.bean.UserPreferenceBean.setUserName(UserPreferenceBean.java:35)
at com.ibm.ws.console.core.User.valueBound(User.java:81)
|
|
|
 |
|
Cause |
When user tries to login to administrative console, a
preferences.xml file is built in
<WAS_HOME>/wstemp/<user_dir>.
If creation of preferences.xml fails due to lack of disk space,
it leaves preferences.xml file with zero length. This zero length
preferences.xml file causes the "SAXParseException Premature end
of file". |
|
|
Resolving the
problem |
To resolve this issue:
- Clean up the disk space problem.
- Delete the
<WAS_HOME>/wstemp/<user_dir>/preferences.xml
file.
- Try to login to administrative console. This should build a new
preferences.xml with the correct data and should allow the user
to login to administrative console.
|
|
|