ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Kuznetsov <akuznet...@apache.org>
Subject Re: Trouble using latest Ignite Web Console (2.1)
Date Thu, 03 Aug 2017 18:19:13 GMT
Muthu,

Thanks for stack trace! I will try tomorrow.
Could you also say what DB you are using (name+version)? and JDBC driver
(name + version).
I will try to reproduce.

As a workaround, could you try the same (import model from DB) on
console.gridgain.com?

On Fri, Aug 4, 2017 at 1:02 AM, Muthu <muthu.kumaran.l@gmail.com> wrote:

> Hi Andrey,
>
> The latest version worked for the connection. However when i try to import
> domain models from my database it fails past the schema selection
> page..once i select my database and hit next it doesn't show my two tables
> that i have in that. Also when i select all (instead of my specific schema)
> & hit next it doesn't proceed at all & shows an error message
> "java.sql.SQLException: Failed to collect metadata". Any clue?
>
> I also see this exception in the logs,
>
> [2017-08-03 11:00:11,291][ERROR][pool-6-thread-1][DatabaseListener]
> Failed to collect metadata
> java.lang.ClassCastException: java.util.ArrayList cannot be cast to
> java.lang.String
> at org.apache.ignite.console.agent.db.dialect.JdbcMetadataDialect.tables(
> JdbcMetadataDialect.java:128)
> at org.apache.ignite.console.agent.db.DbMetadataReader.
> metadata(DbMetadataReader.java:95)
> at org.apache.ignite.console.agent.handlers.DatabaseListener.metadata(
> DatabaseListener.java:280)
> at org.apache.ignite.console.agent.handlers.DatabaseListener$2.execute(
> DatabaseListener.java:122)
> at org.apache.ignite.console.agent.handlers.AbstractListener$1.run(
> AbstractListener.java:67)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:473)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
>
>
> Regards,
> Muthu
>
> -- The real danger with modern technology isn't that machines will begin
> to think like people, but that people will begin to think like machines.
> -- Faith is to believe what you do not see; the reward of this faith is to
> see what you believe.
>
> On Wed, Aug 2, 2017 at 10:50 PM, Muthu <muthu.kumaran.l@gmail.com> wrote:
>
>> Thanks Andrey...I did use the latest..also i validated the token without
>> which the agent doesn't even connect (btw i couldn't initially get the
>> web-agent version downloaded from console.gridgain to connect to web
>> console...it failed complaining version mismatch...then i took the version
>> from inside the web console image & then got it to connect properly).
>>
>> I see the new image has been pushed a couple hours back..will retry with
>> that & let you know.
>>
>> Regards,
>> Muthu
>>
>> -- The real danger with modern technology isn't that machines will begin
>> to think like people, but that people will begin to think like machines.
>> -- Faith is to believe what you do not see; the reward of this faith is
>> to see what you believe.
>>
>> On Wed, Aug 2, 2017 at 8:54 PM, Andrey Novikov <anovikov@apache.org>
>> wrote:
>>
>>> Hi Muthu,
>>>
>>> Do you use following image (in console execute following command:
>>> "docker images")?
>>> REPOSITORY                                        TAG
>>> IMAGE ID
>>> apacheignite/web-console-standalone   latest              ae3d24152e68
>>>
>>> Also, please validate token in agent configuration should be the same as
>>> on profile page.
>>>
>>> On 2017-08-03 09:47, Muthu <muthu.kumaran.l@gmail.com> wrote:
>>> > Hi Folks,
>>> >
>>> > First a big thanks for making the latest version of web console
>>> available
>>> > on docker hub (https://hub.docker.com/r/apac
>>> heignite/web-console-standalone/).
>>> > As i understand this has fixes for some issues i encountered with
>>> ignite
>>> > 2.0 version
>>> >
>>> > I tried it but unfortunately it looks like this latest version has
>>> trouble
>>> > connecting to ignite grid. Even though i have ignite & web-agent
>>> running on
>>> > the same Linux host as the container (with all properly connected as
>>> seen
>>> > from the logs) web console is unable to connect to it.
>>> >
>>> > As a result i am also unable to use it to connect to my db for
>>> model/cache
>>> > artifact generation, etc.
>>> >
>>> > Has any one else tried using it?
>>> >
>>> > Regards,
>>> > Muthu
>>> >
>>> > -- The real danger with modern technology isn't that machines will
>>> begin to
>>> > think like people, but that people will begin to think like machines.
>>> > -- Faith is to believe what you do not see; the reward of this faith
>>> is to
>>> > see what you believe.
>>> >
>>>
>>
>>
>


-- 
Alexey Kuznetsov

Mime
View raw message