Thread Names for Sling Thread Support?

Hi all Sling Thread Support (aka Commons Threads) uses an underlying java.util.concurrent.ThreadPoolExecutor. By default this leads to thread names like "pool-1-thread-5". I was wondering whether we should change the thread names so it is clear they are being managed by Sling Thread Support.

Re: Thread Names for Sling Thread Support?

I’m in favour for changing the thread names to the format "Apache Sling - -Thread #” Konrad > On 01 Dec 2015, at 10:15, Julian Sedding wrote: > > Hi all > > Sling Thread Support (aka Commons Threads) uses an underlying > java.util.concurrent.ThreadPoolExecutor. By default

Re: Thread Names for Sling Thread Support?

It would be better to keep it short as it get used in logs/stacktrace etc. So something like "sling--" Chetan Mehrotra On Tue, Dec 1, 2015 at 2:48 PM, Konrad Windszus wrote: > I’m in favour for changing the thread names to the format "Apache Sling - > -Thread #” > Konrad > >

Re: Thread Names for Sling Thread Support?

On Tue, Dec 1, 2015 at 10:35 AM, Chetan Mehrotra wrote: > ...It would be better to keep it short as it get used in logs/stacktrace > etc. So something like "sling--" ... +1 -Bertrand

[jira] [Created] (SLING-5343) Meaningful thread names

Julian Sedding created SLING-5343: - Summary: Meaningful thread names Key: SLING-5343 URL: https://issues.apache.org/jira/browse/SLING-5343 Project: Sling Issue Type: Improvement

Re: Thread Names for Sling Thread Support?

Are we "allowed" to abbreviate "Apache Sling" to "sling"? The pool name can be set by configuration or by a consuming bundle, e.g. "Apache Sling Job Thread Pool" is set by the EventingThreadPool implementation. Therefore I lean to a mixed-case format (despite the fact that I normally prefer all

[jira] [Updated] (SLING-5343) Meaningful thread names

[ https://issues.apache.org/jira/browse/SLING-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-5343: -- Attachment: SLING-5343.patch Proposed patch. Let's wait which format we finally decide to use

Re: Thread Names for Sling Thread Support?

FYI, I created https://issues.apache.org/jira/browse/SLING-5343 with a proposed patch attached. Regards Julian On Tue, Dec 1, 2015 at 11:12 AM, Julian Sedding wrote: > Are we "allowed" to abbreviate "Apache Sling" to "sling"? > > The pool name can be set by configuration or

[jira] [Updated] (SLING-5026) Allow to set multiple validation error messages in one Validator

[ https://issues.apache.org/jira/browse/SLING-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-5026: --- Description: Currently each {{Validator}} can only set one error message through the String

Re: Thread Names for Sling Thread Support?

On Tue, Dec 1, 2015 at 11:12 AM, Julian Sedding wrote: > ...Are we "allowed" to abbreviate "Apache Sling" to "sling"?... For technical names yes, of course...if you see "sling" in a system that's running Apache Sling there's no possible confusion ;-) -Bertrand

RE: Thread Names for Sling Thread Support?

>It would be better to keep it short as it get used in logs/stacktrace >etc. So something like "sling--" +1

RE: Thread Names for Sling Thread Support?

+1 On Dec 1, 2015 5:55 AM, "Stefan Seifert" wrote: > >It would be better to keep it short as it get used in logs/stacktrace > >etc. So something like "sling--" > > +1 >

[jira] [Created] (SLING-5344) Request log format string %D

Jon Ekdahl created SLING-5344: - Summary: Request log format string %D Key: SLING-5344 URL: https://issues.apache.org/jira/browse/SLING-5344 Project: Sling Issue Type: Bug Components:

[jira] [Comment Edited] (SLING-5343) Meaningful thread names

[ https://issues.apache.org/jira/browse/SLING-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033660#comment-15033660 ] Julian Sedding edited comment on SLING-5343 at 12/1/15 2:39 PM: Fixed in

Re: Thread Names for Sling Thread Support?

Hi Bertrand I just added more tests to also cover the refactored priority logic (https://svn.apache.org/r1717440). Regards Julian On Tue, Dec 1, 2015 at 2:43 PM, Bertrand Delacretaz wrote: > Hi, > > On Tue, Dec 1, 2015 at 2:38 PM, Bertrand Delacretaz >

Re: Thread Names for Sling Thread Support?

On Tue, Dec 1, 2015 at 2:20 PM, Julian Sedding wrote: > Thanks for your inputs. I went ahead and committed the change > (https://svn.apache.org/r1717425). That's https://svn.apache.org/r1717424 actually. -Bertrand

[jira] [Assigned] (SLING-5345) StreamRendererServlet return no content-type

[ https://issues.apache.org/jira/browse/SLING-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso reassigned SLING-5345: Assignee: Antonio Sanso > StreamRendererServlet return no content-type >

Re: Thread Names for Sling Thread Support?

Julian Sedding wrote > Thanks for your inputs. I went ahead and committed the change > (https://svn.apache.org/r1717425). > > The format is "Sling - #". If someone has a > strong preference for an alternative, please go ahead and change it. > It uses String#format(). > Maybe I'm the only one,

[jira] [Commented] (SLING-5269) Sling Pipes IP clearance

[ https://issues.apache.org/jira/browse/SLING-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033680#comment-15033680 ] Bertrand Delacretaz commented on SLING-5269: Sorry for the delay, I have now created the IP

[jira] [Created] (SLING-5345) StreamRendererServlet return no content-type

Antonio Sanso created SLING-5345: Summary: StreamRendererServlet return no content-type Key: SLING-5345 URL: https://issues.apache.org/jira/browse/SLING-5345 Project: Sling Issue Type: Bug

Re: Thread Names for Sling Thread Support?

Hi, On Tue, Dec 1, 2015 at 2:38 PM, Bertrand Delacretaz wrote: > ...That's https://svn.apache.org/r1717424 actually... That revision includes changes to the ExtendedThreadFactory.convertPriority method, is that on purpose? Looks unrelated to the thread name change.

[jira] [Comment Edited] (SLING-5343) Meaningful thread names

[ https://issues.apache.org/jira/browse/SLING-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033660#comment-15033660 ] Julian Sedding edited comment on SLING-5343 at 12/1/15 1:17 PM: Fixed in

[jira] [Resolved] (SLING-5343) Meaningful thread names

[ https://issues.apache.org/jira/browse/SLING-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding resolved SLING-5343. --- Resolution: Fixed Fixed in [1717425|https://svn.apache.org/1717425]. I opted for the

[jira] [Updated] (SLING-5343) Meaningful thread names

[ https://issues.apache.org/jira/browse/SLING-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-5343: -- Fix Version/s: Commons Threads 3.2.4 > Meaningful thread names > --- > >

Re: Thread Names for Sling Thread Support?

Thanks for your inputs. I went ahead and committed the change (https://svn.apache.org/r1717425). The format is "Sling - #". If someone has a strong preference for an alternative, please go ahead and change it. It uses String#format(). Regards Julian On Tue, Dec 1, 2015 at 11:57 AM, Daniel Klco

[jira] [Comment Edited] (SLING-5343) Meaningful thread names

[ https://issues.apache.org/jira/browse/SLING-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033660#comment-15033660 ] Julian Sedding edited comment on SLING-5343 at 12/1/15 2:20 PM: Fixed in

Re: Thread Names for Sling Thread Support?

Thanks for catching the revision error. The priority related changes don't change behaviour. In order to de-clutter the constructor I moved the switch statement to the new convertPriority method and slightly simplified it at the same time. Regards Julian On Tue, Dec 1, 2015 at 2:43 PM, Bertrand

Re: Thread Names for Sling Thread Support?

On Tue, Dec 1, 2015 at 2:58 PM, Carsten Ziegeler wrote: > Julian Sedding wrote >> Thanks for your inputs. I went ahead and committed the change >> (https://svn.apache.org/r1717425). >> >> The format is "Sling - #". If someone has a >> strong preference for an alternative,

Re: Thread Names for Sling Thread Support?

On Tue, Dec 1, 2015 at 2:58 PM, Carsten Ziegeler wrote: > ...I would prefer a name without spaces. Makes > parsing the log files easier... +1 Maybe just replace spaces in pool names with a dash. -Bertrand