Topic
  • 3 replies
  • Latest Post - ‏2007-07-16T10:25:18Z by gutsy_dev
SystemAdmin
SystemAdmin
30895 Posts

Pinned topic SSL peer shut down incorrectly

‏2007-05-24T17:26:02Z |
Hello all,

we're facing a configuration issue when connecting WebSphere Portal 6.0.1.0, using DB2 (8.2 FP 7) on Linux Red Hat Enterprise 4. After configuring LDAP security with Active Directory, including the SSL configuration part, we face the following exception on SystemOut.log (full stack trace attached):

javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
at com.ibm.jsse2.by.a(Unknown Source)
at com.ibm.jsse2.by.l(Unknown Source)
at com.ibm.jsse2.by.a(Unknown Source)
at com.ibm.jsse2.f.write(Unknown Source)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:86)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:144)
at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:420)
http://...
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at com.ibm.jsse2.a.a(Unknown Source)
... 68 more

  • Steps tried:
- changing port from 636 (SSL default) to 389

Did anyone face similar problems that might be due to an incorrect AD SSL certificate setup?

Thanks in advance
Updated on 2007-07-16T10:25:18Z at 2007-07-16T10:25:18Z by gutsy_dev
  • gutsy_dev
    gutsy_dev
    16 Posts

    Re: SSL peer shut down incorrectly

    ‏2007-07-12T14:01:59Z  
    Hi,

    I am also facing the same problem. Have you got any solution on this???

    I would appreciate you help in this.

    Regards,
    Dev
  • SystemAdmin
    SystemAdmin
    30895 Posts

    Re: SSL peer shut down incorrectly

    ‏2007-07-12T15:20:12Z  
    • gutsy_dev
    • ‏2007-07-12T14:01:59Z
    Hi,

    I am also facing the same problem. Have you got any solution on this???

    I would appreciate you help in this.

    Regards,
    Dev
    We had some hits from IBM support on this. They suggested to double-check the way AD was configured to accept client certs. An Enterprise root CA was eventually installed on AD and after importing this certificate to WAS the problem was solved.
  • gutsy_dev
    gutsy_dev
    16 Posts

    Re: SSL peer shut down incorrectly

    ‏2007-07-16T10:25:18Z  
    We had some hits from IBM support on this. They suggested to double-check the way AD was configured to accept client certs. An Enterprise root CA was eventually installed on AD and after importing this certificate to WAS the problem was solved.
    Hi Mapo,

    I have recreated an Enterprise root certificate and imported that on WAS. Still the portal is showing an error as earlier.

    Though my WAS console is working fine and allow me to login to that. Don't have any idea what could be the cause.