StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16918082
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-06-04T12:38:22.410
FavoriteCount
0
LastActivityDate
2013-06-04T12:43:41.687
LastEditDate
2013-06-04T12:43:41.687
LastEditorUserId
829571
OwnerUserId
829571
ParentId
16917536
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
The problem you observe is probably due to how <code>System.out.println</code> works. It is a synchronized method. So a likely explanation is: <ul> <li>when calling <code>System.out.print(".");</code> after <code>t.interrupt();</code>, your main thread acquires the lock to print</li> <li>before the lock is released, worker threads arrive at <code>System.out.println(Thread.currentThread().getName() + ":" + i);</code> and wait for the lock</li> <li>when the main thread releases the lock, all the worker threads that were waiting print their progress.</li> <li>the main thread arrives at <code>System.out.print(".");</code> again and has to wait for the print lock to be available, etc.</li> </ul> Regarding the fact that you see more prints from the worker threads after <code>"All Done"</code> is printed: you only <code>join</code> for 10 ms, so it is possible that it is not enough and a thread is not finished within 10ms of being interrupted. If you just use <code>join()</code> you should not see that any longer. Example of Worker class that reproduces the behaviour you observe: <pre><code>class Walker implements Runnable { public void run() { for (int i = 0;; i++) { try { Thread.sleep(100); } catch (InterruptedException ex) { //do not respond to interruption too quickly on purpose try { Thread.sleep(1000); } catch (InterruptedException e) {} Thread.currentThread().interrupt(); } System.out.println(Thread.currentThread().getName() + ":" + i); if (Thread.interrupted()) { break; } } } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to (reliably) interrupt threads form the main thread after a specific amount of time in Java?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USassylias
UserOwnerUserId
1. USassylias
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to (reliably) interrupt threads form the main thread after a specific amount of time in Java?
 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
CommentsPostId
1. This table or related slice is empty.

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.