20th WebLogic Book Review comes from India!

The two statements from @ganeshk_8 a Senior Technical Consultant for OFM about my WebLogic 12c book are top notch:

“It promises much more than what its name suggests.”

“You will end up thinking – had I read this book earlier, I would have saved a lot of time in my project.”


Read the full review here.

Book Raffle: 3 Free Copies of WebLogic 12c Distinctive Recipes

It’s Christmas time, 2013 is almost over. I’ll be heading to Berlin next week, which will be my last business trip for this year. 2013 has been a good year! A year packed with exciting projects, interesting tech workshops and new customers looking for honest OFM consulting and doing cool stuff.

Free WebLogic 12c Distinctive Recipes Book

To give something back, I am offering three free copies of my 2013 book WebLogic Distinctive Recipes.


By the way, guess who is Santa Claus on that picture? Don’t get fooled by the belly… I had to use an extra pillow to trick my 9-year-old nephew into believing that Santa exists (some friends believe that Beyoncé later copied my trick with the pillow).


The Raffle

To participate in the raffle simply let me know that you like a copy before Dec 20th:

✘✘✘  Just retweet the announcement on Twitter, or tweet about it yourself (and make sure I will see it).

✘✘✘  Or, if you are more a Facebook person,  SHARE the Facebook announcement.

The Smallprint

There is no purchase required to participate! All you need is a delivery address. Winners are drawn Dec 21st. Decisions are final. Any recourse to courts of law is excluded.

Python for the WebLogic Scripting Tool (WLST)

To be able to code more than the most basic WLST scripts for WebLogic you should have reasonably good Python skills. Fortunately there are many good and free resources to get started.  Note that WLST as of WLS 12.1.2 is using Python 2.

Here is a list of recommendations to learn more Python and become better a WLST:

As you can see I haven’t mentioned any real books yet. Let me know your favourite!

WebLogic SNMP UDP Port – Misleading Error Logs

Have you lately tried to use SNMP with WebLogic? I did, because I upgraded an earlier Windows-based domain to WebLogic 12.1.2 running on CentOS Linux.

SNMP Configuration

WebLogic is showing some strange and undesired behaviour here… Firstly, to get started with SNMP basically all you need to do is to enable the SNMP agent.

WebLogic SNMP Agent


This is good enough when running under Windows. Then you might specify a trap destination such as localhost 4000 and run the WebLogic command-line tool to listen to the destination and verify if your setup is working.

WebLogic Trap Destination


The command line to run the trap listener looks like this

$ java weblogic.diagnostics.snmp.cmdline.Manager SnmpTrapMonitor -p 4000
Listening on port:4000

Now, of course you (well, in this case me) forgot to modify SNMP UDP Listen Port and the Master AgentX Port. For sure you know that you cannot bind to ports less than 1024 in UNIX.

WebLogic Bind Exception

What happens

  • Interesting enough, there is an error message in the Weblogic startup – it is just pointing you to the wrong direction since it complains about port 171 not being available. Now, you might wonder, port 171 is configured nowhere!
  • Apparently WebLogic is trying 161 and the following 10 port numbers, eg. to avoid conflicts when several servers are running on a single machine (nothing to complain about, this behavior is documented, just click on “help”).
  • If all ports are unavailable (or not allowed for non-root users in UNIX), WebLogic does not complain about the configured port not available, but about the last one it tried. Not such a good solution…
  • Looking at the Master AgentX port, the situation is different again. Of course the restriction for binding to ports less than 1024 still applies, but there is no auto-increment on WebLogic. Unfortunately, the error message in the log file does not even mention the port number.

To conclude, when specifying a SNMP port number that you cannot bind to, you might see an error message containing a different port number than the one you configured for SNMP UDP Listen Port.
For the Master AgentX Port you will see a rather generic message, not containing the problematic port number at all.

Both is good to know and leaves some space for improvement.

<Sep 21, 2013 8:53:54 AM CEST> <Error> <SNMP> <BEA-320951> <Failed to initalize the SNMP AgentX master subagent. One possible cause is the failure to bind the Master agentX port. If this is the case, check to see if the specified AgentX port is available, or ensure that the process has permissions to bind to the desired port.
weblogic.diagnostics.snmp.agent.SNMPAgentToolkitException: java.net.BindException: Permission denied
 at weblogic.diagnostics.snmp.agent.monfox.MonfoxToolkit.initializeMasterAgentX(MonfoxToolkit.java:186)


What happened with the Web Service Test Client in WebLogic 12.1.2 ?

Trying to run the Web Service Test Client as you used to do it until WebLogic version 12.1.1 fails in WebLogic 12.1.2. It took me a while to find out why.

My 12.1.2 domain was running in development mode, I deployed a web service but could not access the web service test client. The admin console did not display the link under Deployment / Testing and also the typical URL /wls_utc didn’t work.

Web Service Test Client / Console in WebLogic 12.1.2

Now here comes the news.


First of all, the link to access the test client has changed in a way which is hard to spot. No word about this in the release notes. To access the web service test client use the following new URL:


(until 12.1.1 it was wls_utc)


Testing from Console is BROKEN

Of course then you should be able to access the test client using the admin console via Deployments / Testing. Surprisingly this didn’t work for a really simple web service I used for testing. For exactly the same web service, only deployed in 12.1.1 domain, the console displays the testing link.

So not sure if it was only my example, which couldn’t be any simpler, but the testing link was not displayed.


UPDATE: I was trying this with more different web services. I did not work with any of my examples. I looks like a bug to me. I recommend to ask your friendly Oracle consultant if it is a feature.

Using Web Service Test Client from an URL

Although the bug described above, the good news is that you can still use the


for testing, eg.


More Features

Those of you who know the possibilities of the SOA suite test client (part of EM) or the OSB test client might have missed some more features in the WLS web service test client.  The test client coming with 12.1.2 is overhauled (or new?) and comes with a number of additional possibilities like settings for authentication, WS-Adressing, WS-Atomic TX etc. (see the tabs in the first screenshot above).

Let me know if it is working for you.