Apache Ignite

Back to discussions
Expand all | Collapse all

Exception during start processors,node will be stopped and close connections.WalSegmentSyncer:Runtime error caught during grid runnable execution

  • 1.  Exception during start processors,node will be stopped and close connections.WalSegmentSyncer:Runtime error caught during grid runnable execution

     
    Posted 11-25-2020 11:06 AM
      |   view attached
    Hi! , I'm trying to bring up Apache Ignite server locally and i see the below errors in the log. I downloaded the project from webconsole and didn't do any changes.  Below is the log file for you reference. I attached my server.xml file.

    "C:\Program Files\Java\jdk-15\bin\java.exe" "-javaagent:C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.2\lib\idea_rt.jar=61161:C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.2\bin" -Dfile.encoding=UTF-8 -classpath C:\Work\Raghav\Practice\DuckAirlines-project\target\classes;C:\Users\iprag\.m2\repository\org\gridgain\ignite-core\8.7.9\ignite-core-8.7.9.jar;C:\Users\iprag\.m2\repository\javax\cache\cache-api\1.0.0\cache-api-1.0.0.jar;C:\Users\iprag\.m2\repository\org\jetbrains\annotations\16.0.3\annotations-16.0.3.jar;C:\Users\iprag\.m2\repository\org\gridgain\ignite-shmem\1.0.0\ignite-shmem-1.0.0.jar;C:\Users\iprag\.m2\repository\org\gridgain\ignite-spring\8.7.9\ignite-spring-8.7.9.jar;C:\Users\iprag\.m2\repository\org\springframework\spring-core\4.3.18.RELEASE\spring-core-4.3.18.RELEASE.jar;C:\Users\iprag\.m2\repository\org\springframework\spring-aop\4.3.18.RELEASE\spring-aop-4.3.18.RELEASE.jar;C:\Users\iprag\.m2\repository\org\springframework\spring-beans\4.3.18.RELEASE\spring-beans-4.3.18.RELEASE.jar;C:\Users\iprag\.m2\repository\org\springframework\spring-context\4.3.18.RELEASE\spring-context-4.3.18.RELEASE.jar;C:\Users\iprag\.m2\repository\org\springframework\spring-expression\4.3.18.RELEASE\spring-expression-4.3.18.RELEASE.jar;C:\Users\iprag\.m2\repository\org\springframework\spring-tx\4.3.18.RELEASE\spring-tx-4.3.18.RELEASE.jar;C:\Users\iprag\.m2\repository\org\springframework\spring-jdbc\4.3.18.RELEASE\spring-jdbc-4.3.18.RELEASE.jar;C:\Users\iprag\.m2\repository\commons-logging\commons-logging\1.1.1\commons-logging-1.1.1.jar;C:\Users\iprag\.m2\repository\org\gridgain\ignite-h2\8.7.9\ignite-h2-8.7.9.jar;C:\Users\iprag\.m2\repository\org\locationtech\jts\jts-core\1.15.0\jts-core-1.15.0.jar;C:\Users\iprag\.m2\repository\org\gridgain\ignite-indexing\8.7.9\ignite-indexing-8.7.9.jar;C:\Users\iprag\.m2\repository\commons-codec\commons-codec\1.12\commons-codec-1.12.jar;C:\Users\iprag\.m2\repository\org\apache\lucene\lucene-core\7.4.0\lucene-core-7.4.0.jar;C:\Users\iprag\.m2\repository\org\apache\lucene\lucene-analyzers-common\7.4.0\lucene-analyzers-common-7.4.0.jar;C:\Users\iprag\.m2\repository\org\apache\lucene\lucene-queryparser\7.4.0\lucene-queryparser-7.4.0.jar;C:\Users\iprag\.m2\repository\org\apache\lucene\lucene-queries\7.4.0\lucene-queries-7.4.0.jar;C:\Users\iprag\.m2\repository\org\apache\lucene\lucene-sandbox\7.4.0\lucene-sandbox-7.4.0.jar;C:\Users\iprag\.m2\repository\org\gridgain\ignite-rest-http\8.7.9\ignite-rest-http-8.7.9.jar;C:\Users\iprag\.m2\repository\commons-lang\commons-lang\2.6\commons-lang-2.6.jar;C:\Users\iprag\.m2\repository\org\eclipse\jetty\jetty-continuation\9.4.22.v20191022\jetty-continuation-9.4.22.v20191022.jar;C:\Users\iprag\.m2\repository\org\eclipse\jetty\jetty-http\9.4.22.v20191022\jetty-http-9.4.22.v20191022.jar;C:\Users\iprag\.m2\repository\org\eclipse\jetty\jetty-io\9.4.22.v20191022\jetty-io-9.4.22.v20191022.jar;C:\Users\iprag\.m2\repository\org\eclipse\jetty\jetty-server\9.4.22.v20191022\jetty-server-9.4.22.v20191022.jar;C:\Users\iprag\.m2\repository\org\eclipse\jetty\jetty-util\9.4.22.v20191022\jetty-util-9.4.22.v20191022.jar;C:\Users\iprag\.m2\repository\org\eclipse\jetty\jetty-xml\9.4.22.v20191022\jetty-xml-9.4.22.v20191022.jar;C:\Users\iprag\.m2\repository\javax\servlet\javax.servlet-api\3.1.0\javax.servlet-api-3.1.0.jar;C:\Users\iprag\.m2\repository\com\fasterxml\jackson\core\jackson-core\2.9.9\jackson-core-2.9.9.jar;C:\Users\iprag\.m2\repository\com\fasterxml\jackson\core\jackson-annotations\2.9.9\jackson-annotations-2.9.9.jar;C:\Users\iprag\.m2\repository\com\fasterxml\jackson\core\jackson-databind\2.9.9\jackson-databind-2.9.9.jar;C:\Users\iprag\.m2\repository\org\slf4j\slf4j-api\1.7.7\slf4j-api-1.7.7.jar;C:\Users\iprag\.m2\repository\org\slf4j\slf4j-log4j12\1.7.7\slf4j-log4j12-1.7.7.jar;C:\Users\iprag\.m2\repository\log4j\log4j\1.2.17\log4j-1.2.17.jar;C:\Users\iprag\.m2\repository\mysql\mysql-connector-java\8.0.22\mysql-connector-java-8.0.22.jar;C:\Users\iprag\.m2\repository\com\google\protobuf\protobuf-java\3.11.4\protobuf-java-3.11.4.jar startup.ServerNodeCodeStartup
    WARNING: An illegal reflective access operation has occurred
    WARNING: Illegal reflective access by org.apache.ignite.internal.util.GridUnsafe$2 (file:/C:/Users/iprag/.m2/repository/org/gridgain/ignite-core/8.7.9/ignite-core-8.7.9.jar) to field java.nio.Buffer.address
    WARNING: Please consider reporting this to the maintainers of org.apache.ignite.internal.util.GridUnsafe$2
    WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
    WARNING: All illegal access operations will be denied in a future release
    [16:58:05] __________ ________________
    [16:58:05] / _/ ___/ |/ / _/_ __/ __/
    [16:58:05] _/ // (7 7 // / / / / _/
    [16:58:05] /___/\___/_/|_/___/ /_/ /___/
    [16:58:05]
    [16:58:05] ver. 8.7.9#20191211-sha1:3dcbb8ff
    [16:58:05] 2019 Copyright(C) GridGain Systems, Inc. and Contributors
    [16:58:05]
    [16:58:05] Ignite documentation: http://gridgain.com
    [16:58:05]
    [16:58:05] Quiet mode.
    [16:58:05] ^-- Logging to file 'C:\Work\Raghav\Downloads\apache-ignite-2.9.0-bin\apache-ignite-2.9.0-bin\work\log\ignite-22daed6f.0.log'
    [16:58:05] ^-- Logging by 'JavaLogger [quiet=true, config=null]'
    [16:58:05] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or "-v" to ignite.{sh|bat}
    [16:58:05]
    [16:58:05] OS: Windows 10 10.0 amd64
    [16:58:05] VM information: Java(TM) SE Runtime Environment 15+36-1562 Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 15+36-1562
    [16:58:05] Please set system property '-Djava.net.preferIPv4Stack=true' to avoid possible problems in mixed environments.
    [16:58:05] Initial heap size is 254MB (should be no less than 512MB, use -Xms512m -Xmx512m).
    [16:58:06] Configured plugins:
    [16:58:06] ^-- None
    [16:58:06]
    [16:58:06] Configured failure handler: [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]]]
    [16:58:06] Message queue limit is set to 0 which may lead to potential OOMEs when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to message queues growth on sender and receiver sides.
    [16:58:06] Security status [authentication=off, tls/ssl=off]
    [16:58:10] Both Ignite native persistence and CacheStore are configured for cache 'AirportsCache'. This configuration does not guarantee strict consistency between CacheStore and Ignite data storage upon restarts. Consult documentation for more details.
    [16:58:10] Both Ignite native persistence and CacheStore are configured for cache 'FlightsCache'. This configuration does not guarantee strict consistency between CacheStore and Ignite data storage upon restarts. Consult documentation for more details.
    [16:58:10] Both Ignite native persistence and CacheStore are configured for cache 'FrequentFlyerCache'. This configuration does not guarantee strict consistency between CacheStore and Ignite data storage upon restarts. Consult documentation for more details.
    [16:58:10] Both Ignite native persistence and CacheStore are configured for cache 'CustomersCache'. This configuration does not guarantee strict consistency between CacheStore and Ignite data storage upon restarts. Consult documentation for more details.
    [16:58:10] Both Ignite native persistence and CacheStore are configured for cache 'RunwayCache'. This configuration does not guarantee strict consistency between CacheStore and Ignite data storage upon restarts. Consult documentation for more details.
    [16:58:10] Both Ignite native persistence and CacheStore are configured for cache 'PilotLogsCache'. This configuration does not guarantee strict consistency between CacheStore and Ignite data storage upon restarts. Consult documentation for more details.
    [16:58:10] Both Ignite native persistence and CacheStore are configured for cache 'WindsCache'. This configuration does not guarantee strict consistency between CacheStore and Ignite data storage upon restarts. Consult documentation for more details.
    [16:58:10] Both Ignite native persistence and CacheStore are configured for cache 'TelemetryCache'. This configuration does not guarantee strict consistency between CacheStore and Ignite data storage upon restarts. Consult documentation for more details.
    [16:58:10] Both Ignite native persistence and CacheStore are configured for cache 'FixCache'. This configuration does not guarantee strict consistency between CacheStore and Ignite data storage upon restarts. Consult documentation for more details.
    [16:58:10] Both Ignite native persistence and CacheStore are configured for cache 'CrewCache'. This configuration does not guarantee strict consistency between CacheStore and Ignite data storage upon restarts. Consult documentation for more details.
    [16:58:10] Both Ignite native persistence and CacheStore are configured for cache 'FlightPlansCache'. This configuration does not guarantee strict consistency between CacheStore and Ignite data storage upon restarts. Consult documentation for more details.
    [16:58:10] Both Ignite native persistence and CacheStore are configured for cache 'NavaidCache'. This configuration does not guarantee strict consistency between CacheStore and Ignite data storage upon restarts. Consult documentation for more details.
    [16:58:10] Both Ignite native persistence and CacheStore are configured for cache 'AircraftCache'. This configuration does not guarantee strict consistency between CacheStore and Ignite data storage upon restarts. Consult documentation for more details.
    [16:58:10] Both Ignite native persistence and CacheStore are configured for cache 'RouteMetadataCache'. This configuration does not guarantee strict consistency between CacheStore and Ignite data storage upon restarts. Consult documentation for more details.
    [16:58:10] Both Ignite native persistence and CacheStore are configured for cache 'FleetCache'. This configuration does not guarantee strict consistency between CacheStore and Ignite data storage upon restarts. Consult documentation for more details.
    [16:58:10] Both Ignite native persistence and CacheStore are configured for cache 'RouteSegmentsCache'. This configuration does not guarantee strict consistency between CacheStore and Ignite data storage upon restarts. Consult documentation for more details.
    [16:58:10,638][SEVERE][wal-segment-syncer-#44%DuckAirlines%][FileHandleManagerImpl$WalSegmentSyncer] Runtime error caught during grid runnable execution: GridWorker [name=wal-segment-syncer, igniteInstanceName=DuckAirlines, finished=false, heartbeatTs=1606168690101, hashCode=1326205418, interrupted=false, runner=wal-segment-syncer-#44%DuckAirlines%]
    java.lang.NullPointerException: Cannot invoke "java.lang.reflect.Method.invoke(Object, Object[])" because "org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileWriteHandleImpl.mappingOffset" is null
    at org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileWriteHandleImpl.fsync(FileWriteHandleImpl.java:448)
    at org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileWriteHandleImpl.fsync(FileWriteHandleImpl.java:417)
    at org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileHandleManagerImpl.flush(FileHandleManagerImpl.java:258)
    at org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileHandleManagerImpl$WalSegmentSyncer.body(FileHandleManagerImpl.java:614)
    at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
    at java.base/java.lang.Thread.run(Thread.java:832)
    [16:58:10,786][SEVERE][main][IgniteKernal%DuckAirlines] Exception during start processors, node will be stopped and close connections
    java.lang.NullPointerException: Cannot invoke "java.lang.reflect.Method.invoke(Object, Object[])" because "org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileWriteHandleImpl.mappingOffset" is null
    at org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileWriteHandleImpl.fsync(FileWriteHandleImpl.java:448)
    at org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileWriteHandleImpl.fsync(FileWriteHandleImpl.java:417)
    at org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileHandleManagerImpl.flush(FileHandleManagerImpl.java:258)
    at org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.flush(FileWriteAheadLogManager.java:904)
    at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.tailPointer(GridCacheDatabaseSharedManager.java:2147)
    at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.startMemoryRestore(GridCacheDatabaseSharedManager.java:2075)
    at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1186)
    at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2004)
    at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1692)
    at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1112)
    at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:632)
    at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:557)
    at org.apache.ignite.Ignition.start(Ignition.java:319)
    at startup.ServerNodeCodeStartup.main(ServerNodeCodeStartup.java:15)
    [16:58:10,788][SEVERE][main][IgniteKernal%DuckAirlines] Got exception while starting (will rollback startup routine).
    java.lang.NullPointerException: Cannot invoke "java.lang.reflect.Method.invoke(Object, Object[])" because "org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileWriteHandleImpl.mappingOffset" is null
    at org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileWriteHandleImpl.fsync(FileWriteHandleImpl.java:448)
    at org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileWriteHandleImpl.fsync(FileWriteHandleImpl.java:417)
    at org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileHandleManagerImpl.flush(FileHandleManagerImpl.java:258)
    at org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.flush(FileWriteAheadLogManager.java:904)
    at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.tailPointer(GridCacheDatabaseSharedManager.java:2147)
    at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.startMemoryRestore(GridCacheDatabaseSharedManager.java:2075)
    at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1186)
    at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2004)
    at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1692)
    at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1112)
    at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:632)
    at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:557)
    at org.apache.ignite.Ignition.start(Ignition.java:319)
    at startup.ServerNodeCodeStartup.main(ServerNodeCodeStartup.java:15)

    Server.xml


    ------------------------------
    Rag
    ------------------------------

    Attachment(s)

    xml
    DuckAirlines-server.xml   418 KB 1 version


  • 2.  RE: Exception during start processors,node will be stopped and close connections.WalSegmentSyncer:Runtime error caught during grid runnable execution

    Posted 11-25-2020 11:59 PM
    Hello!

    Neither Apache Ignite nor GridGain are compatible with Java 15 at the moment. Please use Java 11 instead.

    Regards,

    ------------------------------
    Ilya Kasnacheev
    Community Support Specialist
    GridGain
    ------------------------------

    Original Message


  • 3.  RE: Exception during start processors,node will be stopped and close connections.WalSegmentSyncer:Runtime error caught during grid runnable execution

     
    Posted 11-29-2020 07:09 PM
    Thanks!  Using Java 11 helped me start the ignite node. When i try to activate the cluster using the control program , i'm seeing the following error related to SSL configuration. I'm running everything locally. Do i still need to explicitly configure the SSL ? Can you please point me to any resources ? 

    This is the error logged in the Ignite server log. 
    [21:45:53] Unknown connection detected (is some other software connecting to this Ignite port? missing SSL configuration on remote node?) [rmtAddr=/127.0.0.1]

    Control program output 
    control --port 47500 --activate
    WARNING: An illegal reflective access operation has occurred
    WARNING: Illegal reflective access by org.apache.ignite.internal.util.GridUnsafe$2 (file:/C:/Work/Raghav/Downloads/apache-ignite-2.9.0-bin/apache-ignite-2.9.0-bin/libs/ignite-core-2.9.0.jar) to field java.nio.Buffer.address
    WARNING: Please consider reporting this to the maintainers of org.apache.ignite.internal.util.GridUnsafe$2
    WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
    WARNING: All illegal access operations will be denied in a future release
    Control utility [ver. 2.9.0#20201015-sha1:70742da8]
    2020 Copyright(C) Apache Software Foundation
    User: iprag
    Time: 2020-11-29T21:45:52.864720300
    Command [ACTIVATE] started
    Arguments: --port 47500 --activate
    --------------------------------------------------------------------------------
    Command deprecated. Use --set-state instead.
    Failed to activate cluster.
    Connection to cluster failed. Please check firewall settings and client and server are using the same SSL configuration.
    Command [ACTIVATE] finished with code: 2
    Control utility has completed execution at: 2020-11-29T21:45:56.821966500
    Execution time: 3957 ms
    Press any key to continue . . .

    I had passed port 47500 to the control program based on the following setting in server.xml file. 
    <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>127.0.0.1:47500..47510</value>
                        </list>
                    </property>
                </bean>
            </property>
        </bean>
    </property>


    ------------------------------
    Rag
    ------------------------------

    Original Message


  • 4.  RE: Exception during start processors,node will be stopped and close connections.WalSegmentSyncer:Runtime error caught during grid runnable execution

    Posted 11-30-2020 01:05 AM
    Hello!

    control.sh should use port 11211 or possibly 11212 (binary REST). It should not use port 47500 (discovery).

    Regards,

    ------------------------------
    Ilya Kasnacheev
    Community Support Specialist
    GridGain
    ------------------------------

    Original Message


  • 5.  RE: Exception during start processors,node will be stopped and close connections.WalSegmentSyncer:Runtime error caught during grid runnable execution

     
    Posted 11-30-2020 07:37 AM
    It failed with the default  port 11211  and 11212 as well 

    control --activate
    WARNING: An illegal reflective access operation has occurred
    WARNING: Illegal reflective access by org.apache.ignite.internal.util.GridUnsafe$2 (file:/C:/Work/Raghav/Downloads/apache-ignite-2.9.0-bin/apache-ignite-2.9.0-bin/libs/ignite-core-2.9.0.jar) to field java.nio.Buffer.address
    WARNING: Please consider reporting this to the maintainers of org.apache.ignite.internal.util.GridUnsafe$2
    WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
    WARNING: All illegal access operations will be denied in a future release
    Control utility [ver. 2.9.0#20201015-sha1:70742da8]
    2020 Copyright(C) Apache Software Foundation
    User: iprag
    Time: 2020-11-29T21:40:19.799581400
    Command [ACTIVATE] started
    Arguments: --activate
    --------------------------------------------------------------------------------
    Command deprecated. Use --set-state instead.
    Failed to activate cluster.
    Connection to cluster failed. Failed to perform request (connection failed): /127.0.0.1:11211
    Command [ACTIVATE] finished with code: 2
    Control utility has completed execution at: 2020-11-29T21:40:20.928798700
    Execution time: 1129 ms
    Press any key to continue . . .
    control --port 11212 --activate
    WARNING: An illegal reflective access operation has occurred
    WARNING: Illegal reflective access by org.apache.ignite.internal.util.GridUnsafe$2 (file:/C:/Work/Raghav/Downloads/apache-ignite-2.9.0-bin/apache-ignite-2.9.0-bin/libs/ignite-core-2.9.0.jar) to field java.nio.Buffer.address
    WARNING: Please consider reporting this to the maintainers of org.apache.ignite.internal.util.GridUnsafe$2
    WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
    WARNING: All illegal access operations will be denied in a future release
    Control utility [ver. 2.9.0#20201015-sha1:70742da8]
    2020 Copyright(C) Apache Software Foundation
    User: iprag
    Time: 2020-11-30T10:33:11.161964600
    Command [ACTIVATE] started
    Arguments: --port 11212 --activate
    --------------------------------------------------------------------------------
    Command deprecated. Use --set-state instead.
    Failed to activate cluster.
    Connection to cluster failed. Latest topology update failed.
    Command [ACTIVATE] finished with code: 2
    Control utility has completed execution at: 2020-11-30T10:33:20.708796900
    Execution time: 9546 ms
    Press any key to continue . . .

    I don't see any updates/errors in the Ignite server log

    ------------------------------
    Rag
    ------------------------------

    Original Message


  • 6.  RE: Exception during start processors,node will be stopped and close connections.WalSegmentSyncer:Runtime error caught during grid runnable execution

    Posted 11-30-2020 07:49 AM
    Hello!

    Are you sure that GridGain was running at the time, on the same host?

    Can you please enable verbose logging (ignite.sh -v, or -DIGNITE_QUIET=false) and share the >>> Local ports: line from log?

    Regards,

    ------------------------------
    Ilya Kasnacheev
    Community Support Specialist
    GridGain
    ------------------------------

    Original Message


  • 7.  RE: Exception during start processors,node will be stopped and close connections.WalSegmentSyncer:Runtime error caught during grid runnable execution

     
    Posted 11-30-2020 08:00 AM
    Yes , it is running on the same host.
    From the server log. 
    >>> Local ports: TCP:8080 TCP:10800 TCP:11211 TCP:47100 TCP:47500

    ------------------------------
    Rag
    ------------------------------

    Original Message


  • 8.  RE: Exception during start processors,node will be stopped and close connections.WalSegmentSyncer:Runtime error caught during grid runnable execution

    Posted 12-02-2020 06:02 AM
    Hello!

    Should be all right then! Can you check what's in the log? It's named control-utility-*.log and it should reside somewhere under the work directory. Please also add --verbose arg to the control.sh invocation.

    Regards,

    ------------------------------
    Ilya Kasnacheev
    Community Support Specialist
    GridGain
    ------------------------------

    Original Message


  • 9.  RE: Exception during start processors,node will be stopped and close connections.WalSegmentSyncer:Runtime error caught during grid runnable execution

     
    Posted 12-02-2020 07:40 PM
    This is what the ports are in the Ignite Server log. 
    [22:30:46,974][INFO][main][IgniteKernal%DuckAirlines]

    >>> +----------------------------------------------------------------------+
    >>> Ignite ver. 8.7.9#20191211-sha1:3dcbb8ffaba7e9bc5c3b13df23c1aa6f5c803598
    >>> +----------------------------------------------------------------------+
    >>> OS name: Windows 10 10.0 amd64
    >>> CPU(s): 8
    >>> Heap: 4.0GB
    >>> VM name: 6056@LAPTOP-34M4O1MJ
    >>> Ignite instance name: DuckAirlines
    >>> Local node [ID=EF2E5A0A-2A26-46B7-9546-5405E0809D1F, order=1, clientMode=false]
    >>> Local node addresses: [LAPTOP-34M4O1MJ/0:0:0:0:0:0:0:1, /127.0.0.1, /192.168.1.23]
    >>> Local ports: TCP:8080 TCP:10800 TCP:11211 TCP:47100 TCP:47500

    This is the exception in the control-utilty.log .

    [22:32:27,732][INFO][session=67334792][CommandHandlerLog] Control utility [ver. 2.9.0#20201015-sha1:70742da8]
    [22:32:27,733][INFO][session=67334792][CommandHandlerLog] 2020 Copyright(C) Apache Software Foundation
    [22:32:27,733][INFO][session=67334792][CommandHandlerLog] User: iprag
    [22:32:27,733][INFO][session=67334792][CommandHandlerLog] Time: 2020-12-02T22:32:27.721570200
    [22:32:27,775][INFO][session=67334792][CommandHandlerLog] Command [ACTIVATE] started
    [22:32:27,775][INFO][session=67334792][CommandHandlerLog] Arguments: --verbose --activate
    [22:32:27,775][INFO][session=67334792][CommandHandlerLog] --------------------------------------------------------------------------------
    [22:32:27,776][WARNING][session=67334792][CommandHandlerLog] Command deprecated. Use --set-state instead.
    [22:32:28,389][SEVERE][session=67334792][CommandHandlerLog] Failed to activate cluster.
    [22:32:28,389][SEVERE][session=67334792][CommandHandlerLog] Connection to cluster failed. Failed to perform request (connection failed): /127.0.0.1:11211
    [22:32:28,389][INFO][session=67334792][CommandHandlerLog] Command [ACTIVATE] finished with code: 2
    [22:32:28,389][INFO][session=67334792][CommandHandlerLog] Error stack trace:
    class org.apache.ignite.internal.client.impl.connection.GridClientConnectionResetException: Failed to perform request (connection failed): /127.0.0.1:11211
    at org.apache.ignite.internal.client.impl.connection.GridClientConnection.getCloseReasonAsException(GridClientConnection.java:523)
    at org.apache.ignite.internal.client.impl.connection.GridClientNioTcpConnection.close(GridClientNioTcpConnection.java:351)
    at org.apache.ignite.internal.client.impl.connection.GridClientNioTcpConnection.close(GridClientNioTcpConnection.java:311)
    at org.apache.ignite.internal.client.impl.connection.GridClientConnectionManagerAdapter$NioListener.onDisconnected(GridClientConnectionManagerAdapter.java:623)
    at org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onSessionClosed(GridNioFilterChain.java:256)
    at org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedSessionClosed(GridNioFilterAdapter.java:95)
    at org.apache.ignite.internal.util.nio.GridNioCodecFilter.onSessionClosed(GridNioCodecFilter.java:71)
    at org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedSessionClosed(GridNioFilterAdapter.java:95)
    at org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onSessionClosed(GridNioServer.java:3649)
    at org.apache.ignite.internal.util.nio.GridNioFilterChain.onSessionClosed(GridNioFilterChain.java:149)
    at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.close(GridNioServer.java:2841)
    at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.close(GridNioServer.java:2758)
    at org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:1170)
    at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2472)
    at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2239)
    at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1880)
    at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
    at java.base/java.lang.Thread.run(Thread.java:834)

    [22:32:28,389][INFO][session=67334792][CommandHandlerLog] Control utility has completed execution at: 2020-12-02T22:32:28.389762200
    [22:32:28,389][INFO][session=67334792][CommandHandlerLog] Execution time: 668 ms

    ------------------------------
    Rag
    ------------------------------

    Original Message


  • 10.  RE: Exception during start processors,node will be stopped and close connections.WalSegmentSyncer:Runtime error caught during grid runnable execution

    Posted 12-03-2020 02:35 AM
    Hello!

    I have noticed that you're using GridGain 8.7.9 on server node but Apache Ignite 2.9's control utility.

    Please check the same scenario with the identical version of GridGain (preferably, a fresh one such as 8.7.31

    GridGain Software Downloads

    Regards,

    ------------------------------
    Ilya Kasnacheev
    Community Support Specialist
    GridGain
    ------------------------------

    Original Message


  • 11.  RE: Exception during start processors,node will be stopped and close connections.WalSegmentSyncer:Runtime error caught during grid runnable execution

     
    Posted 12-07-2020 08:28 PM
      |   view attached
    Thanks! By using the same version of Grid Gain(8.7.9) control utility, i was able to get everything up and running. I have run some code to load the grid gain cache from MySQL database and that has gone through successfully. 

    Example code of loading the caches which ran successfully. 
    Ignite ignite = Ignition.start("DuckAirlines-client.xml")) {
        ignite.cluster().active(true);

        System.out.println(">>> Loading caches...");

        System.out.println(">>> Loading cache: AircraftCache");
        ignite.cache("AircraftCache").loadCache(null);

    But when i try to run the query from GridGain WebConsole, it complains that table doesn't exist.  Is there something i'm missing here. I had attached the screenshot of the GridGain WebConsole error for you reference. 

    This is what is running behind the scenes
    1. Ignite server
    2. Ignite cluster activated using control agent(completed successfully) 
    3. Ignite webconsole Agent


    ------------------------------
    Rag
    ------------------------------

    Original Message


  • 12.  RE: Exception during start processors,node will be stopped and close connections.WalSegmentSyncer:Runtime error caught during grid runnable execution

    Posted 12-09-2020 06:58 AM
    Hello!

    Try specifying explicit schema for cache: 
    SELECT * FROM "AircraftCache".Airports LIMIT 1;


    ------------------------------
    Ilya Kasnacheev
    Community Support Specialist
    GridGain
    ------------------------------

    Original Message


  • 13.  RE: Exception during start processors,node will be stopped and close connections.WalSegmentSyncer:Runtime error caught during grid runnable execution

     
    Posted 12-09-2020 12:58 PM
    Thanks! That worked.

    ------------------------------
    Rag
    ------------------------------

    Original Message