Common entries in the contour logs that are harmless

By Iris posted 01-15-2016 13:10

  

As Jama works to improve the signal to noise ratio within our logs, we want to give administrators a list of information logged that can seem concerning, but is mostly harmless. Unless specified otherwise, these errors will be found in the contour.log file. We are continuously improving our logging and plan to make updates to remove this information in future releases.

Warnings in 2015.3 and below

Failed to find property:

WARN  http-bio-8080-exec-4  [com.jamasoftware.contour.dwr.converter.hibernate4.H4BeanConverter] - Failed to find property: ...

This warning occurs due to objects using the hibernate library not having particular methods initialized. The H4BeanConverter checks for a standard set of properties within each object using the hibernate library. Not every object will use or need these properties, and so they are not initialized. This will not cause any issues within your Jama instance.

Missing Setter:

WARN  http-bio-8080-exec-4  [org.directwebremoting.convert.BasicObjectConverter] - Missing setter: com.jamasoftware.contour.service.dto.ExtDocumentTreeNode...() to match javascript property: ... Check include/exclude rules and overloaded methods

Like the "failed to find property" warning, this message is due to uninitialized properties for certain objects the DWR is expecting to be initialized. Again, these properties are not being used and will not cause any issues within Jama.

Ehcache Warnings:

WARN  localhost-startStop-1  [net.sf.ehcache.config.CacheConfiguration] - Cache: backingPermissionNodeCache has a maxElementsInMemory of 0. This might lead to performance degradation or OutOfMemoryError at Terracotta client.From Ehcache 2.0 onwards this has been changed to mean a store with no capacity limit. Set it to 1 if you want no elements cached in memory    A soft-locked cache entry was expired by the underlying Ehcache. If this happens regularly you should consider increasing the cache timeouts and/or capacity limits

In 2014.2, the limits on caching were removed. This was done after much research and testing revealed that customers were a lot more likely to encounter issues due to the caching being restricted than if it was set to unlimited. The amount of caching Jama will use will rarely exceed any resource limitations on the server, so this will likely never cause an issue. Very rarely will caching be an issue within Jama and these warnings will not help when there is an issue with the cache. 

If you are concerned about the cache, you can check its usage when logged in as the root user under the Cache Statistics tab. From there, you can also clear the cache of a property by selecting Clear Cache.

SMTP Disabled Warnings:

WARN  jamaSchedulerFactoryBean_Worker-1  [com.jamasoftware.contour.service.impl.NotificationServiceImpl] - SMTP server is disabled or not configured properly.  Emails are not sent.

This warning typically appears when SMTP is disabled. If you do not have SMTP enabled, this can be ignored. If you do have SMTP enabled, reach out to Support.

Invalid DSN Exception - found in catalina.out:

log4j:ERROR An exception occurred during the retrieval of the DSN for Raven  net.kencochrane.raven.dsn.InvalidDsnException: The sentry DSN must be provided and not be null      at net.kencochrane.raven.dsn.Dsn.<init>(Dsn.java:48)      at net.kencochrane.raven.log4j.SentryAppender.initRaven(SentryAppender.java:125)      at net.kencochrane.raven.log4j.SentryAppender.activateOptions(SentryAppender.java:114)      at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)      at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172)      at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104)      at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842)      at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768)      at org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:648)      at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:514)      at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580)      at org.apache.log4j.PropertyConfigurator.configure(PropertyConfigurator.java:415)      at org.springframework.util.Log4jConfigurer.initLogging(Log4jConfigurer.java:72)      at org.springframework.web.util.Log4jWebConfigurer.initLogging(Log4jWebConfigurer.java:153)      at org.springframework.web.util.Log4jConfigListener.contextInitialized(Log4jConfigListener.java:45)      at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4973)      at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5467)      at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)      at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)      at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)      at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632)      at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1229)      at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1875)      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)      at java.util.concurrent.FutureTask.run(FutureTask.java:266)      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)      at java.lang.Thread.run(Thread.java:745)

 

This error appears during Jama startup in catalina.out. This is due to a configuration required for our hosted clients which does not exist for on-premises versions. It will not cause any issues during startup. If you are having issues starting Jama, contact Support.

 Severe Thread Warnings - found in catalina.out:

SEVERE: The web application [/contour] created a ThreadLocal with key of type... but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.        SEVERE: The web application [/contour] appears to have started a thread named [jamaSchedulerFactoryBean_Worker-11] but has failed to stop it. This is very likely to create a memory leak.

Both of these warnings are related to Jama not stopping threads when being shutdown. This should not cause issues unless Jama is continuously being re-deployed without Tomcat being restarted. These errors started appearing as a result of memory leak protection added to Tomcat 6 and later. More information can be found on the Apache website.

Warnings in 2015.1 and below

Clash of Converters:

WARN  localhost-startStop-1  [org.directwebremoting.log.startup] - Clash of converters for com.jamasoftware.contour.api.service.dto.PropertyListDTO. Using com.jamasoftware.contour.dwr.converter.ContourApiConverter in place of com.jamasoftware.contour.dwr.converter.JamaH4BeanConverter

This error typically appears when Jama is starting up. It can be ignored and is removed in later versions of Jama.

 



#installation
0 comments
252 views