java LAST_ACK FIN_WAIT2

Use this forum to report bugs and to check for bugfixes and new releases of OpenEMM

Moderator: moderator

ryck
Posts: 1
Joined: Mon Jun 29, 2015 4:54 am

java LAST_ACK FIN_WAIT2

Post by ryck »

Hello folks,

I've been using openemm 2015 for a year. So far so good, but since the beginning, when sending more than a few thousands of mails, the sessions to the :8080 start getting growing to 2-15k.

I increased the amount of opened files, but I would like to get some advice to get rid of these errors. I always solve it restarting by openemm.sh stop / start.


these are some errors I see at the catalina.out:

016-10-05 16:44:49,955: ERROR [http-nio-8080-exec-68] org.agnitas.beans.impl.UserFormImpl - _request: org.agnitas.web.filter.Struts1SecurityFilter$ParamFilteredRequest@5eebc6ec
2016-10-05 16:44:49,955: ERROR [http-nio-8080-exec-68] org.agnitas.web.UserFormExecuteAction - execute()
2016-10-05 16:44:49,956: ERROR [http-nio-8080-exec-68] org.apache.strutsx|x.chain.commands.ExceptionCatcher - Cannot find catalog 'struts'
2016-10-05 16:44:49,954: ERROR [http-nio-8080-exec-100] org.agnitas.beans.impl.UserFormImpl - locale: es_XL
2016-10-05 16:44:49,957: ERROR [http-nio-8080-exec-100] org.agnitas.beans.impl.UserFormImpl - agnuid: 1.me.lo91.3aj.lgr07xd0ly
2016-10-05 16:44:49,957: ERROR [http-nio-8080-exec-100] org.agnitas.beans.impl.UserFormImpl - _request: org.agnitas.web.filter.Struts1SecurityFilter$ParamFilteredRequest@2bf43154
2016-10-05 16:44:49,957: ERROR [http-nio-8080-exec-100] org.agnitas.web.UserFormExecuteAction - execute()
2016-10-05 16:44:49,958: ERROR [http-nio-8080-exec-100] org.apache.struts.chain.commands.ExceptionCatcher - Cannot find catalog 'struts'
2016-10-05 16:46:21,455: ERROR [openemm-startStop-1] org.springframework.web.context.ContextLoader - Context initialization failed
2016-10-05 16:46:21,458: ERROR [openemm-startStop-1] org.agnitas.backend.BackendDatasourceInitializationContextListener - Cannot set Datasource in DBase for Backend. Backend will try to create its own datasource from emm.properties data

Is there other info that could help to trace this faults?

thank you for your advice.