• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
  • Mikalai Zaikin

WebLogic securing Coherence fails

Posts: 21
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have an application that uses Coherence, and I now need to secure it. I found http://docs.oracle.com/middleware/1212/coherence/COHSG/wls_security.htm and followed the steps in section 6.2.1:

1) From the Summary of Coherence Clusters page, click a Coherence Cluster to configure its settings.
2) From the cluster's settings page, click the Security tab.
3) From the General tab, click the Security Framework Enabled option to enable the security framework.
4) Click Save.

When i next restart WebLogic, it fails horribly though, with the following error:

####<24-jun-2014 13:45:59 uur CEST> <Critical> <WebLogicServer> <PC0075> <AdminServer> <main> <<WLS Kernel>> <> <> <1403610359625> <BEA-000362> <Server failed. Reason:

There are 1 nested errors:

weblogic.cacheprovider.coherence.CoherenceException: kss://system/demoidentity does not exist.
at weblogic.cacheprovider.coherence.SecurityHelper.getFile(SecurityHelper.java:299)
at weblogic.cacheprovider.coherence.SecurityHelper.getIdentityKeyStoreBean(SecurityHelper.java:267)
at weblogic.cacheprovider.coherence.CoherenceClusterManager.collectKeystoreInfo(CoherenceClusterManager.java:834)
at weblogic.cacheprovider.coherence.CoherenceClusterManager.configureClusterService(CoherenceClusterManager.java:214)
at weblogic.cacheprovider.CacheProviderServerService.initCoherence(CacheProviderServerService.java:76)
at weblogic.cacheprovider.CacheProviderServerService.initialize(CacheProviderServerService.java:45)
at weblogic.cacheprovider.CacheProviderServerService.start(CacheProviderServerService.java:39)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:254)

####<24-jun-2014 13:45:59 uur CEST> <Notice> <WebLogicServer> <PC0075> <AdminServer> <main> <<WLS Kernel>> <> <> <1403610359634> <BEA-000365> <Server state changed to FAILED.>
####<24-jun-2014 13:45:59 uur CEST> <Error> <WebLogicServer> <PC0075> <AdminServer> <main> <<WLS Kernel>> <> <> <1403610359634> <BEA-000383> <A critical service failed. The server will shut itself down.>
####<24-jun-2014 13:45:59 uur CEST> <Notice> <WebLogicServer> <PC0075> <AdminServer> <main> <<WLS Kernel>> <> <> <1403610359635> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>

Apart from this, all seems to be going right. The kss keystore itself works just fine:

####<24-jun-2014 13:44:02 uur CEST> <Notice> <Security> <PC0075> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <25122c7e-54fd-48dc-874c-8a97fb7ca1b8-0000000b> <1403610242915> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the kss keystore file kss://system/demoidentity.>;

Is it me or WebLogic that's doing something wrong? (From having worked with WebLogic for just a month or 2, the latter doesn't surprise me at all...)
Don't get me started about those stupid light bulbs.
    Bookmark Topic Watch Topic
  • New Topic