StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POPure-Java vs Native SQLiteJDBC driver and Nested VM
text
Body
copied!<p>I currently am working on a quite simple projet using Java web app hosted in Weblogic and an SQLite DB. (Scope quite small, two tables only)</p> <p>Developpement went fine and still works, but when deploying to staging, i got some unexpected prolem.</p> <p>Whenever the app has to read (select) from the DB, i can read the following stack trace : </p> <pre><code>Root cause of ServletException.java.lang.Error: in _syscall() at org.ibex.nestedvm.Runtime.syscall(Runtime.java:1086) at org.sqlite.SQLite.run_0x171800(target/build/SQLite.mips:???) at org.sqlite.SQLite.trampoline(target/build/SQLite.mips:???) at org.sqlite.SQLite._execute(target/build/SQLite.mips:???) at org.ibex.nestedvm.Runtime.__execute(Runtime.java:506) at org.ibex.nestedvm.Runtime.call(Runtime.java:678) at org.ibex.nestedvm.Runtime.call(Runtime.java:647) at org.sqlite.NestedDB.call(NestedDB.java:568) at org.sqlite.NestedDB.call(NestedDB.java:563) at org.sqlite.NestedDB.prepare(NestedDB.java:130) at org.sqlite.DB.prepare(DB.java:123) at org.sqlite.Stmt.executeQuery(Stmt.java:121) </code></pre> <p>Please tell me if i am wrong, but what i understand is that the target/build/SQLite.mips refers to a native implementation of the driver. However, i did specify it should stick to pure java using : </p> <pre><code>Connection con; //Load the JDBC driver class dynamically. Driver d = (Driver)Class.forName("org.sqlite.JDBC").newInstance(); DriverManager.registerDriver(d); //init the connection System.setProperty("sqlite.purejava", "true"); con = DriverManager.getConnection(getConnectionString()); </code></pre> <p>Is my understanding correct ? How could i further enforce the use of pure java implementation ? Could anything else cause such a stack trace ?</p> <p>For the record, both dev and stagging environements are linux / bea weblogic.</p> <p>Thanks for you time :)</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload