[JBoss JIRA] (ISPN-2752) IllegalStateException on shutdown
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-2752?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-2752:
-----------------------------------------------
Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 903308|https://bugzilla.redhat.com/show_bug.cgi?id=903308] from NEW to ASSIGNED
> IllegalStateException on shutdown
> ---------------------------------
>
> Key: ISPN-2752
> URL: https://issues.jboss.org/browse/ISPN-2752
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 5.2.0.CR2
> Reporter: Michal Linhard
> Assignee: Dan Berindei
> Priority: Minor
> Fix For: 5.2.2, 5.3.0.Final
>
>
> This happens on graceful shutdown of 8 or 6 nodes of 5.2.0.CR2:
> {code}
> 07:17:45,892 ERROR [org.infinispan.topology.ClusterTopologyManagerImpl] ISPN000196: Failed to recover cluster state after the current node became the coordinator: java.util.concurrent.ExecutionException: org.infinispan.CacheException: Remote (node0005/default) failed unexpectedly
> at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:232) [rt.jar:1.6.0_33]
> at java.util.concurrent.FutureTask.get(FutureTask.java:91) [rt.jar:1.6.0_33]
> at org.infinispan.topology.ClusterTopologyManagerImpl.executeOnClusterSync(ClusterTopologyManagerImpl.java:567) [infinispan-core-5.2.0.CR2-redhat-1.jar:5.2.0.CR2-redhat-1]
> at org.infinispan.topology.ClusterTopologyManagerImpl.recoverClusterStatus(ClusterTopologyManagerImpl.java:432) [infinispan-core-5.2.0.CR2-redhat-1.jar:5.2.0.CR2-redhat-1]
> at org.infinispan.topology.ClusterTopologyManagerImpl.handleNewView(ClusterTopologyManagerImpl.java:231) [infinispan-core-5.2.0.CR2-redhat-1.jar:5.2.0.CR2-redhat-1]
> at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener.handleViewChange(ClusterTopologyManagerImpl.java:597) [infinispan-core-5.2.0.CR2-redhat-1.jar:5.2.0.CR2-redhat-1]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_33]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_33]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_33]
> at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_33]
> at org.infinispan.notifications.AbstractListenerImpl$ListenerInvocation$1.run(AbstractListenerImpl.java:212) [infinispan-core-5.2.0.CR2-redhat-1.jar:5.2.0.CR2-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]
> Caused by: org.infinispan.CacheException: Remote (node0005/default) failed unexpectedly
> at org.infinispan.remoting.transport.AbstractTransport.parseResponseAndAddToResponseList(AbstractTransport.java:96) [infinispan-core-5.2.0.CR2-redhat-1.jar:5.2.0.CR2-redhat-1]
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:541) [infinispan-core-5.2.0.CR2-redhat-1.jar:5.2.0.CR2-redhat-1]
> at org.infinispan.topology.ClusterTopologyManagerImpl$2.call(ClusterTopologyManagerImpl.java:549) [infinispan-core-5.2.0.CR2-redhat-1.jar:5.2.0.CR2-redhat-1]
> at org.infinispan.topology.ClusterTopologyManagerImpl$2.call(ClusterTopologyManagerImpl.java:546) [infinispan-core-5.2.0.CR2-redhat-1.jar:5.2.0.CR2-redhat-1]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_33]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_33]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA-redhat-2.jar:2.0.0.GA-redhat-2]
> Caused by: java.lang.IllegalStateException: transport was closed
> at org.jgroups.blocks.GroupRequest.transportClosed(GroupRequest.java:273) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final-redhat-1]
> at org.jgroups.blocks.RequestCorrelator.stop(RequestCorrelator.java:269) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final-redhat-1]
> at org.jgroups.blocks.MessageDispatcher.stop(MessageDispatcher.java:152) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final-redhat-1]
> at org.jgroups.blocks.MessageDispatcher.channelDisconnected(MessageDispatcher.java:455) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final-redhat-1]
> at org.jgroups.Channel.notifyChannelDisconnected(Channel.java:507) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final-redhat-1]
> at org.jgroups.JChannel.disconnect(JChannel.java:363) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final-redhat-1]
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.stop(JGroupsTransport.java:258) [infinispan-core-5.2.0.CR2-redhat-1.jar:5.2.0.CR2-redhat-1]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_33]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_33]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_33]
> at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_33]
> at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:203) [infinispan-core-5.2.0.CR2-redhat-1.jar:5.2.0.CR2-redhat-1]
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:883) [infinispan-core-5.2.0.CR2-redhat-1.jar:5.2.0.CR2-redhat-1]
> at org.infinispan.factories.AbstractComponentRegistry.internalStop(AbstractComponentRegistry.java:690) [infinispan-core-5.2.0.CR2-redhat-1.jar:5.2.0.CR2-redhat-1]
> at org.infinispan.factories.AbstractComponentRegistry.stop(AbstractComponentRegistry.java:568) [infinispan-core-5.2.0.CR2-redhat-1.jar:5.2.0.CR2-redhat-1]
> at org.infinispan.factories.GlobalComponentRegistry.stop(GlobalComponentRegistry.java:260) [infinispan-core-5.2.0.CR2-redhat-1.jar:5.2.0.CR2-redhat-1]
> at org.infinispan.manager.DefaultCacheManager.stop(DefaultCacheManager.java:742) [infinispan-core-5.2.0.CR2-redhat-1.jar:5.2.0.CR2-redhat-1]
> at org.infinispan.manager.AbstractDelegatingEmbeddedCacheManager.stop(AbstractDelegatingEmbeddedCacheManager.java:179) [infinispan-core-5.2.0.CR2-redhat-1.jar:5.2.0.CR2-redhat-1]
> at org.jboss.as.clustering.infinispan.subsystem.EmbeddedCacheManagerService.stop(EmbeddedCacheManagerService.java:76) [jboss-datagrid-infinispan-6.1.0.ER9-redhat-1.jar:6.1.0.ER9-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2]
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (ISPN-2822) Profile Infinispan when eviction enabled
by Martin Gencur (JIRA)
Martin Gencur created ISPN-2822:
-----------------------------------
Summary: Profile Infinispan when eviction enabled
Key: ISPN-2822
URL: https://issues.jboss.org/browse/ISPN-2822
Project: Infinispan
Issue Type: Task
Reporter: Martin Gencur
Assignee: Mircea Markus
Fix For: 5.3.0.Final
Profile Infinispan for different eviction strategies (LRU, LIRS) and search for hot spots in the code (places where Infinispan spends most time when executing).
Do this for two scenarios:
1) eviction enabled but no entries evicted (when the capacity is high)
2) eviction enabled and entries being evicted
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (ISPN-2821) CacheQuery sort() sorts entries in reverse order when cache values are updated
by Anna Manukyan (JIRA)
[ https://issues.jboss.org/browse/ISPN-2821?page=com.atlassian.jira.plugin.... ]
Anna Manukyan updated ISPN-2821:
--------------------------------
Attachment: LocalCacheTest.java
please look for testSort() method.
> CacheQuery sort() sorts entries in reverse order when cache values are updated
> -------------------------------------------------------------------------------
>
> Key: ISPN-2821
> URL: https://issues.jboss.org/browse/ISPN-2821
> Project: Infinispan
> Issue Type: Bug
> Components: Querying
> Affects Versions: 5.2.0.Final, 5.2.1
> Reporter: Anna Manukyan
> Assignee: Sanne Grinovero
> Attachments: LocalCacheTest.java
>
>
> While test development for the Query module, I've noticed some strange behaviour, which I couldn't explain anyhow.
> The case is the following:
> 3 new objects type of Person are created and put to the cache. The age parameter is set for all these objects.
> Then the age is changed for them (set to other values), and query is run using sort by age.
> The thing is that even though the sort is descending by default for integers, but the returned result list is sorted in ascending order.
> The code is:
> {code}
> Person person2 = new Person();
> person2.setAge(30);
> //some other setters
> Person person3 = new Person();
> person3.setAge(25);
> // some other setters
> cache.put("key1", person2);
> cache.put("key2", person3);
> person2.setAge(35);
> person3.setAge(12);
> Sort sort = new Sort( new SortField("age", SortField.STRING)); //<--- The same happens for SortField.INT
> queryParser = createQueryParser("name");
> Query luceneQuery = queryParser.parse("Goat");
> CacheQuery cacheQuery = Search.getSearchManager(cache).getQuery(luceneQuery);
> cacheQuery.sort(sort);
> List<Object> found = cacheQuery.list();
> assert found.size() == 2;
> assert found.get(0).equals(person2); //<------ The first element should be the one with higher age, but in reality in the first place it is person3
> assert found.get(1).equals(person3);
> {code}
> By the way, if initially you'll set the values in other order, then the test passes - the sorting works fine.
> {code}
> Person person2 = new Person();
> person2.setAge(25);
> //some other setters
> Person person3 = new Person();
> person3.setAge(30);
> // some other setters
> //............ the rest of the code
> {code}
> You can find attached the test file itself.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (ISPN-2821) CacheQuery sort() sorts entries in reverse order when cache values are updated
by Anna Manukyan (JIRA)
[ https://issues.jboss.org/browse/ISPN-2821?page=com.atlassian.jira.plugin.... ]
Anna Manukyan edited comment on ISPN-2821 at 2/13/13 4:38 AM:
--------------------------------------------------------------
In attachment - please look for testSort() method.
was (Author: amanukyan):
please look for testSort() method.
> CacheQuery sort() sorts entries in reverse order when cache values are updated
> -------------------------------------------------------------------------------
>
> Key: ISPN-2821
> URL: https://issues.jboss.org/browse/ISPN-2821
> Project: Infinispan
> Issue Type: Bug
> Components: Querying
> Affects Versions: 5.2.0.Final, 5.2.1
> Reporter: Anna Manukyan
> Assignee: Sanne Grinovero
> Attachments: LocalCacheTest.java
>
>
> While test development for the Query module, I've noticed some strange behaviour, which I couldn't explain anyhow.
> The case is the following:
> 3 new objects type of Person are created and put to the cache. The age parameter is set for all these objects.
> Then the age is changed for them (set to other values), and query is run using sort by age.
> The thing is that even though the sort is descending by default for integers, but the returned result list is sorted in ascending order.
> The code is:
> {code}
> Person person2 = new Person();
> person2.setAge(30);
> //some other setters
> Person person3 = new Person();
> person3.setAge(25);
> // some other setters
> cache.put("key1", person2);
> cache.put("key2", person3);
> person2.setAge(35);
> person3.setAge(12);
> Sort sort = new Sort( new SortField("age", SortField.STRING)); //<--- The same happens for SortField.INT
> queryParser = createQueryParser("name");
> Query luceneQuery = queryParser.parse("Goat");
> CacheQuery cacheQuery = Search.getSearchManager(cache).getQuery(luceneQuery);
> cacheQuery.sort(sort);
> List<Object> found = cacheQuery.list();
> assert found.size() == 2;
> assert found.get(0).equals(person2); //<------ The first element should be the one with higher age, but in reality in the first place it is person3
> assert found.get(1).equals(person3);
> {code}
> By the way, if initially you'll set the values in other order, then the test passes - the sorting works fine.
> {code}
> Person person2 = new Person();
> person2.setAge(25);
> //some other setters
> Person person3 = new Person();
> person3.setAge(30);
> // some other setters
> //............ the rest of the code
> {code}
> You can find attached the test file itself.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (ISPN-2821) CacheQuery sort() sorts entries in reverse order when cache values are updated
by Anna Manukyan (JIRA)
[ https://issues.jboss.org/browse/ISPN-2821?page=com.atlassian.jira.plugin.... ]
Anna Manukyan updated ISPN-2821:
--------------------------------
Description:
While test development for the Query module, I've noticed some strange behaviour, which I couldn't explain anyhow.
The case is the following:
3 new objects type of Person are created and put to the cache. The age parameter is set for all these objects.
Then the age is changed for them (set to other values), and query is run using sort by age.
The thing is that even though the sort is descending by default for integers, but the returned result list is sorted in ascending order.
The code is:
{code}
Person person2 = new Person();
person2.setAge(30);
//some other setters
Person person3 = new Person();
person3.setAge(25);
// some other setters
cache.put("key1", person2);
cache.put("key2", person3);
person2.setAge(35);
person3.setAge(12);
Sort sort = new Sort( new SortField("age", SortField.STRING)); //<--- The same happens for SortField.INT
queryParser = createQueryParser("name");
Query luceneQuery = queryParser.parse("Goat");
CacheQuery cacheQuery = Search.getSearchManager(cache).getQuery(luceneQuery);
cacheQuery.sort(sort);
List<Object> found = cacheQuery.list();
assert found.size() == 2;
assert found.get(0).equals(person2); //<------ The first element should be the one with higher age, but in reality in the first place it is person3
assert found.get(1).equals(person3);
{code}
By the way, if initially you'll set the values in other order, then the test passes - the sorting works fine.
{code}
Person person2 = new Person();
person2.setAge(25);
//some other setters
Person person3 = new Person();
person3.setAge(30);
// some other setters
//............ the rest of the code
{code}
You can find attached the test file itself.
was:
While test development for the Query module, I've noticed some strange behaviour, which I couldn't explain anyhow.
The case is the following:
3 new objects type of Person are created and put to the cache. The age parameter is set for all these objects.
Then the age is changed for them (set to other values), and query is run using sort by age.
The thing is that even though the sort is descending by default for integers, but the returned result list is sorted in ascending order.
The code is:
{code}
Person person2 = new Person();
person2.setAge(30);
//some other setters
Person person3 = new Person();
person3.setAge(25);
// some other setters
cache.put("key1", person2);
cache.put("key2", person3);
person2.setAge(35);
person3.setAge(12);
Sort sort = new Sort( new SortField("age", SortField.STRING)); //<--- The same happens for SortField.INT
queryParser = createQueryParser("name");
Query luceneQuery = queryParser.parse("Goat");
CacheQuery cacheQuery = Search.getSearchManager(cache).getQuery(luceneQuery);
cacheQuery.sort(sort);
List<Object> found = cacheQuery.list();
assert found.size() == 2;
assert found.get(0).equals(person2); //<------ The first element should be the one with higher age, but in reality in the first place it is person3
assert found.get(1).equals(person3);
{code}
You can find attached the test file itself.
> CacheQuery sort() sorts entries in reverse order when cache values are updated
> -------------------------------------------------------------------------------
>
> Key: ISPN-2821
> URL: https://issues.jboss.org/browse/ISPN-2821
> Project: Infinispan
> Issue Type: Bug
> Components: Querying
> Affects Versions: 5.2.0.Final, 5.2.1
> Reporter: Anna Manukyan
> Assignee: Sanne Grinovero
>
> While test development for the Query module, I've noticed some strange behaviour, which I couldn't explain anyhow.
> The case is the following:
> 3 new objects type of Person are created and put to the cache. The age parameter is set for all these objects.
> Then the age is changed for them (set to other values), and query is run using sort by age.
> The thing is that even though the sort is descending by default for integers, but the returned result list is sorted in ascending order.
> The code is:
> {code}
> Person person2 = new Person();
> person2.setAge(30);
> //some other setters
> Person person3 = new Person();
> person3.setAge(25);
> // some other setters
> cache.put("key1", person2);
> cache.put("key2", person3);
> person2.setAge(35);
> person3.setAge(12);
> Sort sort = new Sort( new SortField("age", SortField.STRING)); //<--- The same happens for SortField.INT
> queryParser = createQueryParser("name");
> Query luceneQuery = queryParser.parse("Goat");
> CacheQuery cacheQuery = Search.getSearchManager(cache).getQuery(luceneQuery);
> cacheQuery.sort(sort);
> List<Object> found = cacheQuery.list();
> assert found.size() == 2;
> assert found.get(0).equals(person2); //<------ The first element should be the one with higher age, but in reality in the first place it is person3
> assert found.get(1).equals(person3);
> {code}
> By the way, if initially you'll set the values in other order, then the test passes - the sorting works fine.
> {code}
> Person person2 = new Person();
> person2.setAge(25);
> //some other setters
> Person person3 = new Person();
> person3.setAge(30);
> // some other setters
> //............ the rest of the code
> {code}
> You can find attached the test file itself.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (ISPN-2821) CacheQuery sort() sorts entries in reverse order when cache values are updated
by Anna Manukyan (JIRA)
Anna Manukyan created ISPN-2821:
-----------------------------------
Summary: CacheQuery sort() sorts entries in reverse order when cache values are updated
Key: ISPN-2821
URL: https://issues.jboss.org/browse/ISPN-2821
Project: Infinispan
Issue Type: Bug
Components: Querying
Affects Versions: 5.2.1, 5.2.0.Final
Reporter: Anna Manukyan
Assignee: Sanne Grinovero
While test development for the Query module, I've noticed some strange behaviour, which I couldn't explain anyhow.
The case is the following:
3 new objects type of Person are created and put to the cache. The age parameter is set for all these objects.
Then the age is changed for them (set to other values), and query is run using sort by age.
The thing is that even though the sort is descending by default for integers, but the returned result list is sorted in ascending order.
The code is:
{code}
Person person2 = new Person();
person2.setAge(30);
//some other setters
Person person3 = new Person();
person3.setAge(25);
// some other setters
cache.put("key1", person2);
cache.put("key2", person3);
person2.setAge(35);
person3.setAge(12);
Sort sort = new Sort( new SortField("age", SortField.STRING)); //<--- The same happens for SortField.INT
queryParser = createQueryParser("name");
Query luceneQuery = queryParser.parse("Goat");
CacheQuery cacheQuery = Search.getSearchManager(cache).getQuery(luceneQuery);
cacheQuery.sort(sort);
List<Object> found = cacheQuery.list();
assert found.size() == 2;
assert found.get(0).equals(person2); //<------ The first element should be the one with higher age, but in reality in the first place it is person3
assert found.get(1).equals(person3);
{code}
You can find attached the test file itself.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month