Sorry was busy last couple of weeks. You can find sources at
https://git.magnolia-cms.com/gitweb/ if you are still looking for them.
Cheers,
Jan
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=ce0c2684-7e76-4084-a120-65bd493a2f32
---
Hi, Here is how we fixed ISSUE 1: We synched up all the users from
author instance to all public instances. It appeared that there were users
whose login information wasn't identical on author and public instances. For
ex: we had couple of users non-active on author instance while they were stil
Ok here is what i have done. I took MySql dumps of magnolia from our production
boxes (including from the one which has the problem). Updated the MySql of
TEST instance with MySql dump from each production instance at a time. Removed
*indexes* before starting server. With one of production serv
[quote]But do tell me what else i need to try. What could be the issue here.
What i am missing.[/quote]
First of all I think you are mixing here number of different problems. You
started with login problems, then had issue with page loading too slow and now
you are showing the errors in index.
Thanks again. Here is what i did hoping to replicate the issue:
[b]Stopped the production server on which the issue is being seen. Took a dump
of magnolia db[/b]
[b]Restored the production magnolia db to Test instance magnolia db[/b]
[b]Ran the magnolia application.[/b]
[b]APPLICATION CAME UP FINE
[quote] It only happens in production. Note this is a non-logged-in page and we
have our cache enabled.
[/quote]
You might have more data in production then in the test instance. You might
have many more sessions running at the same time making other search queries on
public instance then you h
Trying to paste the code properly here.
[code]
<%
DateFormat dfNews = new SimpleDateFormat("MM/dd/");
String queryStrNews = "SELECT * from nt:base WHERE jcr:path LIKE
'/news/%/%/newsContent' ORDER BY articledate DESC";
Query qNews = MgnlContext.getQueryManager("website").createQuery(queryStrNe
Thanks Jan, i could agree no more. We are using .jsp templates and here is some
of the scriplet code. My initial thought is, there is scope for fine tuning.
However, i would need your pointers in grabbing the data properly. However,
what is still troubling me is, why would the [b]page work for s
This just says that rendering of a page takes more then 4 seconds. But not why.
You might want to have a look at the page and what it does. Judging from the
name and from the fact that you ran into issues w/ indexes at the same time, is
it possible that this page executes search? Maybe search is
Thanks Jan. We believe indexes are the problem and we are doing the following.
[b]Deleting the indexes as suggested and restarting tomcat. [/b]
[b]After couple of attempts we see the magnolia application come up fine.[/b]
However, after 30min or so, we seem to have [b]Issue 2[/b] i mentioned abov
Either the lucene index or the users workspace is corrupt on the box (possibly
more, but you won't know until you can login). If it's just indexes go to
/repositories/magnolia/workspaces/users folder and delete
"index" subfolder. Indexes will be regenerated by JR on restart. If this
doesn't hel
Thanks Richard for your response. On our side, on this particular box, we make
sure that we shutdown tomcat and confirm that no tomcat process exists before
we attempt a start. Also we have other web applications running on this box as
well on other boxes along with magnolia application. I am st
12 matches
Mail list logo
