Welcome!

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

Related Topics: Weblogic

Weblogic: Article

Transaction Not Supported? Just Say No!

Transaction Not Supported? Just Say No!

This month I was again inspired by the weblogic.developer.interest.transaction newsgroup on newsgroups.bea.com - if you weren't listening last time I plugged this newsgroup, listen now; one day, it might save your life!

Be Paranoid, Be Very Afraid
A quick guess at what "NotSupported" does might lead you to wonder if it's just a repeat of Never and worry about the redundancy, whilst musing on "Supported" might make you paranoid about what is really going to happen at runtime. Well, be very afraid of these two innocent- sounding attributes!

As you know if you've used EJB container-managed transactions, you have several options available in declaring your methods' transactional behavior, namely NotSupported, Required, Supports, RequiresNew, Mandatory, or Never. I guess the one with the clearest intent is "RequiresNew" - the method requires a new transaction context, so the container will create one before running the code. Next, "Required" - a transaction is required to run this method, so if the caller didn't supply one, the container will create a new transaction context for the method to run in. In "Mandatory" - the method requires a transaction context and it's an error by the caller to not supply a transaction context prior to the call. Then "Never" - a transaction context must never exist when this method is called, and if one does it's an error. There are still two more options, Supports and NotSupported; these are much less imperative sounding than the other choices and, as always in software design, precision is everything!

"The Supports transaction attribute must be used with caution. This is because of the different transactional semantics provided by the two possible modes of execution. Only the enterprise beans that will execute correctly in both modes should use the Supports transaction attribute." (Section 16.7.2.3)

This is clearly bad news, and anyone with any sense will take this as a cue to give Supports a wide berth unless there is a very good justification for not doing so.

However, the spec gives no such warning about the NotSupported behavior, which I think is rather odd since it is even more dangerous.

The spec argues that the danger with Supports is that it makes your methods behave in different ways, depending on the calling context. This obviously is a bad thing, encouraging close (and hard to spot) coupling between the caller and callee and generally breaking the laws of good practice. At least Supports always behaves in the same way. What's not so clear from this section of the spec is in what consistent way this will behave. It simply makes the innocent-sounding statement that "The Container invokes an enterprise bean method whose transaction attribute is set to NotSupported with an unspecified transaction context." (16.7.2.1)

We Need Scooby Doo!
To get to the bottom of this mystery, we need a detective. After staking out the spec for a while from behind a bush we notice a light on after hours in section 16.7.5. In fact, this whole section is a horror story about the kind of things containers get up to in "unspecified transaction contexts" - I'll not quote it verbatim here, my fingers daren't type that kind of horror, but suffice it to say, containers can do whatever they like - start a new transaction per call, start a new transaction and lump multiple calls together in it, run with no transaction context at all. This all adds up to bad news. Your bean's behavior will change from application server to application server (and could even legitimately change between releases of application server) all this adds up to... zoinks! Portability problems. Which was one of the things you set out to mitigate by using J2EE in the first place. As a footnote, WebLogic's behavior in this situation (in the current release!) is to execute methods on Entity beans in their own fresh transaction context (equivalent to the RequiresNew behavior) and to execute methods on session beans with no active transaction (equivalent to a bean managed bean that hasn't started a transaction).

So, we have unmasked the felon - the innocent-looking unspecified transaction context! Remember kids, the moral of the story is: Don't use NotSupported, Never, or Supports for your container managed transactions, or you'll store up a whole load of grief for yourself (or for whoever inherits your code to maintain!).

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
Nicolas Fierro is CEO of MIMIR Blockchain Solutions. He is a programmer, technologist, and operations dev who has worked with Ethereum and blockchain since 2014. His knowledge in blockchain dates to when he performed dev ops services to the Ethereum Foundation as one the privileged few developers to work with the original core team in Switzerland.
Andrew Keys is Co-Founder of ConsenSys Enterprise. He comes to ConsenSys Enterprise with capital markets, technology and entrepreneurial experience. Previously, he worked for UBS investment bank in equities analysis. Later, he was responsible for the creation and distribution of life settlement products to hedge funds and investment banks. After, he co-founded a revenue cycle management company where he learned about Bitcoin and eventually Ethereal. Andrew's role at ConsenSys Enterprise is a mul...
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
If a machine can invent, does this mean the end of the patent system as we know it? The patent system, both in the US and Europe, allows companies to protect their inventions and helps foster innovation. However, Artificial Intelligence (AI) could be set to disrupt the patent system as we know it. This talk will examine how AI may change the patent landscape in the years to come. Furthermore, ways in which companies can best protect their AI related inventions will be examined from both a US and...
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
Bill Schmarzo, Tech Chair of "Big Data | Analytics" of upcoming CloudEXPO | DXWorldEXPO New York (November 12-13, 2018, New York City) today announced the outline and schedule of the track. "The track has been designed in experience/degree order," said Schmarzo. "So, that folks who attend the entire track can leave the conference with some of the skills necessary to get their work done when they get back to their offices. It actually ties back to some work that I'm doing at the University of San...
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, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...
Bill Schmarzo, author of "Big Data: Understanding How Data Powers Big Business" and "Big Data MBA: Driving Business Strategies with Data Science," is responsible for setting the strategy and defining the Big Data service offerings and capabilities for EMC Global Services Big Data Practice. As the CTO for the Big Data Practice, he is responsible for working with organizations to help them identify where and how to start their big data journeys. He's written several white papers, is an avid blogge...
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more busine...
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.