daisy 2.0.1 hangs without error

[Bart Van den Abeele-3]

Hi,

I have several daisy-instances running (20+).  They are version 2.0.1.  Every week i have to restart daisy on several servers.  When i look in the logs i get no message about the shutdown, i see no special exceptions.  I look in data-dir/logs.  This is very annoying and it gives no good image of the product to customers.  What can be done to improve this?

**** DISCLAIMER ****
http://www.schaubroeck.be/maildisclaimer.htm

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

[Karel Vervaeke]

Daisy 2.0.1 is almost 2 and a half years old.
The *most cost-effective way* to solve this would be to try upgrading
to a more recent Daisy version.

Then again, if you insist on finding the problem, there are lots of
things you can do to try to locate the problem (jmx monitoring,
logging on application, jvm (gc!) and os level, ...)
Did you check the logs of the wrapper scripts btw?  There should be at
least some information of the daisy instance hanging.
You are using the wrapper scripts, right?

We recently had some hanging problems, they were solved by changing
the jdk version. (upgraded from java -1.6.0.07 to java-1.6.0.16)

HTH,
Karel


On Tue, Oct 6, 2009 at 11:26 AM, Bart Van den Abeele
<bvda@...> wrote:

> Hi,
>
> I have several daisy-instances running (20+).  They are version 2.0.1.
> Every week i have to restart daisy on several servers.  When i look in the
> logs i get no message about the shutdown, i see no special exceptions.  I
> look in data-dir/logs.  This is very annoying and it gives no good image of
> the product to customers.  What can be done to improve this?
>
> --
> Met vriendelijke groeten,
> Bart Van den Abeele
> Email: bvda@...
> Helpdesk : [phone]
> Persoonlijk : [phone]
>
> **** DISCLAIMER ****
> http://www.schaubroeck.be/maildisclaimer.htm
>
> _______________________________________________
> daisy community mailing list
> Professional Daisy support:
> http://outerthought.org/en/services/daisy/support.html
> mail to: daisy@...
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>
>

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

[Bart Van den Abeele-3]

Hi,

I don't have a good feeling that upgrading just will fix the issue.  I doubt it seriously.  You give no clear reason why that would fix this issue.  2 years back we also needed a stable product.  I would rather feel out why my repo hangs and act on that but without a clear indication of the error that is very hard.  You talk about jmx-monitoring and other stuff.  How do i set this up?  My guess is that it has to do with the cache : 10k docs (these are the default right?) and only 256mb ram 100kb/document requires 1024mb ram.  Wouldn't i get an error of this?  Any other thoughts?   Where can i locate the logging of the wrapper-scripts?

My college's are working hard with my product and the hangs are far to frequent to work fluently.  It is starting to annoy them (and me).  The java-version is 1.6.0.14.  I hope we can resolve this issue soon.



Karel Vervaeke schreef:

Daisy 2.0.1 is almost 2 and a half years old.
The *most cost-effective way* to solve this would be to try upgrading
to a more recent Daisy version.

Then again, if you insist on finding the problem, there are lots of
things you can do to try to locate the problem (jmx monitoring,
logging on application, jvm (gc!) and os level, ...)
Did you check the logs of the wrapper scripts btw?  There should be at
least some information of the daisy instance hanging.
You are using the wrapper scripts, right?

We recently had some hanging problems, they were solved by changing
the jdk version. (upgraded from java -1.6.0.07 to java-1.6.0.16)

HTH,
Karel


On Tue, Oct 6, 2009 at 11:26 AM, Bart Van den Abeele
bvda@... wrote:
  

Hi,

I have several daisy-instances running (20+).  They are version 2.0.1.
Every week i have to restart daisy on several servers.  When i look in the
logs i get no message about the shutdown, i see no special exceptions.  I
look in data-dir/logs.  This is very annoying and it gives no good image of
the product to customers.  What can be done to improve this?

--
Met vriendelijke groeten,
Bart Van den Abeele
Email: bvda@...
Helpdesk : [phone]
Persoonlijk : [phone]

**** DISCLAIMER ****
http://www.schaubroeck.be/maildisclaimer.htm

_______________________________________________
daisy community mailing list
Professional Daisy support:
http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy


    

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

  

**** DISCLAIMER ****
http://www.schaubroeck.be/maildisclaimer.htm

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

[Karel Vervaeke]

On Wed, Oct 14, 2009 at 9:35 AM, Bart Van den Abeele
<bvda@...> wrote:
> Hi,
>
> I don't have a good feeling that upgrading just will fix the issue.  I doubt
> it seriously.  You give no clear reason why that would fix this issue.
Two years of development time is no clear reason, but it is a very
good reason to at least try an upgrade and to see if it fixes your
problem.

> 2 years back we also needed a stable product.  I would rather feel out why my
> repo hangs and act on that but without a clear indication of the error that
> is very hard.  You talk about jmx-monitoring and other stuff.  How do i set
> this up?
Google is your friend. Search for "jmx monitoring" and "garbage
collection logging" respectively to find out which properties.
Once jmx monitoring is enabled you need jconsole or another similar tool.

>  My guess is that it has to do with the cache : 10k docs (these are
> the default right?) and only 256mb ram 100kb/document requires 1024mb ram.
> Wouldn't i get an error of this?
Not having enough ram and a cache size that is much smaller than the
actively consulted set of documents is indeed a possible cause for
problems. I'm not sure which errors you should get.
The wrapper scripts usually log to
${wikidata}/logs/daisy-wiki-service.log and
${repodata}/logs/daisy-repository-server-service.log.

You can also try obtaining a stackdump (using jstack or hitting
ctrl-break with the repository running in a console) when the
repository hangs.

> Any other thoughts?
not immediately.  Just gather as much information to analyse as you
can.  Be prepared to analyse most of it yourself, I have only limited
time
to assist you on the mailing list.

>   Where can i locate the logging of the wrapper-scripts?
The location is described here:
http://www.daisycms.org/daisydocs-2_3/admin/service/330-cd.html

> My college's are working hard with my product and the hangs are far to
> frequent to work fluently.  It is starting to annoy them (and me).  The
> java-version is 1.6.0.14.  I hope we can resolve this issue soon.
As do I

regards,
Karel
_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy