jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-1126) Content created by one TOMCAT not visible for another TOMCAT
Date Wed, 19 Sep 2007 16:43:12 GMT

     [ https://issues.apache.org/jira/browse/JCR-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jukka Zitting resolved JCR-1126.
--------------------------------

    Resolution: Invalid
      Assignee: Jukka Zitting

Again resolving this as Invalid. Please do not use the issue tracker for support questions.

The clustering feature request each cluster node to have their separate repository home directory
and configuration files - only the persisted content is shared between the cluster nodes.
See http://wiki.apache.org/jackrabbit/Clustering and the Jackrabbit mailing list archives
for more details. Also, feel free to ask questions on the Jackrabbit mailing list, but please
only file bug reports when you are reasonably sure that the problem is caused by Jackrabbit
itself and not a misconfiguration.

> Content created by one TOMCAT not visible for another TOMCAT
> ------------------------------------------------------------
>
>                 Key: JCR-1126
>                 URL: https://issues.apache.org/jira/browse/JCR-1126
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: webapp
>         Environment: Application running on loadbalanced 3 tomcats in unix
>            Reporter: Rama Krishna
>            Assignee: Jukka Zitting
>         Attachments: jaas.config, repository.xml, screenshot-1.jpg, workspace-v1.2.xml
>
>
> Hello friends, 
> I am working in a Content Management Project. 
> We have implemented load balancing in TOMCAT (say A, B and C). 
> But now the content created by TOMCAT-A is not visible for TOMCAT-B and TOMCAT-C even
though content folder is shared between the TOMCATS. 
> Thanks & Regards, 
> RK

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message