Minor Description
----Original Message----
From: grouper-users-request
Sent: Thursday, August 28, 2014 3:41 AM
To: grouper-users
Subject: [grouper-users] Grouper 2.2 Error when trying to look at group in new UI
Hi all,
we've recently upgraded our old Grouper 1.5 instance to 2.2 on DEV (with thanks to Shilen for assisting 
). We've noticed the following error when we look up certain groups (in the case below it's the sysadmin group):
Caused by: org.apache.jasper.JasperException: An exception occurred processing JSP page /WEB-INF/grouperUi2/group/groupHeader.jsp at line 170
167: </tr>
168: <tr>
169: <td><strong>${textContainer.text['groupLabelLastEditedBy']}</strong></td>
170: <td>${grouperRequestContainer.groupContainer.guiGroup.lastUpdatedByGuiSubject.shortLinkWithIcon}</td>
171: </tr>
172: <tr>
173: <td><strong>${textContainer.text['groupLabelTypeLabel']}</strong></td>
Stacktrace:
at org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:568)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:470)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:405)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:349)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:721)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:584)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:523)
at edu.internet2.middleware.grouper.ui.util.GrouperUiUtils.convertJspToString(GrouperUiUtils.java:1654)
... 38 more
Caused by: javax.el.ELException: Error reading 'lastUpdatedByGuiSubject' on type edu.internet2.middleware.grouper.grouperUi.beans.api.GuiGroup
at javax.el.BeanELResolver.getValue(BeanELResolver.java:101)
at org.apache.jasper.el.JasperELResolver.getValue(JasperELResolver.java:110)
at org.apache.el.parser.AstValue.getValue(AstValue.java:167)
at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:187)
at org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:956)
at org.apache.jsp.WEB_002dINF.grouperUi2.group.viewGroup_jsp._jspService(viewGroup_jsp.java:254)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
... 47 more
Caused by: edu.internet2.middleware.subject.SubjectNotFoundException: Subject not found by id: 8046F30EBA2D1656E04400144F00F4CC
at edu.internet2.middleware.subject.provider.JDBCSourceAdapter2.getSubject(JDBCSourceAdapter2.java:324)
at edu.internet2.middleware.subject.provider.JDBCSourceAdapter2.getSubject(JDBCSourceAdapter2.java:785)
at edu.internet2.middleware.grouper.subj.SourcesXmlResolver.find(SourcesXmlResolver.java:309)
at edu.internet2.middleware.grouper.subj.CachingResolver.find(CachingResolver.java:143)
at edu.internet2.middleware.grouper.subj.ValidatingResolver.find(ValidatingResolver.java:105)
at edu.internet2.middleware.grouper.SubjectFinder.findByIdAndSource(SubjectFinder.java:465)
at edu.internet2.middleware.grouper.Group.getModifySubject(Group.java:3591)
at edu.internet2.middleware.grouper.grouperUi.beans.api.GuiObjectBase.getLastUpdatedByGuiSubject(GuiObjectBase.java:177)
at sun.reflect.GeneratedMethodAccessor2403.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at javax.el.BeanELResolver.getValue(BeanELResolver.java:97)
... 55 more
If I understand the error correctly it's complaining that it can't find that unique identifier in our IDM which Grouper is configured to use as person source. I guess there are perhaps some internal groups to Grouper which are set with a particular subject id as owner, or our Dev IDM has somehow removed an account on which Grouper relies?
Should we create a functional account for Grouper in our IDM which has that ID in order to resolve that issue? Or is there some other configuration which I've missed?
We're running on Tomcat 8 and JRE 1.8 in case that's relevant.
Thanks!
Richard
Richard Good
Senior Analyst/Team Leader
IS Applications Development ISG team
–
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.