Open ports of Centos 7 in a Virtual Machine over VirtualBox

Recently I have to configure my virtual machine to get some ports exposed in the network using a virtual box for publish, there are only two steps that resolve my problem:

Step 1:  Add port to firewall configuration
1.1. Execute: $ sudo firewall-config
1.2. Add the tcp ports required on ports tab

Step 2: If you have a configuration with NAT network you have to execute the next command according to your machine:
$ VBoxManage modifyvm "dev_centos" --natpf1 "tomcat,tcp,127.0.0.1,<port>,10.0.2.15,<port>"

Best Regards,

Useful MQSC scripts for IBM Message Queue (Part I)

I have been caught by the time, after some years ago, my knowledge of configuration of IBM Message Queue is not being in practice because spending 2 hours trying to configure Channel Security the remembrance of how doing it stuck me.

I have decided to conserve some memories of script of configuration and this is the first part.

1. Backup and recovery script:

2. Remove security to the channel

Important Links:

• https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.adm.doc/q117770_.htm

Best regards,

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,