[JBoss JIRA] (ISPN-6737) 1 new web session creates 3 records in the corresponding war cache
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/ISPN-6737?page=com.atlassian.jira.plugin.... ]
Radoslav Husar closed ISPN-6737.
--------------------------------
Resolution: Rejected
What is printed out is controlled via java.lang.Object#toString thus the objects are not equal even if they have the same toString.
> 1 new web session creates 3 records in the corresponding war cache
> -------------------------------------------------------------------
>
> Key: ISPN-6737
> URL: https://issues.jboss.org/browse/ISPN-6737
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.1.2.Final
> Reporter: Michal Karm Babacek
> Assignee: Radoslav Husar
> Attachments: clusterbench-ee7.ear
>
>
> It might be just my ignorance, but it seems kinda weird anyway :)
> * [^clusterbench-ee7.ear] from [web-cache-investigator|https://github.com/Karm/clusterbench/tree/web-cach...] branch
> * 1 server, no balancer, trivial standalone-ha startup
> * result is way too many records in the cache for a single session id:
> {noformat}
> karm@localhost:~/Projects/MOD_CLUSTER/httpd-2.4.20-build/bin$ curl -c cookie.txt -b cookie.txt http://127.0.0.1:8080/clusterbench/debug
> Serial: 22
> Session ID: Ok6CfU2Az90jOVLJE_NkXPpBwDwq6YP5EwlbD5X-
> Current time: Tue May 31 11:25:25 CEST 2016
> ServletRequest.getServerPort(): 8080
> ServletRequest.getLocalPort(): 8080
> Node name: localhost
> Members: [localhost]
> Cache: clusterbench-ee7.ear.clusterbench-ee7-web-passivating.war, Size: 0
> Keys: []
> Cache: routing, Size: 1
> Keys: [localhost]
> Cache: clusterbench-ee7.ear.clusterbench-ee7-web-granular.war, Size: 0
> Keys: []
> Cache: clusterbench-ee7.ear.clusterbench-ee7-web-default.war, Size: 3
> Keys: [Ok6CfU2Az90jOVLJE_NkXPpBwDwq6YP5EwlbD5X-, Ok6CfU2Az90jOVLJE_NkXPpBwDwq6YP5EwlbD5X-, Ok6CfU2Az90jOVLJE_NkXPpBwDwq6YP5EwlbD5X-]
> Cache: dist, Size: 0
> Keys: []
> Physical addresses: 127.0.0.1:55200;
> karm@localhost:~/Projects/MOD_CLUSTER/httpd-2.4.20-build/bin$ cat cookie.txt
> # Netscape HTTP Cookie File
> # http://curl.haxx.se/docs/http-cookies.html
> # This file was generated by libcurl! Edit at your own risk.
> 127.0.0.1 FALSE /clusterbench FALSE 0 JSESSIONID Ok6CfU2Az90jOVLJE_NkXPpBwDwq6YP5EwlbD5X-.localhost
> {noformat}
> WDYT?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6789) EntryWrappingInterceptor computes location twice on backup owners
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-6789?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-6789:
------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> EntryWrappingInterceptor computes location twice on backup owners
> ------------------------------------------------------------------
>
> Key: ISPN-6789
> URL: https://issues.jboss.org/browse/ISPN-6789
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.0.0.Alpha2, 8.2.2.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Minor
> Fix For: 9.0.0.Alpha3
>
>
> {{cdl.localNodeIsPrimaryOwner(key) || (cdl.localNodeIsOwner(key) && !ctx.isOriginLocal())}} computes the owner twice. In replicated mode, the {{localNodeIsOwner()}} is cheaper, so it's better to call {{localNodeIsPrimaryOwner()}} only on the originator.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6718) Improve error messages
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-6718?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-6718:
--------------------------------------
Status: Open (was: New)
> Improve error messages
> ----------------------
>
> Key: ISPN-6718
> URL: https://issues.jboss.org/browse/ISPN-6718
> Project: Infinispan
> Issue Type: Enhancement
> Components: Console
> Affects Versions: 8.2.2.Final
> Reporter: Jiří Holuša
> Assignee: Vladimir Blagojevic
> Priority: Minor
>
> When editing cache configuration, I try to put some invalid value, for example on "Transactions" tab into "Stop timeout" field, when I put a string "xyz", which is trivially invalid since it's not a number, I get an error dialog with text:
> "domain-failure-description
> WFLYCTL0097: Wrong type for stop-timeout. Expected [LONG] but was STRING"
> The text is very descriptive, which is fine. I would suggest removing the "domain-failure-description" string and maybe even the WildFly error code, to make it more user friendly.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6718) Improve error messages
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-6718?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-6718:
--------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/111
> Improve error messages
> ----------------------
>
> Key: ISPN-6718
> URL: https://issues.jboss.org/browse/ISPN-6718
> Project: Infinispan
> Issue Type: Enhancement
> Components: Console
> Affects Versions: 8.2.2.Final
> Reporter: Jiří Holuša
> Assignee: Vladimir Blagojevic
> Priority: Minor
>
> When editing cache configuration, I try to put some invalid value, for example on "Transactions" tab into "Stop timeout" field, when I put a string "xyz", which is trivially invalid since it's not a number, I get an error dialog with text:
> "domain-failure-description
> WFLYCTL0097: Wrong type for stop-timeout. Expected [LONG] but was STRING"
> The text is very descriptive, which is fine. I would suggest removing the "domain-failure-description" string and maybe even the WildFly error code, to make it more user friendly.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6789) EntryWrappingInterceptor computes location twice on backup owners
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-6789?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-6789:
-------------------------------
Summary: EntryWrappingInterceptor computes location twice on backup owners (was: EnwtryWrappingInterceptor computes location twice on backup owners )
> EntryWrappingInterceptor computes location twice on backup owners
> ------------------------------------------------------------------
>
> Key: ISPN-6789
> URL: https://issues.jboss.org/browse/ISPN-6789
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.0.0.Alpha2, 8.2.2.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Minor
> Fix For: 9.0.0.Alpha3
>
>
> {{cdl.localNodeIsPrimaryOwner(key) || (cdl.localNodeIsOwner(key) && !ctx.isOriginLocal())}} computes the owner twice. In replicated mode, the {{localNodeIsOwner()}} is cheaper, so it's better to call {{localNodeIsPrimaryOwner()}} only on the originator.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6790) Distribution interceptors re-compute key location after remote get
by Dan Berindei (JIRA)
Dan Berindei created ISPN-6790:
----------------------------------
Summary: Distribution interceptors re-compute key location after remote get
Key: ISPN-6790
URL: https://issues.jboss.org/browse/ISPN-6790
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 8.2.2.Final, 9.0.0.Alpha2
Reporter: Dan Berindei
Priority: Minor
Fix For: 9.0.0.Alpha3
If the distribution interceptors don't find a key remotely, they try again to retrieve it from the local data container. Before reading the local value, though, they compute the key's ownership again, to make sure they don't read a stale value that was previously owned by the local node.
Most of the time, the topology doesn't change during the invocation through the interceptor chain, so there's no need to look up the value locally again, or to re-compute the key's location.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months