When it happens to me (it hasn't happened recently) I tracked it down to the
BitStoreManager.store method at line 332
320 // Where on the file system will this new bitstream go?
321 GeneralFile file = getFile(bitstream);
322
323 // Make the parent dirs if necessary
324 GeneralFile parent = file.getParentFile();
325
326 if (!parent.exists())
327 {
328 parent.mkdirs();
329 }
330
331 //Create the corresponding file and open it
332 file.createNewFile();
I don't have that many files, so I don't think the file system has run out
of inodes, but I guess I should really see what the current state is.
John
On 2/9/07, Jim Downing <[EMAIL PROTECTED]> wrote:
Dorothea Salo wrote:
> Jim Downing wrote:
>
Can't spot anything obvious.
> I've got the log level stepped up to DEBUG, so if any of
> that information would be useful, let me know what.
>
There should be a logging output coming out of BitstreamStorageManager
at line 821:
if (log.isDebugEnabled()) {
log.debug("Local filename for " + sInternalId + " is "
+ bufFilename.toString());
}
Examples of this line before successful and unsuccessful file creation
might get us a bit further, I suppose.
>>> The only other thing I can find in the logs that might be related
is this:
>>>
>>> 2007-02-08 15:15:50,628 ERROR org.jboss.web.localhost.Engine @
>>> StandardWrapperValve[edit-item]: Servlet.service() for servlet
edit-item threw
>>> exception
>>> java.lang.IllegalStateException: Cannot forward after response has
been committed
>>> at
> Digging a little further, I stepped through the process bit by
bit, examining
> the logs after each step. I learned that the above error happens after
clicking
> the "Add Creative Commons License" on the Edit Item screen. Doing so
also
> creates the error following:
>
> 2007-02-09 09:51:27,226 ERROR org.jboss.web.localhost.Engine @
> ErrorDispatcherValve[localhost]: Exception Processing
> ErrorPage[exceptionType=java.lang.Exception, location=/internal-error]
> java.lang.IllegalStateException
> at org.apache.coyote.Response.reset(Response.java:340)
> at org.apache.coyote.tomcat4.CoyoteResponse.reset(
CoyoteResponse.java:628)
>
This is a strange one. This exception usually happens if some code
writes to the response and then later forwards to a JSP. I can't see
anywhere this happens in the CC code (and as you point out, the trace
above didn't have any DSpace code in the stack). The only place I can
see that it might occur in DSpace is in the controlled vocabulary tag,
which uses the /internal-error servlet in the errorPage directive, which
I think could cause this problem since InternalErrorServlet also
forwards to a JSP.
So, it's Friday afternoon and my brain is fried - anyone else have any
ideas?
cheers,
jim
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
