DB Issues
- Rajeev Rai
Issue | Cause | Diagnosis | Resolution |
Error:We are facing an issue while splitting source file with 10000 records, but it is putting an error message - | The DB Select Query used in the data mapper may return multiple values from the database and the target field "Material_id" expects a single value that could result into the issue of "Premature end of file". | We will get this error in the stack trace: |
For resolving this issue there are two possible ways. One is to modify your DB query used in data mapper so that it will return a single value from the database. Or you can change the third input Boolean value of the DB Query to 'False' in the Data Mapper that will always return a top value from the ResultSet of the DBQuery. The DBQuery with value false should be like this : "DBQuery{Select material_transformation from product_master_lookup where material_id='$Input_bhi_inventory_ops_schema/Root/Record/Material_ID',$conn_Info ,'false'}" |
DeadLock issue while running events. | The org.quartz.jobStore.acquireTriggersWithinLock property is not set as true in “quartz.properties” | We will get this error in the stack trace: | On facing this deadlock issue while running events, then we need to add the property org.quartz.jobStore.acquireTriggersWithinLock = true in “quartz.properties” file present in “<AdeptiaSuite_Installation_Directory>/ServerKernel/etc” folder. After adding this property we need to restart the “kernel” & “webrunner” to bring this property into effect. |
Deadlock issue while running events | Mostly this deadlock issue comes with “Microsoft SQL Server” when large number of events are activated. | Will see the below error message: org.quartz.JobPersistenceException: Couldn't update trigger state(s): Transaction (Process ID 69) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. [See nested exception: java.sql.SQLException: Transaction (Process ID 69) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.] | On facing above deadlock issue while running events, then we need to add the property below in “quartz.properties” file present in “<AdeptiaSuite_Installation_Directory>/ServerKernel/etc” folder. After adding this property we need to restart the “kernel” & “webrunner” to bring this property into effect.
Change the following property: org.quartz.jobStore.acquireTriggersWithinLock = true |