Win a copy of Securing DevOps this week in the Security forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

WebLogic - Managed server(for OID domain) is not starting UP :(  RSS feed

 
Greenhorn
Posts: 22
Java Windows
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Team,

I am facing issue in starting my weblogic managed server (wls_ods1) & below is the exception :

SCENARIO -1:
Starting managed server using startup command only till "managed server name"

[applidm@erpuat01 bin]$ pwd
/u02/idam/Oracle/Middleware/user_projects/domains/OIDDomain/bin >  ./startManagedWebLogic.sh wls_ods1

//==================================================================================//
<Jun 2, 2017 2:36:03 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Jun 2, 2017 2:36:03 PM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Jun 2, 2017 2:36:03 PM IST> <Notice> <LoggingService> <BEA-320400> <The log file /u02/idam/Oracle/Middleware/user_projects/domains/OIDDomain/servers/wls_ods1/logs/wls_ods1.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Jun 2, 2017 2:36:03 PM IST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /u02/idam/Oracle/Middleware/user_projects/domains/OIDDomain/servers/wls_ods1/logs/wls_ods1.log00001. Log messages will continue to be logged in /u02/idam/Oracle/Middleware/user_projects/domains/OIDDomain/servers/wls_ods1/logs/wls_ods1.log.>
<Jun 2, 2017 2:36:04 PM IST> <Notice> <Log Management> <BEA-170019> <The server log file /u02/idam/Oracle/Middleware/user_projects/domains/OIDDomain/servers/wls_ods1/logs/wls_ods1.log is opened. All server side log events will be written to this file.>
Jun 02, 2017 2:36:19 PM oracle.security.jps.az.internal.runtime.pd.register.PDPRegister run
INFO: PDP registration succeeded.
Jun 02, 2017 2:36:20 PM oracle.security.jps.internal.idstore.util.LibOvdUtil pushLdapNamesToLibOvd
INFO: Pushed ldap name and types info to libOvd. Ldaps : DefaultAuthenticator:idstore.ldap.provideridstore.ldap.
<Jun 2, 2017 2:36:21 PM IST> <Warning> <Security> <BEA-090076> <A failure occurred attempting to load LDIF for provider Authorizer from file /u02/idam/Oracle/Middleware/wlserver_10.3/server/lib/XACMLAuthorizerInit.ldift.>
<Jun 2, 2017 2:36:21 PM IST> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: A failure occurred attempting to load LDIF for provider Authorizer from file /u02/idam/Oracle/Middleware/wlserver_10.3/server/lib/XACMLAuthorizerInit.ldift..
weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: A failure occurred attempting to load LDIF for provider Authorizer from file /u02/idam/Oracle/Middleware/wlserver_10.3/server/lib/XACMLAuthorizerInit.ldift.
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:466)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:841)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:870)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1032)
        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
        Truncated. see log file for complete stacktrace
Caused By: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: A failure occurred attempting to load LDIF for provider Authorizer from file /u02/idam/Oracle/Middleware/wlserver_10.3/server/lib/XACMLAuthorizerInit.ldift.
        at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
        at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
        at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
        at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
        at weblogic.security.service.CSSWLSDelegateImpl.getService(CSSWLSDelegateImpl.java:155)
        Truncated. see log file for complete stacktrace
Caused By: weblogic.security.spi.ProviderInitializationException: A failure occurred attempting to load LDIF for provider Authorizer from file /u02/idam/Oracle/Middleware/wlserver_10.3/server/lib/XACMLAuthorizerInit.ldift.
        at com.bea.common.store.bootstrap.internal.BootStrapServiceImpl.loadFullLDIFTemplate(BootStrapServiceImpl.java:910)
        at com.bea.common.store.bootstrap.internal.BootStrapServiceImpl.loadLDIFTemplate(BootStrapServiceImpl.java:688)
        at com.bea.common.store.bootstrap.internal.BootStrapServiceImpl.loadLDIFXACMLAuthorizerTemplate(BootStrapServiceImpl.java:176)
        at com.bea.common.store.bootstrap.internal.BootStrapServiceImpl.loadLDIFXACMLAuthorizerTemplate(BootStrapServiceImpl.java:160)
        at com.bea.common.security.internal.service.BootStrapServiceImpl.loadLDIFXACMLAuthorizerTemplate(BootStrapServiceImpl.java:106)
        Truncated. see log file for complete stacktrace
Caused By: <openjpa-1.1.1-SNAPSHOT-r422266:1172209 fatal store error> kodo.jdo.FatalDataStoreException: The transaction has been rolled back.  See the nested exceptions for details on the errors that occurred.
        at org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2170)
        at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2017)
        at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1915)
        at org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:1833)
        at org.apache.openjpa.kernel.LocalManagedRuntime.commit(LocalManagedRuntime.java:81)
        Truncated. see log file for complete stacktrace
Caused By: <openjpa-1.1.1-SNAPSHOT-r422266:1172209 fatal store error> kodo.jdo.FatalDataStoreException: error result
        at com.bea.common.ldap.LDAPStoreManager.flush(LDAPStoreManager.java:406)
        at org.apache.openjpa.abstractstore.AbstractStoreManager.flush(AbstractStoreManager.java:277)
        at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
        at org.apache.openjpa.datacache.DataCacheStoreManager.flush(DataCacheStoreManager.java:571)
        at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
        Truncated. see log file for complete stacktrace
Caused By: netscape.ldap.LDAPException: error result (49); Invalid credentials
        at weblogic.ldap.EmbeddedLDAPConnection.bind(EmbeddedLDAPConnection.java:639)
        at weblogic.ldap.EmbeddedLDAPConnection.determineFailover(EmbeddedLDAPConnection.java:2204)
        at weblogic.ldap.EmbeddedLDAPConnection.connect(EmbeddedLDAPConnection.java:366)
        at com.bea.common.ldap.LDAPConfiguration.getConnection(LDAPConfiguration.java:78)
        at com.bea.common.ldap.LDAPStoreManager.flush(LDAPStoreManager.java:312)
        Truncated. see log file for complete stacktrace
>
<Jun 2, 2017 2:36:21 PM IST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jun 2, 2017 2:36:21 PM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:

There are 1 nested errors:

weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:917)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
        at weblogic.security.SecurityService.start(SecurityService.java:141)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

>
<Jun 2, 2017 2:36:21 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jun 2, 2017 2:36:21 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 2, 2017 2:36:21 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

//==============================================================================================

SCENARIO -2:
Starting managed using server startup command only till "managed server name + Admin server host,port"

[applidm@erpuat01 bin]$ pwd
/u02/idam/Oracle/Middleware/user_projects/domains/OIDDomain/bin >  ./startManagedWebLogic.sh wls_ods1 http://10.148.XX.XX:7013


//===================================//
<Jun 2, 2017 12:11:20 PM IST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: java.lang.reflect.InvocationTargetException
java.lang.AssertionError: java.lang.reflect.InvocationTargetException
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:175)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
at weblogic.management.configuration.ServerMBeanImpl.getDefaultIIOPPassword(ServerMBeanImpl.java:1362)
Truncated. see log file for complete stacktrace
Caused By: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
Truncated. see log file for complete stacktrace
Caused By: weblogic.security.internal.encryption.EncryptionServiceException
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:139)
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:187)
at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
Truncated. see log file for complete stacktrace
>
<Jun 2, 2017 12:11:20 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jun 2, 2017 12:11:20 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 2, 2017 12:11:20 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

//==================================================//

Please help.
 
Durga Kannan
Greenhorn
Posts: 22
Java Windows
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Team,

As an update, i am having single /Oracle/Middleware/ under which i am having components like OAM,OID,OHS & OHS WebGate

I have 2 domains one for OAM & another for OID

/u02/idam/Oracle/Middleware/user_projects/domains/OIDDomain  --> This access wls admin with port 7013(SSL - 7014)
/u02/idam/Oracle/Middleware/user_projects/domains/OAMDomain--> This access wls admin with port 7011(SSL - 7012)

My OAM domain admin & managed servers started successfully.
OAM Admin -> 7011 -> Success
OAM Managed -> oam_server1 -> Success

OID Admin -> 7013  -> success
OID Managed -> wls_ods1 -> FAILURE

OID instance(./opmnctl startall) --> success

OHS instance(./opmnctl startall) --> success


P.S:
While bouncing my servers yesterday, i mistakenly gave 7011 port (during wls_ods1 start) instead of giving 7013(admin port).
It seems my config.xml(of OID Domain) file got corrupted, so i restored the back up file & started the admin server & it's UP & RUNNING.

But while starting wls_ods1, i am facing issue continously. Please suggest any clue. Many thanks in advabce
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!