WebCenter Portal Page with Querystring cid=<value> Fails With WELD-000321: No Conversation Found (Doc ID 2651392.1)

Last updated on MARCH 27, 2024

Applies to:

Symptoms

WebCenter Portal (WCP) 12.2.1.3.190416.

Adding the page variable "cid" to any WCP portal page results in an "Internal Error".  The following error stack is seen in the logs:

[2020-03-18T21:15:36.953+05:30] [WC_Portal] [ERROR] [] [oracle.webcenter.webcenterapp.internal.view.webapp] [tid: [ACTIVE].ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: <ECID>] [APP: webcenter] [partition-name: DOMAIN] [tenant-name: GLOBAL] [DSID: <DSID>] [[
org.jboss.weld.context.NonexistentConversationException: WELD-000321: No conversation found to restore for id 1
at org.jboss.weld.context.AbstractConversationContext.initialize(AbstractConversationContext.java:238)
at org.jboss.weld.context.http.LazyHttpConversationContextImpl.initialize(LazyHttpConversationContextImpl.java:90)
at org.jboss.weld.context.http.LazyHttpConversationContextImpl.checkContextInitialized(LazyHttpConversationContextImpl.java:124)
at org.jboss.weld.context.AbstractConversationContext.getCurrentConversation(AbstractConversationContext.java:481)
at org.jboss.weld.jsf.ConversationAwareViewHandler.getActionURL(ConversationAwareViewHand
...

Changes

Create a sample portal and access the page with /webcenter/portal/testportal?cid=1.  It fails with the error described above.  The value "1" is just an example.  Any value will reproduce the behavior.  Any parameter name other than "cid" will work with no issues.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.