ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt Semba (Jira)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-12151) Load Cache: Failed to load bean in app context
Date Mon, 09 Sep 2019 10:21:00 GMT
Kurt Semba created IGNITE-12151:
-----------------------------------

             Summary: Load Cache: Failed to load bean in app context
                 Key: IGNITE-12151
                 URL: https://issues.apache.org/jira/browse/IGNITE-12151
             Project: Ignite
          Issue Type: Bug
          Components: binary, cache
    Affects Versions: 2.7.5
         Environment: * Ubuntu 18.04
 * Ignite server v2.7.5 - running in a docker container with the REST API module enabled
 * Ignite web-console: 2.7.0 - also running in a docker container
 * Ignite web-agent - downloaded from the web-console so I assume also using version 2.7.0
- not running in a docker container (properly connects to both the web-console as well as
the cluster... until I kill my cluster ;) )
 * MySQL DB: v5.7 running on a remote VM
 * IDE: Visual Studio Code (latest update)
            Reporter: Kurt Semba
         Attachments: Dockerfile, clientLoadCaches.log, cluster.log

Hi team,

I was following the instructions from  [https://www.youtube.com/watch?v=SJ6h55VhUBI] and
onwards to use the web-console and web-agent to import data from a MySQL DB. It all works
fine until I download the cluster configuration Java project from the web-console and try
to run the "LoadCaches" java file in my IDE. 

The client (LoadCaches code) fails with an "IgniteCheckedException: Failed to connect to node"
exception but more importantly, the ignite cluster crashes as well with an "IgniteException:
Failed to load bean in application context" exception. See both logs attached. 

The parts where I diverged from the demo video series:
 * I did not tweak the cluster config using the web-console - just kept it as it was auto-created
by the web-console
 * I edited  /src/main/resources/META-INF/ImportedCluster-client.xml and configured the IP
of my Ignite cluster (both the ignite cluster and the IDE code are running on the same server,
but using the default 127.0.0.1 didn't connect)
 * I edited the pom.xml file to make the Java code use the latest v2.7.5 libraries to load
the cache (since the cluster is also running this version)

 

Do I have to somehow pre-stage the cluster / cache with the DB table I'm trying to import?
I was hoping that the web-console would do that when I use the "Import from Database" wizard?

Maybe the version mismatch between web-console (2.7.0) and cluster (2.7.5) is an issue?

Thanks

Kurt  



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message