Shulou(Shulou.com)06/02 Report--

This article mainly introduces "what is the Quartz execution process of java Spring timing tasks". In daily operation, I believe many people have doubts about the Quartz execution process of java Spring timing tasks. Xiaobian consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts of "what is the Quartz execution process of java Spring timing tasks?" Next, please follow the editor to study!

Introduction to the preface

Scheduled tasks are often used in daily development, such as database table scanning and sending MQ, Troun billing, caching data updates, flash sale activity status changes, and so on. Because of the Schedule of Spring, it is very convenient for us to use this kind of scenario. So, how much do you know about it besides the application?

How many task threads are initialized by default

There are several implementations of JobStore. Which one do you usually use?

A brief description of the execution process of a scheduled task

II. Case project

In order to do better source code analysis, we separate the timing task service that is usually used.

1itstack-demo-code-schedule

2 └── src

3 ├── main

4 │ ├── java

5 │ │ └── org.itstack.demo

6 │ │ ├── DemoTask.java

7 │ │ └── JobImpl.java

8 │ └── resources

9 │ ├── props

10 │ │ └── config.properties

11 │ ├── spring

12 │ │ └── spring-config-schedule-task.xml

13 │ ├── logback.xml

14 │ └── spring-config.xml

15 └── test

16 └── java

17 └── org.itstack.demo.test

18 ├── ApiTest.java

19 ├── MyQuartz.java

20 └── MyTask.java

III. Environmental configuration

JDK 1.8

IDEA 2019.3.1

Spring 4.3.24.RELEASE

Quartz 2.3.2 {there are slight code differences between different versions}

IV. Source code analysis 1

2 org.quartz-scheduler

3 quartz

4 2.3.2

five

Depending on the Spring version to upgrade quartz, choose 2.3.2, and if you use xml to configure tasks as shown in this case. Then there will be the following changes

Spring 3.x/org.springframework.scheduling.quart.CronTriggerBean

one

two

three

four

Spring 4.x/org.springframework.scheduling.quartz.CronTriggerFactoryBean

one

two

three

four

Before formal analysis, you can take a look at the default configuration of quartz, where many initialization actions need to get parameters, and you can also configure your own configuration file. For example, when you have a lot of tasks and the 10 thread groups initialized by default do not meet your business needs, you can adjust them as needed.

Quart.properties

1# Default Properties file for use by StdSchedulerFactory

2# to create a Quartz Scheduler Instance, if a different

3# properties file is not explicitly specified.

4#

five

6org.quartz.scheduler.instanceName: DefaultQuartzScheduler

7org.quartz.scheduler.rmi.export: false

8org.quartz.scheduler.rmi.proxy: false

9org.quartz.scheduler.wrapJobExecutionInUserTransaction: false

ten

11org.quartz.threadPool.class: org.quartz.simpl.SimpleThreadPool

12org.quartz.threadPool.threadCount: 10

13org.quartz.threadPool.threadPriority: 5

14org.quartz.threadPool.threadsInheritContextClassLoaderOfInitializingThread: true

fifteen

16org.quartz.jobStore.misfireThreshold: 60000

seventeen

18org.quartz.jobStore.class: org.quartz.simpl.RAMJobStore

1. Start with a simple case.

Usually we use Schedule basically as annotations or xml configuration files, but in order to make it easier to analyze the code, let's start with a simple Demo and put it in the main function.

DemoTask.java & defines a task waiting to be executed

1public class DemoTask {

two

3 private Logger logger = LoggerFactory.getLogger (DemoTask.class)

four

5 public void execute () throws Exception {

6 logger.info ("scheduled processing of user information task: 0ram 5 *?")

7}

eight

9}

MyTask.java & Test class to extract the code configured in xml

1public class MyTask {

two

3 public static void main (String [] args) throws Exception {

four

5 DemoTask demoTask = new DemoTask ()

six

7 / / defines the content of execution

8 MethodInvokingJobDetailFactoryBean methodInvokingJobDetailFactoryBean = new MethodInvokingJobDetailFactoryBean ()

9 methodInvokingJobDetailFactoryBean.setTargetObject (demoTask)

10 methodInvokingJobDetailFactoryBean.setTargetMethod ("execute")

11 methodInvokingJobDetailFactoryBean.setConcurrent (true)

12 methodInvokingJobDetailFactoryBean.setName ("demoTask")

13 methodInvokingJobDetailFactoryBean.afterPropertiesSet ()

fourteen

15 / / defined; the plan of execution

16 CronTriggerFactoryBean cronTriggerFactoryBean = new CronTriggerFactoryBean ()

17 cronTriggerFactoryBean.setJobDetail (methodInvokingJobDetailFactoryBean.getObject ())

18 cronTriggerFactoryBean.setCron_Expression ("0ram 5 *?")

19 cronTriggerFactoryBean.setName ("demoTask")

20 cronTriggerFactoryBean.afterPropertiesSet ()

twenty-one

22 / / realized; performed function

23 SchedulerFactoryBean schedulerFactoryBean = new SchedulerFactoryBean ()

24 schedulerFactoryBean.setTriggers (cronTriggerFactoryBean.getObject ())

25 schedulerFactoryBean.setAutoStartup (true)

26 schedulerFactoryBean.afterPropertiesSet ()

twenty-seven

28 schedulerFactoryBean.start ()

twenty-nine

30 / / pause

31 System.in.read ()

thirty-two

33}

thirty-four

35}

If all goes well, the result will be as follows:

12020-01-04 10 Using default implementation for ThreadExecutor 4715 main INFO org.quartz.impl.StdSchedulerFactory [1220]-Using default implementation for ThreadExecutor

22020-01-04 10 Initialized Scheduler Signaller of type 47 Initialized Scheduler Signaller of type 16.421 [main] INFO org.quartz.core.SchedulerSignalerImpl [61]-class org.quartz.core.SchedulerSignalerImpl

32020-01-04 10 QuartzScheduler 47 created 16.422 [main] INFO org.quartz.core.QuartzScheduler-2.3.2 created.

42020-01-04 10 RAMJobStore initialized 47 RAMJobStore initialized 47 main.

52020-01-04 10 Scheduler meta-data: QuartzScheduler (v2.3.2) 'QuartzScheduler' with instanceId' NON_CLUSTERED'

6 Scheduler class: 'org.quartz.core.QuartzScheduler'-running locally.

7 NOT STARTED.

8 Currently in standby mode.

9 Number of jobs executed: 0

10 Using thread pool 'org.quartz.simpl.SimpleThreadPool'-with 10 threads.

11 Using job-store 'org.quartz.simpl.RAMJobStore'-which does not support persistence. And is not clustered.

twelve

132020-01-04 10 Quartz scheduler 47 main 16.424 [main] INFO org.quartz.impl.StdSchedulerFactory [1374]-Quartz scheduler 'QuartzScheduler' initialized from an externally provided properties instance.

142020-01-04 10 Quartz scheduler version 47 main 424 [main] INFO org.quartz.impl.StdSchedulerFactory [1378]-Quartz scheduler version: 2.3.2

152020-01-04 10 JobFactory set to 47 JobFactory set to 16.426 [main] INFO org.quartz.core.QuartzScheduler [2293]-org.springframework.scheduling.quartz.AdaptableJobFactory@3e9b1010

162020-01-04 10 Scheduler QuartzScheduler_$_NON_CLUSTERED started 47 main INFO org.quartz.core.QuartzScheduler.

January 04, 2020 10:47:16 org.springframework.scheduling.quartz.SchedulerFactoryBean startScheduler

18 Information: Starting Quartz Scheduler now

192020-01-04 10 4720.321 [QuartzScheduler_Worker-1] INFO org.itstack.demo.DemoTask [11]-scheduled processing of user information task: 0ram 5 *?

202020-01-04 10 47V 25.001 [QuartzScheduler_Worker-2] INFO org.itstack.demo.DemoTask [11]-scheduled processing of user information task: 0amp 5 *?

212020-01-04 10 47 30.000 [QuartzScheduler_Worker-3] 30000 [11]-scheduled processing of user information task: 0Compact 5 *?

222020-01-04 10 4715. 001 [QuartzScheduler_Worker-4] INFO org.itstack.demo.DemoTask [11]-scheduled processing of user information task: 0amp 5 *?

232020-01-04 10 47V 40.000 [QuartzScheduler_Worker-5] INFO org.itstack.demo.DemoTask [11]-scheduled processing of user information task: 0ram 5 *?

twenty-four

25Process finished with exit code-1

twenty-six

two。 Define the content of execution (MethodInvokingJobDetailFactoryBean) 1 beat / define the content of execution

2MethodInvokingJobDetailFactoryBean methodInvokingJobDetailFactoryBean = new MethodInvokingJobDetailFactoryBean ()

3methodInvokingJobDetailFactoryBean.setTargetObject (demoTask)

4methodInvokingJobDetailFactoryBean.setTargetMethod ("execute")

5methodInvokingJobDetailFactoryBean.setConcurrent (true)

6methodInvokingJobDetailFactoryBean.setName ("demoTask")

7methodInvokingJobDetailFactoryBean.afterPropertiesSet ()

This piece of content mainly transfers our task body (that is, the task to be executed DemoTask) to MethodInvokingJobDetailFactoryBean management. First, set up the necessary information.

TargetObject: target object bean, that is, demoTask

TargetMethod: target method name, that is, execute

Concurrent: whether to execute tasks in parallel or not. If the previous task is not finished, it will not be executed at the next moment.

Name:xml configuration is not required, and beanName can be obtained in the source code.

Finally, we simulate initialization by manually calling afterPropertiesSet (). If our class is managed by Spring, then the class that implements the InitializingBean interface automatically executes afterPropertiesSet () after the class configuration information is loaded. Generally implement the InitializingBean interface of the class, but also to implement the FactoryBean interface, because this interface can be implemented through T getObject () to get their own custom initialization of the class. This is also often used in some framework development.

MethodInvokingJobDetailFactoryBean.afterPropertiesSet ()

1public void afterPropertiesSet () throws ClassNotFoundException, NoSuchMethodException {

2 prepare ()

3 / / Use specific name if given, else fall back to bean name.

4 String name = (this.name! = null? This.name: this.beanName)

5 / / Consider the concurrent flag to choose between stateful and stateless job.

6 Class jobClass = (this.concurrent? MethodInvokingJob.class: StatefulMethodInvokingJob.class)

7 / / Build JobDetail instance.

8 JobDetailImpl jdi = new JobDetailImpl ()

9 jdi.setName (name)

10 jdi.setGroup (this.group)

11 jdi.setJobClass ((Class) jobClass)

12 jdi.setDurability (true)

13 jdi.getJobDataMap () .put ("methodInvoker", this)

14 this.jobDetail = jdi

fifteen

16 postProcessJobDetail (this.jobDetail)

17}

Line 168 of source code: select task classes according to whether or not to execute in parallel. These two classes are internal classes of MethodInvokingJobDetailFactoryBean. StatefulMethodInvokingJob, which is not executed in parallel, simply inherits MethodInvokingJob and adds markup comments.

171st line of source code: create a JobDetailImpl, add task details, and note that this kind of jdi.setJobClass ((Class) jobClass) is actually MethodInvokingJob. MethodInvokingJob is also what we ultimately want to reflect the execution of the call.

Line 177Source: after initializing the task, assign a value to this.jobDetail = jdi, that is, the final class object

MethodInvokingJobDetailFactoryBean.getObject ()

1@Override

2public JobDetail getObject () {

3 return this.jobDetail

4}

Source code: line 220: this.jobDetail is returned when getting an object, which explains why MethodInvokingJobDetailFactoryBean is assigned directly to a JobDetail after initialization

Official Wechat account: bugstack wormhole stack & Schedule.xml3. Define the execution plan (CronTriggerFactoryBeann) 1 / define; execute the plan

2CronTriggerFactoryBean cronTriggerFactoryBean = new CronTriggerFactoryBean ()

3cronTriggerFactoryBean.setJobDetail (methodInvokingJobDetailFactoryBean.getObject ())

4cronTriggerFactoryBean.setCron_Expression ("0ram 5 *?")

5cronTriggerFactoryBean.setName ("demoTask")

6cronTriggerFactoryBean.afterPropertiesSet ()

This section mainly defines the execution plan of the task, hands the task execution content to CronTriggerFactoryBean management, and sets the necessary information.

JobDetail: sets the task body. The object can be assigned directly in xml, and the information of the executed JobDetail object can be set in hard coding. This is the JobDetailImpl we set above, which is obtained through getObject ().

CronExpression: plan expression; seconds, minutes, hours, day, month, week, year

CronTriggerFactoryBean.afterPropertiesSet ()

1@Override

2public void afterPropertiesSet () throws ParseException {

three

4 / /... Check attribute information

five

6 CronTriggerImpl cti = new CronTriggerImpl ()

7 cti.setName (this.name)

8 cti.setGroup (this.group)

9 if (this.jobDetail! = null) {

10 cti.setJobKey (this.jobDetail.getKey ())

11}

12 cti.setJobDataMap (this.jobDataMap)

13 cti.setStartTime (this.startTime)

14 cti.setCron_Expression (this.cronExpression)

15 cti.setTimeZone (this.timeZone)

16 cti.setCalendarName (this.calendarName)

17 cti.setPriority (this.priority)

18 cti.setMisfireInstruction (this.misfireInstruction)

19 cti.setDescription (this.description)

20 this.cronTrigger = cti

21}

Line 237 of source code: create trigger CronTriggerImpl and set relevant attribute information

245 lines of source code: generate the execution plan class cti.setCron_Expression (this.cronExpression)

1public void setCron_Expression (String cronExpression) throws ParseException {

2 TimeZone origTz = getTimeZone ()

3 this.cronEx = new Cron_Expression (cronExpression)

4 this.cronEx.setTimeZone (origTz)

5}

CronExpression.java & parsing Cron expressions

1protected void build_Expression (String expression) throws ParseException {

2 expressionParsed = true

3 try {/ /... Initialize TreeSet xxx = new TreeSet ()

four

5 int exprOn = SECOND

6 StringTokenizer exprsTok = new StringTokenizer (expression, "\ t"

7 false)

eight

9 while (exprsTok.hasMoreTokens () & & exprOn instantiate ()

1323 lines of source code: tp.initialize ()

5. Start a scheduled task

In this case, a hard-coded call to schedulerFactoryBean.start () is used to start the thread service. Thread collaboration is achieved through Object sigLock, and the sigLock.wait () methods are all in the run method of QuartzSchedulerThread, so sigLock wakes up only thread QuartzSchedulerThread. The core process is as follows

Official account of Wechat: bugstack wormhole stack & scheduling startup process

During this startup process, the core code class is as follows

StdScheduler

QuartzScheduler

QuartzSchedulerThread

ThreadPool

RAMJobStore

CronTriggerImpl

JobRunShellFactory

QuartzScheduler.start () & start

1public void start () throws SchedulerException {

two

3 if (shuttingDown | | closed) {

4 throw new SchedulerException (

5 "The Scheduler cannot be restarted after shutdown () has been called.")

6}

seven

8 / / QTZ-212: calling new schedulerStarting () method on the listeners

9 / / right after entering start ()

10 notifySchedulerListenersStarting ()

eleven

12 if (initialStart = = null) {

13 initialStart = new Date ()

14 this.resources.getJobStore () .schedulerStarted ()

15 startPlugins ()

16} else {

17 resources.getJobStore () .schedulerResumed ()

18}

nineteen

20 / / Wake up thread

21 schedThread.togglePause (false)

twenty-two

23 getLog () .info

24 "Scheduler" + resources.getUniqueIdentifier () + "started.")

twenty-five

26 notifySchedulerListenersStarted ()

27}

QuartzSchedulerThread.run () & execution process

1@Override

2public void run () {

3 int acquiresFailed = 0

four

5 / / only if the halt () method is called will the endless loop be exited.

6 while (! halted.get ()) {

7 try {

eight

9 / 1. If it is paused, the loop times out and waits for 1000 milliseconds

ten

11 / / wait a bit, if reading from job store is consistently failing (e.g. DB is down or restarting)..

twelve

13 / / Block until idle threads are available and return the number of available

14 int availThreadCount = qsRsrcs.getThreadPool () .blockForAvailableThreads ()

15 if (availThreadCount > 0) {

sixteen

17 List triggers

18 long now = System.currentTimeMillis ()

19 clearSignaledSchedulingChange ()

twenty

21 try {

22 / / 2. Get the Trigger list of acquire status, that is, the tasks to be performed

23 triggers = qsRsrcs.getJobStore () .acquireNextTriggers

24 now + idleWaitTime, Math.min (availThreadCount, qsRsrcs.getMaxBat

25 acquiresFailed = 0

26 if (log.isDebugEnabled ())

27 log.debug ("batch acquisition of" + (triggers = = null? 0: triggers

28} catch () {/ /...}

twenty-nine

30 if (triggers! = null & &! triggers.isEmpty ()) {

thirty-one

32 / / 3: get the next trigger time of the first Trigger of List

33 long triggerTime = triggers.get (0). GetNextFireTime (). GetTime ()

thirty-four

35 / / IV: get the task trigger set

36 List res = qsRsrcs.getJobStore () .triggersFired (triggers)

thirty-seven

38 / / 5: set Triggers to 'executing' status

39 qsRsrcs.getJobStore () .releaseAcquiredTrigger (triggers.get (I)

forty

41 / / VI: create JobRunShell

42 qsRsrcs.getJobRunShellFactory () createJobRunShell (bndle)

forty-three

44 / 7: execute Job

45 qsRsrcs.getThreadPool () .runInThread (shell)

forty-six

47 continue; / / while (! halted)

48}

49} else {/ / if (availThreadCount > 0)

50 / / should never happen, if threadPool.blockForAvailableThreads () follows con

51 continue; / / while (! halted)

52}

fifty-three

fifty-four

55} catch (RuntimeException re) {

56 getLog () .error ("Runtime error occurred in main trigger firing loop." re)

57}

58}

fifty-nine

60 qs = null

61 qsRsrcs = null

62}

The code to execute the business logic is in the runInThread (shell) method.

QuartzSchedulerThread.run () & part of the code

1JobRunShell shell = null

2try {

3 shell = qsRsrcs.getJobRunShellFactory () .createJobRunShell (bndle)

4 shell.initialize (qs)

5} catch (SchedulerException se) {

6 qsRsrcs.getJobStore () .triggeredJobComplete (triggers.get (I), bndle.getJobDetail (), CompletedExecutionInstruction.SET_ALL_JOB_TRIGGERS_ERROR)

7 continue

8}

398 lines of source code: qsRsrcs.getThreadPool () .runInThread (shell)

SimpleThreadPool.runInThread

1Universe / saves a collection of all WorkerThread

2private List workers

3Universe / idle WorkerThread collection

4private LinkedList availWorkers = new LinkedList ()

5 WorkerThread collection of tasks / tasks

6private LinkedList busyWorkers = new LinkedList ()

seven

8Candle *

9 * maintain three list data: workers, availWorkers and busyWorkers

10 * there is a task that needs a thread to execute: availWorkers.removeFirst (); busyWorkers.add ()

11 * then call the WorkThread.run (runnable) method

12 * /

13public boolean runInThread (Runnable runnable) {

14 if (runnable = = null) {

15 return false

16} synchronized (nextRunnableLock) {

seventeen

18 handoffPending = true

nineteen

20 / / Wait until a worker thread is available

21 while (availWorkers.size ()

< 1) && !isShutdown) { 22 try { 23 nextRunnableLock.wait(500); 24 } catch (InterruptedException ignore) { 25 } 26 } 27 28 if (!isShutdown) { 29 WorkerThread wt = (WorkerThread)availWorkers.removeFirst(); 30 busyWorkers.add(wt); 31 wt.run(runnable); 32 } else { 33 // If the thread pool is going down, execute the Runnable 34 // within a new additional worker thread (no thread from the pool). 35 36 WorkerThread wt = new WorkerThread(this, threadGroup, 37 "WorkerThread-LastJob", prio, isMakeThreadsDaemons(), runnable); 38 busyWorkers.add(wt); 39 workers.add(wt); 40 wt.start(); 41 } 42 nextRunnableLock.notifyAll(); 43 handoffPending = false; 44} 45 46return true; 47} 源码428行： WorkerThread ，是一个内部类，主要是赋值并唤醒lock对象的等待线程队列 WorkerThread.run(Runnable newRunnable) 1public void run(Runnable newRunnable) { 2 synchronized(lock) { 3 if(runnable != null) { 4 throw new IllegalStateException("Already running a Runnable!"); 5 } 6 runnable = newRunnable; 7 lock.notifyAll(); 8 } 9} 源码561行： WorkerThread 的run方法，方法执行lock.notifyAll()后，对应的WorkerThread就会来到run()方法。到这！接近曙光了！终于来到了执行业务的execute()方法的倒数第二步，runnable对象是一个JobRunShell对象，下面在看JobRunShell.run()方法。 WorkerThread.run() 1@Override 2public void run() { 3 boolean ran = false;while (run.get()) { 4 try { 5 synchronized(lock) { 6 while (runnable == null && run.get()) { 7 lock.wait(500); 8 } 9 if (runnable != null) { 10 ran = true; 11 // 启动真正执行的内容，runnable就是JobRunShell 12 runnable.run(); 13 } 14 } 15 } cache(){//...} 16} 17//if (log.isDebugEnabled()) 18try { 19 getLog().debug("WorkerThread is shut down."); 20} catch(Exception e) { 21 // ignore to help with a tomcat glitch 22} 23} JobRunShell.run() & 从上面WorkerThread.run()，调用到这里执行 1public void run() { 2 qs.addInternalSchedulerListener(this); 3 4 try { 5 OperableTrigger trigger = (OperableTrigger) jec.getTrigger(); 6 JobDetail jobDetail = jec.getJobDetail(); 7 8 do { 9 // ... 10 11 long startTime = System.currentTimeMillis(); 12 long endTime = startTime; 13 14 // execute the job 15 try { 16 log.debug("Calling execute on job " + jobDetail.getKey()); 17 18 // 执行业务代码，也就是我们的task 19 job.execute(jec); 20 21 endTime = System.currentTimeMillis(); 22 } catch (JobExecutionException jee) { 23 endTime = System.currentTimeMillis(); 24 jobExEx = jee; 25 getLog().info("Job " + jobDetail.getKey() + 26 " threw a JobExecutionException: ", jobExEx); 27 } catch (Throwable e) { 28 endTime = System.currentTimeMillis(); 29 getLog().error("Job " + jobDetail.getKey() + 30 " threw an unhandled Exception: ", e); 31 SchedulerException se = new SchedulerException( 32 "Job threw an unhandled exception.", e); 33 qs.notifySchedulerListenersError("Job (" 34 + jec.getJobDetail().getKey() 35 + " threw an exception.", se); 36 jobExEx = new JobExecutionException(se, false); 37 } 38 39 jec.setJobRunTime(endTime - startTime); 40 41 // 其他代码 42 } while (true); 43 44 } finally { 45 qs.removeInternalSchedulerListener(this); 46 } 47} QuartzJobBean.execte() & 继续往下走 1public final void execute(JobExecutionContext context) throws JobExecutionException { 2 try { 3 BeanWrapper bw = PropertyAccessorFactory.forBeanPropertyAccess(this); 4 MutablePropertyValues pvs = new MutablePropertyValues(); 5 pvs.addPropertyValues(context.getScheduler().getContext()); 6 pvs.addPropertyValues(context.getMergedJobDataMap()); 7 bw.setPropertyValues(pvs, true); 8 } 9 catch (SchedulerException ex) { 10 throw new JobExecutionException(ex); 11 } 12 executeInternal(context); 13} MethodInvokingJobDetailFactoryBean->

MethodInvokingJob.executeInternal (JobExecutionContext context)

1protected void executeInternal (JobExecutionContext context) throws JobExecutionException {

2 try {

3 / / reflection executes the business code

4 context.setResult (this.methodInvoker.invoke ())

5}

6 catch (InvocationTargetException ex) {

7 if (ex.getTargetException () instanceof JobExecutionException) {

8 / /-> JobExecutionException, to be logged at info level by Quartz

9 throw (JobExecutionException) ex.getTargetException ()

10}

11 else {

12 /-> "unhandled exception", to be logged at error level by Quartz

13 throw new JobMethodInvocationFailedException (this.methodInvoker, ex.getTargetException ())

14}

15}

16 catch (Exception ex) {

17 /-> "unhandled exception", to be logged at error level by Quartz

18 throw new JobMethodInvocationFailedException (this.methodInvoker, ex)

19}

20}

At this point, the study on "what is the Quartz execution process of java Spring scheduled tasks" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.