Tomcat Log Size Causes OFSAA Application to Crash After 8.1.2.4.0 Upgrade (Doc ID 3072495.1)

Last updated on FEBRUARY 18, 2025

Applies to:

Symptoms

After upgrading to OFSAA 8.1.2.4.0, the application is crashing because the server is running out of space.  The size of the Tomcat catalina.out is growing so large, it takes up all of the space.  The size of the catalina.out increases quickly when users are in the application.

Checking the contents of the catalina.out, the following errors appear repeatedly:

Error #1:

WebHandler:: Inside [getMessageFromLocaleSpeficCache] of [MessageFramework] $$$ key: SMSME.WIN_ALRDY_OPEN locale:
WebHandler:: Inside loadLocaleSpecificCacheMessages of MessageFramework $$$ package: SMSME locale:
WebHandler:: Retrieving package SMSME from cache.
WebHandler:: Getting value against key: [com.ofs.aai.sms.webserver.cache.entity.MessageSetKey@7b3724f0_] from cache
WebHandler:: Value against key: [com.ofs.aai.sms.webserver.cache.entity.MessageSetKey@7b3724f0_] not found
WebHandler:: Package SMSME not available in cache. Loading.
WebHandler:: [DBMessageReader] Getting messages for package:SMSME locale:
WebHandler:: java.lang.NullPointerException
WebHandler:: java.lang.NullPointerException
java.lang.NullPointerException
     at java.util.Hashtable.put(Hashtable.java:461)
     at com.ofs.aai.sms.webserver.cache.client.MessageFramework.loadLocaleSpecificCacheMessages(MessageFramework.java:22)
     at com.ofs.aai.sms.webserver.cache.client.MessageFramework.getMessageFromLocaleSpeficCache(MessageFramework.java:63)
     at com.ofs.aai.sms.webserver.cache.client.MessageFramework.getMessageFromLocaleSpeficCache(MessageFramework.java:64)
     at com.ofs.aai.sms.webserver.cache.client.MessageFramework.getMessageFromLocaleSpeficCache(MessageFramework.java:64)
     at com.ofs.aai.sms.webserver.cache.client.MessageFramework.getMessageFromLocaleSpeficCache(MessageFramework.java:64)

Error #2:

2024-10-13 06:17:03,499 Message Logger Daemon Thread ERROR Recovering from StringBuilderEncoder.encode('[13-10-24 10:17:03,499 GMT AM] [ERROR] [WEB] [SMS] [NA] [DASHBOARDHANDLER]
java.lang.NullPointerException
     at com.ofs.aai.sms.webserver.cache.app.DBMessageReader.getTableName(DBMessageReader.java:140)
     at com.ofs.aai.sms.webserver.cache.app.DBMessageReader.getRecordSet(DBMessageReader.java:51)
     at com.ofs.aai.sms.webserver.cache.app.DBMessageReader.getMessages(DBMessageReader.java:38)
     at com.ofs.aai.sms.webserver.cache.app.MessageFrameworkApp.fetchMessages(MessageFrameworkApp.java:32)
     at com.ofs.aai.sms.webserver.cache.client.MessageFramework.loadLocaleSpecificCacheMessages(MessageFramework.java:21)
     at com.ofs.aai.sms.webserver.cache.client.MessageFramework.getMessageFromLocaleSpeficCache(MessageFramework.java:63)
     at com.ofs.aai.sms.webserver.cache.client.MessageFramework.getMessageFromLocaleSpeficCache(MessageFramework.java:64)
     at com.ofs.aai.sms.webserver.cache.client.MessageFramework.getMessageFromLocaleSpeficCache(MessageFramework.java:64)
     at com.ofs.aai.sms.webserver.cache.client.MessageFramework.getMessageFromLocaleSpeficCache(MessageFramework.java:64)

You can fix the issue temporarily by clearing the catalina.out and re-starting the environment.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.