java.lang.UnsatisfiedLinkError: _getStatementCacheSize about pljava HOT 3 CLOSED

I have the same problem with in our installation of PL/Java. Segmentation fault received.

SELECT sqlj.install_jar(:triggersJar, 'triggers', false);
psql:triggers/install_triggers.sql:1: WARNING: java.lang.UnsatisfiedLinkError: org.postgresql.pljava.internal.Backend._getStatementCacheSize()I
psql:triggers/install_triggers.sql:1: ERROR: Unable to load class org/postgresql/pljava/internal/ExecutionPlan using CLASSPATH '-Djava.class.path=/usr/local/pgsql-9.1/lib/activemq-all.jar:/usr/local/pgsql-9.1/lib/postgresql.jar:/usr/local/pgsql-9.1/lib/pljava.jar:/usr/local/pgsql-9.1/lib/pljava.so:/usr/local/pgsql-9.1/lib/slf4j-log4j12-1.6.4.jar:/usr/local/pgsql-9.1/lib/log4j-1.2.15.jar:/usr/local/pgsql-9.1/lib/commons-logging-1.1.1.jar:/opt/jetty/resources'
SELECT sqlj.set_classpath('public', 'triggers');

Looks rather like incompatibility of the PL/Java and version 9.1

from pljava.

Hi @elena-lebeda

I am a bit perplexed by this bug report - are you still in a position where you could give more details, or did you get it working eventually?

From the information above, I don't think this can involve an incompatibility with a PostgreSQL version. The _getStatementCacheSize function is not part of PostgreSQL, it's part of PL/Java itself, so somehow PL/Java got built in a way that left it with problems finding its own function symbols. What's more strange is that the line that registers that function with JNI and the function definition itself don't appear to have changed in the source code at all in eleven years.

To figure this out, it might take more details on the exact environment where you built PL/Java, maybe a log from the build ... if you are still able to provide that.

Thanks!

from pljava.

Nothing heard from the original reporter in a couple of months, the report is old, and 1.5.0-SNAPSHOT is testing well on several platforms and PG versions up to 9.5. Closing.

from pljava.