Possible solution for 'ISAM error: key value locked' on Informix tables

Recently working on transactional container may me found some exception described as following:


Having a configuration on Spring jdbc I did saw that my transaccional configuration was for read-only on true value so I have to change the configuration like this:

@Transactional(value = "XXXXTransaccionManager", readOnly = false, propagation = Propagation.REQUIRED, timeout = 6000,isolation = Isolation.READ_COMMITTED)

By now my problem was solved, I have remembered having same problem in Oracle by mistake I forget to make that variable true on insert and updates.

Update 1 (25/05/2016)
Rounding on Internet I found  'ISAM error: key value / record is locked using transaccional enviroments is relative to Database lock following there is a explination of the problem:
http://informix-technology.blogspot.mx/2006/10/when-exclusive-is-not-really-exclusive.html
http://informix-technology.blogspot.mx/2012/11/its-errors-stupid.html

Here is a explanitation of IBM documentation: 
http://www.ibm.com/support/knowledgecenter/SSGU8G_12.1.0/com.ibm.sqls.doc/ids_sqs_1171.htm

The solution to the problem should be SET LOCK MODE WAIT or LOCK MODE in table, this resolution was only for a transacctional enviroment, please be free to make a revision of log file in database to check if this is the solution to your system.

Best regards,

Quartz executes twice on Weblogic (Spring 3.2 + Quartz 1.8.6 + Weblogic 10.3g)

If you are developing some jobs with quartz probably you will figure out if your application will be well received by Weblogic, after a few hours some unittest I have the problem that quartz execute twice the method cointained in the job, If you try to debug the application on Weblogic you will be thinking alot of theories my solution was the following steps:

1. Create Quartz Database for clustering, this is at: 

../quartz-1.8.6/docs/dbTables

After executing the script in the database you will have to configure the quartz.properties:

This property file should be included in classpath, to charge this file you will have to add the following lines in applicationContext.xml:

Having this configuration will be loaded the ClusterManager, and you job executes only one time.

Best Regards,

Exception: NoSuchMethodError, org.springframework.beans.factory.annotation.InjectionMetadata

If you are doing Unit Test with Spring Framework you will have to keeping the correct configuration of jar files that you have in you repository, sometimes if you dont have all the jar´s in you classpath exceptions will occur like this one:

java.lang.NoSuchMethodError: org.springframework.beans.factory.annotation.InjectionMetadata.<init>(Ljava/lang/Class,

With a stacktrace like this one...

It is said that you dont have the correct jar with the request method, after the first line of the above stack you can follow the method of the request jar, in this is case you see: "org.springframework.orm", finally you only need to add spring-orm dependency or jar file to your classpath.

 
Best Regards,