[jira] [Created] (IGNITE-3307) IllegalMonitorStateException in IgniteLockExample

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-3307:


 Summary: IllegalMonitorStateException in IgniteLockExample
 Key: IGNITE-3307
 URL: https://issues.apache.org/jira/browse/IGNITE-3307
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.6
Reporter: Alexey Goncharuk


Attaching logs from TC



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

[jira] [Created] (IGNITE-3306) Extend IgniteCluster interface with the methods to send and receive custom discovery events

[Andrey Kornev (JIRA)]

Andrey Kornev created IGNITE-3306:
-

 Summary: Extend IgniteCluster interface with the methods to send 
and receive custom discovery events
 Key: IGNITE-3306
 URL: https://issues.apache.org/jira/browse/IGNITE-3306
 Project: Ignite
  Issue Type: Improvement
Reporter: Andrey Kornev


{{GridDiscoveryManager}} already provides the methods for sending/receiving 
custom discovery messages: {{GridDiscoveryManager.sendCustomEvent(...)}} and 
{{GridDiscoveryManager.setCustomEventListener(...)}} methods correspondingly. 
This API is very powerful as it provides reliable delivery guarantees that are 
totally ordered with respect to the rest of discovery events. It's essential 
for implementing so-called view-synchronous group communication primitives.

Unfortunately, {{GridDiscoveryManager}} is not part of the public API. 

This ticket proposes to extend {{IgniteCluster}} interface to expose those 
methods. {{DiscoveryCustomMessage}} class should also be moved out of the 
{{internal}} package to a public package.



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

[jira] [Created] (IGNITE-3305) Ignite does not wait for dynamically created caches in SYNC rebalance mode

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-3305:


 Summary: Ignite does not wait for dynamically created caches in 
SYNC rebalance mode
 Key: IGNITE-3305
 URL: https://issues.apache.org/jira/browse/IGNITE-3305
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.6
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
 Fix For: 1.7


See GridCacheProcessor#onKernalStart():
{code}
// Wait for caches in SYNC preload mode.
for (CacheConfiguration cfg : ctx.config().getCacheConfiguration()) {
{code}



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

IGNITE-3293 AWS bootstrap scripts patch for Ignite-Cassandra

[Igor Rudyak]

Could somebody please look at the pull request
https://github.com/apache/ignite/pull/794 related to
https://issues.apache.org/jira/browse/IGNITE-3293 ticket.

It's fixes rather important thing for AWS Ignite/Cassandra clusters
bootstrap scripts.

Thanks,
Igor Rudyak

Contribution merged: Mysql support broken in 1.6, externalize sql syntax to make it configurable

[Denis Magda]

Kristian,

Thanks a lot for finding time to improve Apache Ignite project. Your latest 
contribution [1] has been just merged.

Looking forward for more contributions from your side.

[1] https://github.com/apache/ignite/pull/790 


—
Denis

Contribution merged: Fix parameter error in class GridServiceProcessor

[Denis Magda]

Biao Ma,

Thanks for constant contribution into Apache Ignite project. I’ve reviewed and 
merged one more  issue that 
was fixed by you.

Keep improving Ignite the same way!

—
Denis

Re: Maven conflicts within ignite-core from duplicated classes

[Denis Magda]

Hi Pete,

CC-ing Ignite dev list to the thread as well.

Igniters, up to today is there any reason why we need to include sources of 
Nullable JetBrain’s annotation in Ignite sources?

As I see we can rather import that latest version from the maven repository
https://maven-repository.com/artifact/org.jetbrains/annotations/15.0 


Anton, please take a look at Pete issue and suggest a workaround and generic 
solution overall.

—
Denis

> On Jun 9, 2016, at 1:32 PM, Pete Campton  wrote:
> 
> Hello,
> 
> I've come across an issue where there are a couple of classes duplicated from 
> org.jetbrains.annotations within the ignite-core module which conflict with 
> other part of our code base.
> 
> As these files are duplicated rather than being referenced as a maven 
> dependency I am unable to exclude them or reference a specific version of the 
> org.jetbrains.annotations artifact.
> 
> Specifically, the included version cannot be used to annotate types
> ignite-core-1.6.0.jar:org.jetbrains.annotations.Nullable ...
> @Target({ElementType.METHOD, ElementType.FIELD, ElementType.PARAMETER, 
> ElementType.LOCAL_VARIABLE})
> annotations-15.0.jar:org.jetbrains.annotations.Nullable ...
> @Target({ElementType.METHOD, ElementType.FIELD, ElementType.PARAMETER, 
> ElementType.LOCAL_VARIABLE, ElementType.TYPE_USE})
> 
> As far as I know there isn't an easy way of excluding these files from within 
> the ignite-core module. Is there are reason why these "external" files have 
> been duplicated within the ignite code base rather than being referenced as a 
> maven dependency? Or alternatively, has anyone come across a way of avoiding 
> these conflicts?
> 
> Thanks
> Pete
>