java.lang.Error

FATAL: replicated HTTP sessions specified but clustering not > enabled. > at weblogic.servlet.internal.session.SessionContext.getInstance(SessionContext. java:95) > at weblogic.servlet.internal.WebAppServletContext.initSessionContext(WebAppServ letContext.java:1239) > at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.jav a:874) > at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.j ava:823)

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web1464

  • FATAL: replicated HTTP sessions specified but clustering not > enabled. > at weblogic.servlet.internal.session.SessionContext.getInstance(SessionContext. java:95) > at weblogic.servlet.internal.WebAppServletContext.initSessionContext(WebAppServ
  • via Oracle Community by 3004, 2 weeks ago
    FATAL: replicated HTTP sessions specified but clustering not enabled.
  • via Oracle Community by 3004, 1 year ago
    FATAL: replicated HTTP sessions specified but clustering not en abled.
  • Stack trace

    • java.lang.Error: FATAL: replicated HTTP sessions specified but clustering not > enabled. > at weblogic.servlet.internal.session.SessionContext.getInstance(SessionContext. java:95) > at weblogic.servlet.internal.WebAppServletContext.initSessionContext(WebAppServ letContext.java:1239) > at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.jav a:874) > at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.j ava:823) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:444) at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:78) at weblogic.j2ee.Application.addComponent(Application.java:170) at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.