Posts

Showing posts from November, 2017

Eclipse- Failed to load JNI shared library

Today I have downloaded the Eclipse IDE with below details: Version : Mars Release (4.5.0) For OS : Windows 64 bit Link : http://www.eclipse.org/ I have got a *.zip package for startup. When I tried to execute the eclipse.exe file, it shown me a splash screen followed by an alert and then exit. Failed to load JNI shared library "C:\Program Files (x86)\Java\jdk1.6.0_20\jre\bin\client\jvm.dll" I was not able to use the Eclipse IDE. However after a lot of effort, below changes worked as magic to run my eclipse IDE. ------------------------------------------------------------------------- eclipse.ini before ------------------------------------------------------------------------- -startup plugins/org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.300.v20150602-1417 -product org.eclipse.epp.package.jee.product --launcher.defaultAction openFile --launcher.XXMaxPermSize 256M -s

Spring Boot V/S Vert.x

Image
S. No Parameters Vert.x Spring boot 1 Primary Focus Vert.x is designed to build your large-scale, super-scalable and distributable web applications which might have less complex business logic in them, but need to perform reliably under massive load. SpringMVC is focused on enterprise processes and enterprise applications with lower user counts. 2 Reactive Manifesto 1. Asynchronous messaging 3. Elastic 4. Resilient 5. Responsive Vert.x is reactive. Vert.x uses asynchronous messaging, a mechanism that scales. It is particularly useful in mircoservices because messages do not care whether you send them across the network or locally in the same JVM. Spring is not reactive. Spring does not support asynchronous messaging. 3 Non-blocking, event driven runtime Vert.x provides a non-blocking, event-driven runtime