Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
5 replies Latest Post - ‏2007-08-29T17:00:39Z by Stan
Billy.Huang
Billy.Huang
1 Post
ACCEPTED ANSWER

Pinned topic Concurrent user volumn is no more than 10?

‏2005-08-04T02:53:45Z |
I have a websphere portal server 5.1 with an embeded cloudscape db as the portal server repository. The portal server is configued to use LDAP for the application user authentication.

I performed a stress test on singin function and found every time when the concurrent user number reaches 10 (9 is OK), the cloudscape in portal server is dead and didn't respond to any query. I have to restart the server to resume the database.

Here is the error message I got from portal server log



2005.08.03 10:25:26.250 E com.ibm.wps.engine.commands.LoginUser execute
EJPSD0024E: Exception occured. - StackTrace follows...

2005.08.03 10:25:26.250 E com.ibm.wps.engine.commands.LoginUser execute
com.ibm.wps.util.ConcurrentModificationException: EJPDB0030E: Database has been changed since creation of data object [ObjectID = 9_0_FP USER:505].
at com.ibm.wps.datastore.impl.ResourcePersister.storeExisting(ResourcePersister.java:299)
at com.ibm.wps.datastore.impl.ResourcePersister.store(ResourcePersister.java:125)
at com.ibm.wps.datastore.impl.ResourcePersister.store(ResourcePersister.java:98)
at com.ibm.wps.datastore.impl.ResourceImpl.store(ResourceImpl.java:132)
at com.ibm.wps.datastore.UserDescriptor.store(UserDescriptor.java:171)
at com.ibm.wps.engine.commands.LoginUser.execute(LoginUser.java:255)
at com.ibm.wps.engine.Command.execute(Command.java:113)
at com.ibm.wps.auth.AuthenticationServlet.doLoginWithExceptions(AuthenticationServlet.java:101)
at com.ibm.wps.auth.AuthenticationServlet.doLogin(AuthenticationServlet.java:69)
at com.ibm.wps.auth.AuthenticationServlet.doPost(AuthenticationServlet.java:64)
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.ServicingServletState.service(StrictLifecycleServlet.java:333)
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:1033)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java(Compiled Code))
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:204)
at com.ibm.wps.portletservice.authentication.impl.AuthenticationPortletServiceProvider.doLogin(AuthenticationPortletServiceProvider.java:109)
at com.ibm.gvtwizard.portlet.LoginPortlet.processAction(LoginPortlet.java:141)
at com.ibm.wps.pe.pc.std.cmpf.impl.PortletFilterChainImpl.processAction(PortletFilterChainImpl.java:104)
at com.ibm.wps.propertybroker.standard.filter.PropertyBrokerActionFilter.processAction(PropertyBrokerActionFilter.java:253)
at com.ibm.wps.pe.pc.std.cmpf.impl.PortletFilterChainImpl.processAction(PortletFilterChainImpl.java:95)
at com.ibm.wps.pe.pc.std.invoker.impl.PortletServlet.dispatch(PortletServlet.java:148)
at com.ibm.wps.pe.pc.std.invoker.impl.PortletServlet.doPost(PortletServlet.java:76)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at com.ibm.wps.pe.pc.std.cache.CacheablePortlet.service(CacheablePortlet.java:256)
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.ServicingServletState.service(StrictLifecycleServlet.java:333)
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:1038)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java(Compiled Code))
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.include(WebAppRequestDispatcher.java:257)
at com.ibm.wps.pe.pc.std.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:204)
at com.ibm.wps.pe.pc.std.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:168)
at com.ibm.wps.pe.pc.std.invoker.impl.PortletInvokerImpl.action(PortletInvokerImpl.java:82)
at com.ibm.wps.pe.pc.std.event.ActionEvent.execute(ActionEvent.java:107)
at com.ibm.wps.pe.pc.std.event.EventQueueManager.processEventLoop(EventQueueManager.java:85)
at com.ibm.wps.pe.pc.std.PortletContainerImpl.performEvents(PortletContainerImpl.java:175)
at com.ibm.wps.pe.pc.PortletContainerImpl.performEvents(PortletContainerImpl.java:213)
at com.ibm.wps.engine.phases.WPActionPhase.processPortlets(WPActionPhase.java:1170)
at com.ibm.wps.engine.phases.WPActionPhase.execute(WPActionPhase.java:561)
at com.ibm.wps.state.phases.AbstractActionPhase.next(AbstractActionPhase.java:130)
at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:638)
at com.ibm.wps.engine.Servlet.doGet(Servlet.java:496)
at com.ibm.wps.engine.Servlet.doPost(Servlet.java:664)
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.ServicingServletState.service(StrictLifecycleServlet.java:333)
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.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:76)
at com.ibm.wps.state.filter.StateCleanup.doFilter(StateCleanup.java:71)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:132)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:71)
at com.ibm.wps.mappingurl.impl.URLAnalyzer.doFilter(URLAnalyzer.java:174)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:132)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:71)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:1029)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java(Compiled Code))
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:204)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:125)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:286)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:116)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
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:615)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:439)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:912)



Is there anyone who meets this kind of problem?
Updated on 2007-08-29T17:00:39Z at 2007-08-29T17:00:39Z by Stan
  • SystemAdmin
    SystemAdmin
    1525 Posts
    ACCEPTED ANSWER

    Re: Concurrent user volumn is no more than 10?

    ‏2005-08-05T17:06:31Z  in response to Billy.Huang
    Cloudscape has no limit to the number of logins allowed. As long as there is memory available to setup the process space the login will succeed. The problem appears to be elsewhere - note also there are no Cloudscape (com.ibm.db2j.*) classes listed in the stacktrace.

    I am not knowledgable of the Portal Server implementation of Cloudscape so this is a bit of a guess - I would check for configurations that limit connections to 9 or 10. Portal itself may have a limit and datasources usually have a maximum pool size. The message you are getting is not from Cloudscape - can you find out from the Portal Server group what this message indicates?

    Database has been changed since creation of data object [ObjectID = 9_0_FP USER:505].
    • SystemAdmin
      SystemAdmin
      1525 Posts
      ACCEPTED ANSWER

      Re: Concurrent user volumn is no more than 10?

      ‏2005-11-14T08:57:25Z  in response to SystemAdmin
      Hello,
      I'm getting the same error. Please inform me if you found a solution for this.
      • Stan
        Stan
        267 Posts
        ACCEPTED ANSWER

        Re: Concurrent user volumn is no more than 10?

        ‏2005-11-14T16:27:04Z  in response to SystemAdmin
        I found this reference to the error on the Portal Server Support site, it says to run the Portal Cleanup Service note this problem was found NOT to limited to the Lotus Collaborative portlets/components as the intial report implies:

        http://www-1.ibm.com/support/docview.wss?uid=swg21191679

        Hope this helps.

        [b]In Reference to:[/b]
        2005.08.03 10:25:26.250 E com.ibm.wps.engine.commands.LoginUser execute
        EJPSD0024E: Exception occured. - StackTrace follows...

        2005.08.03 10:25:26.250 E com.ibm.wps.engine.commands.LoginUser execute
        com.ibm.wps.util.ConcurrentModificationException: EJPDB0030E: Database has been changed since creation of data object [ObjectID = 9_0_FP USER:505].
        at com.ibm.wps.datastore.impl.ResourcePersister.storeExisting(ResourcePersister.java:299)
        at com.ibm.wps.datastore.impl.ResourcePersister.store(ResourcePersister.java:125)
        at com.ibm.wps.datastore.impl.ResourcePersister.store(ResourcePersister.java:98)

        [b]Solution[/b]
        This issue appears when the portlet has been recently 'Updated' using the Portal Administration user interface, and the Portal's Cleanup Service has not yet run.

        The solution to this issue is to run the "Task.xml" XmlAccess script after the portlet updates. This forces a cleanup of Portal resources rather than having to wait for the next Portal Cleanup process to trigger.

        Note: After further review, this seems to be a general WebSphere Portal problem not limited to the Lotus Collaborative portlets/components.

        Please refer to the topics, "Delayed Cleanup of Deleted Portal Pages" and "Working with the XML Configuration Interface" in the WebSphere Portal v5.1 InfoCenter for more detail on the Portal Cleanup service.
        • SystemAdmin
          SystemAdmin
          1525 Posts
          ACCEPTED ANSWER

          Re: Concurrent user volumn is no more than 10?

          ‏2007-08-29T15:12:06Z  in response to Stan
          Hi,

          Even I am seeing this same error, can the Portal server get hung due this issue.

          Balaji
          • Stan
            Stan
            267 Posts
            ACCEPTED ANSWER

            Re: Concurrent user volumn is no more than 10?

            ‏2007-08-29T17:00:39Z  in response to SystemAdmin
            Please post questions about Portal Server behavior to a Portal Server newsgroup or formum. This forum is best suited to assist with Apache Derby / Cloudscape issues.

            Did the resolution referencing the Portal Server support document posted earlier in this thread help you at all?