Any startup script for IM server should proceed to next step (starting up dtwm) after htt's launch is completed.
(Doc ID 1020393.1)
Last updated on SEPTEMBER 09, 2019
Applies to:Solaris Operating System - Version 8.0 and later
On a system which has a fast CPU, it's possible that dtwm's starting up process is completed before XIM server's launch. That could cause dtwm to be hanging up during XIM request by dtwm. When htt starts, it forks XIM server 'htt_xbe'.htt_xbe takes a time to get ready for accepting XIM request. So if it is invoked with "&" as a background job, XIM request could be sent to htt_xbe before it's ready to accept it. As a result, dtwm could hang because of no reply from XIM server. Therefore, any startup script for IM server should proceed to the next step(starting up dtwm) after htt/htt_xbe's launch is completed. This is LE's startup issue. dtwm is not a problem.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!