My Oracle Support Banner

A Custom Portal Application Fails with Blank Page or Internal Server Error if Another Managed Server is Started in the Managed Server Domain Directory In An Enterprise Deployment (Doc ID 2438419.1)

Last updated on FEBRUARY 03, 2019

Applies to:

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

Symptoms

When attempting to creating separate directories for the AdminServer and the Managed Servers (aserver and mserver),
this causes a custom portal application to fail with either a blank page or Internal Server Error if another managed server is started in the mserver domain directory.


ERROR

Blank Page or Error 500--Internal Server Error

The WC_CustomPortal-diagnostic.log shows:

[2018-05-23T23:23:40.081+00:00] [WC_CustomPortal] [NOTIFICATION][J2EE JSP-00008] [oracle.j2ee.jsp][tid: [ACTIVE].ExecuteThread: '0' for queue:
'weblogic.kernel.Default (self-tuning)'] [userId: anonymous][ecid: 0000MEFKB28Fw000jzwkno1R1VLO000017,0] [APP: SiteBPIMobile]
[DSID: 0000MEFKB1FFw000jzwkno1R1VLO000016]
unable to dispatch JSP page: The following exception occurred:.[[
java.io.FileNotFoundException: MDS-00013: no metadata found for metadata object "/generic-page.jspx"
MDS-00201: PDocument not found in MetadataStore : [store-type=DefaultMetadataStore app-name=SiteBPIMobile lookup-order=ServletContext,Classpath]

 


STEPS

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

  1. Create a domain with a WC_CustomPortal and WC_CustomServicesProducer Managed servers.


  2. Create a separate directory for the Managed Servers per the following documentation:

    Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter Portal
    8 Creating a Domain for an Enterprise Deployment
    8.4 Post-Configuration and Verification Tasks
    8.4.6 Creating a Separate Domain Directory for Managed Servers in the Same Node as the Administration Server

  3. Start the AdminServer (in the admin server directory).


  4. Start the WC_CustomPortal managed server (in the managed server directory).


  5. Deploy a custom Portal application to the WC_CustomPortal managed server.


  6. Access the application and confirm is works fine.


  7. Start the WC_CustomServicesProducer managed server (in the managed server directory).


  8. Access the custom Portal application.

    Here you will get a blank page or Error 500--Internal Server Error





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.