There is one more thing regarding listener for configurations - so I suppose the second webapp starts the listener on same port as first one (they race which one allocates it)
so once indexer is done it tries to send new config to webapp - which might confuse the webapp (I think this is what happens to you)
in trunk (and possibly 0.11.1) there are changes where you can tell OpenGrok script to SKIP sending new config to webapp (or configure new ports? - not sure if this is in, if not, you can try to add it - it's a simple change to codebase) - so it will(is) be possible to better configure automated indexing (which is targeted mainly at single instance containing a lot of projects, rather than separate instances)
hmm? L On 12.6.2012 5:04, Jens Elkner wrote:
On Mon, Jun 11, 2012 at 07:07:30PM +0000, Huiliang Zhang wrote: Hi, ...Tomcat6/webapps/searchforTeama à /var/opengrok/teama Tomcat6/webapps/searchforTeamb à /var/opengrok/teamb When the webpages are visited, they show source code repositories for different teams. However, if I check out a new code for team A and run “/var/opengrok/teama/bin/OpenGrok index” to rebuild the index files for team A, the webpage for team B will display the same source code repositories as in the webpage for team A. What causes this problem? Does “OpenGrok index” command update a shared memory used by both webpage A and webpage B?Do they use different configAddress params? Check web/WEB-INF/web.xml and cmdline param -U ... Have fun, jel.
_______________________________________________ opengrok-discuss mailing list opengrok-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss
