In addition to the AM suggestion, you might want to check that /home/adm/teststart returns to command prompt once the application has started - otherwise, your ssh session will wait until the script does return to command prompt.

Typically, you might have the following in /home/adm/teststart to achieve the desired functionality (unless the application knows how to trun itself into a daemon):

.
.
# Start the app and return
nohup /usr/bin/some_app >/dev/null 2>&1 &
.
.
[download]

nohup(1) allows the application to carry on running once the controlling, in this case the login, session has terminated.