Should I concern about the FNRPE2131090138E RPC token timeout errors in the IBM FileNet Process Engine log

Technote (FAQ)


Question

The IBM FileNet Process Engine log (pesvr_system.log) captured the following error messages:

2013/06/19 06:04:24.116-0400 9568444:WT=29 Reg#301 [Error] FNRPE2131090138E RPC token timeout ** (301)
1.101:159.208.199.132:sv63340.ca.sunlife:71c5ee28-da30-4b58-81c8-462071c07538: =P8PEService2UAT(0) [UTC: 1371636264, RPC: 1371636264(0), WS: 0, LG: 0] Tk(1371545964, 1440) orb_rpc_unlockSaveAndRedirect; Exception: Token timed out

The user should never see this error. The system should automatically re-logon the user.
at filenet.jpe.rpc.orb.OrbRPC.REPORT_TOKEN_TIMEOUT(OrbRPC.java:205)
at filenet.jpe.rpc.orb.OrbRPC.authenticateUser(OrbRPC.java:349)
at filenet.jpe.rpc.orb.OrbRPC.<init>(OrbRPC.java:701)
at filenet.jpe.rpc.orb.ORBPERPC.orb_rpc_unlockSaveAndRedirect(ORBPERPC.java:3114)
at filenet.pe.peorb.FileNet_PERPC.PERPCPOA._invoke(PERPCPOA.java:1312)
at com.ibm.CORBA.poa.POAServerDelegate.dispatchToServant(POAServerDelegate.java:402)
at com.ibm.CORBA.poa.POAServerDelegate.internalDispatch(POAServerDelegate.java:334)
at com.ibm.CORBA.poa.POAServerDelegate.dispatch(POAServerDelegate.java:256)
at com.ibm.rmi.iiop.ORB.process(ORB.java:518)
at com.ibm.CORBA.iiop.ORB.process(ORB.java:1574)
at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2880)
at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2753)
at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
at com.ibm.rmi.iiop.WorkerThread.run(ThreadPoolImpl.java:202)
at java.lang.Thread.run(Thread.java:736)
...

Should I concern about these error messages?

Answer

These are just informational messages and can be ignored.

These error messages indicate that the token timeout has been reached. When the token is timed out, users would have to log back in again. The token is intentionally set to have a 24-hour timeout. This is done as a security measure, so that the connection to the server is never kept open too long for something external to hijack the connection. In this case, it is compared with the database time.
UTC is the database time and Tk is the token time.

From the above example:
Tk: 1371545964GMT is converted to GMT Tue, 18 Jun 2013 08:59:24 UTC
UTC: 1371636264 is converted to GMT: Wed, 19 Jun 2013 10:04:24 UTC

Notice that the token time was stamped more than 24 hour before the current (then) database time. That was the reason for these types of message "FNRPE2131090138E RPC token timeout." The token timeout is completely normal and is nothing to worry about. The token is automatically refreshed by the PE and the end users will never even know it happened.

The token is part of the authentication framework for Process Engine API applications:
P8 5.1:
http://pic.dhe.ibm.com/infocenter/p8docs/v5r1m0/index.jsp?topic=%2Fcom.ibm.p8.security.doc%2Fp8psn040.htm

P8 4.5.1:
http://pic.dhe.ibm.com/infocenter/p8docs/v4r5m1/index.jsp?topic=%2Fcom.ibm.p8.doc%2Fadmin%2Fsecurity%2Fsec_authenticate_pe_auth.htm

Please be ensure that the system clocks on all IBM FileNet P8 servers (CE, PE, AE, WorkplaceXT, CA, BPF...) and the Database servers were all in synchronized.


Rate this page:

(0 users)Average rating

Document information


More support for:

Case Foundation
Process Engine

Software version:

4.5.0, 4.5.1, 5.0, 5.1.0

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

1641629

Modified date:

2013-08-30

Translate my page

Machine Translation

Content navigation