StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13625548
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-11-29T12:10:41.387
FavoriteCount
0
LastActivityDate
2012-11-29T12:10:41.387
LastEditDate
LastEditorUserId
0
OwnerUserId
1831987
ParentId
13624509
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
If you are catching <code>InterruptedException</code> anywhere inside the for-loop, remove all of those try/catch blocks and instead have a single try/catch which surrounds the entire for-loop. This will allow the entire for-loop to cease when you interrupt its thread. Similarly, if you are catching <code>IOException</code>, catch <code>InterruptedIOException</code> and <code>ClosedByInterruptException</code> first. Move those catch blocks outside of the for-loop. (The compiler won't allow it if you are catching <code>IOException</code> internally, since there would be nothing to catch at the outer level.) If the blocking calls are not throwing <code>InterruptedException</code>, you will need to add a check after each of them, like this: <pre><code>if (Thread.interrupted()) { break; } </code></pre> If you have many levels of loops, you might want to add a label so you can directly exit from that first "instructions" loop, without the need for adding lots of flag variables: <pre><code>instructions: for ( ... ) { for ( ... ) { doLongOperation(); if (Thread.interrupted()) { break instructions; } } } </code></pre> Either way, once interrupts are handled, you can have a background thread interrupt your first for-loop: <pre><code>final Thread instructionsThread = Thread.currentThread(); Runnable interruptor = new Runnable() { public void run() { instructionsThread.interrupt(); } }; ScheduledExecutorService executor = Executors.newSingleThreadScheduledExecutor(); executor.schedule(interruptor, 5, TimeUnit.MINUTES); // instructions try { for ( ... ) { } } catch (InterruptedException | InterruptedIOException | ClosedByInterruptException e) { logger.log(Level.FINE, "First loop timed out.", e); } finally { executor.shutdown(); } // instructions2 </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POJava timeout a set of instructions
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USVGR
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. 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.