[jira] [Comment Edited] (IGNITE-1146) Implement summary page with configuration downloads.

2015-09-30 Thread Pavel Konstantinov (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939376#comment-14939376
 ] 

Pavel Konstantinov edited comment on IGNITE-1146 at 10/1/15 6:33 AM:
-

1) I think we should rename generated java factory class 'ConfigurationFactory' 
to 'IgniteConfigurationFactory' because 'IgniteConfiguration' is returned.
2) currently we set gridName using incorrect syntax 'cfg.gridName("aaa");' 
should be 'cfg.setGridName("aaa");'


was (Author: pkonstantinov):
I think we should rename generated java factory class 'ConfigurationFactory' to 
'IgniteConfigurationFactory' because 'IgniteConfiguration' is returned.

> Implement summary page with configuration downloads.
> 
>
> Key: IGNITE-1146
> URL: https://issues.apache.org/jira/browse/IGNITE-1146
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>Assignee: Pavel Konstantinov
> Fix For: ignite-1.5
>
> Attachments: summary - client.png, summary - server.png, 
> test-cluster-2.xml
>
>
> Generate:
> * sprint xml configuration;
> * Java class with configuration;
> * Java snippet with configuration;
> * docker file for run with this configuration.
> Download all generated files as zip archive, generate client configuration.



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


[jira] [Commented] (IGNITE-1146) Implement summary page with configuration downloads.

2015-09-30 Thread Pavel Konstantinov (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939376#comment-14939376
 ] 

Pavel Konstantinov commented on IGNITE-1146:


I think we should rename generated java factory class 'ConfigurationFactory' to 
'IgniteConfigurationFactory' because 'IgniteConfiguration' is returned.

> Implement summary page with configuration downloads.
> 
>
> Key: IGNITE-1146
> URL: https://issues.apache.org/jira/browse/IGNITE-1146
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>Assignee: Pavel Konstantinov
> Fix For: ignite-1.5
>
> Attachments: summary - client.png, summary - server.png, 
> test-cluster-2.xml
>
>
> Generate:
> * sprint xml configuration;
> * Java class with configuration;
> * Java snippet with configuration;
> * docker file for run with this configuration.
> Download all generated files as zip archive, generate client configuration.



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


[jira] [Updated] (IGNITE-1219) Add ssl configuration

2015-09-30 Thread Pavel Konstantinov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov updated IGNITE-1219:
---
Assignee: Vasiliy Sisko  (was: Pavel Konstantinov)

> Add ssl configuration
> -
>
> Key: IGNITE-1219
> URL: https://issues.apache.org/jira/browse/IGNITE-1219
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: ignite-1.4
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
> Fix For: ignite-1.5
>
>
> We need to add ssl configuration to cluster screen



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


[jira] [Commented] (IGNITE-1219) Add ssl configuration

2015-09-30 Thread Pavel Konstantinov (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939360#comment-14939360
 ] 

Pavel Konstantinov commented on IGNITE-1219:


Need to add to UI options for setting following:
{code}



{code}

> Add ssl configuration
> -
>
> Key: IGNITE-1219
> URL: https://issues.apache.org/jira/browse/IGNITE-1219
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: ignite-1.4
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: ignite-1.5
>
>
> We need to add ssl configuration to cluster screen



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


[jira] [Resolved] (IGNITE-888) Web interface to monitoring cluster state.

2015-09-30 Thread Dmitriy Setrakyan (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Setrakyan resolved IGNITE-888.
--
Resolution: Duplicate

> Web interface to monitoring cluster state.
> --
>
> Key: IGNITE-888
> URL: https://issues.apache.org/jira/browse/IGNITE-888
> Project: Ignite
>  Issue Type: Task
>Reporter: Sergey Evdokimov
>Assignee: Gianfranco Murador
>
> Ignite node should start Jetty server with small web application to 
> monitoring node state.
> Web application should has at least 3 pages:
> 1.) Node information: hardware configuration, metrics, node attributes
> 2.) Cluster state: list of available nodes.
> 3.) Caches: list of caches, SQL console, object browser.
> Web application should be packed as Ignite plugin to avoid reference to jetty 
> from Ignite core.
> Technologies:
> - JSP, JSTL, sitemesh
> - Bootstrap, Google Charts



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


[jira] [Closed] (IGNITE-888) Web interface to monitoring cluster state.

2015-09-30 Thread Dmitriy Setrakyan (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Setrakyan closed IGNITE-888.


> Web interface to monitoring cluster state.
> --
>
> Key: IGNITE-888
> URL: https://issues.apache.org/jira/browse/IGNITE-888
> Project: Ignite
>  Issue Type: Task
>Reporter: Sergey Evdokimov
>Assignee: Gianfranco Murador
>
> Ignite node should start Jetty server with small web application to 
> monitoring node state.
> Web application should has at least 3 pages:
> 1.) Node information: hardware configuration, metrics, node attributes
> 2.) Cluster state: list of available nodes.
> 3.) Caches: list of caches, SQL console, object browser.
> Web application should be packed as Ignite plugin to avoid reference to jetty 
> from Ignite core.
> Technologies:
> - JSP, JSTL, sitemesh
> - Bootstrap, Google Charts



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


[jira] [Issue Comment Deleted] (IGNITE-888) Web interface to monitoring cluster state.

2015-09-30 Thread Dmitriy Setrakyan (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Setrakyan updated IGNITE-888:
-
Comment: was deleted

(was: Gianfranco,

I now think this task was filed before the ignite web console development. I 
believe that this exact functionality is now covered in IGNITE-843.

Let's close this ticket as a duplicate.

D.)

> Web interface to monitoring cluster state.
> --
>
> Key: IGNITE-888
> URL: https://issues.apache.org/jira/browse/IGNITE-888
> Project: Ignite
>  Issue Type: Task
>Reporter: Sergey Evdokimov
>Assignee: Gianfranco Murador
>
> Ignite node should start Jetty server with small web application to 
> monitoring node state.
> Web application should has at least 3 pages:
> 1.) Node information: hardware configuration, metrics, node attributes
> 2.) Cluster state: list of available nodes.
> 3.) Caches: list of caches, SQL console, object browser.
> Web application should be packed as Ignite plugin to avoid reference to jetty 
> from Ignite core.
> Technologies:
> - JSP, JSTL, sitemesh
> - Bootstrap, Google Charts



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


[jira] [Commented] (IGNITE-888) Web interface to monitoring cluster state.

2015-09-30 Thread Dmitriy Setrakyan (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939314#comment-14939314
 ] 

Dmitriy Setrakyan commented on IGNITE-888:
--

Gianfranco,

I now think this task was filed before the ignite web console development. I 
believe that this exact functionality is now covered in IGNITE-843.

Let's close this ticket as a duplicate.

D.

> Web interface to monitoring cluster state.
> --
>
> Key: IGNITE-888
> URL: https://issues.apache.org/jira/browse/IGNITE-888
> Project: Ignite
>  Issue Type: Task
>Reporter: Sergey Evdokimov
>Assignee: Gianfranco Murador
>
> Ignite node should start Jetty server with small web application to 
> monitoring node state.
> Web application should has at least 3 pages:
> 1.) Node information: hardware configuration, metrics, node attributes
> 2.) Cluster state: list of available nodes.
> 3.) Caches: list of caches, SQL console, object browser.
> Web application should be packed as Ignite plugin to avoid reference to jetty 
> from Ignite core.
> Technologies:
> - JSP, JSTL, sitemesh
> - Bootstrap, Google Charts



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


[jira] [Commented] (IGNITE-888) Web interface to monitoring cluster state.

2015-09-30 Thread Dmitriy Setrakyan (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939313#comment-14939313
 ] 

Dmitriy Setrakyan commented on IGNITE-888:
--

Gianfranco,

I now think this task was filed before the ignite web console development. I 
believe that this exact functionality is now covered in IGNITE-843.

Let's close this ticket as a duplicate.

D.

> Web interface to monitoring cluster state.
> --
>
> Key: IGNITE-888
> URL: https://issues.apache.org/jira/browse/IGNITE-888
> Project: Ignite
>  Issue Type: Task
>Reporter: Sergey Evdokimov
>Assignee: Gianfranco Murador
>
> Ignite node should start Jetty server with small web application to 
> monitoring node state.
> Web application should has at least 3 pages:
> 1.) Node information: hardware configuration, metrics, node attributes
> 2.) Cluster state: list of available nodes.
> 3.) Caches: list of caches, SQL console, object browser.
> Web application should be packed as Ignite plugin to avoid reference to jetty 
> from Ignite core.
> Technologies:
> - JSP, JSTL, sitemesh
> - Bootstrap, Google Charts



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


[jira] [Updated] (IGNITE-1595) Web Console chart improvements

2015-09-30 Thread Dmitriy Setrakyan (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Setrakyan updated IGNITE-1595:
--
Description: 
Refresh functionality is not working correctly:
* There should be no blinking
* Axises should not refresh, only data
* Graphs that do not support refresh, should have a message saying: Refresh is 
not supported for Bar (icon) charts, use Line (icon) or Area (icon) charts.

Multi-line graphs are not working correctly:
* multiple lines are not shown

  was:
Refresh functionality is not working correctly:
* There should be no blinking
* Axises should not refresh, only data
* Graphs that do not support refresh, should have a message saying: Refresh is 
not support for Bar (icon) charts, use Line (icon) or Area (icon) charts.

Multi-line graphs are not working correctly:
* multiple lines are not shown


> Web Console chart improvements
> --
>
> Key: IGNITE-1595
> URL: https://issues.apache.org/jira/browse/IGNITE-1595
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Dmitriy Setrakyan
>Assignee: Andrey Novikov
> Fix For: 1.5
>
>
> Refresh functionality is not working correctly:
> * There should be no blinking
> * Axises should not refresh, only data
> * Graphs that do not support refresh, should have a message saying: Refresh 
> is not supported for Bar (icon) charts, use Line (icon) or Area (icon) charts.
> Multi-line graphs are not working correctly:
> * multiple lines are not shown



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


[jira] [Updated] (IGNITE-1595) Web Console chart improvements

2015-09-30 Thread Dmitriy Setrakyan (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Setrakyan updated IGNITE-1595:
--
Description: 
Refresh functionality is not working correctly:
* There should be no blinking
* Axises should not refresh, only data
* Graphs that do not support refresh, should have a message saying: Refresh is 
not support for Bar (icon) charts, use Line (icon) or Area (icon) charts.

Multi-line graphs are not working correctly:
* multiple lines are not shown

  was:
Refresh functionality is not working correctly:

# There should be no blinking
# Axises should not refresh, only data
# Graphs that do not support refresh, should have a message saying: Refresh is 
not support for Bar (icon) charts, use Line (icon) or Area (icon) charts.


> Web Console chart improvements
> --
>
> Key: IGNITE-1595
> URL: https://issues.apache.org/jira/browse/IGNITE-1595
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Dmitriy Setrakyan
>Assignee: Andrey Novikov
> Fix For: 1.5
>
>
> Refresh functionality is not working correctly:
> * There should be no blinking
> * Axises should not refresh, only data
> * Graphs that do not support refresh, should have a message saying: Refresh 
> is not support for Bar (icon) charts, use Line (icon) or Area (icon) charts.
> Multi-line graphs are not working correctly:
> * multiple lines are not shown



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


[jira] [Assigned] (IGNITE-1379) Need send error with stacktrace from web control center to webmaster email.

2015-09-30 Thread Vasiliy Sisko (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vasiliy Sisko reassigned IGNITE-1379:
-

Assignee: Vasiliy Sisko

> Need send error with stacktrace from web control center to webmaster email.
> ---
>
> Key: IGNITE-1379
> URL: https://issues.apache.org/jira/browse/IGNITE-1379
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>Assignee: Vasiliy Sisko
>




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


[jira] [Assigned] (IGNITE-1596) Web console agent improvements

2015-09-30 Thread Andrey Novikov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Novikov reassigned IGNITE-1596:
--

Assignee: Andrey Novikov

> Web console agent improvements
> --
>
> Key: IGNITE-1596
> URL: https://issues.apache.org/jira/browse/IGNITE-1596
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Dmitriy Setrakyan
>Assignee: Andrey Novikov
> Fix For: 1.5
>
>
> * Help message should state if the parameter is optional. Ideally default 
> values should be provided on the next line.
> * Default value for config-path should be provided. Text should say: Path to 
> agent property file
> * When started without parameters, web agent should start with defaults 
> instead of printing help message.
> * When started (with or without parameters), agent should print out values 
> for all the configuration settings.
> * We should have a suggestion saying: To start web-agent in test-drive mode, 
> pass "-tm" and "-ts" parameters
> * Before prompting for token, agent should say: 
> Security token is required to establish connection to the web console. 
> It is available on the Profile page: https://URL
> Enter security token:



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


[jira] [Updated] (IGNITE-1595) Web Console chart improvements

2015-09-30 Thread Dmitriy Setrakyan (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Setrakyan updated IGNITE-1595:
--
Summary: Web Console chart improvements  (was: Web Console chart refresh 
functionality)

> Web Console chart improvements
> --
>
> Key: IGNITE-1595
> URL: https://issues.apache.org/jira/browse/IGNITE-1595
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Dmitriy Setrakyan
>Assignee: Andrey Novikov
> Fix For: 1.5
>
>
> Refresh functionality is not working correctly:
> # There should be no blinking
> # Axises should not refresh, only data
> # Graphs that do not support refresh, should have a message saying: Refresh 
> is not support for Bar (icon) charts, use Line (icon) or Area (icon) charts.



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


[jira] [Assigned] (IGNITE-1595) Web Console chart refresh functionality

2015-09-30 Thread Andrey Novikov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Novikov reassigned IGNITE-1595:
--

Assignee: Andrey Novikov

> Web Console chart refresh functionality
> ---
>
> Key: IGNITE-1595
> URL: https://issues.apache.org/jira/browse/IGNITE-1595
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Dmitriy Setrakyan
>Assignee: Andrey Novikov
> Fix For: 1.5
>
>
> Refresh functionality is not working correctly:
> # There should be no blinking
> # Axises should not refresh, only data
> # Graphs that do not support refresh, should have a message saying: Refresh 
> is not support for Bar (icon) charts, use Line (icon) or Area (icon) charts.



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


[jira] [Assigned] (IGNITE-1594) Home page for web console

2015-09-30 Thread Vasiliy Sisko (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vasiliy Sisko reassigned IGNITE-1594:
-

Assignee: Vasiliy Sisko

> Home page for web console
> -
>
> Key: IGNITE-1594
> URL: https://issues.apache.org/jira/browse/IGNITE-1594
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Dmitriy Setrakyan
>Assignee: Vasiliy Sisko
> Fix For: ignite-1.5
>
>
> Home page should look as following:
> # Logo with Apache Ignite Web Console up top
> # Explanation of what web console is immediately below.
> # Login on the left
> # screenshots on the right



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


[jira] [Updated] (IGNITE-1596) Web console agent improvements

2015-09-30 Thread Dmitriy Setrakyan (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Setrakyan updated IGNITE-1596:
--
Description: 
* Help message should state if the parameter is optional. Ideally default 
values should be provided on the next line.
* Default value for config-path should be provided. Text should say: Path to 
agent property file
* When started without parameters, web agent should start with defaults instead 
of printing help message.
* When started (with or without parameters), agent should print out values for 
all the configuration settings.
* We should have a suggestion saying: To start web-agent in test-drive mode, 
pass "-tm" and "-ts" parameters
* Before prompting for token, agent should say: 
Security token is required to establish connection to the web console. 
It is available on the Profile page: https://URL
Enter security token:


  was:
* Help message should state if the parameter is optional. Ideally default 
values should be provided on the next line.
* Default value for config-path should be provided. Text should say: Path to 
agent property file
* When started without parameters, web agent should start with defaults instead 
of printing help message.
* When started (with or without parameters), agent should print out values for 
all the configuration settings.
* We should have a suggestion saying: To start web-agent in test-drive mode, 
pass "-tm" and "-ts" parameters
* Before prompting for token, agent should say: 
Security token is required to establish connection to the web console. 
It is available on the Profile page: http://console.gridgain.com/profile
Enter security token:



> Web console agent improvements
> --
>
> Key: IGNITE-1596
> URL: https://issues.apache.org/jira/browse/IGNITE-1596
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Dmitriy Setrakyan
> Fix For: 1.5
>
>
> * Help message should state if the parameter is optional. Ideally default 
> values should be provided on the next line.
> * Default value for config-path should be provided. Text should say: Path to 
> agent property file
> * When started without parameters, web agent should start with defaults 
> instead of printing help message.
> * When started (with or without parameters), agent should print out values 
> for all the configuration settings.
> * We should have a suggestion saying: To start web-agent in test-drive mode, 
> pass "-tm" and "-ts" parameters
> * Before prompting for token, agent should say: 
> Security token is required to establish connection to the web console. 
> It is available on the Profile page: https://URL
> Enter security token:



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


[jira] [Updated] (IGNITE-1596) Web console agent improvements

2015-09-30 Thread Dmitriy Setrakyan (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Setrakyan updated IGNITE-1596:
--
Description: 
* Help message should state if the parameter is optional. Ideally default 
values should be provided on the next line.
* Default value for config-path should be provided. Text should say: Path to 
agent property file
* When started without parameters, web agent should start with defaults instead 
of printing help message.
* When start (with or without parameters), agent should print out values for 
all the configuration settings.
* We should have a suggestion saying: To start web-agent in test-drive mode, 
pass "-tm" and "-ts" parameters
* Before prompting for token, agent should say: 
Security token is required to establish connection to the web console. 
It is available on the Profile page: http://console.gridgain.com/profile
Enter security token:


  was:
* Help message should state if the parameter is optional. Ideally default 
values should be provided on the next line.
* Default value for config-path should be provided. Text should say: Path to 
agent property file
* When start (with or without parameters), agent should print out values for 
all the configuration settings.
* We should have a suggestion saying: To start web-agent in test-drive mode, 
pass "-tm" and "-ts" parameters
* Before prompting for token, agent should say: 
Security token is required to establish connection to the web console. 
It is available on the Profile page: http://console.gridgain.com/profile
Enter security token:



> Web console agent improvements
> --
>
> Key: IGNITE-1596
> URL: https://issues.apache.org/jira/browse/IGNITE-1596
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Dmitriy Setrakyan
> Fix For: 1.5
>
>
> * Help message should state if the parameter is optional. Ideally default 
> values should be provided on the next line.
> * Default value for config-path should be provided. Text should say: Path to 
> agent property file
> * When started without parameters, web agent should start with defaults 
> instead of printing help message.
> * When start (with or without parameters), agent should print out values for 
> all the configuration settings.
> * We should have a suggestion saying: To start web-agent in test-drive mode, 
> pass "-tm" and "-ts" parameters
> * Before prompting for token, agent should say: 
> Security token is required to establish connection to the web console. 
> It is available on the Profile page: http://console.gridgain.com/profile
> Enter security token:



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


[jira] [Updated] (IGNITE-1596) Web console agent improvements

2015-09-30 Thread Dmitriy Setrakyan (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Setrakyan updated IGNITE-1596:
--
Description: 
* Help message should state if the parameter is optional. Ideally default 
values should be provided on the next line.
* Default value for config-path should be provided. Text should say: Path to 
agent property file
* When started without parameters, web agent should start with defaults instead 
of printing help message.
* When started (with or without parameters), agent should print out values for 
all the configuration settings.
* We should have a suggestion saying: To start web-agent in test-drive mode, 
pass "-tm" and "-ts" parameters
* Before prompting for token, agent should say: 
Security token is required to establish connection to the web console. 
It is available on the Profile page: http://console.gridgain.com/profile
Enter security token:


  was:
* Help message should state if the parameter is optional. Ideally default 
values should be provided on the next line.
* Default value for config-path should be provided. Text should say: Path to 
agent property file
* When started without parameters, web agent should start with defaults instead 
of printing help message.
* When start (with or without parameters), agent should print out values for 
all the configuration settings.
* We should have a suggestion saying: To start web-agent in test-drive mode, 
pass "-tm" and "-ts" parameters
* Before prompting for token, agent should say: 
Security token is required to establish connection to the web console. 
It is available on the Profile page: http://console.gridgain.com/profile
Enter security token:



> Web console agent improvements
> --
>
> Key: IGNITE-1596
> URL: https://issues.apache.org/jira/browse/IGNITE-1596
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Dmitriy Setrakyan
> Fix For: 1.5
>
>
> * Help message should state if the parameter is optional. Ideally default 
> values should be provided on the next line.
> * Default value for config-path should be provided. Text should say: Path to 
> agent property file
> * When started without parameters, web agent should start with defaults 
> instead of printing help message.
> * When started (with or without parameters), agent should print out values 
> for all the configuration settings.
> * We should have a suggestion saying: To start web-agent in test-drive mode, 
> pass "-tm" and "-ts" parameters
> * Before prompting for token, agent should say: 
> Security token is required to establish connection to the web console. 
> It is available on the Profile page: http://console.gridgain.com/profile
> Enter security token:



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


[jira] [Commented] (IGNITE-1596) Web console agent improvements

2015-09-30 Thread Dmitriy Setrakyan (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939308#comment-14939308
 ] 

Dmitriy Setrakyan commented on IGNITE-1596:
---

Web console screens that require agent connectivity should automatically check 
if agent is connected and refresh.

> Web console agent improvements
> --
>
> Key: IGNITE-1596
> URL: https://issues.apache.org/jira/browse/IGNITE-1596
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Dmitriy Setrakyan
> Fix For: 1.5
>
>
> * Help message should state if the parameter is optional. Ideally default 
> values should be provided on the next line.
> * Default value for config-path should be provided. Text should say: Path to 
> agent property file
> * When start (with or without parameters), agent should print out values for 
> all the configuration settings.
> * We should have a suggestion saying: To start web-agent in test-drive mode, 
> pass "-tm" and "-ts" parameters
> * Before prompting for token, agent should say: 
> Security token is required to establish connection to the web console. 
> It is available on the Profile page: http://console.gridgain.com/profile
> Enter security token:



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


[jira] [Updated] (IGNITE-1595) Web Console chart refresh functionality

2015-09-30 Thread Dmitriy Setrakyan (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Setrakyan updated IGNITE-1595:
--
Description: 
Refresh functionality is not working correctly:

# There should be no blinking
# Axises should not refresh, only data
# Graphs that do not support refresh, should have a message saying: Refresh is 
not support for Bar (icon) charts, use Line (icon) or Area (icon) charts.

  was:
Refresh functionality is not working correctly:

# There should be no blinking
# Axises should not refresh, only data
# Graphs that do not support refresh, should have a message saying: Refresh is 
not support for Bar charts, use Line (icon) or Area (icon) charts.


> Web Console chart refresh functionality
> ---
>
> Key: IGNITE-1595
> URL: https://issues.apache.org/jira/browse/IGNITE-1595
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Dmitriy Setrakyan
> Fix For: 1.5
>
>
> Refresh functionality is not working correctly:
> # There should be no blinking
> # Axises should not refresh, only data
> # Graphs that do not support refresh, should have a message saying: Refresh 
> is not support for Bar (icon) charts, use Line (icon) or Area (icon) charts.



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


[jira] [Commented] (IGNITE-1594) Home page for web console

2015-09-30 Thread Dmitriy Setrakyan (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939306#comment-14939306
 ] 

Dmitriy Setrakyan commented on IGNITE-1594:
---

* The clicker left and right arrows should be underneath the image, around the 
little circles
* Description text should not have shadows.

> Home page for web console
> -
>
> Key: IGNITE-1594
> URL: https://issues.apache.org/jira/browse/IGNITE-1594
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Dmitriy Setrakyan
> Fix For: ignite-1.5
>
>
> Home page should look as following:
> # Logo with Apache Ignite Web Console up top
> # Explanation of what web console is immediately below.
> # Login on the left
> # screenshots on the right



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


[jira] [Created] (IGNITE-1596) Web console agent improvements

2015-09-30 Thread Dmitriy Setrakyan (JIRA)
Dmitriy Setrakyan created IGNITE-1596:
-

 Summary: Web console agent improvements
 Key: IGNITE-1596
 URL: https://issues.apache.org/jira/browse/IGNITE-1596
 Project: Ignite
  Issue Type: Sub-task
  Components: UI
Reporter: Dmitriy Setrakyan
 Fix For: 1.5


* Help message should state if the parameter is optional. Ideally default 
values should be provided on the next line.
* Default value for config-path should be provided. Text should say: Path to 
agent property file
* When start (with or without parameters), agent should print out values for 
all the configuration settings.
* We should have a suggestion saying: To start web-agent in test-drive mode, 
pass "-tm" and "-ts" parameters
* Before prompting for token, agent should say: 
Security token is required to establish connection to the web console. 
It is available on the Profile page: http://console.gridgain.com/profile
Enter security token:




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


[jira] [Commented] (IGNITE-1177) Implement metadata screen

2015-09-30 Thread Pavel Konstantinov (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939300#comment-14939300
 ] 

Pavel Konstantinov commented on IGNITE-1177:


I think we have typo in help text for Caches field, currently the text is 
"Select caches to associate database with cache", I think should be the word 
'metadata' instead 'database'.

> Implement metadata screen
> -
>
> Key: IGNITE-1177
> URL: https://issues.apache.org/jira/browse/IGNITE-1177
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.1.4
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: ignite-1.5
>
>
> Implement metadata screen that should:
> 1) Add/edit metadata manually.
> 2) Import metadata from database metadata.



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


[jira] [Commented] (IGNITE-1595) Web Console chart refresh functionality

2015-09-30 Thread Dmitriy Setrakyan (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939296#comment-14939296
 ] 

Dmitriy Setrakyan commented on IGNITE-1595:
---

Timeframe shown on the chart should be configurable.

> Web Console chart refresh functionality
> ---
>
> Key: IGNITE-1595
> URL: https://issues.apache.org/jira/browse/IGNITE-1595
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Dmitriy Setrakyan
> Fix For: 1.5
>
>
> Refresh functionality is not working correctly:
> # There should be no blinking
> # Axises should not refresh, only data
> # Graphs that do not support refresh, should have a message saying: Refresh 
> is not support for Bar charts, use Line (icon) or Area (icon) charts.



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


[jira] [Created] (IGNITE-1595) Web Console chart refresh functionality

2015-09-30 Thread Dmitriy Setrakyan (JIRA)
Dmitriy Setrakyan created IGNITE-1595:
-

 Summary: Web Console chart refresh functionality
 Key: IGNITE-1595
 URL: https://issues.apache.org/jira/browse/IGNITE-1595
 Project: Ignite
  Issue Type: Sub-task
  Components: UI
Reporter: Dmitriy Setrakyan
 Fix For: 1.5


Refresh functionality is not working correctly:

# There should be no blinking
# Axises should not refresh, only data
# Graphs that do not support refresh, should have a message saying: Refresh is 
not support for Bar charts, use Line (icon) or Area (icon) charts.



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


[jira] [Commented] (IGNITE-1594) Home page for web console

2015-09-30 Thread Dmitriy Setrakyan (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939293#comment-14939293
 ] 

Dmitriy Setrakyan commented on IGNITE-1594:
---

Web console should have the following description:

Apache Ignite Web Console is an interactive web management tool which allows 
users to:
# Create and download various configurations for Apache Ignite
# Automatically load SQL metadata form any RDBMS
# Connect to Ignite cluster and run SQL analytics on it

> Home page for web console
> -
>
> Key: IGNITE-1594
> URL: https://issues.apache.org/jira/browse/IGNITE-1594
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Dmitriy Setrakyan
> Fix For: ignite-1.5
>
>
> Home page should look as following:
> # Logo with Apache Ignite Web Console up top
> # Explanation of what web console is immediately below.
> # Login on the left
> # screenshots on the right



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


[jira] [Created] (IGNITE-1594) Home page for web console

2015-09-30 Thread Dmitriy Setrakyan (JIRA)
Dmitriy Setrakyan created IGNITE-1594:
-

 Summary: Home page for web console
 Key: IGNITE-1594
 URL: https://issues.apache.org/jira/browse/IGNITE-1594
 Project: Ignite
  Issue Type: Sub-task
  Components: UI
Reporter: Dmitriy Setrakyan
 Fix For: ignite-1.5


Home page should look as following:
# Logo with Apache Ignite Web Console up top
# Explanation of what web console is immediately below.
# Login on the left
# screenshots on the right



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


[jira] [Commented] (IGNITE-1379) Need send error with stacktrace from web control center to webmaster email.

2015-09-30 Thread Dmitriy Setrakyan (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939287#comment-14939287
 ] 

Dmitriy Setrakyan commented on IGNITE-1379:
---

Also, that screen should have an option to send errors in an email to the admin.

> Need send error with stacktrace from web control center to webmaster email.
> ---
>
> Key: IGNITE-1379
> URL: https://issues.apache.org/jira/browse/IGNITE-1379
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>




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


[jira] [Reopened] (IGNITE-1148) Implement sql query to ignite node.

2015-09-30 Thread Pavel Konstantinov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov reopened IGNITE-1148:

  Assignee: Andrey Novikov  (was: Pavel Konstantinov)

1) We must display warning that no agent connected with possibility to download 
agent and instructions how to run it.
2) After agent will be started and successfully connected to console the SQL 
page must refresh automatically.
3) If console lost connection with agent the warning must appear again.

> Implement sql query to ignite node.
> ---
>
> Key: IGNITE-1148
> URL: https://issues.apache.org/jira/browse/IGNITE-1148
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
> Fix For: ignite-1.5
>
> Attachments: metadata mockup.png, sql - notebooks.png
>
>
> Need create page for display sql query result:
> * Add optional select cache.
> * Scan query
> * Explain query
> * Query
> * Show metadata.
> Connect with agent through websocket. 



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


[jira] [Assigned] (IGNITE-640) Implement IgniteMultimap data structures

2015-09-30 Thread Vladisav Jelisavcic (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladisav Jelisavcic reassigned IGNITE-640:
--

Assignee: Vladisav Jelisavcic

> Implement IgniteMultimap data structures
> 
>
> Key: IGNITE-640
> URL: https://issues.apache.org/jira/browse/IGNITE-640
> Project: Ignite
>  Issue Type: Sub-task
>  Components: data structures
>Reporter: Dmitriy Setrakyan
>Assignee: Vladisav Jelisavcic
>
> We need to add {{IgniteMultimap}} data structure in addition to other data 
> structures provided by Ignite. {{IgniteMultiMap}} should have similar API to 
> {{java.util.Map}} class in JDK, but support the semantics of multiple values 
> per key, similar to [Guava 
> Multimap|http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/collect/Multimap.html]
> Multimap should also support colocated and non-colocated modes, similar to 
> [IgniteQueue|https://github.com/apache/incubator-ignite/blob/master/modules/core/src/main/java/org/apache/ignite/IgniteQueue.java]
>  and its implementation, 
> [GridAtomicCacheQueueImpl|https://github.com/apache/incubator-ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/datastructures/GridAtomicCacheQueueImpl.java].



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


[jira] [Commented] (IGNITE-1355) Potential NPE in CacheAffinityProxy

2015-09-30 Thread Artem Shutak (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14938203#comment-14938203
 ] 

Artem Shutak commented on IGNITE-1355:
--

Ignite.affinity(...) can be called for cache nonexistent cache. As a result a 
call to any method of the affinity will produce NPE.

Fix proposal:
- return special value and empty arrays/collections in this case
- update javadoc for these goals

> Potential NPE in CacheAffinityProxy
> ---
>
> Key: IGNITE-1355
> URL: https://issues.apache.org/jira/browse/IGNITE-1355
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Semen Boikov
>Assignee: Artem Shutak
>Priority: Critical
> Fix For: ignite-1.5
>
>
> NPE was observed on TC:
> {noformat}
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor$AffinityInfo.access$1800(GridAffinityProcessor.java:537)
> at 
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor$CacheAffinityProxy.mapPartitionToPrimaryAndBackups(GridAffinityProcessor.java:879)
> at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:423)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteCacheCrossCacheTxFailoverTest.crossCacheTxFailover(IgniteCacheCrossCacheTxFailoverTest.java:355)
> {noformat}
> As I see method CacheAffinityProxy.cache() can return null, but there are no 
> checks for null.



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


[jira] [Commented] (IGNITE-1589) Platform .Net: CacheAbstractTest.TestPutGetAsyncMultithreaded fails

2015-09-30 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14937695#comment-14937695
 ] 

ASF GitHub Bot commented on IGNITE-1589:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-1589 Platform .Net: CacheAbstractTest.TestPutGetAsyncMultithreaded 
fails

Fix PlatformMemoryStream race condition: finalizer thread calls 
SynchronizeOutput which affects pooled memory used in another thread.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-1589

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/119.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #119


commit 5a15e05673dda9e065c939426fd3d4abc838513a
Author: ptupitsyn 
Date:   2015-09-30T16:42:06Z

Fix PlatformMemoryStream race condition




> Platform .Net: CacheAbstractTest.TestPutGetAsyncMultithreaded fails
> ---
>
> Key: IGNITE-1589
> URL: https://issues.apache.org/jira/browse/IGNITE-1589
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: ignite-1.5
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: ignite-1.5
>
>




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


[jira] [Commented] (IGNITE-1589) Platform .Net: CacheAbstractTest.TestPutGetAsyncMultithreaded fails

2015-09-30 Thread Pavel Tupitsyn (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14937697#comment-14937697
 ] 

Pavel  Tupitsyn commented on IGNITE-1589:
-

Fixed PlatformMemoryStream race condition: finalizer thread calls 
SynchronizeOutput which affects pooled memory used in another thread.

> Platform .Net: CacheAbstractTest.TestPutGetAsyncMultithreaded fails
> ---
>
> Key: IGNITE-1589
> URL: https://issues.apache.org/jira/browse/IGNITE-1589
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: ignite-1.5
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: ignite-1.5
>
>




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


[jira] [Commented] (IGNITE-530) Implement IgniteTwitterStreamer to stream data from Twitter feeds

2015-09-30 Thread Lalit Kumar Jha (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14937492#comment-14937492
 ] 

Lalit Kumar Jha commented on IGNITE-530:


Fixed those issues.

> Implement IgniteTwitterStreamer to stream data from Twitter feeds
> -
>
> Key: IGNITE-530
> URL: https://issues.apache.org/jira/browse/IGNITE-530
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Lalit Kumar Jha
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> We should create {{IgniteTwitterStreamer}} which will consume messages from 
> Twitter and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert Twitter data to Ignite data using an optional pluggable converter.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.



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


[jira] [Commented] (IGNITE-1589) Platform .Net: CacheAbstractTest.TestPutGetAsyncMultithreaded fails

2015-09-30 Thread Pavel Tupitsyn (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14937469#comment-14937469
 ] 

Pavel  Tupitsyn commented on IGNITE-1589:
-

Looks like PlatformMemoryStream finalizer causes this.

> Platform .Net: CacheAbstractTest.TestPutGetAsyncMultithreaded fails
> ---
>
> Key: IGNITE-1589
> URL: https://issues.apache.org/jira/browse/IGNITE-1589
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: ignite-1.5
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: ignite-1.5
>
>




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


[jira] [Commented] (IGNITE-1586) CPP: Add isValid() method to all proxy-like classes

2015-09-30 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14937468#comment-14937468
 ] 

ASF GitHub Bot commented on IGNITE-1586:


GitHub user isapego opened a pull request:

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

IGNITE-1586: Added IsValid() method to Ignite, Cache and QueryCursor



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/isapego/ignite ignite-1586

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/118.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #118


commit 681df9d3e2b2567fafe1d69dcfd08541ba027d63
Author: isapego 
Date:   2015-09-30T16:20:43Z

IGNITE-1586: Added IsValid() method to Ignite, Cache and QueryCursor




> CPP: Add isValid() method to all proxy-like classes
> ---
>
> Key: IGNITE-1586
> URL: https://issues.apache.org/jira/browse/IGNITE-1586
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>
> Need to add isValid() methods to proxy-like classes so users can check if 
> they can use an instance.



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


[jira] [Created] (IGNITE-1592) [Test Failed] GridCachePartitionedOffHeapValuesQueueApiSelfTest.testQueueRemoveMultithreadBounded

2015-09-30 Thread Anton Vinogradov (JIRA)
Anton Vinogradov created IGNITE-1592:


 Summary: [Test Failed] 
GridCachePartitionedOffHeapValuesQueueApiSelfTest.testQueueRemoveMultithreadBounded
 Key: IGNITE-1592
 URL: https://issues.apache.org/jira/browse/IGNITE-1592
 Project: Ignite
  Issue Type: Test
Affects Versions: ignite-1.5
Reporter: Anton Vinogradov
Priority: Blocker
 Fix For: ignite-1.5


java.lang.AssertionError: null
at 
org.apache.ignite.internal.processors.cache.datastructures.GridCacheQueueApiSelfAbstractTest.testQueueRemoveMultithreadBounded(GridCacheQueueApiSelfAbstractTest.java:443)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
--- Stdout: ---
[11:59:42,194][INFO ][main][root] >>> Starting test: 
testQueueRemoveMultithreadBounded <<<
[12:02:42,196][INFO ][main][root] >>> Stopping test: 
testQueueRemoveMultithreadBounded in 180002 ms <<<
--- Stderr: ---
[12:02:42,195][ERROR][main][root] Test failed.
java.lang.AssertionError
at 
org.apache.ignite.internal.processors.cache.datastructures.GridCacheQueueApiSelfAbstractTest.testQueueRemoveMultithreadBounded(GridCacheQueueApiSelfAbstractTest.java:443)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)



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


[jira] [Commented] (IGNITE-1588) CPP: Fix constructor of the IgniteJvmOption class

2015-09-30 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14937035#comment-14937035
 ] 

ASF GitHub Bot commented on IGNITE-1588:


GitHub user isapego opened a pull request:

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

IGNITE-1588: Fix for the IgniteJvmOption class



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/isapego/ignite ignite-1588

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/117.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #117


commit 374ed5277d030cd28afdf0647769757ce3d1d9b1
Author: isapego 
Date:   2015-09-30T15:41:35Z

IGNITE-1588: Fix for the IgniteJvmOption class

commit ea795e7cabad83feb2f1a3518e9547c0f560dfa2
Author: isapego 
Date:   2015-09-30T15:48:49Z

Fix for indentation




> CPP: Fix constructor of the IgniteJvmOption class
> -
>
> Key: IGNITE-1588
> URL: https://issues.apache.org/jira/browse/IGNITE-1588
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>
> Current implementation of the IgniteJvmOption class takes {{char*}} as 
> argument, when it should take {{const char*}} and copy it.



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


[jira] [Created] (IGNITE-1590) IGFS: update & create operations should be truly thread-safe.

2015-09-30 Thread Ivan Veselovsky (JIRA)
Ivan Veselovsky created IGNITE-1590:
---

 Summary: IGFS: update & create operations should be truly 
thread-safe.
 Key: IGNITE-1590
 URL: https://issues.apache.org/jira/browse/IGNITE-1590
 Project: Ignite
  Issue Type: Bug
Affects Versions: ignite-1.4
Reporter: Ivan Veselovsky
Assignee: Ivan Veselovsky
 Fix For: ignite-1.5


Fix #create() operation & revise #update().
Currently the tests with many concurrent operations (involving  
delete/rename/nkdirs/create) reveal concurrency problems -- some tree entries 
get "lost".



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


[jira] [Created] (IGNITE-1589) Platform .Net: CacheAbstractTest.TestPutGetAsyncMultithreaded fails

2015-09-30 Thread Pavel Tupitsyn (JIRA)
Pavel  Tupitsyn created IGNITE-1589:
---

 Summary: Platform .Net: 
CacheAbstractTest.TestPutGetAsyncMultithreaded fails
 Key: IGNITE-1589
 URL: https://issues.apache.org/jira/browse/IGNITE-1589
 Project: Ignite
  Issue Type: Sub-task
  Components: interop
Affects Versions: ignite-1.5
Reporter: Pavel  Tupitsyn
Assignee: Pavel  Tupitsyn
 Fix For: ignite-1.5






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


[jira] [Commented] (IGNITE-1534) Failed to map keys for cache (all partition nodes left the grid).

2015-09-30 Thread Semen Boikov (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936976#comment-14936976
 ] 

Semen Boikov commented on IGNITE-1534:
--

Got another error trying to reproduce this issue:
{noformat}
[16:33:55]W: [org.apache.ignite:ignite-core] 
java.lang.AssertionError: Invalid topology version 
[topVer=AffinityTopologyVersion [topVer=3, minorTopVer=0], 
exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2, 
minorTopVer=0], nodeId=10a04c3e, evt=NODE_JOINED]]
[16:33:55]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.updateTopologyVersion(GridDhtPartitionTopologyImpl.java:213)
[16:33:55]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:719)
[16:33:55]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1204)
[16:33:55]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
{noformat}

Looks like a race in exchanges handling.

> Failed to map keys for cache (all partition nodes left the grid).
> -
>
> Key: IGNITE-1534
> URL: https://issues.apache.org/jira/browse/IGNITE-1534
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Andrey Gura
>Assignee: Semen Boikov
> Fix For: ignite-1.5
>
>
> During testing changes related with IGNITE-1171 the following problem was 
> found:
> {panel}
> Unhandled exception 
> org.apache.ignite.cache.CacheServerNotFoundException: Failed to map keys for 
> cache (all partition nodes left the grid).
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1612)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1744)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.getAndPut(IgniteCacheProxy.java:1043)
>   at io.vertx.spi.cluster.ignite.impl.MapImpl.put(MapImpl.java:85)
>   at io.vertx.core.impl.HAManager.(HAManager.java:147)
>   at io.vertx.core.impl.VertxImpl.lambda$null$143(VertxImpl.java:156)
>   at io.vertx.core.impl.VertxImpl$$Lambda$35/2107573573.handle(Unknown 
> Source)
>   at 
> io.vertx.core.net.impl.NetServerImpl.lambda$null$34(NetServerImpl.java:252)
>   at 
> io.vertx.core.net.impl.NetServerImpl$$Lambda$39/1662210125.handle(Unknown 
> Source)
>   at 
> io.vertx.core.impl.ContextImpl.lambda$wrapTask$20(ContextImpl.java:324)
>   at io.vertx.core.impl.ContextImpl$$Lambda$31/1504729381.run(Unknown 
> Source)
>   at 
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
>   at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
>   at 
> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class 
> org.apache.ignite.internal.cluster.ClusterTopologyServerNotFoundException: 
> Failed to map keys for cache (all partition nodes left the grid).
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(GridNearAtomicUpdateFuture.java:808)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:422)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$100(GridNearAtomicUpdateFuture.java:73)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$1$1.run(GridNearAtomicUpdateFuture.java:406)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6427)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:788)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   ... 1 more
> {panel}
> This exception occures on topology from 3 nodes that start dynamic cache with 
> the same configuration on all nodes and performs {{put}} operation. All 3 
> nodes are alive.
> The problem reproduces period

[jira] [Comment Edited] (IGNITE-1416) .Net: Implement AtomicLong data structure

2015-09-30 Thread Pavel Tupitsyn (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936925#comment-14936925
 ] 

Pavel  Tupitsyn edited comment on IGNITE-1416 at 9/30/15 2:46 PM:
--

We have discussed that and decided to use C-style semantics in all the platform 
code, do you remember that? 
Common is the gateway, yes, and it is in Cpp. We should use semantics that Cpp 
devs are familiar with, the same way as we do in C# API.

> getAndDecrement
getAnd* methods are pointless. 
getAndDecrement = decrementAndGet() + 1; 
Let's not bloat our interop code with them. It is hard enough to maintain 
already.

> so that developer has clear understanding how native call maps to Java 
> operation
C++ dev either does not care about Java operation, or knows it enough to easily 
understand semantic differences.


was (Author: ptupitsyn):
We have discussed that and decided to use C-style semantics in all the platform 
code, do you remember that? 
Common is the gateway, yes, and it is in C++. We should use semantics that C++ 
devs are familiar with, the same way as we do in C# API.

> getAndDecrement
getAnd* methods are pointless. 
getAndDecrement = decrementAndGet() + 1; 
Let's not bloat our interop code with them. It is hard enough to maintain 
already.

> so that developer has clear understanding how native call maps to Java 
> operation
C++ dev either does not care about Java operation, or knows it enough to easily 
understand semantic differences.

> .Net: Implement AtomicLong data structure
> -
>
> Key: IGNITE-1416
> URL: https://issues.apache.org/jira/browse/IGNITE-1416
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Critical
> Fix For: ignite-1.5
>
>




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


[jira] [Commented] (IGNITE-1416) .Net: Implement AtomicLong data structure

2015-09-30 Thread Pavel Tupitsyn (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936925#comment-14936925
 ] 

Pavel  Tupitsyn commented on IGNITE-1416:
-

We have discussed that and decided to use C-style semantics in all the platform 
code, do you remember that? 
Common is the gateway, yes, and it is in C++. We should use semantics that C++ 
devs are familiar with, the same way as we do in C# API.

> getAndDecrement
getAnd* methods are pointless. 
getAndDecrement = decrementAndGet() + 1; 
Let's not bloat our interop code with them. It is hard enough to maintain 
already.

> so that developer has clear understanding how native call maps to Java 
> operation
C++ dev either does not care about Java operation, or knows it enough to easily 
understand semantic differences.

> .Net: Implement AtomicLong data structure
> -
>
> Key: IGNITE-1416
> URL: https://issues.apache.org/jira/browse/IGNITE-1416
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Critical
> Fix For: ignite-1.5
>
>




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


[jira] [Updated] (IGNITE-1588) CPP: Fix constructor of the IgniteJvmOption class

2015-09-30 Thread Igor Sapego (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Igor Sapego updated IGNITE-1588:

Component/s: interop

> CPP: Fix constructor of the IgniteJvmOption class
> -
>
> Key: IGNITE-1588
> URL: https://issues.apache.org/jira/browse/IGNITE-1588
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>
> Current implementation of the IgniteJvmOption class takes {{char*}} as 
> argument, when it should take {{const char*}} and copy it.



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


[jira] [Created] (IGNITE-1588) CPP: Fix constructor of the IgniteJvmOption class

2015-09-30 Thread Igor Sapego (JIRA)
Igor Sapego created IGNITE-1588:
---

 Summary: CPP: Fix constructor of the IgniteJvmOption class
 Key: IGNITE-1588
 URL: https://issues.apache.org/jira/browse/IGNITE-1588
 Project: Ignite
  Issue Type: Task
Reporter: Igor Sapego
Assignee: Igor Sapego


Current implementation of the IgniteJvmOption class takes {{char*}} as 
argument, when it should take {{const char*}} and copy it.



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


[jira] [Updated] (IGNITE-1588) CPP: Fix constructor of the IgniteJvmOption class

2015-09-30 Thread Igor Sapego (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Igor Sapego updated IGNITE-1588:

Affects Version/s: 1.1.4

> CPP: Fix constructor of the IgniteJvmOption class
> -
>
> Key: IGNITE-1588
> URL: https://issues.apache.org/jira/browse/IGNITE-1588
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>
> Current implementation of the IgniteJvmOption class takes {{char*}} as 
> argument, when it should take {{const char*}} and copy it.



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


[jira] [Commented] (IGNITE-1565) Platform .Net: Fix examples

2015-09-30 Thread Pavel Tupitsyn (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936889#comment-14936889
 ] 

Pavel  Tupitsyn commented on IGNITE-1565:
-

Reverted changes in examples code. Added IGNITE_SPRING_CONFIG_URL_PREFIX env 
var to fix config paths at runtime.
See changes in both repos.

> Platform .Net: Fix examples
> ---
>
> Key: IGNITE-1565
> URL: https://issues.apache.org/jira/browse/IGNITE-1565
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: ignite-1.5
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: ignite-1.5
>
>
> Paths have changed in ignite-1282 branch:
> * config paths should be fixed in examples
> * example files paths should be fixed in example tests



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


[jira] [Updated] (IGNITE-1585) [Test Failed] TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1585:
-
Fix Version/s: ignite-1.5

> [Test Failed] TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine
> ---
>
> Key: IGNITE-1585
> URL: https://issues.apache.org/jira/browse/IGNITE-1585
> Project: Ignite
>  Issue Type: Test
>Affects Versions: ignite-1.5
>Reporter: Anton Vinogradov
> Fix For: ignite-1.5
>
>
> org.apache.ignite.spi.IgniteSpiException: Failed to get registered addresses 
> for the provider: google-compute-engine
> at 
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:229)
> at 
> org.jclouds.compute.internal.FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.checkGroup(FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.java:124)
> at 
> org.jclouds.compute.internal.FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.sharedNameForGroup(FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.java:120)
> at 
> org.jclouds.googlecomputeengine.compute.functions.FirewallTagNamingConvention$Factory.get(FirewallTagNamingConvention.java:39)
> at 
> org.jclouds.googlecomputeengine.compute.functions.InstanceToNodeMetadata.apply(InstanceToNodeMetadata.java:68)
> at 
> org.jclouds.googlecomputeengine.compute.functions.InstanceToNodeMetadata.apply(InstanceToNodeMetadata.java:43)
> at 
> com.google.common.base.Functions$FunctionComposition.apply(Functions.java:211)
> at com.google.common.collect.Iterators$8.transform(Iterators.java:794)
> at 
> com.google.common.collect.TransformedIterator.next(TransformedIterator.java:48)
> at com.google.common.collect.Iterators$7.computeNext(Iterators.java:646)
> at 
> com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
> at 
> com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
> at com.google.common.collect.Iterators.addAll(Iterators.java:356)
> at com.google.common.collect.Iterables.addAll(Iterables.java:350)
> at com.google.common.collect.Sets.newLinkedHashSet(Sets.java:328)
> at 
> org.jclouds.compute.internal.BaseComputeService.listNodesDetailsMatching(BaseComputeService.java:359)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinder.getRegisteredAddresses(TcpDiscoveryCloudIpFinder.java:190)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testCloudProvider(TcpDiscoveryCloudIpFinderSelfTest.java:106)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine(TcpDiscoveryCloudIpFinderSelfTest.java:71)
> --- Stdout: ---
> Configured log4j from: 
> /opt/TeamcityAgent/work/871ff4a46e450b13/modules/core/src/test/config/log4j-test.xml
> [14:19:49,901][INFO ][main][root] >>> Starting test class: 
> TcpDiscoveryCloudIpFinderSelfTest <<<
> [14:19:49,944][INFO ][main][root] >>> Starting test: testGoogleComputeEngine 
> <<<
> [14:19:49,945][INFO ][test-runner][root] Testing provider: 
> google-compute-engine
> [14:19:52,312][INFO ][main][root] >>> Stopping test: testGoogleComputeEngine 
> in 2367 ms <<<
> --- Stderr: ---
> [14:19:52,310][ERROR][main][root] Test failed.
> class org.apache.ignite.spi.IgniteSpiException: Failed to get registered 
> addresses for the provider: google-compute-engine
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinder.getRegisteredAddresses(TcpDiscoveryCloudIpFinder.java:210)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testCloudProvider(TcpDiscoveryCloudIpFinderSelfTest.java:106)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine(TcpDiscoveryCloudIpFinderSelfTest.java:71)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> Caused by: java.lang.NullPointerException: group
> at 
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:229)
> at 
> org.jclouds.compute.inte

[jira] [Updated] (IGNITE-1584) [Test Failed] IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1584:
-
Priority: Blocker  (was: Major)

> [Test Failed] 
> IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap
> ---
>
> Key: IGNITE-1584
> URL: https://issues.apache.org/jira/browse/IGNITE-1584
> Project: Ignite
>  Issue Type: Test
>Affects Versions: ignite-1.5
>Reporter: Anton Vinogradov
>Priority: Blocker
> Fix For: ignite-1.5
>
> Attachments: 
> IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap
>
>




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


[jira] [Updated] (IGNITE-1585) [Test Failed] TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1585:
-
Priority: Blocker  (was: Major)

> [Test Failed] TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine
> ---
>
> Key: IGNITE-1585
> URL: https://issues.apache.org/jira/browse/IGNITE-1585
> Project: Ignite
>  Issue Type: Test
>Affects Versions: ignite-1.5
>Reporter: Anton Vinogradov
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> org.apache.ignite.spi.IgniteSpiException: Failed to get registered addresses 
> for the provider: google-compute-engine
> at 
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:229)
> at 
> org.jclouds.compute.internal.FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.checkGroup(FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.java:124)
> at 
> org.jclouds.compute.internal.FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.sharedNameForGroup(FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.java:120)
> at 
> org.jclouds.googlecomputeengine.compute.functions.FirewallTagNamingConvention$Factory.get(FirewallTagNamingConvention.java:39)
> at 
> org.jclouds.googlecomputeengine.compute.functions.InstanceToNodeMetadata.apply(InstanceToNodeMetadata.java:68)
> at 
> org.jclouds.googlecomputeengine.compute.functions.InstanceToNodeMetadata.apply(InstanceToNodeMetadata.java:43)
> at 
> com.google.common.base.Functions$FunctionComposition.apply(Functions.java:211)
> at com.google.common.collect.Iterators$8.transform(Iterators.java:794)
> at 
> com.google.common.collect.TransformedIterator.next(TransformedIterator.java:48)
> at com.google.common.collect.Iterators$7.computeNext(Iterators.java:646)
> at 
> com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
> at 
> com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
> at com.google.common.collect.Iterators.addAll(Iterators.java:356)
> at com.google.common.collect.Iterables.addAll(Iterables.java:350)
> at com.google.common.collect.Sets.newLinkedHashSet(Sets.java:328)
> at 
> org.jclouds.compute.internal.BaseComputeService.listNodesDetailsMatching(BaseComputeService.java:359)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinder.getRegisteredAddresses(TcpDiscoveryCloudIpFinder.java:190)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testCloudProvider(TcpDiscoveryCloudIpFinderSelfTest.java:106)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine(TcpDiscoveryCloudIpFinderSelfTest.java:71)
> --- Stdout: ---
> Configured log4j from: 
> /opt/TeamcityAgent/work/871ff4a46e450b13/modules/core/src/test/config/log4j-test.xml
> [14:19:49,901][INFO ][main][root] >>> Starting test class: 
> TcpDiscoveryCloudIpFinderSelfTest <<<
> [14:19:49,944][INFO ][main][root] >>> Starting test: testGoogleComputeEngine 
> <<<
> [14:19:49,945][INFO ][test-runner][root] Testing provider: 
> google-compute-engine
> [14:19:52,312][INFO ][main][root] >>> Stopping test: testGoogleComputeEngine 
> in 2367 ms <<<
> --- Stderr: ---
> [14:19:52,310][ERROR][main][root] Test failed.
> class org.apache.ignite.spi.IgniteSpiException: Failed to get registered 
> addresses for the provider: google-compute-engine
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinder.getRegisteredAddresses(TcpDiscoveryCloudIpFinder.java:210)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testCloudProvider(TcpDiscoveryCloudIpFinderSelfTest.java:106)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine(TcpDiscoveryCloudIpFinderSelfTest.java:71)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> Caused by: java.lang.NullPointerException: group
> at 
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:229)

[jira] [Updated] (IGNITE-1584) [Test Failed] IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1584:
-
Affects Version/s: ignite-1.5

> [Test Failed] 
> IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap
> ---
>
> Key: IGNITE-1584
> URL: https://issues.apache.org/jira/browse/IGNITE-1584
> Project: Ignite
>  Issue Type: Test
>Affects Versions: ignite-1.5
>Reporter: Anton Vinogradov
> Fix For: ignite-1.5
>
> Attachments: 
> IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap
>
>




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


[jira] [Updated] (IGNITE-1583) [Test Failed] GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1583:
-
Affects Version/s: ignite-1.5

> [Test Failed] GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient
> -
>
> Key: IGNITE-1583
> URL: https://issues.apache.org/jira/browse/IGNITE-1583
> Project: Ignite
>  Issue Type: Test
>Affects Versions: ignite-1.5
>Reporter: Anton Vinogradov
>Assignee: Semen Boikov
>Priority: Blocker
> Fix For: ignite-1.5
>
> Attachments: GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient
>
>
> See attach for details.



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


[jira] [Updated] (IGNITE-1585) [Test Failed] TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1585:
-
Affects Version/s: ignite-1.5

> [Test Failed] TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine
> ---
>
> Key: IGNITE-1585
> URL: https://issues.apache.org/jira/browse/IGNITE-1585
> Project: Ignite
>  Issue Type: Test
>Affects Versions: ignite-1.5
>Reporter: Anton Vinogradov
> Fix For: ignite-1.5
>
>
> org.apache.ignite.spi.IgniteSpiException: Failed to get registered addresses 
> for the provider: google-compute-engine
> at 
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:229)
> at 
> org.jclouds.compute.internal.FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.checkGroup(FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.java:124)
> at 
> org.jclouds.compute.internal.FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.sharedNameForGroup(FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.java:120)
> at 
> org.jclouds.googlecomputeengine.compute.functions.FirewallTagNamingConvention$Factory.get(FirewallTagNamingConvention.java:39)
> at 
> org.jclouds.googlecomputeengine.compute.functions.InstanceToNodeMetadata.apply(InstanceToNodeMetadata.java:68)
> at 
> org.jclouds.googlecomputeengine.compute.functions.InstanceToNodeMetadata.apply(InstanceToNodeMetadata.java:43)
> at 
> com.google.common.base.Functions$FunctionComposition.apply(Functions.java:211)
> at com.google.common.collect.Iterators$8.transform(Iterators.java:794)
> at 
> com.google.common.collect.TransformedIterator.next(TransformedIterator.java:48)
> at com.google.common.collect.Iterators$7.computeNext(Iterators.java:646)
> at 
> com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
> at 
> com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
> at com.google.common.collect.Iterators.addAll(Iterators.java:356)
> at com.google.common.collect.Iterables.addAll(Iterables.java:350)
> at com.google.common.collect.Sets.newLinkedHashSet(Sets.java:328)
> at 
> org.jclouds.compute.internal.BaseComputeService.listNodesDetailsMatching(BaseComputeService.java:359)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinder.getRegisteredAddresses(TcpDiscoveryCloudIpFinder.java:190)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testCloudProvider(TcpDiscoveryCloudIpFinderSelfTest.java:106)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine(TcpDiscoveryCloudIpFinderSelfTest.java:71)
> --- Stdout: ---
> Configured log4j from: 
> /opt/TeamcityAgent/work/871ff4a46e450b13/modules/core/src/test/config/log4j-test.xml
> [14:19:49,901][INFO ][main][root] >>> Starting test class: 
> TcpDiscoveryCloudIpFinderSelfTest <<<
> [14:19:49,944][INFO ][main][root] >>> Starting test: testGoogleComputeEngine 
> <<<
> [14:19:49,945][INFO ][test-runner][root] Testing provider: 
> google-compute-engine
> [14:19:52,312][INFO ][main][root] >>> Stopping test: testGoogleComputeEngine 
> in 2367 ms <<<
> --- Stderr: ---
> [14:19:52,310][ERROR][main][root] Test failed.
> class org.apache.ignite.spi.IgniteSpiException: Failed to get registered 
> addresses for the provider: google-compute-engine
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinder.getRegisteredAddresses(TcpDiscoveryCloudIpFinder.java:210)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testCloudProvider(TcpDiscoveryCloudIpFinderSelfTest.java:106)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine(TcpDiscoveryCloudIpFinderSelfTest.java:71)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> Caused by: java.lang.NullPointerException: group
> at 
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:229)
> at 
> org.jclouds.compute.

[jira] [Updated] (IGNITE-1582) [Test Failed] GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1582:
-
Priority: Blocker  (was: Major)

> [Test Failed] 
> GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore
> --
>
> Key: IGNITE-1582
> URL: https://issues.apache.org/jira/browse/IGNITE-1582
> Project: Ignite
>  Issue Type: Test
>Affects Versions: ignite-1.5
>Reporter: Anton Vinogradov
>Assignee: Artem Shutak
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> {noformat}
> junit.framework.AssertionFailedError: expected:<-1> but was:<13>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4587)
> at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> --- Stdout: ---
> [14:43:02,405][INFO ][main][root] >>> Starting test: testWithSkipStore <<<
> [14:43:02,473][INFO ][main][root] >>> Stopping test: testWithSkipStore in 67 
> ms <<<
> [14:43:02,473][INFO ][main][root] Checking grid: 0
> [14:43:02,491][INFO ][main][root] Size after [idx=0, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> [14:43:02,494][INFO ][main][root] Checking grid: 1
> [14:43:02,503][INFO ][main][root] Size after [idx=1, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> [14:43:02,505][INFO ][main][root] Checking grid: 2
> [14:43:02,513][INFO ][main][root] Size after [idx=2, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> [14:43:02,514][INFO ][main][root] Checking grid: 3
> [14:43:02,522][INFO ][main][root] Size after [idx=3, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> --- Stderr: ---
> [14:43:02,471][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: expected:<-1> but was:<13>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4587)
> at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> {noformat}
> TC: 
> http://94.72.60.102/viewLog.html?buildId=546197&tab=buildResultsDiv&buildTypeId=Ignite_IgniteCacheFullApi



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


[jira] [Updated] (IGNITE-1582) [Test Failed] GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1582:
-
Affects Version/s: ignite-1.5

> [Test Failed] 
> GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore
> --
>
> Key: IGNITE-1582
> URL: https://issues.apache.org/jira/browse/IGNITE-1582
> Project: Ignite
>  Issue Type: Test
>Affects Versions: ignite-1.5
>Reporter: Anton Vinogradov
>Assignee: Artem Shutak
> Fix For: ignite-1.5
>
>
> {noformat}
> junit.framework.AssertionFailedError: expected:<-1> but was:<13>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4587)
> at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> --- Stdout: ---
> [14:43:02,405][INFO ][main][root] >>> Starting test: testWithSkipStore <<<
> [14:43:02,473][INFO ][main][root] >>> Stopping test: testWithSkipStore in 67 
> ms <<<
> [14:43:02,473][INFO ][main][root] Checking grid: 0
> [14:43:02,491][INFO ][main][root] Size after [idx=0, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> [14:43:02,494][INFO ][main][root] Checking grid: 1
> [14:43:02,503][INFO ][main][root] Size after [idx=1, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> [14:43:02,505][INFO ][main][root] Checking grid: 2
> [14:43:02,513][INFO ][main][root] Size after [idx=2, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> [14:43:02,514][INFO ][main][root] Checking grid: 3
> [14:43:02,522][INFO ][main][root] Size after [idx=3, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> --- Stderr: ---
> [14:43:02,471][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: expected:<-1> but was:<13>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4587)
> at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> {noformat}
> TC: 
> http://94.72.60.102/viewLog.html?buildId=546197&tab=buildResultsDiv&buildTypeId=Ignite_IgniteCacheFullApi



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


[jira] [Updated] (IGNITE-1584) [Test Failed] IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1584:
-
Fix Version/s: ignite-1.5

> [Test Failed] 
> IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap
> ---
>
> Key: IGNITE-1584
> URL: https://issues.apache.org/jira/browse/IGNITE-1584
> Project: Ignite
>  Issue Type: Test
>Affects Versions: ignite-1.5
>Reporter: Anton Vinogradov
> Fix For: ignite-1.5
>
> Attachments: 
> IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap
>
>




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


[jira] [Updated] (IGNITE-1582) [Test Failed] GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1582:
-
Fix Version/s: ignite-1.5

> [Test Failed] 
> GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore
> --
>
> Key: IGNITE-1582
> URL: https://issues.apache.org/jira/browse/IGNITE-1582
> Project: Ignite
>  Issue Type: Test
>Affects Versions: ignite-1.5
>Reporter: Anton Vinogradov
>Assignee: Artem Shutak
> Fix For: ignite-1.5
>
>
> {noformat}
> junit.framework.AssertionFailedError: expected:<-1> but was:<13>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4587)
> at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> --- Stdout: ---
> [14:43:02,405][INFO ][main][root] >>> Starting test: testWithSkipStore <<<
> [14:43:02,473][INFO ][main][root] >>> Stopping test: testWithSkipStore in 67 
> ms <<<
> [14:43:02,473][INFO ][main][root] Checking grid: 0
> [14:43:02,491][INFO ][main][root] Size after [idx=0, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> [14:43:02,494][INFO ][main][root] Checking grid: 1
> [14:43:02,503][INFO ][main][root] Size after [idx=1, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> [14:43:02,505][INFO ][main][root] Checking grid: 2
> [14:43:02,513][INFO ][main][root] Size after [idx=2, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> [14:43:02,514][INFO ][main][root] Checking grid: 3
> [14:43:02,522][INFO ][main][root] Size after [idx=3, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> --- Stderr: ---
> [14:43:02,471][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: expected:<-1> but was:<13>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4587)
> at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> {noformat}
> TC: 
> http://94.72.60.102/viewLog.html?buildId=546197&tab=buildResultsDiv&buildTypeId=Ignite_IgniteCacheFullApi



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


[jira] [Updated] (IGNITE-1583) [Test Failed] GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1583:
-
Priority: Blocker  (was: Major)

> [Test Failed] GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient
> -
>
> Key: IGNITE-1583
> URL: https://issues.apache.org/jira/browse/IGNITE-1583
> Project: Ignite
>  Issue Type: Test
>Affects Versions: ignite-1.5
>Reporter: Anton Vinogradov
>Assignee: Semen Boikov
>Priority: Blocker
> Fix For: ignite-1.5
>
> Attachments: GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient
>
>
> See attach for details.



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


[jira] [Updated] (IGNITE-1583) [Test Failed] GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1583:
-
Fix Version/s: ignite-1.5

> [Test Failed] GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient
> -
>
> Key: IGNITE-1583
> URL: https://issues.apache.org/jira/browse/IGNITE-1583
> Project: Ignite
>  Issue Type: Test
>Affects Versions: ignite-1.5
>Reporter: Anton Vinogradov
>Assignee: Semen Boikov
>Priority: Blocker
> Fix For: ignite-1.5
>
> Attachments: GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient
>
>
> See attach for details.



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


[jira] [Created] (IGNITE-1587) [Test Failed] Timeouted IgniteCacheAtomicNodeRestartTest.* at TC Windows agents

2015-09-30 Thread Anton Vinogradov (JIRA)
Anton Vinogradov created IGNITE-1587:


 Summary: [Test Failed] Timeouted 
IgniteCacheAtomicNodeRestartTest.* at TC Windows agents
 Key: IGNITE-1587
 URL: https://issues.apache.org/jira/browse/IGNITE-1587
 Project: Ignite
  Issue Type: Test
Affects Versions: ignite-1.5
Reporter: Anton Vinogradov
Priority: Blocker
 Fix For: ignite-1.5






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


[jira] [Updated] (IGNITE-1585) [Test Failed] TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1585:
-
Summary: [Test Failed] 
TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine  (was: Test failed - 
TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine)

> [Test Failed] TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine
> ---
>
> Key: IGNITE-1585
> URL: https://issues.apache.org/jira/browse/IGNITE-1585
> Project: Ignite
>  Issue Type: Test
>Reporter: Anton Vinogradov
>
> org.apache.ignite.spi.IgniteSpiException: Failed to get registered addresses 
> for the provider: google-compute-engine
> at 
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:229)
> at 
> org.jclouds.compute.internal.FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.checkGroup(FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.java:124)
> at 
> org.jclouds.compute.internal.FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.sharedNameForGroup(FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.java:120)
> at 
> org.jclouds.googlecomputeengine.compute.functions.FirewallTagNamingConvention$Factory.get(FirewallTagNamingConvention.java:39)
> at 
> org.jclouds.googlecomputeengine.compute.functions.InstanceToNodeMetadata.apply(InstanceToNodeMetadata.java:68)
> at 
> org.jclouds.googlecomputeengine.compute.functions.InstanceToNodeMetadata.apply(InstanceToNodeMetadata.java:43)
> at 
> com.google.common.base.Functions$FunctionComposition.apply(Functions.java:211)
> at com.google.common.collect.Iterators$8.transform(Iterators.java:794)
> at 
> com.google.common.collect.TransformedIterator.next(TransformedIterator.java:48)
> at com.google.common.collect.Iterators$7.computeNext(Iterators.java:646)
> at 
> com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
> at 
> com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
> at com.google.common.collect.Iterators.addAll(Iterators.java:356)
> at com.google.common.collect.Iterables.addAll(Iterables.java:350)
> at com.google.common.collect.Sets.newLinkedHashSet(Sets.java:328)
> at 
> org.jclouds.compute.internal.BaseComputeService.listNodesDetailsMatching(BaseComputeService.java:359)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinder.getRegisteredAddresses(TcpDiscoveryCloudIpFinder.java:190)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testCloudProvider(TcpDiscoveryCloudIpFinderSelfTest.java:106)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine(TcpDiscoveryCloudIpFinderSelfTest.java:71)
> --- Stdout: ---
> Configured log4j from: 
> /opt/TeamcityAgent/work/871ff4a46e450b13/modules/core/src/test/config/log4j-test.xml
> [14:19:49,901][INFO ][main][root] >>> Starting test class: 
> TcpDiscoveryCloudIpFinderSelfTest <<<
> [14:19:49,944][INFO ][main][root] >>> Starting test: testGoogleComputeEngine 
> <<<
> [14:19:49,945][INFO ][test-runner][root] Testing provider: 
> google-compute-engine
> [14:19:52,312][INFO ][main][root] >>> Stopping test: testGoogleComputeEngine 
> in 2367 ms <<<
> --- Stderr: ---
> [14:19:52,310][ERROR][main][root] Test failed.
> class org.apache.ignite.spi.IgniteSpiException: Failed to get registered 
> addresses for the provider: google-compute-engine
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinder.getRegisteredAddresses(TcpDiscoveryCloudIpFinder.java:210)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testCloudProvider(TcpDiscoveryCloudIpFinderSelfTest.java:106)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine(TcpDiscoveryCloudIpFinderSelfTest.java:71)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> Caused by: java.lang.NullPointerException: group
> at 
> com.google.common.base.Preconditions.checkN

[jira] [Updated] (IGNITE-1583) [Test Failed] GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1583:
-
Summary: [Test Failed] 
GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient  (was: Test Failed ( 
GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient ))

> [Test Failed] GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient
> -
>
> Key: IGNITE-1583
> URL: https://issues.apache.org/jira/browse/IGNITE-1583
> Project: Ignite
>  Issue Type: Test
>Reporter: Anton Vinogradov
>Assignee: Semen Boikov
> Attachments: GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient
>
>
> See attach for details.



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


[jira] [Updated] (IGNITE-1586) CPP: Add isValid() method to all proxy-like classes

2015-09-30 Thread Igor (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Igor updated IGNITE-1586:
-
Component/s: interop

> CPP: Add isValid() method to all proxy-like classes
> ---
>
> Key: IGNITE-1586
> URL: https://issues.apache.org/jira/browse/IGNITE-1586
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Igor
>Assignee: Igor
>
> Need to add isValid() methods to proxy-like classes so users can check if 
> they can use an instance.



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


[jira] [Updated] (IGNITE-1582) [Test Failed] GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1582:
-
Summary: [Test Failed] 
GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore
  (was: Test Failed - 
GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore)

> [Test Failed] 
> GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore
> --
>
> Key: IGNITE-1582
> URL: https://issues.apache.org/jira/browse/IGNITE-1582
> Project: Ignite
>  Issue Type: Test
>Reporter: Anton Vinogradov
>Assignee: Artem Shutak
>
> {noformat}
> junit.framework.AssertionFailedError: expected:<-1> but was:<13>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4587)
> at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> --- Stdout: ---
> [14:43:02,405][INFO ][main][root] >>> Starting test: testWithSkipStore <<<
> [14:43:02,473][INFO ][main][root] >>> Stopping test: testWithSkipStore in 67 
> ms <<<
> [14:43:02,473][INFO ][main][root] Checking grid: 0
> [14:43:02,491][INFO ][main][root] Size after [idx=0, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> [14:43:02,494][INFO ][main][root] Checking grid: 1
> [14:43:02,503][INFO ][main][root] Size after [idx=1, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> [14:43:02,505][INFO ][main][root] Checking grid: 2
> [14:43:02,513][INFO ][main][root] Size after [idx=2, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> [14:43:02,514][INFO ][main][root] Checking grid: 3
> [14:43:02,522][INFO ][main][root] Size after [idx=3, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> --- Stderr: ---
> [14:43:02,471][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: expected:<-1> but was:<13>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4587)
> at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> {noformat}
> TC: 
> http://94.72.60.102/viewLog.html?buildId=546197&tab=buildResultsDiv&buildTypeId=Ignite_IgniteCacheFullApi



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


[jira] [Commented] (IGNITE-1564) Cannot recover from org.apache.ignite.IgniteClientDisconnectedException

2015-09-30 Thread Semen Boikov (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936872#comment-14936872
 ] 

Semen Boikov commented on IGNITE-1564:
--

Hi Enrico,

Yes, fix will be included in the next release.

> Cannot recover from org.apache.ignite.IgniteClientDisconnectedException
> ---
>
> Key: IGNITE-1564
> URL: https://issues.apache.org/jira/browse/IGNITE-1564
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: ignite-1.4
>Reporter: Enrico Olivelli
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> Using Apache Ignite 1.4, I get this problem.
> I have two "server" nodes.
> Stop all the server nodes.
> The clients gets "IgniteClientDisconnectedException"
> Restart all the server nodes
> On client I get this error and the client cannot recover from that state.
> client has forceservermode=true
> {code}
> 15-09-29-11-06-28 SEVERE Sep 29, 2015 11:06:28 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Runtime error caught during grid runnable execution: IgniteSpiThread 
> [name=tcp-client-disco-msg-worker-#4%SVILUPPOREF]
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.addClientNode(GridDiscoveryManager.java:338)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onDiscoveryDataReceived(GridCacheProcessor.java:1903)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.onExchange(GridDiscoveryManager.java:659)
>   at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1706)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddedMessage(ClientImpl.java:1625)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1535)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1465)
>   at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {code}
> and 
> {code}
> 15-09-14-11-14-56   SEVERE Sep 14, 2015 11:14:56 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Unexpected exception in listener notification for event: 
> DiscoveryEvent [evtNode=TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], topVer=7, 
> nodeId8=a86f4ae8, msg=Node left: TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], type=NODE_LEFT, 
> tstamp=144096055]
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.futureId(GridNearAtomicUpdateFuture.java:239)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$3.onEvent(GridCacheMvccManager.java:200)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:745)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:730)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:270)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:1740)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:1931)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:1779)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}



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


[jira] [Commented] (IGNITE-888) Web interface to monitoring cluster state.

2015-09-30 Thread Gianfranco Murador (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936871#comment-14936871
 ] 

Gianfranco Murador commented on IGNITE-888:
---

Sergey, I'd like to ask you if this issue is open yet, or It has been resolved 
in previous release. 
Thank you, Gianfranco 

> Web interface to monitoring cluster state.
> --
>
> Key: IGNITE-888
> URL: https://issues.apache.org/jira/browse/IGNITE-888
> Project: Ignite
>  Issue Type: Task
>Reporter: Sergey Evdokimov
>Assignee: Gianfranco Murador
>
> Ignite node should start Jetty server with small web application to 
> monitoring node state.
> Web application should has at least 3 pages:
> 1.) Node information: hardware configuration, metrics, node attributes
> 2.) Cluster state: list of available nodes.
> 3.) Caches: list of caches, SQL console, object browser.
> Web application should be packed as Ignite plugin to avoid reference to jetty 
> from Ignite core.
> Technologies:
> - JSP, JSTL, sitemesh
> - Bootstrap, Google Charts



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


[jira] [Updated] (IGNITE-1586) CPP: Add isValid() method to all proxy-like classes

2015-09-30 Thread Igor (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Igor updated IGNITE-1586:
-
Affects Version/s: 1.1.4

> CPP: Add isValid() method to all proxy-like classes
> ---
>
> Key: IGNITE-1586
> URL: https://issues.apache.org/jira/browse/IGNITE-1586
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Igor
>Assignee: Igor
>
> Need to add isValid() methods to proxy-like classes so users can check if 
> they can use an instance.



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


[jira] [Created] (IGNITE-1586) CPP: Add isValid() method to all proxy-like classes

2015-09-30 Thread Igor (JIRA)
Igor created IGNITE-1586:


 Summary: CPP: Add isValid() method to all proxy-like classes
 Key: IGNITE-1586
 URL: https://issues.apache.org/jira/browse/IGNITE-1586
 Project: Ignite
  Issue Type: Task
Reporter: Igor
Assignee: Igor


Need to add isValid() methods to proxy-like classes so users can check if they 
can use an instance.



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


[jira] [Updated] (IGNITE-1582) Test Failed - GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1582:
-
Issue Type: Test  (was: Bug)

> Test Failed - 
> GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore
> --
>
> Key: IGNITE-1582
> URL: https://issues.apache.org/jira/browse/IGNITE-1582
> Project: Ignite
>  Issue Type: Test
>Reporter: Anton Vinogradov
>Assignee: Artem Shutak
>
> {noformat}
> junit.framework.AssertionFailedError: expected:<-1> but was:<13>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4587)
> at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> --- Stdout: ---
> [14:43:02,405][INFO ][main][root] >>> Starting test: testWithSkipStore <<<
> [14:43:02,473][INFO ][main][root] >>> Stopping test: testWithSkipStore in 67 
> ms <<<
> [14:43:02,473][INFO ][main][root] Checking grid: 0
> [14:43:02,491][INFO ][main][root] Size after [idx=0, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> [14:43:02,494][INFO ][main][root] Checking grid: 1
> [14:43:02,503][INFO ][main][root] Size after [idx=1, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> [14:43:02,505][INFO ][main][root] Checking grid: 2
> [14:43:02,513][INFO ][main][root] Size after [idx=2, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> [14:43:02,514][INFO ][main][root] Checking grid: 3
> [14:43:02,522][INFO ][main][root] Size after [idx=3, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> --- Stderr: ---
> [14:43:02,471][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: expected:<-1> but was:<13>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4587)
> at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> {noformat}
> TC: 
> http://94.72.60.102/viewLog.html?buildId=546197&tab=buildResultsDiv&buildTypeId=Ignite_IgniteCacheFullApi



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


[jira] [Updated] (IGNITE-1583) Test Failed ( GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient )

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1583:
-
Issue Type: Test  (was: Bug)

> Test Failed ( GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient )
> ---
>
> Key: IGNITE-1583
> URL: https://issues.apache.org/jira/browse/IGNITE-1583
> Project: Ignite
>  Issue Type: Test
>Reporter: Anton Vinogradov
>Assignee: Semen Boikov
> Attachments: GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient
>
>
> See attach for details.



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


[jira] [Assigned] (IGNITE-1460) CPP: Review all "const" usages on public API.

2015-09-30 Thread Igor (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Igor reassigned IGNITE-1460:


Assignee: Igor

> CPP: Review all "const" usages on public API.
> -
>
> Key: IGNITE-1460
> URL: https://issues.apache.org/jira/browse/IGNITE-1460
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Igor
> Fix For: ignite-1.5
>
>
> Need to make sure that all semantically constant parameters is really "const".



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


[jira] [Updated] (IGNITE-1584) [Test Failed] IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1584:
-
Summary: [Test Failed] 
IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap
  (was: Test Failed - 
IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap)

> [Test Failed] 
> IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap
> ---
>
> Key: IGNITE-1584
> URL: https://issues.apache.org/jira/browse/IGNITE-1584
> Project: Ignite
>  Issue Type: Test
>Reporter: Anton Vinogradov
> Attachments: 
> IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap
>
>




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


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

2015-09-30 Thread Andrey Gura (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936811#comment-14936811
 ] 

Andrey Gura edited comment on IGNITE-1526 at 9/30/15 1:52 PM:
--

>From my point of view {{OptimizedMarshaller}} should work correctly in case of 
>JVMs from different vendors and should be fixed.


was (Author: agura):
>From my point of view {{OptimizedMarshaller}} should works correctly in case 
>of JVMs from different vendors and should be fixed.

> 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: Andrey Gura
>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
> 

[jira] [Updated] (IGNITE-1585) Test failed - TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1585:
-
Issue Type: Test  (was: Bug)

> Test failed - TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine
> ---
>
> Key: IGNITE-1585
> URL: https://issues.apache.org/jira/browse/IGNITE-1585
> Project: Ignite
>  Issue Type: Test
>Reporter: Anton Vinogradov
>
> org.apache.ignite.spi.IgniteSpiException: Failed to get registered addresses 
> for the provider: google-compute-engine
> at 
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:229)
> at 
> org.jclouds.compute.internal.FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.checkGroup(FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.java:124)
> at 
> org.jclouds.compute.internal.FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.sharedNameForGroup(FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.java:120)
> at 
> org.jclouds.googlecomputeengine.compute.functions.FirewallTagNamingConvention$Factory.get(FirewallTagNamingConvention.java:39)
> at 
> org.jclouds.googlecomputeengine.compute.functions.InstanceToNodeMetadata.apply(InstanceToNodeMetadata.java:68)
> at 
> org.jclouds.googlecomputeengine.compute.functions.InstanceToNodeMetadata.apply(InstanceToNodeMetadata.java:43)
> at 
> com.google.common.base.Functions$FunctionComposition.apply(Functions.java:211)
> at com.google.common.collect.Iterators$8.transform(Iterators.java:794)
> at 
> com.google.common.collect.TransformedIterator.next(TransformedIterator.java:48)
> at com.google.common.collect.Iterators$7.computeNext(Iterators.java:646)
> at 
> com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
> at 
> com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
> at com.google.common.collect.Iterators.addAll(Iterators.java:356)
> at com.google.common.collect.Iterables.addAll(Iterables.java:350)
> at com.google.common.collect.Sets.newLinkedHashSet(Sets.java:328)
> at 
> org.jclouds.compute.internal.BaseComputeService.listNodesDetailsMatching(BaseComputeService.java:359)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinder.getRegisteredAddresses(TcpDiscoveryCloudIpFinder.java:190)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testCloudProvider(TcpDiscoveryCloudIpFinderSelfTest.java:106)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine(TcpDiscoveryCloudIpFinderSelfTest.java:71)
> --- Stdout: ---
> Configured log4j from: 
> /opt/TeamcityAgent/work/871ff4a46e450b13/modules/core/src/test/config/log4j-test.xml
> [14:19:49,901][INFO ][main][root] >>> Starting test class: 
> TcpDiscoveryCloudIpFinderSelfTest <<<
> [14:19:49,944][INFO ][main][root] >>> Starting test: testGoogleComputeEngine 
> <<<
> [14:19:49,945][INFO ][test-runner][root] Testing provider: 
> google-compute-engine
> [14:19:52,312][INFO ][main][root] >>> Stopping test: testGoogleComputeEngine 
> in 2367 ms <<<
> --- Stderr: ---
> [14:19:52,310][ERROR][main][root] Test failed.
> class org.apache.ignite.spi.IgniteSpiException: Failed to get registered 
> addresses for the provider: google-compute-engine
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinder.getRegisteredAddresses(TcpDiscoveryCloudIpFinder.java:210)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testCloudProvider(TcpDiscoveryCloudIpFinderSelfTest.java:106)
> at 
> org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine(TcpDiscoveryCloudIpFinderSelfTest.java:71)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> Caused by: java.lang.NullPointerException: group
> at 
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:229)
> at 
> org.jclouds.compute.internal.FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.check

[jira] [Updated] (IGNITE-1584) Test Failed - IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1584:
-
Issue Type: Test  (was: Bug)

> Test Failed - 
> IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap
> ---
>
> Key: IGNITE-1584
> URL: https://issues.apache.org/jira/browse/IGNITE-1584
> Project: Ignite
>  Issue Type: Test
>Reporter: Anton Vinogradov
> Attachments: 
> IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap
>
>




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


[jira] [Commented] (IGNITE-1580) CPP: Review Ignition interface.

2015-09-30 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936861#comment-14936861
 ] 

ASF GitHub Bot commented on IGNITE-1580:


GitHub user isapego opened a pull request:

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

IGNITE-1580: const qualifiers removed for bool arguments



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/isapego/ignite ignite-1580

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/116.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #116


commit ad217b358e7fe48cd06a746a8a47379cca4669ed
Author: isapego 
Date:   2015-09-30T13:51:01Z

IGNITE-1580: const qualifiers removed for bool arguments




> CPP: Review Ignition interface.
> ---
>
> Key: IGNITE-1580
> URL: https://issues.apache.org/jira/browse/IGNITE-1580
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Igor
>Priority: Critical
> Fix For: ignite-1.5
>
>
> It is necessary to review Ignition interface and understand whether it is 
> compliant with common CPP practices. 



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


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

2015-09-30 Thread Vladimir Ozerov (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936859#comment-14936859
 ] 

Vladimir Ozerov commented on IGNITE-1526:
-

Agree. What is the problem of making OptimizedMarshaller work?

> 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: Andrey Gura
>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 
> ja

[jira] [Created] (IGNITE-1585) Test failed - TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine

2015-09-30 Thread Anton Vinogradov (JIRA)
Anton Vinogradov created IGNITE-1585:


 Summary: Test failed - 
TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine
 Key: IGNITE-1585
 URL: https://issues.apache.org/jira/browse/IGNITE-1585
 Project: Ignite
  Issue Type: Bug
Reporter: Anton Vinogradov


org.apache.ignite.spi.IgniteSpiException: Failed to get registered addresses 
for the provider: google-compute-engine
at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:229)
at 
org.jclouds.compute.internal.FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.checkGroup(FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.java:124)
at 
org.jclouds.compute.internal.FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.sharedNameForGroup(FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.java:120)
at 
org.jclouds.googlecomputeengine.compute.functions.FirewallTagNamingConvention$Factory.get(FirewallTagNamingConvention.java:39)
at 
org.jclouds.googlecomputeengine.compute.functions.InstanceToNodeMetadata.apply(InstanceToNodeMetadata.java:68)
at 
org.jclouds.googlecomputeengine.compute.functions.InstanceToNodeMetadata.apply(InstanceToNodeMetadata.java:43)
at 
com.google.common.base.Functions$FunctionComposition.apply(Functions.java:211)
at com.google.common.collect.Iterators$8.transform(Iterators.java:794)
at 
com.google.common.collect.TransformedIterator.next(TransformedIterator.java:48)
at com.google.common.collect.Iterators$7.computeNext(Iterators.java:646)
at 
com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
at 
com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
at com.google.common.collect.Iterators.addAll(Iterators.java:356)
at com.google.common.collect.Iterables.addAll(Iterables.java:350)
at com.google.common.collect.Sets.newLinkedHashSet(Sets.java:328)
at 
org.jclouds.compute.internal.BaseComputeService.listNodesDetailsMatching(BaseComputeService.java:359)
at 
org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinder.getRegisteredAddresses(TcpDiscoveryCloudIpFinder.java:190)
at 
org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testCloudProvider(TcpDiscoveryCloudIpFinderSelfTest.java:106)
at 
org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine(TcpDiscoveryCloudIpFinderSelfTest.java:71)
--- Stdout: ---
Configured log4j from: 
/opt/TeamcityAgent/work/871ff4a46e450b13/modules/core/src/test/config/log4j-test.xml
[14:19:49,901][INFO ][main][root] >>> Starting test class: 
TcpDiscoveryCloudIpFinderSelfTest <<<
[14:19:49,944][INFO ][main][root] >>> Starting test: testGoogleComputeEngine <<<
[14:19:49,945][INFO ][test-runner][root] Testing provider: google-compute-engine
[14:19:52,312][INFO ][main][root] >>> Stopping test: testGoogleComputeEngine in 
2367 ms <<<
--- Stderr: ---
[14:19:52,310][ERROR][main][root] Test failed.
class org.apache.ignite.spi.IgniteSpiException: Failed to get registered 
addresses for the provider: google-compute-engine
at 
org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinder.getRegisteredAddresses(TcpDiscoveryCloudIpFinder.java:210)
at 
org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testCloudProvider(TcpDiscoveryCloudIpFinderSelfTest.java:106)
at 
org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine(TcpDiscoveryCloudIpFinderSelfTest.java:71)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
Caused by: java.lang.NullPointerException: group
at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:229)
at 
org.jclouds.compute.internal.FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.checkGroup(FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.java:124)
at 
org.jclouds.compute.internal.FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.sharedNameForGroup(FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.java:120)
at 
org.jclouds.googlecomputeengine.compute.functions.FirewallTagNamingConvention$Factory.get(FirewallTagNamingConv

[jira] [Commented] (IGNITE-1580) CPP: Review Ignition interface.

2015-09-30 Thread Vladimir Ozerov (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936819#comment-14936819
 ] 

Vladimir Ozerov commented on IGNITE-1580:
-

Lets remove consts from "cancel" flag in scope of this ticket and handle other 
mentioned problems in other tickets.

> CPP: Review Ignition interface.
> ---
>
> Key: IGNITE-1580
> URL: https://issues.apache.org/jira/browse/IGNITE-1580
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Igor
>Priority: Critical
> Fix For: ignite-1.5
>
>
> It is necessary to review Ignition interface and understand whether it is 
> compliant with common CPP practices. 



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


[jira] [Commented] (IGNITE-1564) Cannot recover from org.apache.ignite.IgniteClientDisconnectedException

2015-09-30 Thread Enrico Olivelli (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936817#comment-14936817
 ] 

Enrico Olivelli commented on IGNITE-1564:
-

Thank you
Do you think that this fix will be included in a 1.4.1 release ? 

> Cannot recover from org.apache.ignite.IgniteClientDisconnectedException
> ---
>
> Key: IGNITE-1564
> URL: https://issues.apache.org/jira/browse/IGNITE-1564
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: ignite-1.4
>Reporter: Enrico Olivelli
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> Using Apache Ignite 1.4, I get this problem.
> I have two "server" nodes.
> Stop all the server nodes.
> The clients gets "IgniteClientDisconnectedException"
> Restart all the server nodes
> On client I get this error and the client cannot recover from that state.
> client has forceservermode=true
> {code}
> 15-09-29-11-06-28 SEVERE Sep 29, 2015 11:06:28 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Runtime error caught during grid runnable execution: IgniteSpiThread 
> [name=tcp-client-disco-msg-worker-#4%SVILUPPOREF]
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.addClientNode(GridDiscoveryManager.java:338)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onDiscoveryDataReceived(GridCacheProcessor.java:1903)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.onExchange(GridDiscoveryManager.java:659)
>   at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1706)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddedMessage(ClientImpl.java:1625)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1535)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1465)
>   at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {code}
> and 
> {code}
> 15-09-14-11-14-56   SEVERE Sep 14, 2015 11:14:56 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Unexpected exception in listener notification for event: 
> DiscoveryEvent [evtNode=TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], topVer=7, 
> nodeId8=a86f4ae8, msg=Node left: TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], type=NODE_LEFT, 
> tstamp=144096055]
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.futureId(GridNearAtomicUpdateFuture.java:239)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$3.onEvent(GridCacheMvccManager.java:200)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:745)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:730)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:270)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:1740)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:1931)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:1779)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}



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


[jira] [Updated] (IGNITE-1584) Test Failed - IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1584:
-
Attachment: 
IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap

> Test Failed - 
> IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap
> ---
>
> Key: IGNITE-1584
> URL: https://issues.apache.org/jira/browse/IGNITE-1584
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
> Attachments: 
> IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap
>
>




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


[jira] [Created] (IGNITE-1584) Test Failed - IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap

2015-09-30 Thread Anton Vinogradov (JIRA)
Anton Vinogradov created IGNITE-1584:


 Summary: Test Failed - 
IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap
 Key: IGNITE-1584
 URL: https://issues.apache.org/jira/browse/IGNITE-1584
 Project: Ignite
  Issue Type: Bug
Reporter: Anton Vinogradov






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


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

2015-09-30 Thread Andrey Gura (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936811#comment-14936811
 ] 

Andrey Gura commented on IGNITE-1526:
-

>From my point of view {{OptimizedMarshaller}} should works correctly in case 
>of JVMs from different vendors and should be fixed.

> 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: Andrey Gura
>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.

[jira] [Commented] (IGNITE-1582) Test Failed - GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore

2015-09-30 Thread Artem Shutak (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936808#comment-14936808
 ] 

Artem Shutak commented on IGNITE-1582:
--

Test fails from time to time. Can't reproduce locally. Will analyze the 
stacktrace.

> Test Failed - 
> GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore
> --
>
> Key: IGNITE-1582
> URL: https://issues.apache.org/jira/browse/IGNITE-1582
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Artem Shutak
>
> {noformat}
> junit.framework.AssertionFailedError: expected:<-1> but was:<13>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4587)
> at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> --- Stdout: ---
> [14:43:02,405][INFO ][main][root] >>> Starting test: testWithSkipStore <<<
> [14:43:02,473][INFO ][main][root] >>> Stopping test: testWithSkipStore in 67 
> ms <<<
> [14:43:02,473][INFO ][main][root] Checking grid: 0
> [14:43:02,491][INFO ][main][root] Size after [idx=0, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> [14:43:02,494][INFO ][main][root] Checking grid: 1
> [14:43:02,503][INFO ][main][root] Size after [idx=1, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> [14:43:02,505][INFO ][main][root] Checking grid: 2
> [14:43:02,513][INFO ][main][root] Size after [idx=2, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> [14:43:02,514][INFO ][main][root] Checking grid: 3
> [14:43:02,522][INFO ][main][root] Size after [idx=3, size=0, keySize=0, 
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries 
> []]
> --- Stderr: ---
> [14:43:02,471][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: expected:<-1> but was:<13>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4587)
> at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> {noformat}
> TC: 
> http://94.72.60.102/viewLog.html?buildId=546197&tab=buildResultsDiv&buildTypeId=Ignite_IgniteCacheFullApi



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


[jira] [Updated] (IGNITE-1583) Test Failed ( GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient )

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1583:
-
Description: See attach for details.  (was: TC: 
http://94.72.60.102/viewLog.html?buildId=546150&tab=buildResultsDiv&buildTypeId=Ignite_Basic)

> Test Failed ( GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient )
> ---
>
> Key: IGNITE-1583
> URL: https://issues.apache.org/jira/browse/IGNITE-1583
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Semen Boikov
> Attachments: GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient
>
>
> See attach for details.



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


[jira] [Updated] (IGNITE-1583) Test Failed ( GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient )

2015-09-30 Thread Anton Vinogradov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-1583:
-
Attachment: GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient

> Test Failed ( GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient )
> ---
>
> Key: IGNITE-1583
> URL: https://issues.apache.org/jira/browse/IGNITE-1583
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Semen Boikov
> Attachments: GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient
>
>
> TC: 
> http://94.72.60.102/viewLog.html?buildId=546150&tab=buildResultsDiv&buildTypeId=Ignite_Basic



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


[jira] [Created] (IGNITE-1583) Test Failed ( GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient )

2015-09-30 Thread Anton Vinogradov (JIRA)
Anton Vinogradov created IGNITE-1583:


 Summary: Test Failed ( 
GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient )
 Key: IGNITE-1583
 URL: https://issues.apache.org/jira/browse/IGNITE-1583
 Project: Ignite
  Issue Type: Bug
Reporter: Anton Vinogradov
Assignee: Semen Boikov


TC: 
http://94.72.60.102/viewLog.html?buildId=546150&tab=buildResultsDiv&buildTypeId=Ignite_Basic



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


[jira] [Updated] (IGNITE-1582) Test Failed - GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore

2015-09-30 Thread Artem Shutak (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Artem Shutak updated IGNITE-1582:
-
Description: 
{noformat}
junit.framework.AssertionFailedError: expected:<-1> but was:<13>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:86)
at junit.framework.TestCase.assertEquals(TestCase.java:253)
at 
org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4587)
at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
--- Stdout: ---
[14:43:02,405][INFO ][main][root] >>> Starting test: testWithSkipStore <<<
[14:43:02,473][INFO ][main][root] >>> Stopping test: testWithSkipStore in 67 ms 
<<<
[14:43:02,473][INFO ][main][root] Checking grid: 0
[14:43:02,491][INFO ][main][root] Size after [idx=0, size=0, keySize=0, 
primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries []]
[14:43:02,494][INFO ][main][root] Checking grid: 1
[14:43:02,503][INFO ][main][root] Size after [idx=1, size=0, keySize=0, 
primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries []]
[14:43:02,505][INFO ][main][root] Checking grid: 2
[14:43:02,513][INFO ][main][root] Size after [idx=2, size=0, keySize=0, 
primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries []]
[14:43:02,514][INFO ][main][root] Checking grid: 3
[14:43:02,522][INFO ][main][root] Size after [idx=3, size=0, keySize=0, 
primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries []]
--- Stderr: ---
[14:43:02,471][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError: expected:<-1> but was:<13>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:86)
at junit.framework.TestCase.assertEquals(TestCase.java:253)
at 
org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4587)
at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
{noformat}

TC: 
http://94.72.60.102/viewLog.html?buildId=546197&tab=buildResultsDiv&buildTypeId=Ignite_IgniteCacheFullApi

  was:
junit.framework.AssertionFailedError: expected:<-1> but was:<13>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:86)
at junit.framework.TestCase.assertEquals(TestCase.java:253)
at 
org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4587)
at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
--- Stdout: ---
[14:43:02,405][INFO ][main][root] >>> Starting test: testWithSkipStore <<<
[14:43:02,473][INFO ][main][root] >>> Stopping test: testWithSkipStore in 67 ms 
<<<
[14:43:02,473][INFO ][main][root] Checking grid: 0
[14:43:02,491][INFO ][main][root] Size after [idx=0, siz

[jira] [Created] (IGNITE-1582) Test Failed - GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore

2015-09-30 Thread Anton Vinogradov (JIRA)
Anton Vinogradov created IGNITE-1582:


 Summary: Test Failed - 
GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore
 Key: IGNITE-1582
 URL: https://issues.apache.org/jira/browse/IGNITE-1582
 Project: Ignite
  Issue Type: Bug
Reporter: Anton Vinogradov
Assignee: Artem Shutak


junit.framework.AssertionFailedError: expected:<-1> but was:<13>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:86)
at junit.framework.TestCase.assertEquals(TestCase.java:253)
at 
org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4587)
at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
--- Stdout: ---
[14:43:02,405][INFO ][main][root] >>> Starting test: testWithSkipStore <<<
[14:43:02,473][INFO ][main][root] >>> Stopping test: testWithSkipStore in 67 ms 
<<<
[14:43:02,473][INFO ][main][root] Checking grid: 0
[14:43:02,491][INFO ][main][root] Size after [idx=0, size=0, keySize=0, 
primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries []]
[14:43:02,494][INFO ][main][root] Checking grid: 1
[14:43:02,503][INFO ][main][root] Size after [idx=1, size=0, keySize=0, 
primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries []]
[14:43:02,505][INFO ][main][root] Checking grid: 2
[14:43:02,513][INFO ][main][root] Size after [idx=2, size=0, keySize=0, 
primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries []]
[14:43:02,514][INFO ][main][root] Checking grid: 3
[14:43:02,522][INFO ][main][root] Size after [idx=3, size=0, keySize=0, 
primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries []]
--- Stderr: ---
[14:43:02,471][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError: expected:<-1> but was:<13>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:86)
at junit.framework.TestCase.assertEquals(TestCase.java:253)
at 
org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4587)
at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)


TC: 
http://94.72.60.102/viewLog.html?buildId=546197&tab=buildResultsDiv&buildTypeId=Ignite_IgniteCacheFullApi



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


[jira] [Commented] (IGNITE-1580) CPP: Review Ignition interface.

2015-09-30 Thread Igor (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936797#comment-14936797
 ] 

Igor commented on IGNITE-1580:
--

1. Why threre is {{std::string}} used in one part of API (i.e. {{SqlQuery}} 
class) when there is {{const char*}} used in other parts (i.e. {{Ignition}} 
class)?
2. According to description of methods {{Get()}} and {{Start()}} they return 
null in case of error. But these methods return Ignite class instances, not 
pointers and only pointers in C++ can be null. So currently you can't check if 
the returned Ignite instance is valid.
3. It is not necessary to annotate {{cancel}} argument of {{Stop()}} method 
with {{const}} qualifier because it's passed by value.

> CPP: Review Ignition interface.
> ---
>
> Key: IGNITE-1580
> URL: https://issues.apache.org/jira/browse/IGNITE-1580
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Igor
>Priority: Critical
> Fix For: ignite-1.5
>
>
> It is necessary to review Ignition interface and understand whether it is 
> compliant with common CPP practices. 



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


[jira] [Updated] (IGNITE-1581) Synchronous cache operation can deadlock on async semaphore.

2015-09-30 Thread Vladimir Ozerov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-1581:

Issue Type: Sub-task  (was: Task)
Parent: IGNITE-1334

> Synchronous cache operation can deadlock on async semaphore.
> 
>
> Key: IGNITE-1581
> URL: https://issues.apache.org/jira/browse/IGNITE-1581
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
> Fix For: ignite-1.5
>
>
> Problem can be reproduced as follows:
> 1) Set CacheConfiguration.setMaxConcurrentAsyncOperations() to a very small 
> value, e.g. 3.
> 2) T1: Start PESSIMISTIC/REPEATABLE_READ tx and call Cache.get(1);
> 3) Start 3 other threads, initiate PESSIMISTIC/REPEATABLE_READ tx and call 
> Cache.get(1) on them. They will stuck as expected.
> 4) T1: Call Cache.get(1) again. Instead of getting already locked value, 
> thread is stuck on async semaphore acquire:
> {code}
> at sun.misc.Unsafe.park(Unsafe.java:-1)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> at java.util.concurrent.Semaphore.acquire(Semaphore.java:317)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOpAcquire(GridCacheAdapter.java:4329)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4203)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAllAsync(GridDhtColocatedCache.java:211)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.getAllAsync(GridCacheAdapter.java:4609)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4556)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1569)
> {code}



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


[jira] [Assigned] (IGNITE-1581) Synchronous cache operation can deadlock on async semaphore.

2015-09-30 Thread Semen Boikov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov reassigned IGNITE-1581:


Assignee: Semen Boikov

> Synchronous cache operation can deadlock on async semaphore.
> 
>
> Key: IGNITE-1581
> URL: https://issues.apache.org/jira/browse/IGNITE-1581
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: ignite-1.5
>
>
> Problem can be reproduced as follows:
> 1) Set CacheConfiguration.setMaxConcurrentAsyncOperations() to a very small 
> value, e.g. 3.
> 2) T1: Start PESSIMISTIC/REPEATABLE_READ tx and call Cache.get(1);
> 3) Start 3 other threads, initiate PESSIMISTIC/REPEATABLE_READ tx and call 
> Cache.get(1) on them. They will stuck as expected.
> 4) T1: Call Cache.get(1) again. Instead of getting already locked value, 
> thread is stuck on async semaphore acquire:
> {code}
> at sun.misc.Unsafe.park(Unsafe.java:-1)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> at java.util.concurrent.Semaphore.acquire(Semaphore.java:317)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOpAcquire(GridCacheAdapter.java:4329)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4203)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAllAsync(GridDhtColocatedCache.java:211)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.getAllAsync(GridCacheAdapter.java:4609)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4556)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1569)
> {code}



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


[jira] [Created] (IGNITE-1581) Synchronous cache operation can deadlock on async semaphore.

2015-09-30 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-1581:
---

 Summary: Synchronous cache operation can deadlock on async 
semaphore.
 Key: IGNITE-1581
 URL: https://issues.apache.org/jira/browse/IGNITE-1581
 Project: Ignite
  Issue Type: Task
  Components: cache
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: ignite-1.5


Problem can be reproduced as follows:
1) Set CacheConfiguration.setMaxConcurrentAsyncOperations() to a very small 
value, e.g. 3.
2) T1: Start PESSIMISTIC/REPEATABLE_READ tx and call Cache.get(1);
3) Start 3 other threads, initiate PESSIMISTIC/REPEATABLE_READ tx and call 
Cache.get(1) on them. They will stuck as expected.
4) T1: Call Cache.get(1) again. Instead of getting already locked value, thread 
is stuck on async semaphore acquire:

{code}
at sun.misc.Unsafe.park(Unsafe.java:-1)
  at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
  at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
  at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
  at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
  at java.util.concurrent.Semaphore.acquire(Semaphore.java:317)
  at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOpAcquire(GridCacheAdapter.java:4329)
  at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4203)
  at 
org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAllAsync(GridDhtColocatedCache.java:211)
  at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.getAllAsync(GridCacheAdapter.java:4609)
  at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4556)
  at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1569)
{code}



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


[jira] [Commented] (IGNITE-1573) IGFS: mkdirs operations should be truly thread-safe

2015-09-30 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936742#comment-14936742
 ] 

ASF GitHub Bot commented on IGNITE-1573:


GitHub user iveselovskiy opened a pull request:

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

IGNITE-1573: mkdirs concurrency fixed.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/iveselovskiy/ignite ignite-1573

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/115.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #115


commit a1208cdef23ea4e81f78c99b84d19731d9ec4261
Author: iveselovskiy 
Date:   2015-09-30T10:56:06Z

IGNITE-1573: mkdirs concurrency fixed.




> IGFS: mkdirs operations should be truly thread-safe
> ---
>
> Key: IGNITE-1573
> URL: https://issues.apache.org/jira/browse/IGNITE-1573
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: ignite-1.4
>Reporter: Ivan Veselovsky
>Assignee: Ivan Veselovsky
> Fix For: ignite-1.5
>
>
> Need to lock all the existing parents and try to add the missing path in one 
> transaction.
> If failed due to concurrent creation, retry from the beginning.



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


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

2015-09-30 Thread Denis Magda (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936738#comment-14936738
 ] 

Denis Magda edited comment on IGNITE-1526 at 9/30/15 11:39 AM:
---

+1 to Vladimir suggestion.

In regards to {{OptimizedMarshaller}} we shouldn't rely on it in the 
heterogeneous scenario. That's why we can leave it's implementation as is.

In the heterogeneous scenario the user will use {{PortableMarshaller}}. 
{{JdkMarshaller}} will be used for the rest of core modules.


was (Author: dmagda):
+1 to Vladimir suggestion.

In regards to {{OptimizedMarshaller}} we shouldn't rely on it in the 
heterogeneous scenario. That's why we can live it's implementation as is.

In the heterogeneous scenario the user will use {{PortableMarshaller}}. 
{{JdkMarshaller}} will be used for the rest of core modules.

> 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: Andrey Gura
>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

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

2015-09-30 Thread Denis Magda (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936738#comment-14936738
 ] 

Denis Magda commented on IGNITE-1526:
-

+1 to Vladimir suggestion.

In regards to {{OptimizedMarshaller}} we shouldn't rely on it in the 
heterogeneous scenario. That's why we can live it's implementation as is.

In the heterogeneous scenario the user will use {{PortableMarshaller}}. 
{{JdkMarshaller}} will be used for the rest of core modules.

> 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: Andrey Gura
>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

[jira] [Closed] (IGNITE-1564) Cannot recover from org.apache.ignite.IgniteClientDisconnectedException

2015-09-30 Thread Semen Boikov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov closed IGNITE-1564.

Assignee: (was: Semen Boikov)

> Cannot recover from org.apache.ignite.IgniteClientDisconnectedException
> ---
>
> Key: IGNITE-1564
> URL: https://issues.apache.org/jira/browse/IGNITE-1564
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: ignite-1.4
>Reporter: Enrico Olivelli
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> Using Apache Ignite 1.4, I get this problem.
> I have two "server" nodes.
> Stop all the server nodes.
> The clients gets "IgniteClientDisconnectedException"
> Restart all the server nodes
> On client I get this error and the client cannot recover from that state.
> client has forceservermode=true
> {code}
> 15-09-29-11-06-28 SEVERE Sep 29, 2015 11:06:28 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Runtime error caught during grid runnable execution: IgniteSpiThread 
> [name=tcp-client-disco-msg-worker-#4%SVILUPPOREF]
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.addClientNode(GridDiscoveryManager.java:338)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onDiscoveryDataReceived(GridCacheProcessor.java:1903)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.onExchange(GridDiscoveryManager.java:659)
>   at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1706)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddedMessage(ClientImpl.java:1625)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1535)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1465)
>   at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {code}
> and 
> {code}
> 15-09-14-11-14-56   SEVERE Sep 14, 2015 11:14:56 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Unexpected exception in listener notification for event: 
> DiscoveryEvent [evtNode=TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], topVer=7, 
> nodeId8=a86f4ae8, msg=Node left: TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], type=NODE_LEFT, 
> tstamp=144096055]
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.futureId(GridNearAtomicUpdateFuture.java:239)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$3.onEvent(GridCacheMvccManager.java:200)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:745)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:730)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:270)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:1740)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:1931)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:1779)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}



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


[jira] [Resolved] (IGNITE-1564) Cannot recover from org.apache.ignite.IgniteClientDisconnectedException

2015-09-30 Thread Semen Boikov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov resolved IGNITE-1564.
--
Resolution: Fixed

Fix is merged into master.

> Cannot recover from org.apache.ignite.IgniteClientDisconnectedException
> ---
>
> Key: IGNITE-1564
> URL: https://issues.apache.org/jira/browse/IGNITE-1564
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: ignite-1.4
>Reporter: Enrico Olivelli
>Assignee: Semen Boikov
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> Using Apache Ignite 1.4, I get this problem.
> I have two "server" nodes.
> Stop all the server nodes.
> The clients gets "IgniteClientDisconnectedException"
> Restart all the server nodes
> On client I get this error and the client cannot recover from that state.
> client has forceservermode=true
> {code}
> 15-09-29-11-06-28 SEVERE Sep 29, 2015 11:06:28 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Runtime error caught during grid runnable execution: IgniteSpiThread 
> [name=tcp-client-disco-msg-worker-#4%SVILUPPOREF]
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.addClientNode(GridDiscoveryManager.java:338)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onDiscoveryDataReceived(GridCacheProcessor.java:1903)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.onExchange(GridDiscoveryManager.java:659)
>   at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1706)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddedMessage(ClientImpl.java:1625)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1535)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1465)
>   at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {code}
> and 
> {code}
> 15-09-14-11-14-56   SEVERE Sep 14, 2015 11:14:56 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Unexpected exception in listener notification for event: 
> DiscoveryEvent [evtNode=TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], topVer=7, 
> nodeId8=a86f4ae8, msg=Node left: TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], type=NODE_LEFT, 
> tstamp=144096055]
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.futureId(GridNearAtomicUpdateFuture.java:239)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$3.onEvent(GridCacheMvccManager.java:200)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:745)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:730)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:270)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:1740)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:1931)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:1779)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}



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


[jira] [Comment Edited] (IGNITE-1559) Need to improve tests, javadoc and documentation of UriDeploymentHttpScanner.

2015-09-30 Thread Artem Shutak (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936699#comment-14936699
 ] 

Artem Shutak edited comment on IGNITE-1559 at 9/30/15 10:49 AM:


Updated both: readme.io and javadocs.

Readme.io has been updated according to Yakov comments at email (see below). 
Please, review "Code example" part again.

>From Yakov's email:
---
1. SPI parameters explanations and code example should be before scanners
(scanner is SPI config as well, just more detailed info)
2. code example should include all scanners + add spring configuration
example
3.
>> quot
Http Uri Example
The following example will scan ignite/deployment folder on site
www.mysite.com using authentication 'username:password' every '1'
milliseconds.
http://username:password;freq=10...@www.mysite.com:110/ignite/deployment
>>/quot

I thought this scanner will download the page served by a server and
mysite.com:110 (that will be default page), parse it and download and
deploy all GAR files specified by href attributes of  elements on the
page. Please correct your content if you agree.
---


was (Author: ashutak):
Updated both: readme.io and javadocs.

Readme.io has been updated according to Yakov comments at email (see below). 
Please, review "Code example" part again.

>From Yakov's email:
1. SPI parameters explanations and code example should be before scanners
(scanner is SPI config as well, just more detailed info)
2. code example should include all scanners + add spring configuration
example
3.
>> quot
Http Uri Example
The following example will scan ignite/deployment folder on site
www.mysite.com using authentication 'username:password' every '1'
milliseconds.
http://username:password;freq=10...@www.mysite.com:110/ignite/deployment
>>/quot

I thought this scanner will download the page served by a server and
mysite.com:110 (that will be default page), parse it and download and
deploy all GAR files specified by href attributes of  elements on the
page. Please correct your content if you agree.

> Need to improve tests, javadoc and documentation of UriDeploymentHttpScanner.
> -
>
> Key: IGNITE-1559
> URL: https://issues.apache.org/jira/browse/IGNITE-1559
> Project: Ignite
>  Issue Type: Task
>Reporter: Artem Shutak
>Assignee: Valentin Kulichenko
> Fix For: ignite-1.5
>
>
> Need to improve tests, javadoc and documentation of UriDeploymentHttpScanner. 
> It's not possible to understand from current javadoc of 
> UriDeploymentHttpScanner how it works.
> There's only one simple test in GridHttpDeploymentSelfTest.



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


  1   2   >