I have an app sequenced in App-V that runs without issue, but the sequence does not terminate when the application is closed. It has an internal Java and javaw.exe keeps running after closing the application and the application remains In Use. I set TERMINATECHILDREN = TRUE in the OSD which usually resolves this sort of thing, but not this time. Javaw.exe keeps running after the app is closed and the application will only return to Idle state if I do an End Process on javaw.exe..

Looking at Process Explorer, I see two javaw.exe processes are created when the application launches. One of them terminates when the application is closed. The other has no visible windows and does not terminate when the application is closed.

Does anyone have any ideas on how to resolve this?

Update:
Found more interesting details about how this app works. When the app launches it appears in Process Explorer under explorer.exe > sfttray.exe > sftlp.exe, under that is the application's start.exe, under that is javaw.exe (which is a launcher/updater for the app), under that is another javaw.exe (which is the main user window for the app). What's interesting is that after launcher/updater window automatically closes, the sftlp.exe and start.exe terminates. I'm left with two javaw.exe processes that are no longer sub processes under explorer.exe, they are both under System Idle Process. When the application is closed, only one of these two javaw.exe process terminates. The other keeps the application in an In Use state.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
have you remembered to put the SUBSYSTEM VALUE parameter to "console" in the OSD file?
Java apps tend to freak out if you don't.
Answered 08/31/2011 by: pjgeutjens
Red Belt

Please log in to comment
0
Setting subsystem value to "console" caused the entire app to terminate when the launcher portion automatically closed, so I changed TERMINATECHILDREN back to False. That put me back in the same boat. When the launcher/updater closes I still end up with the two javaw.exe processes and only one of them closes when the application closes.
Not sure what approach to take at this point, I need to kill the other javaw.exe process when the other is closed but how would I trigger that when they're both started by a vendor's launcher? Hmmph.
Answered 08/31/2011 by: VikingLoki
Second Degree Brown Belt

Please log in to comment
0
Figured it out.
The app was intentionally leaving the 2nd javaw.exe process running for an autostart feature, where the app would automatically start at a particular time of day. Disabled that autostart feature within the application and the 2nd javaw.exe process no longer started.

Thanks for the pointer on SUBSYSTEM VALUE = Console value though!
Answered 08/31/2011 by: VikingLoki
Second Degree Brown Belt

Please log in to comment
0
Could you perhaps mention which application you were having the issue with?

Just so that if anyone else attempts to sequence the application they would receive a hit to this post when searching for the application by name.

Nice job on finding out the solution!

Thanks,

Dunnpy
Answered 08/31/2011 by: dunnpy
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity