Indexing and Search Service JMQ Consumer Log Messages

Skip to end of metadata
Go to start of metadata

Indexing and Search Service JMQ Consumer Log Messages

This document provides a list of sample JMQ Consumer log messages in alphabetical order and a description of what each log message means.

INFO level

INFO: Account user1@mailhost.example.com is active on Mon Apr 06 00:00:14 PDT 2009, processing event generated on Mon Apr 06 00:00:14 PDT 2009 with sequence number 1061, time between generate and submit to index svc is 108ms.

This message indicates that account user1 is in Active state (as opposed to Bootstrapping or Inactive), so the real-time event 1061 has been passed to Index Services for indexing. The time between the event being generated on Messaging Server and it being passed to Index Services was 108ms (this is dependent on the Messaging Server and the ISS server having clocks which are in sync).

INFO: Event queue: user1@mailhost.example.com:1 user2@mailhost.example.com:5

The accounts user1 and user2 have queued up events (1 for user1 and 5 for user2). This can happen if the accounts are not in Active state or if a flood of events have been received for the user (events are processed for each user in order).

INFO: Event queue: none

This regularly displayed log message indicates that there are no events queued up for processing. This is the normal state, assuming that all accounts are Active.

INFO: Finished indexing event for account user1@mailhost.example.com with sequence number 10030, time between submit to and return from index svc is 243ms.

This message indicates that Index Services has returned successfully from a submitted real-time event. The total time elapsed between submitting the event from JMQ Consumer to Index Services and the successful return was 243ms.

INFO: JMSType: ChangeFlag (UID 102142,102146:102149,102153) Op 1-> Sys 0 PerUser 0

This message indicates that a ChangeFlag event was received for UIDs 102142, 102146-102149 and 102153.

INFO: JMSType: ChangeFlag (UID 110616:110617,110619,110622:110623,110627) Op 1-> Sys 0 PerUser 3

This message indicates that a ChangeFlag event was received for UIDs 110616-110617, 110619, 110622-110623, and 110627.

INFO: JMSType: ChangeFlag (UID 110621) Op 1-> Sys 0 PerUser 1

This message indicates that a ChangeFlag event was received for UIDs 110621.

INFO: JMSType: ChangeFlag (UID 110635) Op 2-> Sys 0 PerUser 0

This message indicates that a ChangeFlag event was received for UIDs 110635.

INFO: JMSType: Copy

This message indicates that a Copy event was received.

INFO: JMSType: Create

This message indicates that a Create event (new folder) was received.

INFO: JMSType: ExpungeMsg

This message indicates that an ExpungeMsg event was received.

INFO: JMSType: NewMsg

This message indicates that a NewMsg event (new message via SMTP/LMTP) was received.

INFO: JMSType: UpdateMsg

This message indicates that a UpdateMsg event (new message via IMAP) was received. This is frequently a new message to the Sent or Drafts folder.

INFO: Queuing event for user1@mailhost.example.com generated on Fri Apr 03 23:33:08 PDT 2009, with sequence number 79 on Fri Apr 03 23:33:08 PDT 2009

This message indicates that an event was received for user1 and was generated at 23:33:08 on Messaging Server.

INFO: Received event ChangeFlag generated on Fri Apr 03 21:27:01 PDT 2009 with sequence number 13 uidValidity is 1198003994 operation is 1 uidlist is 435190 peruser_flags is 0 system_flags is 0 user_flags1 is 32 user_flags2 is null user_flags3 is null URL is imap://user1@mailhost.example.com/INBOX;UIDVALIDITY=1198003994/;UID=null

This message indicates that a ChangeFlag event was received for UID 435190, folder INBOX, user user1.

INFO: Received event ChangeFlag generated on Mon Apr 06 06:36:35 PDT 2009 with sequence number 2045 uidValidity is 1198002898 operation is 1 uidlist is 620857:620862,620865,620874,620876,620883:620884 peruser_flags is 3 system_flags is 0 user_flags1 is null user_flags2 is null user_flags3 is null URL is imap://user1@mailhost.example.com/INBOX;UIDVALIDITY=1198002898/;UID=null

This message indicates that a ChangeFlag event was received for UIDs 620857-620862, 620865, 620874, 620876, 620883-620884, folder INBOX, user user1.

INFO: Received event Copy generated on Mon Apr 06 06:36:34 PDT 2009 with sequence number 2038 from-username is user1 from-foldername is INBOX to-username is user1 to-foldername is mac-users from-uidValidity is 1198002898 to-uidValidity is 1128698094 from-uidlist is 20804,620807,620830:620837,620843,620850:620851,620863,620867,620870:620873,620879:620880,620882,620885:620887 to-uidlist is 58001:58025 URL is imap://user1@mailhost.example.com/mac-users;UIDVALIDITY=1128698094/;UID=null

This message indicates that a Copy event was received for user1, from the INBOX to the mac-users folder.

INFO: Received event Create generated on Mon Apr 06 11:05:20 PDT 2009 with sequence number 3444 URL is imap://user1@mailhost.example.com/new-folder;UIDVALIDITY=1239041120/;UID=null

This message indicates that a Create event was received for user1, creating the new-folder folder.

INFO: Received event ExpungeMsg generated on Mon Apr 06 06:24:19 PDT 2009 with sequence number 2015 uidValidity is 962866757 uidlist is 612235:612238,612240,612242:612243,612245:612256 URL is imap://user1@mailhost.example.com/INBOX;UIDVALIDITY=962866757/;UID=null

This message indicates that the following UIDs were expunged from user1's INBOX: 12235-612238,612240,612242-612243,612245-612256.

INFO: Received event NewMsg generated on Fri Apr 03 21:24:35 PDT 2009 with sequence number 4 (size h:6526 e:10131 t:10131 - Using text) URL is imap://user1@mailhost.example.com/INBOX;UIDVALIDITY=961021076/;UID=51990

This message indicates that a NewMsg event was received for user1, folder INBOX, UID 51990. Header size was 6526 bytes, email size was 10131, matching the text size of the event, so the email was completely contained within the text of the event.

INFO: Received event NewMsg generated on Fri Apr 03 23:13:24 PDT 2009 with sequence number 77 (size h:8348 e:435411 t:270492 - Using imap) URL is imap://user1@mailhost.example.com/INBOX;UIDVALIDITY=1170916439/;UID=39376

This message indicates that a NewMsg event was received for user1, folder INBOX, UID 39376. Header size was 8348 bytes, email size was 435411 bytes, so larger than the text size of the event, which was 270492, so the email was not completely contained within the text of the event and the email is fetched instead by using IMAP.

INFO: Received event UpdateMsg generated on Fri Apr 03 21:38:32 PDT 2009 with sequence number 28 (size h:350 e:469 t:469 - Using text) URL is imap://user1@mailhost.example.com/Sent;UIDVALIDITY=1002212041/;UID=14555

This message indicates that an UpdateMsg event was received for user1, folder Sent, UID 14555. Header size was 350 bytes, email size was 469, matching the text size of the event, so the email was completely contained within the text of the event.

INFO: Received event UpdateMsg generated on Mon Apr 06 21:23:45 PDT 2009 with sequence number 7132 (size h:654 e:962626 t:262798 - Using imap) URL is imap://user1@mailhost.example.com/Sent;UIDVALIDITY=956794653/;UID=14480

This message indicates that an UpdateMsg event was received for user1, folder Sent, UID 14480. Header size was 654 bytes, email size was 962626 bytes, so larger than the text size of the event, which was 262798, so the email was not completely contained within the text of the event and the email is fetched instead by using IMAP.

INFO: Set account user1@mailhost.example.com state to A

This indicates that user1 has been set to Active state. This message is generated when the account finishes bootstrapping.

INFO: Set account user1@mailhost.example.com state to B

This indicates that user1 has been set to Bootstrapping state. This message is generated when the account starts bootstrapping.

INFO: Set account user1@mailhost.example.com state to I

This indicates that user1 has been set to Inactive state. This message is generated when the account is synced by using the issadmin.sh --checkaccount --sync command.

INFO: Total: 102 Users: 32 Total active: 2 Active Users: 1 Total inactive: 3 Inactive Users: 2 Total bootstrap: 97 Bootstrap Users: 29

This is the last line of the "printQueues" messages in the JMQ log for checking the account queues. It summarizes the number of events in the backlog for all accounts in each of the account states. Thus:

Total of all events in backlog:    102   over 32  users

Total events from Active users:      2   over  1  user
Total events from Inactive users:    3   over  2  users
Total events from Bootstrap users:  97   over 29  users

So all the "Total" fields add up to the first value (2+3+97=102)
and all the "User" fields add up to the second value (1+2+29=32).

WARNING level

WARNING: Account user1@mailhost.example.com doesn't exist, will not process event with sequence number 11

This message indicates that an event was received for an account that does not exist on the ISS server.

WARNING: [I500]: Caught JVM Exception: java.net.ConnectException: Connection refused

This message indicates that a connection could not be made to the IMQ broker. Check that the mail.imq setting is correct and that the IMQ broker is running.

WARNING: Connection problem: com.sun.messaging.jms.JMSSecurityException: [C4060]: Login failed: user=jmquser, broker=mailhost.example.com:7676(46078)

This message indicates that the setting for mail.imq.user or {mail.imq.password}} is incorrect. If mail.imq.password is incorrect and must be changed, you might also need to edit the value stored in the mail.imq.passfile file.

WARNING: Exception while indexing, sequence number: 19006 com.sun.comms.iss.common.IssException: javax.mail.internet.ParseException : Expected parameter name, got "filenameMatrix.odt" Exception while processing: Message UID : 522565 On Host : mailhost.example.com For User : user1 In Folder : INBOX

This message indicates that an error occurred during indexing of a message.

WARNING: Shutdown in progress, no requests will be processed...

This message indicates that a service shutdown is underway.

WARNING: Starting up. Listening to Queue INDEXMS on mailhost.example.com:7676

This is a startup message indicating that JMQ consumer has connected to the broker at mailhost.example.com, port 7676, and is listening to the Queue destination named INDEXMS.

WARNING: Unable to obtain JMS objects to send message response: [SEND_REPLY(9)] [C4036]: A broker error occurred. :[500] com.sun.messaging.jmq.jmsserver.util.BrokerException: Destination Q:temporary_destination:__queue_10.5.185.151_46656_1 could not be found in the store user=misoadmin, broker=isshost.example.com:7676(62279)

This message indicates that account state listener could not send a response back to the producer through the temporary queue. You can ignore this error as it has no impact on functionality.

Labels:
indexsearchservice indexsearchservice Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


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.