[jetty-dev] default M1 etc/jetty.xml causes WARN for threadpool config

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[jetty-dev] default M1 etc/jetty.xml causes WARN for threadpool config

Aaron Daubman
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
[hidden email]
https://dev.eclipse.org/mailman/listinfo/jetty-dev
Reply | Threaded
Open this post in threaded view
|

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

Thomas Becker
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
> [hidden email]
> https://dev.eclipse.org/mailman/listinfo/jetty-dev

_______________________________________________
jetty-dev mailing list
[hidden email]
https://dev.eclipse.org/mailman/listinfo/jetty-dev
Reply | Threaded
Open this post in threaded view
|

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

Aaron Daubman
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 <[hidden email]> 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
>> [hidden email]
>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>
>
> _______________________________________________
> jetty-dev mailing list
> [hidden email]
> https://dev.eclipse.org/mailman/listinfo/jetty-dev
_______________________________________________
jetty-dev mailing list
[hidden email]
https://dev.eclipse.org/mailman/listinfo/jetty-dev
Reply | Threaded
Open this post in threaded view
|

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

Aaron Daubman
another possibly important piece of context - in order to get the
warning, you need to uncomment the server logging section in
start.ini:
---snip---
#===========================================================
# Server logging.
# The following configuration will redirect stderr and stdout
# to file which is rolled over daily.
#-----------------------------------------------------------
etc/jetty-logging.xml
#===========================================================
---snip--

The warning is then the first line logged to the stderrout.log file:
---snip---
2012-10-16 08:08:20.039: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>
---snip---

Without uncommenting the start.ini 'etc/jetty-logging.xml' option, I
do not see this warning...

Thanks again,
      Aaron


On Tue, Oct 16, 2012 at 8:04 AM, Aaron Daubman <[hidden email]> wrote:

> 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 <[hidden email]> 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
>>> [hidden email]
>>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>>
>>
>> _______________________________________________
>> jetty-dev mailing list
>> [hidden email]
>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
_______________________________________________
jetty-dev mailing list
[hidden email]
https://dev.eclipse.org/mailman/listinfo/jetty-dev
Reply | Threaded
Open this post in threaded view
|

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

Jesse McConnell
m1 is available for download from eclipse now

http://download.eclipse.org/jetty/

--
jesse mcconnell
[hidden email]


On Tue, Oct 16, 2012 at 7:10 AM, Aaron Daubman <[hidden email]> wrote:

> another possibly important piece of context - in order to get the
> warning, you need to uncomment the server logging section in
> start.ini:
> ---snip---
> #===========================================================
> # Server logging.
> # The following configuration will redirect stderr and stdout
> # to file which is rolled over daily.
> #-----------------------------------------------------------
> etc/jetty-logging.xml
> #===========================================================
> ---snip--
>
> The warning is then the first line logged to the stderrout.log file:
> ---snip---
> 2012-10-16 08:08:20.039: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>
> ---snip---
>
> Without uncommenting the start.ini 'etc/jetty-logging.xml' option, I
> do not see this warning...
>
> Thanks again,
>       Aaron
>
>
> On Tue, Oct 16, 2012 at 8:04 AM, Aaron Daubman <[hidden email]> wrote:
>> 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 <[hidden email]> 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
>>>> [hidden email]
>>>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>>>
>>>
>>> _______________________________________________
>>> jetty-dev mailing list
>>> [hidden email]
>>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
> _______________________________________________
> jetty-dev mailing list
> [hidden email]
> https://dev.eclipse.org/mailman/listinfo/jetty-dev
_______________________________________________
jetty-dev mailing list
[hidden email]
https://dev.eclipse.org/mailman/listinfo/jetty-dev
Reply | Threaded
Open this post in threaded view
|

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

Thomas Becker
In reply to this post by Aaron Daubman
Ok, uncommenting jetty-logging.xml did the trick. I can reproduce the
warning now. At a first glimpse it looks all ok. Server has a
constructor with a single threadpool parameter. I will have a look and
fix that.

Thanks for pointing that out, Aaron.

On 10/16/12 2:10 PM, Aaron Daubman wrote:

> another possibly important piece of context - in order to get the
> warning, you need to uncomment the server logging section in
> start.ini:
> ---snip---
> #===========================================================
> # Server logging.
> # The following configuration will redirect stderr and stdout
> # to file which is rolled over daily.
> #-----------------------------------------------------------
> etc/jetty-logging.xml
> #===========================================================
> ---snip--
>
> The warning is then the first line logged to the stderrout.log file:
> ---snip---
> 2012-10-16 08:08:20.039: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>
> ---snip---
>
> Without uncommenting the start.ini 'etc/jetty-logging.xml' option, I
> do not see this warning...
>
> Thanks again,
>        Aaron
>
>
> On Tue, Oct 16, 2012 at 8:04 AM, Aaron Daubman <[hidden email]> wrote:
>> 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 <[hidden email]> 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
>>>> [hidden email]
>>>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>>>
>>> _______________________________________________
>>> jetty-dev mailing list
>>> [hidden email]
>>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
> _______________________________________________
> jetty-dev mailing list
> [hidden email]
> https://dev.eclipse.org/mailman/listinfo/jetty-dev

_______________________________________________
jetty-dev mailing list
[hidden email]
https://dev.eclipse.org/mailman/listinfo/jetty-dev
Reply | Threaded
Open this post in threaded view
|

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

Thomas Becker
In reply to this post by Aaron Daubman
Hi Aaron,

the problem is that jetty.xml was loaded after jetty-logging.xml and
thus the "Server" has been instantiated already before jetty.xml is
loaded. So the constructor args for the server have been ignored.

I just fixed:
http://git.eclipse.org/c/jetty/org.eclipse.jetty.project.git/commit/?id=8e30750a7bbf05386691b506313819c2aa493869

All you need to do is to move jetty-logging.xml to a line after
jetty.xml in your start.ini.

Again, thx for pointing this out!

Cheers,
Thomas

On 10/16/12 2:10 PM, Aaron Daubman wrote:

> another possibly important piece of context - in order to get the
> warning, you need to uncomment the server logging section in
> start.ini:
> ---snip---
> #===========================================================
> # Server logging.
> # The following configuration will redirect stderr and stdout
> # to file which is rolled over daily.
> #-----------------------------------------------------------
> etc/jetty-logging.xml
> #===========================================================
> ---snip--
>
> The warning is then the first line logged to the stderrout.log file:
> ---snip---
> 2012-10-16 08:08:20.039: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>
> ---snip---
>
> Without uncommenting the start.ini 'etc/jetty-logging.xml' option, I
> do not see this warning...
>
> Thanks again,
>        Aaron
>
>
> On Tue, Oct 16, 2012 at 8:04 AM, Aaron Daubman <[hidden email]> wrote:
>> 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 <[hidden email]> 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
>>>> [hidden email]
>>>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>>>
>>> _______________________________________________
>>> jetty-dev mailing list
>>> [hidden email]
>>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
> _______________________________________________
> jetty-dev mailing list
> [hidden email]
> https://dev.eclipse.org/mailman/listinfo/jetty-dev

_______________________________________________
jetty-dev mailing list
[hidden email]
https://dev.eclipse.org/mailman/listinfo/jetty-dev