is this fixed in solr-1.4.1 ?
I have seen ConcurrentModificationException during search operation using EmbeddedSolrServer, when tested using jmeter with on more than one Concurrent user
s.

best,
Reuben

On 5/5/2009 2:25 AM, Shalin Shekhar Mangar wrote:
This is fixed in trunk.

2009/5/5 Noble Paul നോബിള്‍ नोब्ळ् <noble.p...@corp.aol.com>

hi Walter,
it needs synchronization. I shall open a bug.



On Mon, May 4, 2009 at 7:31 PM, Walter Ferrara <walters...@gmail.com>
wrote:
I've got a ConcurrentModificationException during a cron-ed delta import
of
DIH, I'm using multicore solr nightly from hudson 2009-04-02_08-06-47.
I don't know if this stacktrace maybe useful to you, but here it is:

java.util.ConcurrentModificationException
       at java.util.LinkedHashMap$LinkedHashIterator.nextEntry(Unknown
Source)
       at java.util.LinkedHashMap$EntryIterator.next(Unknown Source)
       at java.util.LinkedHashMap$EntryIterator.next(Unknown Source)
       at

org.apache.solr.handler.dataimport.DataImporter.getStatusMessages(DataImporter.java:384)
       at

org.apache.solr.handler.dataimport.DataImportHandler.handleRequestBody(DataImportHandler.java:210
)
       at

org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:131)
       at org.apache.solr.core.SolrCore.execute(SolrCore.java:1333)
       at

org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:303)
       at

org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:232)
       at

org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089)
       at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
       at

org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
       at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
       at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
       at
org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
       at

org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
       at

org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
       at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
       at org.mortbay.jetty.Server.handle(Server.java:285)
       at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:502)
       at

org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:821)
       at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
       at
org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:208)
       at
org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:378)
       at

org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:226)
       at

org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
of-course due to the nature of this exception I doubt it can be
reproduced
easily (this is the only one I've got, and the croned job runned a lot of
times), but maybe should a synchronized be put somewhere?
ciao,
Walter



--
-----------------------------------------------------
Noble Paul | Principal Engineer| AOL | http://aol.com




--

Reply via email to