Bug 745902 (EDG-15) - RemoteCacheManager failure in multi-threaded environment with maxActive=Integer.MAX_VALUE
Summary: RemoteCacheManager failure in multi-threaded environment with maxActive=Integ...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: EDG-15
Product: JBoss Data Grid 6
Classification: JBoss
Component: unspecified
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 6.0.0
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/EDG-15
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-13 22:53 UTC by Trustin Lee
Modified: 2012-08-15 16:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-01 08:10:46 UTC
Type: Feature Request

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EDG-15 0 None None None Never

Description Trustin Lee 2011-07-13 22:53:56 UTC 
project_key: EDG

Michal is getting errors like these, when I run test with 100 threads using either shared or multiple remote cache managers:

{code}
java.lang.IllegalStateException: We should not reach here!
	at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:73)
	at org.infinispan.client.hotrod.impl.RemoteCacheImpl.put(RemoteCacheImpl.java:201)
	at org.infinispan.CacheSupport.put(CacheSupport.java:51)
	at org.jboss.edg.test.MultiThreadedManualTest$Runner.run(MultiThreadedManualTest.java:77)
{code}

The cause in his environment came to connection-pool configuration property "maxActive" clients set to Integer.MAX_VALUE
Comment 1 Trustin Lee 2011-07-13 22:54:28 UTC 
Link: Added: This issue depends ISPN-1199
Comment 2 Galder Zamarreño 2011-08-03 07:24:46 UTC 
Michal, can you check that with CR8 this is gone?
Comment 3 Anne-Louise Tangring 2011-09-26 19:41:24 UTC 
Docs QE Status: Removed: NEW
Note You need to log in before you can comment on or make changes to this bug.