spring boot2017.09.05 10:30


Spring Boot 1.3 will ship with a brand new module called spring-boot-devtools. The aim of this module is to try and improve the development-time experience when working on Spring Boot applications.

To use the module you simply need to add it as a dependency in your Maven POM:


or your Gradle build file:

dependencies {

Once included, the spring-boot-devtools module provides a number of nice features that we cover below (If you can’t be bother to read the text, skip to the end of the post for a short video).

Property Defaults

If you’ve used templating technologies such as Thymeleaf with Spring Boot 1.2, you might be familiar with properties such as spring.thymeleaf.cache. These properties are used to disable caching and allow you to update pages without needing to restart your application. Having support for these properties is pretty handy, but remembering to set them during development has always been a bit of a pain.

Now, when you use the spring-boot-devtools module, you no longer need to remember to set the properties. During development caching for Thymeleaf, Freemarker, Groovy Templates, Velocity and Mustache are all automatically disabled.

Automatic Restart

You may have used tools such as JRebel or Spring Loaded in the past to provide instant reload for your Java applications. These tools are great, but they do often require additional configuration or IDE plugins to work (and some of them even cost money!)

With Spring Boot 1.3 we’ve been working on something that’s a little slower than these “instant reload” techniques, and instead works by restarting your application. When you have the spring-boot-devtools module included, any classpath file changes will automatically trigger an application restart. We do some tricks to try and keep restarts fast, so for many microservice style applications this technique might be good enough.


With sensible “cache properties” and “automatic restarts” working, needing to manually click the browser refresh button each time something changes starts to become a little tedious. So to help save your mouse buttons, Spring Boot 1.3 DevTools includes an embedded LiveReload server. LiveReload is a simple protocol that allows your application to automatically trigger a browser refresh whenever things change. Browser extensions are freely available for Chrome, Firefox and Safari from livereload.com.

Remote Debug Tunneling

If you’ve ever tried to host a Java application using Docker, or if you’ve tried a micro PaaS such as Lattice, you may have been frustrated about how difficult it can be to debug your code. You need configure Java to start with -Xdebug and somehow forward the appropriate port so that you can attach the remote debugger.

To help with this, Spring Boot 1.3 can tunnel JDWP (the Java Debug Wire Protocol) over HTTP directly to your application. This can even work with applications deployed to Internet Cloud providers that only expose port 80 and 443 (although since JDWP is quite a chatty protocol this can be quite slow).

Remote Update and Restart

The final trick that DevTools offers is support for remote application updates and restarts. This works by monitoring your local classpath for file changes and pushing them to a remote server which is then restarted. As with local restarts, you can also use this feature in combination with LiveReload.

Video Preview

All the features discussed in this post are already available in Spring Boot 1.3.0.M1 and detailed documentation is available in the reference guide. If you’re not ready to install the bits yourself yet, here’s a short video that shows how they work:

Posted by WebProgrammer 1010
02.Oracle2017.08.17 10:24

alter session set "_ORACLE_SCRIPT"=true;

Posted by WebProgrammer 1010
분류없음2017.07.05 11:56

출처 : http://realforce111.tistory.com/37

리눅스에 SNMP를 설정하는 방법을 알아보겠습니다.

# yum list | grep snmp 

SNMP 패키지 리스트 리스트를 보여 줍니다.

# yum -y install net-snmp.x86_64
# yum -y install net-snmp-util.x86_64

net-snmp.x86_64, net-snmp-utils.x86_64 두 가지 파일을 설치 합니다.

# vi /etc/snmp/snmpd.conf

# First, map the community name "public" into a "security name"

# sec.name source community

com2sec notConfigUser default public

com2sec kimms public     // SNMP 허용 아이피와 community name 입력

com2sec kimms default public


설치 완료 후 /etc/snmp/snmpd.conf 파일 수정

# groupName securityModel securityName 
group notConfigGroup v1 notConfigUser 
group notConfigGroup v2c notConfigUser 
group kimmsgroup v1 kimms      // 그룹 추가
group kimmsgroup v2c kimms 
group kimmsgroup usm kimms


# Finally, grant the group read-only access to the systemview view. 
# group context sec.model sec.level prefix read write notif 
# access notConfigGroup "" any noauth exact roview rwview none 
access kimmsgroup "" any noauth exact all all all

SNMP 서비스를 시작 합니다.

SNMP 서비스가 정상적으로 실행중인지 확인하기 위해 netstat 명령을 실행 합니다.

# snmpwalk -v 2c -c public localhost system
# snmpwalk -v -2c -c public system     // snmpwalk-v 2c -c public "허용 IP" system

정상적으로 출력 된다면 해당 장비의 정보를 가져올 수 있습니다.

출처: http://realforce111.tistory.com/37 [realforce111님의 블로그]

Posted by WebProgrammer 1010
02.Oracle2017.06.02 14:20

VARIABLE jobno number;









Posted by WebProgrammer 1010
분류없음2017.04.17 08:36

systemctl stop firewalld

 systemctl start firewalld

# firewall-cmd --permanent --zone=public --add-port=8080/tcp

# firewall-cmd --reload

Posted by WebProgrammer 1010
분류없음2017.03.28 17:41

map.setCenterAndLevel(new nhn.api.map.LatLng(36.35041200438027,127.38454801772923),7);

Posted by WebProgrammer 1010
hadoop2017.03.07 15:53

hadoop fs -copyToLocal /실제파일위치경로 /내려받을경로

Posted by WebProgrammer 1010
분류없음2017.02.28 16:05

route add mask metric 1 -p

route add mask metric 2 -p

Posted by WebProgrammer 1010
분류없음2017.02.24 10:38

How To Install Dokuwiki on CentOS 7

r00t November 21, 2015

install Dokuwiki on ubuntu 15.04

In this tutorial we will show you how to install and configuration of Dokuwiki on your CentOS 7 server. For those of you who didn’t know, DokuWiki is considered to be the most versatile open source Wiki software application which is proven to meet your demanding wiki needs. Using a very familiar interface, it allows you to easily scale and optimize using many advanced features. Utilizing files instead of a database, DokuWiki is extremely flexible with the type of system it will run on (no database server required).

This article assumes you have at least basic knowledge of linux, know how to use the shell, and most importantly, you host your site on your own VPS. The installation is quite simple. I will show you through the step by step installation Dokuwiki in CentOS 7 server.

Install Dokuwiki on CentOS 7

Step 1. First let’s start by ensuring your system is up-to-date.

Step 2. Install LAMP server.

A CentOS 7 LAMP server is required. If you do not have LAMP installed, you can follow our guide here. Also install required PHP modules:

Step 3. Installing Dokuwiki.

First thing to do is to go to DokuWiki’s download page and  download the latest stable version of Dokuwiki:

We will need to change some folders permissions:

Step 4. Configuring Apache web server for Dokuwiki.

It is time to configure Apache. Create a ‘/etc/httpd/conf.d/vhosts.conf’ file with the following content

Create a ‘/etc/httpd/vhosts.d’ directory where we will put all our virtual hosts:

Create a virtual host for our domain:

Add the following lines at the end of the file:

Save and close the file. Restart the apache service for the changes to take effects:

Step 5. Accessing DokuWiki.

DokuWiki will be available on HTTP port 80 by default. Open your favorite browser and navigate to http://yourdomain.com/install.php or http://server-ip/install.php and complete the required the steps to finish the installation. If you are using a firewall, please open port 80 to enable access to the control panel.

Congratulation’s! You have successfully installed Dokuwiki. Thanks for using this tutorial for installing Dokuwiki on your CentOS 7 system. For additional help or useful information, we recommend you to check the official Dokuwiki web site.

Posted by WebProgrammer 1010
분류없음2017.02.21 10:32

$conf['target']['extern'] = '_blank';

Posted by WebProgrammer 1010