Thank you very much Stuart, your 3 steps helped me solve the delay.

I repeated the operation getting the same results, so I moved to check the
memory.

I configured java to use 2GB max of memory (the server has 4GB) and used
jconsole to see if anything happened but everything was fine on the 10
minutes of waiting, so I moved to network services.

Using netstat I noticed an SMTP connections each time I repeated the
operation and it tourned out to be a configuration error with the SMTP
settings (extraproperties of ssl with gmail).

Thank you again for your time and help.
Greetings

Elifelet López
Jefatura de Infraestructura - DTI
Universidad de Montemorelos


2014-03-06 20:59 GMT-06:00 Stuart Yeates <[email protected]>:

>  [Don't worry about your English; the description of the problem is fine.]
>
>
>
> (a)    The first thing I do in terms of Java slowness is to repeat the
> operation. Often tools such as tomcat can be very slow to start up, but
> once they're started they can be much quicker.
>
> (b)   The second thing is to make sure that you've giving your java
> enough memory (not enough memory results in excessive garbage collection)
> but not too much (which can result in excessive swapping). Try doubling or
> halving the memory you give it. Use system tools to see how much it's
> actually using of what you give it.
>
> (c)    Use a tool like 'top' to see what is running during the 10
> minutes. If java / tomcat is running, it's a dspace issue. If postgres is
> running it's a database issue. If nothing is running it's a network issue
> (such as trying to connect to a remote site and waiting for a timeout) or a
> file I/O issue (such as writing a very large file to a slow disk, etc).
>
> Cheers
>
> stuart
>
>
>
>
>
> *From:* Elifelet Lopez Ramos [mailto:[email protected]]
> *Sent:* Friday, 7 March 2014 2:52 p.m.
> *To:* [email protected]
> *Subject:* [Dspace-tech] Submission taking too much time after license
> agreement
>
>
>
> Hello All
>
>
>
> I'm new in the lists world and English is not my first language so thank
> you for your understanding.
>
>
>
> I'm using DSpace 3.2 and as the title says, when an Item is submitted it
> takes too much time on the final step (the license agreement). I checked
> the logs and found a line that says that Apache Cocoon processed the
> request en 10.092 minutes!!
>
>
>
> I don't know where to start searching for a fix since there is no error at
> all.
>
> Basically i haven't change anything since the installation (except from
> the header file of the jspui) so everything should be default.
>
>
>
> Could someone give me some guidance please?
>
> I'm attaching part the cocoon log where i found the line I'm talking about
> (it's almost at the end).
>
>
>   Elifelet López
>
> [image: Description: Image removed by sender.]
>

<<inline: image001.jpg>>

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to