tracker issue : CF-3330658

select a category, or use search below
(searches all categories and all time range)

CFCollection (Action=list) errors out, resolved by Jetty restart

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/UserError

Reporter/Name(from Bugbase): Tim Parker / Tim Parker (Tim Parker)

Created: 09/13/2012

Components: Text Search

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: Final /

Priority/Frequency: Major / Some users will encounter

Locale/System: English / Windows 7 64-bit

Vote Count: 0

Problem Description:
CFCollection (action=list) occasionally errors out, throwing:
   Error getting collection information.: org.apache.solr.common.SolrException: Error handling 'status' action org.apache.solr.common.SolrException: Error handling 'status' action at org.apache.solr.handler.admin.CoreAdminHandler.handleStatusAction( at org.apache.solr.handler.admin.CoreAdminHandler.handleRequestBody( at org.apache.solr.handler.RequestHandlerBase.handleRequest( at org.apache.solr.servlet.SolrDispatchFilter.handleAdminRequest( at org.apache.solr.servlet.SolrDispatchFilter.doFilter( at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter( at org.mortbay.jetty.servlet.ServletHandler.handle( at at org.mortbay.jetty.servlet.SessionHandler.handle( at org.mortbay.jetty.handler.ContextHandler....

restarting Jetty resolves the problem

Steps to Reproduce:
On an installation with one or more Solr collections configured... 
 - run <CFCollection action="list" name="qry"> - error occurs sporadically

>> While attempting to narrow down the (clearly inadequate for debugging) sequence of events... we also observed latency in the CFCollection (action=list) results - immediately after the Jetty restart, the result set was empty (qry.RecordCount EQ 0) - a minute or two later (not certain of the interval - could be shorter than one minute), the expected result set was returned

Actual Result:

Expected Result:

Any Workarounds:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3330658

Deployment Phase:	Release Candidate

External Customer Info:
External Company:  
External Customer Name: TParker
External Customer Email:  
External Test Config: My Hardware and Environment details:

CF10 (10.0.1. and 10.0.2 updates NOT applied)

Windows 7 ultimate, 16GB, JVM 1.6.0_33, 1GB allocated (Xms1024m Xmx1024m) 256MB maxPermSize

problem seen two separate machines - the other one is similarly configured.



Hi, We are unable to reproduce this issue Can you please check on the latest CF10 update , and if still occuring please provide test case? Regards Viny (Comment added from ex-user id:vnigam)
Comment by Adobe D.
18092 | December 20, 2013 04:35:02 AM GMT
quick testing with CF10 (updater 13) and latest JVM (1.7.0_67) shows that this might be resolved - latency after Jetty restart is minimal (1-2 seconds) and the result set is fully/correctly populated. This instance is running an upgraded Solr installation (3.6) to avoid the 'leading wildcard in search criteria' crash, so it's not clear if the resolution is due to updates included in updater 13... or in Solr - but... either way, it's probably safe to close this out as 'no longer occurs'
Comment by External U.
18093 | September 03, 2014 02:08:19 PM GMT