StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16086871
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-04-18T15:19:53.900
FavoriteCount
0
LastActivityDate
2013-04-18T15:26:39.850
LastEditDate
2013-04-18T15:26:39.850
LastEditorUserId
56285
OwnerUserId
56285
ParentId
16083780
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
<h2>What solved it for me (a Spring, not Jetty issue)</h2> I was wrong when I wrote this in the question: <blockquote> It looks like Jetty by default uses just one thread. </blockquote> This turned out to be purely a Spring issue. In applicationContext.xml, I changed <pre><code><task:annotation-driven/> </code></pre> into <pre><code><task:annotation-driven scheduler="scheduler-pool"/> <task:scheduler id="scheduler-pool" pool-size="5"/> </code></pre> ... and different <code>@Scheduled</code> tasks now happily run in separate threads like <code>scheduler-pool-1</code> or <code>scheduler-pool-3</code>. <h2>How to tweak Jetty threadpool configs (with jetty-runner)</h2> (Before I realised my problem was not a Jetty issue, I had already looked into how Jetty threadpools are configured. Documenting that here; maybe it is useful to someone.) Create a <a href="http://wiki.eclipse.org/Jetty/Reference/jetty.xml"><code>jetty.xml</code> config file</a> (somewhere like <code>src/main/resources</code> so that it gets copied to the compilation target dir), and customise it to your liking. Example (probably a poor one): <pre><code><?xml version="1.0"?>  <Configure id="Server" class="org.eclipse.jetty.server.Server"> <Set name="ThreadPool"> <New class="org.eclipse.jetty.util.thread.QueuedThreadPool"> <Set name="minThreads">3</Set> <Set name="maxThreads">5</Set> </New> </Set> </Configure> </code></pre> Then, tell jetty-runner to use that config file with the <code>--config</code> switch. So for example in Heroku's <code>Procfile</code>, add <code>--config target/classes/jetty.xml</code>: <pre><code>web: java $JAVA_OPTS -jar target/dependency/jetty-runner.jar --config target/classes/jetty.xml --port $PORT target/*.war </code></pre> <hr> If you also happen to be using jetty-maven-plugin, you can tell it to use your custom Jetty config by adding this under <code><configuration></code> in <code>pom.xml</code>: <pre><code><jettyConfig>target/classes/jetty.xml</jettyConfig> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to increase Jetty threadpool size with jetty-runner on Heroku?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJonik
UserOwnerUserId
1. USJonik
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to increase Jetty threadpool size with jetty-runner on Heroku?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThe default size of max connections in the thread pool is just 1? Really?
 singulars
 PostPostId
 PO
 UserUserId
 USLuke
2. CO@Luke, you can find default min/max threadpool size in /etc/jetty.xml relative to jetty directory. 10/200 are the default values
 singulars
 PostPostId
 PO
 UserUserId
 USHeM01

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.