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,

Missing libraries on installation of IBM Message Broker and Message Queue (Part I)

I am going back to IBM Message Queue and Message Broker, after some years, returning to old school, I have decided to publish this time some memories of working around and by now the following libraries are required to install the ibm middleware on a Centos 7 Machine:

  Best regards,

How to solve artifact not found by maven?

Recently I have to chance settings.xml configuration quickly for download from different repositories after compiling I have received the following error:

"was cached in the local repository, resolution will not be reattempted until the update interval of" "has elapsed or updates are forced"

The solution to this problem is remove some keys and blueprint of artifact that were downloaded from different sites: 

find ~/.m2/ -name "*.lastUpdated" | xargs rm

find ~/.m2/ -name "*.sha1" | xargs rm 
find ~/.m2/ -name "*.repositories" | xargs rm 

Best Regards,