Full-text search returns only 1 result

I have a very odd situation that has appeared in both our Development and Test (QA) environments, but not in Production. I don't know when the problem appeared and so haven't been able to nail it down to any particular change.

If I enter a term in the simple search box, I get back 1 and only 1 result. The result is always the same if the word is the same, but is different for different words.

We have a customized Webtop with Brava! Enterprise. Search works fine in "vanilla" webtop and in DA.

We are getting warnings in the all.log: pyxmlrpc_client.fault and socket.error: [Errno 10053], but nothing obvious.

We've verified IP addresses, ipv4/6, registered clients, etc., and have not come up with a resolution.

This is FAST/CS 6.5 SP1.

Does anyone have any ideas where/what to look for?

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

dm_user

Try to following step, see whether it works or not.

Put this entry in your log4j.properties file at the top.

log4j.logger.com.documentum.fc.client.search.impl.generation.docbase.dql.execution.ResultEntryManipulationUtils=WARN

clear the cache and delete compiled jsps.

Restart the app server and check.

I encountered the similar issue earlier.

Regards,

Arindam

All comments

DCTM_Guru

If it works with vanilla webtop and DA, then it has to do with the customizations. Have you deployed new customizations to Dev and Test that hasnt been deployed to PROD.

Also, move this discussion to the Documentum Developer Network.

For guidelines on using this forum, Please Read - DO NOT POST TECHNICAL QUESTIONS TO THIS FORUM!

dm_user

Are you getting only one result for other words too?

What are the changes you have made in the customization?

jklawrence

My apologies for posting in the wrong forum.

Yes, we have customizations in Development and Test that are not in Production. I've reviewed them and backed out several that looked like possibilities but they did not solve the problem. I think my next task will be to start to apply the changes to the vanilla instance and test at each step to see if/when the problem occurs.

And, yes, I get only one result for any word I put in.

dm_user

Try to following step, see whether it works or not.

Put this entry in your log4j.properties file at the top.

log4j.logger.com.documentum.fc.client.search.impl.generation.docbase.dql.execution.ResultEntryManipulationUtils=WARN

clear the cache and delete compiled jsps.

Restart the app server and check.

I encountered the similar issue earlier.

Regards,

Arindam

jklawrence

Arindam -

THANK YOU!!!

Yesterday I redeployed another instance of webtop, appllied all of our custom changes, and it worked fine. We were going to give up and just use the new instance, but it bothered us that we didn't know why it worked. Your suggestion resolved the problem.

In doing a little more digging we realized that we had the top-level setting in log4j set to "DEBUG" in both environments, but of course not in Production. I removed your line and just changed that setting to "WARN" and that also fixed the issue.

So it appears that there is something wrong with the way the cascading DEBUG setting works. We have Brava! installed, and it may be something to do with the integration between the applications.

Anyway, thank you for your help. I should have asked this forum sooner, it would have saved us a lot of headaches!!

- Jane