pepdwill Honored Contributor.
Honored Contributor.
77 views

9.22 - Unable to open Portlet Definition, Preference Fields

We have a very large portlet definition that previously has worked in all of our environments without issue.  After upgrading our Dev environment to 9.22, I am no longer able to open up the Preference Fields tab in the portlet definition.

 

We have about 180 fields in the portlet definitions and about 25 preference/filter fields.

 

The hourglass spins for a long time, eventually loading the page after about almost 10 minutes.

The server log is filling up with messages seen in the attachment.

 

Any ideas?

 

 

Thanks-

Danny

0 Likes
6 Replies
pepdwill Honored Contributor.
Honored Contributor.

Re: 9.22 - Unable to open Portlet Definition, Preference Fields

Also captured the following errors from the server log, while trying to open the Preference Fields tab:

 

ERROR JSESSIONID=1AF8F43FEFC22512922379EDA1306C86.HPPPM,USERNAME=admin server:http-0.0.0.0-8080-Processor16:com.kintana.core.server.servlet:2014/03/24-12:11:55.486 CDT: org.apache.jasper.JasperException: null
    at com.mercury.itg.servlet.ActionMonitorFilter.doFilter(ActionMonitorFilter.java:87)
    at com.mercury.itg.servlet.HibernateSessionFilter.doFilter(HibernateSessionFilter.java:97)
    at com.kintana.core.web.filter.BrowserCompatibilityFilter.applyFilter(BrowserCompatibilityFilter.java:34)
    at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:68)
    at com.kintana.core.web.filter.MLUFilter.applyFilter(MLUFilter.java:115)
    at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:68)
    at com.kintana.core.web.filter.stinger.ValidationFilter.applyFilter(ValidationFilter.java:178)
    at com.kintana.core.web.filter.stinger.ValidationFilter.doFilter(ValidationFilter.java:104)
    at com.kintana.core.web.filter.MultipartRequestFilter.applyFilter(MultipartRequestFilter.java:81)
    at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:68)
    at com.kintana.core.web.filter.ControlFilter.applyFilter(ControlFilter.java:931)
    at com.kintana.core.web.filter.ControlFilter.doFilter(ControlFilter.java:1555)
    at com.mercury.itg.servlet.I18NFilter.doFilter(I18NFilter.java:46)
    at com.kintana.core.web.filter.SchemeBasedRedirectFilter.doFilter(SchemeBasedRedirectFilter.java:75)
    at com.kintana.core.web.filter.Log4jFilter.applyFilter(Log4jFilter.java:56)
    at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:68)
    at com.kintana.core.web.filter.PerformanceFilter.applyFilter(PerformanceFilter.java:60)
    at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:68)

    Filtered Out 50 Stack Trace Lines.
ERROR JSESSIONID=1AF8F43FEFC22512922379EDA1306C86.HPPPM,USERNAME=admin server:http-0.0.0.0-8080-Processor16:com.kintana.core.server.servlet:2014/03/24-12:11:55.487 CDT: An unknown error has occurred. For more information, please contact your PPM administrator and provide the following GUID number:
GUID=F228FBF1-900C-9A44-8881-7A45DEA459D4
nested detail:null



An unknown error has occurred. For more information, please contact your PPM administrator and provide the following GUID number:
GUID=F228FBF1-900C-9A44-8881-7A45DEA459D4
    at com.kintana.core.web.filter.ControlFilter.applyFilter(ControlFilter.java:1007)
    at com.kintana.core.web.filter.ControlFilter.doFilter(ControlFilter.java:1555)
    at com.mercury.itg.servlet.I18NFilter.doFilter(I18NFilter.java:46)
    at com.kintana.core.web.filter.SchemeBasedRedirectFilter.doFilter(SchemeBasedRedirectFilter.java:75)
    at com.kintana.core.web.filter.Log4jFilter.applyFilter(Log4jFilter.java:56)
    at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:68)
    at com.kintana.core.web.filter.PerformanceFilter.applyFilter(PerformanceFilter.java:60)
    at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:68)
Caused by: org.apache.jasper.JasperException: null
    at com.mercury.itg.servlet.ActionMonitorFilter.doFilter(ActionMonitorFilter.java:87)
    at com.mercury.itg.servlet.HibernateSessionFilter.doFilter(HibernateSessionFilter.java:97)
    at com.kintana.core.web.filter.BrowserCompatibilityFilter.applyFilter(BrowserCompatibilityFilter.java:34)
    at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:68)
    at com.kintana.core.web.filter.MLUFilter.applyFilter(MLUFilter.java:115)
    at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:68)
    at com.kintana.core.web.filter.stinger.ValidationFilter.applyFilter(ValidationFilter.java:178)
    at com.kintana.core.web.filter.stinger.ValidationFilter.doFilter(ValidationFilter.java:104)
    at com.kintana.core.web.filter.MultipartRequestFilter.applyFilter(MultipartRequestFilter.java:81)
    at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:68)
    at com.kintana.core.web.filter.ControlFilter.applyFilter(ControlFilter.java:931)
    ... 7 more

    Filtered Out 27 Stack Trace Lines.
ERROR JSESSIONID=1AF8F43FEFC22512922379EDA1306C86.HPPPM,USERNAME=admin server:http-0.0.0.0-8080-Processor16:com.kintana.web:2014/03/24-12:11:55.488 CDT: An unknown error has occurred. For more information, please contact your PPM administrator and provide the following GUID number:
GUID=F228FBF1-900C-9A44-8881-7A45DEA459D4
nested detail:null



An unknown error has occurred. For more information, please contact your PPM administrator and provide the following GUID number:
GUID=F228FBF1-900C-9A44-8881-7A45DEA459D4
    at com.kintana.core.web.filter.ControlFilter.applyFilter(ControlFilter.java:1007)
    at com.kintana.core.web.filter.ControlFilter.doFilter(ControlFilter.java:1555)
    at com.mercury.itg.servlet.I18NFilter.doFilter(I18NFilter.java:46)
    at com.kintana.core.web.filter.SchemeBasedRedirectFilter.doFilter(SchemeBasedRedirectFilter.java:75)
    at com.kintana.core.web.filter.Log4jFilter.applyFilter(Log4jFilter.java:56)
    at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:68)
    at com.kintana.core.web.filter.PerformanceFilter.applyFilter(PerformanceFilter.java:60)
    at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:68)
Caused by: org.apache.jasper.JasperException: null
    at com.mercury.itg.servlet.ActionMonitorFilter.doFilter(ActionMonitorFilter.java:87)
    at com.mercury.itg.servlet.HibernateSessionFilter.doFilter(HibernateSessionFilter.java:97)
    at com.kintana.core.web.filter.BrowserCompatibilityFilter.applyFilter(BrowserCompatibilityFilter.java:34)
    at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:68)
    at com.kintana.core.web.filter.MLUFilter.applyFilter(MLUFilter.java:115)
    at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:68)
    at com.kintana.core.web.filter.stinger.ValidationFilter.applyFilter(ValidationFilter.java:178)
    at com.kintana.core.web.filter.stinger.ValidationFilter.doFilter(ValidationFilter.java:104)
    at com.kintana.core.web.filter.MultipartRequestFilter.applyFilter(MultipartRequestFilter.java:81)
    at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:68)
    at com.kintana.core.web.filter.ControlFilter.applyFilter(ControlFilter.java:931)
    ... 7 more

0 Likes
Absent Member.. randull Absent Member..
Absent Member..

Re: 9.22 - Unable to open Portlet Definition, Preference Fields

Hi Danny,

 

Any error on the serverlog related to this issue?

 

Best regards,
Randall

-- Remember to give Kudos to answers! (click the KUDOS star)
"If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
0 Likes
pepdwill Honored Contributor.
Honored Contributor.

Re: 9.22 - Unable to open Portlet Definition, Preference Fields

Randull -

 

Attached is a zip of the server log files generated while I was reproducing the issue.

 

0 Likes
Absent Member.. randull Absent Member..
Absent Member..

Re: 9.22 - Unable to open Portlet Definition, Preference Fields

Danny,

 

Please set these two parameters in loggin.conf (PPM-Home/conf folder) to initiate debugging in serverlog: 

A) com.kintana.core.logging.PRODUCT_FUNCTION_LOGGING_LEVEL = com.kintana.web.portlets, DEBUG
 
B) com.kintana.core.logging.SYSTEM_THRESHOLD = DEBUG

There is no need to restart the instance, since these are loggin.conf and not the server.conf parameters.

After setting these parameters, please replicate the error or the behavior. Once you are done with that, disable the debugging parameters and then send us the logs (They are present in <PPM_home>/server/<server_name>/log ). 

Best regards,
Randall

-- Remember to give Kudos to answers! (click the KUDOS star)
"If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
0 Likes
pepdwill Honored Contributor.
Honored Contributor.

Re: 9.22 - Unable to open Portlet Definition, Preference Fields

Attached are the logs generated when only trying to open the Preferences page, after making those changes to the logging conf file.

 

Note that the zip file w/ server logs in my post above was captured as I was trying to edit one of the preferences (clicking the Save button, etc).

 

It took a little over 5 minutes just for the page to load.

 

 

0 Likes
pepdwill Honored Contributor.
Honored Contributor.

Re: 9.22 - Unable to open Portlet Definition, Preference Fields

Attached are the server logs as I was saving changes to the portlet preferences.  It took about 6 minutes for the save to finish.  During the wait period nothing new was written to the server log, though some stuff finally appeared after it finished.

 

Any lines with a timestamp after 12:50 were from the Save.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.