My Oracle Support Banner

Java.Lang.Nullpointerexception Starting WebCenter Spaces Managed Server (Doc ID 1182945.1)

Last updated on OCTOBER 04, 2018

Applies to:

Oracle WebCenter Portal - Version 11.1.1.2.0 to 11.1.1.9.0 [Release 11g]
Information in this document applies to any platform.
Checked for currency on 26-MAR-2015

Symptoms


When attempting to start the WLS_Spaces managed server, the following error occurs:

####<Aug 20, 2010 4:55:58 AM PDT> <Info> <Diagnostics> <servername> <WLS_Spaces> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1282305358383> <BEA-320000> <The Diagnostics subsystem is initializing on Server WLS_Spaces.>
####<Aug 20, 2010 4:55:58 AM PDT> <Info> <Store> <servername> <WLS_Spaces> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1282305358411> <BEA-280008> <Opening the persistent file store "WLS_DIAGNOSTICS" for recovery: directory=/u01/app/oracle/product/Middleware/user_projects/domains/wc_domain/servers/WLS_Spaces/data/store/diagnostics requestedWritePolicy="Disabled" fileLockingEnabled=true driver="wlfileio3".>
####<Aug 20, 2010 4:55:58 AM PDT> <Critical> <WebLogicServer> <servername> <WLS_Spaces> <main> <> <> <> <1282305358417> <BEA-000386> <Server subsystem failed. Reason: java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.store.io.file.StoreFile.close(StoreFile.java:432)
at weblogic.store.io.file.Heap.open(Heap.java:307)
at weblogic.store.io.file.FileStoreIO.open(FileStoreIO.java:104)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:413)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:404)
at weblogic.store.xa.PersistentStoreManagerXA.createFileStore(PersistentStoreManagerXA.java:118)
at weblogic.diagnostics.archive.DiagnosticStoreRepository.getStore(DiagnosticStoreRepository.java:91)
at weblogic.diagnostics.lifecycle.DiagnosticSystemService.start(DiagnosticSystemService.java:128)
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)
>
####<Aug 20, 2010 4:55:58 AM PDT> <Notice> <WebLogicServer> <servername> <WLS_Spaces> <main> <> <> <> <1282305358423> <BEA-000365> <Server state changed to FAILED>
####<Aug 20, 2010 4:55:58 AM PDT> <Error> <WebLogicServer> <servername> <WLS_Spaces> <main> <> <> <> <1282305358424> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Aug 20, 2010 4:55:58 AM PDT> <Info> <WorkManager> <servername> <WLS_Spaces> <main> <> <> <> <1282305358424> <BEA-002936> <maximum thread constraint WatchManagerEvents is reached>
####<Aug 20, 2010 4:55:58 AM PDT> <Notice> <WebLogicServer> <servername> <WLS_Spaces> <main> <> <> <> <1282305358429> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>



Note:

This issue can happen with any of the WebCenter Managed Servers.
In this note we show the issue with the WLS_Spaces managed server. But you can use the same steps to start other managed servers having the same issue. Just replace the name of the managed server in the following steps depending on the affected managed server. For example, if using WebCenter 11.1.1.4.0 the WebCenter Spaces Managed Server is WC_Spaces.  If using WCP 12.2.x, the portal managed server is named WC_Portal.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.