It was licensed under the proprietary license. It was purely written using Java programming language. Its recent stable version was released in August Now, if you are looking for a job which is related to Weblogic then you need to prepare for the Weblogic Interview Questions. It is true that every interview is different as per the different job profiles. Here, we have prepared the important Weblogic Interview Questions and Answers which will help you get success in your interview.
|Published (Last):||23 December 2013|
|PDF File Size:||7.56 Mb|
|ePub File Size:||8.45 Mb|
|Price:||Free* [*Free Regsitration Required]|
It prints out some debugging information. If everything is working correctly, you should see your machine name. Question Answer : Yes. One option is to do this every time you come into the onMessage routine for the MDB. This is sufficient if the message rate is relatively low.
The second option is to establish the necessary objects in ejbActivate. When the EJB deactivates, you need to close the associated objects. Because of the way Topics work, the session, and thus every bean instance, receives a copy of each message published on that Topic.
There was also a problem that caused parallel processing not to work correctly. This has been fixed for WLS 6. Within a single server, one topic consumer is used to pass out messages to multiple threads to get the concurrency while producing only a single copy of each message. When using multiple servers, each server gets its own consumer and therefore its own copy of each message.
It is not currently possible to share a consumer across multiple servers. If you want a message to be processed by exactly one MDB, use a queue. One customer had an example where topic MDBs are needed in which there will be multiple implementations of the MDBs listening on the same topic. In other words, more than one MDB with a different implementation may be subscribing to the same topic.
The client has no advanced way of knowing how many different kinds of MDBs may be listening on the same topic, but it is possible for there to be more than one listener, therefore topics, not queues. For each kind of MDB listening on the topic, the message is delivered exactly once i. Answer : Yes, as long as the communication is between source and target WebLogic domains that are both running release 6. Answer : Yes, as long as the WebLogic 7. In fact, there are other classes in the same directory that are getting loaded.
I also get a "Too many open files" error. We have seen this situation when the user account runs out of file descriptors. On Solaris, each user account has a certain limited number of file descriptors. You can find out how many file descriptors you have with the limit command in csh.
You can increase file descriptors if you have enough privileges with the ulimit command in the csh. Otherwise, ask your system administrator to increase the file descriptors available to your processes. Set the minimum and the maximum to the same size. This allocates 32 megabytes of Java heap memory to WebLogic Server, which improves performance and allows WebLogic Server to handle more simultaneous connections. You can increase this value if necessary. Answer : T3 provides a framework for WebLogic Server messages that support for enhancements.
These enhancements include abbreviations and features, such as object replacement, that work in the context of WebLogic Server clusters and HTTP and other product tunneling. T3 is a superset of Java Object. It depends on what you want to do.
Section In addition, we include a WebLogic proprietary high-performance non-validating parser that you can use for small to medium sized XML documents. Answer : The fundamental problem is too few resources database connections in the connection pool for the work load. The correct response is to increase the maximum number of connections in the connection pool. Optimally designed applications only require the server to have one pool connection per execute thread.
The proper application response to a resource exception is not to retry the request in a tight loop, which would tie up execute threads on the server. You should design your application to gracefully fail if no connections are available. Try to ensure that you get the connection as late as possible in your application code and return them to the pool as early as possible so that you do not see as many NoResource exceptions.
BEA WebLogic Server Interview Questions & Answers
The enhancements support for WebLogic Server messages is provided by T3. T3 is superset of java Object. Serialization and RMI can be done over T3. What happens when a failure occurs and the stub cannot connect to a WebLogic Server instance? The stub removes the instance that is failed from its list, when a failure occurs. The stub uses DNS again for finding a running server and obtains a current list of instances, when there are no servers left in its list. The list of available server instances in the cluster will get periodical refreshment, which allows making the advantage of new servers.
Weblogic Interview Questions
Explain deployment descriptors? Deployment descriptors are associated with almost all the modules as well as applications. The deployment descriptors can be seen in the form of XML documents, and they are capable of describing the contents that are part of the directory or the jar file. J2EE specifications usually define the standard as well as the deployment descriptors which are portable for J2EE applications and modules. What is web. Explain the methods for providing user credentials for starting the server?
Oracle WebLogic Interview Questions
Close any open resources, like database connections b. All non-transient, non-serializable fields except some special types should be set to null. All transient fields should be set to null d. Make all database connection reference fields transient e. All primitive type fields should be set to null Choices A, B and D are correct. When a bean is about to be passivated, its ejbPassivate method is invoked, alerting the bean instance that it is about to enter the Passivated state. At this time, the bean instance should close any open resources and set all non transient, non serializable fields to null.