My Oracle Support Banner

The Webpage Cannot Be Found Errors When Adding Another Hierarchy Filters for More Than One Dimension Or Selecting a Dimension Member in a Second Dimension (Doc ID 2435701.1)

Last updated on AUGUST 15, 2018

Applies to:

Oracle Financial Services Profitability Management - Version 8.0.5 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Profitability Management (PFT)

Symptoms

On PFT 8.0.5, in Source, if a hierarchy filter is selected, another hierarchy filter cannot be added for another element / dimension because the pop-up that is opened states "The webpage cannot be found".

ERROR
"The webpage cannot be found"



The nohup.out from Apache shows the following error:

[09-07-18 15:47:33 PM] ~ WARN ~ org.apache.struts2.util.TextProviderHelper ~ The first TextProvider in the ValueStack (com.ofs.fsapps.pft.action.clsActAllocationID) could not locate the message resource with key 'tableDescription'
[09-07-18 15:47:33 PM] ~ WARN ~ org.apache.struts2.util.TextProviderHelper ~ The default value expression 'tableDescription' was evaluated and did not match a property. The literal value 'tableDescription' will be used.
[09-07-18 15:47:33 PM] ~ WARN ~ org.apache.struts2.util.TextProviderHelper ~ The first TextProvider in the ValueStack (com.ofs.fsapps.pft.action.clsActAllocationID) could not locate the message resource with key 'dLookupTableDesc'
[09-07-18 15:47:33 PM] ~ WARN ~ org.apache.struts2.util.TextProviderHelper ~ The default value expression 'dLookupTableDesc' evaluated to ''
enHolcalAdjustments **********8false
09-Jul-2018 15:47:49.517 INFO [http-nio-8080-exec-4] org.apache.coyote.http11.AbstractHttp11Processor.process Error parsing HTTP request header
 Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
 java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986
  at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:285)
  at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1045)
  at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
  at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1539)
  at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1495)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
  at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
  at java.lang.Thread.run(Thread.java:748)

The issue can be reproduced at will with the following steps:
1. Create any allocation and select hierarchy filter node for one dimension.
2. Click the ...next to any other dimension
3. Find error window pop-up instead of dimension selector.

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
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.