Weblogic server 10.3.5 error during SSL handshake

Please some one help to figure the issue with following logs.
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 33092690>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 33095418>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <33092490 SSL Version data invalid>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <Connection to SSL port from Sa-PC - 150.1.104.124 appears to be either unknown SSL version or maybe is plaintext>
<16-Jan-2013 18:40:40 o'clock GMT> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer Sa-PC - 150.1.104.124 during SSL handshake.>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 70
java.lang.Exception: New alert stack
     at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
     at com.certicom.tls.record.ReadHandler.getProtocolVersion(Unknown Source)
     at com.certicom.tls.record.ReadHandler.checkVersion(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
     at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
     at javax.net.ssl.impl.SSLSocketImpl.startHandshake(Unknown Source)
     at weblogic.server.channels.DynamicSSLListenThread$1.run(DynamicSSLListenThread.java:130)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <close(): 33092490>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <close(): 33092490>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.removeContext(ctx): 33092690>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <33095215 SSL Version data invalid>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <Connection to SSL port from Sa-PC - 150.1.104.124 appears to be either unknown SSL version or maybe is plaintext>
<16-Jan-2013 18:40:40 o'clock GMT> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer Sa-PC - 150.1.104.124 during SSL handshake.>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 70
java.lang.Exception: New alert stack
     at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
     at com.certicom.tls.record.ReadHandler.getProtocolVersion(Unknown Source)
     at com.certicom.tls.record.ReadHandler.checkVersion(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
     at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
     at javax.net.ssl.impl.SSLSocketImpl.startHandshake(Unknown Source)
     at weblogic.server.channels.DynamicSSLListenThread$1.run(DynamicSSLListenThread.java:130)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <close(): 33095215>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <close(): 33095215>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.removeContext(ctx): 33095418>
I just created domain with http and https ports. I installed an web app. When I am trying to access the app from browser through https the above error is occurring.
Please somebody help me.
Thanks in advance.
SK

This message indicates that the SSL connection is closed successfully. It is a warning message and normal to see in the logs when you enable the SSL debug flags. This is an expected behavior. If you see alerts when SSL debug is NOT ENABLED then it is a real alert and we need to take care of those issues. Also, it is not a real alert, it is a caught and handled exception from the certicom code which is not harmful and should be ignored, just because you have enabled the SSL debug flag. Once you turn it off, you won't see it in the logs.
Edited by: sharmela on Jan 22, 2013 4:55 AM

Similar Messages

  • Error during SSL handshake

    Hi,
    I am getting the "Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target" error during SSL handshake.
    I am implementing SSL authentication in custom JCA adapter. I have the keypairs in the DEFAULT view in keystorage and the public key of server in services_ssl view. I am able to access the certificated by doing a looklup. Below is the implementation
    KeystoreManager manager = (KeystoreManager)ctx.lookup("keystore");
    trustKeyStore = manager.getKeystore("service_ssl");
    keyStore = manager.getKeystore("DEFAULT);
    KeyManagerFactory kmfactory = KeyManagerFactory.getInstance(
    KeyManagerFactory.getDefaultAlgorithm());
    kmfactory.init(keyStore, null);
    KeyManager[] kmanager= kmfactory.getKeyManagers();
    TrustManagerFactory tmfactory = TrustManagerFactory.getInstance(
    TrustManagerFactory.getDefaultAlgorithm());
    tmfactory.init(trustKeyStore);
    TrustManager[] trustmanagers = tmfactory.getTrustManagers();
    SSLContext sslcontext = SSLContext.getInstance("SSL");
    sslcontext.init(keymanagers, trustManagers, null);
    I am able to get the contents of DEFAULT view and services_ssl view. When i try to connect to the server using httpClient.executeMethod() i am getting the below.
    Is this the correct way to initialize the SSL context? Any info on this will be really helpful.
    Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
         at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150)
         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1584)
         at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:174)
         at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:168)
         at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:848)
         at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:106)
         at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:495)
         at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:433)
         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:877)
         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1089)
         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:618)
         at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:59)
         at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
         at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
         at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:502)
         at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1973)
         at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993)
         at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:395)
         at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
         at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
         at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
         ... 10 more
    Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
         at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:221)
         at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:145)
         at sun.security.validator.Validator.validate(Validator.java:203)
         at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:172)
         at com.sun.net.ssl.internal.ssl.JsseX509TrustManager.checkServerTrusted(SSLContextImpl.java:320)
         at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:841)
         ... 27 more
    Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
         at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:236)
         at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:194)
         at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:216)
    Thanks

    You need to re-add the host using the mkhost command, that will rewrite the wallet for you.
    Thanks
    Rich

  • EAP-TLS or PEAP authentication failed during SSL handshake to the ACS serve

    We are running the LWAPP (2006 wlc's and 1242 AP's) and using the ACS 4.0 for authentication. Our users are
    experiencing an issue, where they are successfully authenticated the first time, however as the number of them is increasing, they're starting to drop the connections and being prompted to re-authenticate. At this point, they are not being able to authenticate again.
    We're using PEAP for the authentication and Win XP SP2 clients as the supplicants. The error message that we are seeing on the ACS for that controller is "EAP-TLS or PEAP authentication failed during SSL handshake to the ACS server"...Not sure if this error msg is relevant since we have other WLC's that are working OK and still generating the same error msg on the ACS...
    Thanks..

    Here are some configs you can try:
    config advanced eap identity-request-timeout 120
    config advanced eap identity-request-retries 20
    config advanced eap request-timeout 120
    config advanced eap request-retries 20
    save config

  • EAP-TLS or PEAP authentication failed during SSL handshake error

    I have 2 Windows 2003 ACS 3.2 servers. I am in the process of upgrading them to ACS 4.0. I am using them for WPA2/PEAP wireless authentication in a WDS environment. I recently upgraded one to ACS 4.0 and ever since that time some (not all) of my Windows XP clients have started to not be authenticated and logging the error "EAP-TLS or PEAP authentication failed during SSL handshake" on the ACS 4.0 server. During the upgrade (which was successful) I did change the Certificate since the current one was going to expire November 2007.
    The clients that do not authenticate on the ACS 4.0 server I can point to the ACS 3.2 server and they successfully authenticate there. I am able to resolve the issue by recreating the Windows XP PEAP profile for the wireless network and by getting a new client Cert. But, I have a couple of questions:
    Is the "EAP-TLS or PEAP authentication failed during SSL handshake" error due to the upgrade to ACS 4.0 or to the fact that I changed the Certificate, or both?
    Can this error ("EAP-TLS or PEAP authentication failed during SSL handshake") be resolved without me touching every Windows XP client (we have over 250+)?
    Thanks for the help

    My experience suggests that the problem is the certificate.
    I'm running ACS 3.3.
    I received the same error message when my clients copied the certificate to the wrong location, or otherwise did not correctly follow the provided instructions.
    Correctly following the instructions led to a successful connection and no more error message.

  • Microsoft SharePoint Server 2010 encountered an error during setup. One or more required office components failed to complete successfully.

    Hi,
    I got the below error while installing share point 2010 on Windows 7 OS.
    Microsoft SharePoint Server 2010 encountered an error during setup. One or more required office components failed to complete successfully.
    Trouble shooted by following link as below
    http://christopherborman.blogspot.in/2013/01/installing-sharepoint-2010-on-windows-7.html
    But still i am facing the same issue.Please share your inputs to cross this issue.
    Regards,
    Sudheer
    Thanks & Regards, Sudheer

    Hi,
    I selected Server Farm Mode,stand alone.
    Post that installation went fine.
    Regards,
    Sudheer 
    Thanks & Regards, Sudheer

  • EAP-TLS or PEAP authentication failed during SSL handshake

    Hi Pros,
                   I am a newbie in the ACS 4.2 and EAP-TLS implementation, with that being said. I face an issue during a EAP-TLS implementation. My search shows that this kind of error message is already certificate issue;However, I have deleted and recreated the certificate in both ACS and the client with the same result. I have deleted and re-install the certchain as well.
    When I check my log in the failed attemps, there is what I found:
    Date
    Time
    Message-Type
    User-Name
    Group-Name
    Caller-ID
    Network Access Profile Name
    Authen-Failure-Code
    Author-Failure-Code
    Author-Data
    NAS-Port
    NAS-IP-Address
    Filter Information
    PEAP/EAP-FAST-Clear-Name
    EAP Type
    EAP Type Name
    Reason
    Access Device
    Network Device Group
    06/23/2010
    17:39:51
    Authen failed
    000e.9b6e.e834
    Default Group
    000e.9b6e.e834
    (Default)
    EAP-TLS or PEAP authentication failed during SSL handshake
    1101
    10.111.22.24
    25
    MS-PEAP
    wbr-1121-zozo-test
    Office Networ
    06/23/2010
    17:39:50
    Authen failed
    [email protected]
    Default Group
    000e.9b6e.e834
    (Default)
    EAP-TLS or PEAP authentication failed during SSL handshake
    1098
    10.111.22.24
    25
    MS-PEAP
    wbr-1121-zozo-test
    Office Network
    [email protected] = my windows active directory name
    1. Why under EAP-TYPE it shows MS-PEAP not EAP-TLS? I did configure EAP-TLS....
    2. Why sometimes it just shows the MAC of the client for username?
    3. Why  it puts me in DEFAULT-GROUP even though i belongs to a group well definy in the acs?
    2. Secondly, When I check in pass authentications... there is what i saw
    Date
    Time
    Message-Type
    User-Name
    Group-Name
    Caller-ID
    NAS-Port
    NAS-IP-Address
    Network Access Profile Name
    Shared RAC
    Downloadable ACL
    System-Posture-Token
    Application-Posture-Token
    Reason
    EAP Type
    EAP Type Name
    PEAP/EAP-FAST-Clear-Name
    Access Device
    Network Device Group
    06/23/2010
    17:30:49
    Authen OK
    groszozo
    NOC Tier 2
    10.11.10.105
    1
    10.111.22.24
    (Default)
    wbr-1121-zozo-test
    Office Network
    06/23/2010
    17:29:27
    Authen OK
    groszozo
    NOC Tier 2
    10.11.10.105
    1
    10.111.22.24
    (Default)
    wbr-1121-zozo-test
    Office Network
    In the output below, it says that the user is authenticate and it puts the user in the right group with the right username, but the user never really authenticate. Maybe for the first few seconds when I initiate the connection.
    Before I forget, the suppliant is using WIN XP and 802.1x is enable. I even uncheck not verify the server and the ACS under External User Databases, I did  check ENABLE EAP-TLS machine authentication.
    Thanks in advance for your help,
    Crazy---

    Any ideas on this guys?? In my end, i've been reading some docs... Things started to make sens to me, but I still cannot authenticate, still the same errors. One more thing that catch my  attention now is the time it takes to open a telnet session to cisco device which has the ACS for auth server.
    My AD(Active Direct) and the ACS server are local same subnet(server subnet). Ping to the ACS from my desktop which is in different subnet is only take 1ms. To confirm that the issue is the ACS server, I decided to use another server in remote location, the telnet connection is way faster than the local ACS.
    Let's brain storm together to figure out this guys.
    Thanks in advance,
    ----Paul

  • EAP-TLS or PEAP authentication failed due to unknown CA certificate during SSL handshake

    Hi All ,
                 I am trying to test EAP_TLS authentication on acs 4.2.1.15 running on Appliance 1120 , I have installed my server certficate along with CA certficate on my appliance box , I have enabled features of  EAP_TLS under golbal authentication setup .
                 I have downloaded client supplicant certficate file for my windows XP machine .
    When i tried to authenticated i am finding following error message under  failed attempts(EAP-TLS or PEAP authentication failed due to unknown CA certificate during SSL handshake) on my acs appliance box .
    Under certficate revocation list , I have forced my CA as CRL in use . Attached snap shot of all .
    Suggest me whether i need to enable all corresponding CA certficate undercertficate trust list , Kindly let me know were i am doing wrong on this ..

    Hello,
    I am NO expert on certificates but I have seen your error dozens of times from wireless clients on my Cisco ACS 4.2 Radius server.
    Through trial and error I wrote up this procedure for our Helpdesk for installing certs in Windows XP and Windows 7. These steps haven't failed me yet and the Helpdesk doesn't bother me as much anymore so see if this helps you:
    -          Manually install the Global CA under BOTH Trusted Root Certification Authorities\Certificates AND Intermediate Certification                      Authorities\Certificates
    -          Manually install the Intermediate CA under JUST the Intermediate Certification Authorities\Certificates
    -          Delete the wireless network from the computer
    -          REBOOT!!
    -          Open the Microsoft Management Console, “mmc”.
    -          Go FILE\Add Remove SnapIn. Select Certificates ..
    -          If promoted, do it for “My User Account”.
    -          Make sure the certificates are where you put them. 
    -          If you see any of these exact certificates out of place in either Trusted Root Certification Authorities\Certificates or Intermediate Certification                      Authorities\Certificates, remove them.
    -          Redo wireless network setup again
    I hope this helps you.
    Mike

  • Error during SSL installation on weblogic 8.1

    Hi
    I'm getting an error during the installation of SSL certificate.
    After importing the keystore, configuring the webserver and rebooting the webserver, I'm getting identity certificate expired error in the webserver logs.Due to this i'm unable to access the HTTPS URL.
    But when i check the keystore, the validity of the certificate is there till 2010.I'm using WEBLOGIC 8.1

    If you get (for example) a 128-bit SSL certificate from Verisign you need to specify a Certificate Signing Request (CSR). This is unique for each server. If you have upgraded your server and the CSR generated from the weblogic CSR generator servlet is the same as it was in the previous version, then I guess you can use the same certificate. If the CSR has changed then I think you will need to replace the certificate, this costs $100. If it's been less than 30 days since your certificate was issued, it's free.

  • WebLogic Server 10.0 MP1: Error in resource adapter deployment

    When I try to deploy our (own implemented) resource adapter into WebLogic Server 10.0 MP1, I get the following error message:
    An error occurred during activation of changes, please see the log for details.
    weblogic.security.service.InvalidParameterException: weblogic.security.service.SecurityServiceException: [Security:090198]No appropriate constructor for java.util.logging.LoggingPermission
    java.util.logging.LoggingPermission.(java.lang.String)
    The same adapter works flawless with Oracle AS/OC4J, JBoss 4.2 and Glassfish V2.
    In the security-permission-spec element of our ra.xml file we use (beside others) the following permissions:
    permission javax.management.MBeanTrustPermission "register";
    permission java.util.logging.LoggingPermission "control";
    When I delete this two lines from the security-permission-spec element, I can deploy the adapter in WebLogic.
    For me this seems to be a bug in WebLogic 10.0MP1.
    Best,
    Manfred

    Re: Installation error: Weblogic Server 10.0 MP2

  • Weblogic server 5.1 startup error

    I am using weblogic 5.1 on Solaris 8 (intel) for testing
    when I start up the server, the following error prompt out
    java.lang.UnsatisfiedLinkError: no jsafe in java.library.path
    at java.lang.Throwable.fillInStackTrace(Native Method)
    at java.lang.Throwable.fillInStackTrace(Compiled Code)
    at java.lang.Throwable.<init>(Compiled Code)
    at java.lang.Error.<init>(Error.java:50)
    at java.lang.LinkageError.<init>(LinkageError.java:43)
    at
    java.lang.UnsatisfiedLinkError.<init>(UnsatisfiedLinkError.java:42)
    at java.lang.ClassLoader.loadLibrary(Compiled Code)
    at java.lang.Runtime.loadLibrary0(Runtime.java:473)
    at java.lang.System.loadLibrary(Compiled Code)
    at COM.rsa.jsafe.JSAFE_DeviceBuilderNative.buildObjects(Compiled
    Code)
    at
    COM.rsa.jsafe.JSAFE_AsymmetricCipher.getInstance(JSAFE_AsymmetricCipher.java
    at COM.rsa.jsafe.JSAFE_AsymmetricCipher.getInstance(Compiled Code)
    at weblogic.security.RSA.performOPJSafe(Compiled Code)
    at weblogic.security.RSA.performOp(RSA.java:104)
    at weblogic.security.RSApkcs1.decrypt(Compiled Code)
    at weblogic.security.RSAMDSignature.verify(RSAMDSignature.java:87)
    at weblogic.security.X509.verifySignature(X509.java:223)
    at
    weblogic.t3.srvr.SSLListenThread.insertIntoCAChain(SSLListenThread.java:192)
    at weblogic.t3.srvr.SSLListenThread.<init>(Compiled Code)
    at weblogic.t3.srvr.SSLListenThread.<init>(Compiled Code)
    at weblogic.t3.srvr.T3Srvr.start(Compiled Code)
    at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:825)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.Server.startServerDynamically(Server.java:140)
    at weblogic.Server.main(Compiled Code)
    at weblogic.Server.main(Server.java:58)
    The java.library.path is
    /usr/java/bin/../jre/bin/../lib/i386:/opt/weblogic/lib/solaris/oci815_8:/opt
    /weblogic/lib/solaris:/usr/lib
    and i am using JSK 1.2.2_07a
    Please help
    Fannie

    That's JVM crash, which is not supposed to happen ;-) You can try to search
    www.javasoft.com for answers, but it looks like Intel Solaris is not terribly
    popular or supported. Did you try to run WebLogic on Linux instead ?
    Fannie <[email protected]> wrote:
    After I add the command to startWebLogic.sh, the server can start up
    properly.
    When I try to test the jsp page through the browser
    The following error message prompt and the server shutdown
    Please help!
    Fannie
    SIGSEGV 11 segmentation violation
    si_signo [11]: SEGV
    si_errno [0]:
    si_code [1]: SEGV_MAPERR [addr: 0x2]
    stackpointer=D639E440
    "SSLListenThread" (TID:0x91a7d28, sys_thread_t:0x91a7c70, state:R, thread_t:
    t@30, threadID:0xd5f50d74, stack_bottom:0xd5f51000, stack_size:0x20000)
    prio=5
    [1] java.net.PlainSocketImpl.socketAccept(Native Method)
    [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:413)
    [3] java.net.ServerSocket.implAccept(ServerSocket.java:241)
    [4] java.net.ServerSocket.accept(ServerSocket.java:223)
    [5]
    weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java
    :121)
    [6] weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:112)
    [7] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
    "ListenThread" (TID:0x9171528, sys_thread_t:0x9171470, state:R, thread_t:
    t@29, threadID:0xd5f80d74, stack_bottom:0xd5f81000, stack_size:0x20000)
    prio=5
    [1] java.net.PlainSocketImpl.socketAccept(Native Method)
    [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:413)
    [3] java.net.ServerSocket.implAccept(ServerSocket.java:241)
    [4] java.net.ServerSocket.accept(ServerSocket.java:223)
    [5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
    "ExecuteThread-14" (TID:0x867b8e8, sys_thread_t:0x867b830, state:CW,
    thread_t: t@24, threadID:0xd6320d74, stack_bottom:0xd6321000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-13" (TID:0x86810e8, sys_thread_t:0x8681030, state:CW,
    thread_t: t@23, threadID:0xd6370d74, stack_bottom:0xd6371000,
    stack_size:0x20000) prio=5
    [1] weblogic.common.internal.DynaQueue.getW(DynaQueue.java:219)
    [2] weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:177)
    [3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    [4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-12" (TID:0x872cd20, sys_thread_t:0x872cc68, state:R,
    thread_t: t@22, threadID:0xd63a0d74, stack_bottom:0xd63a1000,
    stack_size:0x20000) prio=5 current thread
    [1] weblogic.servlet.jsp.JspLexer.mPAGE_DIRECTIVE(JspLexer.java:3344)
    [2] weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3174)
    [3] weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1636)
    [4] weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1477)
    [5] weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1356)
    [6] weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:786)
    [7] weblogic.servlet.jsp.JspParser.doit(JspParser.java:57)
    [8] weblogic.servlet.jsp.JspParser.parse(JspParser.java:109)
    [9] weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
    [10] weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:235)
    [11] weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:198)
    [12] weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:174)
    [13]
    weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:16
    4)
    [14]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :99)
    [15]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :123)
    [16]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:742)
    [17]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:686)
    [18]
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:247)
    [19]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
    [20] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
    [21] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-11" (TID:0x86c80e8, sys_thread_t:0x86c8030, state:CW,
    thread_t: t@21, threadID:0xd63f0d74, stack_bottom:0xd63f1000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-10" (TID:0x8745218, sys_thread_t:0x8745160, state:CW,
    thread_t: t@20, threadID:0xd6fb0d74, stack_bottom:0xd6fb1000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-9" (TID:0x867bce8, sys_thread_t:0x867bc30, state:CW,
    thread_t: t@19, threadID:0xd6ff0d74, stack_bottom:0xd6ff1000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-8" (TID:0x8742098, sys_thread_t:0x8741fe0, state:CW,
    thread_t: t@18, threadID:0xd7920d74, stack_bottom:0xd7921000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-7" (TID:0x8740ed8, sys_thread_t:0x8740e20, state:CW,
    thread_t: t@17, threadID:0xd7970d74, stack_bottom:0xd7971000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-6" (TID:0x86f40e8, sys_thread_t:0x86f4030, state:CW,
    thread_t: t@16, threadID:0xd79a0d74, stack_bottom:0xd79a1000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-5" (TID:0x873dd58, sys_thread_t:0x873dca0, state:CW,
    thread_t: t@15, threadID:0xd79e0d74, stack_bottom:0xd79e1000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-4" (TID:0x86ff4e8, sys_thread_t:0x86ff430, state:CW,
    thread_t: t@14, threadID:0xd86b0d74, stack_bottom:0xd86b1000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-3" (TID:0x86ffce8, sys_thread_t:0x86ffc30, state:CW,
    thread_t: t@13, threadID:0xd8700d74, stack_bottom:0xd8701000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-2" (TID:0x87134e8, sys_thread_t:0x8713430, state:CW,
    thread_t: t@12, threadID:0xd8730d74, stack_bottom:0xd8731000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-1" (TID:0x8739c70, sys_thread_t:0x8739bb8, state:CW,
    thread_t: t@11, threadID:0xd8760d74, stack_bottom:0xd8761000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-0" (TID:0x8739a68, sys_thread_t:0x87399b0, state:CW,
    thread_t: t@10, threadID:0xd8790d74, stack_bottom:0xd8791000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "TimeEventGenerator" (TID:0x869a220, sys_thread_t:0x869a168, state:CW,
    thread_t: t@9, threadID:0xd87c0d74, stack_bottom:0xd87c1000,
    stack_size:0x20000) prio=5
    [1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:249)
    [2]
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
    :131)
    [3] java.lang.Thread.run(Thread.java:479)
    "SpinnerRandomSource" (TID:0x86e8218, sys_thread_t:0x86e8160, state:CW,
    thread_t: t@8, threadID:0xd87f0d74, stack_bottom:0xd87f1000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2]
    weblogic.security.SpinnerThread.stopSpinning(SpinnerRandomBitsSource.java:10
    2)
    [3] weblogic.security.SpinnerThread.run(SpinnerRandomBitsSource.java:116)
    Exiting Thread (sys_thread_t:0xdfb7c29c) : no stack
    "Finalizer" (TID:0x81e3940, sys_thread_t:0x81e3888, state:CW, thread_t: t@6,
    threadID:0xdf4e0d74, stack_bottom:0xdf4e1000, stack_size:0x20000) prio=8
    [1] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:146)
    [2] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:168)
    [3]
    java.lang.ref.Finalizer$FinalizerWorker$FinalizerThread.run(Finalizer.java:1
    24)
    "Reference Handler" (TID:0x81da690, sys_thread_t:0x81da5d8, state:CW,
    thread_t: t@5, threadID:0xdf510d74, stack_bottom:0xdf511000,
    stack_size:0x20000) prio=10
    [1] java.lang.Object.wait(Object.java:424)
    [2] java.lang.ref.Reference$ReferenceHandler.run(Reference.java:130)
    "Signal dispatcher" (TID:0x81a0ea8, sys_thread_t:0x81a0df0, state:MW,
    thread_t: t@4, threadID:0xdf670d74, stack_bottom:0xdf671000,
    stack_size:0x20000) prio=10
    "main" (TID:0x8061728, sys_thread_t:0x8061670, state:CW, thread_t: t@1,
    threadID:0x804c178, stack_bottom:0x8048000, stack_size:0x848000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:1784)
    [3] java.lang.reflect.Method.invoke(Native Method)
    [4] weblogic.Server.startServerDynamically(Server.java:148)
    [5] weblogic.Server.main(Server.java:66)
    [6] weblogic.Server.main(Server.java:58)
    "Dimitri Rakitine" <[email protected]> ¼¶¼g©ó¶l¥ó
    news:[email protected]...
    I do not think there are shared libs for WebLogic on Solaris/Intel.
    You can try disabling native SSL by adding this to WebLogic startup
    command line: -Dweblogic.security.SSL.useJava=true
    Fannie <[email protected]> wrote:
    I am using weblogic 5.1 on Solaris 8 (intel) for testing
    when I start up the server, the following error prompt out
    java.lang.UnsatisfiedLinkError: no jsafe in java.library.path
    at java.lang.Throwable.fillInStackTrace(Native Method)
    at java.lang.Throwable.fillInStackTrace(Compiled Code)
    at java.lang.Throwable.<init>(Compiled Code)
    at java.lang.Error.<init>(Error.java:50)
    at java.lang.LinkageError.<init>(LinkageError.java:43)
    at
    java.lang.UnsatisfiedLinkError.<init>(UnsatisfiedLinkError.java:42)
    at java.lang.ClassLoader.loadLibrary(Compiled Code)
    at java.lang.Runtime.loadLibrary0(Runtime.java:473)
    at java.lang.System.loadLibrary(Compiled Code)
    at COM.rsa.jsafe.JSAFE_DeviceBuilderNative.buildObjects(Compiled
    Code)
    at
    COM.rsa.jsafe.JSAFE_AsymmetricCipher.getInstance(JSAFE_AsymmetricCipher.java
    at COM.rsa.jsafe.JSAFE_AsymmetricCipher.getInstance(CompiledCode)
    at weblogic.security.RSA.performOPJSafe(Compiled Code)
    at weblogic.security.RSA.performOp(RSA.java:104)
    at weblogic.security.RSApkcs1.decrypt(Compiled Code)
    atweblogic.security.RSAMDSignature.verify(RSAMDSignature.java:87)
    at weblogic.security.X509.verifySignature(X509.java:223)
    at
    weblogic.t3.srvr.SSLListenThread.insertIntoCAChain(SSLListenThread.java:192)
    at weblogic.t3.srvr.SSLListenThread.<init>(Compiled Code)
    at weblogic.t3.srvr.SSLListenThread.<init>(Compiled Code)
    at weblogic.t3.srvr.T3Srvr.start(Compiled Code)
    at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:825)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.Server.startServerDynamically(Server.java:140)
    at weblogic.Server.main(Compiled Code)
    at weblogic.Server.main(Server.java:58)
    The java.library.path is
    /usr/java/bin/../jre/bin/../lib/i386:/opt/weblogic/lib/solaris/oci815_8:/opt
    /weblogic/lib/solaris:/usr/lib
    and i am using JSK 1.2.2_07a
    Please help
    Fannie--
    Dimitri
    Dimitri

  • Weblogic server failed to start errors BEA-000362 & BEA-000365

    Hi Friends,
    I'm trying to start weblogic server after starting admin server.I'm getting the below error after
    running the command:
    $ ./startManagedWebLogic.sh
    <Jul 29, 2011 10:09:54 AM IST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    <Jul 29, 2011 10:09:55 AM IST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    <Jul 29, 2011 10:09:57 AM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.1.3-11-141760-1.6.0_24-20110301-1430-linux-ia32 from Oracle Corporation>
    <Jul 29, 2011 10:09:58 AM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
    <Jul 29, 2011 10:09:58 AM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.management.ManagementException: [Management:141247]The configuration directory /Middleware/SOASuite11gR1/wlserver_10.3/common/bin/config does not exist and the admin server is not available.
    at weblogic.management.provider.internal.RuntimeAccessImpl.parseNewStyleConfig(RuntimeAccessImpl.java:200)
    at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:115)
    at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:42)
    at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
    at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
    at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:882)
    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:572)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
    at weblogic.Server.main(Server.java:71)
    >
    <Jul 29, 2011 10:09:58 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Jul 29, 2011 10:09:58 AM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Jul 29, 2011 10:09:58 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    Do you have any idea how to resolve this error and start weblogic server succesfuly.
    Best regards,
    Edited by: user13311731 on Jul 28, 2011 10:45 PM

    Hi,
    Try starting the managed server with parameters:
    ./startManagedWebLogic.sh myManagedServerName http://serverName:7001
    Does that make a difference?
    Regards Peter

  • I can't install weblogic server 10.3 found error

    I have install to 65% and found error.
    i want to know why i can't install weblogic server 10.3 (may be error was create by jdk or anything else Please tell me! )
    and how many  problem  that can happen when install weblogic server 10.3
    ps. - OS that i install is windowsXP  sp2

    Without giving us any details about what error you got, or any circumstances of your environment (just the OS isn't enough), there is no way anyone could give you any help.

  • WebLogic Server 5.1 giving errors of code 500

    Hi,
              We have a system consisting of WebLogic Server 5.1 running on Sparc Solaris and
              JDK 1.2.2 that is going to go into production soon. It houses JSPs and some
              servlets (some of the servlets are JMS clients). The EJBs are kept on another
              Sparc Solaris machine with the same version of WebLogic Server and JDK.
              So far, the EJBs are running fine. However, it is noticed that after running for
              one or two days, the instance of WebLogic Server that houses JSPs would give
              the HTTP error code of 500 whenever it was contacted through a browser. The JMS
              clients in the instance appeared to have stopped, as they did not print out
              texts that were supposed to be shown whenver a message is received. The error
              code of 500 was given for both JSP and HTML accesses. The system would not
              recover from that condition even if it was left running for a few more hours.
              Attaching the WebLogic Server Console to the instance of WebLogic Server
              concerned did not reveal any possible cause, and the console appeared to
              function correctly by providing information on system threads and JSP names
              etc. weblogic.log, access.log and the console output (the messages written by
              WebLogic Server to the terminal where it was started) did not reveal anything
              unusual.
              Wondering if anyone has encountered the same problem. Will appreciate any
              help.
              Thanks in advance.
              Hann Wei
              

    Hann
              Before upgrading to service pack 6 for WebLogic Server 5.1. After first
              starting up the WLS, a user would see our index.html, but then would see
              error code 500 when trying to access the first JSP. A user would have to
              hit the browser back button and try again and the first JSP page would come
              up.
              I would suggest that you see if service pack 6 will have any impact on your
              problem, and see if that helps your situation.
              John J. Feigal Voice (651)766-8787 (main)
              Sr. Technical Consultant (651)766-7249 (direct)
              Ensodex, Inc. Fax (651)766-8792
              4105 N. Lexington Ave., Suite 150 email [email protected]
              Arden Hills, MN 55126 WebSite http://www.ensodex.com
              "Hann Wei Toh" <[email protected]> wrote in message
              news:[email protected]..
              > The systems have service pack 5 applied.
              >
              > Hann Wei
              

  • ID, IR error when try to login (JNDI error) during SSL configuration

    I'm in the process to configure SSL on SAP J2EE Engine. I'm following the document of SAP library and "Enabling SSL and client certificates on SAP J2EE Engine" by Angel Dichev of RIG, SAP Labs.
    I deployed the SAP Java Cryptographic Toolkit and update the unlimited strength jurisdiction policy files.
    As per document, I changed the default setting from SSL provider service for the Dispatcher from manual start to always start.
    After this step, I have problems to log in IR and ID ( SLD and RWB are working), getting the follow errors ( after click on ID or IR, got the login screen for user/pwd and after entering getting the error):
    "Unable to map from JNDI delivered class com.sap.engine.services.jndi.persistent.UnsatisfiedReferenceImpl to class com.sap.aii.ib.sbeans.login.LoginServiceHome registered during login service"
    Any solution of this problem?
    Regards
    Amar

    Thanks Ravi
    I created the certificate and then it work for one day. Today morning, i received the certificate request response from SAP trust centre and imported into our server.
    I have inported into Key storage of visual admin as per guide. Is there any other place to check it?
    Again logon to IB fail with the same error.
    Any idea?
    Regards
    Amar

  • Netscape Directory Server closes LDAPS connection during SSL handshake

    I'm trying to bind to a NDS 6.2 LDAP server over SSL using the 1.4.2_03 JNDI LDAP provider,
    but I can't get past the initial TSL handshake: it throws a "Remote host closed connection
    during handshake" exception. The JSSE FAQ mentions this as likely a problem with
    protocol incompatibilities (e.g. SSL3 vs. TLS1), but I can't seem to force the LDAP provider
    to use an older protocol to investigate this further.
    Here are the environment parameters I'm passing
      java.naming.provider.url=ldap://ldaphost:636/o=foo,ou=bar 
      java.naming.security.principal=cn=foobar
      java.naming.security.credentials=password
      java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory
      java.naming.security.authentication=simple
      java.naming.security.protocol=ssland the associated JSSE debug trace follows.
    Any ideas? Do I need to create some custom socket factory to mess with protocols?
    pch
    ================
    keyStore is :
    keyStore type is : jks
    init keystore
    init keymanager of type SunX509
    trustStore is: C:\tools\jdk1.4.2\jre\lib\security\jssecacerts
    trustStore type is : jks
    init truststore
    adding as trusted cert:
      Subject: [email protected], CN=Petes Bait and Tackle Class Z CA, O=Petes Bait and Tackle, L=Falls Church, ST=Virginia, C=US
      Issuer:  [email protected], CN=Petes Bait and Tackle Class Z CA, O=Petes Bait and Tackle, L=Falls Church, ST=Virginia, C=US
      Algorithm: RSA; Serial number: 0x0
      Valid from Thu Jun 24 13:24:27 EDT 2004 until Fri Jun 24 13:24:27 EDT 2005
    init context
    trigger seeding of SecureRandom
    done seeding SecureRandom
    %% No cached client session
    *** ClientHello, TLSv1
    RandomCookie:  GMT: 1071325469 bytes = { 1, 25, 191, 168, 187, 165, 118, 46, 45, 64, 183, 165, 131, 120, 155, 107, 208, 170, 19, 80, 74, 234, 177, 118, 51, 83, 194, 158 }
    Session ID:  {}
    Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA]
    Compression Methods:  { 0 }
    [write] MD5 and SHA1 hashes:  len = 73
    0000: 01 00 00 45 03 01 40 DB   21 1D 01 19 BF A8 BB A5  ...E..@.!.......
    0010: 76 2E 2D 40 B7 A5 83 78   9B 6B D0 AA 13 50 4A EA  [email protected].
    0020: B1 76 33 53 C2 9E 00 00   1E 00 04 00 05 00 2F 00  .v3S........../.
    0030: 33 00 32 00 0A 00 16 00   13 00 09 00 15 00 12 00  3.2.............
    0040: 03 00 08 00 14 00 11 01   00                       .........
    main, WRITE: TLSv1 Handshake, length = 73
    [write] MD5 and SHA1 hashes:  len = 98
    0000: 01 03 01 00 39 00 00 00   20 00 00 04 01 00 80 00  ....9... .......
    0010: 00 05 00 00 2F 00 00 33   00 00 32 00 00 0A 07 00  ..../..3..2.....
    0020: C0 00 00 16 00 00 13 00   00 09 06 00 40 00 00 15  ............@...
    0030: 00 00 12 00 00 03 02 00   80 00 00 08 00 00 14 00  ................
    0040: 00 11 40 DB 21 1D 01 19   BF A8 BB A5 76 2E 2D 40  ..@.!.......v.-@
    0050: B7 A5 83 78 9B 6B D0 AA   13 50 4A EA B1 76 33 53  ...x.k...PJ..v3S
    0060: C2 9E                                              ..
    main, WRITE: SSLv2 client hello message, length = 98
    main, received EOFException: error
    main, handling exception: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
    main, SEND TLSv1 ALERT:  fatal, description = handshake_failure
    main, WRITE: TLSv1 Alert, length = 2
    main, called closeSocket()

    My first suggestion is to find an log on de NDS server (maybe it states a reason for the closing the connection)
    Otherwise use Ethereal to examen the trafic between the to machines. Maybe that helps.
    Or check if the NDS wants 2-way authentication and is trying to get your certificate as wel.

Maybe you are looking for