cancel
Showing results for 
Search instead for 
Did you mean: 

Error: Performed cache operation with stopped CacheGroup thread

PH
Participant
0 Kudos

Hi all,

we are running SAP BW 7.0 SPS 22 with an Enterprise Portal used for reporting.

We sporadically face the following issue. When I call the logon URL of the portal (http://<hostname>.<domain>:<port>/irj/portal) the logon screen appears.

After entering username and password the following error is shown:

com.sap.engine.lib.util.cache.CacheGroupException: Performed cache operation with stopped CacheGroup thread.
  at com.sap.engine.lib.util.cache.Cache.addCache(Cache.java:183)
  at com.sap.engine.services.security.login.SecuritySessionPool.registerSession(SecuritySessionPool.java:207)
  at com.sap.engine.services.security.login.CreateSessionAction.createSessionFromSubject(CreateSessionAction.java:86)
  at com.sap.engine.services.security.login.CreateSessionAction.run(CreateSessionAction.java:54)
  at com.sap.engine.services.security.login.SecuritySessionPool.add(SecuritySessionPool.java:43)
  at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:314)
  at com.sap.engine.system.SystemLoginModule.login(SystemLoginModule.java:90)
  at sun.reflect.GeneratedMethodAccessor342.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:324)
  at javax.security.auth.login.LoginContext.invoke(LoginContext.java:675)
  at javax.security.auth.login.LoginContext.access$000(LoginContext.java:129)
  at javax.security.auth.login.LoginContext$4.run(LoginContext.java:610)
  at java.security.AccessController.doPrivileged(Native Method)
  at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:607)
  at javax.security.auth.login.LoginContext.login(LoginContext.java:534)
  at com.sap.security.core.logon.imp.SAPJ2EEAuthenticator.logon(SAPJ2EEAuthenticator.java:959)
  at com.sapportals.portal.prt.service.authenticationservice.AuthenticationService.login(AuthenticationService.java:367)
  at com.sapportals.portal.prt.connection.UMHandler.handleUM(UMHandler.java:126)
  at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:186)
  at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:540)
  at java.security.AccessController.doPrivileged(Native Method)
  at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:423)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
  at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
  at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
  at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
  at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
  at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
  at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
  at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
  at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
  at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
  at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
  at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
  at java.security.AccessController.doPrivileged(Native Method)
  at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
  at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

The error only occurs for some users (e. g. my one). The error does not occur, if I use a different client machine (e. g. a PC from a colleague).

We are using Internet Explorer 8.

Has anyone of you came along the same issue?

Regards,

Philipp

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos
PH
Participant
0 Kudos

Hi Kamil,

I already checked that note and also the solution described therein. Our settings were already correct.

Meanwhile, the error has disappeared - for whatever reason

Regards,

Philipp