Hi,
When I tried to remove a data from UI (which will in turn hit SOLR), the whole application got stuck up. When we took the log files of the UI, we could see that this set of requests did not reach SOLR itself. In the SOLR log file, we were able to find the following exception occuring at the same time. SEVERE: org.apache.solr.common.SolrException: null__javalangNullPointerException_ null__javalangNullPointerException_ request: http://solr/coreX/select at org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request at org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request at org.apache.solr.handler.component.HttpCommComponent$1.call at org.apache.solr.handler.component.HttpCommComponent$1.call at java.util.concurrent.FutureTask$Sync.innerRun at java.util.concurrent.FutureTask.run at java.util.concurrent.Executors$RunnableAdapter.call at java.util.concurrent.FutureTask$Sync.innerRun at java.util.concurrent.FutureTask.run at java.util.concurrent.ThreadPoolExecutor$Worker.runTask at java.util.concurrent.ThreadPoolExecutor$Worker.run at java.lang.Thread.run This situation resulted for another few hours. No one was able to perform any operation with the application and If any one tried to perform any action, it resulted in the above exception during that period. But, this situation resolved by itself after few hours and it started working like normal. Can you tell me if this situation was due to deadlock condition or was it due to the CPU utilization going beyond 100%? If it was due to the deadloack, then why did we not get any such messages in the log files?Or is it due to some other problem?Am I missing anything? Can you guide me on this? -- View this message in context: http://lucene.472066.n3.nabble.com/Null-Pointer-Exception-in-SOLR-tp3954952.html Sent from the Solr - User mailing list archive at Nabble.com.
