You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by Michael Nebel <mi...@nebel.de> on 2005/06/30 11:42:09 UTC
Re: [jira] Created: (NUTCH-64) no results after a restart of a search--server
(without tomcat restart)
Hi
the following patch seems to solve the problem:
diff -u net/nutch/ipc/Client.java*
--- net/nutch/ipc/Client.java 2005-06-29 14:41:02.000000000 +0200
+++ net/nutch/ipc/Client.java.~1.10.~ 2005-02-21 19:54:08.000000000 +0100
@@ -275,13 +275,7 @@
throws IOException {
Connection connection;
synchronized (connections) {
- // mijo: after a restart of the search-server connections
- // might be null
- if (connections !=null ) {
- connection = (Connection)connections.get(address);
- } else {
- connection=null;
- }
+ connection = (Connection)connections.get(address);
if (connection == null) {
connection = new Connection(address);
connections.put(address, connection);
Regards
Michael
Michael Nebel (JIRA) wrote:
> no results after a restart of a search--server (without tomcat restart)
> ------------------------------------------------------------------------
>
> Key: NUTCH-64
> URL: http://issues.apache.org/jira/browse/NUTCH-64
> Project: Nutch
> Type: Bug
> Components: searcher
> Environment: nutch-0.6 + patches from Feb. 2005
> Reporter: Michael Nebel
>
>
> After restarting the search-server without restarting the tomcat, the resultpage stays occasionally white. The reason:
>
> 2005-06-25 12:56:16 StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception
> java.lang.NullPointerException
> at java.util.Hashtable.get(Hashtable.java:333)
> at net.nutch.ipc.Client.getConnection(Client.java:278)
> at net.nutch.ipc.Client.call(Client.java:253)
> at net.nutch.searcher.DistributedSearch$Client.getSummary(DistributedSearch.java:418)
> at net.nutch.searcher.NutchBean.getSummary(NutchBean.java:248)
> at org.apache.jsp.meta_jsp._jspService(meta_jsp.java:115)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
> at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
> at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300)
> at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374)
> at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
> at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:675)
> at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
> at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
> at java.lang.Thread.run(Thread.java:534)
>
>
>
--
Michael Nebel
http://www.nebel.de/
http://www.netluchs.de/
Re: Bug in index-more plugin?
Posted by "yoursoft@freemail.hu" <yo...@freemail.hu>.
Dear Stephan,
Thanks for url.
Stefan Groschupf wotte:
> You can find the nutch bug tracking here:
> http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10680
> Cheers,
> Stefan
> Am 01.07.2005 um 11:42 schrieb yoursoft@freemail.hu:
Re: Bug in index-more plugin?
Posted by Stefan Groschupf <sg...@media-style.com>.
You can find the nutch bug tracking here:
http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10680
Cheers,
Stefan
Am 01.07.2005 um 11:42 schrieb yoursoft@freemail.hu:
> Dear Stephan,
>
> I think this is a bug. Where I can open a bug? In wiki?
>
> Regards,
> Ferenc
>
> Stefan Groschupf wrotte:
>
>
>> Hi,
>> this was already mentioned under the topic 'index-more: can't
>> parse erroneous date'.
>> I suggest we open a bug and vote for this bug.
>> Can you open this bug? I will vote for it. :-)
>> Stefan
>>
>> Am 01.07.2005 um 10:59 schrieb yoursoft@freemail.hu:
>>
>>
>>> Dear List,
>>>
>>> I found a problem in MoreIndexingFilter.java.
>>> When I indexing segments, I get large list of error messages:
>>> can't parse errorenous date: Wed, 10 Sep 2003 11:59:14 or
>>> can't parse errorenous date: Wed, 10 Sep 2003 11:59:14GMT
>>>
>>> I modifiing source code (I don't make 'patch'):
>>> Original (lines 137-138):
>>> DateFormat df = new SimpleDateFormat("EEE MMM dd HH:mm:ss yyyy
>>> zzz");
>>> Date d = df.parse(date);
>>> New:
>>> DateFormat df = new SimpleDateFormat("EEE, MMM dd HH:mm:ss
>>> yyyy", Locale.US);
>>> Date d = df.parse(date.substring(0,25));
>>>
>>> The modified code works fine.
>>>
>>> Best Regards,
>>> Ferenc
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>
Re: Bug in index-more plugin?
Posted by "yoursoft@freemail.hu" <yo...@freemail.hu>.
Dear Stephan,
I think this is a bug. Where I can open a bug? In wiki?
Regards,
Ferenc
Stefan Groschupf wrotte:
> Hi,
> this was already mentioned under the topic 'index-more: can't parse
> erroneous date'.
> I suggest we open a bug and vote for this bug.
> Can you open this bug? I will vote for it. :-)
> Stefan
>
> Am 01.07.2005 um 10:59 schrieb yoursoft@freemail.hu:
>
>> Dear List,
>>
>> I found a problem in MoreIndexingFilter.java.
>> When I indexing segments, I get large list of error messages:
>> can't parse errorenous date: Wed, 10 Sep 2003 11:59:14 or
>> can't parse errorenous date: Wed, 10 Sep 2003 11:59:14GMT
>>
>> I modifiing source code (I don't make 'patch'):
>> Original (lines 137-138):
>> DateFormat df = new SimpleDateFormat("EEE MMM dd HH:mm:ss yyyy zzz");
>> Date d = df.parse(date);
>> New:
>> DateFormat df = new SimpleDateFormat("EEE, MMM dd HH:mm:ss yyyy",
>> Locale.US);
>> Date d = df.parse(date.substring(0,25));
>>
>> The modified code works fine.
>>
>> Best Regards,
>> Ferenc
>>
>>
>
>
>
Re: Bug in index-more plugin?
Posted by Stefan Groschupf <sg...@media-style.com>.
Hi,
this was already mentioned under the topic 'index-more: can't parse
erroneous date'.
I suggest we open a bug and vote for this bug.
Can you open this bug? I will vote for it. :-)
Stefan
Am 01.07.2005 um 10:59 schrieb yoursoft@freemail.hu:
> Dear List,
>
> I found a problem in MoreIndexingFilter.java.
> When I indexing segments, I get large list of error messages:
> can't parse errorenous date: Wed, 10 Sep 2003 11:59:14 or
> can't parse errorenous date: Wed, 10 Sep 2003 11:59:14GMT
>
> I modifiing source code (I don't make 'patch'):
> Original (lines 137-138):
> DateFormat df = new SimpleDateFormat("EEE MMM dd HH:mm:ss yyyy zzz");
> Date d = df.parse(date);
> New:
> DateFormat df = new SimpleDateFormat("EEE, MMM dd HH:mm:ss yyyy",
> Locale.US);
> Date d = df.parse(date.substring(0,25));
>
> The modified code works fine.
>
> Best Regards,
> Ferenc
>
>
Bug in index-more plugin?
Posted by "yoursoft@freemail.hu" <yo...@freemail.hu>.
Dear List,
I found a problem in MoreIndexingFilter.java.
When I indexing segments, I get large list of error messages:
can't parse errorenous date: Wed, 10 Sep 2003 11:59:14 or
can't parse errorenous date: Wed, 10 Sep 2003 11:59:14GMT
I modifiing source code (I don't make 'patch'):
Original (lines 137-138):
DateFormat df = new SimpleDateFormat("EEE MMM dd HH:mm:ss yyyy zzz");
Date d = df.parse(date);
New:
DateFormat df = new SimpleDateFormat("EEE, MMM dd HH:mm:ss yyyy",
Locale.US);
Date d = df.parse(date.substring(0,25));
The modified code works fine.
Best Regards,
Ferenc