Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0003404
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Openbravo ERP] C. Securityminoralways2007-10-25 00:132009-05-20 07:21
ReporterroklenardicView Statuspublic 
Assigned Toanthony_wolski 
PrioritynormalResolutionfixedFixed in Version2.50
StatusclosedFix in branchpiFixed in SCM revisionna
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0003404: Background processes

DescriptionIn HttpSecureAppServlet.java, line 130 we have the following code

          try {
          object = new PeriodicBackground(this, Long.parseLong(strPeriodicBackgroundTime), strLogFileAcctServer, backgroundData[countBack].id, backgroundData[countBack].classname);
          } catch (IOException ioe) {
            ioe.printStackTrace();
          }

In case tomcat cannot write in the folder where the strLogFileAcctServer is put, all background processes fail to initialize/execute and noone ever knows about this. In case of Background accounting process, this is a huge issue.
instead of ioe.printStackTrace(); there should at least be log4j logging there.

On the other hand, there should be some kind of special logging/alerting for system critical processes such as background accounting so that the admin can see if they fail. maybe Alerts could be used for that. regardless, the exception catch there should be logged better.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
blocks feature request 00041472.50 closedanthony_wolski Background process management 

-  Notes
(0006993)
user71
2005-06-01 00:00
edited on: 2008-06-12 09:44

This bug was originally reported in SourceForge bug tracker and then migrated to Mantis.

You can see the original bug report in:
https://sourceforge.net/support/tracker.php?aid=1819619 [^]

- Issue History
Date Modified Username Field Change
2008-06-27 16:16 pjuvara Relationship added blocks 0004147
2008-06-27 16:17 pjuvara Assigned To user71 => anthony_wolski
2008-06-27 16:17 pjuvara Status new => acknowledged
2008-11-03 13:25 pjuvara Status acknowledged => scheduled
2008-11-03 13:25 pjuvara fix_in_branch => trunk
2008-11-03 13:25 pjuvara Status scheduled => resolved
2008-11-03 13:25 pjuvara Fixed in Version => 2.50
2008-11-03 13:25 pjuvara svn_revision => na
2008-11-03 13:25 pjuvara Resolution open => fixed
2009-05-20 07:21 pjuvara Status resolved => closed


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker