0030798: Lots of errors in log during tomcat shutdown related to new import entry project

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0030798

Openbravo ERP

A. Platform

public

2015-08-03 16:27

2015-11-16 08:51

Reporter

shuehner

Assigned To

Retail

Priority

immediate

Severity

minor

Reproducibility

have not tried

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

Target Version

3.0PR15Q3.4

Fixed in Version

3.0PR15Q3.4

Merge Request Status

Review Assigned To

marvintm

OBNetwork customer

Web browser

Modules

Core

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0030798: Lots of errors in log during tomcat shutdown related to new import entry project

Description

I.e. in the try-ret-modules test there are often or always many errors on tomcat shutdown which look related to the new import entry project.

Example:
https://ci.openbravo.com/job/try-ret-modules-pgsql/393/artifact/SANDBOX/tomcat-logs/try-ret-modules-pgsql.log [^]

Note: there are many (like 50) errors with all that content in that
2015-08-03 07:13:04,457 [Import Entry Archiver] ERROR org.openbravo.service.importprocess.ImportEntryArchiveManager - WELD-001303 No active contexts for scope type javax.enterprise.context.Dependent
org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.Dependent
    at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:596)
    at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:626)
    at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:653)
    at org.jboss.weld.bean.builtin.InstanceImpl.iterator(InstanceImpl.java:133)
    at org.openbravo.service.importprocess.ImportEntryArchiveManager$ImportEntryArchiveThread.run(ImportEntryArchiveManager.java:151)
    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)

If that bug also happens in Q3 (probably likely) that this should be backported also.

Steps To Reproduce

run latest retail for in try-retail and check openbravo.log after the job finishes

Proposed Solution

Additional Information