Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

classic Classic list List threaded Threaded
22 messages Options
12
Ankit Singhai Ankit Singhai
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

This post was updated on .
Hi All,
I am trying to create an searchable cache where in Linux environment I am getting the below exception everytime but not getting it in my Windows laptop.

org.apache.ignite.IgniteCheckedException: Failed to register query type: QueryTypeDescriptorImpl [space=loginServiceTokenCacheIgnite, name=TokenSessionDetails, tblName=null, fields={globalSessionId=class java.lang.String, serviceSessionId=class java.lang.String, serviceId=class java.lang.String, bindingKey=class java.lang.String, tokenScope=class java.lang.Object}, idxs={}, fullTextIdx=null, keyCls=class java.lang.String, valCls=class java.lang.Object, keyTypeName=java.lang.String, valTypeName=com.pg.loginservice.tokenmanagement.data.TokenSessionDetails, valTextIdx=false, typeId=0, affKey=null, keyFieldName=null, valFieldName=null, obsolete=false]
        at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:1866) ~[ignite-indexing-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.query.GridQueryProcessor.registerCache0(GridQueryProcessor.java:1306) ~[ignite-core-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:756) ~[ignite-core-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:817) ~[ignite-core-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1265) ~[ignite-core-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1943) ~[ignite-core-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1833) ~[ignite-core-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:379) ~[ignite-core-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:688) ~[ignite-core-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:529) [ignite-core-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1806) [ignite-core-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) [ignite-core-2.0.0.jar:2.0.0]
        at java.lang.Thread.run(Thread.java:744) [?:1.7.0_45]
Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it [lock=00007f4c31441960, state=0002ffff0000280d"; SQL statement:
CREATE TABLE "loginServiceTokenCacheIgnite".TokenSessionDetails (_key VARCHAR INVISIBLE NOT NULL,_val OTHER INVISIBLE,_ver OTHER INVISIBLE,globalSessionId VARCHAR,serviceSessionId VARCHAR,serviceId VARCHAR,bindingKey VARCHAR,tokenScope OTHER) engine "org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$H2TableEngine" [50000-195]
        at org.h2.message.DbException.getJdbcSQLException(DbException.java:345) ~[h2-1.4.195.jar:1.4.195]
        at org.h2.message.DbException.get(DbException.java:168) ~[h2-1.4.195.jar:1.4.195]
        at org.h2.message.DbException.convert(DbException.java:295) ~[h2-1.4.195.jar:1.4.195]
        at org.h2.command.Command.executeUpdate(Command.java:268) ~[h2-1.4.195.jar:1.4.195]
        at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:193) ~[h2-1.4.195.jar:1.4.195]
        at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:165) ~[h2-1.4.195.jar:1.4.195]
        at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$H2TableEngine.createTable(IgniteH2Indexing.java:3975) ~[ignite-indexing-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createTable(IgniteH2Indexing.java:2006) ~[ignite-indexing-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:1859) ~[ignite-indexing-2.0.0.jar:2.0.0]
        ... 12 more
Caused by: java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it [lock=00007f4c31441960, state=0002ffff0000280d
        at org.apache.ignite.internal.util.OffheapReadWriteLock.writeUnlock(OffheapReadWriteLock.java:259) ~[ignite-core-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.writeUnlock(PageMemoryNoStoreImpl.java:495) ~[ignite-core-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.cache.database.tree.util.PageHandler.writeUnlock(PageHandler.java:379) ~[ignite-core-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.cache.database.tree.util.PageHandler.writePage(PageHandler.java:288) ~[ignite-core-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.cache.database.tree.util.PageHandler.initPage(PageHandler.java:225) ~[ignite-core-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.cache.database.DataStructure.init(DataStructure.java:328) ~[ignite-core-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.initTree(BPlusTree.java:796) ~[ignite-core-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.query.h2.database.H2Tree.<init>(H2Tree.java:110) ~[ignite-indexing-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex$1.<init>(H2TreeIndex.java:123) ~[ignite-indexing-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.<init>(H2TreeIndex.java:112) ~[ignite-indexing-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createSortedIndex(IgniteH2Indexing.java:947) ~[ignite-indexing-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.access$2800(IgniteH2Indexing.java:241) ~[ignite-indexing-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$TableDescriptor.createSystemIndexes(IgniteH2Indexing.java:3131) ~[ignite-indexing-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.<init>(GridH2Table.java:153) ~[ignite-indexing-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$H2TableEngine.createTable(IgniteH2Indexing.java:3992) ~[ignite-indexing-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$H2TableEngine.createTable(IgniteH2Indexing.java:3942) ~[ignite-indexing-2.0.0.jar:2.0.0]
        at org.h2.schema.Schema.createTable(Schema.java:612) ~[h2-1.4.195.jar:1.4.195]
        at org.h2.command.ddl.CreateTable.update(CreateTable.java:139) ~[h2-1.4.195.jar:1.4.195]
        at org.h2.command.CommandContainer.update(CommandContainer.java:101) ~[h2-1.4.195.jar:1.4.195]
        at org.h2.command.Command.executeUpdate(Command.java:260) ~[h2-1.4.195.jar:1.4.195]
        at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:193) ~[h2-1.4.195.jar:1.4.195]
        at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:165) ~[h2-1.4.195.jar:1.4.195]
        at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$H2TableEngine.createTable(IgniteH2Indexing.java:3975) ~[ignite-indexing-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createTable(IgniteH2Indexing.java:2006) ~[ignite-indexing-2.0.0.jar:2.0.0]
        at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:1859) ~[ignite-indexing-2.0.0.jar:2.0.0]
        ... 12 more


My cache config

    <bean id="loginServiceTokenCacheIgnite" class="org.apache.ignite.configuration.CacheConfiguration" scope="singleton">
        <property name="name" value="loginServiceTokenCacheIgnite"/>
        <property name="cacheMode" value="PARTITIONED"/>
        <property name="backups" value="1"/>
        <property name="writeSynchronizationMode" value="FULL_SYNC"/>
        <property name="statisticsEnabled" value="true"/>
        <property name="expiryPolicyFactory" ref="loginServiceTokenExpiryPolicyFactory"/>
        <property name="rebalanceMode" value="ASYNC"/>
        <property name="rebalanceBatchSize" value="#{1024 * 1024}"/>
        <property name="rebalanceThrottle" value="0"/>
        <property name="rebalanceThreadPoolSize" value="4"/>
        <property name="queryEntities">
            <list>
                <bean class="org.apache.ignite.cache.QueryEntity">
                    <property name="keyType" value="java.lang.String"/>
                    <property name="valueType" value="com.pg.loginservice.tokenmanagement.data.TokenSessionDetails"/>
                    <property name="fields">
                        <map>
                            <entry key="globalSessionId" value="java.lang.String"/>
                            <entry key="serviceSessionId" value="java.lang.String"/>
                            <entry key="serviceId" value="java.lang.String"/>
                            <entry key="bindingKey" value="java.lang.String"/>
                            <entry key="tokenScope" value="com.pg.loginservice.api.TokenScope"/>
                        </map>
                    </property>
                    <property name="indexes">
                        <list>
                            <bean class="org.apache.ignite.cache.QueryIndex">
                                <constructor-arg value="globalSessionId"/>
                            </bean>
                            <bean class="org.apache.ignite.cache.QueryIndex">
                                <constructor-arg value="serviceSessionId"/>
                            </bean>
                            <bean class="org.apache.ignite.cache.QueryIndex">
                                <constructor-arg value="serviceId"/>
                            </bean>
                            <bean class="org.apache.ignite.cache.QueryIndex">
                                <constructor-arg value="bindingKey"/>
                            </bean>
                        </list>
                    </property>
                                </bean>
                         </list>
        </property>
    </bean>

    <bean id="loginServiceTokenExpiryPolicyFactory"
          class="javax.cache.configuration.FactoryBuilder" factory-method="factoryOf">
        <constructor-arg ref="loginServiceTokenAccessedExpiryPolicy"/>
    </bean>

    <bean id="loginServiceTokenAccessedExpiryPolicy" class="javax.cache.expiry.EternalExpiryPolicy">
    </bean>
       
Ignite Config XML
<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="
        http://www.springframework.org/schema/beans
        http://www.springframework.org/schema/beans/spring-beans.xsd">

        <bean id="ignite.cfg" class="org.apache.ignite.configuration.IgniteConfiguration">
        <property name="clientMode" value="${clientMode}"/>
        <property name="igniteInstanceName" value="LoginServices"/>
        <property name="peerClassLoadingEnabled" value="false"/>
        <property name="metricsUpdateFrequency" value="2000" />
        <property name="discoverySpi">
            <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
                <property name="ipFinder">
                    <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
                        <property name="addresses">
                            <list>
                               
                                <value>10.1.54.66:47500..47509</value>
                            </list>
                        </property>
                    </bean>
                </property>
                <property name="localAddress" value="${hostname}"/>
                <property name="reconnectCount" value="100"/>
                <property name="networkTimeout" value="10000"/>
                <property name="socketTimeout" value="10000"/>
                <property name="ackTimeout" value="10000"/>
                <property name="statisticsPrintFrequency" value="60000"/>
            </bean>
        </property>

        <property name="communicationSpi">
            <bean class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
                <property name="localAddress" value="${hostname}"/>
                <property name="slowClientQueueLimit" value="18000"/>
                <property name="messageQueueLimit" value="20000"/>
                <property name="localPort" value="9090"/>
                <property name="connectTimeout" value="5000"/>
                <property name="idleConnectionTimeout" value="75000"/>
                <property name="sharedMemoryPort" value="-1"/>
            </bean>
        </property>
   

        <property name="memoryConfiguration">
            <bean class="org.apache.ignite.configuration.MemoryConfiguration">
                <property name="memoryPolicies">
                    <list>
                        <bean class="org.apache.ignite.configuration.MemoryPolicyConfiguration">
                            <property name="name" value="loginServiceOffHeap"/>
                            <property name="initialSize" value="#{ 256L * 1024 * 1024}"/>
                            <property name="maxSize" value="#{ 512L * 1024 * 1024}"/>
                            <property name="pageEvictionMode" value="RANDOM_LRU"/>
                            <property name="metricsEnabled" value="true"/>
                        </bean>
                    </list>
                </property>
            <property name="defaultMemoryPolicyName" value="loginServiceOffHeap"/>
        </bean>
    </property>
    </bean>
</beans>
                   

public class TokenSessionDetails
        implements Serializable
{
    private static final long serialVersionUID = 1L;
    private String bindingKey;
    private String globalSessionId;
    private String serviceSessionId;
    private String serviceId;
    private TokenScope tokenScope;

    public TokenSessionDetails(String bindingKey, String globalSessionId, String serviceSessionId, String serviceId, TokenScope tokenScope)
    {
        this.bindingKey = bindingKey;
        this.globalSessionId = globalSessionId;
        this.serviceSessionId = serviceSessionId;
        this.serviceId = serviceId;
        this.tokenScope = tokenScope;
    }

    public String getBindingKey()
    {
        return this.bindingKey;
    }

    public String getGlobalSessionId() {
        return this.globalSessionId;
    }

    public String getServiceSessionId() {
        return this.serviceSessionId;
    }

    public String getServiceId() {
        return this.serviceId;
    }

    public TokenScope getTokenScope() {
        return this.tokenScope;
    }

    public void setTokenScope(TokenScope tokenScope) {
        this.tokenScope = tokenScope;
    }
}

public enum TokenScope
{
    SERVICE_SESSION_SCOPE, GLOBAL_SESSION_SCOPE;
}

Note :- In Ignite server I had used -XX:MaxDirectMemorySize=512m

Any suggestions what might be causing this behaviour.
Ankit Singhai Ankit Singhai
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

Hi Folks,
Any help on the above issue.

Regards,
Ankit Singhai
afedotov afedotov
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

Hi Ankit,

Is the issue reproducible on every run or intermittent?
What are the OS and JDK versions in each environment?
Please share full logs.
As well, could you please share a Maven/Gradle based reproducer?

Kind regards,
Alex

27 июля 2017 г. 8:09 AM пользователь "Ankit Singhai [via Apache Ignite Users]" <[hidden email]> написал:
Hi Folks,
Any help on the above issue.

Regards,
Ankit Singhai


To start a new topic under Apache Ignite Users, email [hidden email]
To unsubscribe from Apache Ignite Users, click here.
NAML

Ankit Singhai Ankit Singhai
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

Hi Alex,
Yes it is reproducible every time.
Linux Version:-
Linux 3.10.0-514.26.1.el7.x86_64 #1 SMP Wed Jun 28 20:34:34 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Java Version:-
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)

I have already posted grid & cache config xmls. POJO is also available please use that.

Regards,
Ankit Singhai
afedotov afedotov
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

Ankit thanks for the info.
I'll try to reproduce it on my side and get back to you.

Kind regards,
Alex.

On Thu, Jul 27, 2017 at 10:05 AM, Ankit Singhai [via Apache Ignite Users] <[hidden email]> wrote:
Hi Alex,
Yes it is reproducible every time.
Linux Version:-
Linux 3.10.0-514.26.1.el7.x86_64 #1 SMP Wed Jun 28 20:34:34 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Java Version:-
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)

I have already posted grid & cache config xmls. POJO is also available please use that.

Regards,
Ankit Singhai


To start a new topic under Apache Ignite Users, email [hidden email]
To unsubscribe from Apache Ignite Users, click here.
NAML

Ankit Singhai Ankit Singhai
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

Hi Alex,
Today I tried the same use-case with Apache Ignite 2.1.0. I am getting the same error, attaching the log.
Waiting for your analysis.ignite-c8506efe.zip

Regards,
Ankit Singhai
Ankit Singhai Ankit Singhai
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

Hi Alex,
Did you get an chance to look at this?
Now I am getting this error for both searchable and non-searchable caches.

Thanks,
Ankit Singhai
Ankit Singhai Ankit Singhai
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

Hi Alex / Folks,
PFA zip containing:-
1. Server log
2. Grid Config
3. Java class to initialise all caches
4. Cache CoException_In_Ignite.zipnfig
5. Few POJOs

Please try to replicate at your end and we are stuck at this issue.

Regards,
Ankit Singhai
Ankit Singhai Ankit Singhai
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

Please check folks

On 31-Jul-2017 13:33, "Ankit Singhai [via Apache Ignite Users]" <[hidden email]> wrote:
Hi Alex / Folks,
PFA zip containing:-
1. Server log
2. Grid Config
3. Java class to initialise all caches
4. Cache CoException_In_Ignite.zipnfig
5. Few POJOs

Please try to replicate at your end and we are stuck at this issue.

Regards,
Ankit Singhai


To start a new topic under Apache Ignite Users, email [hidden email]
To unsubscribe from Apache Ignite Users, click here.
NAML
afedotov afedotov
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

Hi Ankit,

Sorry I was busy a bit lately. I'll proceed with the investigation and give you an update.

Kind regards,
Alex.

On Tue, Aug 1, 2017 at 5:31 PM, Ankit Singhai [via Apache Ignite Users] <[hidden email]> wrote:
Please check folks

On 31-Jul-2017 13:33, "Ankit Singhai [via Apache Ignite Users]" <[hidden email]> wrote:
Hi Alex / Folks,
PFA zip containing:-
1. Server log
2. Grid Config
3. Java class to initialise all caches
4. Cache CoException_In_Ignite.zipnfig
5. Few POJOs

Please try to replicate at your end and we are stuck at this issue.

Regards,
Ankit Singhai


To start a new topic under Apache Ignite Users, email [hidden email]
To unsubscribe from Apache Ignite Users, click here.
NAML



To start a new topic under Apache Ignite Users, email [hidden email]
To unsubscribe from Apache Ignite Users, click here.
NAML

Ankit Singhai Ankit Singhai
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

Hi Alex,
Did you get an chance to look at it ?

Regards,
Ankit Singhai
Ankit Singhai Ankit Singhai
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

Hi Folks,
Did anyone facing this issue? Can you please look into it?

Regards,
Ankit Singhai
ezhuravlev ezhuravlev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

Hi,
I tried to run your code on Linux, but everything works fine for me. One thing - I don't see SSL configuration in your config files, while your log contains information that SSL was enabled. Is the same behavior reproducible without SSL?

Also, I see that you use both ipv4 and ipv6, possibly it could lead to the problem that was shown in the log - when a client was unable to connect to the server at the first time. Try to run all nodes with -Djava.net.preferIPv4Stack=true property.


Ankit Singhai Ankit Singhai
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

Hi,
SSL is configured in java code and I didn't try to replicate it w/o SSL. I will add the property -Djava.net.preferIPv4Stack=true and post the results.
Ankit Singhai Ankit Singhai
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

This post was updated on .
PFA log. No luck even by setting the flag IPV4 = true.
ignite-de5180fb.zip

Do you have any recommendation for Java & RHEL kernel version ? Please share your test environment details.

Regards,
Ankit Singhai
ezhuravlev ezhuravlev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

I would suggest updating to the last version of java and check if it will work. I can't reproduce same behavior with your code, but I use java 1.8.0_121-b13.

Please share results after updating.

Evgenii

2017-08-08 15:28 GMT+03:00 Ankit Singhai <[hidden email]>:
PFA log. No luck even by setting the flag for IPV4 = true.
ignite-de5180fb.zip
<http://apache-ignite-users.70518.x6.nabble.com/file/n16050/ignite-de5180fb.zip>



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p16050.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Ankit Singhai Ankit Singhai
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

Even disabling TLS/SSL doesn't have any effect. Moving to Java 1.8 is not an option as we have other dependencies which are incompatible with 1.8.

Any other suggestion?

Regards,
Ankit Singhai
ezhuravlev ezhuravlev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

Yes, It's possible to check the last update of java 1.7

Evgenii

2017-08-08 16:42 GMT+03:00 Ankit Singhai <[hidden email]>:
Even disabling TLS/SSL doesn't have any effect. Moving to Java 1.8 is not an
option as we have other dependencies which are incompatible with 1.8.

Any other suggestion?

Regards,
Ankit Singhai




--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p16054.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

ezhuravlev ezhuravlev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

I tried your code with java 1.7.0_80-b15 and everything works fine.

Also, check that you use right config file - you provided a file with name ignite-config.xml.xml, but in the code, you use ignite-config-login.xml.

Evgenii

2017-08-08 16:44 GMT+03:00 Evgenii Zhuravlev <[hidden email]>:
Yes, It's possible to check the last update of java 1.7

Evgenii

2017-08-08 16:42 GMT+03:00 Ankit Singhai <[hidden email]>:
Even disabling TLS/SSL doesn't have any effect. Moving to Java 1.8 is not an
option as we have other dependencies which are incompatible with 1.8.

Any other suggestion?

Regards,
Ankit Singhai




--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p16054.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


Neelesh Neelesh
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

java 1.7.0_67 definitely has this issue with ignite 1.9, 2.0 and 2.1. We do not see this issue with java 8

On Tue, Aug 8, 2017 at 6:56 AM, Evgenii Zhuravlev <[hidden email]> wrote:
I tried your code with java 1.7.0_80-b15 and everything works fine.

Also, check that you use right config file - you provided a file with name ignite-config.xml.xml, but in the code, you use ignite-config-login.xml.

Evgenii

2017-08-08 16:44 GMT+03:00 Evgenii Zhuravlev <[hidden email]>:
Yes, It's possible to check the last update of java 1.7

Evgenii

2017-08-08 16:42 GMT+03:00 Ankit Singhai <[hidden email]>:
Even disabling TLS/SSL doesn't have any effect. Moving to Java 1.8 is not an
option as we have other dependencies which are incompatible with 1.8.

Any other suggestion?

Regards,
Ankit Singhai




--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p16054.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.



12
Loading...