lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Commented] (SOLR-3706) Ship setup to log with log4j.
Date Thu, 28 Mar 2013 00:53:16 GMT


Hoss Man commented on SOLR-3706:

bq. Something is still broken as far as how log4j is being configured when tests are run...

Possibly related, but as of this change, i can't get "ant test" to pass for the solrj tests.

Using trunk, i can run the following...

svn update -r 1461586 && ant clean && cd solr/solrj/ && ant test -Dtests.dups=10

...and everything runs great.  

But as soon as i try to use r1461587 (or later) at least one of the solrj tests using jetty
will fail (even w/o trying to run duplicate tests) with a NoHttpResponseException...

svn update -r 1461587 && ant clean && cd solr/solrj/ && ant test


[junit4:junit4] HEARTBEAT J2 PID(18228@frisbee): 2013-03-27T17:40:10, stalled for  125s at:
[junit4:junit4] HEARTBEAT J2 PID(18228@frisbee): 2013-03-27T17:41:10, stalled for  185s at:
[junit4:junit4] Suite: org.apache.solr.client.solrj.embedded.SolrExampleJettyTest
[junit4:junit4]   2> SLF4J: Class path contains multiple SLF4J bindings.
[junit4:junit4]   2> SLF4J: Found binding in [jar:file:/home/hossman/lucene/dev/solr/solrj/lib/slf4j-log4j12-1.6.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
[junit4:junit4]   2> SLF4J: Found binding in [jar:file:/home/hossman/lucene/dev/solr/core/lib/slf4j-log4j12-1.6.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
[junit4:junit4]   2> SLF4J: Found binding in [jar:file:/home/hossman/lucene/dev/solr/example/lib/ext/slf4j-log4j12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
[junit4:junit4]   2> SLF4J: See for an
[junit4:junit4]   2> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
[junit4:junit4]   2> log4j:WARN No appenders could be found for logger (org.apache.solr.SolrJettyTestBase).
[junit4:junit4]   2> log4j:WARN Please initialize the log4j system properly.
[junit4:junit4]   2> log4j:WARN See
for more info.
[junit4:junit4]   2> Creating dataDir: /home/hossman/lucene/dev/solr/build/solr-solrj/test/J2/./solrtest-SolrExampleJettyTest-1364431081119
[junit4:junit4]   2> NOTE: reproduce with: ant test  -Dtestcase=SolrExampleJettyTest -Dtests.method=testUpdateMultiValuedField
-Dtests.seed=D7EFA4209757AF4C -Dtests.slow=true -Dtests.locale=uk -Dtests.timezone=America/Argentina/Rio_Gallegos
[junit4:junit4] ERROR    201s J2 | SolrExampleJettyTest.testUpdateMultiValuedField <<<
[junit4:junit4]    > Throwable #1: org.apache.solr.client.solrj.SolrServerException: IOException
occured when talking to server at:
[junit4:junit4]    > 	at __randomizedtesting.SeedInfo.seed([D7EFA4209757AF4C:C5EA294B445B7894]:0)
[junit4:junit4]    > 	at org.apache.solr.client.solrj.impl.HttpSolrServer.request(
[junit4:junit4]    > 	at org.apache.solr.client.solrj.impl.HttpSolrServer.request(
[junit4:junit4]    > 	at org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(
[junit4:junit4]    > 	at org.apache.solr.client.solrj.SolrServer.commit(
[junit4:junit4]    > 	at org.apache.solr.client.solrj.SolrExampleTests.testUpdateMultiValuedField(
[junit4:junit4]    > 	at
[junit4:junit4]    > Caused by: org.apache.http.NoHttpResponseException: The target server
failed to respond
[junit4:junit4]    > 	at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(
[junit4:junit4]    > 	at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(
[junit4:junit4]    > 	at
[junit4:junit4]    > 	at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(
[junit4:junit4]    > 	at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(
[junit4:junit4]    > 	at org.apache.http.impl.conn.ManagedClientConnectionImpl.receiveResponseHeader(
[junit4:junit4]    > 	at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(
[junit4:junit4]    > 	at org.apache.http.protocol.HttpRequestExecutor.execute(
[junit4:junit4]    > 	at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(
[junit4:junit4]    > 	at org.apache.http.impl.client.DefaultRequestDirector.execute(
[junit4:junit4]    > 	at org.apache.http.impl.client.AbstractHttpClient.execute(
[junit4:junit4]    > 	at org.apache.http.impl.client.AbstractHttpClient.execute(
[junit4:junit4]    > 	at org.apache.http.impl.client.AbstractHttpClient.execute(
[junit4:junit4]    > 	at org.apache.solr.client.solrj.impl.HttpSolrServer.request(
[junit4:junit4]    > 	... 44 more
[junit4:junit4]   2> NOTE: test params are: codec=Lucene42: {}, docValues:{}, sim=RandomSimilarityProvider(queryNorm=false,coord=crazy):
{}, locale=uk, timezone=America/Argentina/Rio_Gallegos
[junit4:junit4]   2> NOTE: Linux 3.2.0-40-generic amd64/Oracle Corporation 1.7.0_15 (64-bit)/cpus=4,threads=1,free=171547592,total=337838080
[junit4:junit4]   2> NOTE: All tests run in this JVM: [SolrExampleJettyTest]
[junit4:junit4] Completed on J2 in 213.23s, 27 tests, 1 error <<< FAILURES!
[junit4:junit4] Suite: org.apache.solr.client.solrj.request.TestCoreAdmin
[junit4:junit4] Completed on J2 in 0.65s, 2 tests
[junit4:junit4] Suite: org.apache.solr.client.solrj.embedded.LargeVolumeBinaryJettyTest
[junit4:junit4] Completed on J2 in 1.03s, 1 test
[junit4:junit4] Suite: org.apache.solr.common.util.TestNamedListCodec
[junit4:junit4] Completed on J2 in 0.31s, 4 tests
[junit4:junit4] Suite: org.apache.solr.common.params.SolrParamTest
[junit4:junit4] Completed on J2 in 0.02s, 1 test
[junit4:junit4] Suite: org.apache.solr.client.solrj.embedded.SolrExampleStreamingTest
[junit4:junit4] Completed on J2 in 18.64s, 27 tests
[junit4:junit4] Suite: org.apache.solr.common.util.TestXMLEscaping
[junit4:junit4] Completed on J2 in 0.07s, 7 tests
[junit4:junit4] Suite: org.apache.solr.client.solrj.response.FacetFieldTest
[junit4:junit4] Completed on J2 in 0.01s, 1 test
[junit4:junit4] Tests with failures:
[junit4:junit4]   - org.apache.solr.client.solrj.embedded.SolrExampleJettyTest.testUpdateMultiValuedField
[junit4:junit4] JVM J0:     1.01 ..    79.72 =    78.71s
[junit4:junit4] JVM J1:     1.23 ..    79.74 =    78.52s
[junit4:junit4] JVM J2:     1.02 ..   235.99 =   234.97s
[junit4:junit4] Execution time total: 3 minutes 56 seconds
[junit4:junit4] Tests summary: 45 suites, 266 tests, 1 error

...the failures happen in different tests at different places, but all the ones i've seen
have happened in the middle of tests -- never the "first" attempt at talking to the solr server,
suggesting that the server is in fact up, and responds to at least some of the add/delete/commit
requests but then later it suddenly vanishes.  (I have no idea why this might be happening,
or how it might related to the changes in r1461587 ... there is no hint as to why the server
has suddenly vanished, because of the previously mentioned problem of log4j not finding config).

> Ship setup to log with log4j.
> -----------------------------
>                 Key: SOLR-3706
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>            Priority: Minor
>             Fix For: 4.3, 5.0
>         Attachments: SOLR-3706-maven.patch, SOLR-3706-maven.patch, SOLR-3706.patch, SOLR-3706-solr-log4j.patch,
> Currently we default to java util logging and it's terrible in my opinion.
> *It's simple built in logger is a 2 line logger.
> *You have to jump through hoops to use your own custom formatter with jetty - either
putting your class in the start.jar or other pain in the butt solutions.
> *It can't roll files by date out of the box.
> I'm sure there are more issues, but those are the ones annoying me now. We should switch
to log4j - it's much nicer and it's easy to get a nice single line format and roll by date,
> If someone wants to use JUL they still can - but at least users could start with something

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message