Skip to main content

Java Native Interface (JNI) Interview Questions

What is Native Interface in JAVA?

Answer
JNI is the mechanism used to invoke methods written in languages such as c and C++. You can write code using language like c and c++ and declare its native methods and can use the same method in java using JNI.

JNI exposes JNI functions and pointers that can access java objects and methods.

What is Native Interface in JAVA?

Java Native Interface permits the developers to integrate the native code such as C or C++ into a java application. To take the advantages of C programming and implementing the Java GUI features together makes the applications more efficient and powerful.

JNI is used to handle situations where the entire application can not be written in java.

Explain the advantages and disadvantages of using JNI.

Answer

Advantages of JNI

Using JNI, we can access c and c++ code which adds performance boost to JAVA.
JNI allows JAVA to access some hardware features using other languages like c and c++.

Disadvantages of JNI

JNI uses native languages which mean it has portability issue.
Code debug is big problem for the developers who use JNI features in JAVA.

Explain the advantages and disadvantages of using JNI.

Advantages:

- Use the existing library that was previously written in another languages.
-Use of windows API functions
-Increasing the speed of execution
-Invoke API functions from server product that is developed in C or C++ from a java client.

Disadvantages:

-Write Once Run Anywhere is not possible
-Run time errors debugging is difficult in native code
- An applet can not call a native method
- Security risk is potential

Explain Exception Handling in JNI.

Answer

JNI exceptions are handled by using the following:

* Throw( )

Throws an existing exception object. Used in native methods to rethrow an exception.

* ThrowNew( )

Creates a new exception object and throws.

* ExceptionOccurred( )

Determines the exception status of throws and not yet cleared.

* ExceptionDescribe( )

Displays the exception and stack trace

* ExceptionClear( )

A pending exception is cleared.

* FatalError( )

Causes a fatal error to raise and does not return.

Comments

Popular posts from this blog

Asynchronous Vs. Synchronous Communications

Synchronous (One thread):   1 thread -> |<---A---->||<----B---------->||<------C----->| Synchronous (multi-threaded):   thread A -> |<---A---->| \ thread B ------------> ->|<----B---------->| \ thread C ----------------------------------> ->|<------C----->|

WebSphere MQ Interview Questions

What is MQ and what does it do? Ans. MQ stands for MESSAGE QUEUEING. WebSphere MQ allows application programs to use message queuing to participate in message-driven processing. Application programs can communicate across different platforms by using the appropriate message queuing software products. What is Message driven process? Ans . When messages arrive on a queue, they can automatically start an application using triggering. If necessary, the applications can be stopped when the message (or messages) have been processed. What are advantages of the MQ? Ans. 1. Integration. 2. Asynchrony 3. Assured Delivery 4. Scalability. How does it support the Integration? Ans. Because the MQ is independent of the Operating System you use i.e. it may be Windows, Solaris,AIX.It is independent of the protocol (i.e. TCP/IP, LU6.2, SNA, NetBIOS, UDP).It is not required that both the sender and receiver should be running on the same platform What is Asynchrony? Ans. With messag...

Advantages & Disadvantages of Synchronous / Asynchronous Communications?

  Asynchronous Communication Advantages: Requests need not be targeted to specific server. Service need not be available when request is made. No blocking, so resources could be freed.  Could use connectionless protocol Disadvantages: Response times are unpredictable. Error handling usually more complex.  Usually requires connection-oriented protocol.  Harder to design apps Synchronous Communication Advantages: Easy to program Outcome is known immediately  Error recovery easier (usually)  Better real-time response (usually) Disadvantages: Service must be up and ready. Requestor blocks, held resources are “tied up”.  Usually requires connection-oriented protocol