Welcome!

Java Authors: Trevor Parsons, Carmen Gonzalez, Elizabeth White, Sematext Blog, Kevin Benedict

Related Topics: Java, Open Source, AJAX & REA

Java: Article

Asynchronous Logging Using Spring

Create applications that require high-volume logging without impacting an application’s performance

Each application developer faces the problem of logging usage information. On the one hand, the more logging that's done the easier it is to detect and locate the source of problems. On the other hand, large volume logging might impair an application's performance.

This problem is typically solved by defining various log levels dependent on a program's maturity. For example, a program in developmental stages would have a higher logging requirements; logging requirements would be relatively lower in the production phase. If an application requires a lot of logging for audit purposes, then special measures are required to protect performance.

This article provides a possible solution for this problem by using Spring asynchronous support.

Rationale for High-Volume Logging
Logging is used extensively to help find problems within applications. A developer who finds a problem can investigate it by enabling debug logging. He may then reproduce the problem, or create additional logging if needed. Programmers usually require extensive logging to locate problems.

However, the aforementioned process is not a universal solution. If a developer comes across a one-time event that does not happen again, then he has to uncover and fix the problem using only existing log data. For instance, a security problem should not be resolved by enabling full logging and waiting for another intrusion. Such cases require a lot of logging upfront.

Above and beyond the use of logging for application development, regulatory compliance requirements also demand a minimum amount of logging.

Possible Solutions
The simplest solution would be to log everything synchronously, right inside business logic methods. Of course this solution would reduce processing speed, but if an application does not have strict performance requirements, it might not be a problem.

A developer may also use some existing solutions, such as synchronous logging. Examples include log4j, AsyncAppender, and JMS. The latter is especially useful if none of the logging events should be lost.

Very often logging operations are not very fast because, for reliability purposes, these logs are often written either to a database or to a remote server. In addition, data may be subject to operations before they can be logged.

Consider a simple case when logging is needed, but performance should not be affected.

Please note that threads may not necessarily execute in the same order as they were called, so you'll have to sort the logged events by timestamp in order to have them in chronological order.

Spring 3.0 Asynchronous Support
Overview

Spring 2.0 provided a TaskExecutor abstraction that could be used for running asynchronous tasks. Evolution to version 3.0 enabled annotations to be used for this purpose. Refer to the Task Execution and Scheduling section in the Spring 3.0 documentation.

There are several built-in TaskExecutor implementations, and not all of them are asynchronous. For example, the SyncTaskExecutor invokes a task in the calling thread.

This article will concentrate on the ThreadPoolTaskExecutor - the most commonly used implementation in the Java 5 environment.

The ThreadPoolTaskExecutor provides the following configurable parameters:

pool-size: Defines the size of a pool; it also accepts a "core-max" range. The "core" is the initial number of threads in a pool; the "max" is the maximum number of threads. If only one number is defined, then the core and max are the same size.

Please note that the executor will first use the core number of threads, and then add threads to the pool only when the queue is full.

queue-capacity: Refers to the size of the task queue when all threads are busy. By default the queue is unlimited. That might lead to an OutOfMemory exception and disrupt the application, therefore, a specific queue size should be defined.

rejection-policy: A parameter that determines what should happen if both the thread pool and queue are full. In this case the task is rejected, and then the rejection policy determines what should happen to it.

The following policies are supported:

  • AbortPolicy: Executor will throw a TaskRejectedException
  • DiscardPolicy: Tasks will be skipped
  • DiscardOldestPolicy: Oldest tasks will be skipped
  • CallerRunsPolicy: Task will be executed in caller thread (synchronously)

Spring 3.0 allows bean configuration using both Annotations and XML. We will consider Annotation and XML configuration of TaskExecutors only.

Here is a simple business class that requires logging.

@Service
public class BankOperator {

@Autowired

private BusinessLogger businessLogger;

public void transferMoney() {

//... business logic for transferring money
// writing log
businessLogger.logMoneyTransfer(new Date(), "John", new BigDecimal(100));
}
}

As you can see the businessLogger has a specific method for a specific business operation. Developers always pass the current timestamp and a number of parameters. The timestamp is needed because the logging method will be invoked asynchronously at an arbitrary time in the future. The list of parameters will depend on what kind of logging is done. Usually this kind of logging is saved to a database, so developers need a number of parameters that will be mapped to the fields of the database table.

The maximum possible amount of operations should utilize asynchronous logging.

For example, if logging information depends on an account number, years of service and the balance of a bank account, then it's better to pass these three parameters to a logging method. The logging logic would be implemented, thereby, lessening the influence of logging on execution of the primary service.

XML - configuration
The configuration of ThreadPoolTaskExecutor looks like this:

<bean id="businessLogExecutor" class="org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor">
<property name="corePoolSize" value="1" />
<property name="maxPoolSize" value="1" />
<property name="queueCapacity" value="1" />
<property name="rejectedExecutionHandler" ref="callerRuns" />
</bean>

<bean id="callerRuns" class="java.util.concurrent.ThreadPoolExecutor.CallerRunsPolicy"/>

Spring 3.0 enables developers to use the ‘executor' element to create a ThreadPoolTaskExecutor instance:

<task:executor id="businessLogExecutor"
pool-size="5-25"
queue-capacity="100"
rejection-policy="CALLER_RUNS"/>

The logger class might look like the following:

public class AsyncBusinessLogger implements BusinessLogger {

private TaskExecutor taskExecutor;


public void setTaskExecutor(TaskExecutor taskExecutor) {

this.taskExecutor = taskExecutor;
}

public void logMoneyTransfer(final Date timestamp, final String customerName, final BigDecimal sum) {

taskExecutor.execute(new Runnable() {
public void run() {
System.out.println("Customer '" + customerName + "' transfered $" + sum + " on " + timestamp);
}
});
}
}

A BusinessLogger may resemble the following:

<bean id="businessLogger" class="com.axmor.async.logging.AsyncBusinessLogger">
<property name="taskExecutor" ref="businessLogExecutor" />
</bean>

Using XML configuration is a more flexible approach. A developer can tell many Business Loggers to use the same TaskExecutor, or tell a single Business Logger to use multiple TaskExecutors.

@Async annotation
To use the @Async annotation, turn on task annotation support by including the following in config.xml:

<task:annotation-driven />

In this case, the ThreadPoolTaskExecutor with default settings will be used.

To use the aforementioned executor, insert the following instead:

<task:annotation-driven executor="businessLogExecutor"/>

The logger will look like the following:

@Service
public class AsyncBusinessLogger implements BusinessLogger {

@Async

public void logMoneyTransfer(Date timestamp, String customerName, BigDecimal sum) {
System.out.println("Customer '" + customerName + "' transfered $" + sum + " on " + timestamp);
}
}

The result is simpler and cleaner code. But a less flexible configuration comes at a price: all methods annotated with @Async will use the same TaskExecutor throughout the application.

@Async vs TaskExecutor: when to use
Using the @Async annotation is much simpler than having to wire the task executor to call tasks manually.

Usually the @Async annotation is the preferred method.

In cases where a developer doesn't want to use a single TaskExecutor for all asynchronous operations, which is the case for @Async annotation, he will have to use TaskExecutors.

Conclusion
Developers should strongly consider using asynchronous logging when creating applications that require high-volume logging without impacting an application's performance.

The article shows how easy it is to create your own custom asynchronous logging using Spring 3.0 Async support.

More Stories By Mylnikov Sergey

Mylnikov Sergey is a senior software engineer in the IBM Solution Group at Axmor Software. He has over seven years of experience in software development, as well as strong knowledge in Java SE/EE and web application development. He has been a technical lead and software architect in several successfully completed enterprise projects for US, UK, and Australian customers.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@ThingsExpo Stories
The 3rd International Internet of @ThingsExpo, co-located with the 16th International Cloud Expo - to be held June 9-11, 2015, at the Javits Center in New York City, NY - announces that its Call for Papers is now open. The Internet of Things (IoT) is the biggest idea since the creation of the Worldwide Web more than 20 years ago.
Technology is enabling a new approach to collecting and using data. This approach, commonly referred to as the "Internet of Things" (IoT), enables businesses to use real-time data from all sorts of things including machines, devices and sensors to make better decisions, improve customer service, and lower the risk in the creation of new revenue opportunities. In his General Session at Internet of @ThingsExpo, Dave Wagstaff, Vice President and Chief Architect at BSQUARE Corporation, discuss the real benefits to focus on, how to understand the requirements of a successful solution, the flow of ...
"People are a lot more knowledgeable about APIs now. There are two types of people who work with APIs - IT people who want to use APIs for something internal and the product managers who want to do something outside APIs for people to connect to them," explained Roberto Medrano, Executive Vice President at SOA Software, in this SYS-CON.tv interview at Cloud Expo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
We’re no longer looking to the future for the IoT wave. It’s no longer a distant dream but a reality that has arrived. It’s now time to make sure the industry is in alignment to meet the IoT growing pains – cooperate and collaborate as well as innovate. In his session at @ThingsExpo, Jim Hunter, Chief Scientist & Technology Evangelist at Greenwave Systems, will examine the key ingredients to IoT success and identify solutions to challenges the industry is facing. The deep industry expertise behind this presentation will provide attendees with a leading edge view of rapidly emerging IoT oppor...
In this Women in Technology Power Panel at 15th Cloud Expo, moderated by Anne Plese, Senior Consultant, Cloud Product Marketing at Verizon Enterprise, Esmeralda Swartz, CMO at MetraTech; Evelyn de Souza, Data Privacy and Compliance Strategy Leader at Cisco Systems; Seema Jethani, Director of Product Management at Basho Technologies; Victoria Livschitz, CEO of Qubell Inc.; Anne Hungate, Senior Director of Software Quality at DIRECTV, discussed what path they took to find their spot within the technology industry and how do they see opportunities for other women in their area of expertise.
DevOps Summit 2015 New York, co-located with the 16th International Cloud Expo - to be held June 9-11, 2015, at the Javits Center in New York City, NY - announces that it is now accepting Keynote Proposals. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to wait for long development cycles that produce software that is obsolete at launch. DevOps may be disruptive, but it is essential.
The Industrial Internet revolution is now underway, enabled by connected machines and billions of devices that communicate and collaborate. The massive amounts of Big Data requiring real-time analysis is flooding legacy IT systems and giving way to cloud environments that can handle the unpredictable workloads. Yet many barriers remain until we can fully realize the opportunities and benefits from the convergence of machines and devices with Big Data and the cloud, including interoperability, data security and privacy.
Wearable devices have come of age. The primary applications of wearables so far have been "the Quantified Self" or the tracking of one's fitness and health status. We propose the evolution of wearables into social and emotional communication devices. Our BE(tm) sensor uses light to visualize the skin conductance response. Our sensors are very inexpensive and can be massively distributed to audiences or groups of any size, in order to gauge reactions to performances, video, or any kind of presentation. In her session at @ThingsExpo, Jocelyn Scheirer, CEO & Founder of Bionolux, will discuss ho...
The 3rd International Internet of @ThingsExpo, co-located with the 16th International Cloud Expo - to be held June 9-11, 2015, at the Javits Center in New York City, NY - announces that its Call for Papers is now open. The Internet of Things (IoT) is the biggest idea since the creation of the Worldwide Web more than 20 years ago.
Connected devices and the Internet of Things are getting significant momentum in 2014. In his session at Internet of @ThingsExpo, Jim Hunter, Chief Scientist & Technology Evangelist at Greenwave Systems, examined three key elements that together will drive mass adoption of the IoT before the end of 2015. The first element is the recent advent of robust open source protocols (like AllJoyn and WebRTC) that facilitate M2M communication. The second is broad availability of flexible, cost-effective storage designed to handle the massive surge in back-end data in a world where timely analytics is e...

ARMONK, N.Y., Nov. 20, 2014 /PRNewswire/ --  IBM (NYSE: IBM) today announced that it is bringing a greater level of control, security and flexibility to cloud-based application development and delivery with a single-tenant version of Bluemix, IBM's platform-as-a-service. The new platform enables developers to build ap...

Building low-cost wearable devices can enhance the quality of our lives. In his session at Internet of @ThingsExpo, Sai Yamanoor, Embedded Software Engineer at Altschool, provided an example of putting together a small keychain within a $50 budget that educates the user about the air quality in their surroundings. He also provided examples such as building a wearable device that provides transit or recreational information. He then reviewed the resources available to build wearable devices at home including open source hardware, the raw materials required and the options available to power s...
The Internet of Things promises to transform businesses (and lives), but navigating the business and technical path to success can be difficult to understand. In his session at @ThingsExpo, Sean Lorenz, Technical Product Manager for Xively at LogMeIn, demonstrated how to approach creating broadly successful connected customer solutions using real world business transformation studies including New England BioLabs and more.
Since 2008 and for the first time in history, more than half of humans live in urban areas, urging cities to become “smart.” Today, cities can leverage the wide availability of smartphones combined with new technologies such as Beacons or NFC to connect their urban furniture and environment to create citizen-first services that improve transportation, way-finding and information delivery. In her session at @ThingsExpo, Laetitia Gazel-Anthoine, CEO of Connecthings, will focus on successful use cases.
Enthusiasm for the Internet of Things has reached an all-time high. In 2013 alone, venture capitalists spent more than $1 billion dollars investing in the IoT space. With "smart" appliances and devices, IoT covers wearable smart devices, cloud services to hardware companies. Nest, a Google company, detects temperatures inside homes and automatically adjusts it by tracking its user's habit. These technologies are quickly developing and with it come challenges such as bridging infrastructure gaps, abiding by privacy concerns and making the concept a reality. These challenges can't be addressed w...
The Domain Name Service (DNS) is one of the most important components in networking infrastructure, enabling users and services to access applications by translating URLs (names) into IP addresses (numbers). Because every icon and URL and all embedded content on a website requires a DNS lookup loading complex sites necessitates hundreds of DNS queries. In addition, as more internet-enabled ‘Things' get connected, people will rely on DNS to name and find their fridges, toasters and toilets. According to a recent IDG Research Services Survey this rate of traffic will only grow. What's driving t...
The Internet of Things is a misnomer. That implies that everything is on the Internet, and that simply should not be - especially for things that are blurring the line between medical devices that stimulate like a pacemaker and quantified self-sensors like a pedometer or pulse tracker. The mesh of things that we manage must be segmented into zones of trust for sensing data, transmitting data, receiving command and control administrative changes, and peer-to-peer mesh messaging. In his session at @ThingsExpo, Ryan Bagnulo, Solution Architect / Software Engineer at SOA Software, focused on desi...
"For over 25 years we have been working with a lot of enterprise customers and we have seen how companies create applications. And now that we have moved to cloud computing, mobile, social and the Internet of Things, we see that the market needs a new way of creating applications," stated Jesse Shiah, CEO, President and Co-Founder of AgilePoint Inc., in this SYS-CON.tv interview at 15th Cloud Expo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
The Internet of Things is tied together with a thin strand that is known as time. Coincidentally, at the core of nearly all data analytics is a timestamp. When working with time series data there are a few core principles that everyone should consider, especially across datasets where time is the common boundary. In his session at Internet of @ThingsExpo, Jim Scott, Director of Enterprise Strategy & Architecture at MapR Technologies, discussed single-value, geo-spatial, and log time series data. By focusing on enterprise applications and the data center, he will use OpenTSDB as an example t...
The industrial software market has treated data with the mentality of “collect everything now, worry about how to use it later.” We now find ourselves buried in data, with the pervasive connectivity of the (Industrial) Internet of Things only piling on more numbers. There’s too much data and not enough information. In his session at @ThingsExpo, Bob Gates, Global Marketing Director, GE’s Intelligent Platforms business, to discuss how realizing the power of IoT, software developers are now focused on understanding how industrial data can create intelligence for industrial operations. Imagine ...