3 Replies Latest reply on Oct 3, 2012 6:52 PM by 866532

    FA Framework starting Admin mode after deployment

    866532
      I had to uninstall and re-install foundation service on our HTTP server and also upgrade the WL to 10.1.3.5 for all the servers. After doing so, we redeployed all the products. Foundation Service starts with no issues, but when I start R&A and EAS, these 2 products fail with deployments error and start in the ADMIN mode. We have also tried removing deployments from the WL and and run the configurator to deploy. The issue still remains the same. Would really appreciate all the help.

      <Sep 25, 2012 11:37:28 AM EDT> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
      <Sep 25, 2012 11:37:28 AM EDT> <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>
      <Sep 25, 2012 11:37:29 AM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 17.0-b17 from Sun Microsystems Inc.>
      <Sep 25, 2012 11:37:30 AM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
      <Sep 25, 2012 11:37:32 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
      <Sep 25, 2012 11:37:32 AM EDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
      <Sep 25, 2012 11:37:32 AM EDT> <Notice> <Log Management> <BEA-170019> <The server log file D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\RaFramework0\logs\RaFramework0.log is opened. All server side log events will be written to this file.>
      <Sep 25, 2012 11:38:03 AM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
      <Sep 25, 2012 11:38:08 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
      <Sep 25, 2012 11:38:08 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
      <Sep 25, 2012 11:38:26 AM EDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'RAFRAMEWORK [Version=11.1.2.0]' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: xerces, exact-match: false]..
      weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: xerces, exact-match: false].
           at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
           at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
           at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
           at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
           at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
           Truncated. see log file for complete stacktrace
      >
      <Sep 25, 2012 11:38:26 AM EDT> <Emergency> <Deployer> <BEA-149259> <Server 'RaFramework0' in cluster 'RaFramework' is being brought up in administration state due to failed deployments.>
      <Sep 25, 2012 11:38:32 AM EDT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
      <Sep 25, 2012 11:38:32 AM EDT> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
      <Sep 25, 2012 11:38:32 AM EDT> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of RaFramework.>
      <Sep 25, 2012 11:39:02 AM EDT> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoIdentity.jks.>
      <Sep 25, 2012 11:39:03 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks.>
      <Sep 25, 2012 11:39:03 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file D:\Oracle\Middleware\jdk160_21\jre\lib\security\cacerts.>
      <Sep 25, 2012 11:39:03 AM EDT> <Alert> <Security> <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: Thu Mar 21 15:12:27 EST 2002,
                     To: Tue Mar 22 16:12:27 EDT 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.>
      <Sep 25, 2012 11:39:03 AM EDT> <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.>
      <Sep 25, 2012 11:39:03 AM EDT> <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.>
      <Sep 25, 2012 11:39:03 AM EDT> <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.>
      <Sep 25, 2012 11:39:03 AM EDT> <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.>
      <Sep 25, 2012 11:39:03 AM EDT> <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.>
      <Sep 25, 2012 11:39:03 AM EDT> <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.>
      <Sep 25, 2012 11:39:03 AM EDT> <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.>
      <Sep 25, 2012 11:39:03 AM EDT> <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.>
      <Sep 25, 2012 11:39:03 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default[4]" is now listening on 0:0:0:0:0:0:0:1:45000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
      <Sep 25, 2012 11:39:03 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on fe80:0:0:0:0:100:7f:fffe:45000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
      <Sep 25, 2012 11:39:03 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 172.19.13.73:45000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
      <Sep 25, 2012 11:39:03 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 127.0.0.1:45000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
      <Sep 25, 2012 11:39:03 AM EDT> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[2]" is now listening on fe80:0:0:0:0:100:7f:fffe:45043 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
      <Sep 25, 2012 11:39:03 AM EDT> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[4]" is now listening on 0:0:0:0:0:0:0:1:45043 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
      <Sep 25, 2012 11:39:03 AM EDT> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on 172.19.13.73:45043 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
      <Sep 25, 2012 11:39:03 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:0:5efe:ac13:d49:45000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
      <Sep 25, 2012 11:39:03 AM EDT> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[3]" is now listening on 127.0.0.1:45043 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
      <Sep 25, 2012 11:39:03 AM EDT> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[1]" is now listening on fe80:0:0:0:0:5efe:ac13:d49:45043 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
      <Sep 25, 2012 11:39:03 AM EDT> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "RaFramework0" for domain "EPMSystem" running in Production Mode>
      <Sep 25, 2012 11:39:03 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
      <Sep 25, 2012 11:39:03 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in ADMIN mode>
        • 1. Re: FA Framework starting Admin mode after deployment
          741513
          I saw this in your log: Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: xerces, exact-match: false

          This means that there's a jar file missing and I'm suspecting it may be due to the WL upgrade. Did you follow all the steps required in the WL upgrade?

          You would need to look at the weblogic-application.xml file ro R&A Framework Web App and see which xerces jar file it is looking for. I did a search on one of my servers and saw multiple xerces*.jar file in different locations (EPM Common, Admin Server, etc.)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   
          • 2. Re: FA Framework starting Admin mode after deployment
            AlexLiu
            In version 11.1.2.1, there is a defect related to the old JAR file, which required a patch. Unfortunately, I do not remember the defect/patch number and I also do not have my old notes.

            In the new 11.1.2.x version, the weblogic came with the new software, make sure the Oracle Manager in the Services is running.
            • 3. Re: FA Framework starting Admin mode after deployment
              866532
              great catch luisrcastillo.

              In weblogic: under Deployments > xerces(11.1.2.0, 11.1.2.0) > Target; none of my deployed managed servers were checked. After I checked the all the deployed managed server, it worked.

              thanks for looking into it.