Unrecognized attachment types are classified under the category "other" and are not saved to the attachment store. This message is indicating that an attachment with name "smime.p7s" in UID 7256 of Folder "To Me", user user4 was found, but not saved.

Message in uid 5339, folder ME for user user148 contains a large plain text attachment file. This log message is printed out on every 1MB that was read from the file. The maximum size that will be indexed defaults to 25MB and is configurable.

Seen during the bootstrap of an account, this indicates a new record containing flag information for folder cy2002 for user user24@mailhost.example.com needed to be created.

FINE: Waiting 300000 ms for ThreadPool termination:call#6103

Seen when multiple threads are used for bootstrapping, or during issadmin.sh --checkacount or other processing, this message is generated when the thread pool has completed submitting all its tasks, and is waiting for them all to complete.

This message is indicating that there was no thumbnail image created for file Customers.sxc, found in uid 8579, folder ARCHIVE04, user user99, default icon OOWriter.png will be used as thumbnail image for this file. This message will not be displayed if the attachment file is of MS document type, when default icon is always used.

INFO level

This message may appear when processing email attachments of content-type: text/html. It indicates a problem with the "charset=" field in the html meta specifier was corrected, allowing the text to be processed normally. This message is expected to be obsoleted and not appear in an upcoming release.

This message may appear when processing email attachments of content-type: text/html. It indicates a problem with the "charset=" field in the html meta specifier was corrected, allowing the text to be processed normally. This message is expected to be obsoleted and not appear in an upcoming release.

This message may appear when processing email attachments of content-type: text/html. It indicates a problem with the "charset=" field in the html meta specifier was corrected, allowing the text to be processed normally. This message is expected to be obsoleted and not appear in an upcoming release.

This message may appear when processing email attachments of content-type: text/html. It indicates a problem with the "charset=" field in the html meta specifier was corrected, allowing the text to be processed normally. This message is expected to be obsoleted and not appear in an upcoming release.

INFO: Begin checking write.lock files.

Seen when starting indexing service, a background thread is running to check leftover write.lock files in the index directory which may cause index corruption.

INFO: End checking write.lock files.

Seen when starting indexing service, a background thread is finished to check leftover write.lock files in the index directory which may cause index corruption.

INFO: Initializing account state records.

Seen when starting services, this indicates the services are initializing account state records from dIndex.

INFO: Initializing account transition date records.

Seen when starting services, this indicates the services are initializing account transition date records from dIndex.

Seen when using the issadmin.sh --checkaccount or --checkfolder --detail status commands, this indicates the time it took to find the indicated number of the status messages for the account or folder. The "null" folderId indicates the search was done for the entire account, not just one folder.

INFO: AccountManager.setAccountState: group index directories 00/04/index4_meta and 00/04/index4_content have been optimized

Seen when using the issadmin.sh --setstate O command, this indicates which directories are being optimized for the account.

INFO: All account state notification failure, server not running. This failure is only expected when using svc_control.sh to stop/start services, otherwise check if JMQConsumer is working.

Index service attempts to send out all account state notification at start up, to sync up with JMQ Consumer, but JMQ Consumer is not running. This is usually expected during install or services restart using svc_control.sh, because JMQ Consumer is started after index service.

INFO: Clean up before shutdown...

This is a normal shutdown message indicating cleanup up of resources before completely shutting down index service.

Seen during the update of email flags, this message indicates how often flag data was written to the index, and the size of the largest string written thus far. If many such messages appear, especially in a short period of time, this indicates frequent changes to the flag data, and may show a potential performance problem that should be reported.

Seen when messages are added or deleted from an account, this message shows the total number of the meta/content/attachment records that the indicated folder of the account now has in the index. (Note: the last number, the number of attachments, is not always accurate, so it should be ignored for now.)

In the attempt to find a suitable converter to process an attachment, the same JPEGConverter was determined in retry. This means the first try using JPEGConverter most likely had an error that was not caused by choosing the wrong converter. Index service will report the previous error and continue.

In the attempt to find a suitable converter to process an attachment, the same MSExcelConverter was determined in retry. This means the first try using MSExcelConverter most likely had an error that was not caused by choosing the wrong converter. Index service will report the previous error and continue.

In the attempt to find a suitable converter to process an attachment, the same MSWordConverter was determined in retry. This means the first try using MSWordConverter most likely had an error that was not caused by choosing the wrong converter. Index service will report the previous error and continue.

In the attempt to find a suitable converter to process an attachment, the same PDFConverter was determined in retry. This means the first try using PDFConverter most likely had an error that was not caused by choosing the wrong converter. Index service will report the previous error and continue.

Tracks the current memory usage:
Free memory is the amount of free memory (in MB) in the JVM.
Total memory is the amount of memory (in MB) currently in the JVM.
Max memory is the max amount of memory (in MB) the JVM will attempt to use.

INFO: Processing user user24: 11884 Messages in Folder: INBOX

This message is displayed during bootstrapping. It indicates that bootstrapping of INBOX has commenced and there are 11884 messages in the folder.

INFO: Received event on account: user1@mailhost.example.com with sequence number 10136

Index service received a real time event request from JMQ Consumer, the sequence number was assigned by the JMQ Consumer.

In the attempt to find a suitable converter to process attachment file 0100000005100986.pdf, found in uid 434768, folder INBOX for user user24, the first try found an error which triggers a retry using different converter.

INFO: Sent notification of all account state.

Account state information for all accounts was posted to JMQ Consumer – this may happen if JMQ Consumer restarts.

INFO: SharedWriter.close: optimizing index:/dIndex Time: 101ms

This message indicates the time to complete optimizing the dIndex. Various commands can cause one or more such message, including bootstrapping. The time is proportional to the the size, complexity, and amount of change that has occurred to the dIndex. Unusually long times, on the order of over 10 minutes, may indicate a performance bottleneck, and should be investigated. Also, if such messages for the same index appear very frequently, tuning of the store may be necessary.

This message indicates the time to complete optimizing the 61st group's content index. Various commands can cause one or more such message, including bootstrapping and issadmin.sh --setstate O commands. The time is proportional to the the size, complexity, and amount of change that has occurred to the accounts in the index directories. Unusually long times, on the order of over 10 minutes, may indicate a performance bottleneck, and should be investigated. Also, if such messages for the same index appear very frequently, tuning of the store may be necessary.

INFO: SharedWriter.close: optimizing index:/index61_meta Time: 3278ms

This message indicates the time to complete optimizing the 61st group's meta index. Various commands can cause one or more such message, including bootstrapping and issadmin.sh --setstate O commands. The time is proportional to the the size, complexity, and amount of change that has occurred to the accounts in the index directories. Unusually long times, on the order of over 10 minutes, may indicate a performance bottleneck, and should be investigated. Also, if such messages for the same index appear very frequently, tuning of the store may be necessary.

INFO: Total number of messages in folder is 33984; folderName is INBOX

Seen during bootstrapping of an account, this message shows the current number of messages found (33984) in the indicated folder (INBOX) at the current time.

Index service was not able to determine the file mime type while trying to find a suitable converter, use default converter for mime type APPLICATION/OCTET-STREAM for file found in UID 14459, folder CY2003, user user24.

Index service was not able to determine the file mime type while trying to find a suitable converter, use default converter for mime type TEXT/PLAIN for file found in UID 7088, folder dev, user user111.

Seen at the end of processing a change to email flags, this message shows the total time it took (60ms) to modify the flags of the list of emails in the indicated folder.

INFO: deleteUidList: MetaDocs deleted: 113 content: 113

Seen at the end of processing commands which delete messages from the index, this message shows the number of records in the meta data and content index directories deleted for an account. This gives some idea of the amount of change to the index; the two numbers may not be the same because of sharing of the content records when copying of emails between folders has occurred in the account.

INFO: endElement(): not adding invalid matcher '320 kBits'

Messages of this type can be ignored and may be removed from a future release. They are displayed when attachment processing and the MIME detection library is started.

Seen during the issadmin.sh --checkaccount or --checkfolder command, this message indicates the count of the attachments in folder named Bugs does not match what was expected in the index. Because the method used to count attachments is not fully functional, this kind of message is not correct and should be ignored.

WARNING: AccountManager.getAccount: no such account (account could not be assigned to group) host=mailhost.example.com user=user0 searching: true acctId: xmailhostzexamplezcomxuser0x

Seen when a failure has been detected, this message indicates that the requested account could not be found in the group it should have. Either the issadmin.sh --group value has an error, or the account does not exist in the store.

WARNING: [I500]: Caught JVM Exception: java.io.EOFException

This may be logged if the credentials to the ISS IMQ broker are not correct. Check the settings of iss.imq.user and iss.imq.password. If iss.imq.password must be changed, you may also need to change the value stored at the iss.imq.passfile file.

This message is indicating an error has occurred while converting PDF file Download_Anaylsis.pdf, found in uid 480841, folder INBOX, user user24, into thumbnail image, a default PDF icon will be used as thumbnail image for this file.

This message is indicating an error has occurred while converting PDF file 2P.pdf, found in uid 373, folder ARCHIVE04, user user99, into thumbnail image, a default PDF icon will be used as thumbnail image for this file.

This message is indicating the third party library is not able to convert PDF file WAP.pdf, found in uid 5533, folder ARCHIVE00, user user99, into thumbnail image, a default PDF icon will be used as thumbnail image for this file.

This message is indicating an error has occurred while converting PDF file 0090093471.pdf, found in uid 8745, folder CY2006, user user24, into thumbnail image, a default PDF icon will be used as thumbnail image for this file.

This message is indicating an error has occurred while converting PDF file Platinum.pdf, found in uid 17505, folder Archive/1998, user user24, into thumbnail image, a default PDF icon will be used as thumbnail image for this file.

This message is indicating an error has occurred while converting PDF file OMR-1.pdf, found in uid 3835, folder ARCHIVE05, user user99, into thumbnail image, a default PDF icon will be used as thumbnail image for this file.

This message is indicating an error has occurred while converting PDF file RESUME.pdf, found in uid 6445, folder dev, user user111, into thumbnail image, a default PDF icon will be used as thumbnail image for this file.

This message is indicating an error has occurred while converting PDF file SignUp.pdf, found in uid 7391, folder INBOX, user user112, into thumbnail image, a default PDF icon will be used as thumbnail image for this file.

This message is indicating an error has occurred while converting PDF file Special-2009D.pdf, found in uid 39760, folder INBOX, user user1, into thumbnail image, a default PDF icon will be used as thumbnail image for this file.

This message is indicating the third party library is not able to convert PDF file feature-list.pdf, found in uid 14462, folder Sent, user user8, into thumbnail image, a default PDF icon will be used as thumbnail image for this file.

This message is indicating an error has occurred while converting JPEG file Bg.jpg, found in uid 43513, folder INBOX, user user56, into thumbnail image, a default JPEG icon will be used as thumbnail image for this file.

This message indicates an error during thumbnail creation for file C:DOCUME~1saraLOCALS~1TempnsmailP4.jpeg, found in uid 4051, folder CY2000, user user24, a default icon will be used as thumbnail image for this file.

SEVERE level

This may be logged if the credentials to the ISS IMQ broker are not correct. Check the settings of iss.imq.user and iss.imq.password. If iss.imq.password must be changed, you may also need to change the value stored at the iss.imq.passfile file.

SEVERE: Found /var/iss/index/store/01/24/wrtie.lock, delete

A leftover write.lock was detected and deleted. This may have been a corruption to the index in directory /var/iss/index/store/01/24/.

The individuals who post here are part of the extended Oracle community
and they might not be employed or in any way formally affiliated with Oracle.
The opinions expressed here are their own, are not necessarily reviewed in
advance by anyone but the individual authors, and neither Oracle nor any
other party necessarily agrees with them.