[jira] [Commented] (IGNITE-8225) Add a command to control script to print current topology version
[
https://issues.apache.org/jira/browse/IGNITE-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008492#comment-17008492
]
ruchir choudhry commented on IGNITE-8225:
-
Maxim pls go ahead.
> Add a command to control script to print current topology version
> -
>
> Key: IGNITE-8225
> URL: https://issues.apache.org/jira/browse/IGNITE-8225
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: ruchir choudhry
>Priority: Critical
> Fix For: 2.9
>
>
> The command should be {{./control.sh --topology}} and should print a short
> summary about the current topology (topology version, number of client nodes,
> number of server nodes, baseline topology information)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-9023) LinkageError or ClassNotFoundException should not be swollen by GridDeploymentCommunication during processing deployment request.
[
https://issues.apache.org/jira/browse/IGNITE-9023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16547190#comment-16547190
]
ruchir choudhry edited comment on IGNITE-9023 at 7/17/18 11:22 PM:
---
Hello [~ivandasch]
It will only happen if the Debug is on, which is the correct, right,
Do you want we need to record it in the logs file and send to the client also ?
Will appreciate a quick reply, i will be able to pick this one.
private void processResourceRequest(UUID nodeId, GridDeploymentRequest req) {
if (log.isDebugEnabled())
log.debug("Received peer class/resource loading request [node=" + nodeId + ",
req=" + req + ']');
// this the place you want me to change ? its happening only is log.Debug is
true. which is the right thing to do , Pls confirm
if (req.responseTopic() == null) {
try
{ req.responseTopic(U.unmarshal(marsh, req.responseTopicBytes(),
U.resolveClassLoader(ctx.config(; }
catch (IgniteCheckedException e)
{ U.error(log, "Failed to process deployment request (will ignore): " + req,
e); return; }
}
--
Regards, Ruchir
was (Author: ruchirc):
Hello [~ivandasch]
It will only happen if the Debug is on, which is the correct, right,
Do you want we need to record it in the logs file and send to the client also ?
Will appreciate a quick reply, i will be able to pick this one.
private void processResourceRequest(UUID nodeId, GridDeploymentRequest req) {
if (log.isDebugEnabled())
log.debug("Received peer class/resource loading request [node=" + nodeId + ",
req=" + req + ']');
// this the place you want me to change ? its happening only is log.Debug is
true. which is the right thing to do , Pls confirm
if (req.responseTopic() == null) {
try {
req.responseTopic(U.unmarshal(marsh, req.responseTopicBytes(),
U.resolveClassLoader(ctx.config(;
}
catch (IgniteCheckedException e) {
U.error(log, "Failed to process deployment request (will ignore): " + req, e);
Regards,
Ruchir
return;
}
}
--
> LinkageError or ClassNotFoundException should not be swollen by
> GridDeploymentCommunication during processing deployment request.
> -
>
> Key: IGNITE-9023
> URL: https://issues.apache.org/jira/browse/IGNITE-9023
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.5
>Reporter: Ivan Daschinskiy
>Assignee: ruchir choudhry
>Priority: Minor
> Fix For: 2.7
>
>
> In current implementation any error, that is thrown in
> GridDeploymentCommunication#processResourceRequest, is ignored silently.
> Any error should be logged and send to client.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9023) LinkageError or ClassNotFoundException should not be swollen by GridDeploymentCommunication during processing deployment request.
[
https://issues.apache.org/jira/browse/IGNITE-9023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16547190#comment-16547190
]
ruchir choudhry edited comment on IGNITE-9023 at 7/17/18 11:10 PM:
---
Hello [~ivandasch]
It will only happen if the Debug is on, which is the correct, right,
Do you want we need to record it in the logs file and send to the client also ?
Will appreciate a quick reply, i will be able to pick this one.
private void processResourceRequest(UUID nodeId, GridDeploymentRequest req) {
if (log.isDebugEnabled())
log.debug("Received peer class/resource loading request [node=" + nodeId + ",
req=" + req + ']');
// this the place you want me to change ? its happening only is log.Debug is
true. which is the right thing to do , Pls confirm
if (req.responseTopic() == null) {
try {
req.responseTopic(U.unmarshal(marsh, req.responseTopicBytes(),
U.resolveClassLoader(ctx.config(;
}
catch (IgniteCheckedException e) {
U.error(log, "Failed to process deployment request (will ignore): " + req, e);
Regards,
Ruchir
return;
}
}
--
was (Author: ruchirc):
Hello [~ivandasch]
It will only happen if the Debug is on, which is the correct, right,
Do you want we need to record it in the logs file and send to the client also ?
Will appreciate a quick reply, i will be able to pick this one.
if (!busyLock.enterBusy())
{ if (log.isDebugEnabled()) log.debug("Ignoring deployment request since grid
is stopping " + "[nodeId=" + nodeId + ", msg=" + msg + ']'); return; }
--
> LinkageError or ClassNotFoundException should not be swollen by
> GridDeploymentCommunication during processing deployment request.
> -
>
> Key: IGNITE-9023
> URL: https://issues.apache.org/jira/browse/IGNITE-9023
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.5
>Reporter: Ivan Daschinskiy
>Assignee: ruchir choudhry
>Priority: Minor
> Fix For: 2.7
>
>
> In current implementation any error, that is thrown in
> GridDeploymentCommunication#processResourceRequest, is ignored silently.
> Any error should be logged and send to client.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9023) LinkageError or ClassNotFoundException should not be swollen by GridDeploymentCommunication during processing deployment request.
[
https://issues.apache.org/jira/browse/IGNITE-9023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16547190#comment-16547190
]
ruchir choudhry edited comment on IGNITE-9023 at 7/17/18 11:01 PM:
---
Hello [~ivandasch]
It will only happen if the Debug is on, which is the correct, right,
Do you want we need to record it in the logs file and send to the client also ?
Will appreciate a quick reply, i will be able to pick this one.
if (!busyLock.enterBusy())
{ if (log.isDebugEnabled()) log.debug("Ignoring deployment request since grid
is stopping " + "[nodeId=" + nodeId + ", msg=" + msg + ']'); return; }
--
was (Author: ruchirc):
Hello
It will only happen if the Debug is on, which is the correct, right,
Do you want we need to record it in the logs and send to the client also ?
Will appreciate a quick reply, i will be able to pick this one.
-
if (!busyLock.enterBusy()) {
if (log.isDebugEnabled())
log.debug("Ignoring deployment request since grid is stopping " + "[nodeId=" +
nodeId + ", msg=" + msg + ']');
return;
}
--
> LinkageError or ClassNotFoundException should not be swollen by
> GridDeploymentCommunication during processing deployment request.
> -
>
> Key: IGNITE-9023
> URL: https://issues.apache.org/jira/browse/IGNITE-9023
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.5
>Reporter: Ivan Daschinskiy
>Assignee: ruchir choudhry
>Priority: Minor
> Fix For: 2.7
>
>
> In current implementation any error, that is thrown in
> GridDeploymentCommunication#processResourceRequest, is ignored silently.
> Any error should be logged and send to client.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9023) LinkageError or ClassNotFoundException should not be swollen by GridDeploymentCommunication during processing deployment request.
[ https://issues.apache.org/jira/browse/IGNITE-9023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ruchir choudhry reassigned IGNITE-9023: --- Assignee: ruchir choudhry > LinkageError or ClassNotFoundException should not be swollen by > GridDeploymentCommunication during processing deployment request. > - > > Key: IGNITE-9023 > URL: https://issues.apache.org/jira/browse/IGNITE-9023 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Ivan Daschinskiy >Assignee: ruchir choudhry >Priority: Minor > Fix For: 2.7 > > > In current implementation any error, that is thrown in > GridDeploymentCommunication#processResourceRequest, is ignored silently. > Any error should be logged and send to client. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9023) LinkageError or ClassNotFoundException should not be swollen by GridDeploymentCommunication during processing deployment request.
[
https://issues.apache.org/jira/browse/IGNITE-9023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16547190#comment-16547190
]
ruchir choudhry commented on IGNITE-9023:
-
Hello
It will only happen if the Debug is on, which is the correct, right,
Do you want we need to record it in the logs and send to the client also ?
Will appreciate a quick reply, i will be able to pick this one.
-
if (!busyLock.enterBusy()) {
if (log.isDebugEnabled())
log.debug("Ignoring deployment request since grid is stopping " + "[nodeId=" +
nodeId + ", msg=" + msg + ']');
return;
}
--
> LinkageError or ClassNotFoundException should not be swollen by
> GridDeploymentCommunication during processing deployment request.
> -
>
> Key: IGNITE-9023
> URL: https://issues.apache.org/jira/browse/IGNITE-9023
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.5
>Reporter: Ivan Daschinskiy
>Priority: Minor
> Fix For: 2.7
>
>
> In current implementation any error, that is thrown in
> GridDeploymentCommunication#processResourceRequest, is ignored silently.
> Any error should be logged and send to client.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7793) SQL does not work if value has index filed which name equals to affinity key name
[
https://issues.apache.org/jira/browse/IGNITE-7793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16547159#comment-16547159
]
ruchir choudhry commented on IGNITE-7793:
-
[~michal.warecki] Can i take this one.
> SQL does not work if value has index filed which name equals to affinity key
> name
> -
>
> Key: IGNITE-7793
> URL: https://issues.apache.org/jira/browse/IGNITE-7793
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Priority: Blocker
> Fix For: 2.7
>
>
> SQL does not work if value has index filed which name equals to affinity key
> name:
> {code:java}
> public class AKey {
> @AffinityKeyMapped
> int a;
> public AKey(int a) {
> this.a = a;
> }
> }
> public class AVal {
> @QuerySqlField
> int a;
> public AVal(int a) {
> this.a = a;
> }
> }
> AKey aKey = new AKey(1);
> AVal aVal = new AVal(0);
> IgniteCache cache = ignite.cache("Instrument");
> cache.put(aKey, aVal);
> SqlFieldsQuery query = new SqlFieldsQuery("select * from \"Instrument\".AVal
> it where it.a=?");
> List> res = cache.query(query.setArgs(0)).getAll();
> if(res.isEmpty()) {
> System.out.println("! FAILED !!!");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8982) SQL TX: reuse H2 connections
[ https://issues.apache.org/jira/browse/IGNITE-8982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16541969#comment-16541969 ] ruchir choudhry commented on IGNITE-8982: - No problem , changed it to Ivan Pavlukhin's name. > SQL TX: reuse H2 connections > > > Key: IGNITE-8982 > URL: https://issues.apache.org/jira/browse/IGNITE-8982 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Major > > H2 Connection creation is not very fast. Reusing already created connections > could speed up execution in several cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8982) SQL TX: reuse H2 connections
[ https://issues.apache.org/jira/browse/IGNITE-8982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ruchir choudhry reassigned IGNITE-8982: --- Assignee: Ivan Pavlukhin (was: ruchir choudhry) > SQL TX: reuse H2 connections > > > Key: IGNITE-8982 > URL: https://issues.apache.org/jira/browse/IGNITE-8982 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Major > > H2 Connection creation is not very fast. Reusing already created connections > could speed up execution in several cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8982) SQL TX: reuse H2 connections
[ https://issues.apache.org/jira/browse/IGNITE-8982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ruchir choudhry reassigned IGNITE-8982: --- Assignee: ruchir choudhry > SQL TX: reuse H2 connections > > > Key: IGNITE-8982 > URL: https://issues.apache.org/jira/browse/IGNITE-8982 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Pavlukhin >Assignee: ruchir choudhry >Priority: Major > > H2 Connection creation is not very fast. Reusing already created connections > could speed up execution in several cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8982) SQL TX: reuse H2 connections
[ https://issues.apache.org/jira/browse/IGNITE-8982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16540914#comment-16540914 ] ruchir choudhry commented on IGNITE-8982: - [~Pavlukhin] : If you can help me with the flow a bit, I can take this up. > SQL TX: reuse H2 connections > > > Key: IGNITE-8982 > URL: https://issues.apache.org/jira/browse/IGNITE-8982 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Pavlukhin >Priority: Major > > H2 Connection creation is not very fast. Reusing already created connections > could speed up execution in several cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8225) Add a command to control script to print current topology version
[
https://issues.apache.org/jira/browse/IGNITE-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482082#comment-16482082
]
ruchir choudhry commented on IGNITE-8225:
-
Let me take a shot at it, will report back.
> Add a command to control script to print current topology version
> -
>
> Key: IGNITE-8225
> URL: https://issues.apache.org/jira/browse/IGNITE-8225
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: ruchir choudhry
>Priority: Critical
> Fix For: 2.6
>
>
> The command should be {{./control.sh --topology}} and should print a short
> summary about the current topology (topology version, number of client nodes,
> number of server nodes, baseline topology information)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8225) Add a command to control script to print current topology version
[
https://issues.apache.org/jira/browse/IGNITE-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ruchir choudhry reassigned IGNITE-8225:
---
Assignee: ruchir choudhry
> Add a command to control script to print current topology version
> -
>
> Key: IGNITE-8225
> URL: https://issues.apache.org/jira/browse/IGNITE-8225
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: ruchir choudhry
>Priority: Critical
> Fix For: 2.6
>
>
> The command should be {{./control.sh --topology}} and should print a short
> summary about the current topology (topology version, number of client nodes,
> number of server nodes, baseline topology information)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7721) Apache Ignite web session clustering stack after login success
[
https://issues.apache.org/jira/browse/IGNITE-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ruchir choudhry reassigned IGNITE-7721:
---
Assignee: ruchir choudhry
> Apache Ignite web session clustering stack after login success
> --
>
> Key: IGNITE-7721
> URL: https://issues.apache.org/jira/browse/IGNITE-7721
> Project: Ignite
> Issue Type: Bug
> Components: cache, websession
>Affects Versions: 2.3
>Reporter: Sanjeet Jha
>Assignee: ruchir choudhry
>Priority: Blocker
>
> I implement Apache ignite in my OfBiz application. after login my application
> show login susses. but the browser does not get any response from the server.
> Here is my web.xml
>
> {{ IgniteConfigurationFilePath
> specialpurpose/fnp/webapp/fnp/WEB-INF/ignite-config.xml
>
> IgniteWebSessionsCacheName
> replicated
> org.apache.ignite.startup.servlet.ServletContextListenerStartup
>
> IgniteWebSessionsFilter
> org.apache.ignite.cache.websession.WebSessionFilter
>
> IgniteWebSessionsFilter
> /* }}
>
>
>
> {{and my ignite-config.xml}}
>
>
> {{http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns:util="http://www.springframework.org/schema/util; xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd;> id="ignite.cfg" class="org.apache.ignite.configuration.IgniteConfiguration">
>class="org.apache.ignite.configuration.CacheConfiguration">
>
> class="org.apache.ignite.logger.log4j.Log4JLogger"> type="java.lang.String" value="/data/log/ignite-log4j.xml" />
>name="includeEventTypes">static-field="org.apache.ignite.events.EventType.EVT_TASK_STARTED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_FINISHED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_FAILED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_TIMEDOUT" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_SESSION_ATTR_SET"
> /> static-field="org.apache.ignite.events.EventType.EVT_TASK_REDUCED" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_PUT" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_READ" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_REMOVED" />
> class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> name="ipFinder"> class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">
> 127.0.0.1:47500
> }}{{}}
>
>
>
> I also try to collected ignite log. but there is no error log. Any idea what
> happens.
> And also some time I OutOfMemoryError error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7721) Apache Ignite web session clustering stack after login success
[
https://issues.apache.org/jira/browse/IGNITE-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ruchir choudhry reassigned IGNITE-7721:
---
Assignee: ruchir choudhry
> Apache Ignite web session clustering stack after login success
> --
>
> Key: IGNITE-7721
> URL: https://issues.apache.org/jira/browse/IGNITE-7721
> Project: Ignite
> Issue Type: Bug
> Components: cache, websession
>Affects Versions: 2.3
>Reporter: Sanjeet Jha
>Assignee: ruchir choudhry
>Priority: Blocker
>
> I implement Apache ignite in my OfBiz application. after login my application
> show login susses. but the browser does not get any response from the server.
> Here is my web.xml
>
> {{ IgniteConfigurationFilePath
> specialpurpose/fnp/webapp/fnp/WEB-INF/ignite-config.xml
>
> IgniteWebSessionsCacheName
> replicated
> org.apache.ignite.startup.servlet.ServletContextListenerStartup
>
> IgniteWebSessionsFilter
> org.apache.ignite.cache.websession.WebSessionFilter
>
> IgniteWebSessionsFilter
> /* }}
>
>
>
> {{and my ignite-config.xml}}
>
>
> {{http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns:util="http://www.springframework.org/schema/util; xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd;> id="ignite.cfg" class="org.apache.ignite.configuration.IgniteConfiguration">
>class="org.apache.ignite.configuration.CacheConfiguration">
>
> class="org.apache.ignite.logger.log4j.Log4JLogger"> type="java.lang.String" value="/data/log/ignite-log4j.xml" />
>name="includeEventTypes">static-field="org.apache.ignite.events.EventType.EVT_TASK_STARTED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_FINISHED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_FAILED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_TIMEDOUT" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_SESSION_ATTR_SET"
> /> static-field="org.apache.ignite.events.EventType.EVT_TASK_REDUCED" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_PUT" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_READ" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_REMOVED" />
> class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> name="ipFinder"> class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">
> 127.0.0.1:47500
> }}{{}}
>
>
>
> I also try to collected ignite log. but there is no error log. Any idea what
> happens.
> And also some time I OutOfMemoryError error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7721) Apache Ignite web session clustering stack after login success
[
https://issues.apache.org/jira/browse/IGNITE-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482078#comment-16482078
]
ruchir choudhry commented on IGNITE-7721:
-
Can you pls help me with more details:
Is the folder which you are trying to access is having sufficient write
privilege for the problem 01.
for out of memory problem 2: is he env distributed or local
> Apache Ignite web session clustering stack after login success
> --
>
> Key: IGNITE-7721
> URL: https://issues.apache.org/jira/browse/IGNITE-7721
> Project: Ignite
> Issue Type: Bug
> Components: cache, websession
>Affects Versions: 2.3
>Reporter: Sanjeet Jha
>Priority: Blocker
>
> I implement Apache ignite in my OfBiz application. after login my application
> show login susses. but the browser does not get any response from the server.
> Here is my web.xml
>
> {{ IgniteConfigurationFilePath
> specialpurpose/fnp/webapp/fnp/WEB-INF/ignite-config.xml
>
> IgniteWebSessionsCacheName
> replicated
> org.apache.ignite.startup.servlet.ServletContextListenerStartup
>
> IgniteWebSessionsFilter
> org.apache.ignite.cache.websession.WebSessionFilter
>
> IgniteWebSessionsFilter
> /* }}
>
>
>
> {{and my ignite-config.xml}}
>
>
> {{http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns:util="http://www.springframework.org/schema/util; xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd;> id="ignite.cfg" class="org.apache.ignite.configuration.IgniteConfiguration">
>class="org.apache.ignite.configuration.CacheConfiguration">
>
> class="org.apache.ignite.logger.log4j.Log4JLogger"> type="java.lang.String" value="/data/log/ignite-log4j.xml" />
>name="includeEventTypes">static-field="org.apache.ignite.events.EventType.EVT_TASK_STARTED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_FINISHED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_FAILED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_TIMEDOUT" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_SESSION_ATTR_SET"
> /> static-field="org.apache.ignite.events.EventType.EVT_TASK_REDUCED" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_PUT" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_READ" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_REMOVED" />
> class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> name="ipFinder"> class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">
> 127.0.0.1:47500
> }}{{}}
>
>
>
> I also try to collected ignite log. but there is no error log. Any idea what
> happens.
> And also some time I OutOfMemoryError error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7721) Apache Ignite web session clustering stack after login success
[
https://issues.apache.org/jira/browse/IGNITE-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ruchir choudhry reassigned IGNITE-7721:
---
Assignee: (was: ruchir choudhry)
> Apache Ignite web session clustering stack after login success
> --
>
> Key: IGNITE-7721
> URL: https://issues.apache.org/jira/browse/IGNITE-7721
> Project: Ignite
> Issue Type: Bug
> Components: cache, websession
>Affects Versions: 2.3
>Reporter: Sanjeet Jha
>Priority: Blocker
>
> I implement Apache ignite in my OfBiz application. after login my application
> show login susses. but the browser does not get any response from the server.
> Here is my web.xml
>
> {{ IgniteConfigurationFilePath
> specialpurpose/fnp/webapp/fnp/WEB-INF/ignite-config.xml
>
> IgniteWebSessionsCacheName
> replicated
> org.apache.ignite.startup.servlet.ServletContextListenerStartup
>
> IgniteWebSessionsFilter
> org.apache.ignite.cache.websession.WebSessionFilter
>
> IgniteWebSessionsFilter
> /* }}
>
>
>
> {{and my ignite-config.xml}}
>
>
> {{http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns:util="http://www.springframework.org/schema/util; xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd;> id="ignite.cfg" class="org.apache.ignite.configuration.IgniteConfiguration">
>class="org.apache.ignite.configuration.CacheConfiguration">
>
> class="org.apache.ignite.logger.log4j.Log4JLogger"> type="java.lang.String" value="/data/log/ignite-log4j.xml" />
>name="includeEventTypes">static-field="org.apache.ignite.events.EventType.EVT_TASK_STARTED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_FINISHED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_FAILED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_TIMEDOUT" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_SESSION_ATTR_SET"
> /> static-field="org.apache.ignite.events.EventType.EVT_TASK_REDUCED" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_PUT" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_READ" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_REMOVED" />
> class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> name="ipFinder"> class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">
> 127.0.0.1:47500
> }}{{}}
>
>
>
> I also try to collected ignite log. but there is no error log. Any idea what
> happens.
> And also some time I OutOfMemoryError error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7759) Logger does not print sockTimeout and ackTimeout default values for TcpDiscoverySpi
[
https://issues.apache.org/jira/browse/IGNITE-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482069#comment-16482069
]
ruchir choudhry commented on IGNITE-7759:
-
Hello [~guseinov] , [~Sergey Nuyanzin]
Pls review the changes and suggest if i have done the right way,
[http://apache-ignite-developers.2346864.n4.nabble.com/GitHub-ignite-pull-request-4031-IGNITE-7759-gt-Made-changes-for-this-bug-td30706.html]
Regards,
Ruchir
> Logger does not print sockTimeout and ackTimeout default values for
> TcpDiscoverySpi
> ---
>
> Key: IGNITE-7759
> URL: https://issues.apache.org/jira/browse/IGNITE-7759
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.9, 2.1, 2.3
>Reporter: Roman Guseinov
>Assignee: ruchir choudhry
>Priority: Minor
> Labels: newbie
>
> Logger does not print sockTimeout and ackTimeout default values for
> TcpDiscoverySpi
> Before starting TcpDiscoverySpi logger prints the following message (debug
> mode is enabled):
> {code:java}
> [main][GridDiscoveryManager] Starting SPI: TcpDiscoverySpi [addrRslvr=null,
> sockTimeout=0, ackTimeout=0, marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.internal.IgniteKernal$5@402e37bc], reconCnt=10,
> reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
> clientReconnectDisabled=false]
> {code}
> Note, that sockTimeout=0 and ackTimeout=0. Default values initializing
> happens after TcpDiscoverySpi.spiStart is called:
> {code:java}
> public class TcpDiscoverySpi extends IgniteSpiAdapter implements DiscoverySpi
> {
> /** Node attribute that is mapped to node's external addresses (value is
> disc.tcp.ext-addrs). */
> /** {@inheritDoc} */
> @Override public void spiStart(@Nullable String igniteInstanceName)
> throws IgniteSpiException {
> initializeImpl();
> }
> /**
> *
> */
> private void initializeImpl() {
> if (impl != null)
> return;
> initFailureDetectionTimeout();
> if (!forceSrvMode &&
> (Boolean.TRUE.equals(ignite.configuration().isClientMode( {
> if (ackTimeout == 0)
> ackTimeout = DFLT_ACK_TIMEOUT_CLIENT;
> if (sockTimeout == 0)
> sockTimeout = DFLT_SOCK_TIMEOUT_CLIENT;
> impl = new ClientImpl(this);
> ctxInitLatch.countDown();
> }
> else {
> if (ackTimeout == 0)
> ackTimeout = DFLT_ACK_TIMEOUT;
> if (sockTimeout == 0)
> sockTimeout = DFLT_SOCK_TIMEOUT;
> impl = new ServerImpl(this);
> }
>
> }
> }
> {code}
> To avoid confusion I suggest printing default sockTimeout and ackTimeout if
> they weren't changed like:
> {code:java}
> [main][GridDiscoveryManager] Starting SPI: TcpDiscoverySpi [addrRslvr=null,
> sockTimeout=5000, ackTimeout=5000, marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.internal.IgniteKernal$5@402e37bc], reconCnt=10,
> reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
> clientReconnectDisabled=false]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7759) Logger does not print sockTimeout and ackTimeout default values for TcpDiscoverySpi
[
https://issues.apache.org/jira/browse/IGNITE-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482036#comment-16482036
]
ruchir choudhry commented on IGNITE-7759:
-
[~Sergey Nuyanzin]: Had to take care of some stuff, will close it asap
> Logger does not print sockTimeout and ackTimeout default values for
> TcpDiscoverySpi
> ---
>
> Key: IGNITE-7759
> URL: https://issues.apache.org/jira/browse/IGNITE-7759
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.9, 2.1, 2.3
>Reporter: Roman Guseinov
>Assignee: ruchir choudhry
>Priority: Minor
> Labels: newbie
>
> Logger does not print sockTimeout and ackTimeout default values for
> TcpDiscoverySpi
> Before starting TcpDiscoverySpi logger prints the following message (debug
> mode is enabled):
> {code:java}
> [main][GridDiscoveryManager] Starting SPI: TcpDiscoverySpi [addrRslvr=null,
> sockTimeout=0, ackTimeout=0, marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.internal.IgniteKernal$5@402e37bc], reconCnt=10,
> reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
> clientReconnectDisabled=false]
> {code}
> Note, that sockTimeout=0 and ackTimeout=0. Default values initializing
> happens after TcpDiscoverySpi.spiStart is called:
> {code:java}
> public class TcpDiscoverySpi extends IgniteSpiAdapter implements DiscoverySpi
> {
> /** Node attribute that is mapped to node's external addresses (value is
> disc.tcp.ext-addrs). */
> /** {@inheritDoc} */
> @Override public void spiStart(@Nullable String igniteInstanceName)
> throws IgniteSpiException {
> initializeImpl();
> }
> /**
> *
> */
> private void initializeImpl() {
> if (impl != null)
> return;
> initFailureDetectionTimeout();
> if (!forceSrvMode &&
> (Boolean.TRUE.equals(ignite.configuration().isClientMode( {
> if (ackTimeout == 0)
> ackTimeout = DFLT_ACK_TIMEOUT_CLIENT;
> if (sockTimeout == 0)
> sockTimeout = DFLT_SOCK_TIMEOUT_CLIENT;
> impl = new ClientImpl(this);
> ctxInitLatch.countDown();
> }
> else {
> if (ackTimeout == 0)
> ackTimeout = DFLT_ACK_TIMEOUT;
> if (sockTimeout == 0)
> sockTimeout = DFLT_SOCK_TIMEOUT;
> impl = new ServerImpl(this);
> }
>
> }
> }
> {code}
> To avoid confusion I suggest printing default sockTimeout and ackTimeout if
> they weren't changed like:
> {code:java}
> [main][GridDiscoveryManager] Starting SPI: TcpDiscoverySpi [addrRslvr=null,
> sockTimeout=5000, ackTimeout=5000, marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.internal.IgniteKernal$5@402e37bc], reconCnt=10,
> reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
> clientReconnectDisabled=false]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7759) Logger does not print sockTimeout and ackTimeout default values for TcpDiscoverySpi
[
https://issues.apache.org/jira/browse/IGNITE-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ruchir choudhry reassigned IGNITE-7759:
---
Assignee: ruchir choudhry
> Logger does not print sockTimeout and ackTimeout default values for
> TcpDiscoverySpi
> ---
>
> Key: IGNITE-7759
> URL: https://issues.apache.org/jira/browse/IGNITE-7759
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.9, 2.1, 2.3
>Reporter: Roman Guseinov
>Assignee: ruchir choudhry
>Priority: Minor
> Labels: newbie
>
> Logger does not print sockTimeout and ackTimeout default values for
> TcpDiscoverySpi
> Before starting TcpDiscoverySpi logger prints the following message (debug
> mode is enabled):
> {code:java}
> [main][GridDiscoveryManager] Starting SPI: TcpDiscoverySpi [addrRslvr=null,
> sockTimeout=0, ackTimeout=0, marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.internal.IgniteKernal$5@402e37bc], reconCnt=10,
> reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
> clientReconnectDisabled=false]
> {code}
> Note, that sockTimeout=0 and ackTimeout=0. Default values initializing
> happens after TcpDiscoverySpi.spiStart is called:
> {code:java}
> public class TcpDiscoverySpi extends IgniteSpiAdapter implements DiscoverySpi
> {
> /** Node attribute that is mapped to node's external addresses (value is
> disc.tcp.ext-addrs). */
> /** {@inheritDoc} */
> @Override public void spiStart(@Nullable String igniteInstanceName)
> throws IgniteSpiException {
> initializeImpl();
> }
> /**
> *
> */
> private void initializeImpl() {
> if (impl != null)
> return;
> initFailureDetectionTimeout();
> if (!forceSrvMode &&
> (Boolean.TRUE.equals(ignite.configuration().isClientMode( {
> if (ackTimeout == 0)
> ackTimeout = DFLT_ACK_TIMEOUT_CLIENT;
> if (sockTimeout == 0)
> sockTimeout = DFLT_SOCK_TIMEOUT_CLIENT;
> impl = new ClientImpl(this);
> ctxInitLatch.countDown();
> }
> else {
> if (ackTimeout == 0)
> ackTimeout = DFLT_ACK_TIMEOUT;
> if (sockTimeout == 0)
> sockTimeout = DFLT_SOCK_TIMEOUT;
> impl = new ServerImpl(this);
> }
>
> }
> }
> {code}
> To avoid confusion I suggest printing default sockTimeout and ackTimeout if
> they weren't changed like:
> {code:java}
> [main][GridDiscoveryManager] Starting SPI: TcpDiscoverySpi [addrRslvr=null,
> sockTimeout=5000, ackTimeout=5000, marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.internal.IgniteKernal$5@402e37bc], reconCnt=10,
> reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
> clientReconnectDisabled=false]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7759) Logger does not print sockTimeout and ackTimeout default values for TcpDiscoverySpi
[
https://issues.apache.org/jira/browse/IGNITE-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372509#comment-16372509
]
ruchir choudhry commented on IGNITE-7759:
-
Hello Roman,
Can i pick this ticket ,
Regards,
Ruchir
> Logger does not print sockTimeout and ackTimeout default values for
> TcpDiscoverySpi
> ---
>
> Key: IGNITE-7759
> URL: https://issues.apache.org/jira/browse/IGNITE-7759
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.9, 2.1, 2.3
>Reporter: Roman Guseinov
>Priority: Minor
> Labels: newbie
>
> Logger does not print sockTimeout and ackTimeout default values for
> TcpDiscoverySpi
> Before starting TcpDiscoverySpi logger prints the following message (debug
> mode is enabled):
> {code:java}
> [main][GridDiscoveryManager] Starting SPI: TcpDiscoverySpi [addrRslvr=null,
> sockTimeout=0, ackTimeout=0, marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.internal.IgniteKernal$5@402e37bc], reconCnt=10,
> reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
> clientReconnectDisabled=false]
> {code}
> Note, that sockTimeout=0 and ackTimeout=0. Default values initializing
> happens after TcpDiscoverySpi.spiStart is called:
> {code:java}
> public class TcpDiscoverySpi extends IgniteSpiAdapter implements DiscoverySpi
> {
> /** Node attribute that is mapped to node's external addresses (value is
> disc.tcp.ext-addrs). */
> /** {@inheritDoc} */
> @Override public void spiStart(@Nullable String igniteInstanceName)
> throws IgniteSpiException {
> initializeImpl();
> }
> /**
> *
> */
> private void initializeImpl() {
> if (impl != null)
> return;
> initFailureDetectionTimeout();
> if (!forceSrvMode &&
> (Boolean.TRUE.equals(ignite.configuration().isClientMode( {
> if (ackTimeout == 0)
> ackTimeout = DFLT_ACK_TIMEOUT_CLIENT;
> if (sockTimeout == 0)
> sockTimeout = DFLT_SOCK_TIMEOUT_CLIENT;
> impl = new ClientImpl(this);
> ctxInitLatch.countDown();
> }
> else {
> if (ackTimeout == 0)
> ackTimeout = DFLT_ACK_TIMEOUT;
> if (sockTimeout == 0)
> sockTimeout = DFLT_SOCK_TIMEOUT;
> impl = new ServerImpl(this);
> }
>
> }
> }
> {code}
> To avoid confusion I suggest printing default sockTimeout and ackTimeout if
> they weren't changed like:
> {code:java}
> [main][GridDiscoveryManager] Starting SPI: TcpDiscoverySpi [addrRslvr=null,
> sockTimeout=5000, ackTimeout=5000, marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.internal.IgniteKernal$5@402e37bc], reconCnt=10,
> reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
> clientReconnectDisabled=false]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
