Weblogic Authors: Yeshim Deniz, Elizabeth White, Michael Meiner, Michael Bushong, Avi Rosenthal

Related Topics: Weblogic

Weblogic: Article

Transactions: Driving You to Distraction?

Choose The Type 2 Driver To Help

One definition of a commodity is something that you take for granted.

I'll bet there aren't many readers out there who wake in the morning and exclaim, "Thank goodness there's air in the room to breathe!" Likewise, computer users will seldom give thanks for their operating systems, a proclamation like "praise be to those at AT&T and BSD for giving me Unix!" would likely raise more eyebrows than nods around an average water cooler. Things that are taken so much for granted are ripe for methods such as open source as provisioning mechanisms - at the end of the day, if its interfaces are well known and an implementation works "well enough" and is supported, then who cares if it was written in a garage or a high-tech lab? That's one of the reasons why I think the application server has some way to go before it commoditizes to the point where open source provides a realistic alternative as an underpinning to a business critical deployment - the application server market is small, and the capabilities offered by the market leading app. Servers are too rich (and the standards are evolving too quickly) for that to happen just yet a while.

But I digress (although I'm not sure if it's possible to digress before you have actually started...). This month's article is about a piece of technology that exists somewhere in the twilight zone between commodity and valuable asset - the humble JDBC driver.

One of the main drivers for the widespread adoption of the J2EE platform was the existence of standards that provide a good degree of plug-and-playability in terms of the resources accessing and accessed by the platform. One such principal resource is the SQL database (whose adoption in its own life cycle was fueled by the standard relational model for data access providing some swapability at a different layer of the architecture). The Java standard that makes SQL databases pluggable at this level is, of course, JDBC. At a brief glance, you may be wondering what I am going to write about next, apparently being on the verge of saying that the JDBC driver is yet another commodity, but actually, the truth is, especially in the context of XA transactions, all JDBC drivers were not created equal. My intent this month is to dig a bit deeper into this, and help answer two questions: What's the overhead of XA and what JDBC driver should I use to access my Oracle database in an XA transaction?

What's the Overhead of XA?
Quite a few years ago, when X/Open first created the XA standard, there were no commercial databases that supported it. Then came Oracle 7 (and the other RDBMS products of around the same vintage) and XA moved from nice theory to realistic deployment option and the distributed transaction was finally liberated from the mainframe to roam free across the world of open systems. In those days, it was not unreasonable advice to suggest that architects build all their services to access the database via XA. The performance overhead of XA was small (I dimly remember figures of 5% bandied about) and the 1pc optimization built into Tuxedo (and later brought forward into BEA WebLogic Server's transaction manager) meant that the 5% was all you paid, if you didn't need a distributed transaction for any particular use-case.

These days, the world has moved on, and this advice is in need of amendment - it turns out that with recent versions of Oracle, and Java in the picture, the overhead of accessing the database via XA is considerably more than 5% - some benchmarks put the degradation in throughput caused by using XA as high as 15x in the worst case (and note, this is not the overhead of two-phase commit, simply overhead introduced by the DBMS engine as a result of using xa_begin and xa_commit to delineate transactions).

Clearly, the prudent advice to anyone architecting a J2EE system is, at the very least, to benchmark your application using the XA configuration you need for production to ensure that your exact setup will give the throughput you require from your application, and be prepared to segment your database accesses into those that can use database local transactions and those that require XA for synchronisation with resources external to the database (for example, once and once only guaranteed message delivery from transactional message queues).

What JDBC Driver Should I Use to Access Oracle?
The JDBC standard provides for four different "types" of JDBC drivers. The important ones for this discussion are type 2 (in which the database is accessed via JNI calls from the java layer to Oracle's native OCI libraries) and type 4 (in which a pure Java driver implementation talks across a socket to a remote server, which accesses the database as a proxy for the client)

Looking at this from a "commodity component" perspective, the choice between the type 2 and type 4 drivers might be expected to be academic (with perhaps a slight preference for type 4, given that this doesn't require installation of the database native components on your application server box). This is by and large the case for non-XA database access; however, for XA access the story is somewhat different. In this case, the throughput of the type 2 drivers is somewhat better than that of their type 4 equivalents, but more pronounced is the effect on the database CPU - XA access via the type 4 driver causes dramatically increased CPU utilization on the database server relative to the type 2 equivalent.

So, What's the Conclusion?
As with all performance-type considerations, the main conclusion has to be that you should performance test an exact replica of your intended production configuration in order to determine that its performance will meet your needs. Any benchmark or other comparison of that kind is inherently heavily influenced by the usage patterns of the application, and also any benchmark is a snapshot in time of the state of the system - patches or new releases of the driver code (or the database engine itself) could completely change (hopefully for the better!) the results of any comparison.

However, with the technology where it is today, it seems safe to conclude that you should try to stick to the type 2 driver for XA database access, unless you have a pretty compelling reason to do otherwise.

More Stories By Peter Holditch

Peter Holditch is a senior presales engineer in the UK for Azul Systems. Prior to joining Azul he spent nine years at BEA systems, going from being one of their first Professional Services consultants in Europe and finishing up as a principal presales engineer. He has an R&D background (originally having worked on BEA's Tuxedo product) and his technical interests are in high-throughput transaction systems. "Of the pitch" Peter likes to brew beer, build furniture, and undertake other ludicrously ambitious projects - but (generally) not all at the same time!

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.

IoT & Smart Cities Stories
The platform combines the strengths of Singtel's extensive, intelligent network capabilities with Microsoft's cloud expertise to create a unique solution that sets new standards for IoT applications," said Mr Diomedes Kastanis, Head of IoT at Singtel. "Our solution provides speed, transparency and flexibility, paving the way for a more pervasive use of IoT to accelerate enterprises' digitalisation efforts. AI-powered intelligent connectivity over Microsoft Azure will be the fastest connected pat...
There are many examples of disruption in consumer space – Uber disrupting the cab industry, Airbnb disrupting the hospitality industry and so on; but have you wondered who is disrupting support and operations? AISERA helps make businesses and customers successful by offering consumer-like user experience for support and operations. We have built the world’s first AI-driven IT / HR / Cloud / Customer Support and Operations solution.
Codete accelerates their clients growth through technological expertise and experience. Codite team works with organizations to meet the challenges that digitalization presents. Their clients include digital start-ups as well as established enterprises in the IT industry. To stay competitive in a highly innovative IT industry, strong R&D departments and bold spin-off initiatives is a must. Codete Data Science and Software Architects teams help corporate clients to stay up to date with the mod...
At CloudEXPO Silicon Valley, June 24-26, 2019, Digital Transformation (DX) is a major focus with expanded DevOpsSUMMIT and FinTechEXPO programs within the DXWorldEXPO agenda. Successful transformation requires a laser focus on being data-driven and on using all the tools available that enable transformation if they plan to survive over the long term. A total of 88% of Fortune 500 companies from a generation ago are now out of business. Only 12% still survive. Similar percentages are found throug...
Druva is the global leader in Cloud Data Protection and Management, delivering the industry's first data management-as-a-service solution that aggregates data from endpoints, servers and cloud applications and leverages the public cloud to offer a single pane of glass to enable data protection, governance and intelligence-dramatically increasing the availability and visibility of business critical information, while reducing the risk, cost and complexity of managing and protecting it. Druva's...
BMC has unmatched experience in IT management, supporting 92 of the Forbes Global 100, and earning recognition as an ITSM Gartner Magic Quadrant Leader for five years running. Our solutions offer speed, agility, and efficiency to tackle business challenges in the areas of service management, automation, operations, and the mainframe.
The Jevons Paradox suggests that when technological advances increase efficiency of a resource, it results in an overall increase in consumption. Writing on the increased use of coal as a result of technological improvements, 19th-century economist William Stanley Jevons found that these improvements led to the development of new ways to utilize coal. In his session at 19th Cloud Expo, Mark Thiele, Chief Strategy Officer for Apcera, compared the Jevons Paradox to modern-day enterprise IT, examin...
With 10 simultaneous tracks, keynotes, general sessions and targeted breakout classes, @CloudEXPO and DXWorldEXPO are two of the most important technology events of the year. Since its launch over eight years ago, @CloudEXPO and DXWorldEXPO have presented a rock star faculty as well as showcased hundreds of sponsors and exhibitors! In this blog post, we provide 7 tips on how, as part of our world-class faculty, you can deliver one of the most popular sessions at our events. But before reading...
DSR is a supplier of project management, consultancy services and IT solutions that increase effectiveness of a company's operations in the production sector. The company combines in-depth knowledge of international companies with expert knowledge utilising IT tools that support manufacturing and distribution processes. DSR ensures optimization and integration of internal processes which is necessary for companies to grow rapidly. The rapid growth is possible thanks, to specialized services an...
At CloudEXPO Silicon Valley, June 24-26, 2019, Digital Transformation (DX) is a major focus with expanded DevOpsSUMMIT and FinTechEXPO programs within the DXWorldEXPO agenda. Successful transformation requires a laser focus on being data-driven and on using all the tools available that enable transformation if they plan to survive over the long term. A total of 88% of Fortune 500 companies from a generation ago are now out of business. Only 12% still survive. Similar percentages are found throug...