[ http://jira.magnolia.info/browse/MAGNOLIA-1037?page=all ]

Grégory Joseph closed MAGNOLIA-1037.
------------------------------------

    Resolution: Cannot Reproduce

Please use the user's list for help about that kind of issue - or the 
appropriate channel if you have a support contract with us.


> Memory issue - crashing server
> ------------------------------
>
>                 Key: MAGNOLIA-1037
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-1037
>             Project: Magnolia
>          Issue Type: Bug
>    Affects Versions: 3.0 RC2
>         Environment: Linux, Jboss
>            Reporter: david hickman
>         Assigned To: Philipp Bracher
>
>  Several times in the past few weeks, the site has gone down. The
> majority of the times that this happened, I was working on the site. I
> haven't completely isolated what I was doing when it crashed. Sometimes it
> seemed when I was adding a lot of new users. Sometimes it happened when
> importing XML files. Many times I would be in the system, waiting for a
> process to complete...waiting...waiting...and at a certain point, I refreshed
> and received a "server unavailable" message. In most of those cases, IT would
> tell me that from their view, the box rebooted, but they still had to do
> rereboot it to bring it up. Ed and Chris seemed to think it was some sort of
> caching problem. They could probably add some comments here. Today's instance
> did not display a "server unavailable", but produced an empty window for the
> URL. In all of these cases, we've been able to reboot to recover.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------

Reply via email to