Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012635Openbravo ERPA. Platformpublic2010-03-10 16:292010-03-10 18:30
Reporterpsarobe 
Assigned Toiperdomo 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionduplicate 
PlatformOS5OS Version
Product Version2.50MP12 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0012635: Process request: An error in the log
DescriptionThis is the log error:

 ERROR org.openbravo.scheduling.ProcessRequestData - SQL error in query: »··UPDATE AD_Process_Request »SET Updatedby = ?, AD_User_ID = ?, Status = ?, Channel = ?, »··Previous_Fire_Time = TO_TIMESTAMP(?, 'DD-MM-YYYY HH24:MI:SS'), »··· e_Time = TO_TIMESTAMP(?, 'DD-MM-YYYY HH24:MI:SS'), »···Scheduled_Finish = TO_TIMESTAMP(?, 'DD-MM-YYYY HH24:MI:SS'), »·Ob_Context = ? WHERE AD_Process_Request_ID = ?Exception:java.sql.SQLDataException: ORA-01830: date format picture ends before converting entire input string
Steps To ReproduceSorry but not really steps I can write. Just after a while using the ERP if you go to the logs you can see the error

The error has to do with the date you pass that the value is too long. For example you can reproduce it in Oracle if you execute this statement:

select TO_TIMESTAMP('01-01-2010 00:00:00,000000000', 'DD-MM-YYYY HH24:MI:SS') from dual

Please notice what it's supposed to be the date
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
duplicate of defect 00123822.50MP14 closed iperdomo The ProcessReques_data.xsql file does not take into account the date format defined on the Openbravo.properties file 
related to defect 00126702.50MP14 closed iperdomo In Oracle, I cannot unschedule background processes 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-03-10 16:29psarobeNew Issue
2010-03-10 16:29psarobeAssigned To => iperdomo
2010-03-10 16:36psarobeStatusnew => scheduled
2010-03-10 16:36psarobefix_in_branch => pi
2010-03-10 16:44iperdomoRelationship addedduplicate of 0012382
2010-03-10 16:44iperdomoNote Added: 0025212
2010-03-10 16:44iperdomoStatusscheduled => closed
2010-03-10 16:44iperdomoResolutionopen => duplicate
2010-03-10 17:25anonymoussf_bug_id0 =>
2010-03-10 18:30anonymoussf_bug_id => 2968129
2010-03-12 17:11plujanRelationship addedrelated to 0012670

Notes
(0025212)
iperdomo   
2010-03-10 16:44   
Duplicated of existing issue targeting 2.50MP14