Welcome!

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

Related Topics: Weblogic

Weblogic: Article

Show Me Some Commitment - Connecting with Transactions

Show Me Some Commitment - Connecting with Transactions

For several months now I've waxed lyrical about transactions and how they hide the complexities of distributed updates in applications, and indeed the concept of the two-phase commit transaction is a very powerful one, allowing you to make the assumption that all the transactional data stores that hold your business data will roll forward or back in lockstep.

However, as with all "under the covers" behavior (if you'll excuse a mixed metaphor), sometimes you need to get inside the kimono to get what you really need.

For example, what if you're using a bean-managed transaction from a stateful session bean to update state represented by a number of entity beans (a common case)? Although the transaction will ensure the consistency of the entity beans, since the state in the session bean is not held in a transactional resource, it is not impacted whatsoever by the transaction. Now consider the case where the transaction rolls back for some reason. Although all the databases will look as though the transaction never happened, the session bean may have state set in it that makes sense only if the transaction committed.

This sounds a bit desperate! What should we do? Throw out the stateful session bean and keep all the state in entities? Well, we could, but if we have no requirements for long-term persistence of the state, there's no reason to weigh a database down with it, and to split the state from the function would break the encapsulation that the session bean provided. You might think that there must be a more elegant solution, and there is...

JTA provides a session synchronization interface, javax.ejb.SessionSynchronization. This is how you, as an application developer, can request that JTA open its kimono to you. Through this interface you provide three callback functions that the JTA subsystem can use to notify your code of what it's doing behind the scenes. The three methods provided are afterBegin(), beforeCompletion(), and afterCompletion().

To digress a moment for the pedantic, this interface is actually provided by the EJB container. Only the latter two methods map directly onto JTA interfaces as such. In the context of a raw user of JTA, an afterBegin method would make no sense, since the transaction would begin under the control of the application code. In the EJB world, a container-managed transaction could be begun on behalf of the logic by the container, and the afterBegin() notification is the EJB container's way of letting your code know that this has happened. The "raw" JTA equivalent of this interface is in fact called javax.transaction.Synchronization.

Anyway, back to the plot... through the synchronization interface, your stateful session beans can register for notification of when the "under the covers" transactional behaviors take place. If you'll excuse another brief digression, I have a colleague at BEA who has a pathological hatred of stateful session beans. He recommends using them in only two cases: if you need to keep session state in a J2EE application and can't rely on an HTTP front end (and hence, can't use an HTTP session object), or if you need to respond to transactional events - while an HTTP session object can't easily register for these events, the EJB container provides the machinery to do this easily. The fact that this particular individual can be persuaded to use a stateful session bean at all indicates the potential power of linking to JTA in this way.

So, as you by now suspect, the typical use case of the SessionSynchronization interface is a stateful session bean with its beforeCompletion method containing an implementation that flushes any state that may have been cached before the commit processing begins (of course, if state is cached when the transaction is committed, then it will never be written to the back-end storage). The afterCompletion implementation, when the final result is a JTA rollback, will likely return the session state to some values saved prior to its commencement.

As a final note, the afterBegin and beforeCompletion methods are called in the scope of the transaction to which they refer, so any updates they make to transactional stores will be included in the transaction, along with whatever updates are caused by the business logic. Clearly, the afterCompletion method cannot be called in the context of the transaction since it has by that stage, by definition, completed.

"Groundhog Day" for JTA
That's all well and good - using the session synchronization interface we have a way to make our stateful session beans' state pseudo-transactional, and we have a placeholder to allow for session state to be cached at application level should this be necessary. Before the story ends and we live happily ever after, however, a few moments would be well spent thinking through the implications of that innocuous-looking previous paragraph...

Consider again that the beforeCompletion method must be called before the two-phase commit process can start. Also remember that the whole point of JTA is that an arbitrary number of objects can be bound together in a single transaction. Given this, it will quickly become apparent that the job of the JTA subsystem at commit time is to call all the beforeCompletion methods registered with the transaction before commencing the conventional two-phase commit processing with the underlying data stores also registered with the transaction. It is this characteristic that has sometimes led object-based transaction monitors to be described as performing a "two- and-a-half-phase commit."

This sounds simple until you realize that not only is the list of beforeCompletion methods dynamic, but since all of them are called in the context of the transaction themselves, any of them could cause the list itself to grow. Imagine the scenario where stateful session beans S1 and S2 both implement beforeCompletion methods. A business method on S1 is called, causing a transaction to be started and resulting in two entity beans, E1 and E2, being involved in the transaction.

Now it's commit time. The JTA subsystem goes to commit the transaction. For the first "half phase" it sees that the beforeCompletion method on S1 needs to be called. Imagine that this method calls the second session bean, S2. During the first half phase another beforeCompletion method has been added to the list. S1's beforeCompletion method returns, and the JTA subsystem realizes that S2's beforeCompletion method is now in the list and needs to be called, so JTA makes the call. If S2's beforeCompletion method has no side effects, then on its return JTA can start the two-phase commit proper. However, if S2's beforeCompletion method has invoked a method on S1, then suddenly S1's method is back in the list. Despite the fact that it has already been called, the state of S1 may have been changed by the latest call, so it will need to be called again.

You can see from this that we have created Groundhog Day for the JTA subsystem. As fast as it tries to cross beforeCompletion methods off its list, new ones are added. This will cause an infinite loop, which may provide entertainment for anyone who has sadistic inclinations toward application servers - for most normal people, this will just be a bad case of bad news. In fact, I have bad news for the sadists too... the WebLogic developers thought of this, which provides an explanation of one of the more obscure JTA configuration parameters, the "beforeCompletionIterationLimit". This parameter is set on a JTA-wide basis by the administrator and limits the number of times that JTA will loop around trying to cross beforeCompletion methods off a transaction's list before it will just give up and abort the transaction. Clearly, identifying one of these infinite loop, Groundhog Day-type situations by code inspection as a developer requires a view of the implementations of all the beforeCompletion methods in a transaction and is likely to be pretty difficult to spot and fix, particularly in situations where old beans are being reused in new transactional scenarios.

Based on this, I would propose a best practice for the implementation of beforeCompletion methods.

Safest of all will be those that do nothing but touch the in-memory state of the session bean of which they form a part. Next safest will be those that directly access XA resources (for example, by direct JDBC access through a TxDataSource to a database). The most dangerous will be those that call external J2EE components. As soon as you invoke external components, you lose control over exactly what resources will be touched, and hence potentially unwittingly send WebLogic into Groundhog Day until the beforeCompletionIterationlimit is reached. Consequently, I recommend that beforeCompletion methods do not invoke external components.

So that's all for this month, more transaction-related chat real soon ...
So that's all for this month, more transaction-related chat real soon ...
So that's all for this month, more transaction-related chat real soon ...

Oops, is there a configurable limit for this kind of thing?

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.


@ThingsExpo Stories
In his session at 21st Cloud Expo, Carl J. Levine, Senior Technical Evangelist for NS1, will objectively discuss how DNS is used to solve Digital Transformation challenges in large SaaS applications, CDNs, AdTech platforms, and other demanding use cases. Carl J. Levine is the Senior Technical Evangelist for NS1. A veteran of the Internet Infrastructure space, he has over a decade of experience with startups, networking protocols and Internet infrastructure, combined with the unique ability to it...
"There's plenty of bandwidth out there but it's never in the right place. So what Cedexis does is uses data to work out the best pathways to get data from the origin to the person who wants to get it," explained Simon Jones, Evangelist and Head of Marketing at Cedexis, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"Cloud Academy is an enterprise training platform for the cloud, specifically public clouds. We offer guided learning experiences on AWS, Azure, Google Cloud and all the surrounding methodologies and technologies that you need to know and your teams need to know in order to leverage the full benefits of the cloud," explained Alex Brower, VP of Marketing at Cloud Academy, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clar...
Large industrial manufacturing organizations are adopting the agile principles of cloud software companies. The industrial manufacturing development process has not scaled over time. Now that design CAD teams are geographically distributed, centralizing their work is key. With large multi-gigabyte projects, outdated tools have stifled industrial team agility, time-to-market milestones, and impacted P&L stakeholders.
Gemini is Yahoo’s native and search advertising platform. To ensure the quality of a complex distributed system that spans multiple products and components and across various desktop websites and mobile app and web experiences – both Yahoo owned and operated and third-party syndication (supply), with complex interaction with more than a billion users and numerous advertisers globally (demand) – it becomes imperative to automate a set of end-to-end tests 24x7 to detect bugs and regression. In th...
"Akvelon is a software development company and we also provide consultancy services to folks who are looking to scale or accelerate their engineering roadmaps," explained Jeremiah Mothersell, Marketing Manager at Akvelon, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"MobiDev is a software development company and we do complex, custom software development for everybody from entrepreneurs to large enterprises," explained Alan Winters, U.S. Head of Business Development at MobiDev, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
SYS-CON Events announced today that CrowdReviews.com has been named “Media Sponsor” of SYS-CON's 22nd International Cloud Expo, which will take place on June 5–7, 2018, at the Javits Center in New York City, NY. CrowdReviews.com is a transparent online platform for determining which products and services are the best based on the opinion of the crowd. The crowd consists of Internet users that have experienced products and services first-hand and have an interest in letting other potential buye...
"IBM is really all in on blockchain. We take a look at sort of the history of blockchain ledger technologies. It started out with bitcoin, Ethereum, and IBM evaluated these particular blockchain technologies and found they were anonymous and permissionless and that many companies were looking for permissioned blockchain," stated René Bostic, Technical VP of the IBM Cloud Unit in North America, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Conventi...
SYS-CON Events announced today that Telecom Reseller has been named “Media Sponsor” of SYS-CON's 22nd International Cloud Expo, which will take place on June 5-7, 2018, at the Javits Center in New York, NY. Telecom Reseller reports on Unified Communications, UCaaS, BPaaS for enterprise and SMBs. They report extensively on both customer premises based solutions such as IP-PBX as well as cloud based and hosted platforms.
"Space Monkey by Vivent Smart Home is a product that is a distributed cloud-based edge storage network. Vivent Smart Home, our parent company, is a smart home provider that places a lot of hard drives across homes in North America," explained JT Olds, Director of Engineering, and Brandon Crowfeather, Product Manager, at Vivint Smart Home, in this SYS-CON.tv interview at @ThingsExpo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Coca-Cola’s Google powered digital signage system lays the groundwork for a more valuable connection between Coke and its customers. Digital signs pair software with high-resolution displays so that a message can be changed instantly based on what the operator wants to communicate or sell. In their Day 3 Keynote at 21st Cloud Expo, Greg Chambers, Global Group Director, Digital Innovation, Coca-Cola, and Vidya Nagarajan, a Senior Product Manager at Google, discussed how from store operations and ...
It is of utmost importance for the future success of WebRTC to ensure that interoperability is operational between web browsers and any WebRTC-compliant client. To be guaranteed as operational and effective, interoperability must be tested extensively by establishing WebRTC data and media connections between different web browsers running on different devices and operating systems. In his session at WebRTC Summit at @ThingsExpo, Dr. Alex Gouaillard, CEO and Founder of CoSMo Software, presented ...
WebRTC is great technology to build your own communication tools. It will be even more exciting experience it with advanced devices, such as a 360 Camera, 360 microphone, and a depth sensor camera. In his session at @ThingsExpo, Masashi Ganeko, a manager at INFOCOM Corporation, introduced two experimental projects from his team and what they learned from them. "Shotoku Tamago" uses the robot audition software HARK to track speakers in 360 video of a remote party. "Virtual Teleport" uses a multip...
A strange thing is happening along the way to the Internet of Things, namely far too many devices to work with and manage. It has become clear that we'll need much higher efficiency user experiences that can allow us to more easily and scalably work with the thousands of devices that will soon be in each of our lives. Enter the conversational interface revolution, combining bots we can literally talk with, gesture to, and even direct with our thoughts, with embedded artificial intelligence, whic...
SYS-CON Events announced today that Evatronix will exhibit at SYS-CON's 21st International Cloud Expo®, which will take place on Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. Evatronix SA offers comprehensive solutions in the design and implementation of electronic systems, in CAD / CAM deployment, and also is a designer and manufacturer of advanced 3D scanners for professional applications.
Leading companies, from the Global Fortune 500 to the smallest companies, are adopting hybrid cloud as the path to business advantage. Hybrid cloud depends on cloud services and on-premises infrastructure working in unison. Successful implementations require new levels of data mobility, enabled by an automated and seamless flow across on-premises and cloud resources. In his general session at 21st Cloud Expo, Greg Tevis, an IBM Storage Software Technical Strategist and Customer Solution Architec...
To get the most out of their data, successful companies are not focusing on queries and data lakes, they are actively integrating analytics into their operations with a data-first application development approach. Real-time adjustments to improve revenues, reduce costs, or mitigate risk rely on applications that minimize latency on a variety of data sources. In his session at @BigDataExpo, Jack Norris, Senior Vice President, Data and Applications at MapR Technologies, reviewed best practices to ...
An increasing number of companies are creating products that combine data with analytical capabilities. Running interactive queries on Big Data requires complex architectures to store and query data effectively, typically involving data streams, an choosing efficient file format/database and multiple independent systems that are tied together through custom-engineered pipelines. In his session at @BigDataExpo at @ThingsExpo, Tomer Levi, a senior software engineer at Intel’s Advanced Analytics gr...
When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things’). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing? IoT is not about the devices, it’s about the data consumed and generated. The devices are tools, mechanisms, conduits. In his session at Internet of Things at Cloud Expo | DXWor...