Re: [jetty-dev] default M1 etc/jetty.xml causes WARN for threadpool conf

[Aaron Daubman <daubman@xxxxxxxxx>]

Hi Thomas,

Sorry if this is a red herring - maybe I was too eager to get rolling with M1.
I grabbed the source from:
https://github.com/eclipse/jetty.project/zipball/jetty-9.0.0.M1
did a `mvn clean install` and then ran from target in distribution...

Thanks,
     Aaron

On Tue, Oct 16, 2012 at 5:26 AM, Thomas Becker <tbecker@xxxxxxxxxxx> wrote:
> Hi Aaron,
>
> I've downloaded M1 from here:
> http://search.maven.org/remotecontent?filepath=org/eclipse/jetty/jetty-distribution/9.0.0.M1/jetty-distribution-9.0.0.M1.tar.gz
>
> Unpacked it, didn't touch any configs and started it with "java -jar
> start.jar" which loads jetty.xml as configured by default in start.ini.
> However I don't get that warning. Could you please describe what you did to
> get the warning? jetty.xml looks ok to me.
>
> Cheers,
> Thomas
>
>
> On 10/16/12 4:15 AM, Aaron Daubman wrote:
>>
>> Greetings,
>>
>> Upon testing out the M1 build, I see the following logged in the
>> 'stderrout.log' file:
>>
>> ---snip---
>> 2012-10-15 22:04:24.913:WARN:oejx.XmlConfiguration:main: Ignored arg:
>> <Arg name="threadpool">|      <New id="threadpool"
>> class="org.eclipse.jetty.util.thread.QueuedThreadPool"><Set
>> name="minThreads">10</Set><Set name="maxThreads">200</Set><Set
>> name="detailedDump">false</Set></New>|    </Arg>
>> 2012-10-15 22:04:25.148:INFO:oejs.Server:main: jetty-9.0.0.M1
>> ---snip---
>>
>> Other than this, things appear to be running well.
>>
>> Thanks,
>>       Aaron
>> _______________________________________________
>> jetty-dev mailing list
>> jetty-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>
>
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-dev