Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4850890

SSL exception : Received close_notify during handshake

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: P4 P4
    • None
    • 1.4.1_02
    • security-libs
    • None

      The following exception was observed while running S1MQ longevity test with
      SSL transport. This happens randomly - most of the connection attempts
      are successful.

      The test was run on a Solaris 10 MP machine with JDK 1.4.1_02.

      We have already verified that this bug does NOT occur with JDK 1.4.2 beta. We will
      also try running the same test with 1.4.1_03 and update this bug description..

      The impact on S1MQ is limited - it means occasionally the JMS clients will get a
      connection exception but if they try again the connection usually goes through..

      Here is the stack trace obtained using JMSException.getLinkedException.printStackTrace()..

      javax.net.ssl.SSLException: Received close_notify during handshake
              at com.sun.net.ssl.internal.ssl.BaseSSLSocketImpl.a(DashoA6275)
              at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275)
              at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275)
              at com.sun.net.ssl.internal.ssl.SSLSocketImpl.b(DashoA6275)
              at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275)
              at com.sun.net.ssl.internal.ssl.SSLSocketImpl.j(DashoA6275)
              at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275)
              at com.sun.net.ssl.internal.ssl.AppOutputStream.write(DashoA6275)
              at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:69)
              at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:127)
              at com.sun.messaging.jmq.io.ReadOnlyPacket.writePacket(ReadOnlyPacket.java:421)
              at com.sun.messaging.jmq.io.ReadWritePacket.writePacket(ReadWritePacket.java:72)
              at com.sun.messaging.jmq.jmsclient.ProtocolHandler.writePacketNoAck(ProtocolHandler.java:203)
              at com.sun.messaging.jmq.jmsclient.ProtocolHandler.writePacketWithAck(ProtocolHandler.java:391)
              at com.sun.messaging.jmq.jmsclient.ProtocolHandler.writePacketWithReply2(ProtocolHandler.java:277)
              at com.sun.messaging.jmq.jmsclient.ProtocolHandler.hello(ProtocolHandler.java:588)
              at com.sun.messaging.jmq.jmsclient.ConnectionImpl.hello(ConnectionImpl.java:238)
              at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1512)
              at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:403)
              at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:234)
              at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
              at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
              at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
              at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:57)
              at Longevity.SyncUp.SyncUpwithSubscriber(SyncUp.java:27)
              at Longevity.LongevityProducer.UpdateCount(LongevityProducer.java:127)
              at Longevity.SessionsThread.doProduceMessage(SessionsThread.java:457)
              at Longevity.SessionsThread.run(SessionsThread.java:82)

      ###@###.### 2003-04-18
      ###@###.### 2003-04-18

            wetmore Bradford Wetmore
            duke J. Duke
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: