[
http://jira.jboss.com/jira/browse/JBCACHE-1352?page=all ]
Manik Surtani updated JBCACHE-1352:
-----------------------------------
Workaround Description: As a workaround, don't pass in an existing channel. Allow
JBoss Cache to create one for you. Put your channel configs in the cache config XML. You
can even use the mux this way.
Workaround: [Workaround Exists]
Inifinite wait when creating a TreeCache on an existing channel
---------------------------------------------------------------
Key: JBCACHE-1352
URL:
http://jira.jboss.com/jira/browse/JBCACHE-1352
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.4.1.SP9
Environment: Windows XP SP2, WebSphere Application Server 6.0.2.25, J2RE 1.4.2
Reporter: Kai Blankenhorn
Assigned To: Manik Surtani
Fix For: 1.4.X
When creating a new TreeCache using the single argument constructor and an existing
channel, the startService method hangs infinitely when called.
Code to reproduce:
-----
// Builds a properties String
JGroupsProperties props = new JGroupsProperties();
JChannel channel = new JChannel(props.getProps());
cache = new TreeCache(channel);
cache.setCacheMode(TreeCache.REPL_SYNC);
cache.startService();
-----
The wait occurs in the following method call:
Vector(Object).wait(long, int) line: not available [native method]
Vector(Object).wait() line: 199
TreeCache.getCoordinator() line: 1840
TreeCache.determineCoordinator() line: 1818
TreeCache.startService() line: 1580
Apparently, the viewAccepted method that should normally notify the members Vector is
never called.
JGroups version is 2.4.2. The JGroups config is almost identical to
replAsync-service.xml.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira