Skip to main content

WebLogic Interview Questions

In this article I will briefly discuss how I conduct interviews for WebLogic Administration roles.

When conducting interviews I prefer to avoid difficult questions, and instead ask fairly simple questions and look at how well the candidate answers. I would prefer to hire someone who can clearly and concisely explain how to do a simple task than someone who knows every single thing about a particular technology.

I explain at the beginning of the interview, it's acceptable if they are not able to answer every question; I use their answers to help decide if they will be a good fit for the team and the role.

Here are some of the questions I like to ask after I've given them a description of the role on offer.

Non-Technical Questions
  • Which of your previous roles do you think have give you experience that could be important for this role?
  • Tell me what is involved in a typical day in this role?
  • Describe the kind of infrastructure you worked with in this role?
  • On a scale of 1 to 10, with 1 being "no knowledge" and 10 being "know everything", how would you rate your own skills? (I don't look for people who think they "know everything").
  • What are some of the things you need to learn more about?

Technical Questions
  • If you were trying to access an application via a HTTP proxy and were getting a 404 error, how would you go about determining why you were getting this error?
  • Describe how you would go about configuring a WebLogic server to give an application access to a database.
  • How many threads does a managed server make available to an application? (expect different answers for different versions of WebLogic)
  • What kind of problems would you expect to encounter when trying to increase a managed server's maximum heap size to 3 GB? (Problems on 32-bit operating systems).
  • If an application was suffering short periodic freezes, and no errors were appearing in the logs, can you suggest a possible cause? (Garbage collection)
  • How could you prevent these periodic lock-ups?
  • What are the ways you could check when garbage collection is occurring?
  • If you start an admin server as a Windows service, where is that server's classpath defined? (Windows Registry)
  • If you start a managed server via a node manager, where is that server's classpath defined? (config.xml)
  • If a managed server is crashing with a StackOverflow exception, what could be the cause?
  • Describe how you would go about configuring a JMS queue in a WebLogic cluster. (i.e. a distributed queue).
  • Describe how you might run a WLST script?

Other Questions
Note it is also important to ask questions that determine if the candidate is familiar with best practices, such as Change Control and Configuration Management.

Comments

  1. Thanks for sharing this helpful interview questions.

    Interview Questions

    ReplyDelete
  2. do you have more detailed answers to these questions ?

    ReplyDelete
  3. Hi

    I read this post 2 times. It is very useful.

    Pls try to keep posting.

    Let me show other source that may be good for community.

    Source: People manager interview questions

    Best regards
    Jonathan.

    ReplyDelete

Post a Comment

Popular posts from this blog

BAD_CERTIFICATE - A corrupt or unuseable certificate...

This is a simple symptom-cause-solution blog entry only. I hope these blogs will help fellow administrators.
Symptom
In wls_utc, when trying to test a webservice using SSL, the following error message is received: javax.net.ssl.SSLKeyException: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
If SSL debugging is enabled, the following error also appears in the logs: ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)' <1254822672320>>
verification failed because RSA key public exponent [3] is too small
Cause
The certificate encryption is of a weaker strength than expected by newer versions of Java.
Solution
Add the flag "-Dweblogic.security.SSL.allowSmallRSAExponent=true" to the server startup parameters.
References


None.

Connection refused: No available router to destination

This is a simple symptom-cause-solution blog entry only. I hope these blogs will help fellow administrators.
Symptom

The following exception occurs in WebLogic server logs. Most likely to occur during WebLogic server start-up, but similar exceptions may occur at other times.
java.net.ConnectException: t3://myserver:8000: Destination unreachable; nested exception is: java.net.ConnectException: Connection refused: connect; No available router to destination] at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:49) at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:773) at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:363) at weblogic.jndi.Environment.getContext(Environment.java:307) at weblogic.jndi.Environment.getContext(Environment.java:277)
Cause
This message (Connection refused: connect; No available router to destination) is a kind of "catch…

BEASVC.EXE - WebLogic as a Windows Service

I remember the first time I had to work out why WebLogic wouldn't run as a service. It was a frustrating experience. There were no error messages. No Windows error dialog. No console output.

How do you troubleshoot something like this??!!

This short article will show you. For simplicity I'll talk about the node manager, but the same principles apply for running an admin or managed server as a service.

First Steps

First, you still have your server logs. Sure the console output is better, but it's a starting point. Check this log for errors and especially take note of the start up variables such as PATH and CLASSPATH. If the server log isn't being created, that tells you WebLogic probably isn't even being started. (Check that you have a license file if you haven't already.)

Ok, so the logs were no help. The next step is to look at how the service is trying to start WebLogic.

When you install WebLogic as a service, you're really setting up beasvc.exe as the service.…