Load | Techartifact

Hi,

If you have got this weird issue in starting webcenter server

Failed to initialize the application ‘webcenter [Version=11.1.1.4.0]’ due to error weblogic.application.ModuleException: Failed to load webapp: ‘/wcsdocs’.
weblogic.application.ModuleException: Failed to load webapp: ‘/wcsdocs’
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:395)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)
… …

Caused By: weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for “[email protected][app:webcenter module:/wcsdocs path:/wcsdocs spec-version:2.5 version:11.1.1.4.0]”, defined in weblogic.xml [Extension-Name: SomeLibraryName, exact-match: false]
at weblogic.servlet.internal.WebAppServletContext.processWebAppLibraries(WebAppServletContext.java:2750)
at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:416)

Solution – You need to delete the reference of this library in weblogic.xml and delete this library.First you can check in
/archives/applications and see if there is reference in weblogic.xml .

You can find weblogic.xml using following command.

find / -iname weblogic.xml

If you cant find then check in
/user_projects/domains/DomainName/servers/WC_Spaces/tmp/_WL_user/webcenter_11.1.1.4.0/extend.spaces.webapp

Check weblogic.xml and delete the reference.

Thats it. Happy coding with vinay in techartifact.

Requirment- Resolving ADF_FACES-30107: The view state of the page has expired. Load the page again.
ugly error actually.- you don’t know what went wrong- and you will see a very long error message like
ADF_FACES-30107: The view state of the page has expired. Load the page again………………………………………………………………………..

What’s the problemFirst understand , why we get this error – The ViewExpiredException will be thrown whenever the javax.faces.STATE_SAVING_METHOD is set to server (default) and the enduser sends a HTTP POST request using or or some valueChangeEvent on a view, while the associated view state isn’t available in the session anymore. The view state is identified by a hidden input field javax.faces.ViewState of the

In the oracle documentation this error states-

ADF_FACES-30107: The view state of the page has expired. Reload the page.
Cause: The UI state of the view has expired, either because the back button has been used too many times, too many page submissions have occurred on ther pages, or because of an underlying bug in the view code.
Action: The application using ADF should install an ADFc error handler for JSF ViewExpiredExceptions, or configure the org.apache.myfaces.trinidad.CLIENT_STATE_MAX_TOKENS web.xml parameter to a larger value.
Level: 2

Type: ERROR

Impact: Logging

How to resolve this – Find for the org.apache.myfaces.trinidad.CLIENT_STATE_MAX_TOKENS in web.xml as context parameter . If it not set as it happened to my application. Set this parameter and put value.Sometimes,it will not work for value for 15 to 20. I set it as 500.This mean , it can handle this much page submission for the pages.