Re: web-console not displaying the latest version of ignite

Hi, Looks like you are deployed old image of apacheignite/web-console-frontend. What version did you see in web-console footer? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Web Console on Kubernetes Cluster

Hi, You may run agent on server node pods. Also you need pass user's security tokens: https://apacheignite-tools.readme.io/docs/getting-started#section-configuration -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Web Agent 2.1.3 giving message "You are using an older version of the agent."

Hello Kenan Dalley, Compatibility between different versions of web-agent is not supported. Please download web-agent that is available to download in an your run docker image. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Trouble using latest Ignite Web Console (2.1)

Hi Muthu, Do you use following image (in console execute following command: "docker images")? REPOSITORYTAGIMAGE ID apacheignite/web-console-standalone latest ae3d24152e68 Also, please validate token in agent

Re: Ignite web console not running in browser

You need use web server for deliver web pages and proxying requests to backend service. Added documentation for Apache HTTP Server: https://apacheignite-tools.readme.io/docs/build-and-deploy#section-run-ignite-web-console-in-production-mode -- View this message in context:

Re: Ignite web console not running in browser

Hi, In Ignite 1.9, Ignite 2.0 developer web server bind only on localhost interface. This was fixed in master where developer web server bind for all interfaces. As temporary workaround you can try to replace localhost with your ip in

Re: WebConsole 1.9.0 not working

Hi, Please check is babel-preset-angular module installed: npm install --save- dev babel-preset-angular And enabled the preset in .babelrc: { "presets": ["angular"], "plugins": [[ "transform-builtin-extend", { "globals": ["Error", "Array"], "approximate": true } ]] }

Re: using ignite web console

Hi, Note your are trying to use development mode in production! To bind development web server to all interfaces on your linux machine you need fix following file: modules/web-console/frontend/gulpfile.babel.js/webpack/environments/development.js like this

Re: OOME on 2-node cluster with visor running repeatedly, Ignite 1.9

"nc - Total number of nodes in the grid" count server + client nodes. I can't find metrics for server nodes. I tried to check the heap dump in "mat" and found a large size of TcpCommunicationSpi#recoveryDescs. Does anyone have an idea why this happened? -- View this message in context:

Re: OOME on 2-node cluster with visor running repeatedly, Ignite 1.9

Hi tysli2016, You can run connected to cluster visorcmd in background and register an alert. When this alert is triggered, it may call custom user script. More info can be found here: https://apacheignite-tools.readme.io/docs/alerts-configuration -- View this message in context:

Re: Web Console not working!!

Hi, Pranav Web Console was just updated to new version. Please try again, you will need to reload Web Agent. If you will not be able to connect please send Web agent logs -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Web-Console-not-working-tp11359p11389.html

Re: insert/update/delete issue in Version 1.8

Denis, Ticket https://issues.apache.org/jira/browse/IGNITE-4622 was fixed in master branch. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/insert-update-delete-issue-in-Version-1-8-tp10244p10280.html Sent from the Apache Ignite Users mailing list archive at

Re: Automatic Persistence - POJOs and XMLs for couchbase

Hi, Abhishek Jain. I successfully connect to couchbase using Simba couchbase JDBC driver. For do this you need: * create folder for driver jars in $IGNITE_HOME/libs (for example: couchbase-driver) * copy all jars from Driver folder in Simba_Couchbase_JDBC.zip * copy

Re: Web Console on Local Machine not working

Your need download fronted dependencies using jspm. This step with number 5 was missed in DEVNOTES.txt = How to deploy locally: ... 4. Run "npm install" in terminal for download *backend* dependencies. *5. Run "jspm install" in terminal for download frontend dependencies.*

Re: Web Console on Local Machine not working

As I understand web console 1.6 has bug with upgrade JSZip from v2 to v3. In 1.7 this bug was fixed. You may try to change version of JSZip in package.json or switch to 1.7 -- View this message in context:

Re: SQL Query on REST APIs

Hi Francesco, Francesco wrote > But let me notice you that the example in your link > (https://apacheignite.readme.io/docs/rest-api#sql-query-execute) is wrong, > in fact it uses 'pzs' instead of 'pageSize'. This is what has confused me. Sorry for the late reply. Thank you for your note, I've

Re: Jetty configuration for adding new Handler

Hi Saurabh, I've investigated ignite-rest-http module and found that handler from configuration will be overrided by default handler (org/apache/ignite/internal/processors/rest/protocols/http/jetty/GridJettyRestProtocol.java:332) I've created issue for fix this problem