Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0027201Retail ModulesWeb POSpublic2014-07-25 12:452014-12-17 15:39
ReporterOrekaria 
Assigned Tomarvintm 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionsuspended 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0027201: Backend WARN org.openbravo.erpCommon.ad_forms.AcctServer - java.lang.IllegalStateException
Description2014-07-25 07:41:54,273 [DefaultQuartzScheduler_Worker-10] WARN org.openbravo.erpCommon.ad_forms.AcctServer - java.lang.IllegalStateException
Steps To ReproduceNA
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
blocks defect 0027337 acknowledged Retail Stabilization: No tomcat errors while running the WebPOS 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-07-25 12:45OrekariaNew Issue
2014-07-25 12:45OrekariaAssigned To => marvintm
2014-07-25 12:45OrekariaOBNetwork customer => No
2014-07-25 12:45OrekariaTriggers an Emergency Pack => No
2014-07-25 12:46OrekariaSummaryWARN org.openbravo.erpCommon.ad_forms.AcctServer - java.lang.IllegalStateException => Backend WARN org.openbravo.erpCommon.ad_forms.AcctServer - java.lang.IllegalStateException
2014-08-14 13:18OrekariaRelationship addedblocks 0027337
2014-12-17 15:39mtaalNote Added: 0072644
2014-12-17 15:39mtaalStatusnew => closed
2014-12-17 15:39mtaalResolutionopen => suspended

Notes
(0072644)
mtaal   
2014-12-17 15:39   
In the end the decision is to ignore these log warnings. Any issues here should be entered on the ERP functional part as it is not correct to log these things in openbravo log