Something else to try: See what happens when you launch your client using the appclient script. Much - but not quite all - of the logic is the same as in a Java Web Start launch and it's easier to debug the client with the appclient command:
Either redeploy your app using
asadmin deploy --retrieve localDir ...
or
asadmin get-client-stubs --appname ${nameOfApp} localDir
Then use
appclient -agentlib:jdwp=transport=dt_socket,address=8118,server=y,suspend=y localDir/${nameOfApp}Client.jar args-to-pass-to-client
Of course you can use any port (8118) you want and any local directory you want. The nameOfApp is usually the name part of the EAR you deployed unless you specified --name on the deploy command.
Anyway, see if the double-prompting occurs launching with appclient. That'll help point to where we need to look next.
- Tim
[Message sent by forum member 'tjquinn']
http://forums.java.net/jive/thread.jspa?messageID=477782