Hi Oliver,
 
I am using slide 2.0.  Is this fixed in later versions? When can we expect 2.1?
 
Revati

Oliver Zeigermann <[EMAIL PROTECTED]> wrote:
I guess I have found the reason for the OutOfMemory error. All the 
descriptors were bunching up and were never freed. I guess I fixed this 
with my latest commit.

Could you please check?

Oliver

James Mason wrote:

> Oliver,
> Here's the stacktrace.
> 
> Also look at
> http://www.mail-archive.com/[EMAIL PROTECTED]/msg11007.html.
> I don't know if it's related, but the symptoms seem similar to me.
> 
> Other stuff:
> Auto versioning is off.
> With 2.0 restarting the server didn't seem to have any effect (still
> couldn't upload files). With the latest code from HEAD restarting seems
> to unstick it. I'll verify that in the morning.
> 
> -James
> 
> 
>>>>[EMAIL PROTECTED] 07/26/04 11:59 AM >>>
> 
> After the 2.0 release I had introduced sequences and Tlocks and had 
> hoped to fix most problems of that kind. However, it seems there still 
> are some left :(
> 
> Anyway, the pre-releases are there to detect and then fix problems like 
> those. I will persue this issue and am very confident it will be fixed 
> with the final 2.1 release.
> 
> If you people want to support me, please send as much information as 
> possible:
> 
> - Does this happen with the database store as well?
> - How do stack traces look like?
> - Does it happen as well when auto versioning is turned off?
> - Are uploads being done to the collection or different ones?
> - What is the timeout both for TLocks as well as for the file store?
> - Which part of the code do you suspect to be faulty?
> - James, could you send in the stack trace of that OutOfMemory error?
> 
> Oliver
> 
> James Mason wrote:
> 
> 
>>I'm seeing very similar behavior. I'll post a stacktrace this evening
>>when I get home.
>>
>>I've seen this happen with both the 2.0 release and a checkout from
>>HEAD yesterday. The new transaction API gives a slightly different
>>message, though. What's happening for me is an OutOfMemory error
> 
> occurs
> 
>>after putting the 500th or so file (it's like 90 bytes, so it's not
> 
> the
> 
>>size that's causing the error). After the error the logs report the
>>database is in a *dirty* state and no modification will be made until
> 
> a
> 
>>recovery is run.
>>
>>I think the problem is somewhere in the file store (not the
> 
> descriptor)
> 
>>since I've seen this happen using the tx store for descriptors as well
>>as the JDBC store.
>>
>>-James
>>
>>
>>
>>>>>[EMAIL PROTECTED] 7/26/2004 4:48:00 AM >>>
>>
>>Which Slide version are you using?
>>
>>The below message tells you a timeout occured while the transaction 
>>tries to prepare itself for commit. Try to increase the timeout time
> 
> in
> 
>>Domain.xml.
>>
>>Besides, I am not quite sure if Slide's implementation of the TM
>>handles 
>>failed prepares in the right way...
>>
>>Oliver
>>
>>r d wrote:
>>
>>
>>
>>>Hi,
>>>
>>>We are using slide webdav client and file store. During stress test,
>>
>>we got bombarded with 500- Internal server errors with log files
> 
> showing
> 
>>following
>>
>>
>>>org.apache.slide.store.txfile.AbstractTxFileStoreService - CRITICAL
>>
>>- Thread Thread[http8080-Processor98,5,main] failed to prepare
>>transaction branch http8080-Processor98-1090588028363-16435
>>
>>
>>>org.apache.slide.store.txfile.rm.ResourceManagerException:
>>
>>http8080-Processor98-1090588028363-16435: Could not upgrade to commit
>>lock for resource at '/history.def.xml' (ERR_NO_LOCK)
>>
>>
>>>and
>>>
>>>org.apache.slide.webdav.WebdavServlet - ERROR -
>>
>>org.apache.slide.webdav.WebdavException: Internal Server Error
>>
>>
>>>org.apache.slide.webdav.WebdavException: Internal Server Error
>>>at
>>
>>
> org.apache.slide.webdav.method.AbstractWebdavMethod.run(AbstractWebdavMethod.java:355)
> 
>>>at
>>
>>org.apache.slide.webdav.WebdavServlet.service(WebdavServlet.java:165)
>>
>>
>>>What could be the problem and solution thereof? We were having 200
>>
>>users.
>>
>>
>>>Thanks in advance
>>>
>>> 
>>>---------------------------------
>>>Do you Yahoo!?
>>>Yahoo! Mail is new and improved - Check it out!
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [EMAIL PROTECTED] 
>>For additional commands, e-mail: [EMAIL PROTECTED] 
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Reply via email to