AS5400 - ISR Spin too long

Question

I have an AS5400-IS-M running 12.4(24)T1. I have 2 AS5X-FCs, each with 6 AS5X-PVDM2-64. I also have a CT3 card with a DS3 circuit coming into it. The bootloader is 12.3(12r)PI6b.
I am getting the following message every 4-30 seconds:
from Trunk(7): Framer Chip 2: ISR Spin too long!
I can find nothing from Google on this error. My T3 controller is down and the show isdn stat has the following for each of the T1s.
ISDN Serial7/0:1:23 interface
        dsl 0, interface ISDN Switchtype = primary-4ess : Primary D channel of nfas group 1
    Layer 1 Status:
        DEACTIVATED
    Layer 2 Status:
        TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED 
I am also seeing the following errors cycle repeatedly:
%DSX1-1-FIRMWARE_STOPPED: T1/E1 Firmware in slot 7 is not running
%DSX1-1-FIRMWARE_RUNNING: T1/E1 Firmware in slot 7 is running
If I get a loopback, then everything comes up and the ISR spin message goes away.
Does anyone have any ideas about what the cause of the "ISR Sping too long" error is?
Thank you!

Answer 1

Doc2text is native search client functionality used by portal, automation, ws, collab, publisher, etc. The portal components use it when indexing content to search server. It is installed seperately with each portal component. If you have multiple portal components installed on the same box, the ones that use Doc2text will share it from the common folder where it is located. Doc2text uses different libraries for the purpose of raw text extraction and processing, the processed information being sent in a proprietary format to the search server.
Doc2text is a processor heavy component as it needs to execute intensives tasks necessary to parse and extract raw data from such file formats as Microsoft Office and Adobe Acrobat. Some files may be more complex to extract data from and take longer for this task to complete.
The best way to increase performance would be to install the various portal components onto their own machines. For example not installing portal and automation on seperate servers. This way when you run a crawler job that imports files, the running of doc2text will not use cpu cycles on the portal web server.