14 Replies Latest reply: Jan 30, 2012 11:29 AM by user9503787 RSS

    Errors starting Portal Admin Server after configuring RDBMS Security Store.

    712492
      Hi,
      I'm using WLST to build and configure the portal domain. I've already had our DBA run all the necessary scripts on the Database.
      We are using WLP 10.3 on RHEL 4 and Oracle 10G RAC. I read on some thread that RDBMS is only compatble with verion 10.3.2 but why is the feature in 10.3?

      The error below seems to point to the URL; does this mean that the RDBMS config does not support RAC databases?

      Hope someone can shed light on this as it's pretty urgent.

      Many thanks
      A


      This is the configuration for the created security store:-

      -rw- CompatibilityObjectName null
      -rw- ConnectionProperties
      user=rdbms_user,portNumber=1521,serviceName=portal_db_service
      -rw- ConnectionURL
      jdbc:oracle:thin:@(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST =
      portal_host)(PORT = 1521))(CONNECT_DATA = (SERVER = DEDICATED)
      (SERVICE_NAME = portal_db_service)))
      -rw- DriverName
      oracle.jdbc.xa.client.OracleXADataSource
      -rw- JMSExceptionReconnectAttempts 0
      -rw- JMSTopic null
      -rw- JMSTopicConnectionFactory null
      -rw- JNDIPasswordEncrypted null
      -rw- JNDIUsername null
      -rw- Name RDBMSSecurityStore
      -rw- NotificationProperties null
      -rw- PasswordEncrypted ********
      -rw- Username rdbms_user

      This is the error I'm getting when I attempt to start the Admin Server :-

      ####<10-May-2010 18:19:28 o'clock BST> <Info> <Security> <server>
      <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue:
      'weblogic.kernel.Default (sel
      f-tuning)'> <<WLS Kernel>> <1273511968053> <BEA-000000> <Using
      dictionary class "kodo.jdbc.sql.KodoOracleDictionary".>
      ####<10-May-2010 18:19:28 o'clock BST> <Info> <Security> <server>
      <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue:
      'weblogic.kernel.Default (sel
      f-tuning)'> <<WLS Kernel>> <1273511968246> <BEA-000000> <OpenJPA
      is now connecting to the database in order to figure out what JDBC
      driver you are using
      , as OpenJPA must alter its behavior for this database depending on the
      driver vendor. To avoid this connection, set the DriverVendor value in
      your openjpa.j
      dbc.DBDictionary configuration property to one of the following values:
      oracle, oracle92 (for the 9.2 driver), datadirect, datadirect61 (for
      driver versions <= 3.1), other
      For example:
      openjpa.jdbc.DBDictionary: oracle(DriverVendor=oracle92)>
      ####<10-May-2010 18:19:28 o'clock BST> <Info> <Security> <server>
      <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue:
      'weblogic.kernel.Default (sel
      f-tuning)'> <<WLS Kernel>> <1273511968257> <BEA-090511> <The
      following exception has occurred:

      com.bea.common.engine.ServiceInitializationException:
      <openjpa-1.1.0-r422266:657916 fatal internal error>
      org.apache.openjpa.util.InternalException: There was
      an error when invoking the static getInstance method on the named
      factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested
      exception for detai
      ls.
      at
      com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
      iceEngineImpl.java:365)
      at
      com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
      iceEngineImpl.java:315)
      at
      com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEn
      gineImpl.java:257)
      at
      com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java
      :72)
      at
      weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(Unk
      nown Source)
      at
      weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(Unk
      nown Source)
      at
      weblogic.security.service.CSSWLSDelegateImpl.initialize(Unknown Source)
      at
      weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.Initi
      alizeServiceEngine(Unknown Source)
      at
      weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
      alizeRealm(Unknown Source)
      at
      weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadR
      ealm(Unknown Source)
      at
      weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
      alizeRealms(Unknown Source)
      at
      weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
      alizeRealms(Unknown Source)
      at
      weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
      alize(Unknown Source)
      at
      weblogic.security.service.SecurityServiceManager.initialize(Unknown
      Source)
      at
      weblogic.security.SecurityService.start(SecurityService.java:141)
      at
      weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
      <openjpa-1.1.0-r422266:657916 fatal internal error>
      org.apache.openjpa.util.InternalException: There was an error when
      invoking the static getInstance method
      on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory".
      See the nested exception for details.
      at
      org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:95)
      at
      com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSeri
      vceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)
      at
      com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(S
      toreServiceDelegate.java:145)
      at
      com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(St
      oreServiceDelegate.java:98)
      at
      com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServ
      iceImpl.java:76)
      at
      com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
      iceEngineImpl.java:363)
      at
      com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
      iceEngineImpl.java:315)
      at
      com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEn
      gineImpl.java:257)
      at
      com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java
      :72)
      at
      weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(Unk
      nown Source)
      at
      weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(Unk
      nown Source)
      at
      weblogic.security.service.CSSWLSDelegateImpl.initialize(Unknown Source)
      at
      weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.Initi
      alizeServiceEngine(Unknown Source)
      at
      weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
      alizeRealm(Unknown Source)
      at
      weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadR
      ealm(Unknown Source)
      at
      weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
      alizeRealms(Unknown Source)
      at
      weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
      alize(Unknown Source)
      at
      weblogic.security.service.SecurityServiceManager.initialize(Unknown
      Source)
      at
      weblogic.security.SecurityService.start(SecurityService.java:141)
      at
      weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
      java.lang.RuntimeException: There were errors initializing your
      configuration: <openjpa-1.1.0-r422266:657916 fatal store error>
      org.apache.openjpa.util.StoreE
      xception: Invalid Oracle URL specified: OracleDataSource.makeURL
      at
      org.apache.openjpa.jdbc.schema.DataSourceFactory.installDBDictionary(Dat
      aSourceFactory.java:235)
      at
      org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(
      JDBCConfigurationImpl.java:684)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at
      sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
      a:39)
      at
      sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
      Impl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at
      org.apache.openjpa.lib.conf.ConfigurationImpl.instantiateAll(Configurati
      onImpl.java:288)
      at
      org.apache.openjpa.conf.OpenJPAConfigurationImpl.instantiateAll(OpenJPAC
      onfigurationImpl.java:1409)
      at
      org.apache.openjpa.kernel.AbstractBrokerFactory.makeReadOnly(AbstractBro
      kerFactory.java:646)
      at
      org.apache.openjpa.kernel.AbstractBrokerFactory.pool(AbstractBrokerFacto
      ry.java:131)
      at
      kodo.jdbc.kernel.KodoJDBCBrokerFactory.getInstance(KodoJDBCBrokerFactory
      .java:43)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at
      sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
      a:39)
      at
      sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
      Impl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at
      org.apache.openjpa.kernel.Bootstrap.invokeFactory(Bootstrap.java:124)
      at
      org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:90)
      at
      com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSeri
      vceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)
      at
      com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(S
      toreServiceDelegate.java:145)
      at
      com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(St
      oreServiceDelegate.java:98)
      at
      com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServ
      iceImpl.java:76)
      at
      com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
      iceEngineImpl.java:363)
      at
      com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
      iceEngineImpl.java:315)
      at
      com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEn
      gineImpl.java:257)
      at
      com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java
      :72)
      at
      weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(Unk
      nown Source)
      at
      weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(Unk
      nown Source)
      at
      weblogic.security.service.CSSWLSDelegateImpl.initialize(Unknown Source)
      at
      weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.Initi
      alizeServiceEngine(Unknown Source)
      at
      weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
      alizeRealm(Unknown Source)
      at
      weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadR
      ealm(Unknown Source)
      at
      weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
      alizeRealms(Unknown Source)
      at
      weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
      alize(Unknown Source)
      at
      weblogic.security.service.SecurityServiceManager.initialize(Unknown
      Source)
      at
      weblogic.security.SecurityService.start(SecurityService.java:141)
      at
      weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
      Caused by: java.sql.SQLException: Invalid Oracle URL specified:
      OracleDataSource.makeURL
      at
      oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:
      70)
      at
      oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112)
      at
      oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:17
      3)
      at
      oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:22
      9)
      at
      oracle.jdbc.pool.OracleDataSource.makeURL(OracleDataSource.java:1234)
      at
      oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:18
      4)
      at
      org.apache.openjpa.lib.jdbc.DelegatingDataSource.getConnection(Delegatin
      gDataSource.java:113)
      at
      org.apache.openjpa.lib.jdbc.DecoratingDataSource.getConnection(Decoratin
      gDataSource.java:93)
      at
      org.apache.openjpa.jdbc.schema.DataSourceFactory.installDBDictionary(Dat
      aSourceFactory.java:227)
      ... 37 more

      <openjpa-1.1.0-r422266:657916 fatal store error>
      org.apache.openjpa.util.StoreException: Invalid Oracle URL specified:
      OracleDataSource.makeURL
      at
      org.apache.openjpa.jdbc.schema.DataSourceFactory.installDBDictionary(Dat
      aSourceFactory.java:235)
      at
      org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(
      JDBCConfigurationImpl.java:684)
      at
      org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCCon
      figurationImpl.java:782)
      at
      org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getDataSource2(JDBCCo
      nfigurationImpl.java:789)
      at
      org.apache.openjpa.jdbc.sql.OracleDictionary.ensureDriverVendor(OracleDi
      ctionary.java:253)
      at
      kodo.jdbc.sql.OracleAdvancedSQL.setDriverVendorDefaults(OracleAdvancedSQ
      L.java:50)
      at
      kodo.jdbc.sql.OracleAdvancedSQL.getBatchLimit(OracleAdvancedSQL.java:28)
      at
      kodo.jdbc.kernel.AutoOrderUpdateManager.setConfiguration(AutoOrderUpdate
      Manager.java:56)
      at
      org.apache.openjpa.lib.conf.Configurations.configureInstance(Configurati
      ons.java:473)
      at
      org.apache.openjpa.lib.conf.Configurations.configureInstance(Configurati
      ons.java:430)
      at
      org.apache.openjpa.lib.conf.PluginValue.instantiate(PluginValue.java:103
      )
      at
      org.apache.openjpa.lib.conf.ObjectValue.instantiate(ObjectValue.java:83)
      at
      org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getUpdateManagerInsta
      nce(JDBCConfigurationImpl.java:577)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at
      sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
      a:39)
      at
      sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
      Impl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at
      org.apache.openjpa.lib.conf.ConfigurationImpl.instantiateAll(Configurati
      onImpl.java:288)
      at
      org.apache.openjpa.conf.OpenJPAConfigurationImpl.instantiateAll(OpenJPAC
      onfigurationImpl.java:1409)
      at
      org.apache.openjpa.kernel.AbstractBrokerFactory.makeReadOnly(AbstractBro
      kerFactory.java:646)
      at
      org.apache.openjpa.kernel.AbstractBrokerFactory.pool(AbstractBrokerFacto
      ry.java:131)
      at
      kodo.jdbc.kernel.KodoJDBCBrokerFactory.getInstance(KodoJDBCBrokerFactory
      .java:43)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at
      sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
      a:39)
      at
      sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
      Impl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at
      org.apache.openjpa.kernel.Bootstrap.invokeFactory(Bootstrap.java:124)
      at
      org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:90)
      at
      com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSeri
      vceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)
      at
      com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(S
      toreServiceDelegate.java:145)
      at
      com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(St
      oreServiceDelegate.java:98)
      at
      com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServ
      iceImpl.java:76)
      at
      com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
      iceEngineImpl.java:363)
      at
      com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
      iceEngineImpl.java:315)
        • 1. Re: Errors starting Portal Admin Server after configuring RDBMS Security Store.
          672451
          "Caused by: java.sql.SQLException: Invalid Oracle URL specified:"
          If you are using
          "jdbc:oracle:thin" then the rest of your url is wrong(http://www.oracle.com/technology/tech/java/sqlj_jdbc/htdocs/jdbc_faq.html - What is the form of the url) . check the docs for samples. or use a sample domain , create a datasource from the console and check its settings
          Do you really want to use XA (thats what your driver states)?

          http://download.oracle.com/docs/cd/E13222_01/wls/docs90/jta/thirdpartytx.html#1084836
          . I read on some thread that RDBMS is only compatble with verion 10.3.2 but why is the feature in 10.3?
          Depends on what you are referring to. As far as I remember 10.3.2 lets you run on a RDBMS without any embedded LDAp requirements. Previous versions needed the embedded ldap (but could use RDBMS for most of their needs)
          • 2. Re: Errors starting Portal Admin Server after configuring RDBMS Security Store.
            712492
            Thanks deep - oversight on my part wrt the driver - all good now on that side.

            However, I've finished build the Portal domain and not sure I added all the necessary templates.

            What I did was build an ordinary weblogic domain and then extended it (using wlst) by adding three template jars (wlp.jar, content.jar and p13n.jar). Are these all the templates I need or am I missing any other template?

            Looked around at all the Portal docs but couldn't find this info.


            Many thanks
            • 3. Re: Errors starting Portal Admin Server after configuring RDBMS Security Store.
              Ravi Jegga
              You have another option. Create a Portal Domain using normal Config Wizard. Configure all the stuff like the portal datasources to point to any other database other then default out of box Pointbase db etc. Start this domain and make sure it starts fine. Then create a Template out of this working portal domain. Now use this template in your WLST script to create multiple domains. In this way all required portal stuff will be there in the template.

              http://download.oracle.com/docs/cd/E15523_01/web.1111/e14139/tempbuild.htm

              Thanks
              Ravi Jegga
              • 4. Re: Errors starting Portal Admin Server after configuring RDBMS Security Store.
                712492
                Thanks Ravi,
                already done that earlier. The problem I faced is that the template (along with the scripts) has to be used in various environments which means the database credentials will change. I guess DNS names can be used for the hosts but getting round the problem of setting the passwords is a real pain as they can't be set in clear text when in production mode (which is the mode being used everywhere but development). Which means we will have to manually encrypt the passwords before amending the datasources' -jdbc.xml files. Quite cumbersome and prone to errors - any idea how we could do this better?

                Also, I read a thread where you advised people not to specifically configure RDBMS SecurityStore as this is done by default. The problem here is the default RDBMS is created using pointbase and when I try to start the server, I get a NoClassDef error on some pointbase session class. So I went against your advise (sorry!) and specifically configured mine to point to the RAC DB we are using - seems to work so far too.

                Thanks for you all your help (I say 'all' because sooo many of your posts have been of great help!!)

                A
                • 5. Re: Errors starting Portal Admin Server after configuring RDBMS Security Store.
                  672451
                  If you arent using groupspace. then I think you are only missing workshop_wl_10_2.jar.
                  if you were creating the domain using the config wizard , how many checkboxes you checked should tell you how many jars you should add
                  • 6. Re: Errors starting Portal Admin Server after configuring RDBMS Security Store.
                    672451
                    WLST had some way of encrypting the password If i remember correctly (so you'd checkin the encrypted version which can then used)
                    • 7. Re: Errors starting Portal Admin Server after configuring RDBMS Security Store.
                      712492
                      Thanks, I've decided to go the template route. New to me as I have always done things through WLST so far - so will be good practice.

                      Yes, there is a WLST utility to encrypt - java weblogic.security.Encrypt or something like that. Will give it a go...

                      Off to pack and unpack...

                      Thanks for your help.

                      A
                      • 8. Re: Errors starting Portal Admin Server after configuring RDBMS Security Store.
                        672451
                        Just one thing , My workshop template posted probably has the incorrect version for you (10_2) , you would use whatever jar file name you have in your version...
                        • 9. Re: Errors starting Portal Admin Server after configuring RDBMS Security Store.
                          712492
                          Yes, thanks...
                          So I used the configuration wizard to build the domain, generated a template out of it, used pack to create a managed server template, copied the jar (generated by pack) to the second host which would host the second managed server and unpacked the jar. Started the AdminServer and first managed server fine (on the frist host) bbut having problems starting the second managed server.

                          It seems as though it's not picking up the configuration from the AdminServer (even though I have been able to connect to the AdminServer from the second host using wlst). The AdminServer and the 1st managed server start up in Production mode but the 2nd is starting up in Dev mode.

                          I'm getting the error below and a quick search suggests I should add a parameter which set the ALTERNATIVE_TYPES_DIR to the start up scripts. Checked the startup arguments and found the parameter in there already although it contain a tag which hadn't been expanded (WL_INSTALL_DIR). Sorted this out by adding it in the setDomainEnv.sh and restarted it. Unfortunately the bugger is having none of it and I'm still getting the same error. Seems I've missed a step in my templating. Any ideas?

                          Many thanks in advance
                          A


                          tuning)'> <<WLS Kernel>> <> <> <1273769846994> <BEA-000436> <Allocating
                          3 reader threads.>
                          ####<13-May-2010 17:57:26 o'clock BST> <Info> <Socket> <host2>
                          <m_server_2> <[ACTIVE] ExecuteThread: '0' for queue:
                          'weblogic.kernel.Default (self-
                          tuning)'> <<WLS Kernel>> <> <> <1273769846996> <BEA-000446> <Native IO
                          Enabled.>
                          ####<13-May-2010 17:57:27 o'clock BST> <Info> <IIOP> <host2>
                          <m_server_2> <[ACTIVE] ExecuteThread: '0' for queue:
                          'weblogic.kernel.Default (self-tu
                          ning)'> <<WLS Kernel>> <> <> <1273769847276> <BEA-002014> <IIOP
                          subsystem enabled.>
                          ####<13-May-2010 17:58:28 o'clock BST> <Info> <Security> <host2>
                          <m_server_2> <[ACTIVE] ExecuteThread: '0' for queue:
                          'weblogic.kernel.Default (sel
                          f-tuning)'> <<WLS Kernel>> <> <> <1273769908733> <BEA-000000> <Starting
                          BEA Kodo 4.2.0>
                          ####<13-May-2010 17:58:28 o'clock BST> <Info> <Security> <host2>
                          <m_server_2> <[ACTIVE] ExecuteThread: '0' for queue:
                          'weblogic.kernel.Default (sel
                          f-tuning)'> <<WLS Kernel>> <> <> <1273769908822> <BEA-000000> <Using
                          dictionary class "kodo.jdbc.sql.KodoOracleDictionary".>
                          ####<13-May-2010 17:58:52 o'clock BST> <Info> <Security> <host2>
                          <m_server_2> <[ACTIVE] ExecuteThread: '0' for queue:
                          'weblogic.kernel.Default (sel
                          f-tuning)'> <<WLS Kernel>> <> <> <1273769932520> <BEA-000000> <Started
                          listening for remote commit information on topic
                          "p13n.security.RDBMSSecurityStoreTopic
                          ".>
                          ####<13-May-2010 17:58:52 o'clock BST> <Info> <Security> <host2>
                          <m_server_2> <[ACTIVE] ExecuteThread: '0' for queue:
                          'weblogic.kernel.Default (sel
                          f-tuning)'> <<WLS Kernel>> <> <> <1273769932521> <BEA-000000> <Status of
                          JMS availability transited from "INIT" to "ACTIVE" >
                          ####<13-May-2010 17:58:52 o'clock BST> <Info> <Security> <host2>
                          <m_server_2> <[ACTIVE] ExecuteThread: '0' for queue:
                          'weblogic.kernel.Default (sel
                          f-tuning)'> <<WLS Kernel>> <> <> <1273769932559> <BEA-000000>
                          <StoreServiceImpl.initJDO - StoreService is initialized with Id =
                          rdbms_Fdeb2p4Uk6tZ1SSwlMj3oZkA
                          2O0=>
                          ####<13-May-2010 17:58:52 o'clock BST> <Info> <Security> <host2>
                          <m_server_2> <[ACTIVE] ExecuteThread: '0' for queue:
                          'weblogic.kernel.Default (sel
                          f-tuning)'> <<WLS Kernel>> <> <> <1273769932656> <BEA-090511> <The
                          following exception has occurred:

                          com.bea.common.engine.ServiceInitializationException:
                          com.bea.common.engine.SecurityServiceRuntimeException:
                          [Security:097533]SecurityProvider service class n
                          ame for WSRPIdentityAsserter is not specified.
                          at
                          com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
                          iceEngineImpl.java:365)
                          at
                          com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
                          iceEngineImpl.java:315)
                          at
                          com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEn
                          gineImpl.java:257)
                          at
                          com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java
                          :72)
                          at
                          weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLS
                          IdentityServiceImpl.java:47)
                          at
                          weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSS
                          WLSDelegateImpl.java:300)
                          at
                          weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateIm
                          pl.java:221)
                          at
                          weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.Initi
                          alizeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)
                          at
                          weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
                          alizeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
                          at
                          weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadR
                          ealm(CommonSecurityServiceManagerDelegateImpl.java:840)
                          at
                          weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
                          alizeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
                          at
                          weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
                          alize(CommonSecurityServiceManagerDelegateImpl.java:1028)
                          at
                          weblogic.security.service.SecurityServiceManager.initialize(SecurityServ
                          iceManager.java:875)
                          at
                          weblogic.security.SecurityService.start(SecurityService.java:141)
                          at
                          weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
                          at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
                          at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

                          Caused By: com.bea.common.engine.SecurityServiceRuntimeException:
                          [Security:097533]SecurityProvider service class name for
                          WSRPIdentityAsserter is not specifi
                          ed.
                          at
                          com.bea.common.security.internal.legacy.service.SecurityProviderImpl.ini
                          t(SecurityProviderImpl.java:47)
                          at
                          com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
                          iceEngineImpl.java:363)
                          at
                          com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
                          iceEngineImpl.java:315)
                          at
                          com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEn
                          gineImpl.java:257)
                          at
                          com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java
                          :72)
                          at
                          weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLS
                          IdentityServiceImpl.java:47)
                          at
                          weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSS
                          WLSDelegateImpl.java:300)
                          at
                          weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateIm
                          pl.java:221)
                          at
                          weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.Initi
                          alizeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)
                          at
                          weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
                          alizeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
                          at
                          weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadR
                          ealm(CommonSecurityServiceManagerDelegateImpl.java:840)
                          at
                          weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
                          alizeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
                          at
                          weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
                          alize(CommonSecurityServiceManagerDelegateImpl.java:1028)
                          at
                          weblogic.security.service.SecurityServiceManager.initialize(SecurityServ
                          iceManager.java:875)
                          at
                          weblogic.security.SecurityService.start(SecurityService.java:141)
                          at
                          weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
                          at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
                          at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
                          • 10. Re: Errors starting Portal Admin Server after configuring RDBMS Security Store.
                            Ravi Jegga
                            Hi
                            On the second machine, you run unpack command and that creates the second managed server. ALSO, you need to manually copy the following 3 files from the main master domain root folder (where you have admin server etc) to the managed servers domain root folder.
                            DemoIdentity.jks
                            DemoTrust.jks
                            wsrpKeystore.jks

                            One more small thing incase if you use default Pointbase database to store Portal db schema. Once the cluster domain is created. Go to the master domain root folder/config/jdbc. Open all the datasource *.xml files. Replace the word "localhost" with that machines IP address or DNS Names. Because when you start the second managed server, it will copy all the configuration files from main master domain to this managed servers domain. And it will try to connect to Pointbase db. Now if you have "localhost" in datasources .xml file, managed server will try to start the pointbase on that machine itself and you will get weird errors like NoClassDefFound errors on Pointbase classes etc. Note that the Pointbase should start only in the main master domain. But if you replace the "localhost" with the machines IP or DNS names, then the managed server will jsut try to connect to the Pointbase db using that IP or DNS name. Since the admin server is already started, it will be able to connect to the pointbase db. If you use any other db like Oracle or MySQL etc, you will be giving that dbs host name (assuming you DO NOT have db also on the same machine and use localhost etc).

                            Also, when you start managed server on remote machine, first try using startmanagedweblogic command. Once it starts fine, later on you can use NodeManager etc.

                            Thanks
                            Ravi Jegga
                            • 11. Re: Errors starting Portal Admin Server after configuring RDBMS Security Store.
                              712492
                              Thanks, Ravi - already did all that. I have managed to stand the whole cluster up but two niggly things - one more so!

                              First, when I start any of the managed servers for the forst time, I get the error below; it's as if the managed server can't download the ldap config from the AdminServer - subsequent restarts work fine though.

                              tuning)'> <<WLS Kernel>> <> <> <1273851208837> <BEA-000436> <Allocating 3 reader threads.>
                              ####<14-May-2010 16:33:28 o'clock BST> <Info> <Socket> <host_2> <server_2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-
                              tuning)'> <<WLS Kernel>> <> <> <1273851208839> <BEA-000446> <Native IO Enabled.>
                              ####<14-May-2010 16:33:29 o'clock BST> <Info> <IIOP> <host_2> <server_2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1273851209488> <BEA-002014> <IIOP subsystem enabled.>
                              ####<14-May-2010 16:34:28 o'clock BST> <Critical> <WebLogicServer> <host_2> <server_2> <Main Thread> <<WLS Kernel>> <> <> <1273851268370> <BEA-000
                              386> <Server subsystem failed. Reason: weblogic.ldap.EmbeddedLDAPException: Empty initial replica
                              weblogic.ldap.EmbeddedLDAPException: Empty initial replica
                              at weblogic.ldap.EmbeddedLDAP.getInitialReplicaFromAdminServer(EmbeddedLDAP.java:1301)
                              at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:221)
                              at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
                              at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
                              at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
                              >
                              ####<14-May-2010 16:34:28 o'clock BST> <Notice> <WebLogicServer> <host_2> <server_2> <Main Thread> <<WLS Kernel>> <> <> <1273851268601> <BEA-00036
                              5> <Server state changed to FAILED>


                              Secondly, both managed server are starting in ADMIN mode because some of the libraries aren't getting deployed. Think this is due to clashes in the Implementation-Version. I get the errors below (loads of the libraries - approx a third but I just pasted this for brevity) although after starting them with nodemanager and they go into ADMIN mode, I can always click on resume which then starts them up. Any idea why this is the case?

                              Many, many, thanks!
                              A

                              plementation-Version: 1.0.2.2 (WAR).>
                              ####<14-May-2010 16:59:21 o'clock BST> <Error> <Deployer> <host_2> <server_2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
                              lf-tuning)'> <<WLS Kernel>> <> <> <1273852761063> <BEA-149205> <Failed to initialize the application 'content-management-app-lib [LibSpecVersion=10.3.2,LibImp
                              lVersion=10.3.2]' due to error weblogic.application.library.LibraryDeploymentException: [J2EE:160145]Failed to deploy library Extension-Name: content-manageme
                              nt-app-lib, Specification-Version: 10.3.2, Implementation-Version: 10.3.2.1, because of conflicting library Manifest values, and library information registere
                              d with the server: [Implementation-Version: 10.3.2.1 vs. 10.3.2]. Check the library"s MANIFEST.MF file, and correct version info there to match server setting
                              s. Or undeploy the misconfigured library..
                              weblogic.application.library.LibraryDeploymentException: [J2EE:160145]Failed to deploy library Extension-Name: content-management-app-lib, Specification-Versi
                              on: 10.3.2, Implementation-Version: 10.3.2.1, because of conflicting library Manifest values, and library information registered with the server: [Implementat
                              ion-Version: 10.3.2.1 vs. 10.3.2]. Check the library"s MANIFEST.MF file, and correct version info there to match server settings. Or undeploy the misconfigure
                              d library.
                              at weblogic.application.internal.library.LibraryDeploymentFactory.getLibData(LibraryDeploymentFactory.java:106)
                              at weblogic.application.internal.library.LibraryDeploymentFactory.createDeployment(LibraryDeploymentFactory.java:46)
                              at weblogic.application.internal.DeploymentManagerImpl.createDeployment(DeploymentManagerImpl.java:84)
                              at weblogic.deploy.internal.targetserver.BasicDeployment.createDeployment(BasicDeployment.java:149)
                              at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:114)
                              at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
                              at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
                              at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
                              at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
                              at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
                              at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
                              at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
                              at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
                              at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
                              at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
                              at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
                              >
                              ####<14-May-2010 16:59:21 o'clock BST> <Info> <J2EE> <host_2> <server_2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tu
                              ning)'> <<WLS Kernel>> <> <> <1273852761069> <BEA-160151> <Registered library Extension-Name: content-management-app-lib, Specification-Version: 10.3.2, Imple
                              mentation-Version: 10.3.2.1 (EAR).>
                              ####<14-May-2010 16:59:21 o'clock BST> <Error> <Deployer> <host_2> <server_2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
                              lf-tuning)'> <<WLS Kernel>> <> <> <1273852761074> <BEA-149205> <Failed to initialize the application 'content-management-cmis-base-web-lib [LibSpecVersion=10.
                              3.2,LibImplVersion=10.3.2]' due to error weblogic.application.library.LibraryDeploymentException: [J2EE:160145]Failed to deploy library Extension-Name: conten
                              t-management-cmis-base-web-lib, Specification-Version: 10.3.2, Implementation-Version: 10.3.2.1, because of conflicting library Manifest values, and library i
                              nformation registered with the server: [Implementation-Version: 10.3.2.1 vs. 10.3.2]. Check the library"s MANIFEST.MF file, and correct version info there to
                              match server settings. Or undeploy the misconfigured library..
                              weblogic.application.library.LibraryDeploymentException: [J2EE:160145]Failed to deploy library Extension-Name: content-management-cmis-base-web-lib, Specifica
                              tion-Version: 10.3.2, Implementation-Version: 10.3.2.1, because of conflicting library Manifest values, and library information registered with the server: [I
                              mplementation-Version: 10.3.2.1 vs. 10.3.2]. Check the library"s MANIFEST.MF file, and correct version info there to match server settings. Or undeploy the mi
                              sconfigured library.
                              at weblogic.application.internal.library.LibraryDeploymentFactory.getLibData(LibraryDeploymentFactory.java:106)
                              at weblogic.application.internal.library.LibraryDeploymentFactory.createDeployment(LibraryDeploymentFactory.java:46)
                              at weblogic.application.internal.DeploymentManagerImpl.createDeployment(DeploymentManagerImpl.java:84)
                              at weblogic.deploy.internal.targetserver.BasicDeployment.createDeployment(BasicDeployment.java:149)
                              at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:114)
                              at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
                              at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
                              at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
                              at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
                              at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
                              at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
                              at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
                              at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
                              at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
                              • 12. Re: Errors starting Portal Admin Server after configuring RDBMS Security Store.
                                Ravi Jegga
                                Hi
                                1. For the first error, first stop all the managed servers. From managed servers domain folder on remote machine/servers/yourmanagedserver/data/ delete the folde named ldap or just rename it like ldapold. Delete all tmp, cache, logs folders also from you managedserver folder. Then restart the managed server. When you start the managed server, it does get copy of ldap folder from main master domain.

                                2. The second error is by anychance do you have like different version of portal application deploying on a domain of different version. Also when you create the Clustered Domain it is must that all the machines have exactly same version of WLP/WLS installed. We cannot have remote managed servers running on a different versions of weblogic. One more thing. By default, Clustered Portal domain, will have all the shared modules deployed only to the Cluster and NOT to the managed servers. Check your config.xml file for any shared modules deployed. Check the target attribute and it will show the cluster. This means your have to deploy and target your PortalApplication ONLY to the Cluster and NOT to the admin server. Incase if you do need to deploy your portalApp on admin server also, you need to deploy all the shared modules on admin server also. Do global replacement of target attribute to include adminserver name also (take back up of config.xml file too).

                                Entry in my WLP 10.3.2 Domain config.xml file single domain server:
                                <library>
                                <name>content-management-web-lib#10.3.2@10.3.2</name>
                                <target>AdminServer</target>
                                <source-path>C:\beawlp1032/modules/com.bea.content.vcr_10.3.2.0/content-management-web-lib.war</source-path>
                                <deployment-order>1</deployment-order>
                                <security-dd-model>DDOnly</security-dd-model>
                                </library>
                                Entry in my weblogic.xml file in my portalWeb project:
                                </wls:library-ref><wls:library-ref>
                                <wls:library-name>content-management-web-lib</wls:library-name>
                                <wls:specification-version>10.3.2</wls:specification-version>
                                <wls:implementation-version>10.3.2</wls:implementation-version>
                                <wls:exact-match>false</wls:exact-match>
                                </wls:library-ref>

                                Thanks
                                Ravi Jegga
                                • 13. Re: Errors starting Portal Admin Server after configuring RDBMS Security Store.
                                  712492
                                  Thanks, with regards to the second error, I have only one instance of Portal installed. Please note that prior to using pack to create a template, I had started the AdminServer and one managed server with no issues at all. It was after I had created a template, then used WLST to configure and create a new domain that I got this error. Read somewhere that pack does that but need a work around for it as the server is starting up in admin mode.

                                  Ta muchly
                                  • 14. Re: Errors starting Portal Admin Server after configuring RDBMS Security Store.
                                    user9503787
                                    Adisco wrote:

                                    I'm getting the error below and a quick search suggests I should add a parameter which set the ALTERNATIVE_TYPES_DIR to the start up scripts. Checked the startup arguments and found the parameter in there already although it contain a tag which hadn't been expanded (WL_INSTALL_DIR). Sorted this out by adding it in the setDomainEnv.sh and restarted it. Unfortunately the bugger is having none of it and I'm still getting the same error. Seems I've missed a step in my templating. Any ideas?
                                    I saw @WL_INSTALL_DIR is not expanded either in my setDomainEnv and some of my own classpath setting are missing also. I doubt there is something missing in write a portal template. How did you solve it? I don't really want to just modify the file manually after the domain creation.