weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable

I got the following error while restarting our managed Weblogic 10.3.5 server:

<Mar 22, 2013 2:07:40 PM CET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
Exception in thread "VDE Transaction Processor Thread" java.lang.OutOfMemoryError: Java heap space
        at com.octetstring.vde.Entry.readBytes(Entry.java:507)
        at com.octetstring.vde.Entry.<init>(Entry.java:99)
        at com.octetstring.vde.backend.standard.TransactionProcessor.run(TransactionProcessor.java:234)
<Mar 22, 2013 2:07:42 PM CET> <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:916)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
        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:209)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

Turned out that one of our custom SecurityProviders was removed from the classpath (wlserver_10.3/server/lib/mbeantypes), resulting in this error. Re-adding the SecurityProvider to the classpath solved everything.

//Edit 2014/05/07: the same thing happened again today. This time I solved it by calling

wlctrl setClassPath
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s