.p12 Certificate import in weblogic server 10.3.6.0

Hi,
I am facing a issue regarding certificate import in weblogic server 10.3.6.0. In my project I built a java webservice where a https url  is invoked with xml input(correct format).Https url is restricted. I can not open this url from my browser. I got '403 : Forbidden' error in browser as well as webservice log in server. I asked my client. They gave me one .jks and one .p12 certificated file and password. When I installed this .p12 (giving password) in my local windows computer, I am able to open that https in my browser.I have imported this .p12 certificate in 'cacerts' as well as 'DemoTrust.jks' in weblogic server and restarted the server. But i am getting the same error(403 : Forbidden) in weblogic server.
Where should I import this .p12 in weblogic server? I mean in which key store.
FYI,
This code is running fine in 10g production server.I haven't developed this code. I have migrated this code to 11.1.1.7.0.
I am using this .jks() in the java code.       
        System.setProperty("javax.net.ssl.keyStore", keyStore.jks);
        System.setProperty("javax.net.ssl.keyStorePassword", "<password>");
Weblogic server is running in unix environment.
Read many posts... But did not any find right solution. Can anybody please help me solve this.

If i remember correctly, .p12 will have both the public and private key.
You need to convert it to a jks and configure the server to use this jks
Converting certificate formats | Middleware wonders!!
Weblogic SSL configuration
Thanks,
Faisal

Similar Messages

  • Enabling ssl on Weblogic server 5.1 using Verisign certificate.

    "Hi,I am trying to enable ssl in Weblogic server 5.1The properties set in my properties file areweblogic.security.certificate.server=servercert.pem(sent from the verisign via email)weblogic.security.key.server=cp8212-2d2-key.der(generated by the Certificate Servlet of Weblogic Server)

    "Hi,I am trying to enable ssl in Weblogic server 5.1The properties set in my properties file areweblogic.security.certificate.server=servercert.pem(sent from the verisign via email)weblogic.security.key.server=cp8212-2d2-key.der(generated by the Certificate Servlet of Weblogic Server)

  • How do I get a digital certificate for WebLogic Server?

    I has three files(*.der, *.pem, *.pem)generated by weblogic certificate sevlet. And I has also got file from verisign throuth my CSR file. But when I give the *.der file to server key file name field on the console, some error occur in my weblogic:
    <2002-6-12 %u4E0A%u534811%u65F622%u520614%u79D2> <Alert> <WebLogicServer> <Security configuration pr
    oblem with certificate file config/mydomain/eintech-key.der, java.io.EOFExceptio
    n>
    java.io.EOFException
    at weblogic.security.Utils.inputByte(Utils.java:133)
    at weblogic.security.ASN1.ASN1Header.inputTag(ASN1Header.java:125)
    at weblogic.security.ASN1.ASN1Header.input(ASN1Header.java:119)
    at weblogic.security.RSAPrivateKey.input(RSAPrivateKey.java:119)
    at weblogic.security.RSAPrivateKey.<init>(RSAPrivateKey.java:91)
    at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:397)
    at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:300)
    at weblogic.t3.srvr.T3Srvr.initializeListenThreads(T3Srvr.java:1045)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:480)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    I don't know where is the error raise? help me?

    Hi.
    Just a guess, but sometimes this happens when the .der file is actually in .pem format, or vice versa. You might try changing the name of the cert to .pem, specify it in the console and see if that helps.
    You also might get a better answer posting this question on the security newsgroup.
    Regards,
    Michael
    javachina wrote:
    I has three files(*.der, *.pem, *.pem)generated by weblogic certificate sevlet. And I has also got file from verisign throuth my CSR file. But when I give the *.der file to server key file name field on the console, some error occur in my weblogic:
    <2002-6-12 %u4E0A%u534811%u65F622%u520614%u79D2> <Alert> <WebLogicServer> <Security configuration pr
    oblem with certificate file config/mydomain/eintech-key.der, java.io.EOFExceptio
    n>
    java.io.EOFException
    at weblogic.security.Utils.inputByte(Utils.java:133)
    at weblogic.security.ASN1.ASN1Header.inputTag(ASN1Header.java:125)
    at weblogic.security.ASN1.ASN1Header.input(ASN1Header.java:119)
    at weblogic.security.RSAPrivateKey.input(RSAPrivateKey.java:119)
    at weblogic.security.RSAPrivateKey.<init>(RSAPrivateKey.java:91)
    at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:397)
    at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:300)
    at weblogic.t3.srvr.T3Srvr.initializeListenThreads(T3Srvr.java:1045)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:480)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    I don't know where is the error raise? help me?--
    Michael Young
    Developer Relations Engineer
    BEA Support

  • Weblogic server 9.2 and SSL server certificate for the wrong site

    I turned on SSL service for a weblogic 9.2 server and later on changed the hostname of the machine that weblogic was running on. So the hostname that my SSL server certificate was issued to has now became an invalid hostname. But my weblogic server continues to run SSL service without any exception. I can still access my web applications thru the SSL port (except of course I get a warning for the server certificate every time that it is for the "wrong site"). My question is this: should weblogic 9.2 verify the hostname in the server certificate and stop SSL service if the certificate is for the wrong site? Or is verifying the certificate strictly the job of the browser? Just want to make sure there is nothing wrong with my SSL configuration. Thanks.

    So you are saying that something is wrong with my weblogic 9.2 ssl configuration? And that given a server certificate issued to a different hostname, my weblogic server should NOT be servicing ssl request and/or it should throw some sort of exception during startup? Thanks for clarifying.

  • Import a valid Server Certificate as a trustStore.?

    How do I import a valid server certificate as a trustStore and put
    this in jre/lib/security.
    I have a Java class that needs to connect to a valid HTTPS Server
    having a certificate issued by a CA.
    Now,I have a Java client that connects to this server,and sends and
    receives data.
    I will need to import the server certificate into the jre/lib/security
    directory?
    I guess we need to do this so that the client accepts the server's
    certificate
    Has anyone understood my question?
    Attached is my java class:
    public class HttpsSender
    String sURL = "SomeServerAddress";
    public static String ec(String sMess)
    String response=null;
    try {
    Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
    System.setProperty("java.protocol.handler.pkgs","com.sun.net.ssl.internal.www.protocol");
    /* Temporarily testing on Tomcat and hence the Context:A_SYMBIAN_SERVLET */
    URL url;
    String uri = "https://" + sURL
    url = new URL(uri);
    HttpsURLConnection hpCon= (HttpsURLConnection)url.openConnection();
    hpCon.setRequestMethod("POST");
    hpCon.setDoOutput(true);
    hpCon.setDoInput(true);
    /** Transfer Data over https */
    DataOutputStream dos = new DataOutputStream(hpCon.getOutputStream());
    dos.writeUTF(sMess);
    /* Response from the Receiving Servlet.*/
    DataInputStream dis = new DataInputStream(hpCon.getInputStream());
    try {
    response = dis.readUTF();
    }finally
    dos.close();
    dis.close();
    }catch(IOException e)
    System.out.println("Error in Client " + e);
    return response;
    } // End of Method Encrypt.

    You can import a valid server certificate into a Store with the keytool!
    Good link:
    http://forum.java.sun.com/thread.jsp?forum=2&thread=4240
    You must provide to the Java-VM where it can find the TrustStore:
    -> on command line:
    java -Djavax.net.ssl.trustStore=XXX/jssesamples/samplecacerts
    For Testing the Debug Output can be usefull! Enable with:
    java -Djavax.net.debug=handshake,ssl
    -> in source code:
    System.setProperty("javax.net.ssl.trustStore",STORE_FILE);
    System.setProperty("javax.net.ssl.trustStorePassword",STORE_PASS);

  • How to import a password protected p12 certificate to keystore?

    Hi all,
    I am new in java security programming.
    And I got something very urgent need your help..
    How to import a password protected p12 certificate to keystore programmatically?
    Does anyone have sample codes on this issue?
    thanks very much
    Wyan

    Hi omslion,
    I responded to a similar post from you (and moved it to the Acrobat forums). Password protecting a file requires Adobe Acrobat. You are welcome to download a free 30-day trial of Acrobat. For more information, see www.adobe.com/products/acrobat.html.
    Best,
    Sara

  • Importance of Pointbase server in Weblogic 7.0

    Hi,
    While starting Weblogic Server 7.0, Pointbase services also start. Is it mandatory to have Pointbase services running along with Weblogic Server?
    What are the uses of Pointbase server and what does it cater to?
    Thanks in advance.
    Seetesh

    Hi Cmmcorvey,
    Thanks 4 ur post.
    Can I comment this line appearing in startWLServer.cmd?
    start "PointBase" cmd /c ""d:\bea\jdk131_06\bin\java" -classpath "%CLASSPATH%" com.pointbase.net.netServer /port:9092 /d:3 /pointbase.ini=%SAMPLES_HOME%\server\config\examples\pointbase.ini" > %SAMPLES_HOME%\server\config\examples\pointbase.log 2>&1
    Rgds,
    Seetesh

  • Getting error while hitting weblogic server from EBS client instance

    Hi,
    We are trying to hit weblogic server from EBS client instance.
    Steps Done from our side :-
    1. Created a self signed key store and certificate (.cer file) with server host name and used it for SSL enabling on weblogic server.
    2. Created a self signed key store and certificate (.cer file) with client host name and used it for SSL enabling on oracle EBS client.
    3. Imported client certificate .cer file in Server Side Trust Store.
    4. Used Server keystore for client side verification.
    We are getting these logs from Client Side (Oracle EBS AS) :-
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:33 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:34 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:34 AM AST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 9, 2012 10:40:34 AM AST> <Warning> <Security> <BEA-090542> <Certificate chain received from whjed-ebspay.nmc.com - 192.168.100.169 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.>
    <Nov 9, 2012 10:40:34 AM AST> <Warning> <Security> <BEA-090542> <Certificate chain received from whjed-ebspay.nmc.com - 192.168.100.169 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.>
    <Nov 9, 2012 10:40:34 AM AST> <Warning> <Security> <BEA-090542> <Certificate chain received from whjed-ebspay.nmc.com - 192.168.100.169 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.>
    javax.net.ssl.SSLKeyException: [Security:090542]Certificate chain received from whjed-ebspay.nmc.com - 192.168.100.169 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.
    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)
    at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
    at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
    at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
    at com.certicom.tls.record.ReadHandler.processRecord(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 com.certicom.tls.record.WriteHandler.write(Unknown Source)
    at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
    at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
    at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
    at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
    at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:158)
    at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:363)
    at oracle.apps.nmc.filetransmission.DigitalSigner.sendSignedFileToBank(DigitalSigner.java:532)
    at oracle.apps.nmc.filetransmission.DigitalSigner.signXmlFile(DigitalSigner.java:330)
    at oracle.apps.nmc.filetransmission.DigitalSigner.invokerInit(DigitalSigner.java:437)
    at oracle.apps.nmc.filetransmission.DigitalSigner.runProgram(DigitalSigner.java:390)
    at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
    We are getting these logs from Server Side (Weblogic server) :-
    <Nov 9, 2012 10:34:51 AM AST> <Warning> <Security> <BEA-090482> <BAD_CERTIFICATE alert was received from whjed-apstest3.nmc.com - 192.168.100.246. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
    Kindly suggest on this.
    Regards
    Deepak Gupta

    Hi;
    Please make a search BEA-090482 Check the peer to determine why it rejected at metalink. There are 8 docs avaliable, please review them
    Regard
    Helios

  • Boot.properties file not fetching by weblogic server 10.3.6.0

    Hi Team,
    I have Installaed weblogic Server 10.3.6.0 and Forms and Reports 11.1.2.2.0. Even though the boot.properties with weblogic credentials is located in Weblogic Domain under security folder, the weblogic server is asking username and password while starting the services.
    Environment : Windows Server 2008 R2- 64 bit
    Please suggesst what would be the root cause of this issue.
    Many thanks in advance!
    Kind Regards,
    Mohan

    ####<Dec 19, 2014 10:05:13 AM SGT> <Notice> <WebLogicServer> <SRVBIAPDEV02> <AdminServer> <main> <<WLS Kernel>> <> <> <1418954713757> <BEA-000365> <Server state changed to STANDBY>
    ####<Dec 19, 2014 10:05:13 AM SGT> <Notice> <WebLogicServer> <SRVBIAPDEV02> <AdminServer> <main> <<WLS Kernel>> <> <> <1418954713757> <BEA-000365> <Server state changed to STARTING>
    ####<Dec 19, 2014 10:05:13 AM SGT> <Info> <SAFService> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954713788> <BEA-281003> <SAF Service has been initialized.>
    ####<Dec 19, 2014 10:05:13 AM SGT> <Info> <SAFService> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954713803> <BEA-281002> <SAF Service has been started.>
    ####<Dec 19, 2014 10:05:13 AM SGT> <Info> <WseeCore> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954713803> <BEA-220502> <The Wsee Service is starting>
    ####<Dec 19, 2014 10:05:13 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954713913> <BEA-149209> <Resuming.>
    ####<Dec 19, 2014 10:05:14 AM SGT> <Info> <JMX> <SRVBIAPDEV02> <AdminServer> <JMX FRAMEWORK Domain Runtime MBeanServer pooling thread> <<WLS Kernel>> <> <0000KdWIeWT2ZN8LziO5yW1K^sVM000001> <1418954714755> <BEA-149505> <The administration server was unable to establish JMX Connectivity with the WLS_FORMS at the JMX Service URL of <none>.>
    ####<Dec 19, 2014 10:05:14 AM SGT> <Info> <JMX> <SRVBIAPDEV02> <AdminServer> <JMX FRAMEWORK Domain Runtime MBeanServer pooling thread> <<WLS Kernel>> <> <0000KdWIeWT2ZN8LziO5yW1K^sVM000001> <1418954714755> <BEA-149505> <The administration server was unable to establish JMX Connectivity with the WLS_REPORTS at the JMX Service URL of <none>.>
    ####<Dec 19, 2014 10:05:15 AM SGT> <Info> <WorkManager> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954715707> <BEA-002901> <Creating WorkManager "consoleWorkManager" for module "null" and application "consoleapp">
    ####<Dec 19, 2014 10:05:18 AM SGT> <Info> <Diagnostics> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954718889> <BEA-320114> <Initializing the Diagnostics Harvester.>
    ####<Dec 19, 2014 10:05:18 AM SGT> <Info> <Diagnostics> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954718905> <BEA-320117> <The Harvester is being disabled because there are no Harvestable types configured specified.>
    ####<Dec 19, 2014 10:05:18 AM SGT> <Info> <Diagnostics> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954718905> <BEA-320119> <The Harvester is now in a inactive state.>
    ####<Dec 19, 2014 10:05:19 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954719217> <BEA-160151> <Registered library Extension-Name: UIX, Specification-Version: 11, Implementation-Version: 11.1.1.1.0 (WAR).>
    ####<Dec 19, 2014 10:05:19 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954719341> <BEA-160151> <Registered library Extension-Name: adf.oracle.businesseditor, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (WAR).>
    ####<Dec 19, 2014 10:05:20 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954720153> <BEA-160151> <Registered library Extension-Name: adf.oracle.domain, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (EAR).>
    ####<Dec 19, 2014 10:05:21 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954721260> <BEA-160151> <Registered library Extension-Name: adf.oracle.domain.webapp, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (WAR).>
    ####<Dec 19, 2014 10:05:21 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954721447> <BEA-160151> <Registered library Extension-Name: emai (WAR).>
    ####<Dec 19, 2014 10:05:21 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954721759> <BEA-160151> <Registered library Extension-Name: emas (WAR).>
    ####<Dec 19, 2014 10:05:22 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954722337> <BEA-160151> <Registered library Extension-Name: emcore (WAR).>
    ####<Dec 19, 2014 10:05:22 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954722461> <BEA-160151> <Registered library Extension-Name: jsf, Specification-Version: 1.2, Implementation-Version: 1.2.9.0 (WAR).>
    ####<Dec 19, 2014 10:05:22 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954722539> <BEA-160151> <Registered library Extension-Name: jstl, Specification-Version: 1.2, Implementation-Version: 1.2.0.1 (WAR).>
    ####<Dec 19, 2014 10:05:22 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954722633> <BEA-160151> <Registered library Extension-Name: ohw-rcf, Specification-Version: 5, Implementation-Version: 5.0 (WAR).>
    ####<Dec 19, 2014 10:05:22 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954722711> <BEA-160151> <Registered library Extension-Name: ohw-uix, Specification-Version: 5, Implementation-Version: 5.0 (WAR).>
    ####<Dec 19, 2014 10:05:22 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954722914> <BEA-160151> <Registered library Extension-Name: oracle.adf.dconfigbeans, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (JAR).>
    ####<Dec 19, 2014 10:05:22 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954722976> <BEA-160151> <Registered library Extension-Name: oracle.adf.desktopintegration, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (WAR).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723023> <BEA-160151> <Registered library Extension-Name: oracle.adf.desktopintegration.model, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (EAR).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723101> <BEA-160151> <Registered library Extension-Name: oracle.adf.management, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (WAR).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723210> <BEA-160151> <Registered library Extension-Name: oracle.bi.adf.model.slib, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (EAR).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723304> <BEA-160151> <Registered library Extension-Name: oracle.bi.adf.view.slib, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (WAR).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723397> <BEA-160151> <Registered library Extension-Name: oracle.bi.adf.webcenter.slib, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (WAR).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723460> <BEA-160151> <Registered library Extension-Name: oracle.bi.composer, Specification-Version: 11.1.1, Implementation-Version: 0.1 (WAR).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723491> <BEA-160151> <Registered library Extension-Name: oracle.bi.jbips, Specification-Version: 11.1.1, Implementation-Version: 0.1 (EAR).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723850> <BEA-160151> <Registered library Extension-Name: oracle.bpm.mgmt, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 (EJB).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723865> <BEA-160151> <Registered library Extension-Name: oracle.dconfig-infra, Specification-Version: 11, Implementation-Version: 11.1.1.1.0 (JAR).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723943> <BEA-160151> <Registered library Extension-Name: oracle.jrf.system.filter (WAR).>
    ####<Dec 19, 2014 10:05:24 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954724053> <BEA-160151> <Registered library Extension-Name: oracle.jsp.next, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 (JAR).>
    ####<Dec 19, 2014 10:05:24 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954724068> <BEA-160151> <Registered library Extension-Name: oracle.pwdgen, Specification-Version: 11.1.1, Implementation-Version: 11.1.1.2.0 (JAR).>
    ####<Dec 19, 2014 10:05:24 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954724084> <BEA-160151> <Registered library Extension-Name: oracle.wsm.seedpolicies, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 (JAR).>
    ####<Dec 19, 2014 10:05:24 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954724084> <BEA-160151> <Registered library Extension-Name: orai18n-adf, Specification-Version: 11, Implementation-Version: 11.1.1.1.0 (JAR).>
    ####<Dec 19, 2014 10:05:24 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954724365> <BEA-160151> <Registered library Extension-Name: oracle.webcenter.composer, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 (WAR).>
    ####<Dec 19, 2014 10:05:24 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954724692> <BEA-160151> <Registered library Extension-Name: oracle.webcenter.skin, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 (EAR).>
    ####<Dec 19, 2014 10:05:24 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954724723> <BEA-149059> <Module dms.war of application DMS Application [Version=11.1.1.1.0] is transitioning from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:25 AM SGT> <Warning> <Security> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954725425> <BEA-090668> <Ignored deployment of role "Admin" for resource "type=<url>, application=DMS Application#11.1.1.1.0, contextPath=/dms, uri=/">
    ####<Dec 19, 2014 10:05:25 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954725425> <BEA-149060> <Module dms.war of application DMS Application [Version=11.1.1.1.0] successfully transitioned from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:25 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954725628> <BEA-149059> <Module / of application FMW Welcome Page Application [Version=11.1.0.0.0] is transitioning from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:25 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954725753> <BEA-149060> <Module / of application FMW Welcome Page Application [Version=11.1.0.0.0] successfully transitioned from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:25 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954725847> <BEA-149059> <Module /inspection.wsil of application wsil-wls is transitioning from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:25 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954725987> <BEA-149060> <Module /inspection.wsil of application wsil-wls successfully transitioned from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:27 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954727032> <BEA-149059> <Module NonJ2EEManagement of application NonJ2EEManagement [Version=11.1.1] is transitioning from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:27 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954727251> <BEA-149060> <Module NonJ2EEManagement of application NonJ2EEManagement [Version=11.1.1] successfully transitioned from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:27 AM SGT> <Warning> <Munger> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954727313> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in D:\Oracle\Middleware\user_projects\applications\ClassicDomain\em.ear/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    ####<Dec 19, 2014 10:05:27 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954727422> <BEA-160170> <Imported library Extension-Name: oracle.webcenter.skin, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 for Application em>
    ####<Dec 19, 2014 10:05:27 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954727485> <BEA-160170> <Imported library Extension-Name: adf.oracle.domain, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 for Application em>
    ####<Dec 19, 2014 10:05:27 AM SGT> <Warning> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954727531> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application em is not versioned.>
    ####<Dec 19, 2014 10:05:27 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954727797> <BEA-149059> <Module empty.jar of application em is transitioning from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:27 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954727797> <BEA-149060> <Module empty.jar of application em successfully transitioned from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:27 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954727797> <BEA-149059> <Module /em of application em is transitioning from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:32 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954732461> <BEA-149060> <Module /em of application em successfully transitioned from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:32 AM SGT> <Warning> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954732477> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.rules, referenced from: D:\Oracle\Middleware\user_projects\domains\ClassicDomain\servers\AdminServer\tmp\_WL_user\emai\xalnv4]. Make sure the referenced optional package has been deployed as a library.>
    ####<Dec 19, 2014 10:05:32 AM SGT> <Info> <WebService> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954732960> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceHttps for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 19, 2014 10:05:33 AM SGT> <Info> <WebService> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954733116> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceJms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 19, 2014 10:05:33 AM SGT> <Info> <WebService> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954733132> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseService for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 19, 2014 10:05:33 AM SGT> <Info> <WebService> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954733147> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Jms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 19, 2014 10:05:33 AM SGT> <Info> <WebService> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954733179> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12 for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 19, 2014 10:05:33 AM SGT> <Info> <WebService> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954733179> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Https for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 19, 2014 10:05:33 AM SGT> <Info> <netuix> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954733491> <BEA-423101> <[console] Initializing the NetUIx container>
    ####<Dec 19, 2014 10:05:33 AM SGT> <Info> <netuix> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954733896> <BEA-423120> <WEB-INF/client-classifications.xml file not found at uri [console//WEB-INF/client-classifications.xml]. Classifications functionality not enabled.>
    ####<Dec 19, 2014 10:05:34 AM SGT> <Info> <netuix> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954734411> <BEA-423101> <[consolehelp] Initializing the NetUIx container>
    ####<Dec 19, 2014 10:05:34 AM SGT> <Info> <netuix> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954734489> <BEA-423120> <WEB-INF/client-classifications.xml file not found at uri [consolehelp//WEB-INF/client-classifications.xml]. Classifications functionality not enabled.>
    ####<Dec 19, 2014 10:05:34 AM SGT> <Info> <WebLogicServer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954734645> <BEA-000256> <Invoking weblogic.transaction.internal.StartupClass.main(null)>
    ####<Dec 19, 2014 10:05:34 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954734661> <BEA-149059> <Module dms.war of application DMS Application [Version=11.1.1.1.0] is transitioning from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:34 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954734661> <BEA-149060> <Module dms.war of application DMS Application [Version=11.1.1.1.0] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739091> <BEA-149059> <Module / of application FMW Welcome Page Application [Version=11.1.0.0.0] is transitioning from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739091> <BEA-149060> <Module / of application FMW Welcome Page Application [Version=11.1.0.0.0] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739122> <BEA-149059> <Module /inspection.wsil of application wsil-wls is transitioning from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739122> <BEA-149060> <Module /inspection.wsil of application wsil-wls successfully transitioned from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739200> <BEA-149059> <Module NonJ2EEManagement of application NonJ2EEManagement [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739200> <BEA-149060> <Module NonJ2EEManagement of application NonJ2EEManagement [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <ServletContext-/NonJ2EEManagement> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739497> <BEA-000000> <Can not locate oracleDmsNotifier for now. DMS will discover opmnInfoCenter instead.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739512> <BEA-149059> <Module empty.jar of application em is transitioning from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739528> <BEA-149060> <Module empty.jar of application em successfully transitioned from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739528> <BEA-149059> <Module /em of application em is transitioning from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739528> <BEA-149060> <Module /em of application em successfully transitioned from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Diagnostics> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954771508> <BEA-320000> <The Diagnostics subsystem is initializing on Server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Store> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954771523> <BEA-280008> <Opening the persistent file store "WLS_DIAGNOSTICS" for recovery: directory=D:\Oracle\Middleware\user_projects\domains\ClassicDomain\servers\AdminServer\data\store\diagnostics requestedWritePolicy="Disabled" fileLockingEnabled=true driver="wlfileio3".>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Store> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954771555> <BEA-280009> <The persistent file store "WLS_DIAGNOSTICS" (d07e85b4-188c-42cd-a669-feceb778a8ea) has been opened: blockSize=512 actualWritePolicy="Disabled(single-handle-non-direct)" explicitIOEnforced=false records=29.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Log Management> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954771586> <BEA-170025> <Initialized Domain Logging. Domain log events will be written to D:\Oracle\Middleware\user_projects\domains\ClassicDomain\servers\AdminServer\logs/ClassicDomain.log.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Notice> <Log Management> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954771586> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Diagnostics> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954771695> <BEA-320077> <Initialized the Diagnostic Accessor Service.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Diagnostics> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000005> <1418954771726> <BEA-320117> <The Harvester is being disabled because there are no Harvestable types configured specified.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Diagnostics> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000005> <1418954771726> <BEA-320119> <The Harvester is now in a inactive state.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Notice> <WebLogicServer> <SRVBIAPDEV02> <AdminServer> <main> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000006> <1418954771773> <BEA-000365> <Server state changed to ADMIN>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Notice> <WebLogicServer> <SRVBIAPDEV02> <AdminServer> <main> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000006> <1418954771882> <BEA-000365> <Server state changed to RESUMING>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771929> <BEA-149059> <Module dms.war of application DMS Application [Version=11.1.1.1.0] is transitioning from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771929> <BEA-149060> <Module dms.war of application DMS Application [Version=11.1.1.1.0] successfully transitioned from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771929> <BEA-149059> <Module / of application FMW Welcome Page Application [Version=11.1.0.0.0] is transitioning from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771929> <BEA-149060> <Module / of application FMW Welcome Page Application [Version=11.1.0.0.0] successfully transitioned from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771929> <BEA-149059> <Module /inspection.wsil of application wsil-wls is transitioning from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771929> <BEA-149060> <Module /inspection.wsil of application wsil-wls successfully transitioned from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771929> <BEA-149059> <Module NonJ2EEManagement of application NonJ2EEManagement [Version=11.1.1] is transitioning from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771929> <BEA-149060> <Module NonJ2EEManagement of application NonJ2EEManagement [Version=11.1.1] successfully transitioned from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771945> <BEA-149059> <Module empty.jar of application em is transitioning from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771945> <BEA-149060> <Module empty.jar of application em successfully transitioned from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771945> <BEA-149059> <Module /em of application em is transitioning from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771945> <BEA-149060> <Module /em of application em successfully transitioned from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Management> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771945> <BEA-141053> <The auto deployment poller has not started for the production server.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Server> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000008> <1418954771960> <BEA-002610> <Dynamic Listener Service initialized.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Notice> <Server> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000008> <1418954771960> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:0:100:7f:fffe:7001 for protocols iiop, t3, ldap, snmp, http.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Warning> <Server> <SRVBIAPDEV02> <AdminServer> <DynamicListenThread[Default]> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000009> <1418954771960> <BEA-002611> <Hostname "SRVBIAPDEV02", maps to multiple IP addresses: 10.4.93.117, 0:0:0:0:0:0:0:1>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Notice> <Server> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000008> <1418954771960> <BEA-002613> <Channel "Default[3]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Notice> <Server> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000008> <1418954771960> <BEA-002613> <Channel "Default[2]" is now listening on 0:0:0:0:0:0:0:1:7001 for protocols iiop, t3, ldap, snmp, http.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Notice> <Server> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000008> <1418954771960> <BEA-002613> <Channel "Default" is now listening on 10.4.93.117:7001 for protocols iiop, t3, ldap, snmp, http.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Notice> <WebLogicServer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000008> <1418954771960> <BEA-000329> <Started WebLogic Admin Server "AdminServer" for domain "ClassicDomain" running in Production Mode>
    ####<Dec 19, 2014 10:06:12 AM SGT> <Notice> <WebLogicServer> <SRVBIAPDEV02> <AdminServer> <main> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000006> <1418954772007> <BEA-000365> <Server state changed to RUNNING>
    ####<Dec 19, 2014 10:06:12 AM SGT> <Notice> <WebLogicServer> <SRVBIAPDEV02> <AdminServer> <main> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000006> <1418954772007> <BEA-000360> <Server started in RUNNING mode>
    ####<Dec 19, 2014 10:06:12 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-000000000000000a> <1418954772007> <BEA-160151> <Registered library Extension-Name: bea_wls_async_response (JAR).>
    ####<Dec 19, 2014 10:06:12 AM SGT> <Info> <EJB> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-000000000000000a> <1418954772350> <BEA-010008> <EJB Deploying file: mejb.jar>
    ####<Dec 19, 2014 10:06:13 AM SGT> <Info> <EJB> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-000000000000000a> <1418954773333> <BEA-010009> <EJB Deployed EJB with JNDI name ejb.mgmt.MEJB.>
    ####<Dec 19, 2014 10:07:11 AM SGT> <Info> <Health> <SRVBIAPDEV02> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-000000000000000c> <1418954831724> <BEA-310002> <39% of the total memory in the server is free>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893174> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file D:\Oracle\Middleware\wlserver_10.3\server\lib\DemoIdentity.jks.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893330> <BEA-090169> <Loading trusted certificates from the jks keystore file D:\Oracle\Middleware\wlserver_10.3\server\lib\DemoTrust.jks.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893345> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\PROGRA~1\Java\jdk1.7.0_71\jre\lib\security\cacerts.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Alert> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893455> <BEA-090152> <Demo trusted CA certificate is being used in production mode: [
      Version: V3
      Subject: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
      Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
      Key:  Sun RSA public key, 512 bits
      modulus: 9550192877869244258838480703390456015046425375252278279190673063544122510925482179963329236052146047356415957587628011282484772458983977898996276815440753
      public exponent: 65537
      Validity: [From: Fri Mar 22 04:12:27 SGT 2002,
                   To: Wed Mar 23 04:12:27 SGT 2022]
      Issuer: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
      SerialNumber: [    33f10648 fcde0deb 4199921f d64537f4]
    Certificate Extensions: 1
    [1]: ObjectId: 2.5.29.15 Criticality=true
    KeyUsage [
      Key_CertSign
      Algorithm: [MD5withRSA]
      Signature:
    0000: 9D 26 4C 29 C8 91 C3 A7   06 C3 24 6F AE B4 F8 82  .&L)......$o....
    0010: 80 4D AA CB 7C 79 46 84   81 C4 66 95 F4 1E D8 C4  .M...yF...f.....
    0020: E9 B7 D9 7C E2 23 33 A4   B7 21 E0 AA 54 2B 4A FF  .....#3..!..T+J.
    0030: CB 21 20 88 81 21 DB AC   90 54 D8 7D 79 63 23 3C  .! ..!...T..yc#<
    ] The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893501> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893517> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893517> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G2,OU=(c) 2007 thawte\, Inc. - For authorized use only,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893517> <BEA-090898> <Ignoring the trusted CA certificate "CN=Buypass Class 3 Root CA,O=Buypass AS-983163327,C=NO". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893517> <BEA-090898> <Ignoring the trusted CA certificate "CN=Buypass Class 2 Root CA,O=Buypass AS-983163327,C=NO". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893517> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893517> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893517> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Class 3 Public Primary Certification Authority - G4,OU=(c) 2007 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893517> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893533> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893533> <BEA-090898> <Ignoring the trusted CA certificate "CN=AffirmTrust Commercial,O=AffirmTrust,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893533> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893533> <BEA-090898> <Ignoring the trusted CA certificate "CN=AffirmTrust Premium ECC,O=AffirmTrust,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'web

  • Certificate error while admin server startup (solaris 8, wls 8.1.4)

    HI All,
    I am getting the following error while starting up my admin server using startWebLogic.sh.
    <Feb 5, 2010 7:51:19 AM GMT> <Notice> <WebLogicServer> <BEA-000327> <Starting WebLogic Admin Server "BOS1-ADMIN" for domain "BOS1">
    java.io.IOException: Inconsistent security configuration, Certificate expired: [
    Version: V3
    Subject: EMAILADDRESS=******************, CN=***********, OU=********, O=************, L=*******, ST=*******, C=**
    Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
    Key: com.sun.net.ssl.internal.ssl.JSA_RSAPublicKey@672
    Validity: [From: Thu Feb 03 11:25:08 GMT 2005,
    To: Tue Feb 02 11:25:08 GMT 2010]
    Issuer: EMAILADDRESS=******************, CN=***********, OU=********, O=************, L=*******, ST=*******, C=**
    SerialNumber: 00
    Certificate Extensions: 3
    [1]: ObjectId: 2.5.29.14 Criticality=false
    SubjectKeyIdentifier [
    KeyIdentifier [
    0000: E9 1E E1 30 86 89 7E 1A 67 A2 58 5B 9D 8A 9E 7A ...0....g.X[...z
    0010: C1 CF C4 DA ....
    [2]: ObjectId: 2.5.29.35 Criticality=false
    AuthorityKeyIdentifier [
    KeyIdentifier [
    0000: E9 1E E1 30 86 89 7E 1A 67 A2 58 5B 9D 8A 9E 7A ...0....g.X[...z
    0010: C1 CF C4 DA ....
    EMAILADDRESS=******************, CN=***********, OU=********, O=************, L=*******, ST=*******, C=**
    SerialNumber: 00]
    [3]: ObjectId: 2.5.29.19 Criticality=false
    BasicConstraints:[
    CA:true
    PathLen:2147483647
    Algorithm: MD5withRSA
    Signature:
    0000: 74 15 DF 05 54 27 1D 1D D5 35 F4 99 24 1A 84 1C t...T'...5..$...
    0010: BF 93 25 FA 50 D7 1E 36 66 7F 30 1A EF 67 2A 79 ..%.P..6f.0..g*y
    0020: 4A 72 FD C1 3B 33 05 61 D0 52 92 2D 15 89 68 67 Jr..;3.a.R.-..hg
    0030: E8 13 A6 60 18 38 16 53 16 22 CC 4D 87 19 9F 30 ...`.8.S.".M...0
    0040: 28 F3 3C C0 4C C2 C4 34 69 D3 BA 5C B2 4D 8A FF (.<.L..4i..\.M..
    0050: AA DD BD 04 96 AF 69 05 73 77 8D 93 89 90 5D 23 ......i.sw....]#
    0060: E9 D0 CA 02 5A 20 39 40 85 12 A9 67 04 ED 7B 59 ....Z [email protected]
    0070: 34 FB 31 E7 AD F6 C0 AE E4 5E 66 BB 8E 7D 45 72 4.1......^f...Er
    at weblogic.t3.srvr.SSLListenThread.initSSLContext(SSLListenThread.java:205)
    at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:139)
    at weblogic.t3.srvr.T3Srvr.initializeListenThreads(T3Srvr.java:1637)
    at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:890)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
    at weblogic.Server.main(Server.java:32)
    Any thoughts to share mates????
    I have already posted this topic in general discussion forum and as suggested by faisal posting here as well..Please let me know how to renew certificates????
    Cheers,
    Dinesh

    Hi Dinesh,
    Below are the steps to renew / get new certificates.
    Step A -- Create a Keystore file
    1. Using keytool, enter the following:
    keytool -genkey -alias server -keyalg RSA -keystore your_domain.jks
    'your_domain' in the command above should be the name of the domain you are securing. If you are ordering a Wildcard Certificate, do not include the * in the filename as it is not a valid filename character.
    2. You will be prompted to enter the information for your certificate.
    Please note: When prompted for the first and last name, DO NOT enter your first and last name. Instead, enter the name to which the certificate is being issued (e.g., www.yourdomain.com, mail.yourdomain.com, *.yourdomain.com).
    3. When prompted, enter 'y' or 'yes' to confirm. You will next be asked for a password. You will need to use this same password when generating a CSR and importing your certificates.
    Step B -- Generate a CSR from your new keystore
    1.     Use keytool to create a Certificate Signing Request from your keystore:
    keytool -certreq -alias server -keyalg RSA -file your_domain.csr -keystore your_domain.jks
    Again, 'your_domain' is the name of the domain you are securing. (without the * character if you are ordering a Wildcard Certificate).
    2.     Enter the keystore password.
    3.     Submit the CSR to the Certificate Authority for the certificates.
    Step C: Import and Install the Certificates.
    1.     First you will need to install the Root CA Certificate into your keystore. Copy-and-paste the root certificate from the body of the fulfillment email into a simple text editor such as Notepad.
    2.     Save the file to your server as trustroot.pem in the same directory where your keystore was created.
    3.     Using the java keytool command line utility, import the root certificate geotrustroot.pem into your keystore using the following command:
    keytool -import -alias geotrustca -keystore mykeystore -file geotrustroot.pem
    The command should be typed on one line. This command imports the GeoTrust Root CA Certificate into the keystore named mykeystore.
    Step D: Import and Install the SSL Server Certificate
    1.     Next install your SSL Server Certificate (public key) into your keystore. Copy-and-paste the server certificate from the body of the fulfillment email into a simple text editor such as Notepad.
    2.     Save the file to your server as public.pem in the same directory where your keystore was created.
    3.     Using the java keytool command line utility, import the SSL server certificate public.pem into your keystore using the following command:
    keytool -import -alias tomcat -keystore mykeystore -file public.pem
    The command should be typed on one line. This command imports the SSL server certificate into the keystore named
    mykeystore.
    Step E: Configuring Keystores
    1.     Both the GeoTrust root CA and SSL server certificates are now installed on your server. Next you will need to configure the keystores by following the instructions in the WebLogic documentation section Configuring Keystores.
    2.     Restart the WebLogic server.
    Hope the information helps.
    Regards,
    Raj

  • Configuring Weblogic Server for X.509 Smart Card Authentication

    0 down vote favorite
    share [g+] share [fb] share [tw]
    I am running Oracle Weblogic 11g (10.3.6) and attempting to configure two-way SSL (client certificate requested and enforced). The client certificate is on a smart card.
    I have enabled "basic" ssl in the weblogic server, and used keytool to import the relevant root CA certificates into the DemoTruststore.jks file. I have set the Two-way client cert behavior to Client Certs Requested and Enforced for the server.
    Unfortunately, attempting to access my application causes the following:
    <pre>
    <Certificate chain received from 127.0.0.1 - 127.0.0.1 was incomplete.>
    <NO_CERTIFICATE alert was received from 127.0.0.1 - 127.0.0.1. Verify the SSL configuration has a proper SSL certificate chain and private key specified.>
    <Certificate chain received from 127.0.0.1 - 127.0.0.1 was incomplete.>
    </pre>
    The ActivClient dialog never appears to select a certificate from the Smart Card, and a pin is never requested. Therefore, I think I misconfigured something.
    Help would be greatly appreciated.
    Jason

    Hello Mukunthan Damodharan,
    this means that the SSL Server Certificate has not his fully quallified name in the subject alternative name extension of the X.509 certificate.
    You can create a valid one or disbale that check in the Secure Login Client.
    How does the configuration gets to the clients?
    With the Policy Download you can disable that check over the Secure Login Server Administration console in the corresponding authentication profile.
    If manually you can change the following registry key:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\SAP\SecureLogin\profiles\<profile name>
    "sslHostAlternativeNameCheck"=dword:00000000
    the value 0 disable that check on the client.
    best regards
    Alexander Gimbel

  • Apache 2.2 21 forward Proxy 2 way SSL for weblogic server as a client

    Hi All,
    Currently, i am trying to implement a forward SSL proxy. The client will hit my apache server which in return will hit a IIS Server.
    scenarios 1
    client(weblogic)--*2 way SSL*Apache(forward proxy)*2 way SSL*-- IIS
    If i were to implement 1 way ssl, i am able to see the content of the website.
    client(weblogic) --- Apache(forward proxy) --- IIS
    If i were to launch the web browser from the client machine (with the client certificate imported in the browser), i am able to view the content in the IIS. But if i were to simulate the connection from weblogic server, it just give me end of file exception (response contain no data) on the logs.
    Below is my configuration
    Listen 8080
    <VirtualHost default:8080>
    ServerName serverA
    ErrorLog "logs/ssl_error_log"
    CustomLog "logs/ssl_access_log" common
    SSLProxyEngine On
    SSLProxyMachineCertificateFile /certificate/servercert.cer
    SSLProxyCACertificateFile /certificate/rootCA.cer
    SSLProxyVerify require
    SSLProxyVerifyDepth 10
    ProxyRequests On
    ProxyVia On
    AllowConnect 12345
    <Proxy *>
    Order allow,deny
    Allow from all
    </Proxy>
    </VirtualHost>
    For 2 way SSL, will the client forward their client certificate to my apache proxy server and apache will on the client behalf forward the client certificate to the IIS server for authenication?
    Or the SSL authenication still happen between the client (weblogic) and the end server (IIS) bypassing the proxy server.
    Please help.

    It is a domain wide setting. Can you not create a new domain? I do not think that you can handle it from web.xml. I have never seen such thing in web.xml.

  • How to delete the deployed composite in weblogic server 11g

    Can someone tell me how to delete the deployed composite in weblogic server 11g ?I'm facing an issue where the weblogic server is getting started and immediately after sometime the server changes to "Force shutdown"..When i checked the logs,there is an error in one of the composite i deployed..So now i wanted to delete the deployed composite?Please help ....
    Thanks

    Hi
    1. Deleting a domain will not hold any references. But make sure that under your user_projects/applications also remove the folder that matches with your domain. Basically under user_projects folder you will see 2 folders named applications and domains. When you create a domain say mySoaDomain, it will crate a folder with the same name under applications folder also with few files like em.ear. If you do this, then you can crate a new soa domain and use the same old name.
    2. NOW comes the most important thing. If you create a new SOADomain, at one point, you had to give details for soainfra and mds schemas. If you give your current existing db details (that was used for your old deleted domain), then you may still have the issues. Because the soainfra db may still have the instances for your old process.
    3. If you really want to have a full clean soa domain, here is what you do:
    a) Run rcu and drop the existing schemas for soainfra and mds.
    b) Run rcu again and create above schemas again.
    c) Now create SOADomain using config wizard and refer above clean rcu db and you are all set.
    3. Under your domain root folder, just searh for files named with your workflow and you should see the .jar location.
    Thanks
    Ravi Jegga

  • Error in Starting Weblogic Server 12c

    Hi,
    I get the below error when I run Weblogic server 12c. I am running it on Windows 7 Enterprise sp1.
    I have installed the products. Oracle DB 11.2.0.1.0, RCU 11.1.1.6.0, Webcenter Portal & Content- 11.1.1.8.0
    The main error I see is Opening of file based keystore failed from below log.
    C:\Oracle\Middleware\user_projects\domains\New_domain\bin>startWebLogic.cmd >> log.txt
    'C:\Oracle\MIDDLE~1\ORACLE~3\ucm\idc\bin\\Installer64' is not recognized as an internal or external command,
    operable program or batch file.
    'C:\Oracle\MIDDLE~1\ORACLE~3\ucm\idc\bin\\Installer' is not recognized as an internal or external command,
    operable program or batch file.
    'C:\Oracle\MIDDLE~1\ORACLE~3\ucm\idc\bin\\Installer' is not recognized as an internal or external command,
    operable program or batch file.
    'C:\Oracle\MIDDLE~1\ORACLE~3\ucm\idc\bin\\Installer' is not recognized as an internal or external command,
    operable program or batch file.
    FINDSTR: No search strings
    java version "1.6.0_29"
    Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
    Java HotSpot(TM) Client VM (build 20.4-b02, mixed mode)
    6 Sep, 2013 2:27:09 PM oracle.security.jps.internal.keystore.file.FileKeyStoreManager openKeyStore
    WARNING: Opening of file based keystore failed.
    JAVA Memory arguments: -Xms512m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m  -XX:MaxPermSize=512m
    WLS Start Mode=Development
    CLASSPATH=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;C:\Oracle\MIDDLE~1\patch_wls1211\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_12.1.1.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;;C:\Oracle\MIDDLE~1\ORACLE~1\soa\modules\commons-cli-1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:\Oracle\Middleware\oracle_common\webcenter\modules\oracle.portlet.server_11.1.1\oracle-portlet-api.jar;C:\Oracle\Middleware\Oracle_WC1\wcps-services-app\modules\oracle.wcps_11.1.1\wcps-connection-mbeans.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\Oracle\MIDDLE~1\WLSERV~1.1\common\derby\lib\derbyclient.jar;C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\xqrl.jar;C:\Oracle\MIDDLE~1\ORACLE~3\ucm\idc\jlib\idcloader.jar;C:\Oracle\MIDDLE~1\ORACLE~3\ucm\idc\components\NativeOsUtils\classes-NativeOsUtils.jar;
    PATH=C:\Oracle\MIDDLE~1\patch_wls1211\profiles\default\native;C:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\native;C:\Oracle\MIDDLE~1\WLSERV~1.1\server\native\win\32;C:\Oracle\MIDDLE~1\WLSERV~1.1\server\bin;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1\bin;C:\Oracle\MIDDLE~1\JDK160~1\jre\bin;C:\Oracle\MIDDLE~1\JDK160~1\bin;C:\app2\v.narasakumar.kuchi\product\11.2.0\dbhome_1\bin;C:\app1\v.narasakumar.kuchi\product\11.2.0\dbhome_1\bin;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Java\jdk1.6.0_38\bin;C:\Oracle\MIDDLE~1\WLSERV~1.1\server\native\win\32\oci920_8
    *  To start WebLogic Server, use a username and   *
    *  password assigned to an admin-level user.  For *
    *  server administration, use the WebLogic Server *
    *  console at http:\\hostname:port\console        *
    starting weblogic with Java version:
    Starting WLS with line:
    C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client   -Xms512m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m  -XX:MaxPermSize=512m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\weblogic.policy  -Xverify:none -Djava.endorsed.dirs=C:\Oracle\MIDDLE~1\JDK160~1/jre/lib/endorsed;C:\Oracle\MIDDLE~1\WLSERV~1.1/endorsed  -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.1 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.1\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.1\server  -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\NEW_DO~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\NEW_DO~1\config\FMWCON~1\servers\AdminServer -Doracle.domain.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\NEW_DO~1\config\FMWCON~1  -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~1\USER_P~1\domains\NEW_DO~1\config\FMWCON~1\carml  -Digf.arisidstack.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\NEW_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\Oracle\MIDDLE~1\USER_P~1\domains\NEW_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\NEW_DO~1\servers\AdminServer\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol  -Dweblogic.jdbc.remoteEnabled=false -Djps.auth.debug=false -Dtangosol.coherence.log=jdk -DjiveHome=C:\Oracle\MIDDLE~1\USER_P~1\domains\NEW_DO~1\config\fmwconfig\servers\AdminServer\owc_discussions -DUSE_JAAS=false -Djps.policystore.hybrid.mode=false -Djps.combiner.optimize.lazyeval=true -Djps.combiner.optimize=true -Djps.auth=ACC -Doracle.core.ojdl.logging.usercontextprovider=oracle.core.ojdl.logging.impl.UserContextImpl -Doracle.webcenter.analytics.disable-native-partitioning=false -Doracle.webcenter.tagging.scopeTags=false -Djava.awt.headless=true -Doracle.webcenter.tagging.scopeTags=false -XX:+UseParallelGC -XX:+DisableExplicitGC -Dportlet.oracle.home=C:\Oracle\Middleware\oracle_common -Dwc.oracle.home=C:\Oracle\Middleware\Oracle_WC1  -Dipm.oracle.home=C:\Oracle\Middleware\Oracle_ECM1 -Doracle.capture.home=C:\Oracle\Middleware\Oracle_ECM1 -Ducm.oracle.home=C:\Oracle\MIDDLE~1\ORACLE~3 -Dirm.oracle.home=C:\Oracle\Middleware\Oracle_ECM1 -Dem.oracle.home=C:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=true  -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1211\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sysext_manifest_classpath  weblogic.Server
    <6 Sep, 2013 2:27:03 PM 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>
    <6 Sep, 2013 2:27:03 PM 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>
    <6 Sep, 2013 2:27:03 PM IST> <Notice> <WebLogicServer> <BEA-000395> <The following extensions directory contents added to the end of the classpath:
    C:\Oracle\Middleware\user_projects\domains\New_domain\lib\mbeantypes\csp-id-asserter.jar;C:\Oracle\Middleware\user_projects\domains\New_domain\lib\mbeantypes\jps-wls-trustprovider.jar.>
    <6 Sep, 2013 2:27:04 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 20.4-b02 from Sun Microsystems Inc..>
    <6 Sep, 2013 2:27:05 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for 13340309 Thu Feb 16 18:30:21 IST 2012
    WebLogic Server Temporary Patch for 13019800 Mon Jan 16 16:53:54 IST 2012
    WebLogic Server Temporary Patch for BUG13391585 Thu Feb 02 10:18:36 IST 2012
    WebLogic Server Temporary Patch for 13516712 Mon Jan 30 15:09:33 IST 2012
    WebLogic Server Temporary Patch for BUG13641115 Tue Jan 31 11:19:13 IST 2012
    WebLogic Server Temporary Patch for BUG13603813 Wed Feb 15 19:34:13 IST 2012
    WebLogic Server Temporary Patch for 13424251 Mon Jan 30 14:32:34 IST 2012
    WebLogic Server Temporary Patch for 13361720 Mon Jan 30 15:24:05 IST 2012
    WebLogic Server Temporary Patch for BUG13421471 Wed Feb 01 11:24:18 IST 2012
    WebLogic Server Temporary Patch for BUG13657792 Thu Feb 23 12:57:33 IST 2012
    WebLogic Server 12.1.1.0  Wed Dec 7 08:40:57 PST 2011 1445491 >
    <6 Sep, 2013 2:27:06 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>
    <6 Sep, 2013 2:27:07 PM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool.>
    <6 Sep, 2013 2:27:07 PM IST> <Notice> <LoggingService> <BEA-320400> <The log file C:\Oracle\Middleware\user_projects\domains\New_domain\servers\AdminServer\logs\AdminServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms, such as Windows.>
    <6 Sep, 2013 2:27:07 PM IST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Oracle\Middleware\user_projects\domains\New_domain\servers\AdminServer\logs\AdminServer.log00009. Log messages will continue to be logged in C:\Oracle\Middleware\user_projects\domains\New_domain\servers\AdminServer\logs\AdminServer.log.>
    <6 Sep, 2013 2:27:07 PM IST> <Notice> <Log Management> <BEA-170019> <The server log file C:\Oracle\Middleware\user_projects\domains\New_domain\servers\AdminServer\logs\AdminServer.log is opened. All server side log events will be written to this file.>
    <6 Sep, 2013 2:27:09 PM IST> <Error> <Security> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-06514: Opening of file based keystore failed.>
    <6 Sep, 2013 2:27:09 PM IST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-06514: Opening of file based keystore failed.
    weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-06514: Opening of file based keystore failed.
      at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)
      at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)
      at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
      at weblogic.security.SecurityService.start(SecurityService.java:148)
      at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
      Truncated. see log file for complete stacktrace
    Caused By: oracle.security.jps.JpsRuntimeException: JPS-06514: Opening of file based keystore failed.
      at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:170)
      at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:383)
      at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
      at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
      at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
      Truncated. see log file for complete stacktrace
    Caused By: oracle.security.jps.JpsException: JPS-06514: Opening of file based keystore failed.
      at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPDPService(PolicyUtil.java:2984)
      at oracle.security.jps.internal.policystore.PolicyUtil.getPDPService(PolicyUtil.java:3226)
      at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:167)
      at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:383)
      at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
      Truncated. see log file for complete stacktrace
    Caused By: oracle.security.jps.service.keystore.KeyStoreServiceException: JPS-06514: Opening of file based keystore failed.
      at oracle.security.jps.internal.keystore.file.FileKeyStoreManager.openKeyStore(FileKeyStoreManager.java:406)
      at oracle.security.jps.internal.keystore.file.FileKeyStoreManager.openKeyStore(FileKeyStoreManager.java:352)
      at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.doInit(FileKeyStoreServiceImpl.java:122)
      at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:88)
      at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(KeyStoreProvider.java:164)
      Truncated. see log file for complete stacktrace
    >
    <6 Sep, 2013 2:27:09 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.>
    <6 Sep, 2013 2:27:09 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down.>
    <6 Sep, 2013 2:27:09 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>
    I get the same error when I execute "startWeblogic.cmd" from domain folder and bin folder.
    Any help is appreciated. Thanks.

    Hi,
    Few comments here...
    1) Seems your environment is not setup correctly but that is not the big cause here.....
    2) This one is important, it seems that you installed weblogic using a different account and are trying to run it from a different account.
    So the account with which you are trying to run weblogic does not have proper permission on
    MW_HOME\user_projects\domains\bifoundation_domain\config\fmwconfig\bootstrap\cwallet.sso
    Right click on the file and go in properties ..
    Enable full control,modify,Read and execute,read and write permissions for the user you are trying to start weblogic and apply it.
    if this simple steps doesnt work, please enable more logging by adding "-Djava.security.debug=jpspolicy" to startup option and grab more details.
    Good Luck let me know if this works.

  • Error in starting WebLogic Server Process

    Hi,
    I'm suffering a serious sproblem that results in failure in starting WebLogic
    Server Processes. What i'm trying is to use "PostBindUID" nad "PostBindGID" services
    that changes the processes owner from "root" to "somebody". However, once i set
    it in Console (Configure a new Unix Machine), the server cannot start afterwards
    with the following errors in the screen (when i execute startWebLogic.sh) ...
    An unexpected exception has been detected in native code outside the VM.
    Unexpected Signal : 11 occurred at PC=0x917116B8
    Function=Java_weblogic_platform_Unix_getEGroup0+0x28
    Library=/opt/weblogic/bea/weblogic81/server/lib/solaris/libweblogicunix1.so
    Current Java thread:
    at weblogic.platform.Unix.getEGroup0(Native Method)
    at weblogic.platform.Unix.getEffectiveGroup(Unix.java:95)
    at weblogic.t3.srvr.T3Srvr.switchEffectiveGroup(T3Srvr.java:2080)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:1001)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
    at weblogic.Server.main(Server.java:32)
    Dynamic libraries:
    0x10000 /opt/weblogic/bea/jdk141_05/bin/java
    0xff360000 /usr/lib/libthread.so.1
    0xff3a0000 /usr/lib/libdl.so.1
    0xff280000 /usr/lib/libc.so.1
    0xff350000 /usr/platform/FJSV,GPUZC-M/lib/libc_psr.so.1
    0xfe000000 /opt/weblogic/bea/jdk141_05/jre/lib/sparc/server/libjvm.so
    0xff210000 /usr/lib/libCrun.so.1
    0xff1f0000 /usr/lib/libsocket.so.1
    0xff100000 /usr/lib/libnsl.so.1
    0xff0b0000 /usr/lib/libm.so.1
    0xff240000 /usr/lib/libw.so.1
    0xff090000 /usr/lib/libmp.so.2
    0xff060000 /opt/weblogic/bea/jdk141_05/jre/lib/sparc/native_threads/libhpi.so
    0xff030000 /opt/weblogic/bea/jdk141_05/jre/lib/sparc/libverify.so
    0xfe7c0000 /opt/weblogic/bea/jdk141_05/jre/lib/sparc/libjava.so
    0xfe7a0000 /opt/weblogic/bea/jdk141_05/jre/lib/sparc/libzip.so
    0xfe670000 /usr/lib/nss_files.so.1
    0x91850000 /opt/weblogic/bea/jdk141_05/jre/lib/sparc/libnet.so
    0x91710000 /opt/weblogic/bea/weblogic81/server/lib/solaris/libweblogicunix1.so
    0x914d0000 /opt/weblogic/bea/jdk141_05/jre/lib/sparc/libnio.so
    0x914b0000 /usr/lib/librt.so.1
    0x91260000 /usr/lib/libaio.so.1
    0x91240000 /opt/weblogic/bea/jdk141_05/jre/lib/sparc/libioser12.so
    0x90d60000 /usr/lib/nss_dns.so.1
    0x90b30000 /usr/lib/libresolv.so.2
    Local Time = Mon Jun 14 18:16:04 2004
    Elapsed Time = 143
    # The exception above was detected in native code outside the VM
    # Java VM: Java HotSpot(TM) Server VM (1.4.1_05-b01 mixed mode)
    Abort
    If anyone have any thoughts, please kindly let me know.
    Many thanks,
    Ralph

    Hi,
    Few comments here...
    1) Seems your environment is not setup correctly but that is not the big cause here.....
    2) This one is important, it seems that you installed weblogic using a different account and are trying to run it from a different account.
    So the account with which you are trying to run weblogic does not have proper permission on
    MW_HOME\user_projects\domains\bifoundation_domain\config\fmwconfig\bootstrap\cwallet.sso
    Right click on the file and go in properties ..
    Enable full control,modify,Read and execute,read and write permissions for the user you are trying to start weblogic and apply it.
    if this simple steps doesnt work, please enable more logging by adding "-Djava.security.debug=jpspolicy" to startup option and grab more details.
    Good Luck let me know if this works.

Maybe you are looking for