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
SYS-CON Events announced today that Yuasa System will exhibit at the Japan External Trade Organization (JETRO) Pavilion 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. Yuasa System is introducing a multi-purpose endurance testing system for flexible displays, OLED devices, flexible substrates, flat cables, and films in smartphones, wearables, automobiles, and healthcare.
SYS-CON Events announced today that Taica will exhibit at the Japan External Trade Organization (JETRO) Pavilion 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. Taica manufacturers Alpha-GEL brand silicone components and materials, which maintain outstanding performance over a wide temperature range -40C to +200C. For more information, visit http://www.taica.co.jp/english/.
Enterprises have taken advantage of IoT to achieve important revenue and cost advantages. What is less apparent is how incumbent enterprises operating at scale have, following success with IoT, built analytic, operations management and software development capabilities – ranging from autonomous vehicles to manageable robotics installations. They have embraced these capabilities as if they were Silicon Valley startups. As a result, many firms employ new business models that place enormous impor...
SYS-CON Events announced today that SourceForge has been named “Media Sponsor” of 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. SourceForge is the largest, most trusted destination for Open Source Software development, collaboration, discovery and download on the web serving over 32 million viewers, 150 million downloads and over 460,000 active development projects each and every month.
SYS-CON Events announced today that Dasher Technologies 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. Dasher Technologies, Inc. ® is a premier IT solution provider that delivers expert technical resources along with trusted account executives to architect and deliver complete IT solutions and services to help our clients execute their goals, plans and objectives. Since 1999, we'v...
As popularity of the smart home is growing and continues to go mainstream, technological factors play a greater role. The IoT protocol houses the interoperability battery consumption, security, and configuration of a smart home device, and it can be difficult for companies to choose the right kind for their product. For both DIY and professionally installed smart homes, developers need to consider each of these elements for their product to be successful in the market and current smart homes.
SYS-CON Events announced today that MIRAI Inc. will exhibit at the Japan External Trade Organization (JETRO) Pavilion 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. MIRAI Inc. are IT consultants from the public sector whose mission is to solve social issues by technology and innovation and to create a meaningful future for people.
SYS-CON Events announced today that Massive Networks, that helps your business operate seamlessly with fast, reliable, and secure internet and network solutions, has been named "Exhibitor" of 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. As a premier telecommunications provider, Massive Networks is headquartered out of Louisville, Colorado. With years of experience under their belt, their team of...
SYS-CON Events announced today that TidalScale, a leading provider of systems and services, 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. TidalScale has been involved in shaping the computing landscape. They've designed, developed and deployed some of the most important and successful systems and services in the history of the computing industry - internet, Ethernet, operating s...
Widespread fragmentation is stalling the growth of the IIoT and making it difficult for partners to work together. The number of software platforms, apps, hardware and connectivity standards is creating paralysis among businesses that are afraid of being locked into a solution. EdgeX Foundry is unifying the community around a common IoT edge framework and an ecosystem of interoperable components.
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, will discuss how from store operations...
In a recent survey, Sumo Logic surveyed 1,500 customers who employ cloud services such as Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP). According to the survey, a quarter of the respondents have already deployed Docker containers and nearly as many (23 percent) are employing the AWS Lambda serverless computing framework. It’s clear: serverless is here to stay. The adoption does come with some needed changes, within both application development and operations. Tha...
SYS-CON Events announced today that IBM has been named “Diamond Sponsor” of SYS-CON's 21st Cloud Expo, which will take place on October 31 through November 2nd 2017 at the Santa Clara Convention Center in Santa Clara, California.
In his Opening Keynote at 21st Cloud Expo, John Considine, General Manager of IBM Cloud Infrastructure, will lead you through the exciting evolution of the cloud. He'll look at this major disruption from the perspective of technology, business models, and what this means for enterprises of all sizes. John Considine is General Manager of Cloud Infrastructure Services at IBM. In that role he is responsible for leading IBM’s public cloud infrastructure including strategy, development, and offering ...
Infoblox delivers Actionable Network Intelligence to enterprise, government, and service provider customers around the world. They are the industry leader in DNS, DHCP, and IP address management, the category known as DDI. We empower thousands of organizations to control and secure their networks from the core-enabling them to increase efficiency and visibility, improve customer service, and meet compliance requirements.
Join IBM November 1 at 21st Cloud Expo at the Santa Clara Convention Center in Santa Clara, CA, and learn how IBM Watson can bring cognitive services and AI to intelligent, unmanned systems. Cognitive analysis impacts today’s systems with unparalleled ability that were previously available only to manned, back-end operations. Thanks to cloud processing, IBM Watson can bring cognitive services and AI to intelligent, unmanned systems. Imagine a robot vacuum that becomes your personal assistant tha...
With major technology companies and startups seriously embracing Cloud strategies, now is the perfect time to attend 21st Cloud Expo October 31 - November 2, 2017, at the Santa Clara Convention Center, CA, and June 12-14, 2018, at the Javits Center in New York City, NY, and learn what is going on, contribute to the discussions, and ensure that your enterprise is on the right path to Digital Transformation.
Recently, REAN Cloud built a digital concierge for a North Carolina hospital that had observed that most patient call button questions were repetitive. In addition, the paper-based process used to measure patient health metrics was laborious, not in real-time and sometimes error-prone. In their session at 21st Cloud Expo, Sean Finnerty, Executive Director, Practice Lead, Health Care & Life Science at REAN Cloud, and Dr. S.P.T. Krishnan, Principal Architect at REAN Cloud, will discuss how they b...
SYS-CON Events announced today that mruby Forum will exhibit at the Japan External Trade Organization (JETRO) Pavilion 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. mruby is the lightweight implementation of the Ruby language. We introduce mruby and the mruby IoT framework that enhances development productivity. For more information, visit http://forum.mruby.org/.
Digital transformation is changing the face of business. The IDC predicts that enterprises will commit to a massive new scale of digital transformation, to stake out leadership positions in the "digital transformation economy." Accordingly, attendees at the upcoming Cloud Expo | @ThingsExpo at the Santa Clara Convention Center in Santa Clara, CA, Oct 31-Nov 2, will find fresh new content in a new track called Enterprise Cloud & Digital Transformation.