Grouper Users - Open Discussion List

[Chris Hyzer <>]

Which app server are you using?  Where are the files stored when you don't 
specify something?  This is just a guess. But maybe if it is an empty string, 
then it just uses the current directory (that the app server was started in?) 
 And maybe the appservers on different nodes were started in different 
directories, in one case where the appserver couldn't write to?

Thanks,
Chris

-----Original Message-----
From: 

 
[mailto:]
 On Behalf Of Colin Hudler
Sent: Friday, January 06, 2012 12:43 PM
To: 

Subject: Re: [grouper-users] Error liteui member import

Forget all that. I do see that you've created a custom 
servletFileUpload() to wrap it all with the factory. This stands out:

String tempDir = TagUtils.mediaResourceString("file.upload.temp.dir");

That property has no setting in media.properties. Why would it work in 
the other environments? It can be fixed by giving that a valid value. It 
also fixes my previous report of the problem. I'd love to be able to 
understand what might make it work without that setting, since none of 
the other environments have it either.

On 01/06/2012 11:23 AM, Colin Hudler wrote:
> My previous troubleshooting was probably a red-herring. Here's 
> something else that I am more interested in. I think it is related and 
> may provide better indications as to what is wrong. Also the problem 
> makes the ui hard to use.
>
> Only one of our many grouper environments has this problem, but I 
> cannot detect any difference. Some are exact clones with no FS change 
> whatsoever, yet do not exhibit this. *It happens with any browser and 
> every time*. We're running 1.6.3.
>
> The fault is easily triggered. Navigate to any group, then select 
> "Manage members". Click "Change Display". The display setting is not 
> saved, but the standard grouper-ui "Error" screen is displayed. The 
> following is logged.
>
> 2012-01-06 10:33:39,844 ERROR ui.GrouperUiFilter:  UI error
> java.lang.NullPointerException
>         at java.io.File.<init>(File.java:222)
>         at 
> org.apache.commons.fileupload.disk.DiskFileItem.getTempFile(DiskFileItem.java:611)
>  
>
>         at 
> org.apache.commons.fileupload.disk.DiskFileItem.getOutputStream(DiskFileItem.java:556)
>  
>
>         at 
> org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:362)
>  
>
>         at 
> org.apache.commons.fileupload.servlet.ServletFileUpload.parseRequest(ServletFileUpload.java:126)
>  
>
>         at 
> edu.internet2.middleware.grouper.j2ee.GrouperRequestWrapper.initMultipartMap(GrouperRequestWrapper.java:175)
>  
>
>         at 
> edu.internet2.middleware.grouper.j2ee.GrouperRequestWrapper.init(GrouperRequestWrapper.java:111)
>  
>
>         at 
> edu.internet2.middleware.grouper.ui.GrouperUiFilter.initRequest(GrouperUiFilter.java:534)
>  
>
>         at 
> edu.internet2.middleware.grouper.ui.GrouperUiFilter.doFilter(GrouperUiFilter.java:650)
>  
>
>         at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
>  
>
>         at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>  
>
>         at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219)
>  
>
>         at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>  
>
>         at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>  
>
>         at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>  
>
>         at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>  
>
>         at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) 
>
>         at 
> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at 
> org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at 
> org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:774)
>         at 
> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:703)
>  
>
>         at 
> org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:896)
>  
>
>         at 
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>  
>
>         at java.lang.Thread.run(Thread.java:619)
> 2012-01-06 10:33:39,856 ERROR ui.TileRecorderTag:  
> javax.servlet.jsp.JspException: ServletException in 
> '/WEB-INF/jsp/dynamicTile.jsp': NullPointerException:null
>
> Note that this stacktrace is about the same as the one I was 
> troubleshooting on the liteUI page. Here's some observations, but I'm 
> hoping you can steer me in some certain direction.
>
> - The tempfile setup for tomcat looks good. It can write files and 
> owns the directory, etc.
> - The form on that page is multipart/form-data. There is no 
> file-upload input.
> - GrouperRequestWrapper.initMultipartMap does indeed initialize 
> servletFileUpload() and parse the request
> - We're using tomcat 6.0.29
> - Grouper-ui is rather stock here with no changes outside of the 
> normal configuration files.
> - GrouperRequestWrapper.initMultipartMap doesn't use a 
> FileItemFactory, which is not correct use of the API, as far as I can 
> tell. See 
> <http://commons.apache.org/fileupload/apidocs/org/apache/commons/fileupload/servlet/ServletFileUpload.html>.
>  
> On the other hand, I have no idea why it works everywhere else.
>
> On 10/11/2011 02:46 PM, Chris Hyzer wrote:
>> It works for me.  Can you reproduce it on the grouper demo server 
>> (google finds link)?  :)
>>
>> Which browser are you using?
>>
>> Thanks,
>> Chris
>>
>> -----Original Message-----
>> From: 
>> 
>>  
>> [mailto:]
>>  On Behalf Of Colin Hudler
>> Sent: Tuesday, October 11, 2011 3:12 PM
>> To: 
>> 
>> Subject: [grouper-users] Error liteui member import
>>
>> Importing members from LiteUI (Advanced->Import) results in no web
>> response, but the attached error is logged. What is going on? It doesn't
>> happen every time, but most of the time. Seems to happen equally if "on
>> screen" or file upload is selected.
>>
>
>