Welcome!

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

Related Topics: Weblogic

Weblogic: Article

Programmatic Clients, Symmetry, and the Humble Ant

Programmatic Clients, Symmetry, and the Humble Ant

Picnicking during my summer holidays with my family, I was a little peeved to find that we had set up camp near an ant hill and some of them had decided to help themselves to elements of our lunch. Just as well, really, that I prefer sausage rolls and pork pies to chocolate buns, I guess. Every time I see an ant, I'm reminded of countless documentaries from my youth, waxing lyrical about how an ant can carry many times its own body weight.

Right now, the evidence is being played out in front of me, so at least you can believe some of what you see on TV. Isn't nature a miraculous thing! So what does this have to do with transactions? Well, very little actually.

Bear with My Ramblings, Won't You? I'm on Holiday!
I thought this month I would come up for air with a review of a piece of obsure knowledge about the WebLogic Server transaction manager implementation. As you probably realize by now, if you want to demarcate a transaction from a piece of Java code, you simply need to obtain a reference to the User Transaction object and start invoking its begin, commit, etc., methods at will. What could be simpler?

What may have escaped your notice (since the specs don't make a very big deal about it) is that you can do this wherever you want - in EJBs configured to use bean-managed transactions, in RMI objects, in startup classes, you name it. These are all server-side places; however, the list goes on.... You can also demarcate transactions from Swing clients or even Java applets. In fact, in an alarming throwback to flower power and Woodstock, you can do it wherever you please, on the server or off it. Think about that for a minute...coordinating a transaction (as you may remember from previous columns) requires transaction logs, which are the linchpin of your business data's integrity. You need to be very paranoid about these - put them on RAID disks, make them available to multiple machines for failover, prevent the intern system administrator from deleting them to save disk space, and so on. Now let's think about clients - potentially applets - not exactly where you'd keep your proverbial family silver, or your actual transaction log. So how can transactions be demarcated there? Visions of MS Internet Explorer (with the Java plug-in) powering over a picnic rug carrying a RAID disk array are spinning through my mind... I need to lie down, I'm overcome. Let's face it, this is technology, not the miracle of nature. There is no clever evolutionary mechanism to fall back on here.

What's Going on Behind This Choking Smoke and These Dizzying Mirrors?
As you may have guessed, the BEA engineers who wrote the transaction manager in WebLogic Server were well aware of the asymmetry between the client and server, and they engineered the infrastructure (they'd get cross if I carried the smoke and mirrors reference forward) to take care of it. If you get a reference to the User Transaction object on a client, the implementation is well aware of the lowly status of the container it's running in. It does all the usual stuff with respect to associating a transaction object to the relevant threads on the client, and propagates the transaction context across the wire when the client makes RMI calls to remote objects in the scope of a transaction. However, at commit time it knows its place. It packages all the information about the transaction and sends it to a server, where the commit processing can proceed in an environment more conducive to reliability and where the RAID disks and suchlike are kept. The server processes the commitment of the transaction, and when that's done it sends the result back to the client (if the client is still around to receive it - remember, it's none too reliable out there!). From the programmers' point of view, all this was hidden; they just gaily used the objects they knew and loved and the stuff they coded came to pass.

That's fine and dandy, but there must be some side effects, right? Well yes, from an administrative point of view there are. Relax, they're not too serious, but I'll tell you about them just in case you ever meet them in a dark alley somewhere.

Let's look at an example of a client invoking methods on three objects, A, B, and C (in that order), in a single transaction. Assume that these objects all run in different instances of the application server (clearly a poor design on all counts, but this is a Discovery Channel-style contrived example). At commit time, it's entirely possible that the three application servers have never directly communicated with one another. Certainly all the servers know of the existence of the transaction since it has touched them, but server A thinks it's the only participant - after all, it was the only participant the last time it was called. Only the client knows it has the full picture of the transaction. So the client chooses a server to handle the commit.

The current WebLogic Server implementation chooses the first server that was touched, A in this case, but as with all implementation details, that could change. Don't write code that relies on this behavior. Server A is sent the transaction object so now it, too, has the full picture of what the transaction is comprised of, and it can process the transaction's commitment. At this point, the commit processing is the same as for a transaction started within the application server; server A needs to tell servers B and C about the impending commitment. As you may already know from a previous article, the servers will need to trust one another (if you're not a regular reader, it serves you right - get the back issues!). There is, however, one subtle difference. Remember, servers A, B, and C may never have connected to each other before this moment, in which case they'll have to connect now. It's at this point that you'll get weird commitment failures (you guessed it, your old favorite HeuristicMixedException) if the servers can't contact each other. Whoever configured the TCP/IP network you're using better have allowed for this. Note that this is a static configuration error that can be caught only at runtime - a very good place for a timely reminder that you should do preproduction testing of your applications in as close a facsimile of the production system as you can get, even down to the network.

*  *  *

So, that's more WebLogic Server arcana unearthed for you. I'm back off to the beach now, just as soon as I catch up with that pork pie that's receding over the hilltop!

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.
@DevOpsSummit at Cloud Expo, taking place November 12-13 in New York City, NY, is co-located with 22nd international CloudEXPO | first international DXWorldEXPO and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. 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 t...
Headquartered in Plainsboro, NJ, Synametrics Technologies has provided IT professionals and computer systems developers since 1997. Based on the success of their initial product offerings (WinSQL and DeltaCopy), the company continues to create and hone innovative products that help its customers get more from their computer applications, databases and infrastructure. To date, over one million users around the world have chosen Synametrics solutions to help power their accelerated business or per...
DXWordEXPO New York 2018, colocated with CloudEXPO New York 2018 will be held November 11-13, 2018, in New York City and will bring together Cloud Computing, FinTech and Blockchain, Digital Transformation, Big Data, Internet of Things, DevOps, AI, Machine Learning and WebRTC to one location.
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...
Charles Araujo is an industry analyst, internationally recognized authority on the Digital Enterprise and author of The Quantum Age of IT: Why Everything You Know About IT is About to Change. As Principal Analyst with Intellyx, he writes, speaks and advises organizations on how to navigate through this time of disruption. He is also the founder of The Institute for Digital Transformation and a sought after keynote speaker. He has been a regular contributor to both InformationWeek and CIO Insight...
IoT is rapidly becoming mainstream as more and more investments are made into the platforms and technology. As this movement continues to expand and gain momentum it creates a massive wall of noise that can be difficult to sift through. Unfortunately, this inevitably makes IoT less approachable for people to get started with and can hamper efforts to integrate this key technology into your own portfolio. There are so many connected products already in place today with many hundreds more on the h...
CloudEXPO New York 2018, colocated with DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City and will bring together Cloud Computing, FinTech and Blockchain, Digital Transformation, Big Data, Internet of Things, DevOps, AI, Machine Learning and WebRTC to one location.
SYS-CON Events announced today that IoT Global Network has been named “Media Sponsor” of SYS-CON's @ThingsExpo, which will take place on June 6–8, 2017, at the Javits Center in New York City, NY. The IoT Global Network is a platform where you can connect with industry experts and network across the IoT community to build the successful IoT business of the future.
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...