Details

    • Type: Bug Bug
    • Status: Resolved Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 6.1.0pre0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
      Using the SslEnging connector using test webapp
    • Number of attachments :
      0

      Description

      I occassionally get messages like:

      bytesConsumed = 0 bytesProduced = 0
      2006-11-05 14:41:18.423::WARN: unwrap Status = BUFFER_OVERFLOW HandshakeStatus = NEED_UNWRAP

      The web app appears to work OK.

        Activity

        Hide
        nik gonzalez added a comment -

        This is a warning message when the call to unwrap in the fill method results in a BUFFER_OVERFLOW. SslEngine documentation states BUFFER_OVERFLOW after unwrapping means that there is not enough destination buffer space available and that it should be reallocated to the sslsession.getApplicationBufferSize. In our case, the destination buffer is the passed in buffer who's buffer size is already set. Since the passed in buffer's size has already been allocated elsewhere, I just threw an exception when I get a buffer_overflow instead of reallocating to the packetbuffersize. It didn't seem to have any adverse effects since all the tests I made against it have been working. Any suggestions on how to handle this better?

        Show
        nik gonzalez added a comment - This is a warning message when the call to unwrap in the fill method results in a BUFFER_OVERFLOW. SslEngine documentation states BUFFER_OVERFLOW after unwrapping means that there is not enough destination buffer space available and that it should be reallocated to the sslsession.getApplicationBufferSize. In our case, the destination buffer is the passed in buffer who's buffer size is already set. Since the passed in buffer's size has already been allocated elsewhere, I just threw an exception when I get a buffer_overflow instead of reallocating to the packetbuffersize. It didn't seem to have any adverse effects since all the tests I made against it have been working. Any suggestions on how to handle this better?
        Hide
        nik gonzalez added a comment -

        committed a fix in svn.

        The solution was to clear the destination when a buffer_overflow results from an unwrap. reference: http://download.java.net/jdk6/docs/technotes/guides/security/jsse/JSSERefGuide.html#OperationStatus

        Show
        nik gonzalez added a comment - committed a fix in svn. The solution was to clear the destination when a buffer_overflow results from an unwrap. reference: http://download.java.net/jdk6/docs/technotes/guides/security/jsse/JSSERefGuide.html#OperationStatus
        Hide
        Greg Wilkins added a comment -

        Nik... can you mark this issue as resolved?

        Show
        Greg Wilkins added a comment - Nik... can you mark this issue as resolved?

          People

          • Assignee:
            nik gonzalez
            Reporter:
            Greg Wilkins
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 2 hours
              2h