Topic
  • 3 replies
  • Latest Post - ‏2010-02-04T12:05:24Z by flames
rshriv
rshriv
2 Posts

Pinned topic TAM for e-business WebSear Error Message in WebSphere Portal Applicaition!

‏2010-01-20T20:26:27Z |
I use to get " Error 0x38cf013d", DPWWA0317E The Request was too large to store in session cache. How to resolve this error or how to increase the session cache at TAM or WebSEAL side?.
Updated on 2010-02-04T12:05:24Z at 2010-02-04T12:05:24Z by flames
  • flames
    flames
    417 Posts

    Re: TAM for e-business WebSear Error Message in WebSphere Portal Applicaition!

    ‏2010-01-21T10:09:25Z  
    This usually happens as the standard TAI configuration for SSO to portal configures the junction to include iv-user and iv-groups. If
    iv-groups ( the number of groups the user is a member of ) gets large, you get this error.

    One way to resolve it is to remove iv-groups from the junction definition and the TAI setup, if this suits your requirements.
  • rshriv
    rshriv
    2 Posts

    Re: TAM for e-business WebSear Error Message in WebSphere Portal Applicaition!

    ‏2010-01-22T16:56:35Z  
    • flames
    • ‏2010-01-21T10:09:25Z
    This usually happens as the standard TAI configuration for SSO to portal configures the junction to include iv-user and iv-groups. If
    iv-groups ( the number of groups the user is a member of ) gets large, you get this error.

    One way to resolve it is to remove iv-groups from the junction definition and the TAI setup, if this suits your requirements.
    I am using iv_cred and iv_user in junction not iv_group. Is there any other setting for iv_cred and iv_user?.
  • flames
    flames
    417 Posts

    Re: TAM for e-business WebSear Error Message in WebSphere Portal Applicaition!

    ‏2010-02-04T12:05:24Z  
    • rshriv
    • ‏2010-01-22T16:56:35Z
    I am using iv_cred and iv_user in junction not iv_group. Is there any other setting for iv_cred and iv_user?.
    My mistake. I meant iv-creds, but the same suggestion applies. Depending on the version of TAI you're using, you may be able to do away with passing iv-creds across.

    Another options is to take a look at the max-webseal-header-size attribute which splits the headers into multiple headers, which should sort
    out.