Why does EMS log "JAAS: Exception initializing JAAS configuration file xxx: java.util.concurrent.TimeoutException" during starting up?

Why does EMS log "JAAS: Exception initializing JAAS configuration file xxx: java.util.concurrent.TimeoutException" during starting up?

book

Article ID: KB0082028

calendar_today

Updated On:

Products Versions
TIBCO Enterprise Message Service -

Description

The default value of jaas_login_timeout is ten seconds. It is also used for authentication user by the JAAS module. When JRE or the JAAS configuration file are on network drive (i.e NFS), system call (i.e., read, open, etc.) it may take a long time. Files can not be loaded withinten  seconds. A timeout occurs.

Issue/Introduction

When EMS is configured to use a JAAS module, it logs the error, "JAAS: Exception initializing JAAS configuration file cfg/jaas.conf: java.util.concurrent.TimeoutException" during starting up. The JAAS module is not loaded.

Environment

All

Resolution

1). Consult your System Administrator or Storage Team regarding the slowness in the open/read system calls. Try to place the files on a local disk.

2).  Try to load the JVM and JAR files by running a simple Java program prior to starting the EMS server.

For example:

<java_home>/bin/java -classpath .:<path>/tibemsd_sec.jar:<path>/tibemsd_sec_internal.jar Test

The files can be cached by the OS. EMS can access the files faster.

3).  If a datastore is not large enough, set the jaas_login_timeout to a longer time (i.e., two minutes) before starting the EMS server, so that the timeout does not happen.  Then remove the parameter. Restart the EMS server again.

Additional Information

EMS User's Guide