nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

servletd.log and servletd_out.log

nirjari

servletd.log is used to check errors in main screen (which comes from Tomcat) , whats servletd_out.log used for ?

thanks

Find more posts tagged with

Comments

mart2001

I usually check for custom workflow url external task errors, or when you get the message that says servlet engine can't connect to proxy server. Also for when the UI doesn't come up.

nipper

servletd_out takes everything that would have normally gone to STDOUT and saves it to the log. The data is quite varied, a lot of debug information, Jave stack dumps, etc.

Reji Varghese

Also contains, any incorrect attempt to login.

If the customized UI build has any errors, its logged in here.

mart2001

Also, if you turn on base loggers, it would all go into serlvetd_out.log too.

nirjari

thanks.

I thiought external tasks and workflow errors are logged in iwutild.log and iwutild_cmdout.log files.

Then what are these iwutild.log and iwutild_cmdout.log used for ?

thansk

nipper

utilcmd takes WFT logs (basically anything kicked off with perl) as well as TPL generated errors/warning. ANything that is perl based needs to be run by the util daemon and will put debug information in utilcmd log. util.log maintains little useful information

SendNullValuesToBottomOfCrosstab.zip

vpatel

thanks.

I thiought external tasks and workflow errors are logged in iwutild.log and iwutild_cmdout.log files.

Then what are these iwutild.log and iwutild_cmdout.log used for ?

thansk

External tasks and workflow erros could be logged differently for different TS instances based on the TS configuration, External task configuration, Workflow configuration, etc. For example, if your External task is written in Java and you are using *default* logging then more than likely it is getting logged in servlet_d.log. Alternatively, if you configure the log4j you could have it logging in a custom log file. There are various possibilities. Bottom line is that you have to understand and analyze your own environment's configurations. Of course there are some base logging that happens that you may not have ability to configure and info around those log files could be gathered througg TS product guides and / or training.