[jboss-jira] [JBoss JIRA] Commented: (JBREM-674) add test case for client exiting correctly

[Ron Sigal (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBREM-674?page=comments#action_12351323 ] 
            
Ron Sigal commented on JBREM-674:
---------------------------------

A new unit test has been added to verify that a Remoting system shuts down properly without any wayward threads hanging it up..  The main classes are in org.jboss.test.remoting.shutdown, and the transport specific versions are in org.jboss.test.remoting.transport.<transport>.shutdown and org.jboss.test.remoting.transport.<transport>.ssl.shutdown. 

In the test, a server is started in one JVM and a client is started in another JVM.  To exercise as many threads as possible, client side connection verification, callback polling, and server side leasing are enabled.  Moreover, the test is run for each transport because some transports add their own threads.  There are actually two variations of the test:  in each of the two test methods, after the client has made an invocation and added a callback listener, it starts a long running thread.  In the first variation, testHangingClient(), the long running thread is not a daemon, and in the second variation, testClosingClient(), it is a daemon.  The first variation is just to demonstrate that the test code can catch a Remoting application failing to shut down in a timely manner, and the second variation is to demonstrate that a normal Remoting application does in fact shut down as it should.

> add test case for client exiting correctly
> ------------------------------------------
>
>                 Key: JBREM-674
>                 URL: http://jira.jboss.com/jira/browse/JBREM-674
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: general
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For:  2.2.0.Beta1 (Bluto)
>
>
> Per Tim Fox:
> Suggestion:
> Create a test in the remoting test suite which creates a remoting client in it's own vm, does some stuff then tries to exit cleanly. If it can't then the test fails.
> This would catch any similar issues in the future if people add timers without remembering to make them daemon.
> (We're going to add a test in the JBM test suite anyway for this.)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira