Clarity

I am trying to open a filter portlet (properties etc) in  Administration, but all I get is a blnk screen which keeps refreshing and refreshing and refreshing...

The same thing with any of the filter portlets in the system.

The same problem on two systems.

I should like to modify one and create some more.

The filter seems to work OK.

What might the problem be?

The error in the logs is

ERROR 2016-12-14 09:45:30,854 [catalina-exec-10] vxml.VXMLService (clarity:martti.kinnunen@v.com:7677382__F9E0FE06-FC6D-49EE-A7B4-099B5AA1889B:npt.filterPropertiesE

ntry) Exception in processing

com.niku.union.web.WebException: Portlet view processing failed for portlet: npt.filterProperties

        at com.niku.union.web.XMLPageProcessor.processPage(XMLPageProcessor.java:242)

        at com.niku.union.web.XMLPageProcessor.processPage(XMLPageProcessor.java:83)

        at com.ca.clarity.uif.service.vxml.Evolution3PageProcessor.retrievePage(Evolution3PageProcessor.java:146)

        at com.niku.union.web.UIPageProcessor.buildPage(UIPageProcessor.java:89)

        at com.ca.clarity.uif.service.vxml.VXMLResponseHandler.processResponse(VXMLResponseHandler.java:168)

        at com.ca.clarity.uif.service.vxml.VXMLService.processRequest(VXMLService.java:591)

        at com.ca.clarity.uif.UIServlet.service(UIServlet.java:69)

        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)

        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)

        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

        at com.niku.union.web.filter.GZIPResponseFilter.doFilter(GZIPResponseFilter.java:142)

        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)

        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

        at org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108)

        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)

        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)

        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)

        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)

        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)

        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

        at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)

        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)

        at org.apache.catalina.valves.StuckThreadDetectionValve.invoke(StuckThreadDetectionValve.java:193)

        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)

        at org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:190)

        at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)

        at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:2442)

        at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:2431)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)

        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

        at java.lang.Thread.run(Thread.java:722)

Caused by: com.niku.union.web.WebException: Failed to process portlet npt.filterProperties

        at com.niku.union.web.XMLPageProcessor.processPortletJSPX(XMLPageProcessor.java:818)

       at com.niku.union.web.XMLPageProcessor.processPage(XMLPageProcessor.java:198)

        ... 32 more

Caused by: org.apache.jasper.JasperException: Unable to compile class for JSP

        at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:672)

        at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:357)

Have you tried turning it off and back on again?

(i.e. stop/start the APP)

I've edited filter-portlet definitions OK in the past, but I do seem to remember having to do it via XOG occasionally - XOG out the definition, edit the XML and XOG it back in again. Can't remember exactly why I felt that I needed to do that though.

Yes it's been turned off and on as this has persisted for months.

Now I would really need to create new.

Just looked at filter portlets at  the community sandbox. No problem there.

Can you check if it is because of this ?

Apache Tomcat defect with version 7.0.50 will cause issues with Clarity 

https://communities.ca.com/message/111125220 

NJ

Thanks, it is 7.0.54 so it should not be the Tomcat version.

Will try to create the new one in xml and then XOG in.

XOGed out an existing filter page.

Modified it to to have a field which I wanted in the page filter.

Displays OK in the list of portlets (still cannot open them)

Put that on a page.

Opened the page.

No sign of the filter. :-(

Hi urmas

mmmm...

Try the following:

1 - Run as sysdba:
alter login niku with DEFAULT_LANGUAGE = us_english
2 - Restart CA PPM services

If not working: What are your DB parameters?

SELECT * FROM NLS_DATABASE_PARAMETERS WHERE parameter in ('NLS_CHARACTERSET', 'NLS_NCHAR_CHARACTERSET','NLS_DATE_FORMAT', 'NLS_SORT', 'NLS_COMP')

Thanks Aurora_Gaimon 

The admin did something which worked. I do not know yet what that was.

Now I can edit/create filter portlets on that system.

Comparing my page with ones that have a page filter working there is a differences.

I'll try to make mine similar to see if it works then.

Edit

My page was not a page with tabs which seems to be needed to use page filters.

Now it works fine.

Apparently refreshing the tomcat files did the trick.