This week's book giveaway is in the Spring forum.
We're giving away four copies of Spring Boot in Practice and have Somnath Musib on-line!
See this thread for details.
Win a copy of Spring Boot in Practice this week in the Spring forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

Unable to start administrative console in WSAD

 
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I'm unable to start the admin console in WSAD 5.1. I have not had this problem before, recently I had to rebuild my machine and reinstalled WSAD and this problem popped up. When I tried to start the admin console I got the following error on screen...

Error 500
An error occurred while processing request: /secure/logon.do
Message: Server caught unhandled exception from servlet [action]: null

Clicking on the "Show Details" button reveals..
Invalid Session
Session has become invalid

Invalid Session
Your session has become invalid. This is due to a session timeout, an administrator has logged you out, or another user has invalidated your session by logging on with the same User ID.

The stack trace in the logs ..
WebGroup E SRVE0026E: [Servlet Error]-[action]: java.lang.NullPointerException
at com.ibm.ws.sm.workspace.impl.RepositoryContextImpl.buildContextOnly(RepositoryContextImpl.java:115)
at com.ibm.ws.sm.workspace.impl.RepositoryContextImpl.buildContext(RepositoryContextImpl.java:93)
at com.ibm.ws.sm.workspace.impl.WorkSpaceImpl.buildContext(WorkSpaceImpl.java:95)
at com.ibm.ws.sm.workspace.impl.WorkSpaceImpl.restore(WorkSpaceImpl.java:257)
at com.ibm.ws.sm.workspace.impl.WorkSpaceManagerImpl.createWorkSpace(WorkSpaceManagerImpl.java:100)
at com.ibm.ws.sm.workspace.impl.WorkSpaceManagerImpl.getWorkSpace(WorkSpaceManagerImpl.java:130)
at com.ibm.ws.console.core.action.LogonAction.createWorkSpace(LogonAction.java:168)
at com.ibm.ws.console.core.action.LogonAction.createUser(LogonAction.java:149)
at com.ibm.ws.console.core.action.LogonAction.perform(LogonAction.java:85)
at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1791)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:201)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:610)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:431)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)

Any help would be appreciated urgently..

Rob
 
Ugly Redneck
Posts: 1006
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Try some of the following links:

PQ85431

PQ87759
 
Robert Lay
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I had a look at the links what they say seem to indicate the problem was caused by installing WSAD and Websphere server together, however I have only WSAD 5.1.0(with latest updates) installed.
Within WSAD it is able to display the login screen for the admin console, however after I enter an id and click Ok it gives me the above mentioned error.
Further suggestions would be great. Thanx
 
Paul McKenna
Ugly Redneck
Posts: 1006
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Was WSAD working before you did the wipe out and reload? I hate it when people say this, but could you possibly try reloading WSAD on another "clean" machine and try?
 
Robert Lay
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes it was working before until I reinstalled though I have version 5.1.1 prior. My colleague was also unable to start the console giving the same error. Could ther ebe a bug with WSAD 5.10 , the build ID is 20030726_2016
Could it be the updates which I applied that have cause it?
 
Paul McKenna
Ugly Redneck
Posts: 1006
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Could very well be. IBM is getting to be as notorious as Microsoft with their patches but that could be your problem. I dont have any problems with WSAD so I dont think it is a bug with it.
 
Robert Lay
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have installed version 5.1.2 and its all up and running now. Thanx for helping.
Running into another problem now. Will start a new post.
 
reply
    Bookmark Topic Watch Topic
  • New Topic