I would suggest requesting resources by IP address. On server A, you can perform an update, and then request that same resource from server B. On update the resource should be invalidated from participating servers in the cluster, so the resulting request on server B should be the (newly) updated resource.

我建议通过IP地址请求资源。在服务器A上,您可以执行更新,然后从服务器B请求相同的资源。在更新时,资源应该从群集中的参与服务器失效,因此服务器B上的结果请求应该是(新)更新的资源。

The easiest would be to check the 2nd level cache contents via the embedded console that JBoss 5 comes with and do an exercise like the one @Rich Kroll suggests.

最简单的方法是通过JBoss 5附带的嵌入式控制台检查二级缓存内容并进行类似@Rich Kroll建议的练习。

You can have a look at the Cache statistics via the embedded console that JBoss 5 comes with. It'll show the number of invalidations that have happened.

您可以通过JBoss 5附带的嵌入式控制台查看Cache统计信息。它将显示已发生的失效数量。