You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Andrew Munn <mu...@gmail.com> on 2020/02/20 01:36:03 UTC
ERROR: h2 Unsupported connection setting "MULTI_THREADED"
I'm building/running my client app w/Gradle and I'm seeing this error. Am
I overloading the Ingite H2 fork with the real H2 or something? It appears
I have the latest h2:
[.gradle]$ find ./ -name *h2*
./caches/modules-2/metadata-2.82/descriptors/com.h2database
./caches/modules-2/metadata-2.82/descriptors/com.h2database/h2
./caches/modules-2/files-2.1/com.h2database
./caches/modules-2/files-2.1/com.h2database/h2
./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/6178ecda6e9fea8739a3708729efbffd88be43e3/h2-1.4.200.pom
./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/f7533fe7cb8e99c87a43d325a77b4b678ad9031a/h2-1.4.200.jar
2020-02-19 19:59:28.229 ERROR 102356 --- [ main]
o.a.i.internal.IgniteKernal%dev-cluster : Exception during start
processors, node will be stopped and close connections
org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
initialize system DB connection:
jdbc:h2:mem:b52dce26-ba01-4051-9130-e087e19fab4f;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=10000;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.GridH2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.systemConnection(IgniteH2Indexing.java:434)
~[ignite-indexing-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSystemStatement(IgniteH2Indexing.java:699)
~[ignite-indexing-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createSchema0(IgniteH2Indexing.java:646)
~[ignite-indexing-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:3257)
~[ignite-indexing-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:248)
~[ignite-core-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1700)
~[ignite-core-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1017)
~[ignite-core-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
~[ignite-core-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
~[ignite-core-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
~[ignite-core-2.7.6.jar:2.7.6]
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076)
~[ignite-core-2.7.6.jar:2.7.6]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962)
~[ignite-core-2.7.6.jar:2.7.6]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861)
~[ignite-core-2.7.6.jar:2.7.6]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731)
~[ignite-core-2.7.6.jar:2.7.6]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700)
~[ignite-core-2.7.6.jar:2.7.6]
at org.apache.ignite.Ignition.start(Ignition.java:348)
~[ignite-core-2.7.6.jar:2.7.6]
at
com.centiva.ig.etl.loader.LoaderApplication.main(LoaderApplication.java:14)
~[main/:na]
Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported
connection setting "MULTI_THREADED" [90113-200]
at
org.h2.message.DbException.getJdbcSQLException(DbException.java:622)
~[h2-1.4.200.jar:1.4.200]
Re: ERROR: h2 Unsupported connection setting "MULTI_THREADED"
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
I recommend tweaking your dependency importing to make sure you exclude all
H2 versions but the one needed by Apache Ignite.
With Maven, mvn dependency:tree to the rescue.
H2 is currently the heart of Ignite's SQL and, as such, it is not
negotiable.
Regards,
--
Ilya Kasnacheev
вт, 25 февр. 2020 г. в 16:19, Andrew Munn <mu...@gmail.com>:
> Yes I'm using spring boot. Can Ignite be updated to work with the latest
> h2?
>
> On Fri, Feb 21, 2020, 6:25 AM Ilya Kasnacheev <il...@gmail.com>
> wrote:
>
>> Hello!
>>
>> I've heard about issues with e.g. Spring Boot overriding h2 database
>> version and breaking our runtime. I'm not sure who else does that.
>>
>> Regards,
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> Ilya Kasnacheev
>>
>>
>> чт, 20 февр. 2020 г. в 19:24, Andrew Munn <mu...@gmail.com>:
>>
>>> Thanks. Adding this runtime dependency to build.gradle fixed it:
>>>
>>> dependencies {
>>> runtime("com.h2database:h2:1.4.197")
>>> ...
>>> compile group: 'org.apache.ignite', name: 'ignite-spring', version:
>>> '2.7.6'
>>> compile group: 'org.apache.ignite', name: 'ignite-core', version:
>>> '2.7.6'
>>> }
>>>
>>> But I suspect this should be getting enforced automatically if using h2
>>> ver1.4.200 breaks something. Am I specifying the Ignite dependency
>>> incorrectly?
>>>
>>>
>>> On Thu, Feb 20, 2020 at 4:08 AM Taras Ledkov <tl...@gridgain.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Ignite uses H2 version 1.4.197 (see [1]).
>>>>
>>>>
>>>> [1]. https://github.com/apache/ignite/blob/master/parent/pom.xml#L74
>>>>
>>>> On 20.02.2020 4:36, Andrew Munn wrote:
>>>> > I'm building/running my client app w/Gradle and I'm seeing this
>>>> > error. Am I overloading the Ingite H2 fork with the real H2 or
>>>> > something? It appears I have the latest h2:
>>>> >
>>>> > [.gradle]$ find ./ -name *h2*
>>>> > ./caches/modules-2/metadata-2.82/descriptors/com.h2database
>>>> > ./caches/modules-2/metadata-2.82/descriptors/com.h2database/h2
>>>> > ./caches/modules-2/files-2.1/com.h2database
>>>> > ./caches/modules-2/files-2.1/com.h2database/h2
>>>> >
>>>> ./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/6178ecda6e9fea8739a3708729efbffd88be43e3/h2-1.4.200.pom
>>>> >
>>>> ./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/f7533fe7cb8e99c87a43d325a77b4b678ad9031a/h2-1.4.200.jar
>>>> >
>>>> >
>>>> >
>>>> > 2020-02-19 19:59:28.229 ERROR 102356 --- [ main]
>>>> > o.a.i.internal.IgniteKernal%dev-cluster : Exception during start
>>>> > processors, node will be stopped and close connections
>>>> > org.apache.ignite.internal.processors.query.IgniteSQLException:
>>>> Failed
>>>> > to initialize system DB connection:
>>>> >
>>>> jdbc:h2:mem:b52dce26-ba01-4051-9130-e087e19fab4f;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=10000;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.GridH2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine
>>>> > at
>>>> >
>>>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.systemConnection(IgniteH2Indexing.java:434)
>>>>
>>>> > ~[ignite-indexing-2.7.6.jar:2.7.6]
>>>> > at
>>>> >
>>>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSystemStatement(IgniteH2Indexing.java:699)
>>>>
>>>> > ~[ignite-indexing-2.7.6.jar:2.7.6]
>>>> > at
>>>> >
>>>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createSchema0(IgniteH2Indexing.java:646)
>>>>
>>>> > ~[ignite-indexing-2.7.6.jar:2.7.6]
>>>> > at
>>>> >
>>>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:3257)
>>>>
>>>> > ~[ignite-indexing-2.7.6.jar:2.7.6]
>>>> > at
>>>> >
>>>> org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:248)
>>>>
>>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>>> > at
>>>> >
>>>> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1700)
>>>>
>>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>>> > at
>>>> > org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1017)
>>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>>> > at
>>>> >
>>>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
>>>>
>>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>>> > at
>>>> >
>>>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
>>>>
>>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>>> > at
>>>> > org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
>>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>>> > at
>>>> >
>>>> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076)
>>>>
>>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>>> > at
>>>> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962)
>>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>>> > at
>>>> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861)
>>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>>> > at
>>>> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731)
>>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>>> > at
>>>> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700)
>>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>>> > at org.apache.ignite.Ignition.start(Ignition.java:348)
>>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>>> > at
>>>> >
>>>> com.centiva.ig.etl.loader.LoaderApplication.main(LoaderApplication.java:14)
>>>> > ~[main/:na]
>>>> > Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException:
>>>> > Unsupported connection setting "MULTI_THREADED" [90113-200]
>>>> > at
>>>> > org.h2.message.DbException.getJdbcSQLException(DbException.java:622)
>>>> > ~[h2-1.4.200.jar:1.4.200]
>>>>
>>>> --
>>>> Taras Ledkov
>>>> Mail-To: tledkov@gridgain.com
>>>>
>>>>
Re: ERROR: h2 Unsupported connection setting "MULTI_THREADED"
Posted by Andrew Munn <mu...@gmail.com>.
Yes I'm using spring boot. Can Ignite be updated to work with the latest
h2?
On Fri, Feb 21, 2020, 6:25 AM Ilya Kasnacheev <il...@gmail.com>
wrote:
> Hello!
>
> I've heard about issues with e.g. Spring Boot overriding h2 database
> version and breaking our runtime. I'm not sure who else does that.
>
> Regards,
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> Ilya Kasnacheev
>
>
> чт, 20 февр. 2020 г. в 19:24, Andrew Munn <mu...@gmail.com>:
>
>> Thanks. Adding this runtime dependency to build.gradle fixed it:
>>
>> dependencies {
>> runtime("com.h2database:h2:1.4.197")
>> ...
>> compile group: 'org.apache.ignite', name: 'ignite-spring', version:
>> '2.7.6'
>> compile group: 'org.apache.ignite', name: 'ignite-core', version:
>> '2.7.6'
>> }
>>
>> But I suspect this should be getting enforced automatically if using h2
>> ver1.4.200 breaks something. Am I specifying the Ignite dependency
>> incorrectly?
>>
>>
>> On Thu, Feb 20, 2020 at 4:08 AM Taras Ledkov <tl...@gridgain.com>
>> wrote:
>>
>>> Hi,
>>>
>>> Ignite uses H2 version 1.4.197 (see [1]).
>>>
>>>
>>> [1]. https://github.com/apache/ignite/blob/master/parent/pom.xml#L74
>>>
>>> On 20.02.2020 4:36, Andrew Munn wrote:
>>> > I'm building/running my client app w/Gradle and I'm seeing this
>>> > error. Am I overloading the Ingite H2 fork with the real H2 or
>>> > something? It appears I have the latest h2:
>>> >
>>> > [.gradle]$ find ./ -name *h2*
>>> > ./caches/modules-2/metadata-2.82/descriptors/com.h2database
>>> > ./caches/modules-2/metadata-2.82/descriptors/com.h2database/h2
>>> > ./caches/modules-2/files-2.1/com.h2database
>>> > ./caches/modules-2/files-2.1/com.h2database/h2
>>> >
>>> ./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/6178ecda6e9fea8739a3708729efbffd88be43e3/h2-1.4.200.pom
>>> >
>>> ./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/f7533fe7cb8e99c87a43d325a77b4b678ad9031a/h2-1.4.200.jar
>>> >
>>> >
>>> >
>>> > 2020-02-19 19:59:28.229 ERROR 102356 --- [ main]
>>> > o.a.i.internal.IgniteKernal%dev-cluster : Exception during start
>>> > processors, node will be stopped and close connections
>>> > org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
>>> > to initialize system DB connection:
>>> >
>>> jdbc:h2:mem:b52dce26-ba01-4051-9130-e087e19fab4f;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=10000;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.GridH2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine
>>> > at
>>> >
>>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.systemConnection(IgniteH2Indexing.java:434)
>>>
>>> > ~[ignite-indexing-2.7.6.jar:2.7.6]
>>> > at
>>> >
>>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSystemStatement(IgniteH2Indexing.java:699)
>>>
>>> > ~[ignite-indexing-2.7.6.jar:2.7.6]
>>> > at
>>> >
>>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createSchema0(IgniteH2Indexing.java:646)
>>>
>>> > ~[ignite-indexing-2.7.6.jar:2.7.6]
>>> > at
>>> >
>>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:3257)
>>>
>>> > ~[ignite-indexing-2.7.6.jar:2.7.6]
>>> > at
>>> >
>>> org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:248)
>>>
>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>> > at
>>> >
>>> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1700)
>>>
>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>> > at
>>> > org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1017)
>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>> > at
>>> >
>>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
>>>
>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>> > at
>>> >
>>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
>>>
>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>> > at
>>> > org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>> > at
>>> >
>>> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076)
>>>
>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>> > at
>>> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962)
>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>> > at
>>> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861)
>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>> > at
>>> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731)
>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>> > at
>>> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700)
>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>> > at org.apache.ignite.Ignition.start(Ignition.java:348)
>>> > ~[ignite-core-2.7.6.jar:2.7.6]
>>> > at
>>> >
>>> com.centiva.ig.etl.loader.LoaderApplication.main(LoaderApplication.java:14)
>>> > ~[main/:na]
>>> > Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException:
>>> > Unsupported connection setting "MULTI_THREADED" [90113-200]
>>> > at
>>> > org.h2.message.DbException.getJdbcSQLException(DbException.java:622)
>>> > ~[h2-1.4.200.jar:1.4.200]
>>>
>>> --
>>> Taras Ledkov
>>> Mail-To: tledkov@gridgain.com
>>>
>>>
Re: ERROR: h2 Unsupported connection setting "MULTI_THREADED"
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
I've heard about issues with e.g. Spring Boot overriding h2 database
version and breaking our runtime. I'm not sure who else does that.
Regards,
--
Ilya Kasnacheev
чт, 20 февр. 2020 г. в 19:24, Andrew Munn <mu...@gmail.com>:
> Thanks. Adding this runtime dependency to build.gradle fixed it:
>
> dependencies {
> runtime("com.h2database:h2:1.4.197")
> ...
> compile group: 'org.apache.ignite', name: 'ignite-spring', version:
> '2.7.6'
> compile group: 'org.apache.ignite', name: 'ignite-core', version:
> '2.7.6'
> }
>
> But I suspect this should be getting enforced automatically if using h2
> ver1.4.200 breaks something. Am I specifying the Ignite dependency
> incorrectly?
>
>
> On Thu, Feb 20, 2020 at 4:08 AM Taras Ledkov <tl...@gridgain.com> wrote:
>
>> Hi,
>>
>> Ignite uses H2 version 1.4.197 (see [1]).
>>
>>
>> [1]. https://github.com/apache/ignite/blob/master/parent/pom.xml#L74
>>
>> On 20.02.2020 4:36, Andrew Munn wrote:
>> > I'm building/running my client app w/Gradle and I'm seeing this
>> > error. Am I overloading the Ingite H2 fork with the real H2 or
>> > something? It appears I have the latest h2:
>> >
>> > [.gradle]$ find ./ -name *h2*
>> > ./caches/modules-2/metadata-2.82/descriptors/com.h2database
>> > ./caches/modules-2/metadata-2.82/descriptors/com.h2database/h2
>> > ./caches/modules-2/files-2.1/com.h2database
>> > ./caches/modules-2/files-2.1/com.h2database/h2
>> >
>> ./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/6178ecda6e9fea8739a3708729efbffd88be43e3/h2-1.4.200.pom
>> >
>> ./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/f7533fe7cb8e99c87a43d325a77b4b678ad9031a/h2-1.4.200.jar
>> >
>> >
>> >
>> > 2020-02-19 19:59:28.229 ERROR 102356 --- [ main]
>> > o.a.i.internal.IgniteKernal%dev-cluster : Exception during start
>> > processors, node will be stopped and close connections
>> > org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
>> > to initialize system DB connection:
>> >
>> jdbc:h2:mem:b52dce26-ba01-4051-9130-e087e19fab4f;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=10000;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.GridH2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine
>> > at
>> >
>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.systemConnection(IgniteH2Indexing.java:434)
>>
>> > ~[ignite-indexing-2.7.6.jar:2.7.6]
>> > at
>> >
>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSystemStatement(IgniteH2Indexing.java:699)
>>
>> > ~[ignite-indexing-2.7.6.jar:2.7.6]
>> > at
>> >
>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createSchema0(IgniteH2Indexing.java:646)
>>
>> > ~[ignite-indexing-2.7.6.jar:2.7.6]
>> > at
>> >
>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:3257)
>>
>> > ~[ignite-indexing-2.7.6.jar:2.7.6]
>> > at
>> >
>> org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:248)
>>
>> > ~[ignite-core-2.7.6.jar:2.7.6]
>> > at
>> >
>> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1700)
>>
>> > ~[ignite-core-2.7.6.jar:2.7.6]
>> > at
>> > org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1017)
>> > ~[ignite-core-2.7.6.jar:2.7.6]
>> > at
>> >
>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
>>
>> > ~[ignite-core-2.7.6.jar:2.7.6]
>> > at
>> >
>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
>>
>> > ~[ignite-core-2.7.6.jar:2.7.6]
>> > at
>> > org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
>> > ~[ignite-core-2.7.6.jar:2.7.6]
>> > at
>> >
>> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076)
>>
>> > ~[ignite-core-2.7.6.jar:2.7.6]
>> > at
>> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962)
>> > ~[ignite-core-2.7.6.jar:2.7.6]
>> > at
>> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861)
>> > ~[ignite-core-2.7.6.jar:2.7.6]
>> > at
>> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731)
>> > ~[ignite-core-2.7.6.jar:2.7.6]
>> > at
>> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700)
>> > ~[ignite-core-2.7.6.jar:2.7.6]
>> > at org.apache.ignite.Ignition.start(Ignition.java:348)
>> > ~[ignite-core-2.7.6.jar:2.7.6]
>> > at
>> >
>> com.centiva.ig.etl.loader.LoaderApplication.main(LoaderApplication.java:14)
>> > ~[main/:na]
>> > Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException:
>> > Unsupported connection setting "MULTI_THREADED" [90113-200]
>> > at
>> > org.h2.message.DbException.getJdbcSQLException(DbException.java:622)
>> > ~[h2-1.4.200.jar:1.4.200]
>>
>> --
>> Taras Ledkov
>> Mail-To: tledkov@gridgain.com
>>
>>
Re: ERROR: h2 Unsupported connection setting "MULTI_THREADED"
Posted by Andrew Munn <mu...@gmail.com>.
Thanks. Adding this runtime dependency to build.gradle fixed it:
dependencies {
runtime("com.h2database:h2:1.4.197")
...
compile group: 'org.apache.ignite', name: 'ignite-spring', version:
'2.7.6'
compile group: 'org.apache.ignite', name: 'ignite-core', version:
'2.7.6'
}
But I suspect this should be getting enforced automatically if using h2
ver1.4.200 breaks something. Am I specifying the Ignite dependency
incorrectly?
On Thu, Feb 20, 2020 at 4:08 AM Taras Ledkov <tl...@gridgain.com> wrote:
> Hi,
>
> Ignite uses H2 version 1.4.197 (see [1]).
>
>
> [1]. https://github.com/apache/ignite/blob/master/parent/pom.xml#L74
>
> On 20.02.2020 4:36, Andrew Munn wrote:
> > I'm building/running my client app w/Gradle and I'm seeing this
> > error. Am I overloading the Ingite H2 fork with the real H2 or
> > something? It appears I have the latest h2:
> >
> > [.gradle]$ find ./ -name *h2*
> > ./caches/modules-2/metadata-2.82/descriptors/com.h2database
> > ./caches/modules-2/metadata-2.82/descriptors/com.h2database/h2
> > ./caches/modules-2/files-2.1/com.h2database
> > ./caches/modules-2/files-2.1/com.h2database/h2
> >
> ./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/6178ecda6e9fea8739a3708729efbffd88be43e3/h2-1.4.200.pom
> >
> ./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/f7533fe7cb8e99c87a43d325a77b4b678ad9031a/h2-1.4.200.jar
> >
> >
> >
> > 2020-02-19 19:59:28.229 ERROR 102356 --- [ main]
> > o.a.i.internal.IgniteKernal%dev-cluster : Exception during start
> > processors, node will be stopped and close connections
> > org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> > to initialize system DB connection:
> >
> jdbc:h2:mem:b52dce26-ba01-4051-9130-e087e19fab4f;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=10000;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.GridH2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine
> > at
> >
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.systemConnection(IgniteH2Indexing.java:434)
>
> > ~[ignite-indexing-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSystemStatement(IgniteH2Indexing.java:699)
>
> > ~[ignite-indexing-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createSchema0(IgniteH2Indexing.java:646)
>
> > ~[ignite-indexing-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:3257)
>
> > ~[ignite-indexing-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:248)
>
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1700)
>
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> > org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1017)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
>
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
>
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> > org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> >
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076)
>
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> > org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at org.apache.ignite.Ignition.start(Ignition.java:348)
> > ~[ignite-core-2.7.6.jar:2.7.6]
> > at
> >
> com.centiva.ig.etl.loader.LoaderApplication.main(LoaderApplication.java:14)
> > ~[main/:na]
> > Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException:
> > Unsupported connection setting "MULTI_THREADED" [90113-200]
> > at
> > org.h2.message.DbException.getJdbcSQLException(DbException.java:622)
> > ~[h2-1.4.200.jar:1.4.200]
>
> --
> Taras Ledkov
> Mail-To: tledkov@gridgain.com
>
>
Re: ERROR: h2 Unsupported connection setting "MULTI_THREADED"
Posted by Taras Ledkov <tl...@gridgain.com>.
Hi,
Ignite uses H2 version 1.4.197 (see [1]).
[1]. https://github.com/apache/ignite/blob/master/parent/pom.xml#L74
On 20.02.2020 4:36, Andrew Munn wrote:
> I'm building/running my client app w/Gradle and I'm seeing this
> error. Am I overloading the Ingite H2 fork with the real H2 or
> something? It appears I have the latest h2:
>
> [.gradle]$ find ./ -name *h2*
> ./caches/modules-2/metadata-2.82/descriptors/com.h2database
> ./caches/modules-2/metadata-2.82/descriptors/com.h2database/h2
> ./caches/modules-2/files-2.1/com.h2database
> ./caches/modules-2/files-2.1/com.h2database/h2
> ./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/6178ecda6e9fea8739a3708729efbffd88be43e3/h2-1.4.200.pom
> ./caches/modules-2/files-2.1/com.h2database/h2/1.4.200/f7533fe7cb8e99c87a43d325a77b4b678ad9031a/h2-1.4.200.jar
>
>
>
> 2020-02-19 19:59:28.229 ERROR 102356 --- [ main]
> o.a.i.internal.IgniteKernal%dev-cluster : Exception during start
> processors, node will be stopped and close connections
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> to initialize system DB connection:
> jdbc:h2:mem:b52dce26-ba01-4051-9130-e087e19fab4f;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=10000;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.GridH2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.systemConnection(IgniteH2Indexing.java:434)
> ~[ignite-indexing-2.7.6.jar:2.7.6]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSystemStatement(IgniteH2Indexing.java:699)
> ~[ignite-indexing-2.7.6.jar:2.7.6]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createSchema0(IgniteH2Indexing.java:646)
> ~[ignite-indexing-2.7.6.jar:2.7.6]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:3257)
> ~[ignite-indexing-2.7.6.jar:2.7.6]
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:248)
> ~[ignite-core-2.7.6.jar:2.7.6]
> at
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1700)
> ~[ignite-core-2.7.6.jar:2.7.6]
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1017)
> ~[ignite-core-2.7.6.jar:2.7.6]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
> ~[ignite-core-2.7.6.jar:2.7.6]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
> ~[ignite-core-2.7.6.jar:2.7.6]
> at
> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
> ~[ignite-core-2.7.6.jar:2.7.6]
> at
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076)
> ~[ignite-core-2.7.6.jar:2.7.6]
> at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962)
> ~[ignite-core-2.7.6.jar:2.7.6]
> at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861)
> ~[ignite-core-2.7.6.jar:2.7.6]
> at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731)
> ~[ignite-core-2.7.6.jar:2.7.6]
> at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700)
> ~[ignite-core-2.7.6.jar:2.7.6]
> at org.apache.ignite.Ignition.start(Ignition.java:348)
> ~[ignite-core-2.7.6.jar:2.7.6]
> at
> com.centiva.ig.etl.loader.LoaderApplication.main(LoaderApplication.java:14)
> ~[main/:na]
> Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException:
> Unsupported connection setting "MULTI_THREADED" [90113-200]
> at
> org.h2.message.DbException.getJdbcSQLException(DbException.java:622)
> ~[h2-1.4.200.jar:1.4.200]
--
Taras Ledkov
Mail-To: tledkov@gridgain.com