On 5/10/2013 8:56 PM, Michael Sokolov wrote:
> On 5/10/2013 10:18 PM, Shawn Heisey wrote:
>> I don't know why I'm not having any trouble. I'm certainly glad that
>> I'm not, though! Thanks, Shawn
> Shawn, one question - in your server setup do you have:
>
> _querySolr.setRequestWriter(new BinaryRequestWriter());
>
> ? I didn't see that - it (used to be) the way you would request
> javabin to be used to communicate with the server.
>
> If you don't have that, you are probably using XML format. I guess we
> could just do that, too, at least until all our servers have been
> upgraded.
I did a packet capture on the both server versions, the updates that the
client is sending are indeed in XML format. I find myself a little
surprised by this. I'm not going to try to change it in production
until I have upgraded everything and lo longer have 3.5.0 in my network,
but I will go ahead and try it on my dev server.
I don't have a call to setRequestWriter or setParser. My server log
shows that the responses are javabin, and the packet captures confirm
that as well:
>From the 3.5.0 log:
May 10, 2013 9:04:07 PM org.apache.solr.core.SolrCore execute
INFO: [s0live] webapp=/solr path=/update
params={waitSearcher=true&wt=javabin&commit=true&softCommit=false&version=2}
status=0 QTime=5446
>From the 4.2.1 log:
INFO - 2013-05-10 21:04:02.276;
org.apache.solr.update.processor.LogUpdateProcessor; [s0live]
webapp=/solr path=/update
params={waitSearcher=true&commit=true&wt=javabin&version=2&softCommit=false}
{commit=} 0 1561
Thanks,
Shawn
