0 Replies Latest reply on Jan 3, 2008 2:29 AM by soon5

    Portal 2.6.2 + Cluster + CAS = Not Working ;-)

    soon5

      Hy There,

      I am testing with a CAS Server in a Clustered environment. First I tried to setup the HA Version of Portal 2.6.2 and access the same CAS Server with both portals. I got errors, and wrote that in an other Subject. In that Subject I was told, that currently Portal and CAS Server have to run on the same JBoss.

      My second try was, to setup two CAS Servers, one on each of my two portal nodes and configure each Portal to use the local CAS Server. When I try this, I get exceptions because the org.jboss.portal.identity.sso.cas.CASAuthenticationValve tries to set a non Serializable Object Attribute (which can't be session-replicated):

      08:18:30,203 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing
      java.lang.IllegalArgumentException: setAttribute: Non-serializable attribute
       at org.jboss.web.tomcat.service.session.ClusteredSession.setAttribute(ClusteredSession.java:535)
       at org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:130)
       at org.jboss.portal.identity.sso.cas.CASAuthenticationValve.invoke(CASAuthenticationValve.java:320)
       at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
       at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
       at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
       at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
       at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
       at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
       at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437)
       at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381)
       at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
       at java.lang.Thread.run(Thread.java:619)
      


      I just assume, that currently Portal is not able to handle both, CAS and Clustering at once.

      Greetings Soon5