This post is part of a series exploring the unique aspects and capabilities of WebSphere Liberty when running on z/OS.
We'll also explore considerations when moving from WebSphere traditional on z/OS to Liberty on z/OS.

To start at the beginning, follow this link to the first post.

---------------

There’s not a lot to say about CWWKE0002I.  This is the message that gets issued when the ‘kernel’ of Liberty is started.  It includes the number of seconds that it took to get this far. 

It is important to have this as you’re trying to sort out any delays in getting the server all the way up.  At this point we’ve got the core of the server in place but it hasn’t actually started doing anything yet.  As you’ll see from the messages we look at in coming weeks, there’s still a lot to happen before we get to the message that says we’re all the way up.

Some of the stuff still to come is really server stuff.  We’re either cleaning things up from a previous instance of this server or we’re initializing things that you told us to do through various configuration.  Ports get opened and all that sort of thing.

And, of course, the applications have to start.  Not to beat on the applications folks, but that’s usually where delays in server startup happen. 

Anyway, back to the kernel started message.  The stuff that happens before this point has to happen and it, generally, shouldn’t take very long relative to other startup things (your mileage may vary).  The message serves as a nice separation point between that basic stuff and all that follows it.  The first thing I’d do looking at a startup delay problem would be to find this message and use it to decide if the problem is either before or after this point.