unique iwserver process identifier

maheshyogi

Is there any unique iwserver process identifier that could be added to the timestamp in each line custom log to separate the gush of messages? The ID might be internal process ID. I would like to know if java has access to internal cssdk process number to add Id number to custom log file.I guess TeamSite and ControlHub have the internal id.

Example:
'Unable to change ownership of Task XX,****,**** - [Task Name]: com.interwoven.cssdk.filesys.CSReadOnlyFileSystemException - Filesystem is read-only or archive is frozen'


XX,****,**** - is the Task ID, Even you can see the ID in Hex if you do cmd on iwstat I think.

Please help to me on this to update the log with the ID.

Teamsite Environment: TS 6.7.2

Adam Stoller

Is there any unique iwserver process identifier that could be added to the timestamp in each line custom log to separate the gush of messages? The ID might be internal process ID. I would like to know if java has access to internal cssdk process number to add Id number to custom log file.I guess TeamSite and ControlHub have the internal id. Example: 'Unable to change ownership of Task XX,****,**** - [Task Name]: com.interwoven.cssdk.filesys.CSReadOnlyFileSystemException - Filesystem is read-only or archive is frozen' XX,****,**** - is the Task ID, Even you can see the ID in Hex if you do cmd on iwstat I think. Please help to me on this to update the log with the ID. Teamsite Environment: TS 6.7.2

If you are writing custom code, then you can write custom diagnostic statements in that code and have it log whatever you like.

I do this in my custom code (both Perl [Log::Log4perl] and Java [org.apache.log4j]) and generally make sure to (a) have a decent timestamp before each log entry and (b) include the jobid and taskid [as integers] in each log entry.

Unfortunately, many of the OOTB diagnostic messages fail to have one, the other, or both of those pieces of information - and all you can do then is try to file a bug for it with Support.