텅 비어가는 ..

vi /Applications/eclipse/Eclipse.app/Contents/MacOS/eclipse.ini

showsplash org.eclipse.platform
--launcher.XXMaxPermSize 512m
-vmargs
-Xms40m
-Xmx512m
-XX:MaxPermSize=512m
-Xms40m
-Xmx512m

12.5. iBATIS SQL Maps

The iBATIS support in the Spring Framework much resembles the JDBC / Hibernate support in that it supports the same template style programming and just as with JDBC or Hibernate, the iBATIS support works with Spring's exception hierarchy and let's you enjoy the all IoC features Spring has.

Transaction management can be handled through Spring's standard facilities. There are no special transaction strategies for iBATIS, as there is no special transactional resource involved other than a JDBCConnection. Hence, Spring's standard JDBC DataSourceTransactionManager orJtaTransactionManager are perfectly sufficient.

12.5.1. Setting up the SqlMapClient

If we want to map the previous Account class with iBATIS 2.x we need to create the following SQL map'Account.xml':

The configuration file for iBATIS 2 looks like this:

Remember that iBATIS loads resources from the class path, so be sure to add the 'Account.xml' file to the class path.

We can use the SqlMapClientFactoryBean in the Spring container. Note that with iBATIS SQL Maps 2.x, the JDBC DataSource is usually specified on the SqlMapClientFactoryBean, which enables lazy loading.

12.5.2. Using SqlMapClientTemplate and SqlMapClientDaoSupport

The SqlMapClientDaoSupport class offers a supporting class similar to the SqlMapDaoSupport. We extend it to implement our DAO:

In the DAO, we use the pre-configured SqlMapClientTemplate to execute the queries, after setting up the SqlMapAccountDao in the application context and wiring it with our SqlMapClient instance:

Note that a SqlMapTemplate instance could also be created manually, passing in the SqlMapClient as constructor argument. The SqlMapClientDaoSupport base class simply pre-initializes aSqlMapClientTemplate instance for us.

The SqlMapClientTemplate also offers a generic execute method, taking a customSqlMapClientCallback implementation as argument. This can, for example, be used for batching:

In general, any combination of operations offered by the native SqlMapExecutor API can be used in such a callback. Any SQLException thrown will automatically get converted to Spring's genericDataAccessException hierarchy.

12.5.3. Implementing DAOs based on plain iBATIS API

DAOs can also be written against plain iBATIS API, without any Spring dependencies, directly using an injected SqlMapClient. A corresponding DAO implementation looks like as follows:

In such a scenario, the SQLException thrown by the iBATIS API needs to be handled in a custom fashion: usually, wrapping it in your own application-specific DAO exception. Wiring in the application context would still look like before, due to the fact that the plain iBATIS-based DAO still follows the Dependency Injection pattern:

[시스템 정보 확인] 

#echo "";echo "[DATE]";date;echo "";echo "[HOSTNAME]";hostname;echo "";echo "[UPTIME]";uptime;echo "";echo "[FS]";df -h;echo "";echo "[MEMORY]";free -m;echo "";

[SQL Node Process 확인] 

#ps -ef | grep mysqld | grep -v grep 

[MySQL Variables 확인] 

#/usr/local/mysql/bin/mysql -uroot -p -e "show global variables;"

[MySQL Status 확인] 

#/usr/local/mysql/bin/mysql -uroot -p -e "show global status;"

[DB의 Table 당 DATA 크기와 INDEX 크기 확인] 

#/usr/local/mysql/bin/mysql -uroot -p -e "select table_schema,table_name,(data_length)/(1024*1024) as 'DATA(MB)',(index_length)/(1024*1024) as 'INDEX(MB)' from information_schema.tables ;"

[SQL Node 로그 확인] 

#tail -100 /data/mysqldb/datadb/sql2.err

[MGM Node Process 확인] 

#ps -ef | grep ndb_mgmd | grep -v grep

[Cluster 상태 확인]

#/usr/local/mysql/bin/ndb_mgm -e "show"

[Cluster 메모리 사용량 확인]

#/usr/local/mysql/bin/ndb_mgm -e "all dump 1000"; tail -10 /mysqldb/clusterdb/ndb_1_cluster.log | grep -w usage

[MGM Node 로그 확인] 

#/mysqldb/clusterdb/ndb_1_cluster.log


[각 시스템 상태 확인] 

#vmstat -S m -n 5 60

[DATA Node Process 확인] 

#ps -ef | grep ndbd | grep -v grep

[DATA Node 로그 확인] 

#tail -20 /data/mysqldb/clusterdb/ndb_3_out.log

#tail -20 /data/mysqldb/clusterdb/ndb_3_error.log


[점검후 최종 상태 확인]

#/usr/local/mysql/bin/ndb_mgm -e "show"