[jira] [Created] (IGNITE-1531) Allow users to create and start Ignite configurations via OSGi Managed Service Factories

[JIRA]

Raúl Kripalani created IGNITE-1531:
--

 Summary: Allow users to create and start Ignite configurations via 
OSGi Managed Service Factories
 Key: IGNITE-1531
 URL: https://issues.apache.org/jira/browse/IGNITE-1531
 Project: Ignite
  Issue Type: Sub-task
  Components: general
Reporter: Raúl Kripalani
Assignee: Raúl Kripalani






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Updating docs

[Konstantin Boudnik]

On Tue, Sep 22, 2015 at 05:11AM, Dmitriy Setrakyan wrote:
> Cos,
> 
> You should have permissions to add documentation. Perhaps we can add
> multiple tabs for maven examples here:
> https://apacheignite.readme.io/docs/maven-setup

Yup, that was my thinking as well. We'll try to finish it once am done with my
presentation for the conference next week. Thanks for the permissions!

Cos

> On Tue, Sep 22, 2015 at 12:11 AM, Konstantin Boudnik  wrote:
> 
> > Good point, I will. I was referring to the examples of how to pull the
> > depedencies in. Currently, there's only Maven, so I thought Grape would be
> > beneficial.
> >
> > Cos
> >
> > On Mon, Sep 21, 2015 at 11:58PM, Dmitriy Setrakyan wrote:
> > > Cos,
> > >
> > > If you are adding examples, perhaps you should add them to code, no? We
> > > have examples module in Ignite.
> > >
> > > We don't have examples section in documentation.
> > >
> > > D.
> > >
> > > On Mon, Sep 21, 2015 at 11:24 PM, Konstantin Boudnik 
> > wrote:
> > >
> > > > Guys,
> > > >
> > > > what's the current way of updating documentation? I want to add some
> > > > examples
> > > > for programming around Ignite with Groovy and Grapes. I have suggested
> > an
> > > > edit
> > > > in the past, but looks like it never got applied, so I'd rather do it
> > > > myself
> > > > now ;)
> > > >
> > > > Appreciate the pointer to the procedure. Thanks!
> > > >   Cos
> > > >
> > > >
> >

Re: After setting streamer and ignite,getting NULL

[chandresh pancholi]

Not yet.
Still doing brainstorming why StormStreamer object is getting NULLL
in-spite setting up ignite and streamer instances.

On Tue, Sep 22, 2015 at 7:22 PM, Vishal Garg  wrote:

> Did you figure it out? Something related to your storm integration?
> Vishal
>
> Sent from my iPhone
>
> > On Sep 22, 2015, at 4:50 AM, chandresh pancholi <
> chandreshpancholi...@gmail.com> wrote:
> >
> > Problem here is with Storm. Its making streamer object null once it goes
> > into submit topology.
> >
> > On Mon, Sep 21, 2015 at 7:13 PM, Lalit Kumar Jha 
> > wrote:
> >
> >> Hi Chandresh,
> >>
> >> See test suite class here, its based on annotations
> >>
> >>
> https://github.com/sylentprayer/ignite/blob/ignite-530/modules/twitter/src/test/java/org/apache/ignite/stream/twitter/IgniteTwitterStreamerTestSuite.java
> >>
> >> No code required in class body.
> >>
> >> On Mon, Sep 21, 2015 at 6:24 PM, chandresh pancholi <
> >> chandreshpancholi...@gmail.com> wrote:
> >>
> >>> Hi Gian/Vishal/Lalit,
> >>>
> >>> You guys have worked on Streamer integration with Ignite. I am working
> on
> >>> Storm-ignite integration.
> >>>
> >>> I am setting up setStreamer() and setIgnite() in Test class and sending
> >>> this object to setBolt() method.
> >>>
> >>> When i try to read via gettreamer() and getIgnite() i am getting NULL.
> I
> >> am
> >>> trying to find out why is it happening but No Luck.
> >>>
> >>> If any one of you find some time and look into the code and help me to
> >>> resolve this. It would be great.
> >>>
> >>> Git : https://github.com/chandresh-pancholi/ignite
> >>> Module : storm
> >>>
> >>> --
> >>> Chandresh Pancholi
> >>> Senior Software Engineer
> >>> Flipkart.com
> >>> Email-id:chandresh.panch...@flipkart.com
> >>> Contact:08951803660
> >
> >
> >
> > --
> > Chandresh Pancholi
> > Senior Software Engineer
> > Flipkart.com
> > Email-id:chandresh.panch...@flipkart.com
> > Contact:08951803660
>



-- 
Chandresh Pancholi
Senior Software Engineer
Flipkart.com
Email-id:chandresh.panch...@flipkart.com
Contact:08951803660

[jira] [Created] (IGNITE-1532) IgniteCache.put() should load value from store if interceptor is used and CacheConfiguration.isLoadPreviousValue() == true

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-1532:
---

 Summary: IgniteCache.put() should load value from store if 
interceptor is used and CacheConfiguration.isLoadPreviousValue() == true
 Key: IGNITE-1532
 URL: https://issues.apache.org/jira/browse/IGNITE-1532
 Project: Ignite
  Issue Type: Bug
Reporter: Valentin Kulichenko
Priority: Critical
 Fix For: ignite-1.5






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Pull Request Merge Process

[Lalit Kumar Jha]

I submitted pull request for IGNITE-530 (Twitter streamer).

What is the proceess for reviewing and merging?

Re: Updating docs

[Konstantin Boudnik]

Good point, I will. I was referring to the examples of how to pull the
depedencies in. Currently, there's only Maven, so I thought Grape would be
beneficial.

Cos

On Mon, Sep 21, 2015 at 11:58PM, Dmitriy Setrakyan wrote:
> Cos,
> 
> If you are adding examples, perhaps you should add them to code, no? We
> have examples module in Ignite.
> 
> We don't have examples section in documentation.
> 
> D.
> 
> On Mon, Sep 21, 2015 at 11:24 PM, Konstantin Boudnik  wrote:
> 
> > Guys,
> >
> > what's the current way of updating documentation? I want to add some
> > examples
> > for programming around Ignite with Groovy and Grapes. I have suggested an
> > edit
> > in the past, but looks like it never got applied, so I'd rather do it
> > myself
> > now ;)
> >
> > Appreciate the pointer to the procedure. Thanks!
> >   Cos
> >
> >

[GitHub] ignite pull request: IGNITE-1522 - Made cache entry listener confi...

[vkulichenko]

Github user vkulichenko closed the pull request at:

https://github.com/apache/ignite/pull/103


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-1530) Support Zero Deployment with Ignite OSGi server mode

[JIRA]

Raúl Kripalani created IGNITE-1530:
--

 Summary: Support Zero Deployment with Ignite OSGi server mode
 Key: IGNITE-1530
 URL: https://issues.apache.org/jira/browse/IGNITE-1530
 Project: Ignite
  Issue Type: Sub-task
  Components: general
Reporter: Raúl Kripalani
Assignee: Raúl Kripalani






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [NOTICE] TeamCity is down

[Konstantin Boudnik]

Something like this could be arranged with INFRA
https://issues.apache.org/jira/browse/INFRA-10092
so there's an official CNAME for the CI server.

Cos

On Tue, Sep 22, 2015 at 11:31AM, Raul Kripalani wrote:
> Hey guys,
> 
> (Continuing "Maybe review my first commits" thread here).
> 
> I updated the Wiki in several places to point to .153:
> 
> - Frontpage
> - Git process
> - How to Contribute
> 
> Are there any plans to create a hostname for TeamCity? Else we can create a
> page at http://ignite.apache.org/teamcity that redirects to the right place.
> 
> Thanks,
> 
> *Raúl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
> 
> On Tue, Sep 22, 2015 at 6:05 AM, Denis Magda  wrote:
> 
> > Hi Raul,
> >
> > That server got down almost a month ago.
> > There is a secondary one - http://204.14.53.153/
> >
> > Are we going to recover .152 server? If we don't then we have to update
> > our wiki and refer to .153.
> >
> > --
> > Denis
> >
> >
> > On 9/22/2015 12:25 AM, Raúl Kripalani wrote:
> >
> >> I'm trying to access TeamCity via the URL in the Wiki (
> >> http://204.14.53.152/)
> >> but it seems to be down...
> >>
> >> http://downforeveryoneorjustme.com/http://204.14.53.152/
> >>
> >> Could someone please check?
> >>
> >> Thanks,
> >> Raúl.
> >>
> >>
> >

Re: ignite 1.4 status

[Yakov Zhdanov]

Alex, I spent some time debugging this today.

I noticed that we do not verify that topology version of the custom message
is identical to current ring version. After I added this condition test
started passing. However, it hangs from time to time since custom message
gets discarded before it gets processed (the new condition works here)
which means that topology version has somehow been changed, but custom
message has not been processed yet by that time.

My changes are in ignite-1171-debug. Can you please take a further look?

--Yakov

2015-09-22 5:50 GMT+03:00 Alexey Goncharuk :

> Folks,
>
> I was debugging issues with discovery today, my findings are below:
>
>- Issue with assertion "topology version has not been updated" was
>caused by sending discard message for custom messages. Now since we
>re-arrange custom messages, discardId gets repositioned and messages
> that
>should have been discarded were not discarded.
>- Fixed the issue above by introducing separate pending queue for custom
>messages which gets discarded independently from other discovery
> messages.
>- Did not get to the bottom of "joining nodes" assertion. From the debug
>I see that coordinator always fires custom messages at the right moment,
>when joiningNodes is empty, however despite the fixed (above) issue with
>custom messages discard, custom processed custom messages get re-sent
> which
>leads to this assertion
>
> I committed my pending debug code to ignite-1171-debug branch, if any of
> you guys is up to debugging this issue while I'm asleep - great, if not -
> I'll continue digging into it tomorrow.
>
> 2015-09-21 10:55 GMT-07:00 Yakov Zhdanov :
>
> > Igniters,
> >
> > We are not ready to release today.
> >
> > Alexey Goncharuk is still working on ignite-1171. Alex please provide
> > updates by the end of the day.
> >
> > https://issues.apache.org/jira/browse/IGNITE-1516 - performance offheap
> > query benchmark is not fully recovered. Semyon will be fixing it. Sergi,
> > can you please assist?
> >
> > https://issues.apache.org/jira/browse/IGNITE-973 - Semyon has fixed race
> > in
> > cache logic, but issue is still reproducible due to possible issues in
> > indexing logic. Sergi, this is on you. Can you please take a look?
> >
> > --Yakov
> >
>

[jira] [Created] (IGNITE-1529) Support server mode with Ignite OSGi without Zero Deployment

[JIRA]

Raúl Kripalani created IGNITE-1529:
--

 Summary: Support server mode with Ignite OSGi without Zero 
Deployment
 Key: IGNITE-1529
 URL: https://issues.apache.org/jira/browse/IGNITE-1529
 Project: Ignite
  Issue Type: Sub-task
  Components: general
Reporter: Raúl Kripalani
Assignee: Raúl Kripalani






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Azul Zing

[Dmitriy Setrakyan]

On Tue, Sep 22, 2015 at 10:45 AM, Andrey Kornev 
wrote:

> Hello,
>
> Since it looks like there is an effort underway to certify Ignite on
> different JVMs, I'm wondering if Azul Zing could also be considered as a
> potential candidate?
>

Andrey, I don't see why not. Can you please file a ticket?


>
> Regards
> Andrey
>

Re: Azul Zing

[Konstantin Boudnik]

I have heard some conversations that most of their sales are coming from the
commercial support of OpenJDK. What I am saying that if the support effort of
Azul is huge, may be there's no point of doing this... ;)?

Cos

On Tue, Sep 22, 2015 at 11:47AM, Dmitriy Setrakyan wrote:
> On Tue, Sep 22, 2015 at 10:45 AM, Andrey Kornev 
> wrote:
> 
> > Hello,
> >
> > Since it looks like there is an effort underway to certify Ignite on
> > different JVMs, I'm wondering if Azul Zing could also be considered as a
> > potential candidate?
> >
> 
> Andrey, I don't see why not. Can you please file a ticket?
> 
> 
> >
> > Regards
> > Andrey
> >

[jira] [Created] (IGNITE-1528) Support client mode with Ignite OSGi

[JIRA]

Raúl Kripalani created IGNITE-1528:
--

 Summary: Support client mode with Ignite OSGi
 Key: IGNITE-1528
 URL: https://issues.apache.org/jira/browse/IGNITE-1528
 Project: Ignite
  Issue Type: Sub-task
  Components: general
Reporter: Raúl Kripalani
Assignee: Raúl Kripalani






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

RE: Azul Zing

[Andrey Kornev]

According to my sources ;) they are quite popular in the finance.

I'll create a ticket anyway and let the community decide. :)

Andrey

> Date: Tue, 22 Sep 2015 10:09:48 -0700
> From: c...@apache.org
> To: dev@ignite.apache.org
> Subject: Re: Azul Zing
> 
> I have heard some conversations that most of their sales are coming from the
> commercial support of OpenJDK. What I am saying that if the support effort of
> Azul is huge, may be there's no point of doing this... ;)?
> 
> Cos
> 
> On Tue, Sep 22, 2015 at 11:47AM, Dmitriy Setrakyan wrote:
> > On Tue, Sep 22, 2015 at 10:45 AM, Andrey Kornev 
> > wrote:
> > 
> > > Hello,
> > >
> > > Since it looks like there is an effort underway to certify Ignite on
> > > different JVMs, I'm wondering if Azul Zing could also be considered as a
> > > potential candidate?
> > >
> > 
> > Andrey, I don't see why not. Can you please file a ticket?
> > 
> > 
> > >
> > > Regards
> > > Andrey
> > >
  

Re: Azul Zing

[Konstantin Boudnik]

On Tue, Sep 22, 2015 at 03:36PM, Andrey Kornev wrote:
> According to my sources ;) they are quite popular in the finance.

Fair enough. Not trying to discourage the contribution: rather exploring it ;)

Thanks

> I'll create a ticket anyway and let the community decide. :)
> 
> Andrey
> 
> > Date: Tue, 22 Sep 2015 10:09:48 -0700
> > From: c...@apache.org
> > To: dev@ignite.apache.org
> > Subject: Re: Azul Zing
> > 
> > I have heard some conversations that most of their sales are coming from the
> > commercial support of OpenJDK. What I am saying that if the support effort 
> > of
> > Azul is huge, may be there's no point of doing this... ;)?
> > 
> > Cos
> > 
> > On Tue, Sep 22, 2015 at 11:47AM, Dmitriy Setrakyan wrote:
> > > On Tue, Sep 22, 2015 at 10:45 AM, Andrey Kornev 
> > > wrote:
> > > 
> > > > Hello,
> > > >
> > > > Since it looks like there is an effort underway to certify Ignite on
> > > > different JVMs, I'm wondering if Azul Zing could also be considered as a
> > > > potential candidate?
> > > >
> > > 
> > > Andrey, I don't see why not. Can you please file a ticket?
> > > 
> > > 
> > > >
> > > > Regards
> > > > Andrey
> > > >
> 

Re: After setting streamer and ignite,getting NULL

[Vishal Garg]

Did you figure it out? Something related to your storm integration?
Vishal

Sent from my iPhone

> On Sep 22, 2015, at 4:50 AM, chandresh pancholi 
>  wrote:
> 
> Problem here is with Storm. Its making streamer object null once it goes
> into submit topology.
> 
> On Mon, Sep 21, 2015 at 7:13 PM, Lalit Kumar Jha 
> wrote:
> 
>> Hi Chandresh,
>> 
>> See test suite class here, its based on annotations
>> 
>> https://github.com/sylentprayer/ignite/blob/ignite-530/modules/twitter/src/test/java/org/apache/ignite/stream/twitter/IgniteTwitterStreamerTestSuite.java
>> 
>> No code required in class body.
>> 
>> On Mon, Sep 21, 2015 at 6:24 PM, chandresh pancholi <
>> chandreshpancholi...@gmail.com> wrote:
>> 
>>> Hi Gian/Vishal/Lalit,
>>> 
>>> You guys have worked on Streamer integration with Ignite. I am working on
>>> Storm-ignite integration.
>>> 
>>> I am setting up setStreamer() and setIgnite() in Test class and sending
>>> this object to setBolt() method.
>>> 
>>> When i try to read via gettreamer() and getIgnite() i am getting NULL. I
>> am
>>> trying to find out why is it happening but No Luck.
>>> 
>>> If any one of you find some time and look into the code and help me to
>>> resolve this. It would be great.
>>> 
>>> Git : https://github.com/chandresh-pancholi/ignite
>>> Module : storm
>>> 
>>> --
>>> Chandresh Pancholi
>>> Senior Software Engineer
>>> Flipkart.com
>>> Email-id:chandresh.panch...@flipkart.com
>>> Contact:08951803660
> 
> 
> 
> -- 
> Chandresh Pancholi
> Senior Software Engineer
> Flipkart.com
> Email-id:chandresh.panch...@flipkart.com
> Contact:08951803660

Re: Client node throws exception when server node killed

[Artem Shutak]

Filed an issue: https://issues.apache.org/jira/browse/IGNITE-1524. Attached
logs.

Let me know if I can help.

-- Artem --

On Tue, Sep 22, 2015 at 10:23 AM, Semyon Boikov 
wrote:

> Artem,
>
> This looks like a bug, client should not disconnect from cluster if there
> are alive server nodes, I'll try to reproduce this error.
>
> On Mon, Sep 21, 2015 at 8:31 PM, Artem Shutak 
> wrote:
>
> > Igniters,
> >
> > In process of working on [1] I've found that Ignite client node throws
> > CacheException which caused by IgniteClientDisconnectedException (stack
> > trace below) sometimes when I kill one server node at cluster.
> >
> > It looks like not expected behavior for me. Is it know issue?
> >
> > My configuration:
> > - 3 server nodes
> > - 2 client nodes
> > - discovery configuration:
> > 
> >  > class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
> > 
> >  >
> >
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
> > 
> > 
> > 127.0.0.1:47500
> > 127.0.0.1:47501
> > 127.0.0.1:47502
> > 
> > 
> > 
> > 
> > 
> > 
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-1397
> >
> > -- Artem --
> >
> > javax.cache.CacheException: class
> > org.apache.ignite.IgniteClientDisconnectedException: Operation has been
> > cancelled (client node disconnected).
> > at
> >
> >
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1621)
> > at
> >
> >
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1749)
> > at
> >
> >
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:815)
> > at
> >
> >
> org.apache.ignite.yardstick.cache.failover.IgniteAtomicRetriesFailoverBenchmark.test(IgniteAtomicRetriesFailoverBenchmark.java:39)
> > at
> >
> org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:165)
> > at java.lang.Thread.run(Thread.java:745)
> > Caused by: class org.apache.ignite.IgniteClientDisconnectedException:
> > Operation has been cancelled (client node disconnected).
> > at
> >
> org.apache.ignite.internal.util.IgniteUtils$14.apply(IgniteUtils.java:801)
> > at
> >
> org.apache.ignite.internal.util.IgniteUtils$14.apply(IgniteUtils.java:799)
> > ... 6 more
> > Caused by: class
> > org.apache.ignite.internal.IgniteClientDisconnectedCheckedException:
> > Operation has been cancelled (client node disconnected).
> > at
> >
> >
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager.disconnectedError(GridCacheMvccManager.java:360)
> > at
> >
> >
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager.onDisconnected(GridCacheMvccManager.java:334)
> > at
> >
> >
> org.apache.ignite.internal.processors.cache.GridCacheSharedContext.onDisconnected(GridCacheSharedContext.java:141)
> > at
> >
> >
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onDisconnected(GridCacheProcessor.java:997)
> > at
> >
> >
> org.apache.ignite.internal.IgniteKernal.onDisconnected(IgniteKernal.java:2983)
> > at
> >
> >
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$5.onDiscovery(GridDiscoveryManager.java:592)
> > at
> >
> >
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2024)
> > at
> >
> >
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2005)
> > at
> >
> >
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1422)
> > at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> >
>

[jira] [Created] (IGNITE-1524) Client node throws exception when server node killed

[Artem Shutak (JIRA)]

Artem Shutak created IGNITE-1524:


 Summary: Client node throws exception when server node killed
 Key: IGNITE-1524
 URL: https://issues.apache.org/jira/browse/IGNITE-1524
 Project: Ignite
  Issue Type: Bug
Reporter: Semen Boikov
 Fix For: ignite-1.4


In process of working on IGNITE-1397 I've found that Ignite client node throws 
CacheException which caused by IgniteClientDisconnectedException (stack trace 
below) sometimes when I kill one server node at cluster.

My configuration:
- 3 server nodes
- 2 client nodes
- discovery configuration:






127.0.0.1:47500
127.0.0.1:47501
127.0.0.1:47502







Test description:
- client nodes make random atomic ops to cluster (pts, gets, invoke, remove)
- the first client node has a thread which kill with -9 and start one server 
one by one. Kills every 60 seconds and run after 10 seconds.

Client node fails not always. 

{noformat}
javax.cache.CacheException: class 
org.apache.ignite.IgniteClientDisconnectedException: Operation has been 
cancelled (client node disconnected).
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1621)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1749)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:815)
at 
org.apache.ignite.yardstick.cache.failover.IgniteAtomicRetriesFailoverBenchmark.test(IgniteAtomicRetriesFailoverBenchmark.java:39)
at 
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:165)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteClientDisconnectedException: Operation 
has been cancelled (client node disconnected).
at 
org.apache.ignite.internal.util.IgniteUtils$14.apply(IgniteUtils.java:801)
at 
org.apache.ignite.internal.util.IgniteUtils$14.apply(IgniteUtils.java:799)
... 6 more
Caused by: class 
org.apache.ignite.internal.IgniteClientDisconnectedCheckedException: Operation 
has been cancelled (client node disconnected).
at 
org.apache.ignite.internal.processors.cache.GridCacheMvccManager.disconnectedError(GridCacheMvccManager.java:360)
at 
org.apache.ignite.internal.processors.cache.GridCacheMvccManager.onDisconnected(GridCacheMvccManager.java:334)
at 
org.apache.ignite.internal.processors.cache.GridCacheSharedContext.onDisconnected(GridCacheSharedContext.java:141)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onDisconnected(GridCacheProcessor.java:997)
at 
org.apache.ignite.internal.IgniteKernal.onDisconnected(IgniteKernal.java:2983)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$5.onDiscovery(GridDiscoveryManager.java:592)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2024)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2005)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1422)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: After setting streamer and ignite,getting NULL

[chandresh pancholi]

Problem here is with Storm. Its making streamer object null once it goes
into submit topology.

On Mon, Sep 21, 2015 at 7:13 PM, Lalit Kumar Jha 
wrote:

> Hi Chandresh,
>
> See test suite class here, its based on annotations
>
> https://github.com/sylentprayer/ignite/blob/ignite-530/modules/twitter/src/test/java/org/apache/ignite/stream/twitter/IgniteTwitterStreamerTestSuite.java
>
> No code required in class body.
>
> On Mon, Sep 21, 2015 at 6:24 PM, chandresh pancholi <
> chandreshpancholi...@gmail.com> wrote:
>
> > Hi Gian/Vishal/Lalit,
> >
> > You guys have worked on Streamer integration with Ignite. I am working on
> > Storm-ignite integration.
> >
> > I am setting up setStreamer() and setIgnite() in Test class and sending
> > this object to setBolt() method.
> >
> > When i try to read via gettreamer() and getIgnite() i am getting NULL. I
> am
> > trying to find out why is it happening but No Luck.
> >
> > If any one of you find some time and look into the code and help me to
> > resolve this. It would be great.
> >
> > Git : https://github.com/chandresh-pancholi/ignite
> > Module : storm
> >
> > --
> > Chandresh Pancholi
> > Senior Software Engineer
> > Flipkart.com
> > Email-id:chandresh.panch...@flipkart.com
> > Contact:08951803660
> >
>



-- 
Chandresh Pancholi
Senior Software Engineer
Flipkart.com
Email-id:chandresh.panch...@flipkart.com
Contact:08951803660

Re: Updating docs

[Dmitriy Setrakyan]

Cos,

You should have permissions to add documentation. Perhaps we can add
multiple tabs for maven examples here:
https://apacheignite.readme.io/docs/maven-setup

D.

On Tue, Sep 22, 2015 at 12:11 AM, Konstantin Boudnik  wrote:

> Good point, I will. I was referring to the examples of how to pull the
> depedencies in. Currently, there's only Maven, so I thought Grape would be
> beneficial.
>
> Cos
>
> On Mon, Sep 21, 2015 at 11:58PM, Dmitriy Setrakyan wrote:
> > Cos,
> >
> > If you are adding examples, perhaps you should add them to code, no? We
> > have examples module in Ignite.
> >
> > We don't have examples section in documentation.
> >
> > D.
> >
> > On Mon, Sep 21, 2015 at 11:24 PM, Konstantin Boudnik 
> wrote:
> >
> > > Guys,
> > >
> > > what's the current way of updating documentation? I want to add some
> > > examples
> > > for programming around Ignite with Groovy and Grapes. I have suggested
> an
> > > edit
> > > in the past, but looks like it never got applied, so I'd rather do it
> > > myself
> > > now ;)
> > >
> > > Appreciate the pointer to the procedure. Thanks!
> > >   Cos
> > >
> > >
>

[jira] [Created] (IGNITE-1526) IBM JDK is not fully supported by the platfrom

[Denis Magda (JIRA)]

Denis Magda created IGNITE-1526:
---

 Summary: IBM JDK is not fully supported by the platfrom
 Key: IGNITE-1526
 URL: https://issues.apache.org/jira/browse/IGNITE-1526
 Project: Ignite
  Issue Type: Bug
Reporter: Denis Magda
Assignee: Denis Magda
Priority: Blocker
 Fix For: ignite-1.5


There are several issue related to IBM JDK.

1) It's not possible to compile the platform using IBM JDK ver 1.7;

2) Besides of the fact that two IBM nodes can connect to each other some 
functionality still doesn't work. As an example 
{{CacheClientPortablePutGetExample}} fails with the following stack trace

{noformat}
[14:38:56,930][ERROR][grid-nio-worker-0-#26%null%][TcpCommunicationSpi] Caught 
unhandled exception in NIO worker thread (restart the node).
class org.apache.ignite.IgniteException: Invalid field type: 0
at 
org.gridgain.grid.internal.communication.PortableDirectMessageReader.readRemovedField(PortableDirectMessageReader.java:670)
at 
org.gridgain.grid.internal.communication.PortableDirectMessageReader.readFieldHeader(PortableDirectMessageReader.java:520)
at 
org.gridgain.grid.internal.communication.PortableDirectMessageReader.readMessage(PortableDirectMessageReader.java:339)
at 
org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:248)
at 
org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:76)
at 
org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:103)
at 
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
at 
org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:122)
at 
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
at 
org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:2078)
at 
org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:172)
at 
org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:858)
at 
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeys(GridNioServer.java:1397)
at 
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1339)
at 
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1223)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
at java.lang.Thread.run(Thread.java:801)
{noformat}

3) Oracle JVM based server node fails to connect to IBM server node producing 
the stack trace below. Tested with JDK and Portable marshallers.

{noformat}
[13:47:33,935][SEVERE][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Failed to
unmarshal discovery data for component: 0
class org.apache.ignite.IgniteCheckedException: Failed to deserialize object wit
h given class loader: sun.misc.Launcher$AppClassLoader@56092666
at org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshalle
r.java:105)
at org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMar
shaller.java:68)
at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDis
coverySpi.java:1697)
at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.proc
essNodeAddedMessage(ServerImpl.java:3258)
at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.proc
essMessage(ServerImpl.java:1993)
at org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.b
ody(ServerImpl.java:5206)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
Caused by: java.io.InvalidClassException: org.apache.ignite.internal.util.lang.G
ridFunc$38; local class incompatible: stream classdesc serialVersionUID = -55433
49853748590486, local class serialVersionUID = -5664060422647374863
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:617)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:162
2)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1
771)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at org.apache.ignite.internal.processors.continuous.GridContinuousProces
sor$DiscoveryDataItem.readExternal(GridContinuousProcessor.java:1455)
at 

Azul Zing

[Andrey Kornev]

Hello,

Since it looks like there is an effort underway to certify Ignite on different 
JVMs, I'm wondering if Azul Zing could also be considered as a potential 
candidate?

Regards
Andrey
  

Supporting non Oracle JVMs

[Denis Magda]

Igniters,

During this month we found out that Ignite doesn't work well with non 
Oracle JVMs and big-endian architecture.


In general there three related issues:
- [1] issues on IBM JDK: https://issues.apache.org/jira/browse/IGNITE-1526
- [2] issue on HP JDK: https://issues.apache.org/jira/browse/IGNITE-1493
- [3] issue on big-endian architecture as I suppose: 
https://issues.apache.org/jira/browse/IGNITE-1497


Number [1] is a good point to start. So I'm taking this issue.

If you have any thoughts, suggestions please leave them in [1].

From my side I'll definitely share and discuss complex places, that 
need to be modified, with the community.


--
Denis