Problems with Lucene search

[spanishjohnny]

Sorry to bother but this is driving us mad…
Also some searches fail using both the webservices and the node browser so maybe this is not the appropriate section, sorry if this is so, but we're using webservices so I'm posting this here
we're trying to use alfresco (labs 3.0 under jboss 4.2) for our document management, but sometimes it seems to fail on lucene searches. I said "sometimes" because sometimes they work and sometimes they don't. So we tried to do a full reindex changing the appropriate field in repository.properties and all of a sudden one of the searches we impelemented stopped working both in our application and in node browser.
here's the snippet of our custommodel involved

 <type name="ip:profilo">
         <title>Profilo</title>
         <parent>cm:folder</parent>
         <properties>
            <property name="ip:noteprofilo">
               <type>d:text</type>
            </property>
         <property name="ip:numerolegislatura">
               <type>d:text</type>
            </property>
         <property name="ip:interrogante">
               <type>d:text</type>
            </property>
         <property name="ip:gruppo">
               <type>d:text</type>
            </property>
         <property name="ip:tipoatto">
               <type>d:text</type>
            </property>
         <property name="ip:datarisposta">
               <type>d:text</type>
            </property>
         <property name="ip:dataarchiviazione">
               <type>d:text</type>
            </property>
         <property name="ip:datarispostaaltrodic">
               <type>d:text</type>
            </property>
         <property name="ip:datapresentazione">
               <type>d:text</type>
            </property>
         <property name="ip:resoconto">
               <type>d:text</type>
            </property>
         <property name="ip:statointerrogazione">
               <type>d:text</type>
            </property>
         </properties>
      </type>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

queries fail only on one of this fields, the field ip:interrogante. Queries work if we do something like @ip\:interrogante:filippo* and fail if we do @ip\:interrogante:filippo
obviously the field is set to "filippo". I don't see any reason why this can fail on that particular field, there's no error during the indexing phase (other than on some docs where transformation fails, but this relates on their content I suppose).
We had to change some values in repository.properties such

# The maximum time spent pruning results
system.acl.maxPermissionCheckTimeMillis=600000
# The maximum number of results to perform permission checks against
system.acl.maxPermissionChecks=50000
‍‍‍‍‍

because of the number of docs and fields, but things worked fine for a while…
Is there any kind soul with some hint on this issue? also is there a way we can check lucene indexes to see if that field gets properly indexed?
thank you
FIlippo

[jm_pascal]

Hello,
Did you try a query like this  @ip\:interrogante:"filippo" ?

[spanishjohnny]

Hello,
Did you try a query like this  @ip\:interrogante:"filippo" ?

yes this is exactly what we tried both in the application and in node browser, it doesn't get any result.
Searching @ip\:interrogante:"filippo*" or @ip\:interrogante:filippo* brings some results (e.g. interrogante=filippo, interrogante=filippoxxx and in some cases interrogante:filippini). Just in case you're wondering there are no hidden or non utf chars after "filippo" and this search worked fine some days ago. I suspect some corruption with lucene indexes, but we tried deleting them and forcing a full reindex with no result…thanks