Failure to access keystore location prevents Vibe from starting up

  • 7016847
  • 17-Sep-2015
  • 22-Sep-2015

Environment

Novell Vibe 4.0

Situation

When initializing the inbound SMTP server, if the keystore cannot be accessed for any reason (bad path, wrong keystore password, etc.) Vibe fails to start and logs bogus exception about access to SPropsUtil which is very misleading and causes confusion.

The error message in appserver.log looks as follows:

Error creating bean with name 'sPropsUtil' defined in ServletContext resource [/WEB-INF/context/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.kablink.teaming.util.SPropsUtil]: Constructor threw exception; nested exception is java.lang.IllegalStateException: PropsUtil is a singleton class
    at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:334)
    at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:108)
    ............

Resolution

A fix for this issue is available in the Vibe 4.0 Hot Patch 4, available via the Novell Patch Finder.

Additional Information

Note:
With the fix in place if the keystore cannot be accessed for any reason (bad path, wrong keystore password, etc.), the following error will be logged in appserver.log file and Vibe will continue to run with the Inbound SMTP server disabled (i.e., with no inbound email support):

2015-09-14 08:20:35,047 ERROR [localhost-startStop-1] [org.kablink.teaming.smtp.impl.SMTPManagerImpl] - Inbound SMTP Server:  Cannot access keystore file. 
Inbound SMTP m_server will be disabled.
java.io.FileNotFoundException: /opt/novell/teaming/apache-tomcat/webapps/ssf/../../conf/.keystore (No such file or directory)

Feedback service temporarily unavailable. For content questions or problems, please contact Support.