Error in SDK 1.4.0 SSL

Hi,
I have an application running on Linux Slackware 8.1, using SDK 1.4.0
Every couple of days this error occurs, and the server dies (which is really bad for something I want to just sit there, and do stuff without needing to baby sit it).
This error does not occur with any other Platform that it has been run on however, and it seems to be a pretty low level error.
Can someone explain to me what this error is, and whether upgrading to SDK 1.4.1 would correct it? (I could not find any similar errors in the Bug database :( )
Thanks :)

Sorry, forgot to paste the error.
The error I got was:
Unexpected Signal : 11 occurred at PC=0x403F2089
Function=is_address__C11LIR_OprDesc+0x21
Library=/home/database/j2sdk1.4.0/jre/lib/i386/client/libjvm.so
Current Java thread:
     at java.math.BigInteger.oddModPow(BigInteger.java:1554)
     at java.math.BigInteger.modPow(BigInteger.java:1452)
     at sun.security.provider.DSA.generateV(DSA.java:279)
     at sun.security.provider.DSA.engineVerify(DSA.java:229)
     at sun.security.provider.DSA.engineVerify(DSA.java:187)
     at java.security.Signature.verify(Signature.java:464)
     at sun.security.x509.X509CertImpl.verify(X509CertImpl.java:397)
     at sun.security.x509.X509CertImpl.verify(X509CertImpl.java:361)
     at javax.crypto.SunJCE_b.e(DashoA6275)
     at javax.crypto.SunJCE_b.<clinit>(DashoA6275)
     at javax.crypto.Cipher.getInstance(DashoA6275)
     at com.sun.net.ssl.internal.ssl.SunJSSE_w.a(DashoA6275)
     at com.sun.net.ssl.internal.ssl.SunJSSE_ax.<init>(DashoA6275)
     at com.sun.net.ssl.internal.ssl.SunJSSE_aw.a(DashoA6275)
     at com.sun.net.ssl.internal.ssl.SunJSSE_av.<init>(DashoA6275)
     at com.sun.net.ssl.internal.ssl.ClientHandshaker.a(DashoA6275)
     at
com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(DashoA6275)
     at
com.sun.net.ssl.internal.ssl.Handshaker.process_record(DashoA6275)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275)
     - locked <0x4461f908> (a
com.sun.net.ssl.internal.ssl.SSLSocketImpl)
     - locked <0x4461f980> (a java.lang.Object)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275)
     - locked <0x4461f988> (a java.lang.Object)
     at
com.sun.net.ssl.internal.ssl.AppOutputStream.write(DashoA6275)
     - locked <0x4461f9b8> (a
com.sun.net.ssl.internal.ssl.AppOutputStream)
     at java.io.OutputStream.write(OutputStream.java:58)
     at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(DashoA6275)
     - locked <0x4461f908> (a
com.sun.net.ssl.internal.ssl.SSLSocketImpl)
     at webpay.client.Webpay.connect(Webpay.java:331)
     at webpay.client.Webpay.initTransaction(Webpay.java:399)
     at webpay.client.Webpay.execute(Webpay.java:378)
     at anz4.main(anz4.java:150)
Dynamic libraries:
08048000-0804d000 r-xp 00000000 03:01 1010991
/home/database/j2sdk1.4.0/bin/java
0804d000-0804e000 rw-p 00004000 03:01 1010991
/home/database/j2sdk1.4.0/bin/java
40000000-40014000 r-xp 00000000 03:01 43 /lib/ld-2.2.5.so
40014000-40015000 rw-p 00013000 03:01 43 /lib/ld-2.2.5.so
40015000-40017000 r--s 00000000 03:01 1467413
/home/database/j2sdk1.4.0/jre/lib/ext/dnsns.jar
40018000-40026000 r-xp 00000000 03:01 63 /lib/libpthread-0.9.so
40026000-4002d000 rw-p 0000e000 03:01 63 /lib/libpthread-0.9.so
4002d000-4002f000 r-xp 00000000 03:01 51 /lib/libdl-2.2.5.so
4002f000-40030000 rw-p 00001000 03:01 51 /lib/libdl-2.2.5.so
40030000-40149000 r-xp 00000000 03:01 46 /lib/libc-2.2.5.so
40149000-4014f000 rw-p 00119000 03:01 46 /lib/libc-2.2.5.so
40153000-40416000 r-xp 00000000 03:01 1206567
/home/database/j2sdk1.4.0/jre/lib/i386/client/libjvm.so
40416000-4055e000 rw-p 002c2000 03:01 1206567
/home/database/j2sdk1.4.0/jre/lib/i386/client/libjvm.so
40572000-40584000 r-xp 00000000 03:01 54 /lib/libnsl-2.2.5.so
40584000-40585000 rw-p 00011000 03:01 54 /lib/libnsl-2.2.5.so
40587000-405bb000 r-xp 00000000 03:01 586951
/usr/i386-slackware-linux/lib/libstdc++-2-libc6.1-1-2.9.0.so
405bb000-405c7000 rw-p 00033000 03:01 586951
/usr/i386-slackware-linux/lib/libstdc++-2-libc6.1-1-2.9.0.so
405c9000-405e9000 r-xp 00000000 03:01 52 /lib/libm-2.2.5.so
405e9000-405ea000 rw-p 0001f000 03:01 52 /lib/libm-2.2.5.so
405ea000-405f3000 r-xp 00000000 03:01 2282670
/home/database/j2sdk1.4.0/jre/lib/i386/native_threads/libhpi.so
405f3000-405f4000 rw-p 00008000 03:01 2282670
/home/database/j2sdk1.4.0/jre/lib/i386/native_threads/libhpi.so
405f4000-40605000 r-xp 00000000 03:01 2087030
/home/database/j2sdk1.4.0/jre/lib/i386/libverify.so
40605000-40607000 rw-p 00010000 03:01 2087030
/home/database/j2sdk1.4.0/jre/lib/i386/libverify.so
40607000-40628000 r-xp 00000000 03:01 2087031
/home/database/j2sdk1.4.0/jre/lib/i386/libjava.so
40628000-4062a000 rw-p 00020000 03:01 2087031
/home/database/j2sdk1.4.0/jre/lib/i386/libjava.so
4062b000-4063f000 r-xp 00000000 03:01 2087033
/home/database/j2sdk1.4.0/jre/lib/i386/libzip.so
4063f000-40642000 rw-p 00013000 03:01 2087033
/home/database/j2sdk1.4.0/jre/lib/i386/libzip.so
40642000-41cba000 r--s 00000000 03:01 815333
/home/database/j2sdk1.4.0/jre/lib/rt.jar
41cfc000-41d13000 r--s 00000000 03:01 815314
/home/database/j2sdk1.4.0/jre/lib/sunrsasign.jar
41d13000-41d81000 r--s 00000000 03:01 815316
/home/database/j2sdk1.4.0/jre/lib/jsse.jar
41d81000-41d94000 r--s 00000000 03:01 815315
/home/database/j2sdk1.4.0/jre/lib/jce.jar
41d94000-42015000 r--s 00000000 03:01 815331
/home/database/j2sdk1.4.0/jre/lib/charsets.jar
4c140000-4c14b000 r-xp 00000000 03:01 55
/lib/libnss_compat-2.2.5.so
4c14b000-4c14c000 rw-p 0000a000 03:01 55
/lib/libnss_compat-2.2.5.so
4c177000-4c194000 r--s 00000000 03:01 1467412
/home/database/j2sdk1.4.0/jre/lib/ext/sunjce_provider.jar
4c194000-4c237000 r--s 00000000 03:01 1467414
/home/database/j2sdk1.4.0/jre/lib/ext/localedata.jar
4c237000-4c245000 r--s 00000000 03:01 1467415
/home/database/j2sdk1.4.0/jre/lib/ext/ldapsec.jar
4c245000-4c257000 r-xp 00000000 03:01 2087036
/home/database/j2sdk1.4.0/jre/lib/i386/libnet.so
4c257000-4c258000 rw-p 00011000 03:01 2087036
/home/database/j2sdk1.4.0/jre/lib/i386/libnet.so
4c258000-4c260000 r-xp 00000000 03:01 58
/lib/libnss_files-2.2.5.so
4c260000-4c261000 rw-p 00008000 03:01 58
/lib/libnss_files-2.2.5.so
(now .. I know I dropped my mind here somewhere .. I wonder where it is..)

Similar Messages

  • Application builder Error: Windows SDK function returned an error. (Error code -12) *** End Error Report

     try to create an installer in Labview 8.6.  The build fail and I got this message.
    CDK_CreateNewWizard_Invoke.vi.ProxyCaller >> CDK_CreateNewWizard_Invoke.vi >> CDK_InstallerConfiguration_Editor.vi 
    >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFBuildDist_Build.vi
    Loading product deployment information
    Loading product deployment information
    Loading product deployment information
    Loading product deployment information
    Adding files to installer
    Done adding files
    Preparing to build deployment
    Copying products from distributions
    Copying distribution 'NI LabVIEW 8.6.1 Datalogging and Supervisory Control Module' from: 
    D:\software\application\LabView\NI.LABVIEW\NI-Labview 8.6.1 DSC Module\ to: C:\Documents and Settings\Lidaoling\桌面
    \Builds\generate waveform\My Installer\
    Building deployment
    Copying setup files
    Setting merged database information
    Setting product information
    Setting developer part information
    Starting final build
    Validating...
    Copying files...
    Updating files...
    Creating merged database...
    *** Error: Windows SDK function returned an error. (Error code -12)
    *** End Error Report
    Done building deployment 

    Solution

  • Bug Report: Lr3 does not report error when SDK version is too low.

    Lr3 should report an error if SDK is under-version'd. For example, I have this in one of my plugins:
        LrSdkVersion = 2.0,
        LrSdkMinimumVersion = 2.0, -- minimum SDK version required by this plugin.
    If I put Lr3.0 specific stuff in the plugin, Lr3 does not report an error, but it should - otherwise whats the point in specifying a version.
    I have to take the plugin into Lr2 to test for inadvertent Lr3 specific inclusion mistakes. Thank goodness I'm not worrying about Lr1...
    Rob

    Hi ,
    Could you please helping me out on finding the Patches (SP4,SP5)?
    ans also i have tested very oftenly, that my log in credentials are seems to be fine since its working for other reports too.
    With Hunting,
    MAK

  • ERROR http: 5: Unable to initialize ssl connection with server, aborting co

    HI EXPERTS,
    one of my database give me below error when i start its dbconsole. and after failure it give me meassge
    TZ set to Asia/Karachi
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    https://test:5500/em/console/aboutApplication
    Starting Oracle Enterprise Manager 10g Database Control ..............................................................
    ........ failed.
    Logs are generated in directory /u01/oracle/product/10.2/cnichol_cpuplt/sysman/log
    and in trace file name "emdctl.trc" below error is logged.
    ERROR http: 5: Unable to initialize ssl connection with server, aborting connection attempt
    ERROR ssl: nzos_Handshake failed, ret=29024
    and trace file named "emagent.trc" give below error
    2010-10-04 19:12:25 Thread-88238992 ERROR http: 11: Unable to initialize ssl connection with server, aborting connection attempt
    2010-10-04 19:12:25 Thread-88238992 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://test:5500/em/upload/: retStatus=-1
    2010-10-04 19:12:38 Thread-88238992 ERROR upload: Error in uploadXMLFiles. Trying again in 300.00 seconds.
    dbconosle URL is
    https://test:5500/em/console/aboutApplication
    Operating system is Redhat linux AS 5.3
    what is the possible cause of this failure any one can guide me.
    thanx in Advance
    regards,
    Edited by: AMIABU on Oct 4, 2010 7:28 AM

    oracle@bcm-laptop:~$ emctl
    Oracle Enterprise Manager 11g Database Control Release 11.2.0.1.0
    Copyright (c) 1996, 2009 Oracle Corporation.  All rights reserved.
       Oracle Enterprise Manager 10g Database Control commands:
            emctl start | stop dbconsole
            emctl status | secure | setpasswd dbconsole
            emctl config dbconsole -heap_size <size_value> -max_perm_size <size_value>
           emctl status agent
           emctl status agent -secure [-omsurl <http://<oms-hostname>:<oms-unsecure-port>/em/*>]
           emctl getversion
           emctl reload | upload | clearstate | getversion agent
           emctl reload agent dynamicproperties [<Target_name>:<Target_Type>]....
           emctl config agent <options>
           emctl config agent updateTZ
           emctl config agent getTZ
           emctl resetTZ agent
           emctl config agent credentials [<Target_name>[:<Target_Type>]]
           emctl gensudoprops
           emctl clearsudoprops
    Blackout Usage :
           emctl start blackout <Blackoutname> [-nodeLevel] [<Target_name>[:<Target_Type>]].... [-d <Duration>]
           emctl stop blackout <Blackoutname>
           emctl status blackout [<Target_name>[:<Target_Type>]]....
    The following are valid options for blackouts
    <Target_name:Target_type> defaults to local node target if not specified.
    If -nodeLevel is specified after <Blackoutname>,the blackout will be applied to all targets and any target list that follows will be ignored.
    Duration is specified in [days] hh:mm
            emctl getemhome
            emctl ilint
    Em Key Commands Usage :
    emctl config emkey -emkeyfile <emkey.ora path> [-force] [-sysman_pwd <sysman password>]
    emctl config emkey -emkey [-emkeyfile <emkey.ora path>] [-force] [-sysman_pwd <sysman password>]
    emctl config emkey -repos [-emkeyfile <emkey.ora path>] [-force] [-sysman_pwd <sysman password>]
    emctl config emkey -remove_from_repos [-sysman_pwd <sysman password>]
    emctl config emkey -copy_to_repos [-sysman_pwd <sysman password>]
    emctl status emkey [-sysman_pwd <sysman password>]
    Secure DBConsole Usage :
    emctl secure dbconsole -sysman_pwd <sysman password> [-passwd_file <abs file loc>]
         [-host <slb hostname>] [-sid <service name>] [-reset] [-secure_port <secure_port>]
         [-root_dc <root_dc>] [-root_country <root_country>] [-root_state <root_state>] [-root_loc <root_loc>]
         [-root_org <root_org>] [-root_unit <root_unit>] [-root_email <root_email>]
         [-wallet <wallet loc>] [-wallet_pwd <wallet pwd>] [-trust_certs_loc <certs loc>]
    emctl secure status dbconsole
    Register Targettype Usage :
    emctl register oms targettype [-o <Output filename>] <XML filename> <rep user> <rep passwd> <rep host> <rep port> <rep sid> OR
    emctl register oms targettype [-o <Output filename>] <XML filename> <rep user> <rep passwd> <rep connect descriptor>

  • Error: Windows SDK function returned an error. (Error code -12)

    I receive this error when attempting to build an installer for my Labview application.
    CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
    Loading product deployment information
    Loading product deployment information
    Adding files to installer
    Done adding files
    Preparing to build deployment
    Copying products from distributions
    Copying distribution 'NI-DAQ 8.0.1' from: D:\ to: C:\DARTS\ATS_TE_Project\DARTS_NI-DAQ_HP3561A_Dynamic_Signal_Analyzer\Installer\
    *** Error: Windows SDK function returned an error. (Error code -12)
    The system cannot find the file specified.
    *** End Error Report
    Done building deployment

    I was able to get the install builder to build an installer for my
    Application today 6/6/07. These are the steps I performed along with good amounts of trail and error.
    1) I attempted to re-install the NI-DAQ 8.0.1 drivers however I didn't
    perform this because it said it remove NI products which I didn't want
    removed. But it didn't tell me what it would remove.
    2) Instead, I copied the entire NI-DAQ 8.0.1 distribution to a directory on my hard drive.
    3) I set the NI-DAQ 8.3 install build type to FULL in install builder.
    4) In install builder when prompted for the components from the NI-DAQ
    8.0.1 I browsed to the NI-DAQ 8.0.1 directory on the hard drive and
    also un-checked the cache box.
    5) It through another error this time saying it couldn't find
    C:\NI-DAQ8_0_1\8.0.1\Products\LabVIEW_Broker71\LVBroker71Deu.mst (and,
    LVBroker71Fra.mst, LVBroker71jpn.mst, LVBroker1071Deu,
    LVBroker1071Fra.mst, LVBroker1071jpn.mst). It also could not find the
    LVBroker1071 files in the
    C:\NI-DAQ8_0_1\8.0.1\Products\LabVIEW_Broker1071 directory either.
    6) I performed a search for these files and they did not exist in the
    NI-DAQ 8.0.1 directory on my hard drive or the 8.0.1 CD I have.
    7) These files DID exist in my NI-DAQ 8.3 directory located on my hard drive.
    8) I copied the LVBrokerxxxx.mst (listed in 5 above) files from the
    NI-DAQ 8.3 directory on my hard drive to the corresponding location in
    the NI-8.0.1 directory on my hard drive.
    9) This time when I rebuilt the installer for my application the build was successful.
    Additional information:
    When I built my application I only selected English for language
    support. In Install builder in "Dialog Information I also selected
    English.
    I haven't attempted to try the installer on my target yet so I'm not
    quite sure how successful I really was but at least I have a installer.
    Let me know if this also works for you.
    Rich...

  • Error while adding a connector for SSL..help!!!

    i'm getting this error when i added a connector for SSL and restarted tomcat
    my connector tag is
    <Connector keystorePass="kalima" scheme="https" port="8443" sslProtocol="TLS" redirectPort="-1" enableLookups="true" keystoreFile="Mykeystore" protocol="TLS" keystore="C:\Documents and Settings\santhoshyma\Mykeystore" clientauth="false" algorithm="SunX509" keypass="changeit" secure="true" keytype="JKS">
          <Factory className="org.apache.coyote.tomcat5.CoyoteServerSocketFactory" keystorePass="kalima" keystoreFile="C:\SSLTest\Mykeystore"/>
        </Connector>
    LifecycleException:  Protocol handler instantiation failed: java.lang.NullPointe
    rException
            at org.apache.coyote.tomcat5.CoyoteConnector.initialize(CoyoteConnector.
    java:1368)
            at org.apache.catalina.core.StandardService.initialize(StandardService.j
    ava:609)
            at org.apache.catalina.core.StandardServer.initialize(StandardServer.jav
    a:2384)
            at org.apache.catalina.startup.Catalina.load(Catalina.java:507)
            at org.apache.catalina.startup.Catalina.load(Catalina.java:528)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:324)
            at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:250)
            at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:424)

    The question is answered in CRM 7.0 forum:
    Getting error while adding a custom field (with input help) through AET

  • Error while invoking web service over SSL

    While making a SSL Connections to web service i am getting the below mentioned error in spite of configuring the certificate provided by the client onto WLS.
    I tried adding the certificate to the default DemoTrust and DemoIdentity Keystores. The error still persisted.
    I also tried importing the certificate(into cacerts keystore) as Java Standard Trust as well as tried pointing it to the custom keystores. None of it worked :(
    Could somebody please give a solution to resolve this error ASAP.
    The error is:
    Message:exception occured, due to org.apache.axis2.AxisFault: 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
    org.apache.axis2.AxisFault: 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 org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
         at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:83)
         at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java:84)
         at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:499)
         at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2114)
         at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096)
         at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
         at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
         at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
         at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
         at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:542)
         at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:199)
         at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:76)
         at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:400)
         at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:225)
         at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:435)
         at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
         at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
         at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
         at com.intel.services.warrantyservice.Get_Warranty_Details_OutServiceStub.get_Warranty_Details_Out(Get_Warranty_Details_OutServiceStub.java:184)
         at com.intel.www.PortalServices.PortalServicesSOAPImpl.getWarrantyDetails(PortalServicesSOAPImpl.java:1865)
         at com.intel.www.PortalServices.PortalServicesSOAPSkeleton.getWarrantyDetails(PortalServicesSOAPSkeleton.java:213)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
         at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
         at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
         at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
         at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
         at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
         at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
         at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
         at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3590)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: javax.xml.stream.XMLStreamException: 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 weblogic.xml.stax.XMLWriterBase.flush(XMLWriterBase.java:504)
         at org.apache.axiom.om.impl.MTOMXMLStreamWriter.flush(MTOMXMLStreamWriter.java:168)
         at org.apache.axis2.databinding.utils.writer.MTOMAwareXMLSerializer.flush(MTOMAwareXMLSerializer.java:79)
         at org.apache.axis2.databinding.ADBDataSource.serialize(ADBDataSource.java:94)
         at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerializeAndConsume(OMSourcedElementImpl.java:738)
         at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:966)
         at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:995)
         at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally(SOAPEnvelopeImpl.java:254)
         at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:242)
         at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:995)
         at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:486)
         at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:79)
         ... 48 more
    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:174)
         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1591)
         at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:187)
         at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:181)
         at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1035)
         at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:124)
         at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:516)
         at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:454)
         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:884)
         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1096)
         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:623)
         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.ChunkedOutputStream.flush(ChunkedOutputStream.java:191)
         at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:278)
         at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:122)
         at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:212)
         at java.io.BufferedWriter.flush(BufferedWriter.java:236)
         at weblogic.xml.stax.XMLWriterBase.flush(XMLWriterBase.java:502)
         ... 59 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:285)
         at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:191)
         at sun.security.validator.Validator.validate(Validator.java:218)
         at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:126)
         at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:209)
         at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:249)
         at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1014)
         ... 74 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:174)
         at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:238)
         at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:280)
         ... 80 more

    Which version/platform are you using?
    The thing you need to consider here is that the JDev proxy settings do not affect the BPEL server.
    So if the BPEL server cannot connect to your webservice, it will not be because of any Jdev setting.
    Check the proxy settings on your BPEL server (on 10.1.2 developer install it will be in obsetenv.bat, on 10.1.3 it will be a commandline property of the JVM - see AS Control administration page for the JVM)

  • Java Web Start Error in through codebase url with SSL

    I have created one Java web-start plugin application in swing which is launched from PHP site at browser plugin.
    All things were working fine, but when we implemented SSL in our site it stopped working. And when we try to start the application from browser it thorws error like:
    Unable to launch Application.
    In Java console it puts following log:
    JNLP Ref (...): NULL !
    #### Java Web Start Error:
    #### null
    Following is my JNLP file:
    <jnlp spec="1.0+" codebase="https://<<server_domain>>/MyPlugin/">
      <information>
        <title>Test Plugin</title>
        <vendor>The Java(tm) Tutorial</vendor>
        <homepage href="null"/>
        <description>Test Plugin</description>
        <description kind="short">Test Plugin</description>
        <offline-allowed/>
      </information>
      <security>
        <all-permissions/>
      </security>
      <update check="timeout" policy="always"/>
      <resources>
        <java version="1.7+"/>
        <jar href="http://<<server_domain>>/MyPluginJar.jar" download="eager" main="false"/>
      </resources>
      <application-desc>
        <argument>test</argument>
        <argument>test</argument>
        <argument>test</argument>
        <argument>test</argument>
        <argument>test</argument>
      </application-desc>
    </jnlp>
    The issue started only after implementation of SSL in our site. Please provide any solution for this. Many thanks in advance.
    P.S. My Jar file is signed by third party authorized certificate.

    Have you tried using Rosetta?

  • BAD_CERTIFICATE error calling a web service over SSL in ALSB 2.6

    We have a business service on an ALSB 2.6 server (running on WL 9.2.1) that connects to a web service over SSL. When we try to run it, we get the following exception:
    <Sep 17, 2009 7:49:17 AM PDT> <Error> <ALSB Kernel> <BEA-380001> <Exception on TransportManagerImpl.sendMessageToService, com.bea.
    wli.sb.transports.TransportException: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
    com.bea.wli.sb.transports.TransportException: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
    at com.bea.wli.sb.transports.TransportException.newInstance(TransportException.java:146)
    at com.bea.wli.sb.transports.http.HttpOutboundMessageContext.send(HttpOu
    tboundMessageContext.java:310)
    at com.bea.wli.sb.transports.http.HttpsTransportProvider.sendMessageAsync(HttpsTransportProvider.java:435)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    Truncated. see log file for complete stacktrace
    javax.net.ssl.SSLKeyException: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
    at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
    Truncated. see log file for complete stacktrace
    This exception only occurs when hitting the web service through the bus. I have written a standalone Java application that posts to the web service and it works fine. I ran the application on the server where the ALSB is running using the same jdk (1.5.0_06 - the version that ships with 9.2.1) and the same cacerts file so I know it's not a problem with the certificate not being trusted. I have tried updating the cacerts file to the latest one distributed with JRE 1.6 and it still doesn't work.
    After 8 hours of troubleshooting, I'm out of ideas. Does anyone have any suggestiosn?
    Thanks.
    Matt
    Edited by: user6946981 on Sep 17, 2009 7:58 AM

    Are you sure that your standalone application is using the same keystore (eg. cacert)? Default WebLogic configuration uses different keystore (demo).
    I saw BAD_CERTIFICATE error only once and the cause was in keytool that somehow corrupted certificate during import. Deleting and importing certificate again helped me, but I doubt you have the same problem as your standalone application works.
    Another idea ... Is hostname varification used? I know that the error message would look different if this was the cause, but try to add this parameter to your weblogic startup script: -Dweblogic.security.SSL.ignoreHostnameVerification=true
    Last but not least, there is difference between your standalone application and ALSB runtime as WebLogic uses Certicom SSL provider. If you don't find the reason, contact Oracle support. Maybe they can help you to tweak Certicom provider in some way.

  • Error while provisioning OIM - AD in SSL

    Hi All,
    I am trying to configure OIM - AD communication in SSL mode. for that, I installed the AD connector MSFT_AD_Base_91100 and i deployed it. It was successfully configured. and my OIM version is OIM9101.
    I configured the IT Resource by mentioning
    Use SSL:yes
    Allow Password Provisioning: yes
    port number:636
    I tried to provision a testuser which was created in OIM.But i am getting an error that "Error encountered while connecting to target system."
    could anyone please help me in resolving the issue.
    Thanks & Regards.

    Hi suren,
    now i am able to connect to AD at 636 through jxplorer. actually i forgot to import the trusted certificate in jxplorer.
    Now i am able to connect to AD in SSL mode.
    now my purpose is to enable the OIM AD communication in SSL mode and to provision the password. for that i am using Weblogic 10.3.0,OIM 9.1.0.1 and oracle DB 10g. I used the connector MSFT_AD_Base_91100 version.
    I tested in non SSL mode by using this connector and its working fine. but when i am trying to provision a user in SSL mode i am getting the following error.
    Response: Connection Error encountered
    Response Description: Error encountered while connecting to target system
    this error was caught in the status of ADuser--->create user.
    could you help me in resolvng this issue.
    Thanks & Regards.

  • Connection error while provisioning to AD in SSL mode

    Hi all,
    I am trying to establish the OIM-AD communication in SSL mode to provision the passwords.
    for that i used the MSFT_AD_base_91100 connector and deployed it on my OIM-9101which is on Win Server 2003
    I configured the ITResource by specifying the following details.
    use SSL: yes allow password provisioning: yes port:636
    and i imported the keystore by executing 'keytool' command at \bea\jdk....\jre\... keytool.exe
    but when i am trying to provision the user by using this SSL mode configuration i am getting the error "Error encountered while connecting to target system". and in the logs i am getting the following exception
    =========================================================
    ERROR,25 Mar 2010 03:40:49,812,[OIMCP.ADCS],com.thortech.xl.integration.ActiveDi
    rectory.tcUtilADTasks : createUser
    ERROR,25 Mar 2010 03:40:49,812,[OIMCP.ADCS],Connection Error Occur
    ERROR,25 Mar 2010 03:40:49,812,[OIMCP.ADCS],Description : Connection Error Occur
    ERROR,25 Mar 2010 03:40:49,812,[OIMCP.ADCS],com.thortech.xl.exception.Connection
    Exception: Connection Error Occur
    ==========================================================
    Note: 1) checked AD in SSL mode through jxplorer and ldapbrowser and it is connecting in SSL mode.
    2) checked by provisioning the user in non-ssl mode using this connector and its working fine.
    Could anyone help me in resolving the issue.?????
    Thanks in advance.

    My suggestion would be - Follow the steps religiously and see if you missed any step or not because I have tried it many a times and other people have also did and it works. You are saying that you imported that certificate in OIM too. See the document and verify your steps and finally the connection parameters in IT resource should be:
    - Use SSL = yes
    - Port Number = *636*
    Thanks
    Sunny

  • A fatal error when attempting to access the SSL server credential private key. Error code 0x8009030d. Windows 8.1.

    Hi,
    We develop a server-side application which receives incoming https connections using self-signed certificate. It was all ok while we were using Windows 7 or Windows 2008 as OS, but when our clients started installing Windows 8 as server OS they encountered
    big problem: application got unavailable in few hours after start. 
    In event logs we have following:
    A fatal error occurred when attempting to access the SSL server credential private key. The error code returned from the cryptographic module is 0x8009030d. The internal error state is 10001.
    After restart, application recreates certificate and all works normal few hours till next fatal error.
    This
    article did not help us. And I repeat that this error appears only on Windows 8 (we tested on Windows 8.1). Windows 2012 Server we did not test yet.
    How we can solve this problem?
    Best regards.

    Hi,
    Since this article released in 2008,I suspect the code mentioned in this article doesn't  supprot Windows 8.
    And since the certificate was written by C#,I suggest you submit a new case on MSDN Forum as they will be more professional on your issue:
    https://social.msdn.microsoft.com/Forums/en-US/home
    Regards,
    Kelvin hsu
    TechNet Community Support

  • Errors with sdk 1.4.1, but not with 1.3??

    I just upgraded to the j2sdk 1.4.1 yesterday from 1.3, and I'm getting a weird compile time error from an import statement that never used to happen. I'm just importing another class I've made, other imports from java.util etc. work fine, but not classes that I have made. Here's the code that gives an error.
    import java.io.File;
    import java.util.Vector;
    import java.util.Enumeration;
    import listDir; // only this line gives an error
    and here's the error.
    C:\kevin\listAll.java:4: '.' expected
    import listDir;
    ^
    1 error
    Anyone have any idea why that happens? Have the rules changed for importing since sdk 1.3? This worked just fine 2 days ago with 1.3. Thanks for any help.

    Hi all,
    This is what I found will work with the stand alone classes (not package classes).
    1) Do not use import MyClass; in your java app.
    2) MyClass should be in the same directory as you java app, unless you have set up your CLASSPATH to point to MyClass.
    Here is the listing
    //import MyClass;
    class HelloWorldApp {
    public static void main(String[] args) {
    String strNewPwd = null;
    System.out.println("Hello World!"); //Display the string.
    MyClass myClass = new MyClass();
    //Do something to call your class
    System.out.println(myClass.getMsg());
    It seems to work now. If someone knows where I can find an updated documents on how to include classes on 1.4.1, please reply to this message.
    Beside this problem, I am trying to use Tomcat 4.1 to develope a web application. I have similar problems finding my classes. On Tomcat 4.0, the app runs fine. I've try the above work around (not include import MyClass), but still does not work. Any suggestions?

  • Error when configuring Web Dispatcher for SSL with Enterprise Portal

    We are in the process of configuring the Web Dispatcher using SSL to connect to our Enterprise Portal (the Web Dispatcher will be in the DMZ).  We have followed all of the help.sap.com guides and now have SSL listening on the EP side (port 8103).  We are now receiving this strange certificate error when we start the Web Dispatcher:
    [Thr 5332] Tue Mar 20 00:36:23 2007
    [Thr 5332]   MatchTargetName("<FULLY QUALIFIED HOSTNAME>", "CN=XXX, OU=XXX, O=XXXX, C=XX") FAILS
    [Thr 5332]   SSL socket: local=<IPADDRESS>:4742  peer=<IPADDRESS>:8103
    [Thr 5332] <<- ERROR: SapSSLSessionStart(sssl_hdl=009D7670)==SSSLERR_SERVER_CERT_MISMATCH
    [Thr 5332] *** ERROR => IcmConnInitClientSSL: SapSSLSessionStart failed (-30): SSSLERR_SERVER_CERT_MISMATCH [icxxconn.c 2005]
    [Thr 5332] *** ERROR => IcmConnClientRqCreate() failed (rc=-14) [icrxx.c      4919]
    [Thr 5332] *** ERROR => Could not connect to SAP Message Server at <FULLY QUALIFIED HOST NAME>. URL=/msgserver/text/logon?version=1.2 [icrxx.c      2301]
    [Thr 5332] *** ERROR => rc=-1, HTTP response code: 0 [icrxx.c      2302]
    [Thr 5332] *** ERROR => see also OSS note 552286 [icrxx.c      2303]
    We have gone through the trouble shooting note 552286 as listed in the error above.  Any assistance is appreciated.

    Hello, did you receive any resolution for this problem?  We are receiving a similar error and I am unsure of how to resolve.

  • Help!:  Build error on SDK 3.0

    Hi,
    I get the following error while building on SDK 3.0. The project includes Frameworks - CoreFoundation, Foundation, MessageUI and UIKit; but the MessageUI is in 'red' color. Any idea?
    Thanks - Sam.
    cd "/Users/sam/myApp"
    setenv MACOSXDEPLOYMENTTARGET 10.5
    setenv PATH "/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin"
    /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/gcc-4.2 -arch i386 -isysroot /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.0.sdk "-L/Users/sam/myApp/build/Debug-iphonesimulator" "-F/Users/sam/myApp/build/Debug-iphonesimulator" -filelist "/Users/sam/myApp/build/myApp.build/Debug-iphonesimulator/myApp.build/Objects-normal/i386/myApp.LinkFileList" -mmacosx-version-min=10.5 -framework CoreGraphics -framework CoreFoundation -framework Foundation -framework MessageUI -framework UIKit -o "/Users/sam/myApp/build/Debug-iphonesimulator/myApp.app/iNotate"
    Undefined symbols:
    ".objcclass_nameCameraViewController", referenced from:
    literal-pointer@_OBJC@__clsrefs@CameraViewController in myAppAppDelegate.o
    ld: symbol(s) not found
    collect2: ld returned 1 exit status
    ".objcclass_nameCameraViewController", referenced from:
    literal-pointer@_OBJC@__clsrefs@CameraViewController in myAppAppDelegate.o
    ld: symbol(s) not found
    collect2: ld returned 1 exit status
    Build failed (1 error)

    Hi,
    I checked the build/.../.../i386 directories (for simulator and device) - and the .o file is not present.
    After 'Clean All', the all .o's are removed. After 'Build', all but that .o files are built. Hmmm.
    The project includes the .h and the .m file for the CameraViewController class. It is the newly-added class to the project.
    What would be the reason for this file to be ignored during the build?
    Sam

Maybe you are looking for

  • How do I ignore the difference​s in DBMSs when reading data from a DB?

    My boss wants me to create a text parser that parses the below sentence and executes an SQL query. 'get table field1,field2,field3,...,fieldN [where SQL conditional statements]' This corresponds to 'select field1, field2, field3, ..., fieldN from tab

  • How to count the number of cycles in sine wave

    Hi, I am new to Labview.  I have labview 8.2 version and my dataacquisition is NIDAQPAD6015.  I could write a program to generate a sine wave of desired frequency through simulate signal. My question is how do i measure the number of cycles for this

  • Keep getting carrier update when connecting my new iPad to Itunes

    keep getting carrier update when connecting my new iPad to Itunes even though I have updated it I am with o2

  • Modifying existing theme

    Hi ! I use N79. I just want to modify the theme to add a wallpaper so that it sit nicely in the middle of the screen. Where can I find the existing themes ? Thanks

  • DTP Full/Delta loads

    I am loading data from one DSO to another. The change log of the source DSO has been deleted for any request before 20 days. I want to do a full load from active table and then start the delta loads from change log. But the problem is the load is pic