You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Thorsten Glaser <t....@tarent.de> on 2009/09/03 13:43:28 UTC
Clustering: valid Node IDs?
Hello everyone,
which values are exactly legal for <Cluster id="…" syncDelay="2000" /> ?
I’m currently using the hostname (FQDN), with everything EXCEPT [a-zA-Z0-9-]
converted to _, and XML encoded (like → -), however, I am told that this
does not “work”.
Thanks in advance!
Sincerely,
//Th.Glaser
--
tarent Gesellschaft für Softwareentwicklung und IT-Beratung mbH
Geschäftsführer: Boris Esser, Elmar Geese
HRB AG Bonn 5168 - Ust-ID: DE122264941
http://www.tarent.com/
Heilsbachstr. 24, 53123 Bonn, fon +49 228 52675-0, fax +49 228 52675-25
Weigandufer 45, 12059 Berlin, fon +49 30 5682943-30, fax +49 228 52675-25
Schützenstr. 18, 10117 Berlin, fon +49 30 27594853, fax +49 30 78709617
Re: Clustering: valid Node IDs?
Posted by Thorsten Glaser <t....@tarent.de>.
On Mon, 7 Sep 2009, Thomas Müller wrote:
> The cluster id must be a String, I don't think there is a restriction.
Mmh, this is what I saw on the website too, which is why I’d ask.
> Except, the config file must be well formed.
<Cluster id="stage2a-1_tarent_net" syncDelay="2000">
> > however, I am told that this does not “work”.
>
> Could you provide more details?
Not right now, sorry. The reporter of this problem does not exactly
remember the problems and doesn’t currently have any time to reproduce
the issues. We are not even sure if the above-mentioned node ID is the
cause.
Thanks
//Th.Glaser
--
tarent Gesellschaft für Softwareentwicklung und IT-Beratung mbH
Geschäftsführer: Boris Esser, Elmar Geese
HRB AG Bonn 5168 - Ust-ID: DE122264941
http://www.tarent.com/
Heilsbachstr. 24, 53123 Bonn, fon +49 228 52675-0, fax +49 228 52675-25
Weigandufer 45, 12059 Berlin, fon +49 30 5682943-30, fax +49 228 52675-25
Schützenstr. 18, 10117 Berlin, fon +49 30 27594853, fax +49 30 78709617
Re: Clustering: valid Node IDs?
Posted by Thorsten Glaser <t....@tarent.de>.
On Mon, 7 Sep 2009, Thomas Müller wrote:
> Could you provide more details?
Okay, got it. The mod_jk workers.properties file used was set up
for "node1" and "node2", respectively, and the person installing
it did not know that these had to be replaced with the cluster
node IDs for it to work. (Our local “expert” just came back from
vacation.)
Thanks anyway!
bye,
//mirabilos
--
tarent Gesellschaft für Softwareentwicklung und IT-Beratung mbH
Geschäftsführer: Boris Esser, Elmar Geese
HRB AG Bonn 5168 - Ust-ID: DE122264941
http://www.tarent.com/
Heilsbachstr. 24, 53123 Bonn, fon +49 228 52675-0, fax +49 228 52675-25
Weigandufer 45, 12059 Berlin, fon +49 30 5682943-30, fax +49 228 52675-25
Schützenstr. 18, 10117 Berlin, fon +49 30 27594853, fax +49 30 78709617
Re: Clustering: valid Node IDs?
Posted by Thomas Müller <th...@day.com>.
Hi,
> which values are exactly legal for <Cluster id="…" syncDelay="2000" /> ?
The cluster id must be a String, I don't think there is a restriction.
Except, the config file must be well formed.
> however, I am told that this does not “work”.
Could you provide more details?
Regards,
Thomas
Re: SearchIndex config and supportHighlighting changes causes NPE on
search.jsp
Posted by Marcel Reutegger <ma...@gmx.net>.
Hi,
supportHighlighting is required to build excerpt for query results. if
you set supportHighlighting to false then the query result will return
null for the rep:excerpt() column. that's probably the case here. just
check if the excerpt value is non-null before calling getString() on
the value.
regards
marcel
2009/9/3 GILBART Frederic (extérieur société ALMAVIA)
<Fr...@groupe-berri.fr>:
> Hi all,
>
>
>
> After using jackrabbit for months i tryed to change my
> repository-workspace-SearchIndex config using
> http://wiki.apache.org/jackrabbit/Search parameters, to optimize index size
> and queries response times on my existing repository.
>
>
>
> I deleted all index/* and worskpaces/* folders to have index rebuilded and
> everything seems ok but 1 parameter cannot be changed.
>
>
>
> First repository was using supportHighlighting=true in its workspace config
> – everyting was ok.
>
>
>
> When it changes to supportHighlighting=false, i cannot search anymore using
> the
>
> /jackrabbit-webapp-1.6.0/search.jsp?q=* because of :
>
>
>
> org.apache.jasper.JasperException: java.lang.NullPointerException
>
>
> org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:522)
>
>
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:416)
>
>
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
>
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
>
> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>
>
>
> cause m�re
>
>
>
> java.lang.NullPointerException
>
> org.apache.jsp.search_jsp._jspService(search_jsp.java:265)
>
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>
> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>
>
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
>
>
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
>
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
>
> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>
>
>
> (For information, search does not produce NPE if has no results.)
>
>
>
> All others parameters may change or not, only this one produce the
> NullPointerException
>
> If i change it back to supportHighlighting=true and reduild indexes
> everything is ok again.
>
>
>
> Is this a bug or do I miss some steps in such update ? Does someone notice
> same behavior ? In such case, may the wiki be updated to warn of this ?
>
>
>
> Does someone know how to move from supportHighlighting=true to false because
> indexes are smaller that way ?
>
>
>
> Regards,
>
> Frederic Gilbart
>
>
>
>
>
>
>
>
>
> Ce message peut contenir de l’information confidentielle et est adressé
> uniquement au(x) destinataire(s) prévu(s) par l’expéditeur. Si vous n’êtes
> pas celui-ci, vous êtes priés de ne pas user, utiliser, disséminer ou
> reproduire le contenu de ce message. S’il s’agit d’une erreur, veuillez en
> avertir l’expéditeur dans les plus brefs délais.
>
> L’information contenue dans ce message reflète exclusivement l’opinion de la
> personne qui l’a émise mais en aucun cas celle du Groupe Berri.
>
> This message may contain confidential information destined to be read only
> by the intended recipient. No other persons should read, use, publish or
> reproduce the content of this message. If you receive this message by
> mistake, please notify the sender immediately.
>
> The information contained in this message represents the personal opinions
> of the individual that sent it and should not be construed as representing
> the position of the Berri Group.
>
>
SearchIndex config and supportHighlighting changes causes NPE on search.jsp
Posted by "GILBART Frederic (extérieur société ALMAVIA)" <Fr...@groupe-berri.fr>.
Hi all,
After using jackrabbit for months i tryed to change my repository-workspace-SearchIndex config using http://wiki.apache.org/jackrabbit/Search parameters, to optimize index size and queries response times on my existing repository.
I deleted all index/* and worskpaces/* folders to have index rebuilded and everything seems ok but 1 parameter cannot be changed.
First repository was using supportHighlighting=true in its workspace config - everyting was ok.
When it changes to supportHighlighting=false, i cannot search anymore using the
/jackrabbit-webapp-1.6.0/search.jsp?q=* because of :
org.apache.jasper.JasperException: java.lang.NullPointerException
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:522)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:416)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
cause m�re
java.lang.NullPointerException
org.apache.jsp.search_jsp._jspService(search_jsp.java:265)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
(For information, search does not produce NPE if has no results.)
All others parameters may change or not, only this one produce the NullPointerException
If i change it back to supportHighlighting=true and reduild indexes everything is ok again.
Is this a bug or do I miss some steps in such update ? Does someone notice same behavior ? In such case, may the wiki be updated to warn of this ?
Does someone know how to move from supportHighlighting=true to false because indexes are smaller that way ?
Regards,
Frederic Gilbart