Robert Lay

When you create a new server do you see an entry stating Websphere Portal 5.0 test server? If so then portal toolkit is installed.
Also when you create a new project select Others, if you can see Portal Application project then you have installed the toolkit.

Hi,

Have a query in regard to the portal test server V5.0
The test environment runs fine but I am unable to retain the page layout settings after I restart the test server.

I can create new pages but any portlets which I add onto those pages gets removed after server restart and all I'm left with are empty pages.
This is a pain for testing as I need to add the portlets back in every time I restart the server.

Could there be a setting where I could enable to retain page layout settings?

Hi,

When I try to modify an already existing application in the test environment (test server version v5.0) I get the message "Deployment Descriptor is required". The application runs fine if I do Run On Server but I am unable to make any modification to its runtime properties via the administration console such as Starting Weight or Reload Interval.

Within the admin console if I try to view the Deployment descriptor I get a blank screen with the console displaying the followign messages..

456d8e11 TraceNLS u Unable to load ResourceBundle com.ibm.ws.console.deploymentdescriptor.ddutilsMessages
[4/11/04 16:24:46:037 EST] 456d8e11 DescriptorVie E COULD_NOT_LOAD_ERROR_WUDU0004
[4/11/04 16:24:46:068 EST] 456d8e11 TraceNLS u Unable to load ResourceBundle com.ibm.ws.console.deploymentdescriptor.ddutilsMessages
[4/11/04 16:24:46:068 EST] 456d8e11 DescriptorVie E WORKSPACE_RETURNED_NULL_ERROR_WUDU0006

I am using websphere studio v5.1.2

Any help would be appreciated.

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.

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?

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

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

Hi all, I'm developing an application using Websphere 5.
Currently having an issue with class instantiation and hope someone could enlighten my day.
The situation is that I have a Web project called TestWeb that references a utility jar file called utility.jar
Within that utility.jar file I have a class that uses dynamic class loading to create a class existing inside TestWeb. The code is
Class adapterclass = Class.forName(cName);
where cName is a class existing in TestWeb.

When the above line exceutes I get a NoClassDefFoundException. As far as I know the class definition should have been loaded as the class file sits inside the WEB-INF\classes directory of TestWeb. If thats the case then any other jar files being used by the TestWeb application should have access to this classpath.

Am I right or am I extremely convoluted in my thinking?
Any help would be greatly appreciated.

Regards,
UD