StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19302715
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-10-10T17:48:15.963
FavoriteCount
0
LastActivityDate
2013-10-10T17:48:15.963
LastEditDate
LastEditorUserId
0
OwnerUserId
1264321
ParentId
19293827
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
I dont know if this fits your needs but it actually worked for my app. The listener is called at application start, if it is declared in your web.xml: <pre><code><listener> <listener-class>your.package.TestServletListener</listener-class> </listener> </code></pre> There you can do testing and call the ShutdownThread if one fails. It will connect to Tomcats shutdown port and send the shutdown command as a String: <pre><code>public class TestServletListener implements ServletContextListener { @Override public void contextInitialized(ServletContextEvent arg0) { System.out.println("Starting app, running 5 tests ..."); // do tests ... for (int i = 0; i < 5; i++) { System.out.println("testing ... " + i); waitFor(1000); } // If a test failed call: System.out.println("test failed!"); new ShutdownTask().start(); } @Override public void contextDestroyed(ServletContextEvent arg0) { System.out.print("Stopping app, cleaning up (takes 3 sec) ... "); waitFor(3000); System.out.println("done"); } private void waitFor(int i) { try { Thread.sleep(i); } catch (InterruptedException e) { e.printStackTrace(); } } class ShutdownTask extends Thread { @Override public void run() { try { Socket s = new Socket("127.0.0.1", 8015); PrintStream os = new PrintStream(s.getOutputStream()); os.println("shutdown"); s.close(); System.out.println("Shutting down server ..."); } catch (IOException e) { e.printStackTrace(); } } } } </code></pre> You need to make sure that the shutdown port and shutdown command are in sync with your Tomcats server.xml: <pre><code>... <Server port="8015" shutdown="shutdown"> ... </code></pre> For example, you could pass them as context parameters in your web.xml. Like System.exit(...) this is not going to work (without further config) if Tomcat is running with a SecurityManager.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POShutdown Tomcat instance using Java
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USStefan
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POShutdown Tomcat instance using 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COYes, that seems like something I could use - didn't know the listener could be used like that, thanks!
 singulars
 PostPostId
 PO
 UserUserId
 USKingTravisG

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.