[
https://jira.jboss.org/jira/browse/JBCACHE-1432?page=com.atlassian.jira.p...
]
Bill Middleton commented on JBCACHE-1432:
-----------------------------------------
See
http://sourceforge.net/mailarchive/forum.php?thread_name=3da2061200026bfe...
seems others are finally seeing 64bit troubles as well. (Although this seems a jgroups
issue, or perhaps even lower, now)
Cache corrupted by 64bit windows member
---------------------------------------
Key: JBCACHE-1432
URL:
https://jira.jboss.org/jira/browse/JBCACHE-1432
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.2.1.CR1
Environment: Windows 64bit OS with either 32 or 64bit jvm
in cluster with any linux OS (32 or 64bit) with any linux jvm.
Reporter: Bill Middleton
Assignee: Manik Surtani
Fix For: 3.2.0.GA
Hello. We've run into some trouble in attempting to bring a 64bit windows machine
into an existing cluster. The cluster has (had) two 64bit linux members and was running
fine when we attempted to insert a 64bit windows machine into the cluster. Anytime the
64bit windows machine wrote a node, the node was thereafter unreadable by either of the
original cluster members. Exceptions of the following form were thrown by the other
members (will attach stacktrace as comment)
I attempted to get help on this issue in the user forum, but it seems that nobody else is
running 64bit windows as a cluster member with other OS's in the cluster. I hope
perhaps someone can at least confirm this now formally?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira