Re: Apache Ignite: Failed to unmarshal discovery data

[Evgenii Zhuravlev]

Hi,

answered you here:
https://stackoverflow.com/questions/44155694/apache-ignite-failed-to-unmarshal-discovery-data/44238855#44238855

Evgenii

2017-05-25 11:24 GMT+03:00 brent :

> I'm trying to use the Ignite Jdbc connection; with my goal to be able to
> call
> the cache from any client over Jdbc.
>
> I've got a number of scenario's working; so have data loaded correctly; and
> can run sql queries 'directly' against the cache.
>
> When I try to call from a separate client with
>
> ```
> ResultSet rs = conn.createStatement().executeQuery("select * from
> my_table");
>
> ```
>
> I hit an error:
>
> ```
> class org.apache.ignite.IgniteCheckedException: Failed to find class with
> given class loader for unmarshalling (make sure same versions of all
> classes
> are available on all nodes or enable peer-class-loading)
> [clsLdr=URLClassLoader with NativeCopyLoader with RawResources(
>
> ```
>
> Is there a way to prevent the Ignite jdbc connection from trying to do any
> unmarshalling?
>
> I would like my client to be as agnostic as possible to the Ignite classes.
> For example; I would like to swap out calling mariaDb to Ignite - with as
> little code change as possible on the client side.
>
> If I'm thinking about things the wrong way; then answer along the lines of
> No, that will never work because ... are more than welcome too.
>
> I can get the client to work by adding the required classes to the class
> path. But I would like to avoid having todo that.
>
> Thanks Brent
>
>
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Apache-Ignite-Failed-to-unmarshal-
> discovery-data-tp13140.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Apache Ignite: Failed to unmarshal discovery data

[brent]

I'm trying to use the Ignite Jdbc connection; with my goal to be able to call
the cache from any client over Jdbc.

I've got a number of scenario's working; so have data loaded correctly; and
can run sql queries 'directly' against the cache.

When I try to call from a separate client with

```
ResultSet rs = conn.createStatement().executeQuery("select * from
my_table");

```

I hit an error:

```
class org.apache.ignite.IgniteCheckedException: Failed to find class with
given class loader for unmarshalling (make sure same versions of all classes
are available on all nodes or enable peer-class-loading)
[clsLdr=URLClassLoader with NativeCopyLoader with RawResources(

```

Is there a way to prevent the Ignite jdbc connection from trying to do any
unmarshalling?

I would like my client to be as agnostic as possible to the Ignite classes.
For example; I would like to swap out calling mariaDb to Ignite - with as
little code change as possible on the client side.

If I'm thinking about things the wrong way; then answer along the lines of
No, that will never work because ... are more than welcome too.

I can get the client to work by adding the required classes to the class
path. But I would like to avoid having todo that. 

Thanks Brent





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-Failed-to-unmarshal-discovery-data-tp13140.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.