Results 1 to 1 of 1

Thread: Zimbra & CAS - Almost there...

  1. #1
    Join Date
    Jun 2011
    Rep Power

    Red face Zimbra & CAS - Almost there...

    First things first - Thank You cfremon for putting a sample of in CASifying Zimbra 6.0 with filled-in casServerLoginUrl, casServerUrlPrefix, and each serverName.

    I was almost mad from trying to figure out which to put in which - when I realized that unlike the original artikel in JASIG's website, the one here have those tags filled.

    I was able to move forward with my effort to CASify Zimbra. And it was also such a huge relief.
    Thanks again, cfremon

    Now to the point - unfortunately, I'm stuck in the last stage. After I authenticated by CAS, it redirected me back to Zimbra - which promptly complained :

    Internal Server Error.

    The server has encountered an internal error.
    Please try again later.

    ERROR: 500
    From my previous experience in setting up CAS with Liferay & Alfresco, an error here is usually caused by SSL. So, I enabled SSL debugging, by editing file /opt/zimbra/bin/zmmailboxdctl, editing the following lines :

         sudo ${zimbra_home}/libexec/zmmailboxdmgr start \
            ${mailboxd_java_options} ${spnegoJavaOptions} -Xms${javaXms}m \
             -Xmx${javaXmx}m -Xmn${javaXmn}m < /dev/null > /dev/null 2>&1
    Into :

         sudo ${zimbra_home}/libexec/zmmailboxdmgr start \
            ${mailboxd_java_options} ${spnegoJavaOptions} -Xms${javaXms}m \
     -Xmx${javaXmx}m -Xmn${javaXmn}m < /dev/null > /dev/null 2>&1

    The SSL trace was then logged into /opt/zimbra/log/zmmailboxd.out

    And here's something in it which I never saw before :

    Total time for which application threads were stopped: 0.0004080 seconds
    btpool0-7://, setSoTimeout(1) called
    btpool0-7://, handling exception: Read timed out
    btpool0-7://, setSoTimeout(60000) called
    btpool0-7://, setSoTimeout(300000) called
    btpool0-7://, WRITE: TLSv1 Application Data, length = 522
    btpool0-1, WRITE: TLSv1 Application Data, length = 718
    btpool0-7://, READ: TLSv1 Application Data, length = 734
    Total time for which application threads were stopped: 0.0001960 seconds
    To my knowledge, setSoTimeout(1) means that you set a timeout of 1 milisecond for the next Socket operation

    And indeed, the next socket operation failed straight away with error message "handling exception: Read timed out"

    I've looked again into the preauth.jsp source code, but failed to find anything which may cause it. It's probably somewhere else then.

    And here's where I stuck

    I've searched this forum, Googled everywhere with results even remotely resembling my problem, and so on. Still no clue whatsoever.

    I would be most grateful for any hint related to this issue.

    Last edited by sufehmi; 09-17-2011 at 08:49 AM. Reason: privacy

Similar Threads

  1. ZCS7 Beta only Listens on IPv6
    By tobru in forum Installation
    Replies: 2
    Last Post: 03-25-2011, 03:31 AM
  2. zmtlsctl give LDAP error
    By sourcehound in forum Administrators
    Replies: 5
    Last Post: 03-11-2007, 03:48 PM
  3. Replies: 8
    Last Post: 02-27-2007, 03:10 AM
  4. dspam logrotate errors
    By michaeln in forum Users
    Replies: 7
    Last Post: 02-19-2007, 11:45 AM
  5. huge log size
    By rmvg in forum Administrators
    Replies: 5
    Last Post: 01-02-2007, 09:39 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts