My Oracle Support Banner

OWSM Policies Attached to the WebCenter Portal Discussion Server are Lost after Restarting the WC_Collaboration Managed Server (Doc ID 2217182.1)

Last updated on APRIL 01, 2021

Applies to:

Oracle WebCenter Portal - Version 12.2.1.1.0 and later
Information in this document applies to any platform.

Symptoms


ACTUAL BEHAVIOR

OWSM Policies attached to the Discussion Server are lost after restarting the managed server.


EXPECTED BEHAVIOR

Expect the policies to stay attached.


STEPS

The issue can be reproduced at will with the following steps:

 

  1. Attach the OWSM policy on the discussions web service endpoint:

    attachWebServicePolicy(application='owc_discussions', moduleName='owc_discussions', moduleType='web', serviceName='OWCDiscussionsServiceAuthenticated',subjectName='OWCDiscussionsServiceAuthenticated', policyURI='oracle/wss11_saml_token_with_message_protection_service_policy')
     

  2. Confirm the policy was attached:

    listWebServicePolicies('/webcenter/WC_Collaboration/owc_discussions', 'owc_discussions', 'web', 'OWCDiscussionsServiceAuthenticated', 'OWCDiscussionsServiceAuthenticated')

    Here you will see: The policy subject is secure in this context.
     

  3. Restart the WC_Collaboration managed server.


  4. Check if the policy is attached:

    listWebServicePolicies('/webcenter/WC_Collaboration/owc_discussions', 'owc_discussions', 'web', 'OWCDiscussionsServiceAuthenticated', 'OWCDiscussionsServiceAuthenticated')
     
    Here you will see the policy is not retained.
    You will see this message: The policy subject is not secure in this context.

 


   
The WC_Collaboration-diagnostic.log was showing the following errors:

[2016-09-27T08:07:49.437-04:00] [WC_Collaboration] [TRACE] [] [oracle.wsm.config.ConfigurationManager] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [ecid: <ECID>] [partition-name: DOMAIN] [tenant-name: GLOBAL] [SRC_CLASS: oracle.wsm.config.ConfigurationManager] [SRC_METHOD: initializeAccessors] oracle.wsm.policymanager.PolicyManagerException: WSM-02054 : Failure in looking up EJB component. The EJB JNDI name is "UsageTracker#oracle.wsm.policymanager.bean.ejb.IRemoteUsageTracker", the provider URL is "t3://server:8890,server:8889,server:8888".[[
oracle.wsm.policymanager.PolicyManagerException: WSM-02054 : Failure in looking up EJB component. The EJB JNDI name is "UsageTracker#oracle.wsm.policymanager.bean.ejb.IRemoteUsageTracker", the provider URL is "t3://server:8890,server:8889,server:8888".
at oracle.wsm.policymanager.BeanFactory.getJndiObj(BeanFactory.java:978)
at oracle.wsm.policymanager.BeanFactory.lookupJndiObj(BeanFactory.java:1231)
...

Caused by: javax.naming.NameNotFoundException: While trying to lookup 'UsageTracker#oracle.wsm.policymanager.bean.ejb.IRemoteUsageTracker' didn't find subcontext 'UsageTracker#oracle'. Resolved ''; remaining name 'UsageTracker#oracle/wsm/policymanager/bean/ejb/IRemoteUsageTracker'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1292)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:349)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:221)

 

 

 

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.