[MAGNOLIA-1682] Content activation to Jackrabbit clustered public instances causes Index exceptions Created: 16/Aug/07 Updated: 15/Sep/08 Resolved: 03/Sep/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.5 |
| Type: | Bug | Priority: | Critical |
| Reporter: | zam6ak | Assignee: | Jan Haderka |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Magnilia 3.1-SNAPSHOT |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
To reporoduce
Problems found:
INFO info.magnolia.module.exchangesimple.ReceiveFilter ReceiveFilter.java(receive:114) 16.08.2007 08:08:16 Activation succeeded
ERROR info.magnolia.cms.taglibs.Include Include.java(doEndTag:166) 16.08.2007 08:10:18 Paragraph not found for page /features/mainColumnParagraphs/0
ERROR org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/magnoliaPublic02].[jsp] ApplicationDispatcher.java(invoke:704) 16.08.2007 11:17:39 Servlet.service() for servlet jsp threw exception java.lang.NullPointerException
|
| Comments |
| Comment by Jan Haderka [ 03/Sep/08 ] |
|
The Lucene index synchronization issues were solved in JackRabbit 1.3.3. Magnolia 3.5 have been released with JR 1.3.3 so this issue should not occur anymore. If there are still issues with index synchronization please report those directly on JackRabbit jira. |
| Comment by Magnolia International [ 09/Sep/08 ] |
|
Note that you might need / want to clear your indexes (before restarting the app server) to force Magnolia/Jackrabbit to reindex your repo - if you're not in a hurry, that is |
| Comment by zam6ak [ 10/Sep/08 ] |
|
So if I understand this correctly, untill Jackrabbit corrects all the clustering issues there is no way to set up Magnolia public instances in a cluster? |
| Comment by Philippe Marschall [ 11/Sep/08 ] |
|
It is very well possible. You just have to cluster at the Magnolia level (have multiple subscribers) instead of the Jackrabbit level. |
| Comment by Philipp Bracher [ 12/Sep/08 ] |
|
Note the 3.6 EE uses a transaction activation. Means that we guarantee that the content reaches either both or none of the public instances. This is recommended way for 'clustering' public instances. Nevertheless we want to use jr clustering in future (for other shared data like public users, comments), but for now we are 'blocked' by some critical issues. |
| Comment by zam6ak [ 15/Sep/08 ] |
|
Although transactional activation helps quite a bit it is not the same as clustering. |